Menu
▾
▴
devil-linux-develop
|
From: Heiko Z. <he...@zu...> - 2003-11-08 21:26:22
|
Hey, the latest changes to the initrd and the usage of the loop mounted zisofs should enable us to boot from almost any device without changes to the init system. Only the save-config part will most likely need some "adjustments". Another benefit is of course, that the zisofs image is much smaller and we can now use i.e. 256 MB PenDrives for the full DL and still have a lot of free space left. cya Heiko |
|
From: Bruce S. <bw...@ar...> - 2003-11-08 21:44:32
|
> the latest changes to the initrd and the usage of the loop mounted > zisofs should enable us to boot from almost any device without changes > to the init system. > Only the save-config part will most likely need some "adjustments". > > Another benefit is of course, that the zisofs image is much smaller and > we can now use i.e. 256 MB PenDrives for the full DL and still have a > lot of free space left. Does save-config work OK if the pendrive is zisofs? - BS |
|
From: Heiko Z. <he...@zu...> - 2003-11-08 22:51:22
|
Bruce Smith wrote: >>the latest changes to the initrd and the usage of the loop mounted >>zisofs should enable us to boot from almost any device without changes >>to the init system. >>Only the save-config part will most likely need some "adjustments". >> >>Another benefit is of course, that the zisofs image is much smaller and >>we can now use i.e. 256 MB PenDrives for the full DL and still have a >>lot of free space left. >> >> > >Does save-config work OK if the pendrive is zisofs? > > It should. I can't test it today, since a friend is picking me up soon. Remind me tomorrow, to check it. cya Heiko |
|
From: Bruce S. <bw...@ar...> - 2003-11-08 23:21:21
|
> >Does save-config work OK if the pendrive is zisofs? > > > It should. I don't know anything about "zisofs", but if it's anything like ISO9660 (the standard for CDROM's), then there may be a problem. You can't write to ISO9660 filesystems, no matter if they are on read-write media or not. If that's the case, then the pendrive would have to be partitioned with a second non-zisofs partition to save the config to. > I can't test it today, since a friend is picking me up soon. > Remind me tomorrow, to check it. Consider this your reminder! :-) - BS |
|
From: Heiko Z. <he...@zu...> - 2003-11-09 15:41:22
|
Bruce Smith wrote: >>>Does save-config work OK if the pendrive is zisofs? >>> >>> >>> >>It should. >> >> > >I don't know anything about "zisofs", but if it's anything like >ISO9660 (the standard for CDROM's), then there may be a problem. >You can't write to ISO9660 filesystems, no matter if they are >on read-write media or not. > >If that's the case, then the pendrive would have to be partitioned >with a second non-zisofs partition to save the config to. > > You're correct. But it works the following way: I format the USB stick with FAT16, transfer the MBR and syslinux bootloader. Then I copy a bunch of files to the root of the stick (license, DEVIL-LINUX file to recognize the correct partition) and I copy the file bootcd.iso. Then I (loop) mount the iso image. The main disadvantage is that we can't unmount the initrd (since we have open file), but we'll probably find a way around this too. cya Heiko |
|
From: Diego T. <dt...@co...> - 2003-11-15 12:10:58
|
On Sun, Nov 09, 2003 at 10:38:42AM -0500, Heiko Zuerker wrote: > You're correct. > But it works the following way: > I format the USB stick with FAT16, transfer the MBR and syslinux bootloader. Question: That means that usb sticks with more than 512Mb can't be used ? Why don't we use FAT32? > Then I copy a bunch of files to the root of the stick (license, > DEVIL-LINUX file to recognize the correct partition) and I copy the file > bootcd.iso. > Then I (loop) mount the iso image. -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-11-15 14:05:29
|
Diego Torres wrote: >On Sun, Nov 09, 2003 at 10:38:42AM -0500, Heiko Zuerker wrote: > > > >>You're correct. >>But it works the following way: >>I format the USB stick with FAT16, transfer the MBR and syslinux bootloader. >> >> > >Question: That means that usb sticks with more than 512Mb can't be used ? Why don't we use FAT32? > > No. The limit of FAT16 is 2 GB. You can use FAT32 if you want, I just "suggested" FAT16 cu Heiko |
|
From: Diego T. <dt...@co...> - 2003-11-16 12:42:21
|
On Sat, Nov 15, 2003 at 09:00:40AM -0500, Heiko Zuerker wrote: > >>I format the USB stick with FAT16, transfer the MBR and syslinux > >>bootloader. > > > >Question: That means that usb sticks with more than 512Mb can't be used ? > >Why don't we use FAT32? > > > No. The limit of FAT16 is 2 GB. You can use FAT32 if you want, I just > "suggested" FAT16 btw, using fat16 truncates the file devil-linux to "devil-li" more important thing, it doesn't work for me. the new system (iso+mbr) doesn't boot on my system. did someone test it? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-11-16 13:52:52
|
On Sun, Nov 16, 2003 at 01:40:07PM +0100, Diego Torres wrote: > > more important thing, it doesn't work for me. the new system (iso+mbr) doesn't boot on my system. is it possible to use the old grub with the new zisofs? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-11-16 15:35:23
|
On Sun, Nov 16, 2003 at 02:51:22PM +0100, Diego Torres wrote: USB-Stick stuff (maybe this should go to the faq) ? When booting from strange media (aka non-cd), maybe you should check a couple of settings from your bios options. With grub: On an EPIA motherboard, if you try to boot from an usb stick, select USB-HD as the boot device. With Syslinux: On an EPIA motherboard, if you try to boot from an usb stick, select USB-ZIP as the boot device. Do not select anything different from FAT16 when partitioning the media, because syslinux won't boot (as stated on the syslinux.doc file). Specially, don't use fat32 or ext2. If you find problems booting with syslinux, try using the "-s" switch on the dist/install-on-usb script. Sometimes it would help (depends on the hardware used). Yes, I know that the things written above may sound strange, but the worked for me O:) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-11-16 16:41:59
|
Diego Torres wrote: >On Sun, Nov 16, 2003 at 01:40:07PM +0100, Diego Torres wrote: > > >>more important thing, it doesn't work for me. the new system (iso+mbr) doesn't boot on my system. >> >> > >is it possible to use the old grub with the new zisofs? > > Yes it should, it probably needs only minor adjustments (if any). Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-11-16 16:41:00
|
Diego Torres wrote: >On Sat, Nov 15, 2003 at 09:00:40AM -0500, Heiko Zuerker wrote: > > >>>>I format the USB stick with FAT16, transfer the MBR and syslinux >>>>bootloader. >>>> >>>> >>>Question: That means that usb sticks with more than 512Mb can't be used ? >>>Why don't we use FAT32? >>> >>> >>> >>No. The limit of FAT16 is 2 GB. You can use FAT32 if you want, I just >>"suggested" FAT16 >> >> > >btw, using fat16 truncates the file devil-linux to "devil-li" > > The problem is fixed. I mounted the USB stick on the script witht the FS "auto", which most likely resulted on being mounted as "msdos" on your machine. I explicitly set it now to mount with "vfat", which supports the long filenames. >more important thing, it doesn't work for me. the new system (iso+mbr) doesn't boot on my system. > >did someone test it? > > Yes it worked just fine on my box. Heiko |
|
From: Diego T. <dt...@co...> - 2003-11-16 16:51:52
|
On Sun, Nov 16, 2003 at 11:35:48AM -0500, Heiko Zuerker wrote: > The problem is fixed. > I mounted the USB stick on the script witht the FS "auto", which most > likely resulted on being mounted as "msdos" on your machine. > I explicitly set it now to mount with "vfat", which supports the long > filenames. won't work, because the filesystem is fat16 (mkfs.msdos does fat16), not vfat. the correct fix (the one i'm testing now) is to check for /mnt/DEVIL-LINUX and /mnt/devil-li on the mounted media (on config/etc/initrd/linuxrc) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Friedrich L. <fl...@fl...> - 2003-11-16 17:10:18
|
Diego Torres wrote on 16.11.2003 17:51 MET: > On Sun, Nov 16, 2003 at 11:35:48AM -0500, Heiko Zuerker wrote: > >>The problem is fixed. >>I mounted the USB stick on the script witht the FS "auto", which most >>likely resulted on being mounted as "msdos" on your machine. >>I explicitly set it now to mount with "vfat", which supports the long >>filenames. > > won't work, because the filesystem is fat16 (mkfs.msdos does fat16), not vfat. AFAIK vfat works on both FAT16 and FAT32. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
|
From: Heiko Z. <he...@zu...> - 2003-11-16 17:16:56
|
Diego Torres wrote: >On Sun, Nov 16, 2003 at 11:35:48AM -0500, Heiko Zuerker wrote: > > >>The problem is fixed. >>I mounted the USB stick on the script witht the FS "auto", which most >>likely resulted on being mounted as "msdos" on your machine. >>I explicitly set it now to mount with "vfat", which supports the long >>filenames. >> >> > >won't work, because the filesystem is fat16 (mkfs.msdos does fat16), not vfat. > > My understanding is, that vfat is only an extension to fatXX. Can you quickly check you kernel configuration, if vfat is enable under Filesystems? >the correct fix (the one i'm testing now) is to check for /mnt/DEVIL-LINUX and /mnt/devil-li on the mounted media (on config/etc/initrd/linuxrc) > > > We should get it working without those changes. Heiko |
|
From: Diego T. <dt...@co...> - 2003-11-16 17:26:53
|
On Sun, Nov 16, 2003 at 12:14:06PM -0500, Heiko Zuerker wrote: > >won't work, because the filesystem is fat16 (mkfs.msdos does fat16), not > >vfat. > > > My understanding is, that vfat is only an extension to fatXX. yes, you're right. so then, if the device is mounted as vfat then cp should use long filenames? lets try it! > Can you quickly check you kernel configuration, if vfat is enable under > Filesystems? # lsmod |grep vfat vfat 10604 0 (autoclean) fat 32056 0 (autoclean) [vfat msdos] yes, its compiled and installed. mount -t vfat works without problems. -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-11-16 18:48:55
|
On Sun, Nov 16, 2003 at 06:25:56PM +0100, Diego Torres wrote: > > yes, you're right. so then, if the device is mounted as vfat then cp should use long filenames? lets try it! yes, it's working now.... btw.- could someone explain me why su can't be executed by anyone? how i'm supposed to go to root when doing a ssh? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-11-16 19:03:47
|
On Sun, Nov 16, 2003 at 07:47:26PM +0100, Diego Torres wrote: > btw.- could someone explain me why su can't be executed by anyone? how i'm supposed to go to root when doing a ssh? of course diego, you have to add the user you want to enable su to the root group. ah, thanks diego! :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-11-16 22:22:08
|
Diego Torres wrote: >On Sun, Nov 16, 2003 at 07:47:26PM +0100, Diego Torres wrote: > > > >>btw.- could someone explain me why su can't be executed by anyone? how i'm supposed to go to root when doing a ssh? >> >> > >of course diego, you have to add the user you want to enable su to the root group. > >ah, thanks diego! :) > > > Talking to himself...... hmmm..... ;-) Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-11-16 22:22:08
|
Diego Torres wrote: >On Sun, Nov 16, 2003 at 06:25:56PM +0100, Diego Torres wrote: > > >>yes, you're right. so then, if the device is mounted as vfat then cp should use long filenames? lets try it! >> >> > >yes, it's working now.... > >btw.- could someone explain me why su can't be executed by anyone? how i'm supposed to go to root when doing a ssh? > > > The user needs to be member of the group root that's all. Now I'm confused.... didn't we decide to use the group "wheel" ?? Heiko |
|
From: Diego T. <dt...@co...> - 2003-11-16 23:48:26
|
On Sun, Nov 16, 2003 at 05:17:48PM -0500, Heiko Zuerker wrote: > >yes, it's working now.... > > > >btw.- could someone explain me why su can't be executed by anyone? how i'm > >supposed to go to root when doing a ssh? > > > The user needs to be member of the group root that's all. > > Now I'm confused.... didn't we decide to use the group "wheel" ?? yes, something about that was talked. but, were is the documentation for that? :) the solution (adding the user to the root group) was the first thing that came to my mind :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-11-17 00:11:44
|
Diego Torres wrote: >On Sun, Nov 16, 2003 at 05:17:48PM -0500, Heiko Zuerker wrote: > > >>>yes, it's working now.... >>> >>>btw.- could someone explain me why su can't be executed by anyone? how i'm >>>supposed to go to root when doing a ssh? >>> >>> >>> >>The user needs to be member of the group root that's all. >> >>Now I'm confused.... didn't we decide to use the group "wheel" ?? >> >> > >yes, something about that was talked. but, were is the documentation for that? :) > >the solution (adding the user to the root group) was the first thing that came to my mind :) > > I'll changed the group to wheel right now.... Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-11-17 00:27:40
|
Heiko Zuerker wrote: > Diego Torres wrote: > >> On Sun, Nov 16, 2003 at 05:17:48PM -0500, Heiko Zuerker wrote: >> >> >>>> yes, it's working now.... >>>> >>>> btw.- could someone explain me why su can't be executed by anyone? >>>> how i'm supposed to go to root when doing a ssh? >>>> >>>> >>> >>> The user needs to be member of the group root that's all. >>> >>> Now I'm confused.... didn't we decide to use the group "wheel" ?? >>> >> >> >> yes, something about that was talked. but, were is the documentation >> for that? :) >> >> the solution (adding the user to the root group) was the first thing >> that came to my mind :) >> >> > I'll changed the group to wheel right now.... > It was already in 1.0, but it seems I forgott to do it in 1.1. That's done now. Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-11-09 16:16:15
|
Bruce Smith wrote: >>>Does save-config work OK if the pendrive is zisofs? >>> >>> >>> >>It should. >> >> > >I don't know anything about "zisofs", but if it's anything like >ISO9660 (the standard for CDROM's), then there may be a problem. >You can't write to ISO9660 filesystems, no matter if they are >on read-write media or not. > >If that's the case, then the pendrive would have to be partitioned >with a second non-zisofs partition to save the config to. > > That was something I actually forgott to mention: The read-only mounted (z)isofs is actually a benefit, since nobody can modify the files (just like on the CD). This means now it's less of a problem using a CF card, which has no write protect switch. >>I can't test it today, since a friend is picking me up soon. >>Remind me tomorrow, to check it. >> >> > >Consider this your reminder! :-) > > save-config works just fine. cya Heiko |
|
From: Diego T. <dt...@co...> - 2003-11-09 02:12:16
|
On Sat, Nov 08, 2003 at 04:23:40PM -0500, Heiko Zuerker wrote: > we can now use i.e. 256 MB PenDrives for the full DL and still have a > lot of free space left. kisses :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
