From: Roland P. <pa...@ta...> - 2004-01-31 03:41:11
|
Hi, I'm currently coding the option to preselect the boot options (I prefer 1024x768, not text) and adding user-defined options to the boot loader. In the /build/scripts/build-iso script, there is this passage which writes the loader configs and the first two entries read (that's line 250) prompt 1 label 0 kernel /boot/vmlinuz append root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc ramdisk=8096 label 1 kernel /boot/vmlinuz append root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc ramdisk_blocksize=4096 vga=769 the other labels look like "label 1". Shouldn't this read all the same except for the vga option? Is ramdisk_blocksize an error (should be ramdisk)? And I guess 8096 should read 4096... thanks, Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
From: Heiko Z. <he...@zu...> - 2004-01-31 15:26:21
|
Roland Pabel wrote: > Hi, > I'm currently coding the option to preselect the boot options (I prefer > 1024x768, not text) and adding user-defined options to the boot loader. > In the /build/scripts/build-iso script, there is this passage which writes the > loader configs and the first two entries read (that's line 250) > > prompt 1 > label 0 > kernel /boot/vmlinuz > append root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc ramdisk=8096 > label 1 > kernel /boot/vmlinuz > append root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc > ramdisk_blocksize=4096 vga=769 > > the other labels look like "label 1". Shouldn't this read all the same except > for the vga option? Is ramdisk_blocksize an error (should be ramdisk)? > And I guess 8096 should read 4096... You are absolutely correct, this was a bug. Update from CVS and you'll get the fixed version. Hey I get an idea! Why don't you modify it so, that you can select the default resolution via menuconfig ? And of course send us the patch then.... ;-) Heiko |
From: Roland P. <pa...@ta...> - 2004-01-31 18:32:24
|
On Saturday 31 January 2004 16:22, Heiko Zuerker wrote: > Roland Pabel wrote: > > Hi, > > I'm currently coding the option to preselect the boot options (I prefer > > 1024x768, not text) and adding user-defined options to the boot loader. > > In the /build/scripts/build-iso script, there is this passage which > > writes the loader configs and the first two entries read (that's line > > 250) > > > > prompt 1 > > label 0 > > kernel /boot/vmlinuz > > append root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc ramdisk=8096 > > label 1 > > kernel /boot/vmlinuz > > append root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc > > ramdisk_blocksize=4096 vga=769 > > > > the other labels look like "label 1". Shouldn't this read all the same > > except for the vga option? Is ramdisk_blocksize an error (should be > > ramdisk)? And I guess 8096 should read 4096... > > You are absolutely correct, this was a bug. Update from CVS and you'll > get the fixed version. > > Hey I get an idea! Why don't you modify it so, that you can select the > default resolution via menuconfig ? And of course send us the patch > then.... ;-) Well, that is actually what I'm doing...(I hope that was no sarcasm ;) The resolution selection part is already done, but I'm having some problems with the "enter a text" part: I can't find a way to transparently write "text" as the first word into .result with the current scripts. You solved this for lists by returning "listsel x" for a selected item, but "lxdialog --inputbox" doesn't support that (at least I think so, can't find much documentation about it) Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
From: Heiko Z. <he...@zu...> - 2004-01-31 19:56:24
|
Roland Pabel wrote: > On Saturday 31 January 2004 16:22, Heiko Zuerker wrote: > >>Roland Pabel wrote: >> >>>Hi, >>>I'm currently coding the option to preselect the boot options (I prefer >>>1024x768, not text) and adding user-defined options to the boot loader. >>>In the /build/scripts/build-iso script, there is this passage which >>>writes the loader configs and the first two entries read (that's line >>>250) >>> >>>prompt 1 >>>label 0 >>>kernel /boot/vmlinuz >>>append root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc ramdisk=8096 >>>label 1 >>>kernel /boot/vmlinuz >>>append root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc >>>ramdisk_blocksize=4096 vga=769 >>> >>>the other labels look like "label 1". Shouldn't this read all the same >>>except for the vga option? Is ramdisk_blocksize an error (should be >>>ramdisk)? And I guess 8096 should read 4096... >> >>You are absolutely correct, this was a bug. Update from CVS and you'll >>get the fixed version. >> >>Hey I get an idea! Why don't you modify it so, that you can select the >>default resolution via menuconfig ? And of course send us the patch >>then.... ;-) > > Well, that is actually what I'm doing...(I hope that was no sarcasm ;) Cool. :-)) > The resolution selection part is already done, but I'm having some problems > with the "enter a text" part: > I can't find a way to transparently write "text" as the first word into > .result with the current scripts. You solved this for lists by returning > "listsel x" for a selected item, but "lxdialog --inputbox" doesn't support > that (at least I think so, can't find much documentation about it) > Roland Why don't you just make it a listsel ? 0 text mode 80x25 1 640x480 VESA 2 800x600 VESA and so on. In the build-iso file, then just "cut" it. This "should" work (of course no promise ;-) ) Heiko |
From: Roland P. <pa...@ta...> - 2004-02-01 21:11:55
Attachments:
boot_options.diff
|
> Why don't you just make it a listsel ? > 0 text mode 80x25 > 1 640x480 VESA > 2 800x600 VESA > and so on. > > In the build-iso file, then just "cut" it. > > This "should" work (of course no promise ;-) ) Ok, here is the patch. works for me ( no promise ;-) ) Checked out CVS minutes ago, but the ramdisk part was still not fixed (cvs problems?!) According to linux/Documentation/ramdisk.txt "ramdisk=<size>" is obsolete, so I changed it to "ramdisk_size=<size>" Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
From: Friedrich L. <fl...@fl...> - 2004-02-01 21:50:59
|
Roland Pabel wrote on 01.02.2004 22:11 MET: > Checked out CVS minutes ago, but the ramdisk part was still not fixed (cvs > problems?!) The public CVS is as it seems currently at least some days behind the project CVS server. See http://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1 -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
From: Heiko Z. <he...@zu...> - 2004-02-01 22:06:20
Attachments:
build-iso
|
Friedrich Lobenstock wrote: > Roland Pabel wrote on 01.02.2004 22:11 MET: > >> Checked out CVS minutes ago, but the ramdisk part was still not fixed >> (cvs problems?!) > > > The public CVS is as it seems currently at least some days behind the > project CVS server. > > See http://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1 > It looks like, the anonymous CVS is even older... You patch doesn't apply, I added you the current build-iso file, please create the patch against this one. Heiko |
From: Roland P. <pa...@ta...> - 2004-02-01 22:47:09
Attachments:
boot_options.diff
|
> It looks like, the anonymous CVS is even older... > You patch doesn't apply, I added you the current build-iso file, please > create the patch against this one. done, Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
From: Friedrich L. <fl...@fl...> - 2004-02-01 22:53:53
|
Roland Pabel wrote on 01.02.2004 23:47 MET: >>It looks like, the anonymous CVS is even older... >>You patch doesn't apply, I added you the current build-iso file, please >>create the patch against this one. > > done, Can this possibly be added to the "custom-cd" script so everybody can have this option without need to recompile the whole thing? -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
From: Roland P. <pa...@ta...> - 2004-02-01 23:09:00
|
On Sunday 01 February 2004 23:53, Friedrich Lobenstock wrote: > Roland Pabel wrote on 01.02.2004 23:47 MET: > Can this possibly be added to the "custom-cd" script so everybody > can have this option without need to recompile the whole thing? Unless you have made major changes in CVS to the custom-cd script, it doesn't use dialogs. I guess the easiest way would be to add a few lines which utilize sed and grep to modify the "default x" flag in isolinux.cfg and not touch the ramdisk-type configs. I could try to write that tomorrow, if that would suffice... Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
From: Friedrich L. <fl...@fl...> - 2004-02-01 23:20:11
|
Roland Pabel wrote on 02.02.2004 00:08 MET: > On Sunday 01 February 2004 23:53, Friedrich Lobenstock wrote: > >>Roland Pabel wrote on 01.02.2004 23:47 MET: > > >>Can this possibly be added to the "custom-cd" script so everybody >>can have this option without need to recompile the whole thing? > > > Unless you have made major changes in CVS to the custom-cd script, it doesn't > use dialogs. I guess the easiest way would be to add a few lines which > utilize sed and grep to modify the "default x" flag in isolinux.cfg and not > touch the ramdisk-type configs. I could try to write that tomorrow, if that > would suffice... Anyway better than not being able to change the screen settings as a "normal" user. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
From: Heiko Z. <he...@zu...> - 2004-02-01 23:31:17
|
Roland Pabel wrote: > On Sunday 01 February 2004 23:53, Friedrich Lobenstock wrote: > >>Roland Pabel wrote on 01.02.2004 23:47 MET: > > >>Can this possibly be added to the "custom-cd" script so everybody >>can have this option without need to recompile the whole thing? > > > Unless you have made major changes in CVS to the custom-cd script, it doesn't > use dialogs. I guess the easiest way would be to add a few lines which > utilize sed and grep to modify the "default x" flag in isolinux.cfg and not > touch the ramdisk-type configs. I could try to write that tomorrow, if that > would suffice... I'm not sure if we should add this selection to the custom-cd script. If somebody wants to change the default resolution, he/she only has to inject a new isolinux.cfg via the script. just my 2 cents Heiko |
From: Friedrich L. <fl...@fl...> - 2004-02-01 23:37:23
|
Heiko Zuerker wrote on 02.02.2004 00:27 MET: > Roland Pabel wrote: > >> On Sunday 01 February 2004 23:53, Friedrich Lobenstock wrote: >> >>> Roland Pabel wrote on 01.02.2004 23:47 MET: >> >> >> >>> Can this possibly be added to the "custom-cd" script so everybody >>> can have this option without need to recompile the whole thing? >> >> >> >> Unless you have made major changes in CVS to the custom-cd script, it >> doesn't use dialogs. I guess the easiest way would be to add a few >> lines which utilize sed and grep to modify the "default x" flag in >> isolinux.cfg and not touch the ramdisk-type configs. I could try to >> write that tomorrow, if that would suffice... > > > I'm not sure if we should add this selection to the custom-cd script. > > If somebody wants to change the default resolution, he/she only has to > inject a new isolinux.cfg via the script. Yes, *_only_* (double underlined and extra bold). > just my 2 cents just my 2 öre ;-) -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
From: Heiko Z. <he...@zu...> - 2004-02-01 23:46:22
|
Friedrich Lobenstock wrote: > Heiko Zuerker wrote on 02.02.2004 00:27 MET: > >> Roland Pabel wrote: >> >>> On Sunday 01 February 2004 23:53, Friedrich Lobenstock wrote: >>> >>>> Roland Pabel wrote on 01.02.2004 23:47 MET: >>> >>> >>> >>> >>>> Can this possibly be added to the "custom-cd" script so everybody >>>> can have this option without need to recompile the whole thing? >>> >>> >>> >>> >>> Unless you have made major changes in CVS to the custom-cd script, it >>> doesn't use dialogs. I guess the easiest way would be to add a few >>> lines which utilize sed and grep to modify the "default x" flag in >>> isolinux.cfg and not touch the ramdisk-type configs. I could try to >>> write that tomorrow, if that would suffice... >> >> >> >> I'm not sure if we should add this selection to the custom-cd script. >> >> If somebody wants to change the default resolution, he/she only has to >> inject a new isolinux.cfg via the script. > > > Yes, *_only_* (double underlined and extra bold). Point taken. ;-) Heiko |
From: Heiko Z. <he...@zu...> - 2004-02-01 23:36:17
|
Roland Pabel wrote: >>It looks like, the anonymous CVS is even older... >>You patch doesn't apply, I added you the current build-iso file, please >>create the patch against this one. OK I added it, thanks for the contribution ! > + append root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc $BOOT_OPTION_RAMDISK vga=${BOOT_OPTIONS_MODE[$i]} The variable name was wrong, I had to change it to BOOT_OPTIONS_KERNEL_MODE cu Heiko |
From: Roland P. <pa...@ta...> - 2004-02-01 23:52:10
|
On Monday 02 February 2004 00:33, Heiko Zuerker wrote: > Roland Pabel wrote: > >>It looks like, the anonymous CVS is even older... > >>You patch doesn't apply, I added you the current build-iso file, please > >>create the patch against this one. > > OK I added it, thanks for the contribution ! > > > + append root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc > > $BOOT_OPTION_RAMDISK vga=${BOOT_OPTIONS_MODE[$i]} > > The variable name was wrong, I had to change it to BOOT_OPTIONS_KERNEL_MODE oh yes, overlooked it ( one of those late last-minute variable-renames that went wrong) -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |