Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #205840 > unrolled thread

User rw Permissions on New Hard Drive

Back to article view | Back to linux.debian.user

Contents

  User rw Permissions on New Hard Drive "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-02-28 21:50 +0100
    Re: User rw Permissions on New Hard Drive Dekks Herton <dekkzz78@gmail.com> - 2019-03-01 02:00 +0100
    Re: User rw Permissions on New Hard Drive David Wright <deblis@lionunicorn.co.uk> - 2019-03-01 03:30 +0100
      Re: User rw Permissions on New Hard Drive Felix Miata <mrmazda@earthlink.net> - 2019-03-01 04:50 +0100
        Re: User rw Permissions on New Hard Drive Cindy-Sue Causey <butterflybytes@gmail.com> - 2019-03-01 07:40 +0100
          Re: string "defaults" in fstab options columns (was: User rw  Permissions on New Hard Drive) Felix Miata <mrmazda@earthlink.net> - 2019-03-01 09:00 +0100
            Re: string "defaults" in fstab options columns (was: User rw  Permissions on New Hard Drive) David Wright <deblis@lionunicorn.co.uk> - 2019-03-01 18:00 +0100
              Re: string "defaults" in fstab options columns Felix Miata <mrmazda@earthlink.net> - 2019-03-01 19:30 +0100
          Re: User rw Permissions on New Hard Drive David Wright <deblis@lionunicorn.co.uk> - 2019-03-01 18:00 +0100
            Re: User rw Permissions on New Hard Drive Greg Wooledge <wooledg@eeg.ccf.org> - 2019-03-01 18:10 +0100
              Re: User rw Permissions on New Hard Drive David Wright <deblis@lionunicorn.co.uk> - 2019-03-01 18:40 +0100
      Re: User rw Permissions on New Hard Drive Dekks Herton <dekkzz78@gmail.com> - 2019-03-01 08:40 +0100
        Re: User rw Permissions on New Hard Drive Michael Stone <mstone@debian.org> - 2019-03-01 15:40 +0100
          Re: User rw Permissions on New Hard Drive Stefan Monnier <monnier@iro.umontreal.ca> - 2019-03-01 18:50 +0100
            Re: User rw Permissions on New Hard Drive Reco <recoverym4n@enotuniq.net> - 2019-03-01 19:10 +0100
        Re: User rw Permissions on New Hard Drive David Wright <deblis@lionunicorn.co.uk> - 2019-03-01 18:20 +0100
      Re: User rw Permissions on New Hard Drive "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-03-05 15:20 +0100
        Re: User rw Permissions on New Hard Drive Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-03-05 20:20 +0100
        Re: User rw Permissions on New Hard Drive "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-03-06 23:50 +0100
    Re: User rw Permissions on New Hard Drive Cousin Stanley <cousinstanley@gmail.com> - 2019-03-07 15:40 +0100
      Re: User rw Permissions on New Hard Drive Michael Stone <mstone@debian.org> - 2019-03-07 16:10 +0100
        Re: User rw Permissions on New Hard Drive Cousin Stanley <cousinstanley@gmail.com> - 2019-03-07 18:20 +0100
          Re: User rw Permissions on New Hard Drive Michael Stone <mstone@debian.org> - 2019-03-07 19:10 +0100
          Re: User rw Permissions on New Hard Drive David Wright <deblis@lionunicorn.co.uk> - 2019-03-07 20:30 +0100
            Re: User rw Permissions on New Hard Drive Cousin Stanley <cousinstanley@gmail.com> - 2019-03-07 22:10 +0100
              Re: User rw Permissions on New Hard Drive Michael Stone <mstone@debian.org> - 2019-03-07 22:30 +0100
                Re: User rw Permissions on New Hard Drive Cousin Stanley <cousinstanley@gmail.com> - 2019-03-08 01:30 +0100
              Re: User rw Permissions on New Hard Drive David Wright <deblis@lionunicorn.co.uk> - 2019-03-08 03:20 +0100
                Re: User rw Permissions on New Hard Drive Cousin Stanley <cousinstanley@gmail.com> - 2019-03-08 07:10 +0100
            Re: User rw Permissions on New Hard Drive Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-03-07 23:20 +0100
              Re: User rw Permissions on New Hard Drive David Wright <deblis@lionunicorn.co.uk> - 2019-03-08 04:20 +0100
                Re: User rw Permissions on New Hard Drive Greg Wooledge <wooledg@eeg.ccf.org> - 2019-03-08 14:30 +0100
                  Re: User rw Permissions on New Hard Drive David Wright <deblis@lionunicorn.co.uk> - 2019-03-09 05:30 +0100
                Re: User rw Permissions on New Hard Drive Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-03-09 20:40 +0100
                  Re: User rw Permissions on New Hard Drive David Wright <deblis@lionunicorn.co.uk> - 2019-03-11 19:50 +0100
                    Re: User rw Permissions on New Hard Drive Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-03-16 10:50 +0100
                      Re: User rw Permissions on New Hard Drive David Wright <deblis@lionunicorn.co.uk> - 2019-03-17 16:30 +0100
      Re: User rw Permissions on New Hard Drive Felix Miata <mrmazda@earthlink.net> - 2019-03-07 18:20 +0100

Page 1 of 2  [1] 2  Next page →

#205840 — User rw Permissions on New Hard Drive

I am running Stretch and after much trial and tribulation, and at times 
abject horror, I have succeeded in installing a new SSD.

My drive structure is:

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

and my fstab is:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type> <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=ce25f0e1-610d-4030-ab47-129cd47d974e /               ext4 
errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=a8f6dc7e-13f1-4495-b68a-27886d386db0 none            swap 
sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0 0

UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 errors=remount-ro 
0       1

UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 errors=remount-ro 
0       1


Finally, my user group structure is (comp is the  user):

comp cdrom floppy sudo audio dip video plugdev users netdev lpadmin scanner

The problem is how do I set rw permissions on the new SSD?

Googling only leaves me in a high state of mental entropy.

Solutions will be welcome.

Thanks in advance.

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [next] | [standalone]

#205845

[Multipart message — attachments visible in raw view] — view raw

"Stephen P. Molnar" <s.molnar@sbcglobal.net> writes:

> I am running Stretch and after much trial and tribulation, and at times abject horror, I have succeeded in installing a new SSD.
>
> My drive structure is:
>
> 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
>
> and my fstab is:
>
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
> # that works even if disks are added and removed. See fstab(5).
> #
> # <file system> <mount point>   <type> <options>       <dump>  <pass>
> # / was on /dev/sda1 during installation
> UUID=ce25f0e1-610d-4030-ab47-129cd47d974e /               ext4 errors=remount-ro 0       1
> # swap was on /dev/sda5 during installation
> UUID=a8f6dc7e-13f1-4495-b68a-27886d386db0 none            swap sw              0       0
> /dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0 0
>
> UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 errors=remount-ro 0       1
>
> UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 errors=remount-ro 0       1
>
>
> Finally, my user group structure is (comp is the  user):
>
> comp cdrom floppy sudo audio dip video plugdev users netdev lpadmin scanner
>
> The problem is how do I set rw permissions on the new SSD?
>
> Googling only leaves me in a high state of mental entropy.
>
> Solutions will be welcome.
>
> Thanks in advance.

sudo chown user_name mount_point?

-- 
Regards.........
 
PGP Fingerprint: 3DF8 311C 4740 B5BC 3867  72DF 1050 452F 9BCE BA00

[toc] | [prev] | [next] | [standalone]

#205846

On Thu 28 Feb 2019 at 15:45:47 (-0500), Stephen P. Molnar wrote:
> I am running Stretch and after much trial and tribulation, and at
> times abject horror, I have succeeded in installing a new SSD.
> 
> My drive structure is:
> 
> 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
> 
> and my fstab is:
> 
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
> # that works even if disks are added and removed. See fstab(5).
> #
> # <file system> <mount point>   <type> <options>       <dump>  <pass>
> # / was on /dev/sda1 during installation
> UUID=ce25f0e1-610d-4030-ab47-129cd47d974e /               ext4
> errors=remount-ro 0       1
> # swap was on /dev/sda5 during installation
> UUID=a8f6dc7e-13f1-4495-b68a-27886d386db0 none            swap sw
> 0       0
> /dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0 0
> 
> UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 errors=remount-ro
> 0       1
> 
> UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 errors=remount-ro
> 0       1

Well, you did ask for a sanity check, but those mount points are still
completely insane. And you still have 1 for the last field of your
non-root filesystems when it should be 2.

I always add an explicit rw or ro under options, along with defaults.
With systemd, I add nofail to any filesystems that aren't vital for
the system to run, which means the system will still boot fully
without them.

> Finally, my user group structure is (comp is the  user):
> 
> comp cdrom floppy sudo audio dip video plugdev users netdev lpadmin scanner
> 
> The problem is how do I set rw permissions on the new SSD?

As posted by Dekks, but make sure the filesystem is already mounted:
it's the filesystem that needs changing, not the underlying mount
point.

I think your 2TB disk hasn't been altered. You could just use its
ownership/permissions as a model if you were happy with them.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#205847

David Wright composed on 2019-02-28 20:26 (UTC-0600):

> I always add an explicit rw or ro under options, along with defaults.

English can be tricky. Please clarify. AIUI, the string "defaults" is a placeholder, unnecessary if
any other option is specified. Man mount doesn't make it clear to me. I can't recall ever including
it along with any other option. I've always assumed all defaults not explicitly overridden will be
used.
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#205849

On 2/28/19, Felix Miata <mrmazda@earthlink.net> wrote:
> David Wright composed on 2019-02-28 20:26 (UTC-0600):
>
>> I always add an explicit rw or ro under options, along with defaults.
>
> English can be tricky. Please clarify. AIUI, the string "defaults" is a
> placeholder, unnecessary if
> any other option is specified. Man mount doesn't make it clear to me. I
> can't recall ever including
> it along with any other option. I've always assumed all defaults not
> explicitly overridden will be
> used.


That's what I'd been thinking, too. Because of your question, I just
tried a search for...

"defaults,rw" /etc/fstab

Some things pulled up from varying resources out there. Without
actually visiting any of the results, sometimes they just said the
above. Other times, they would have "defaults,rw" with a few of the
various remaining options tacked on the end of that, as well.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

[toc] | [prev] | [next] | [standalone]

#205852 — Re: string "defaults" in fstab options columns (was: User rw Permissions on New Hard Drive)

Cindy-Sue Causey composed on 2019-03-01 01:30 (UTC-0500):

> Felix Miata wrote:

>> David Wright composed on 2019-02-28 20:26 (UTC-0600):

>>> I always add an explicit rw or ro under options, along with defaults.

>> English can be tricky. Please clarify. AIUI, the string "defaults" is a
>> placeholder, unnecessary if
>> any other option is specified. Man mount doesn't make it clear to me. I
>> can't recall ever including
>> it along with any other option. I've always assumed all defaults not
>> explicitly overridden will be
>> used.

> That's what I'd been thinking, too. Because of your question, I just
> tried a search for...

> "defaults,rw" /etc/fstab

> Some things pulled up from varying resources out there. Without
> actually visiting any of the results, sometimes they just said the
> above. Other times, they would have "defaults,rw" with a few of the
> various remaining options tacked on the end of that, as well.

To be clear, "including it" above meant an fstab line I created from scratch or any options entry I
edited, not any created by any Linux installer. I just checked original fstabs created by

Etch (in 2006)
Fedora 7 (in 2006)
openSUSE 10.3 (in 2007)
Squeeze (in 2011)
openSUSE 42.1 (in 2015)
Bionic (in 2018)
Buster (in 2018)

on PCs here. Not one contains the string "defaults" adjacent to a comma. I have seen defaults
adjacent to a comma in fstab option lines in web searches, mailing lists and forums, but don't know
why it ever happens.
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#205887 — Re: string "defaults" in fstab options columns (was: User rw Permissions on New Hard Drive)

On Fri 01 Mar 2019 at 02:51:33 (-0500), Felix Miata wrote:
> Cindy-Sue Causey composed on 2019-03-01 01:30 (UTC-0500):
> > Felix Miata wrote:
> >> David Wright composed on 2019-02-28 20:26 (UTC-0600):
> >>> I always add an explicit rw or ro under options, along with defaults.
> 
> >> English can be tricky. Please clarify. AIUI, the string "defaults" is a
> >> placeholder, unnecessary if
> >> any other option is specified. Man mount doesn't make it clear to me. I
> >> can't recall ever including
> >> it along with any other option. I've always assumed all defaults not
> >> explicitly overridden will be
> >> used.
> 
> > That's what I'd been thinking, too. Because of your question, I just
> > tried a search for...
> 
> > "defaults,rw" /etc/fstab
> 
> > Some things pulled up from varying resources out there. Without
> > actually visiting any of the results, sometimes they just said the
> > above. Other times, they would have "defaults,rw" with a few of the
> > various remaining options tacked on the end of that, as well.
> 
> To be clear, "including it" above meant an fstab line I created from scratch or any options entry I
> edited, not any created by any Linux installer. I just checked original fstabs created by
> 
> Etch (in 2006)
> Fedora 7 (in 2006)
> openSUSE 10.3 (in 2007)
> Squeeze (in 2011)
> openSUSE 42.1 (in 2015)
> Bionic (in 2018)
> Buster (in 2018)
> 
> on PCs here. Not one contains the string "defaults" adjacent to a comma. I have seen defaults
> adjacent to a comma in fstab option lines in web searches, mailing lists and forums, but don't know
> why it ever happens.

I don't see harm in making explicit what's implicit. My use may have
arisen from habit back in the early days, way before etch. But I'd
better remove defaults forthwith in any posts, as they're obviously
causing such concern (and you so much work).

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#205902 — Re: string "defaults" in fstab options columns

David Wright composed on 2019-03-01 10:56 (UTC-0600):

> (and you so much work).

Was wondering for years. I think I'm over it now. :)
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#205888

On Fri 01 Mar 2019 at 01:30:47 (-0500), Cindy-Sue Causey wrote:
> On 2/28/19, Felix Miata <mrmazda@earthlink.net> wrote:
> > David Wright composed on 2019-02-28 20:26 (UTC-0600):
> >
> >> I always add an explicit rw or ro under options, along with defaults.
> >
> > English can be tricky. Please clarify. AIUI, the string "defaults" is a
> > placeholder, unnecessary if
> > any other option is specified. Man mount doesn't make it clear to me. I
> > can't recall ever including
> > it along with any other option. I've always assumed all defaults not
> > explicitly overridden will be
> > used.
> 
> That's what I'd been thinking, too. Because of your question, I just
> tried a search for...
> 
> "defaults,rw" /etc/fstab

You've really limited what can be found with that string.
For example, you won't find rw,defaults. But the shell
makes a more productive search string look like toothpick-hell:

$ grep '\(rw\)\|\(defaults\)' /etc/fstab

will match lines with either word.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#205889

On Fri, Mar 01, 2019 at 10:52:00AM -0600, David Wright wrote:
> On Fri 01 Mar 2019 at 01:30:47 (-0500), Cindy-Sue Causey wrote:
> > That's what I'd been thinking, too. Because of your question, I just
> > tried a search for...
> > 
> > "defaults,rw" /etc/fstab
> 
> You've really limited what can be found with that string.
> For example, you won't find rw,defaults. But the shell
> makes a more productive search string look like toothpick-hell:
> 
> $ grep '\(rw\)\|\(defaults\)' /etc/fstab
> 
> will match lines with either word.

*shudder*  You don't need ANY of those parentheses, let alone escaped
parentheses.  And you're relying on a GNUism to make the | work instead
of just calling grep -E or egrep like you're supposed to.

grep -E 'rw|defaults' /etc/fstab

If you wanted to match lines that have BOTH strings, then try
<https://mywiki.wooledge.org/BashFAQ/079> instead.

[toc] | [prev] | [next] | [standalone]

#205897

On Fri 01 Mar 2019 at 12:00:06 (-0500), Greg Wooledge wrote:
> On Fri, Mar 01, 2019 at 10:52:00AM -0600, David Wright wrote:
> > On Fri 01 Mar 2019 at 01:30:47 (-0500), Cindy-Sue Causey wrote:
> > > That's what I'd been thinking, too. Because of your question, I just
> > > tried a search for...
> > > 
> > > "defaults,rw" /etc/fstab
> > 
> > You've really limited what can be found with that string.
> > For example, you won't find rw,defaults. But the shell
> > makes a more productive search string look like toothpick-hell:
> > 
> > $ grep '\(rw\)\|\(defaults\)' /etc/fstab
> > 
> > will match lines with either word.
> 
> *shudder*  You don't need ANY of those parentheses, let alone escaped
> parentheses.  And you're relying on a GNUism to make the | work instead
> of just calling grep -E or egrep like you're supposed to.
> 
> grep -E 'rw|defaults' /etc/fstab

Sorry. I think I've been writing too much sed recently, making my
audio and video configurations switch between monitor and HDMI.

> If you wanted to match lines that have BOTH strings, then try
> <https://mywiki.wooledge.org/BashFAQ/079> instead.

Your FAQs are well worth reading, as always. So much reading,
so little time. (Opposite of another well known poster.)

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#205851

[Multipart message — attachments visible in raw view] — view raw

David Wright <deblis@lionunicorn.co.uk> writes:

> On Thu 28 Feb 2019 at 15:45:47 (-0500), Stephen P. Molnar wrote:
>> I am running Stretch and after much trial and tribulation, and at
>> times abject horror, I have succeeded in installing a new SSD.
>> 
>> My drive structure is:
>> 
>> 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
>> 
>> and my fstab is:
>> 
>> # /etc/fstab: static file system information.
>> #
>> # Use 'blkid' to print the universally unique identifier for a
>> # device; this may be used with UUID= as a more robust way to name devices
>> # that works even if disks are added and removed. See fstab(5).
>> #
>> # <file system> <mount point>   <type> <options>       <dump>  <pass>
>> # / was on /dev/sda1 during installation
>> UUID=ce25f0e1-610d-4030-ab47-129cd47d974e /               ext4
>> errors=remount-ro 0       1
>> # swap was on /dev/sda5 during installation
>> UUID=a8f6dc7e-13f1-4495-b68a-27886d386db0 none            swap sw
>> 0       0
>> /dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0 0
>> 
>> UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 errors=remount-ro
>> 0       1
>> 
>> UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 errors=remount-ro
>> 0       1
>
> Well, you did ask for a sanity check, but those mount points are still
> completely insane. And you still have 1 for the last field of your
> non-root filesystems when it should be 2.

Agree with non-root being 2 but that fstab looks like how debian does
defaults, it likes errrors=remount-ro.

> I always add an explicit rw or ro under options, along with defaults.
> With systemd, I add nofail to any filesystems that aren't vital for
> the system to run, which means the system will still boot fully
> without them.

nofail is intended for removable drives that could be missing on boot,
such as Thinkpad ultrabay drives/CF or SD cards.

>> Finally, my user group structure is (comp is the  user):
>> 
>> comp cdrom floppy sudo audio dip video plugdev users netdev lpadmin scanner
>> 
>> The problem is how do I set rw permissions on the new SSD?
>
> As posted by Dekks, but make sure the filesystem is already mounted:
> it's the filesystem that needs changing, not the underlying mount
> point.
>
> I think your 2TB disk hasn't been altered. You could just use its
> ownership/permissions as a model if you were happy with them.
>
> Cheers,
> David.
>

-- 
Regards.........
 
PGP Fingerprint: 3DF8 311C 4740 B5BC 3867  72DF 1050 452F 9BCE BA00

[toc] | [prev] | [next] | [standalone]

#205881

On Fri, Mar 01, 2019 at 07:30:15AM +0000, Dekks Herton wrote:
>David Wright <deblis@lionunicorn.co.uk> writes:
>> I always add an explicit rw or ro under options, along with defaults.
>> With systemd, I add nofail to any filesystems that aren't vital for
>> the system to run, which means the system will still boot fully
>> without them.
>
>nofail is intended for removable drives that could be missing on boot,
>such as Thinkpad ultrabay drives/CF or SD cards.

It is also, as he said, useful if you don't want a failure of a 
non-essential disk to make the system drop to single user on boot. 

[toc] | [prev] | [next] | [standalone]

#205898

>>nofail is intended for removable drives that could be missing on boot,
>>such as Thinkpad ultrabay drives/CF or SD cards.
> It is also, as he said, useful if you don't want a failure of
> a non-essential disk to make the system drop to single user on boot. 

Yup.  `nofail` corresponds to the behavior that was standard
before systemd.

The only partitions where I don't use `nofail` are those where I forgot
to put it ;-)


        Stefan

[toc] | [prev] | [next] | [standalone]

#205900

	Hi.

On Fri, Mar 01, 2019 at 12:49:11PM -0500, Stefan Monnier wrote:
> >>nofail is intended for removable drives that could be missing on boot,
> >>such as Thinkpad ultrabay drives/CF or SD cards.
> > It is also, as he said, useful if you don't want a failure of
> > a non-essential disk to make the system drop to single user on boot. 
> 
> Yup.  `nofail` corresponds to the behavior that was standard
> before systemd.

... in Debian. That part of systemd was inherited from Red Hat's
interpretation of "proper OS booting".

Reco

[toc] | [prev] | [next] | [standalone]

#205891

On Fri 01 Mar 2019 at 07:30:15 (+0000), Dekks Herton wrote:
> David Wright <deblis@lionunicorn.co.uk> writes:
> > On Thu 28 Feb 2019 at 15:45:47 (-0500), Stephen P. Molnar wrote:

> >> # /etc/fstab: static file system information.
> >> #
> >> # Use 'blkid' to print the universally unique identifier for a
> >> # device; this may be used with UUID= as a more robust way to name devices
> >> # that works even if disks are added and removed. See fstab(5).
> >> #
> >> # <file system> <mount point>   <type> <options>       <dump>  <pass>
> >> # / was on /dev/sda1 during installation
> >> UUID=ce25f0e1-610d-4030-ab47-129cd47d974e /               ext4
> >> errors=remount-ro 0       1
> >> # swap was on /dev/sda5 during installation
> >> UUID=a8f6dc7e-13f1-4495-b68a-27886d386db0 none            swap sw
> >> 0       0
> >> /dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0 0
> >> 
> >> UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 errors=remount-ro
> >> 0       1
> >> 
> >> UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 errors=remount-ro
> >> 0       1
> >
> > Well, you did ask for a sanity check, but those mount points are still
> > completely insane. And you still have 1 for the last field of your
> > non-root filesystems when it should be 2.
> 
> Agree with non-root being 2 but that fstab looks like how debian does
> defaults, it likes errrors=remount-ro.

Or even errors=remount-ro. I do remember running sed's
s/defaults/errors=remount-ro,defaults/ many years ago when I
discovered its availability.

People here might object to seeing ro,errors=remount-ro in anyone's
fstab, but so what?

> > I always add an explicit rw or ro under options, along with defaults.
> > With systemd, I add nofail to any filesystems that aren't vital for
> > the system to run, which means the system will still boot fully
> > without them.
> 
> nofail is intended for removable drives that could be missing on boot,
> such as Thinkpad ultrabay drives/CF or SD cards.

Maybe. I use user,noauto throughout fstab for my removables, and then
mount them when I connect them. I was under the impression that nofail
was aimed more at mounts that are made via 'iffy' technologies, like
those across a network.

But my use is entirely aimed at avoiding tears and work. Thus all my
Windows/manufacturer partitions on this dual-boot machine are mounted
nofail. After all, I have no idea whether some Windows operation or
update is going to tweak something that causes a mount to fail the
next time I boot linux.

On machines that I boot using WoL, I don't want to have to go and
turn on the monitor just to find out why it stalled booting.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#206016

On 03/01/2019 01:56 PM, David Wright wrote:
> On Fri 01 Mar 2019 at 08:46:30 (-0500), Stephen P. Molnar wrote:
>> I am sure that you will castigate men for two things:
>>
>> 1.  Top posting
>> 2.  Not replying to debian-users
>>
>> However, I wanted to keep my reply private
>> in the hope of not starting a flame war.
>>
>> Please see my further comment below.
<cut>
<cut>

Thanks for your reply. i think that we are on the same page, now.

I would ask your indulgence for one more request.

Here is my durectiry stucture:

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 
/media/comp/900b5f0b-4f3d-4a64-8c91-29aee4c6fd07
├─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 
/media/comp/1f363165-2c59-4236-850d-36d1e807099e
sr0     11:0    1  1024M  0 rom

Here is what I have asteh installed fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type> <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=4dc278b7-1792-4e89-b67e-a517fce97d19 /               ext4 
errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=acfb9d26-69c6-4489-88fc-12f5c50bda97 none            swap 
sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0 0

Here is wwhat I'm proposing:

/dev/hda1 / ext4 defaults 0 1
/dev/hda5 none swap sw 0 0
/dev/hdb1 /hdb1 ext4 defaults 0 0
/dev/hdc1 /hdc1 ext4 defaults 0 0

There are two key questions:

     1.  Will the boot proceed to completion?
     2.  Will users have read/write permission?

Finally, if the answer(s), to either or both, is/are 'no' - what should 
the fstab entries be in order to allow users to Read/Write?

This is rather critical for my continuing good health.  If I crash the 
system and have to reinstall the OS my wife is going to be greatly 
displeased.  I would like to avoid this fate.

Thanks in advance.

Regards,

         Steve

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [prev] | [next] | [standalone]

#206020

Le 05/03/2019 à 15:17, Stephen P. Molnar a écrit :
> 
> 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 
> /media/comp/900b5f0b-4f3d-4a64-8c91-29aee4c6fd07
> ├─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 
> /media/comp/1f363165-2c59-4236-850d-36d1e807099e
> sr0     11:0    1  1024M  0 rom
(...)

> Here is wwhat I'm proposing:
> 
> /dev/hda1 / ext4 defaults 0 1
> /dev/hda5 none swap sw 0 0
> /dev/hdb1 /hdb1 ext4 defaults 0 0
> /dev/hdc1 /hdc1 ext4 defaults 0 0
> 
> There are two key questions:
> 
>      1.  Will the boot proceed to completion?

No. /dev/hd* do not exist.

>      2.  Will users have read/write permission?

No. At best, you will end up in emergency mode with a read-only root 
filesystem.

> Finally, if the answer(s), to either or both, is/are 'no' - what should 
> the fstab entries be in order to allow users to Read/Write?

Leave existing / and swap lines as they are.
Device names /dev/sd* are not persistent and may change at each boot.
Use UUID or LABEL instead of device names to identify the filesystem.
Do not name mount points after supposed device names. Choose names based 
on contents instead.

Finally, user permissions are not set in fstab. They are set in the 
filesystem itself, using chown/chmod if you are using standard Unix 
permissions or setfacl if you are going with ACLs.

[toc] | [prev] | [next] | [standalone]

#206044

I would beg the group's indulgence again, as I want to be sure I get 
this correctly.

I think this is what I want as the fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type> <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=4dc278b7-1792-4e89-b67e-a517fce97d19 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=acfb9d26-69c6-4489-88fc-12f5c50bda97 none swap sw 0 0

UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 
defaults,errors=remount-ro 0 1

UUID=1f363165-2c59-4236-850d-36d1e807099e /Apps ext4 
defaults,errors=remount-ro 0 1

/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

in addition I need to have:

/sbd1
/Apps
/dev/sdb1
/dev/Apps

   Comments and corrections will be much appreciated.

> Thanks in advance.
>
> Regards,
>
>         Steve
>

-- 
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

[toc] | [prev] | [next] | [standalone]

#206048

Stephen P. Molnar wrote:

> ....
> and my fstab is:
> 
> # /etc/fstab: static file system information.
> ....
 
  I've found that labeling my disk partitions
  and using  /dev/disk/by-label/xyzzy  lines
  in the  /etc/fstab  file seems to be much easier 
  for my own small brain to comprehend.

  An example from one of my local machines ....

# <file system>               <mount point>  <type>  <options>         <dump>  <pass>

/dev/disk/by-label/ssd1_root  /               ext4    errors=remount-ro   0       1

/dev/disk/by-label/ssd1_efi   /boot/efi       vfat    umask=0077          0       1

/dev/disk/by-label/ssd1_swap  none            swap    sw                  0       0

/dev/disk/by-label/ssd1_home  /home           ext4    defaults            0       2


  To label the disk partitions check the  man  pages
  for the following labeling options ....

   $ ls -1 /sbin | grep label
   dosfslabel
   e2label
   exfatlabel
   fatlabel
   ntfslabel
   swaplabel

  The  e2label  program is effective for  ext  partitions.


  To list the disk labels .... 

  $ ls -Ahl /dev/disk/by-label



-- 
Stanley C. Kitching
Human Being
Phoenix, Arizona

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web