On Wed, 25 Apr 2007 11:20:17 +0100
Wackojacko <[EMAIL PROTECTED]> wrote:
> Joe Hart wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > John L Fjellstad wrote:
> >> Joe Hart <[EMAIL PROTECTED]> writes:
> >>
> >>> Now that is a good reason. AFAIK, as of the newer kernels (forget
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
P Kapat wrote:
> Might be a little OT, but here is the question: Suppose I plugin an
> USB drive (small pendrives, or may be a big backup external disk), KDE
> pops up a box to choose the action to mount/cancel the new drive. What
> if I don't want to
On Wed, 2007-04-25 at 18:42 -0400, P Kapat wrote:
> Might be a little OT, but here is the question: Suppose I plugin an
> USB drive (small pendrives, or may be a big backup external disk), KDE
> pops up a box to choose the action to mount/cancel the new drive. What
> if I don't want to mount it thi
On Wed, Apr 25, 2007 at 06:42:56PM -0400, P Kapat wrote:
> USB drive (small pendrives, or may be a big backup external disk), KDE
> pops up a box to choose the action to mount/cancel the new drive. What
> if I don't want to mount it this way (why? i'll explain later **). I
> want to go back to CLI
Might be a little OT, but here is the question: Suppose I plugin an
USB drive (small pendrives, or may be a big backup external disk), KDE
pops up a box to choose the action to mount/cancel the new drive. What
if I don't want to mount it this way (why? i'll explain later **). I
want to go back to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Folkert wrote:
> On Wed, 2007-04-25 at 19:13 +0200, Joe Hart wrote:
>> Greg Folkert wrote:
>> [snip]
>>> How about posting it here?
>>>
>>> -
>>>
>>> # /etc/fstab: static file system information.
>>> #
>
On Wed, 2007-04-25 at 19:13 +0200, Joe Hart wrote:
> Greg Folkert wrote:
> [snip]
> > How about posting it here?
> >
> > -
> >
> > # /etc/fstab: static file system information.
> > #
> > #
> > proc /proc proc defaults 0 0
> >
> > # /dev/hda3
> > U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Folkert wrote:
[snip]
> How about posting it here?
>
> -
>
> # /etc/fstab: static file system information.
> #
> #
> proc /proc proc defaults 0 0
>
> # /dev/hda3
> UUID=456600fd-b794-4931-8703-bd
On Wed, 2007-04-25 at 07:59 -0400, Douglas Allan Tutty wrote:
> On Wed, Apr 25, 2007 at 12:02:00PM +0200, Joe Hart wrote:
> > John L Fjellstad wrote:
> > > Joe Hart <[EMAIL PROTECTED]> writes:
> > >
> > > Well, my Kubuntu system runs 2.6.20 and havs everything as sdX (when it
> > > was hdX before)
Wackojacko wrote:
Joe Hart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John L Fjellstad wrote:
Joe Hart <[EMAIL PROTECTED]> writes:
Now that is a good reason. AFAIK, as of the newer kernels (forget
which release) all drives are now sdX, so this issue becomes moot. I
can see why UU
On Wed, Apr 25, 2007 at 12:02:00PM +0200, Joe Hart wrote:
> John L Fjellstad wrote:
> > Joe Hart <[EMAIL PROTECTED]> writes:
> >
> > Well, my Kubuntu system runs 2.6.20 and havs everything as sdX (when it
> > was hdX before), and my Debian system runs 2.6.18 and still has hdX,
> > some somewhere i
Joe Hart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John L Fjellstad wrote:
Joe Hart <[EMAIL PROTECTED]> writes:
Now that is a good reason. AFAIK, as of the newer kernels (forget
which release) all drives are now sdX, so this issue becomes moot. I
can see why UUID is a good idea,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John L Fjellstad wrote:
> Joe Hart <[EMAIL PROTECTED]> writes:
>
>> Now that is a good reason. AFAIK, as of the newer kernels (forget
>> which release) all drives are now sdX, so this issue becomes moot. I
>> can see why UUID is a good idea, but a L
Joe Hart <[EMAIL PROTECTED]> writes:
> Now that is a good reason. AFAIK, as of the newer kernels (forget
> which release) all drives are now sdX, so this issue becomes moot. I
> can see why UUID is a good idea, but a LABEL is much easier to read.
Well, my Kubuntu system runs 2.6.20 and havs eve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John L Fjellstad wrote:
> Joe Hart <[EMAIL PROTECTED]> writes:
>
>> I can understand the usage of UUID on removable drives, but it seems the
>> new way of dealing with *all* disks is UUID. Why this needs to be so
>> for normal hard drives remains a m
Joe Hart <[EMAIL PROTECTED]> writes:
> I can understand the usage of UUID on removable drives, but it seems the
> new way of dealing with *all* disks is UUID. Why this needs to be so
> for normal hard drives remains a mystery to me.
Name of the disks are influx in the kernel right now. For inst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Apr 24, 2007 at 06:28:24PM +0200, Joe Hart wrote:
> -BEGIN PGP SIGNED MESSAGE-
> I can understand the usage of UUID on removable drives, but it seems the
> new way of dealing with *all* disks is UUID. Why this needs to be so
> for norm
Joe Hart wrote the following on 24.04.2007 18:28:
> I can understand the usage of UUID on removable drives, but it seems the
> new way of dealing with *all* disks is UUID. Why this needs to be so
> for normal hard drives remains a mystery to me.
First
I had used the LABEL in fstab even before
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob McGowan wrote:
> Michael Pobega wrote:
[snip]
>>
>> I think UUID is used because it is better to use UUID to recognize the
>> drives than /dev. For example, if you're trying to have your USB drive
>> automount to /mnt/usb, you'd use something like
Michael Pobega wrote:
On Tue, Apr 24, 2007 at 04:03:13PM +0200, Andrea S. Gozzi wrote:
I noticed that ubuntu 7.04 switched to the UUID method for
drives/partitions identification in fstab.
I heard rumors that debian will soon do the same (or already does).
Even with google I couldn't find any *
On Tue, Apr 24, 2007 at 04:03:13PM +0200, Andrea S. Gozzi wrote:
> I noticed that ubuntu 7.04 switched to the UUID method for
> drives/partitions identification in fstab.
> I heard rumors that debian will soon do the same (or already does).
>
> Even with google I couldn't find any *impartial* comp
21 matches
Mail list logo
