Re: [Cooker] mkbootdisk errors
Hi, I didn't catch all mails concerning this topic, but I had the same errors. The problem was, that I used XFS for the root-FS, because the modules needed in intrd are too big to fit on the floppy. The moment I changed over '/' (a small one with 150 MB) to ext3 or ReiseFS it worked without problems! If you don't use XFS for root, at least it was worth a try! Best regards, Heinz [EMAIL PROTECTED] schrieb am 21.01.02: Still getting mkboodisk errors. Formatting /dev/fd0... done. Copying /boot/vmlinuz-2.4.17-5mdk... done. Creating initrd image... mke2fs 1.25 (20-Sep-2001) cp: writing `/tmp/mkbootdisk/initrd.img': No space left on device Error ! I get this whether using DrakConf or mkbootdisk from command line This may be a known issue but at least it tries to mkbootdisk while the previous stock cooker20011224 could even go anywhere except error... I do not have All the updates so maybe this is already addressed !? William Bouterse Talkeetna, Ak __ Eine Klasse für sich - der WEB.DE Club. High End Kommunikation MEHR. Mehr Speicher, mehr Leistung, mehr Vorteile - http://club.web.de
Re: [Cooker] mkbootdisk - no space on device
Guillaume Cottenceau wrote: svetljo [EMAIL PROTECTED] writes: and what if smbd install on XFS / raid and can not remember exactly which stripe_size and/or raid_dev and/or in which order he maked the raids the kernel from the CD doesn't have compiled in raid so no autodetect i'm really happy that you didn't abandoned XFS ( i was realy afraid of that) what in case smbd upgrade the lvm tools and kernel code the CD can not help in these cases there allways be need for a custem created boot disk/s We can't handle easily all situations, but I'm not willing to change profoundly some tools you can leave the old tools , and provide a modified version with different names of the tools when they only concern expert and very unusual situations. this sound a bit like Mandrake is only for home users not for advanced ones that couldn't be true i really like Mandrake or the person should have some more place and reinstall, upgrade the tools or create the special kernel and then use them to rescue the old system is that not crucial
Re: [Cooker] mkbootdisk - no space on device
i think this is a big misstake, lvm is definetly not advanced/expert feature why so ? it makes life simplier, the only clue i see , is that the current lvm can not initialaise the LV's without initrd we have to have one normal partition for the initrd and it makes the life pretty simple it's a dumb example , but what can i do if i use standart partitions and 1# i had for example too much MP3s and no more space on device A how can i get some more place , should i make new partitions, format them and copy the files over to device B explain a newbie scenario to handle that problem with current actual tools in the distro. instead of making different partitions, you make only one and make it LVM and on it make your instalation , i think currently both lilo and grub can handle it, or at least there are patches to boot from lvm in case you get a new hd simply ad it to the VG and grow your LV's in case you don't wont more win xx , you don't need to repartition or to format and try figure out mountpoints and copy some data to the new mount points you ad the existing partition to the VG and extend your LV's 2# i didn't know how big should i make partition C and now i use only 25% and so on reduce the LV and extend the one you need more place
Re: [Cooker] mkbootdisk - no space on device
/boot where i have my radtab, you can mount the separate /boot ? it's ext2 /dev/hde5 , no troubles mounting it and i'm not that shure but i think i can not create more then 2 or 3 raids ( i have 6, with LVM over them ) why ? mkraid complained smth about no such device i think a lot of the lvm stuff is missing and it's 0.9.1beta2 version ( i use 1.0.1rc2 ) what's missing ? the userland tools , it couldn't find pvscan, lvscan ... i had to use the XFS-cooker as rescue and i will try MDK 8.1 but i think that won't help much tell us we can fix stuff if we agree on the most. the fixable i think is to add all the lvm-tools and may be raid autodetect the not fixable lvm upgrade to 1.0 or 1.0.1rc2 , Haiz Mauelshagen talked about 1.0.1-rc3 next week it wont have raid compiled in the kernel and it wont have lvm-1.0 or later and in case it doesn't have xfs in the boot-kernel or as module ... one we have xfs in the boot kernel as a module (and jfs and ext3 and reiserfs and lvm etc) more point what about the people which can not boot from a cd for some reason how would they install or rescue with XFS can it be done with the floppy images ? network.img hd.img these floppies have kernel and modules for XFS, JFS, raid , lvm ? etc our rescue system can be launched at all places the install can be launched. it's just a similar program than the install program.
Re: [Cooker] mkbootdisk - no space on device
The problem is that it's not -accessible- to newbies currently. E.g easily usable. diskdrake works perfectly for a standart home PC, and it's easy to do what is the difference between working with standart partitions and LVM that we should add the partitions to VG -- thats all, everything else is the same [...] That is not the answer to my question.. probably i can not understand you correct ( my bad english) what do you mean by a newbie scenario Operations a newbie would do to take advantage of LVM. The aim was to demonstrate that LVM is not for newbies because using/modifying LVM requires expert skills with commandline stuff and so on. one doesn't need command line , he can use diskdrake for that purpose with diskdrake you can create extend reduce LV's you really don't need comand line if you don't plan to do smth that special as striped LV how can a newbie install on LVM or how can newbie work with LVM after the install diskdrake allready has some suport for lvm , and for an average home user PC it has everything needed average home user have a great fear when dealing with disks and partitions. well i'm saying the same and i'm sure that lvm make it simplier to deal with disks and partitions
Re: [Cooker] mkbootdisk - no space on device
Guillaume Cottenceau wrote: Chmouel Boudjnah [EMAIL PROTECTED] writes: humm actually i just tested and i created a initrd with xfs support without problem. Of course. The problem is to make a -bootdisk- (on a standard 1.44 floppy) with XFS support. on a single standart floppy it simply doesn't work we need 2 floppies , the other solution is zip/ supper disk (100/120Mb) or CD with 2.88Mb boot image or hd emulation but not everybody has zip/supper disk or cd writer
Re: [Cooker] mkbootdisk - no space on device
Yes unfortunately XFS pushes a boot floppy over the edge. http://oss.sgi.com/projects/xfs/faq.html#xfsfitfloppy As the installer CD's can usually be used as a rescue disk we haven't spent much time trying to shrink XFS ... not that it would be an easy task. Also note the latest linux care rescue image mini CD's has xfs support. (I haven't tried it personally but Martin Peterson of LC was the source) On Fri, 2001-09-14 at 03:42, Borsenkow Andrej wrote: New install, single had, root on /dev/hda1 as xfs. Bootdisk is not bootable,after Uncompressing RAM image endless dots. From ddebug.log: DrakX v1.576 built Thu Sep 13 16:03:57 2001 * starting step `createBootdisk' * to put in modules * missing module floppy * missing module floppy * running: /usr/bin/insmod_ 2 /dev/tty5 -f /tmp/loop.o * running: /usr/bin/insmod_ 2 /dev/tty5 -f /tmp/fat.o * running: /usr/bin/insmod_ 2 /dev/tty5 -f /tmp/vfat.o * running: mkbootdisk --noprompt --appendargs devfs=mount --device /dev/fd0 2.4 .8-22mdk with root /mnt mke2fs 1.24a (02-Sep-2001) gzip: stdout: No space left on device * step `createBootdisk' finished * starting step `setupBootloader' * to put in modules * running: mkinitrd -v -f /boot/initrd-2.4.8-22mdk.img --ifneeded 2.4.8-22mdk wi th root /mnt Using modules: ./kernel/fs/pagebuf/pagebuf.o ./kernel/fs/xfs_support/xfs_suppor t.o ./kernel/fs/xfs/xfs.o /sbin/nash - /tmp/initrd.YF1tLh/bin/nash /sbin/insmod.static - /tmp/initrd.YF1tLh/bin/insmod Loading module pagebuf with options Loading module xfs_support with options Loading module xfs with options Contents of RCFILE: #!/bin/nash echo Loading pagebuf module insmod /lib/pagebuf.o echo Loading xfs_support module insmod /lib/xfs_support.o echo Loading xfs module insmod /lib/xfs.o echo Mounting /proc filesystem mount -t proc /proc /proc echo Creating root device mkrootdev /dev/root echo 0x0100 /proc/sys/kernel/real-root-dev umount /proc echo Mounting root filesystem mount --ro -t xfs /dev/root /sysroot pivot_root /sysroot /sysroot/initrd echo Remounting devfs at correct place if necessary handledevfs Creating filesystem with size 1344KB and 46 inodes mke2fs 1.24a (02-Sep-2001)
Re: [Cooker] mkbootdisk - no space on device
On Fri, 2001-09-14 at 14:49, svetljo wrote: Hi couldn't we have 2 bootdisk: one for the kernel and lilo, and one for the ramdisk smth like debian, the kernel is realy too big it should be much simple with 2 floppies If anybody knows how to create a 2 floppy boot we would be interested in the procedure. This question has come up many times before and there is no real good answer for a standard 1.44 floppy. Guillaume Cottenceau wrote: Chmouel Boudjnah [EMAIL PROTECTED] writes: Guillaume Cottenceau [EMAIL PROTECTED] writes: retry mkbootdisk with it. With XFS, I'm not sure it would suffice, but we can pray (and now I can't do anything else than asking we switch from the Linux kernel to a less bloated kernel if any). russel for initrd can we remove the pagebuf module and load it after ? won't change much isn't it ? -rw-r--r--1 root root 576672 Sep 14 16:32 xfs.o -rw-r--r--1 root root20523 Sep 14 16:32 xfs_support.o -rw-r--r--1 root root43796 Sep 14 16:32 pagebuf.o
Re: [Cooker] mkbootdisk - no space on device
Russell Cattelan wrote: On Fri, 2001-09-14 at 14:49, svetljo wrote: Hi couldn't we have 2 bootdisk: one for the kernel and lilo, and one for the ramdisk smth like debian, the kernel is realy too big it should be much simple with 2 floppies If anybody knows how to create a 2 floppy boot we would be interested in the procedure. Debian has allways used 2 1.44 floppies for install and rescue the first one is kernel + bootloader +init scripts the second is the ramdisk This question has come up many times before and there is no real good answer for a standard 1.44 floppy. Guillaume Cottenceau wrote: Chmouel Boudjnah [EMAIL PROTECTED] writes: Guillaume Cottenceau [EMAIL PROTECTED] writes: retry mkbootdisk with it. With XFS, I'm not sure it would suffice, but we can pray (and now I can't do anything else than asking we switch from the Linux kernel to a less bloated kernel if any). russel for initrd can we remove the pagebuf module and load it after ? won't change much isn't it ? -rw-r--r--1 root root 576672 Sep 14 16:32 xfs.o -rw-r--r--1 root root20523 Sep 14 16:32 xfs_support.o -rw-r--r--1 root root43796 Sep 14 16:32 pagebuf.o
Re: [Cooker] mkbootdisk - no space on device
On Tuesday 18 Sep 2001 19:32, svetljo wrote: Russell Cattelan wrote: On Fri, 2001-09-14 at 14:49, svetljo wrote: Hi couldn't we have 2 bootdisk: one for the kernel and lilo, and one for the ramdisk [...] Debian has allways used 2 1.44 floppies for install and rescue the first one is kernel + bootloader +init scripts the second is the ramdisk Redhat used to use two floppies as well. Why not us now? -- Peter Ruskin, Wrexham, Wales. Registered Linux User No. 219434 ( see http://counter.li.org/ ). Linux Mandrake release 8.0 (Traktopel) for i586, kernel 2.4.3-20mdk-win4lin-pnr1. XFree86 4.0.3, patch level 7mdk. KDE: 2.1.1. Qt: 2.3.1. Uptime: 18:47
Re: [Cooker] mkbootdisk - no space on device
Guillaume Cottenceau wrote: svetljo [EMAIL PROTECTED] writes: do you agree that we can not have a single bootable floppy for xfs lvm system or i'm missing smth XFS is special in the sense that it has a big VFS-like bloat for patching on a standard 2.4 kernel, so it doesn't really count. as of LVM, this is another story, and I don't know pretty well as hard do we want it for everyone's use. here at mandrake, we don't use/test it very often so i was inclined to think that it's more of an advanced/expert feature, but i don't know it well to say more. i think this is a big misstake, lvm is definetly not advanced/expert feature and it makes the life pretty simple it's a dumb example , but what can i do if i use standart partitions and 1# i had for example too much MP3s and no more space on device A how can i get some more place , should i make new partitions, format them and copy the files over to device B 2# i didn't know how big should i make partition C and now i use only 25% and so on
Re: [Cooker] mkbootdisk - no space on device
On Fri, 2001-09-14 at 09:26, Chmouel Boudjnah wrote: Guillaume Cottenceau [EMAIL PROTECTED] writes: retry mkbootdisk with it. With XFS, I'm not sure it would suffice, but we can pray (and now I can't do anything else than asking we switch from the Linux kernel to a less bloated kernel if any). russel for initrd can we remove the pagebuf module and load it after ? No pagebuf is the linux I/O part of XFS. It is a complete rewrite of the irix I/O routines for linux. One idea that has floated around in my head for a while is to modularize the dir code. XFS has 2 directory formats dir1 and dir2, dir1 was the original format that had several performance drawbacks, and such was rewritten (dir2) By default mkfs.xfs on linux is set to use dir2, but the dir1 format is still supported for compatibility with older irix filesystems. If the dir1 code was separated out and made a LKM an thus only loaded for the rare cases of FS migration it might reduce the footprint of XFS. But I have no idea how much space it would save... it's just an idea. -Russell
Re: [Cooker] mkbootdisk - no space on device
Guillaume Cottenceau wrote: svetljo [EMAIL PROTECTED] writes: Of course. The problem is to make a -bootdisk- (on a standard 1.44 floppy) with XFS support. on a single standart floppy it simply doesn't work we need 2 floppies , the other solution is zip/ supper disk (100/120Mb) or CD with 2.88Mb boot image or hd emulation but not everybody has zip/supper disk or cd writer There is also the superformatted floppies (as for example XFS people talks about[1]) but it's a no-go because too dangerous. And actually having bootdisks is not that important since you normally boot your system with on-disk bootloader, and when you need to rescue you can use CDROM distro (or network floppy etc) to launch our rescue. Of course if we can fix current problem it's cool but I don't want to put a dirty and hassling hack in mkinitrd/mkbootdisk for an issue that I don't see as crucial (XFS large code + medium important need for booting from floppy). and what if smbd install on XFS / raid and can not remember exactly which stripe_size and/or raid_dev and/or in which order he maked the raids the kernel from the CD doesn't have compiled in raid so no autodetect i'm really happy that you didn't abandoned XFS ( i was realy afraid of that) what in case smbd upgrade the lvm tools and kernel code the CD can not help in these cases there allways be need for a custem created boot disk/s or the person should have some more place and reinstall, upgrade the tools or create the special kernel and then use them to rescue the old system is that not crucial Ref: [1] http://oss.sgi.com/projects/xfs/faq.html#xfsfitfloppy
Re: [Cooker] mkbootdisk - no space on device
mcc has a facility for building the boot floppy. If the kernel is becoming too large for a floppy, one way to attempt to make it fit is to probe the system to discover which kernel modules are in use and only include them in the boot floppy. --- Guillaume Cottenceau [EMAIL PROTECTED] wrote: SI Reasoning [EMAIL PROTECTED] writes: Maybe it would be simpler to have the system judge which modules are in use when building the rescue disk and include only them. What do you mean? -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/ = SI Reasoning [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. Benjamin Franklin __ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/
Re: [Cooker] mkbootdisk - no space on device
Guillaume Cottenceau wrote: svetljo [EMAIL PROTECTED] writes: what about my idea about 2 disks IMO, 2 floppies is way to unsafe. As for me, i prefer using a cdrom rescue, or why should it be a way to unsafe, i would also prefer to use a rescue CD it's much faster and you have much more tools, but if you use some exotic things like RAID, LVM-1.0.1rc2, XFS, i think there are no that much ( if any ) rescue CD's which can handle the situation and there will be always new things like EVMS when it becomes more stable There is ours! Please try it, it should support everything a rescue would need. Type rescue at the very beginning of the install (first splash screen). well i have tried it many times but the kernel is without raid, so i have no autodetect , i have separate /boot where i have my radtab, and i'm not that shure but i think i can not create more then 2 or 3 raids ( i have 6, with LVM over them ) a lot of the lvm stuff is missing and it's 0.9.1beta2 version ( i use 1.0.1rc2 ) i had to use the XFS-cooker as rescue and i will try MDK 8.1 but i think that won't help much it wont have raid compiled in the kernel and it wont have lvm-1.0 or later and in case it doesn't have xfs in the boot-kernel or as module ... one more point what about the people which can not boot from a cd for some reason how would they install or rescue with XFS can it be done with the floppy images ?
Re: [Cooker] mkbootdisk - no space on device
Chmouel Boudjnah wrote: svetljo [EMAIL PROTECTED] writes: Blue Lizard wrote: I recall chmouel stating that [the mandrake] xfs patch is not so big. but smbd (i think he ) said that the xfs module is ~500k Numbers : Without XFS (chmou@kernel)[linux/]-% grep CONFIG_XFS_FS .config [nothing] (chmou@kernel)[linux/]-% make oldconfig make dep make clean make bzImage [...] (chmou@kernel)[linux/]-% du -sh arch/i386/boot/bzImage 1016k arch/i386/boot/bzImage With XFS : (chmou@kernel)[linux/]-% grep CONFIG_XFS_FS .config CONFIG_XFS_FS=m (chmou@kernel)[linux/]-% make oldconfig make dep make clean make bzImage [...] (chmou@kernel)[linux/]-% du -sh arch/i386/boot/bzImage 1016k arch/i386/boot/bzImage and what about xfs.o
Re: [Cooker] mkbootdisk - no space on device
Chmouel Boudjnah wrote: svetljo [EMAIL PROTECTED] writes: and what about xfs.o what do you mean by that, can we access a xfs root without xfs modules in the initrd or without compileing it in the kernel how can i build bootdisk for a xfs system ? this is another story : (chmou@kernel)[~]-% lsmod|grep xfs xfs 518752 1 (autoclean) xfs_support 9536 0 (autoclean) [xfs] pagebuf27008 1 (autoclean) [xfs xfs_support] it's probably my trouble but [root@svetljo xfs]# pwd /lib/modules/2.4.9-ac7-devfs/kernel/fs/xfs [root@svetljo xfs]# ls -l total 4144 -rw-r--r--1 root root 4241177 Sep 17 09:09 xfs.o [root@svetljo xfs_support]# pwd /lib/modules/2.4.9-ac7-devfs/kernel/fs/xfs_support [root@svetljo xfs_support]# ls -l total 20 -rw-r--r--1 root root16642 Sep 17 09:09 xfs_support.o [root@svetljo pagebuf]# pwd /lib/modules/2.4.9-ac7-devfs/kernel/fs/pagebuf [root@svetljo pagebuf]# ls -l total 40 -rw-r--r--1 root root40905 Sep 17 09:09 pagebuf.o it's a 2.4.9-ac7 with your patch for xfs from 2.4.8-22mdk
Re: [Cooker] mkbootdisk - no space on device
do you agree that we can not have a single bootable floppy for xfs lvm system or i'm missing smth Chmouel Boudjnah wrote: svetljo [EMAIL PROTECTED] writes: and what about xfs.o this is another story : (chmou@kernel)[~]-% lsmod|grep xfs xfs 518752 1 (autoclean) xfs_support 9536 0 (autoclean) [xfs] pagebuf27008 1 (autoclean) [xfs xfs_support]
Re: [Cooker] mkbootdisk - no space on device
Chmouel Boudjnah wrote: svetljo [EMAIL PROTECTED] writes: yes i am but that another problem... to have more then one boot floppy ? humm actually i just tested and i created a initrd with xfs support without problem. what do you mean by that you could place the kernel, the initrd and bootloader on a single floppy ? or you could create a initrd with xfs support ? i had no troubles creating a initrd with xfs, but making boot disk with the initrd and the kernel i think is imposible with single floppy am i wrong
Re: [Cooker] mkbootdisk - no space on device
Chmouel Boudjnah wrote: Chmouel Boudjnah [EMAIL PROTECTED] writes: svetljo [EMAIL PROTECTED] writes: what do you mean by that you could place the kernel, the initrd and bootloader on a single floppy ? or you could create a initrd with xfs support ? i had no troubles creating a initrd with xfs, but making boot disk with the initrd and the kernel i think is imposible with single floppy am i wrong i mean a mkbootdisk.. humm forget me i used a usb-floppy driver which make the things not casual.. not casual ? is it normal floppy or zip/ supper disk ( smth about = 100Mb) and in case 1,44 floppy and lvm-1.0.1rc2 ,can i ask you to send me the .img of the floppy but how did you done that the kernel is ~1Mb , the initrd should be more than 0,5Mb i think ( in case it contains the lvm binaries) it is already no place on the floppy , and what about the bootloader ?
Re: [Cooker] mkbootdisk - no space on device
Chmouel Boudjnah wrote:
svetljo [EMAIL PROTECTED] writes:
not casual ?
humm i mean that this device (i believe it is not the device but the
kernel) report wrong size so it can copy it but after booting is
none...
but it works with zip, so i have pretty much place now
i thought i can not boot from zip ( i have read that somewhere )( ha ha
so people go for zip !)
and one idea couldn't we have mkbootdisk.lvm with lvmcreate_initrd
or may be i should post this to the LVM-list
i'm not familiar with shell scripts but take a look at the diff, would you
*** mkbootdisk.lvm Mon Sep 17 12:11:09 2001
--- mkbootdisk Mon Sep 17 12:07:23 2001
***
*** 175,187
[ -n $verbose ] echo done.
[ -n $verbose ] echo -n Creating initrd image...
! /sbin/lvmcreate_initrd $mkinitrdargs $kernel
! cp -a /boot/initrd-lvm-$kernel.gz $MOUNTDIR/initrd.gz
[ -n $verbose ] echo done.
[ -n $verbose ] echo -n Setting up syslinux...
! [ -f $MOUNTDIR/initrd.gz ] INITRDARG=initrd=initrd.gz
if [ $(echo $rootdev | cut -b 6-9) = loop ]; then
rootdev=$(ls -l $rootdev | sed 's/,//' | awk '{ printf(%02x%02x\n, $5, $6); }')
--- 175,186
[ -n $verbose ] echo done.
[ -n $verbose ] echo -n Creating initrd image...
! /sbin/mkinitrd $mkinitrdargs $witheth --ifneeded $MOUNTDIR/initrd.img $kernel
[ -n $verbose ] echo done.
[ -n $verbose ] echo -n Setting up syslinux...
! [ -f $MOUNTDIR/initrd.img ] INITRDARG=initrd=initrd.img
if [ $(echo $rootdev | cut -b 6-9) = loop ]; then
rootdev=$(ls -l $rootdev | sed 's/,//' | awk '{ printf(%02x%02x\n, $5, $6); }')
Re: [Cooker] mkbootdisk - no space on device
Submitted 14-Sep-01 by Guillaume Cottenceau: (and now I can't do anything else than asking we switch from the Linux kernel to a less bloated kernel if any). The Linux kernel isn't really bloated, until you start adding the 100+ patches that make up a Mandrake kernel. I'm afraid that our attempt to appease all of the desires for the latest thing is making our kernel too large. While it would be unreasonable to provide specific kernels for every combination of desirable features, perhaps features that would not be available in a default Mandrake install should be unavailable in a precompiled binary kernel. With the availability of both the .src.rpm and kernel-source package, it is trivial for anyone who wants the more exotic features to compile his own kernel. -- Anton GrahamGPG ID: 0x18F78541 [EMAIL PROTECTED] RSA key available upon request There is nothing wrong with writing ... as long as it is done in private and you wash your hands afterward.
Re: [Cooker] mkbootdisk - no space on device
well ok , but have you compiled a xfs kernel how much does it weight my is 1.3 Mb with compiled in raid-0 linear-raid lvm xfs,reiser,ext2 SI Reasoning wrote: Maybe it would be simpler to have the system judge which modules are in use when building the rescue disk and include only them. --- Anton Graham [EMAIL PROTECTED] wrote: Submitted 14-Sep-01 by Guillaume Cottenceau: (and now I can't do anything else than asking we switch from the Linux kernel to a less bloated kernel if any). The Linux kernel isn't really bloated, until you start adding the 100+ patches that make up a Mandrake kernel. I'm afraid that our attempt to appease all of the desires for the latest thing is making our kernel too large. While it would be unreasonable to provide specific kernels for every combination of desirable features, perhaps features that would not be available in a default Mandrake install should be unavailable in a precompiled binary kernel. With the availability of both the .src.rpm and kernel-source package, it is trivial for anyone who wants the more exotic features to compile his own kernel. -- Anton GrahamGPG ID: 0x18F78541 [EMAIL PROTECTED] RSA key available upon request There is nothing wrong with writing ... as long as it is done in private and you wash your hands afterward. = SI Reasoning [EMAIL PROTECTED] gnupg/pgp key id 035213BC The smart way to keep people passive and obedient is to strictly limit the spectrum of acceptable opinion, but allow very lively debate within that spectrum. -- Noam Chomsky __ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/
Re: [Cooker] mkbootdisk - no space on device
what about my idea about 2 disks IMO, 2 floppies is way to unsafe. As for me, i prefer using a cdrom rescue, or why should it be a way to unsafe, i would also prefer to use a rescue CD it's much faster and you have much more tools, but if you use some exotic things like RAID, LVM-1.0.1rc2, XFS, i think there are no that much ( if any ) rescue CD's which can handle the situation and there will be always new things like EVMS when it becomes more stable a simple grub on floppy. that sounds gut but what can i do with my kernel (1.3Mb) where should i put the initrd -- you can not initialise LVM without it even if its compiled in mkbootdisk should die!
Re: [Cooker] mkbootdisk - no space on device
I would think worst case should be 1 floppy with kernel and maybe a 2nd with extra modules that could not fit in 1st. If kernel is too large, modulize more. --- svetljo [EMAIL PROTECTED] wrote: well ok , but have you compiled a xfs kernel how much does it weight my is 1.3 Mb with compiled in raid-0 linear-raid lvm xfs,reiser,ext2 SI Reasoning wrote: Maybe it would be simpler to have the system judge which modules are in use when building the rescue disk and include only them. --- Anton Graham [EMAIL PROTECTED] wrote: Submitted 14-Sep-01 by Guillaume Cottenceau: (and now I can't do anything else than asking we switch from the Linux kernel to a less bloated kernel if any). The Linux kernel isn't really bloated, until you start adding the 100+ patches that make up a Mandrake kernel. I'm afraid that our attempt to appease all of the desires for the latest thing is making our kernel too large. While it would be unreasonable to provide specific kernels for every combination of desirable features, perhaps features that would not be available in a default Mandrake install should be unavailable in a precompiled binary kernel. With the availability of both the .src.rpm and kernel-source package, it is trivial for anyone who wants the more exotic features to compile his own kernel. -- Anton GrahamGPG ID: 0x18F78541 [EMAIL PROTECTED] RSA key available upon request There is nothing wrong with writing ... as long as it is done in private and you wash your hands afterward. = SI Reasoning [EMAIL PROTECTED] gnupg/pgp key id 035213BC The smart way to keep people passive and obedient is to strictly limit the spectrum of acceptable opinion, but allow very lively debate within that spectrum. -- Noam Chomsky __ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/ = SI Reasoning [EMAIL PROTECTED] gnupg/pgp key id 035213BC The smart way to keep people passive and obedient is to strictly limit the spectrum of acceptable opinion, but allow very lively debate within that spectrum. -- Noam Chomsky __ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/
Re: [Cooker] mkbootdisk - no space on device
I would think worst case should be 1 floppy with kernel and maybe a 2nd with extra modules that could not fit in 1st. If kernel is too large, modulize more. that was my idea too 1 floppy : kernel with compiled in raid and if there is some more space lvm ,FSes 2 floppy : initrd with lvm-tools and other modules ( FS ) my kernel has almost only the important for my system raid-0, linear-raid, lvm, ext2,xfs,reiserfs( i'll let reiser soon) the thing is that xfs is too big i'd tried kernel with FS , raid as modules, the kernel was ~800-900k the initrd --preload xfs ,raid-0, linear was ~2Mb ! --- svetljo [EMAIL PROTECTED] wrote: well ok , but have you compiled a xfs kernel how much does it weight my is 1.3 Mb with compiled in raid-0 linear-raid lvm xfs,reiser,ext2 SI Reasoning wrote: Maybe it would be simpler to have the system judge which modules are in use when building the rescue disk and include only them. --- Anton Graham [EMAIL PROTECTED] wrote: Submitted 14-Sep-01 by Guillaume Cottenceau: (and now I can't do anything else than asking we switch from the Linux kernel to a less bloated kernel if any). The Linux kernel isn't really bloated, until you start adding the 100+ patches that make up a Mandrake kernel. I'm afraid that our attempt to appease all of the desires for the latest thing is making our kernel too large. While it would be unreasonable to provide specific kernels for every combination of desirable features, perhaps features that would not be available in a default Mandrake install should be unavailable in a precompiled binary kernel. With the availability of both the .src.rpm and kernel-source package, it is trivial for anyone who wants the more exotic features to compile his own kernel. -- Anton GrahamGPG ID: 0x18F78541 [EMAIL PROTECTED] RSA key available upon request There is nothing wrong with writing ... as long as it is done in private and you wash your hands afterward. = SI Reasoning [EMAIL PROTECTED] gnupg/pgp key id 035213BC The smart way to keep people passive and obedient is to strictly limit the spectrum of acceptable opinion, but allow very lively debate within that spectrum. -- Noam Chomsky __ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/ = SI Reasoning [EMAIL PROTECTED] gnupg/pgp key id 035213BC The smart way to keep people passive and obedient is to strictly limit the spectrum of acceptable opinion, but allow very lively debate within that spectrum. -- Noam Chomsky __ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/
Re: [Cooker] mkbootdisk - no space on device
I recall chmouel stating that [the mandrake] xfs patch is not so big.
Re: [Cooker] mkbootdisk - no space on device
Le Dimanche 16 Septembre 2001 23:33, Blue Lizard scribit : I recall chmouel stating that [the mandrake] xfs patch is not so big. About 1k diff. Re: [Cooker] Re: [CHRPM] mkinitrd-3.1.6-8mdk De : Chmouel Boudjnah [EMAIL PROTECTED] À : [EMAIL PROTECTED] Cc : [EMAIL PROTECTED] Date : 15 Sep 2001 16:16:48 +0200 Fabrice FACORAT [EMAIL PROTECTED] writes: Sure but what about the changes in the core system ? it will be interesting to see the size with and without the XFS patch that only 1k worse. -- Copyleft Faber's prod. 2001 http://perso.wanadoo.fr/linux_wizard/index.html
Re: [Cooker] mkbootdisk - no space on device
Blue Lizard wrote: I recall chmouel stating that [the mandrake] xfs patch is not so big. but smbd (i think he ) said that the xfs module is ~500k
Re: [Cooker] mkbootdisk - no space on device
Hi couldn't we have 2 bootdisk: one for the kernel and lilo, and one for the ramdisk smth like debian, the kernel is realy too big it should be much simple with 2 floppies Guillaume Cottenceau wrote: Chmouel Boudjnah [EMAIL PROTECTED] writes: Guillaume Cottenceau [EMAIL PROTECTED] writes: retry mkbootdisk with it. With XFS, I'm not sure it would suffice, but we can pray (and now I can't do anything else than asking we switch from the Linux kernel to a less bloated kernel if any). russel for initrd can we remove the pagebuf module and load it after ? won't change much isn't it ? -rw-r--r--1 root root 576672 Sep 14 16:32 xfs.o -rw-r--r--1 root root20523 Sep 14 16:32 xfs_support.o -rw-r--r--1 root root43796 Sep 14 16:32 pagebuf.o
Re: [Cooker] mkbootdisk - no space on device
sorry it was syslinux right ? svetljo wrote: Hi couldn't we have 2 bootdisk: one for the kernel and lilo, and one for the ramdisk smth like debian, the kernel is realy too big it should be much simple with 2 floppies Guillaume Cottenceau wrote: Chmouel Boudjnah [EMAIL PROTECTED] writes: Guillaume Cottenceau [EMAIL PROTECTED] writes: retry mkbootdisk with it. With XFS, I'm not sure it would suffice, but we can pray (and now I can't do anything else than asking we switch from the Linux kernel to a less bloated kernel if any). russel for initrd can we remove the pagebuf module and load it after ? won't change much isn't it ? -rw-r--r--1 root root 576672 Sep 14 16:32 xfs.o -rw-r--r--1 root root20523 Sep 14 16:32 xfs_support.o -rw-r--r--1 root root43796 Sep 14 16:32 pagebuf.o
Re: [Cooker] mkbootdisk
[EMAIL PROTECTED] (andre) writes: mkbootdisk (and subsequently drakfloppy) doesn't work with me Here is the error i get mkbootdisk --device /dev/fd0 2.4.8-12mdk Insert a disk in /dev/fd0. Any information on the disk will be lost. Press Enter to continue or ^C to abort: /dev/fd0H1440: No such file or directory seems like devfsd provides only a minimal compatibility. adding this to /etc/devfsd.conf fixes it: REGISTER^floppy/0u1440 CFUNCTION GLOBAL symlink floppy/0u1440 fd0H1440 REGISTER^floppy/1u1440 CFUNCTION GLOBAL symlink floppy/1u1440 fd1H1440 UNREGISTER ^floppy/0u1440 CFUNCTION GLOBAL unlink fd0H1440 UNREGISTER ^floppy/1u1440 CFUNCTION GLOBAL unlink fd1H1440 but this is quite ugly :-( i'm also going to patch mkbootdisk so this isn't needed anymore.
Re: [Cooker] mkbootdisk
[EMAIL PROTECTED] (andre) writes: mkbootdisk (and subsequently drakfloppy) doesn't work with me Here is the error i get mkbootdisk --device /dev/fd0 2.4.8-12mdk Insert a disk in /dev/fd0. Any information on the disk will be lost. Press Enter to continue or ^C to abort: /dev/fd0H1440: No such file or directory Failed to format /dev/fd0 You should use rpmmon[1] and CC to the maintainer, for speed of response. [gc@bi ~] rpmmon -p mkbootdisk yduret Anyway, this is a devfsd problem, and we're working on it. Ref: [1] http://people.mandrakesoft.com/~gc/html/rpmmon-tut.html -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] mkbootdisk
[EMAIL PROTECTED] (andre) writes: [...] You should use rpmmon[1] and CC to the maintainer, for speed of response. [gc@bi ~] rpmmon -p mkbootdisk yduret [...] Ref: [1] http://people.mandrakesoft.com/~gc/html/rpmmon-tut.html [...] rpm -qi mkbootdisk gives [EMAIL PROTECTED] This makes the difference between `Packager' and `Maintainer'. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] mkbootdisk
[EMAIL PROTECTED] (andre) writes: mkbootdisk (and subsequently drakfloppy) doesn't work with me Here is the error i get mkbootdisk --device /dev/fd0 2.4.8-12mdk Insert a disk in /dev/fd0. Any information on the disk will be lost. Press Enter to continue or ^C to abort: /dev/fd0H1440: No such file or directory Failed to format /dev/fd0 You should use rpmmon[1] and CC to the maintainer, for speed of response. [gc@bi ~] rpmmon -p mkbootdisk yduret Anyway, this is a devfsd problem, and we're working on it. Ref: [1] http://people.mandrakesoft.com/~gc/html/rpmmon-tut.html -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/ rpm -qi mkbootdisk gives [EMAIL PROTECTED]
Re: [Cooker] mkbootdisk
"Paul Giordano" [EMAIL PROTECTED] writes: Hi Pixel, If the devices are not equal ($device $rdevice) then lilo gets a device busy attempting to write to the floppy (now, I'm using devfs and that may be the difference.) As long as the device lilo attempts to use is the same as the one mounted to /mnt/mkbootdisk then lilo's happy (at least on my system!) ok, i didn't understand. Now it's plain clear :) thanks, Pixel (fixing the pb now)
Re: [Cooker] mkbootdisk
Hi Pixel, If the devices are not equal ($device $rdevice) then lilo gets a device busy attempting to write to the floppy (now, I'm using devfs and that may be the difference.) As long as the device lilo attempts to use is the same as the one mounted to /mnt/mkbootdisk then lilo's happy (at least on my system!) Thanks for the help... Gio - Original Message - From: "Pixel" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, March 11, 2001 3:42 PM Subject: Re: [Cooker] mkbootdisk "Paul Giordano" [EMAIL PROTECTED] writes: Also - could you change the line "boot=$device" that's written to the $MOUNTDIR/etc/lilo.conf to read "boot=$rdevice"? Otherwise you get a device busy condition using devfs - $device is /dev/fd0, $rdevice is /dev/fd0u1440. can you explain more? rdevice is /dev/fd0H1440, not fd0u1440. why would it work better with boot=/dev/fd0H1440 in lilo.conf? thanks, Pixel.
Re: [Cooker] mkbootdisk
"Paul Giordano" [EMAIL PROTECTED] writes: Could you put double-quotes around the [ -z $rootdev ] at the bottom please? ok, done
Re: [Cooker] mkbootdisk
"Paul Giordano" [EMAIL PROTECTED] writes: Also - could you change the line "boot=$device" that's written to the $MOUNTDIR/etc/lilo.conf to read "boot=$rdevice"? Otherwise you get a device busy condition using devfs - $device is /dev/fd0, $rdevice is /dev/fd0u1440. can you explain more? rdevice is /dev/fd0H1440, not fd0u1440. why would it work better with boot=/dev/fd0H1440 in lilo.conf? thanks, Pixel.
Re: [Cooker] mkbootdisk-1.2.7-2mdk broken on cooker
"Dmitry V. Levin" [EMAIL PROTECTED] writes: Why not to add "Requires" or "Conflicts" tag about lilo requirements? :) It would help various automated tools to do proper package upgrades. because it was introduced only since the new upgrade of lilo which was only for cooker. -- MandrakeSoft Inc http://www.chmouel.org --Chmouel
Re: [Cooker] mkbootdisk-1.2.7-2mdk broken on cooker
Peter Ruskin [EMAIL PROTECTED] writes: [11:27 root@penguin:~]# mkbootdisk --device /dev/fd0 2.2.17-28mdk Insert a disk in /dev/fd0. Any information on the disk will be lost. Press Enter to continue or ^C to abort: mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 usage: lilo [ -C config_file ] -q [ -m map_file ] [ -v ... ] lilo [ -C config_file ] [ -b boot_device ] [ -c ] [ -l | -L ] [ -i boot_loader ] [ -m map_file ] [ -d delay ] [ -v ... ] [ -t ] [ -s save_file | -S save_file ] [ -P fix | -P ignore ] [ -r root_dir ] [ -w ] lilo [ -C config_file ] [ -m map_file ] -R [ word ... ] lilo [ -C config_file ] -I name [ options ] lilo [ -C config_file ] [ -s save_file ] -u | -U [ boot_device ] lilo -T help (to see a list of options) lilo -V The result is not a bootable disk. There seems to be something wrong with the way lilo is called. upgrade to the last lilo.. -- MandrakeSoft Inc http://www.chmouel.org --Chmouel
Re: [Cooker] mkbootdisk-1.2.7-2mdk broken on cooker
On Mon, Nov 27, 2000 at 09:09:51PM +0100, Chmouel Boudjnah wrote: [11:27 root@penguin:~]# mkbootdisk --device /dev/fd0 2.2.17-28mdk Insert a disk in /dev/fd0. Any information on the disk will be lost. Press Enter to continue or ^C to abort: mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 usage: lilo [ -C config_file ] -q [ -m map_file ] [ -v ... ] lilo [ -C config_file ] [ -b boot_device ] [ -c ] [ -l | -L ] [ -i boot_loader ] [ -m map_file ] [ -d delay ] [ -v ... ] [ -t ] [ -s save_file | -S save_file ] [ -P fix | -P ignore ] [ -r root_dir ] [ -w ] lilo [ -C config_file ] [ -m map_file ] -R [ word ... ] lilo [ -C config_file ] -I name [ options ] lilo [ -C config_file ] [ -s save_file ] -u | -U [ boot_device ] lilo -T help (to see a list of options) lilo -V The result is not a bootable disk. There seems to be something wrong with the way lilo is called. upgrade to the last lilo.. Why not to add "Requires" or "Conflicts" tag about lilo requirements? :) It would help various automated tools to do proper package upgrades. Regards, Dmitry +-+ Dmitry V. Levin mailto:[EMAIL PROTECTED] Software Engineer PGP pubkey http://www.fandra.org/users/ldv/pgpkeys.html IPLabs Linux Team http://linux.iplabs.ru Fandra Project http://www.fandra.org +-+ UNIX is user friendly. It's just very selective about who it's friends are. PGP signature
