<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><div dir="ltr">On Mar 6, 2019, at 12:23, Chris Punches <<a href="mailto:punches.chris@gmail.com">punches.chris@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><div dir="auto">Perms options are file system specific you'll need to research the options for your file system type</div></div></blockquote><div><br></div><div>Not really? Unless you’re diving into selinux or ACLs. Maybe there’s a filesystem out there that doesn’t support the user/group ownership and octal user/group/other permissions of typical *nix, but that would mean a huge mess of stuff would be different, not just those two things. In any case, I don’t think that would apply here.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Wed, Mar 6, 2019, 1:08 PM Stephen P. Molnar <<a href="mailto:s.molnar@sbcglobal.net">s.molnar@sbcglobal.net</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
I would beg the group's indulgence again, as I want to be sure I get
this correctly.<br></div></blockquote></div></div></blockquote><div><br></div><div>No worries. We all had to start our Linux adventures somewhere.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
I think this is what I want as the fstab:<br>...</div></blockquote></div></div></blockquote><div><br></div>Nothing jumps out at me as egregiously wrong. Make a backup of your known good fstab file so you can start over, and have a LiveCD / bootable USB drive or something like that handy just in case you typo something. It happens to all of us. If your flavor allows you to create a rescue disk, that’d be easiest. If not, most any LiveCD/USB (Linux, of course) type system will get you at least shell prompt and access to the disks - thus /etc/fstab.<div><br></div><div>Technically I suppose it’s possible to FUBAR a system messing with fstab, but it’s unlikely you’ll do any damage that can’t be recovered by booting from alternate media, fixing up fstab, and trying again.<br><br><blockquote type="cite"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
in addition I need to have:<br>
<br>
/sbd1<br>
/Apps<br>
/dev/sdb1<br>
/devApps<br></div></blockquote></div></div></blockquote><div><br></div><div>So as far as permissions, don’t worry about the device (/dev/sd*) files themselves. Focus on the mount points - ie /Apps. It’s been a while since I’ve done this, but IIRC, you should just need to set ‘comp’ as the owner of /Apps, and make sure /Apps has at least 700 permissions set.</div><div><br></div><div>Assuming you haven’t put any files on the new mounted file system(s) yet, this should do the trick:</div><div><br></div><div>$ sudo chown comp /Apps</div><div>$ sudo chmod 755 /Apps # or 700 if you want to restrict access to anyone not “comp”</div><div><br></div><div>Check out the manpage for chmod.</div><br></div></body></html>