On Sat 16 Mar 2019 at 10:49:19 (+0100), Pascal Hambourg wrote:
> Le 11/03/2019 à 19:46, David Wright a écrit :
> > On Sat 09 Mar 2019 at 20:31:36 (+0100), Pascal Hambourg wrote:
> > >
> > > I did not mean using UDF on opticals discs but on regular drives, just
> > > as any other general purpose
Le 11/03/2019 à 19:46, David Wright a écrit :
On Sat 09 Mar 2019 at 20:31:36 (+0100), Pascal Hambourg wrote:
I did not mean using UDF on opticals discs but on regular drives, just
as any other general purpose filesystem. I once considered using it
for file sharing between Windows and Linux
On Sat 09 Mar 2019 at 20:31:36 (+0100), Pascal Hambourg wrote:
> Le 08/03/2019 à 04:15, David Wright a écrit :
> > On Thu 07 Mar 2019 at 23:12:29 (+0100), Pascal Hambourg wrote:
> > > Le 07/03/2019 à 20:23, David Wright a écrit :
> > > >
> > > > A filesystem
> > > > that has a label, has that
Le 08/03/2019 à 04:15, David Wright a écrit :
On Thu 07 Mar 2019 at 23:12:29 (+0100), Pascal Hambourg wrote:
Le 07/03/2019 à 20:23, David Wright a écrit :
A filesystem
that has a label, has that label regardless of any OS.
Have you ever used UDF ?
Yes. As far as my experience goes,
Please don't oversnip. This subthread was about labels (aka LABELs).
On Fri 08 Mar 2019 at 08:20:40 (-0500), Greg Wooledge wrote:
> On Thu, Mar 07, 2019 at 09:15:51PM -0600, David Wright wrote:
> > On Thu 07 Mar 2019 at 23:12:29 (+0100), Pascal Hambourg wrote:
> > > Le 07/03/2019 à 20:23, David
On Thu, Mar 07, 2019 at 09:15:51PM -0600, David Wright wrote:
> Yes. As far as my experience goes, there's not a lot of difference.
> I've had no occasion to *write* DVDs on a computer system, so I can
> only speak of reading them.
For writing, fstab and mount are not involved in any way
David Wright wrote:
> I would not expect to find the characters
> /dev/disk/by-label/ anywhere in the partition.
>
> That string belongs to the linux system, not to the card.
>
> That's what I meant by "actually belongs to the filesystems".
OK, that's clear and I understand.
>> I'm not
On Thu 07 Mar 2019 at 23:12:29 (+0100), Pascal Hambourg wrote:
> Le 07/03/2019 à 20:23, David Wright a écrit :
> >
> > A filesystem
> > that has a label, has that label regardless of any OS.
>
> Have you ever used UDF ?
Yes. As far as my experience goes, there's not a lot of difference.
I've
On Thu 07 Mar 2019 at 13:49:42 (-0700), Cousin Stanley wrote:
> David Wright wrote:
>
> > I prefer to populate fstab with canonical information
> > that actually belongs to the filesystems that are to be mounted.
>
> I don't understand what you're saying here.
>
> Does a disk label not
Michael Stone wrote:
> On Thu, Mar 07, 2019 at 01:49:42PM -0700, Cousin Stanley wrote:
>>David Wright wrote:
>>> All that stuff in /dev/disk/ is just an ephemeral
>>> bunch of convenient symbolic links, presumably conjured
>>> up by udev or somesuch, if not the linux kernel
>>
>> But are they
Le 07/03/2019 à 20:23, David Wright a écrit :
A filesystem
that has a label, has that label regardless of any OS.
Have you ever used UDF ? It has a set of identifiers, and I observed
that Windows and blkid did not use the same identifier as the label.
On Thu, Mar 07, 2019 at 01:49:42PM -0700, Cousin Stanley wrote:
David Wright wrote:
All that stuff in /dev/disk/ is just an ephemeral
bunch of convenient symbolic links, presumably conjured
up by udev or somesuch, if not the linux kernel
But are they not accurate after boot
for particular
David Wright wrote:
> I prefer to populate fstab with canonical information
> that actually belongs to the filesystems that are to be mounted.
I don't understand what you're saying here.
Does a disk label not belong to a filesystem
that is to be mounted ?
> A filesystem that has a
On Thu 07 Mar 2019 at 09:59:43 (-0700), Cousin Stanley wrote:
> Michael Stone wrote:
> > On Thu, Mar 07, 2019 at 07:11:36AM -0700, Cousin Stanley wrote:
> >>Stephen P. Molnar wrote:
> >>>
> >>> and my fstab is:
> >>>
> >>> # /etc/fstab: static file system information.
> >>>
> >>
> >>
On Thu, Mar 07, 2019 at 09:59:43AM -0700, Cousin Stanley wrote:
Michael Stone wrote:
On Thu, Mar 07, 2019 at 07:11:36AM -0700, Cousin Stanley wrote:
Stephen P. Molnar wrote:
and my fstab is:
# /etc/fstab: static file system information.
I've found that labeling my disk
Michael Stone wrote:
> On Thu, Mar 07, 2019 at 07:11:36AM -0700, Cousin Stanley wrote:
>>Stephen P. Molnar wrote:
>>
>>>
>>> and my fstab is:
>>>
>>> # /etc/fstab: static file system information.
>>>
>>
>> I've found that labeling my disk partitions
>> and using
Cousin Stanley composed on 2019-03-07 07:11 (UTC-0700):
> 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
On Thu, Mar 07, 2019 at 07:11:36AM -0700, Cousin Stanley wrote:
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
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.
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
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
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
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
>>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
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...
>
On Fri 01 Mar 2019 at 07:30:15 (+), Dekks Herton wrote:
> David Wright 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;
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
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
On Fri 01 Mar 2019 at 01:30:47 (-0500), Cindy-Sue Causey wrote:
> On 2/28/19, 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
On Fri, Mar 01, 2019 at 07:30:15AM +, Dekks Herton wrote:
David Wright 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
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
>>
David Wright 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
On 2/28/19, 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
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.
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
"Stephen P. Molnar" 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:00 465.8G 0 disk
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:00 465.8G 0 disk
├─sda1 8:10 457.9G 0 part /
├─sda2
37 matches
Mail list logo
