On Thu, Feb 08, 2007, Warren Turkal wrote:
> Why was the functionality removed from the kernel? Or alternatively, why does
> it need to be in the kernel if the info if available without kernel support?
It's best to use the functionality in the kernel instead of reinventing
the wheel in each pro
On Thursday 08 February 2007 01:22, you wrote:
> The preferred path for fixing for now still seems to be fixing the
> kernel. This bug has a release critical severity, so theoritically we
> should address it before etch.
Why was the functionality removed from the kernel? Or alternatively, why
On Wed, Feb 07, 2007, Warren Turkal wrote:
> 22.7.3 does not work. Is there any chance of copying the required logic from
> fdisk to lilo in time for Etch?
The preferred path for fixing for now still seems to be fixing the
kernel. This bug has a release critical severity, so theoritically we
On Wednesday 07 February 2007 15:05, you wrote:
> On Wed, Feb 07, 2007, Warren Turkal wrote:
> > I am glad you see what the issue is.
>
> With another person having the same problem, it was diagnosed as being
> probably a regression of the kernel. I don't have any fix or
> workaround for you un
On Wed, Feb 07, 2007, Warren Turkal wrote:
> I am glad you see what the issue is.
With another person having the same problem, it was diagnosed as being
probably a regression of the kernel. I don't have any fix or
workaround for you unfortunately.
> Is is possible that the 22.7.3 versio
On Wednesday 07 February 2007 11:43, you wrote:
> Ok, so fdisk is more clever than lilo and will compute heads and
> sectors either by using the HDIO_GETGEO ioctl() or the information from
> the partition table.
>
> I suppose that if the kernel issue can not be solved, we may still
> implement
On Wednesday 07 February 2007 11:27, Loïc Minier wrote:
> Oh interesting, could you attach a strace of this fdisk -l run?
The output of 'strace -o ~wt/fdisk.strace fdisk -l c0d0' is attached.
wt
--
Warren Turkal, Research Associate III/Systems Administrator
Colorado State University, Dept. of A
On Wed, Feb 07, 2007, Warren Turkal wrote:
> The output of 'strace -o ~wt/fdisk.strace fdisk -l c0d0' is attached.
Ok, so fdisk is more clever than lilo and will compute heads and
sectors either by using the HDIO_GETGEO ioctl() or the information from
the partition table.
I suppose that if th
On Wed, Feb 07, 2007, Warren Turkal wrote:
> /dev/cciss#fdisk -l c0d0
>
> Disk c0d0: 500.0 GB, 500074307584 bytes
> 255 heads, 63 sectors/track, 60797 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> c0d0p1
On Wednesday 07 February 2007 02:30, you wrote:
> Do you use udev or a static /dev?
udev
> Is there a device on which you can "fdisk -l" to get the partitions of
> your RAID array?
/dev/cciss#ls
c0d0 c0d0p1
/dev/cciss#fdisk -l c0d0
Disk c0d0: 500.0 GB, 500074307584 bytes
255 heads, 63 sectors/
Hi,
On Tue, Feb 06, 2007, Warren Turkal wrote:
> Here is the lilo strace output you asked for. I didn't see anything that the
> public shouldn't know in the output, so I have just attached it whole.
Do you use udev or a static /dev?
Is there a device on which you can "fdisk -l" to get
Hi,
Here is the lilo strace output you asked for. I didn't see anything that the
public shouldn't know in the output, so I have just attached it whole.
wt
--
Warren Turkal, Research Associate III/Systems Administrator
Colorado State University, Dept. of Atmospheric Science
15558 execve("/sbin/l
12 matches
Mail list logo
