Re: Fstab Questions (Final time)
On 03/18/2019 02:50 PM, Dan Ritter wrote: Stephen P. Molnar wrote: On 03/18/2019 11:36 AM, Dan Ritter wrote: Stephen P. Molnar wrote: I now have a system that boots without any problems. The fstab is: # # / was on /dev/sda1 during installation UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 from man mount: users Allow any user to mount and to unmount the filesystem, even when some other ordinary user mounted it. This option implies the options noexec, nosuid, and nodev noexec overrules your permissions. -dsr- This makes sense. So what is the solution? Remove users from the fstab entries? You can do that, or you can add the option exec. -dsr- Many thanks. adding the exec option solved the problem. -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
Re: Fstab Questions (Final time)
Stephen P. Molnar wrote: > > On 03/18/2019 11:36 AM, Dan Ritter wrote: > > Stephen P. Molnar wrote: > > > I now have a system that boots without any problems. > > > > > > The fstab is: > > > > > > # > > > # / was on /dev/sda1 during installation > > > UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 > > > # swap was on /dev/sda5 during installation > > > UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 > > > UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 > > > UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 > > > /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > > > > > from man mount: > > > > users Allow any user to mount and to unmount the filesystem, > > even when some other ordinary user mounted it. This option > > implies the options noexec, nosuid, and nodev > > > > noexec overrules your permissions. > > > > -dsr- > > > > > > This makes sense. So what is the solution? Remove users from the fstab > entries? You can do that, or you can add the option exec. -dsr-
Re: Fstab Questions (Final time)
On 03/18/2019 11:36 AM, Dan Ritter wrote: Stephen P. Molnar wrote: I now have a system that boots without any problems. The fstab is: # # / was on /dev/sda1 during installation UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 comp@AbNormal:/sdc1/Apps$ l total 68208 drwxr-xr-x 27 comp comp 4096 Jan 1 09:17 Fortran -rwxrwxrwx 1 comp comp 69826864 Mar 18 10:16 Miniconda3-latest-Linux-x86_64.sh drwxr-xr-x 57 comp comp 4096 Feb 11 13:24 Models drwxr-xr-x 3 comp comp 4096 Mar 17 08:43 orca drwxr-xr-x 41 comp comp 4096 Feb 2 13:02 Python Unfortunately, when I attemped running MMiniconda3-latest-Linux-x86_64.sh I got; in part: Miniconda3 will now be installed into this location: /home/comp/miniconda3 - Press ENTER to confirm the location - Press CTRL-C to abort the installation - Or specify a different location below [/home/comp/miniconda3] >>> /sdc1/Apps/miniconda3 PREFIX=/sdc1/Apps/miniconda3 installing: python-3.7.1-h0371630_7 ... Miniconda3-latest-Linux-x86_64.sh: 370: Miniconda3-latest-Linux-x86_64.sh: /sdc1/Apps/miniconda3/pkgs/python-3.7.1-h0371630_7/bin/python: Permission denied Even I can see that I have a permissions problem. from man mount: users Allow any user to mount and to unmount the filesystem, even when some other ordinary user mounted it. This option implies the options noexec, nosuid, and nodev noexec overrules your permissions. -dsr- This makes sense. So what is the solution? Remove users from the fstab entries? -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
Re: Fstab Questions (Final time)
Stephen P. Molnar wrote: > > I now have a system that boots without any problems. > > The fstab is: > > # > # / was on /dev/sda1 during installation > UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 > # swap was on /dev/sda5 during installation > UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 > UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 > UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 > /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > > comp@AbNormal:/sdc1/Apps$ l > total 68208 > drwxr-xr-x 27 comp comp 4096 Jan 1 09:17 Fortran > -rwxrwxrwx 1 comp comp 69826864 Mar 18 10:16 > Miniconda3-latest-Linux-x86_64.sh > drwxr-xr-x 57 comp comp 4096 Feb 11 13:24 Models > drwxr-xr-x 3 comp comp 4096 Mar 17 08:43 orca > drwxr-xr-x 41 comp comp 4096 Feb 2 13:02 Python > > Unfortunately, when I attemped running MMiniconda3-latest-Linux-x86_64.sh I > got; > > in part: > > Miniconda3 will now be installed into this location: > /home/comp/miniconda3 > > - Press ENTER to confirm the location > - Press CTRL-C to abort the installation > - Or specify a different location below > > [/home/comp/miniconda3] >>> /sdc1/Apps/miniconda3 > PREFIX=/sdc1/Apps/miniconda3 > installing: python-3.7.1-h0371630_7 ... > Miniconda3-latest-Linux-x86_64.sh: 370: Miniconda3-latest-Linux-x86_64.sh: > /sdc1/Apps/miniconda3/pkgs/python-3.7.1-h0371630_7/bin/python: Permission > denied > > Even I can see that I have a permissions problem. from man mount: users Allow any user to mount and to unmount the filesystem, even when some other ordinary user mounted it. This option implies the options noexec, nosuid, and nodev noexec overrules your permissions. -dsr-
Re: Fstab Questions (Final time)
On Monday, March 18, 2019 09:59:03 AM Dan Purgert wrote: > rhkra...@gmail.com wrote: > > I (some time ago) read the FHS more than once, and had some input into > > changing some portions of it (related to /home -- my intent was to allow > > owned files to be either in /home/ or in some other, > > arbitrarily named, top level directory chosen by the user. > > So, you'd move their home directory then? Or do you mean to say that > > $HOME -> /home/username (as is usually done) > $FILES -> /somewhere (some new directory for them to throw stuff) Hmm, I guess (maybe) in your terms, I use the latter -- I maintain (that is, keep) /home/, but I use it for configuration type information -- the stuff that is often in . (hidden) files or directories. For what I consider my real user data (movies, documents, MIDI files, ...), I create new top level directories (with appropriate subdirectories under them. The top level is usually named something like / or / (for the 2nd and beyond), and then subdirectories like //Documents, //music. To the extent possible, I try to change the configuration of any program that I use so that if I save a program from those files, they go to an appropriate subdirectory under / by default or display a dialog to let me choose the location. Currently, I think the only program that I haven't managed to get to do that is the Firefox in Jessie. (No problem with Firefox in Wheezy, and I haven't yet set up anything beyond jessie.)
Re: Fstab Questions (Final time)
On Monday, March 18, 2019 09:53:53 AM Michael Stone wrote: > On Mon, Mar 18, 2019 at 12:56:20PM -, Dan Purgert wrote: > >Or is there some caveat that allows for mounting new partitions into > >the root directory, while remaining "FHS compliant"? > > FHS is about determining where vendors install things, not about telling > you how to arrange your own system. Good answer (better than mine)!
Re: Fstab Questions (Final time)
On 03/18/2019 09:59 AM, Dan Purgert wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 rhkra...@gmail.com wrote: On Monday, March 18, 2019 08:56:20 AM Dan Purgert wrote: I'm bad with the FHS, but shouldn't say your shark-attack movies be somewhere in /usr(/local) ? I'd say no -- if they were shark attack programs, /usr/local could be appropriate. (/usr/local is for local programs) I think source code can go there as well (/usr/local/src). But taking a quick look at the FHS, /usr/local is indeed more geared towards programs, rather than just "read-only" data. So, yeah, /usr/local is probably out. If they are files (movies, documents, MIDI files, ), they should be either in /home/ ... (keep reading) Maybe I misinterpreted it -- I thought we were talking about "shared" media, saved on an extra harddrive / partition, rather than something that was more "personal" in nature as implied by sticking it in $HOME. maybe /srv if you're running a media server? I've had some input into the FHS -- read more below -- but I don't remember offhand about /srv -- I vaguely think that is ok, but keep reading ... According to the FHS[1] , "/srv - Data for services provided by this system". So, if it's a media server (rather than a desktop with extra harddrive for local watching), it seems a mountpoint within /srv (e.g. /srv/movies ) would conform to things. Or is there some caveat that allows for mounting new partitions into the root directory, while remaining "FHS compliant"? I (some time ago) read the FHS more than once, and had some input into changing some portions of it (related to /home -- my intent was to allow owned files to be either in /home/ or in some other, arbitrarily named, top level directory chosen by the user. So, you'd move their home directory then? Or do you mean to say that $HOME -> /home/username (as is usually done) $FILES -> /somewhere (some new directory for them to throw stuff) I do this all the time, and I believe I am in compliance with the FHS. If anyone (who is familiar with the FHS) believes different, I'd like to know, and I would then attempt to amend the FHS appropriately. That approach seems to be non-compliant, with the idea that the root filesystem (/) is supposed to be "as small as reasonably possible". Though that being said, the FHS seems geared more toward programmers (i.e. "use the defined directories for your application's needs") and distro maintainers (i.e. "think very carefully before customizing your directories...") -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlyPpCUACgkQjhHd8xJ5 ooGmtwgAqBPsqSGF1sBvOcPAc+52SPv09ZqOJK6kZBoEyQpihan6dSic3B1Ho+0K 0BrM6lEglGJvD6aL6qds5dfg9hvkaSeurd+L+mV6mlY/hOhx9/K5fkVUCKkeRlHv Y/W+mgdLQdOOtPAe3cWBZXFSNyg2N/63US2ScnW65OwQiBKnN+SPEhB3mpBBl+2p ZZy8/EQ7zOEHg7+3pkcb5ButnP10rfv1ROmiTXuFP5rSCDoHeHEZVP9rO9+K5bba EpLgkrT3odtSBS0bajMr/X0bcUbv+SmHl946tobI5oawQ1Xq3qKdkvCkMKaPo5J2 we/dTA1sNVVdqEEtimqUMFRZOLV0OQ== =HJ3a -END PGP SIGNATURE- While I appreciate the comments of folks much more learned than I in the intricacies of Linux, I would like to hue to the intent of my original thread of postings. That is requesting help in getting my OS setup after some hardware charges. (please note I am not trying to start a flame war.) I now have a system that boots without any problems. The fstab is: # # / was on /dev/sda1 during installation UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 which results in: comp@AbNormal:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 457.9G 0 part / ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 7.9G 0 part [SWAP] sdb 8:16 0 1.8T 0 disk ├─sdb1 8:17 0 1.8T 0 part /sdb1 ├─sdb2 8:18 0 1K 0 part └─sdb5 8:21 0 7.9G 0 part sdc 8:32 0 465.8G 0 disk └─sdc1 8:33 0 465.8G 0 part /sdc1 sr0 11:0 1 1024M 0 rom Further, as root I created a directory; /sbc1/Apps and gave it permissions chmod 777 /sdc1/Apps -R. I can read and write to Apps, Currently I have: comp@AbNormal:/sdc1/Apps$ l total 68208 drwxr-xr-x 27 comp comp 4096 Jan 1 09:17 Fortran -rwxrwxrwx 1 comp comp 69826864 Mar 18 10:16 Miniconda3-latest-Linux-x86_64.sh drwxr-xr-x 57 comp comp 4096 Feb 11 13:24 Models drwxr-xr-x 3 comp comp 4096 Mar 17 08:43 orca drwxr-xr-x 41 comp comp 4096 Feb 2 13:02 Python Unfortunately, when I attemped running MMiniconda3-latest-Linux-x86_64.sh I got; in part: Miniconda3 will now be installed into this location: /home/comp/miniconda3 - Press ENTER to confirm the location - Press CTRL-C to abort the installation - Or specify a different location below [/home/comp/miniconda3] >>> /sdc1/Apps/miniconda3
Re: Fstab Questions (Final time)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 rhkra...@gmail.com wrote: > On Monday, March 18, 2019 08:56:20 AM Dan Purgert wrote: >> I'm bad with the FHS, but shouldn't say your shark-attack movies be >> somewhere in /usr(/local) ? > > I'd say no -- if they were shark attack programs, /usr/local could be > appropriate. (/usr/local is for local programs) I think source code can go there as well (/usr/local/src). But taking a quick look at the FHS, /usr/local is indeed more geared towards programs, rather than just "read-only" data. So, yeah, /usr/local is probably out. > > If they are files (movies, documents, MIDI files, ), they should > be either in /home/ ... (keep reading) Maybe I misinterpreted it -- I thought we were talking about "shared" media, saved on an extra harddrive / partition, rather than something that was more "personal" in nature as implied by sticking it in $HOME. > >> maybe /srv if you're running a media >> server? > > I've had some input into the FHS -- read more below -- but I don't > remember offhand about /srv -- I vaguely think that is ok, but keep > reading ... According to the FHS[1] , "/srv - Data for services provided by this system". So, if it's a media server (rather than a desktop with extra harddrive for local watching), it seems a mountpoint within /srv (e.g. /srv/movies ) would conform to things. > >> >> Or is there some caveat that allows for mounting new partitions into >> the root directory, while remaining "FHS compliant"? > > I (some time ago) read the FHS more than once, and had some input into > changing some portions of it (related to /home -- my intent was to allow > owned files to be either in /home/ or in some other, > arbitrarily named, top level directory chosen by the user. So, you'd move their home directory then? Or do you mean to say that $HOME -> /home/username (as is usually done) $FILES -> /somewhere (some new directory for them to throw stuff) > > I do this all the time, and I believe I am in compliance with the FHS. > > If anyone (who is familiar with the FHS) believes different, I'd like > to know, and I would then attempt to amend the FHS appropriately. That approach seems to be non-compliant, with the idea that the root filesystem (/) is supposed to be "as small as reasonably possible". Though that being said, the FHS seems geared more toward programmers (i.e. "use the defined directories for your application's needs") and distro maintainers (i.e. "think very carefully before customizing your directories...") -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlyPpCUACgkQjhHd8xJ5 ooGmtwgAqBPsqSGF1sBvOcPAc+52SPv09ZqOJK6kZBoEyQpihan6dSic3B1Ho+0K 0BrM6lEglGJvD6aL6qds5dfg9hvkaSeurd+L+mV6mlY/hOhx9/K5fkVUCKkeRlHv Y/W+mgdLQdOOtPAe3cWBZXFSNyg2N/63US2ScnW65OwQiBKnN+SPEhB3mpBBl+2p ZZy8/EQ7zOEHg7+3pkcb5ButnP10rfv1ROmiTXuFP5rSCDoHeHEZVP9rO9+K5bba EpLgkrT3odtSBS0bajMr/X0bcUbv+SmHl946tobI5oawQ1Xq3qKdkvCkMKaPo5J2 we/dTA1sNVVdqEEtimqUMFRZOLV0OQ== =HJ3a -END PGP SIGNATURE- -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
Re: Fstab Questions (Final time)
On Mon, Mar 18, 2019 at 12:56:20PM -, Dan Purgert wrote: I'm bad with the FHS, but shouldn't say your shark-attack movies be somewhere in /usr(/local) ? maybe /srv if you're running a media server? Or is there some caveat that allows for mounting new partitions into the root directory, while remaining "FHS compliant"? FHS is about determining where vendors install things, not about telling you how to arrange your own system.
Re: Fstab Questions (Final time)
On Monday, March 18, 2019 08:56:20 AM Dan Purgert wrote: > I'm bad with the FHS, but shouldn't say your shark-attack movies be > somewhere in /usr(/local) ? I'd say no -- if they were shark attack programs, /usr/local could be appropriate. (/usr/local is for local programs) If they are files (movies, documents, MIDI files, ), they should be either in /home/ ... (keep reading) > maybe /srv if you're running a media > server? I've had some input into the FHS -- read more below -- but I don't remember offhand about /srv -- I vaguely think that is ok, but keep reading ... > > Or is there some caveat that allows for mounting new partitions into > the root directory, while remaining "FHS compliant"? I (some time ago) read the FHS more than once, and had some input into changing some portions of it (related to /home -- my intent was to allow owned files to be either in /home/ or in some other, arbitrarily named, top level directory chosen by the user. I do this all the time, and I believe I am in compliance with the FHS. If anyone (who is familiar with the FHS) believes different, I'd like to know, and I would then attempt to amend the FHS appropriately.
Re: Fstab Questions (Final time)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Greg Wooledge wrote: > On Sun, Mar 17, 2019 at 07:43:42AM -0400, Stephen P. Molnar wrote: >> Finally, here is what I am proposing adding to the fstab: >> >> UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 >> UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 > > You keep mounting file systems on directories that are named for transient > and fluid device names that have no MEANING or CONSISTENCY. > > The place where you mount a file system should have a meaningful name > that tells you what the file system IS, or what it's FOR. Is it your > collection of shark attack movies? Then name it /shark or something. > Not /sdc1. I'm bad with the FHS, but shouldn't say your shark-attack movies be somewhere in /usr(/local) ? maybe /srv if you're running a media server? Or is there some caveat that allows for mounting new partitions into the root directory, while remaining "FHS compliant"? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlyPlXQACgkQjhHd8xJ5 ooFhugf+NzUYmCr4WVyoZwqG7CZx8p0bG/pUCVOGT0zAbyQreU20mUZk30OP9ZaZ YYZdPEr1/8qHxQXQWgZtk3cGWTFMDiG57AIAFpU6zPgWoqgNuqgst0CVulseSoxm ZpSj12F+WG+NDrPJpswcXZihArKYMbDgObjgUliFk1fTdTb87LM4QMlob9GpAJP/ EKszA/oh0d55KT//yj4FJGMCvPTl7Bz0kfFAyT2PMoIS8dJEI/+CP+hftk9pe3zr hYLtgyaSzq3g8fjd6vk/e6JXJBSRksrIH6ZjvXznQelEwFwFRXFDDrkfKkDnY+Mq BM+6ZZWQyKPULmxo0tQiKLIdPzZZyw== =XT0l -END PGP SIGNATURE- -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
Re: Fstab Questions (Final time)
On Sun, Mar 17, 2019 at 07:43:42AM -0400, Stephen P. Molnar wrote: > Finally, here is what I am proposing adding to the fstab: > > UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 > UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 You keep mounting file systems on directories that are named for transient and fluid device names that have no MEANING or CONSISTENCY. The place where you mount a file system should have a meaningful name that tells you what the file system IS, or what it's FOR. Is it your collection of shark attack movies? Then name it /shark or something. Not /sdc1.
Re: Fstab Questions (Final time)
Hi, I would like to offer you a general tip for future queries. On Sun, 17 Mar 2019 at 22:44, Stephen P. Molnar wrote: > > Here is my current drive structure: > [...] > > Here are the the results of blkid: > [...] > > Here is the curerent fstab (missing exteraneous comment statements): > [...] >From the perspective of someone reading your message in order to possibly assist you, this style of presenting information is unsettling, because often the output of a command can be different depending on the details of the command used. There's no need to write "here are the results of", just copy and paste both the entire command and its output. For examples: # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 931.5G 0 disk # cat /etc/fstab LABEL=FOO/ext4errors=remount-ro0 1 Or cat /etc/fstab | grep -v '^#' if you want to strip comments. That style is both more concise, and more informative to the reader.
Re: Fstab Questions (Final time)
On Sun 17 Mar 2019 at 05:24:05 (-0700), Charlie Kravetz wrote: > On Sun, 17 Mar 2019 07:43:42 -0400 "Stephen P. Molnar" > wrote: > > >At least I hope it's the final time. > > > > > >I know that I have posted this question before, but due to reinstalling > >the OS, I have a clean slate at this point. Now, I've done quite a bit > >of goggling and utubing and I want to be sure that I'm not going to > >crash the system when I add two drives to the fstab. > > > >Here is my current drive structure: > > > > > >NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > >sda 8:0 0 465.8G 0 disk > >├─sda1 8:1 0 457.9G 0 part / > >├─sda2 8:2 0 1K 0 part > >└─sda5 8:5 0 7.9G 0 part [SWAP] > >sdb 8:16 0 1.8T 0 disk > >├─sdb1 8:17 0 1.8T 0 part > >├─sdb2 8:18 0 1K 0 part > >└─sdb5 8:21 0 7.9G 0 part > >sdc 8:32 0 465.8G 0 disk > >└─sdc1 8:33 0 465.8G 0 part > >sr0 11:0 1 1024M 0 rom > > > >sdc is a new SSD and I formatted it with only one partition. sdb still > >has a previous OS that I intend removing. > > > >Here are the the results of blkid: > > > >/dev/sda1: UUID="71f1ed49-9178-4bbc-b872-510f7982e245" TYPE="ext4" > >PARTUUID="1435f170-01" > >/dev/sda5: UUID="4b041dec-d00f-4acf-a731-f6a34d885105" TYPE="swap" > >PARTUUID="1435f170-05" > >/dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" > >PARTUUID="eb2be395-01" > >/dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" > >PARTUUID="0bc7db76-01" > >/dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" > >PARTUUID="0bc7db76-05" > > > >Here is the curerent fstab (missing exteraneous comment statements): > > > ># > ># / was on /dev/sda1 during installation > >UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 > ># swap was on /dev/sda5 during installation > >UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 > >/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > > > >Finally, here is what I am proposing adding to the fstab: > > > >UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 > >UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 > > > >Note: I have added /sdb1 and /sdc1. > > > >The only questions at this point are: > >1. Will these changes crash the system,and > >2. Will I be able to read adn write to the added drives? > > I am no expert, and they can correct me if I am wrong. Should "users" > be singular, as in "user"? That depends on the m.o. If Ethel mounts the disk each morning and Ethan expects to unmount it in the afternoon, then "user" will thwart him. But in any case I can't see the point of having either, unless accompanied by "noauto", because the OS will already have done the deed. (I can see why the possibility is offered; just not a corresponding scenario.) The OP appears very timid about making this change, hence my recommendation for the inclusion of "nofail" on any partition that's not essential for the system to just run successfully. Once there is confidence that the mounts are working ok, then the nofail items could be removed, so that a successful boot shows the system is ready to perform all its tasks (rather than just being in a running state). But I think I've editorialized too much already, so I'll leave it there. (I'm no expert.) Cheers, David.
Re: Fstab Questions (Final time)
On Sun, 17 Mar 2019 07:43:42 -0400 "Stephen P. Molnar" wrote: >At least I hope it's the final time. > > >I know that I have posted this question before, but due to reinstalling >the OS, I have a clean slate at this point. Now, I've done quite a bit >of goggling and utubing and I want to be sure that I'm not going to >crash the system when I add two drives to the fstab. > >Here is my current drive structure: > > >NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >sda 8:0 0 465.8G 0 disk >├─sda1 8:1 0 457.9G 0 part / >├─sda2 8:2 0 1K 0 part >└─sda5 8:5 0 7.9G 0 part [SWAP] >sdb 8:16 0 1.8T 0 disk >├─sdb1 8:17 0 1.8T 0 part >├─sdb2 8:18 0 1K 0 part >└─sdb5 8:21 0 7.9G 0 part >sdc 8:32 0 465.8G 0 disk >└─sdc1 8:33 0 465.8G 0 part >sr0 11:0 1 1024M 0 rom > >sdc is a new SSD and I formatted it with only one partition. sdb still >has a previous OS that I intend removing. > >Here are the the results of blkid: > >/dev/sda1: UUID="71f1ed49-9178-4bbc-b872-510f7982e245" TYPE="ext4" >PARTUUID="1435f170-01" >/dev/sda5: UUID="4b041dec-d00f-4acf-a731-f6a34d885105" TYPE="swap" >PARTUUID="1435f170-05" >/dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" >PARTUUID="eb2be395-01" >/dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" >PARTUUID="0bc7db76-01" >/dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" >PARTUUID="0bc7db76-05" > >Here is the curerent fstab (missing exteraneous comment statements): > ># ># / was on /dev/sda1 during installation >UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 ># swap was on /dev/sda5 during installation >UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 >/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > >Finally, here is what I am proposing adding to the fstab: > >UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 >UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 > >Note: I have added /sdb1 and /sdc1. > >The only questions at this point are: >1. Will these changes crash the system,and >2. Will I be able to read adn write to the added drives? > >Thanks in advance. > I am no expert, and they can correct me if I am wrong. Should "users" be singular, as in "user"? -- Charlie Kravetz Linux Registered User Number 425914 [http://linuxcounter.net/user/425914.html] Never let anyone steal your DREAM. [http://keepingdreams.com]
Re: Fstab Questions (Final time)
On 3/17/2019 12:43 PM, Stephen P. Molnar wrote: > At least I hope it's the final time. > > > I know that I have posted this question before, but due to reinstalling > the OS, I have a clean slate at this point. Now, I've done quite a bit > of goggling and utubing and I want to be sure that I'm not going to > crash the system when I add two drives to the fstab. > > Here is my current drive structure: > > > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:0 0 465.8G 0 disk > ├─sda1 8:1 0 457.9G 0 part / > ├─sda2 8:2 0 1K 0 part > └─sda5 8:5 0 7.9G 0 part [SWAP] > sdb 8:16 0 1.8T 0 disk > ├─sdb1 8:17 0 1.8T 0 part > ├─sdb2 8:18 0 1K 0 part > └─sdb5 8:21 0 7.9G 0 part > sdc 8:32 0 465.8G 0 disk > └─sdc1 8:33 0 465.8G 0 part > sr0 11:0 1 1024M 0 rom > > sdc is a new SSD and I formatted it with only one partition. sdb still > has a previous OS that I intend removing. > > Here are the the results of blkid: > > /dev/sda1: UUID="71f1ed49-9178-4bbc-b872-510f7982e245" TYPE="ext4" > PARTUUID="1435f170-01" > /dev/sda5: UUID="4b041dec-d00f-4acf-a731-f6a34d885105" TYPE="swap" > PARTUUID="1435f170-05" > /dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" > PARTUUID="eb2be395-01" > /dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" > PARTUUID="0bc7db76-01" > /dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" > PARTUUID="0bc7db76-05" > > Here is the curerent fstab (missing exteraneous comment statements): > > # > # / was on /dev/sda1 during installation > UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 > # swap was on /dev/sda5 during installation > UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 > /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 > > Finally, here is what I am proposing adding to the fstab: > > UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 > UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 > > Note: I have added /sdb1 and /sdc1. > > The only questions at this point are: > 1. Will these changes crash the system,and Before rebooting the system try 'mount -a' and fix any error before rebooting. If 'mount -a' does not conplain, you should be fine; if an error were to happened, you can always recover. Also, keep an unmodified copy of your fstab file before modifying it. > 2. Will I be able to read adn write to the added drives? > Looks like it, trying your changes will be the only way to tell. P.S. If you are that afraid of messing around, having a test environment is clearly needed. -- John Doe
Fstab Questions (Final time)
At least I hope it's the final time. I know that I have posted this question before, but due to reinstalling the OS, I have a clean slate at this point. Now, I've done quite a bit of goggling and utubing and I want to be sure that I'm not going to crash the system when I add two drives to the fstab. Here is my current drive structure: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 457.9G 0 part / ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 7.9G 0 part [SWAP] sdb 8:16 0 1.8T 0 disk ├─sdb1 8:17 0 1.8T 0 part ├─sdb2 8:18 0 1K 0 part └─sdb5 8:21 0 7.9G 0 part sdc 8:32 0 465.8G 0 disk └─sdc1 8:33 0 465.8G 0 part sr0 11:0 1 1024M 0 rom sdc is a new SSD and I formatted it with only one partition. sdb still has a previous OS that I intend removing. Here are the the results of blkid: /dev/sda1: UUID="71f1ed49-9178-4bbc-b872-510f7982e245" TYPE="ext4" PARTUUID="1435f170-01" /dev/sda5: UUID="4b041dec-d00f-4acf-a731-f6a34d885105" TYPE="swap" PARTUUID="1435f170-05" /dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" PARTUUID="eb2be395-01" /dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" PARTUUID="0bc7db76-01" /dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" PARTUUID="0bc7db76-05" Here is the curerent fstab (missing exteraneous comment statements): # # / was on /dev/sda1 during installation UUID=71f1ed49-9178-4bbc-b872-510f7982e245 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=4b041dec-d00f-4acf-a731-f6a34d885105 none swap sw 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 Finally, here is what I am proposing adding to the fstab: UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 rw,users,defaults 0 0 UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 rw,users,defaults 0 0 Note: I have added /sdb1 and /sdc1. The only questions at this point are: 1. Will these changes crash the system,and 2. Will I be able to read adn write to the added drives? Thanks in advance. -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
