| 1 |
Christophe PEREZ wrote: |
| 2 |
> Le Sat, 25 Jun 2005 18:13:09 -0700, Zac Medico a écrit : |
| 3 |
> |
| 4 |
> |
| 5 |
>>The rootdelay parameter should work (use a 5 or 10 second delay) |
| 6 |
> |
| 7 |
> |
| 8 |
> I use it, it works. |
| 9 |
> |
| 10 |
> |
| 11 |
>>with |
| 12 |
>>root=/dev/sda1 (no initrd) and statically linked usb drivers. |
| 13 |
> |
| 14 |
> |
| 15 |
> It woudl'nt be the same system as the iso at all. |
| 16 |
> I wanted exactly the same, but on a usb key. |
| 17 |
> |
| 18 |
> |
| 19 |
>>If the |
| 20 |
>>usb drivers are modular then you need to have a delay inside linuxrc |
| 21 |
>>between the modules loading and udevstart (again, sleep 5 or 10 should |
| 22 |
>>do it). A parameter like "scandelay" is useful for tuning this. |
| 23 |
>> |
| 24 |
>>Note that if you get the 'Please specify a device to boot, or "shell" |
| 25 |
>>for a shell...' message then you can choose shell, run udevstart, exit, |
| 26 |
> |
| 27 |
> |
| 28 |
> I didn't need anything, just launch /dev/ram0. udevstart doesn't create |
| 29 |
> any /dev/sd* for me. |
| 30 |
> |
| 31 |
|
| 32 |
Are the usb drivers modular? In any case, udevstart should work if the usb drivers have had time to initialize and create /sys entries. I think you need to add a delay somewhere (I boot from a usb hard disk and udev works fine for me). |
| 33 |
|
| 34 |
> |
| 35 |
>>and try to specify your root device again. There is a loop there inside |
| 36 |
>>linuxrc that helps for troubleshooting. |
| 37 |
> |
| 38 |
> |
| 39 |
> I saw that. |
| 40 |
> |
| 41 |
> |
| 42 |
>>You should see your block |
| 43 |
>>device inside /sys/block if it has been detected properly. |
| 44 |
> |
| 45 |
> |
| 46 |
> now, it is, because of my "mknod". |
| 47 |
> |
| 48 |
|
| 49 |
Also, maybe it's better not to assume that /dev/sda1 will be assigned to your usb drive (the may be other usb devices connected). There is a feature request that will allow you to specify a partition label or uuid instead of a specific device. |
| 50 |
|
| 51 |
http://bugs.gentoo.org/show_bug.cgi?id=83771 |
| 52 |
|
| 53 |
> All is fine now, but I wanted to show that it is not so simple as said... |
| 54 |
> |
| 55 |
> I put the img there : |
| 56 |
> http://www.madinux.org/download/install-x86-minimal-2005.0_usb_64m.img.bz2 |
| 57 |
> |
| 58 |
> It's for a 64Mb key. |
| 59 |
> |
| 60 |
> I'll try now to understand how I can use catalyst to personnalize it. |
| 61 |
> |
| 62 |
> Something great would be to have exactly the template for the original iso. |
| 63 |
> I tried to do one, but my iso is 116Mb, not 50. I don't understand why. |
| 64 |
> |
| 65 |
|
| 66 |
Maybe you can use the "du" command to compare your space usage and pinpoint the cause. |
| 67 |
|
| 68 |
Zac |
| 69 |
-- |
| 70 |
gentoo-catalyst@g.o mailing list |
Archives