On Wed, 17 Nov 1999, Guest section DW wrote:
> > 3. Running lilo on some (large) disks results in
> >
> > ll_rw_block: device 08:00: only 1024-char blocks implemented (4096)
> >
> > Workaround: use "linear" option in /etc/lilo.conf.
>
> And this is not involving the loop device?
> In normal use of any program, lilo or not, on any disk, large or not,
> this should not occur.
This is not involving loop device at all. If you are curious, here is my
lilo.conf and fdisk -l output.
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
linear
timeout=50
default=2328
append="mem=64M console=ttyS1,9600 console=tty0"
image=/boot/vmlinuz-2.3.28
label=2328
read-only
root=/dev/sda3
image=/boot/vmlinuz-2.2.12-20smp
label=linux
initrd=/boot/initrd-2.2.12-20smp.img
read-only
root=/dev/sda3
image=/boot/vmlinuz-2.2.12-20
label=linux-up
initrd=/boot/initrd-2.2.12-20.img
read-only
root=/dev/sda3
other=/dev/sda1
label=diag
table=/dev/sda
other=/dev/sda4
label=uw213
table=/dev/sda
# fdisk -l /dev/sda
Disk /dev/sda: 255 heads, 63 sectors, 522 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 5 40131 12 Compaq diagnostics
/dev/sda2 6 18 104422+ 82 Linux swap
/dev/sda3 19 337 2562367+ 83 Linux
/dev/sda4 * 338 522 1486012+ 63 GNU HURD or SysV
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/