search for: wd0a

Good morning everybody, I get a: Error: Adding extent to vbd failed: device (vbd (uname file:/xen/slackware-linux-10/linu.img) (dev hda1) (mode w)), error 8 What is "error 8"? Where are those error-codes listed? My linux.conf: kernel="/xen/slackware-linux-10/vmlinuz-install" # <- the one from Xen memory=64 name="Linux" # <- is it right that this cannot have

...le ? we have one binary that can be booted via floppy, HDD, CD (El Torito or direct), under DOS, as Multiboot OS Kernel (*ahem*, but it reverts to mostly-16-bit mode then), and since DOS was already there, under SYSLINUX (and the others). You boot a kernel by telling it the path, for example boot wd0a:/bsd or boot tftp:/bsd.rd and, when booted from DOS or SYSLINUX, you can do boot c:/mirbsd/bsd (and, in general, access paths the same as SYSLINUX does). (When booted via Multiboot, it can also access the ?modules? passed from e.g. GNU GRUB2, as a virtual in-memory filesystem.) Another benefit f...

...at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask c860 netmask cc60 ttymask dce2 pctr: user-level cycle counter enabled Kernelized RAIDframe activated dkcsum: wd0 matched BIOS disk 80 dkcsum: wd1 matched BIOS disk 81 dkcsum: wd2 matched BIOS disk 82 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 raid0: Component /dev/wd1a being configured at row: 0 col: 0 Row: 0 Column: 0 Num Rows: 1 Num Columns: 2 Version: 2 Serial Number: 12345 Mod Counter: 207 Clean: Yes Status: 0 raid0: Component /dev/wd2a being configured at row: 0 col...