The system I'm using is a Dell server, originally purchased with Red Hat
Linux 7.1 (may have been 7.0, I don't recall for sure) installed at the
factory. I did not presume that they would have loaded any Windows
software on a new system with new disks purchased this way.
Is there a way to
Package: udev
Version: 0.091-2
Severity: normal
Subject: udev: vol_id returns incorrect information for my boot device
Package: udev
Version: 0.091-2
Severity: normal
I've been trying to get the 'root=LABEL=label_name' functionality to
work for my system, since it's SCSI based and the presence
I've found that the problem appears to be related to vol_id failing to
find proper information for my root device, /dev/sda1. I've run the
commands 'e2label', '/lib/udev/vol_id', 'mount' and 'fdisk' with the
following results:
Never use any of the all broken mkfs* tools without writing zeros
Wonderful ;(
There's nothing in any of the installation documentation that I can
remember that warns me about any of this. I suppose this could be
considered a documentation bug?
As mentioned in my response to Kay Sievers, so far as I know this system
had never had any other operating
On May 12, Bob McGowan [EMAIL PROTECTED] wrote:
There's nothing in any of the installation documentation that I can
remember that warns me about any of this. I suppose this could be
considered a documentation bug?
I agree with Kay that this should be considered a bug in the program
used to
On May 12, md wrote:
I suggest you discuss this with the e2fsprogs maintainer, Theodore Ts'o
[EMAIL PROTECTED].
Or even better ask about this on debian-boot, it could be argued that
it's up to whatever d-i uses to partition the disk to deal with it.
--
ciao,
Marco
signature.asc
Description:
6 matches
Mail list logo
