Hi mika,
Perhaps related to the earlier bootparams issue, I get this after creating scripts/grml.sh on a usb memory stick and booting with the 'scripts' option:
* grml script found on CD, executing /cdrom/scripts/*. config_cdrom_scripts:.:4: no such file or directory: /cdrom/scripts/*
and the script doesn't execute. Not sure if this is deprecated or not, as you described /cdrom as the 'old directory layout' in issue414.
Thanks again.
* Jon iroquoi@gmail.com [20080218 15:32]:
Perhaps related to the earlier bootparams issue, I get this after creating scripts/grml.sh on a usb memory stick and booting with the 'scripts' option:
- grml script found on CD, executing /cdrom/scripts/*.
config_cdrom_scripts:.:4: no such file or directory: /cdrom/scripts/*
and the script doesn't execute. Not sure if this is deprecated or not, as you described /cdrom as the 'old directory layout' in issue414.
This should be fixed with upload of grml-autoconfig (0.8.4) as well. Thanks for reporting.
regards, -mika-
* Jon iroquoi@gmail.com [20080218 16:26]:
On Mon, Feb 18, 2008 at 04:02:51PM +0100, Michael Prokop wrote:
This should be fixed with upload of grml-autoconfig (0.8.4) as well.
Great. What is the best way to get/test such updates? Spin a new iso with grml-live?
We are busy testing rc5 of grml¹ in those minutes. If you want I can build an ISO for you which contains the above package. Either visit #grml on IRC for more information or I'll drop you a mail as soon as the ISO is available. Of course spinning a new ISO using grml-live is an option as well, though unstable isn't fun in those days.²
¹ You might ask: rc5, what? Isn't rc1 the most current release?! Well, it's an "half-official" build, everyone is welcome to test it, though you have to grab it from http://debian.netcologne.de/www.grml.org/devel/ as it's not on the (other) official mirrors available.
² And that's why I'm pretty happy that our release process using grml-live works so great: we have our reference chroot and when we have the feature freeze for a new stable release we just don't build ISOs from scratch anymore. Instead we use the update/buildonly feature of grml-live using the existing chroots which receive only manually selected updates. Making unstable stable. Rocking, ey? :)
regards, -mika-
* Michael Prokop mika@grml.org [20080218 16:38]:
- Jon iroquoi@gmail.com [20080218 16:26]:
Great. What is the best way to get/test such updates? Spin a new iso with grml-live?
We are busy testing rc5 of grml¹ in those minutes. If you want I can build an ISO for you which contains the above package.
Alright Jon, there we go:
http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso.md5 http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso.md5.as...
Please let me know whether it works for you.
regards, -mika-
On Mon, Feb 18, 2008 at 05:04:49PM +0100, Michael Prokop wrote:
Alright Jon, there we go:
http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso.md5 http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso.md5.as...
Please let me know whether it works for you.
Thanks a lot!
The ISO boots fine as a CD, but doesn't boot once copied to USB in the same manner as before. This is printed at the boot splash screen:
boot: Could not find kernel image: /boot/grmlmedium/linux26
* Jon iroquoi@gmail.com [20080218 22:20]:
On Mon, Feb 18, 2008 at 05:04:49PM +0100, Michael Prokop wrote:
Alright Jon, there we go:
http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso.md5 http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso.md5.as...
Please let me know whether it works for you.
Thanks a lot!
The ISO boots fine as a CD, but doesn't boot once copied to USB in the same manner as before. This is printed at the boot splash screen:
boot: Could not find kernel image: /boot/grmlmedium/linux26
What method did you use for preparing the usb device? Manually or using grml2usb? Does the directory boot/grmlmedium on your usb device exist?
JFYI: The "Prepare system" instructions on http://wiki.grml.org/doku.php?id=usb aren't up2date in those hours because we had to rework the directory layout on grml due to a problem with syslinux. grml2usb should work though, if not it's a bug. :)
regards, -mika-
On Mon, Feb 18, 2008 at 10:53:00PM +0100, Michael Prokop wrote:
- Jon iroquoi@gmail.com [20080218 22:20]:
On Mon, Feb 18, 2008 at 05:04:49PM +0100, Michael Prokop wrote:
Alright Jon, there we go:
http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso.md5 http://debian.netcologne.de/www.grml.org/devel/grmlmedium_0.1-jon.iso.md5.as...
Please let me know whether it works for you.
Thanks a lot!
The ISO boots fine as a CD, but doesn't boot once copied to USB in the same manner as before. This is printed at the boot splash screen:
boot: Could not find kernel image: /boot/grmlmedium/linux26
What method did you use for preparing the usb device? Manually or using grml2usb? Does the directory boot/grmlmedium on your usb device exist?
I prepared it manually but boot/grmlmedium/linux26 exists.
JFYI: The "Prepare system" instructions on http://wiki.grml.org/doku.php?id=usb aren't up2date in those hours because we had to rework the directory layout on grml due to a problem with syslinux. grml2usb should work though, if not it's a bug. :)
Well, I formatted the partition and tried grml2usb but still get the same error. :-)
* Jon iroquoi@gmail.com [20080218 23:18]:
On Mon, Feb 18, 2008 at 10:53:00PM +0100, Michael Prokop wrote:
- Jon iroquoi@gmail.com [20080218 22:20]:
boot: Could not find kernel image: /boot/grmlmedium/linux26
What method did you use for preparing the usb device? Manually or using grml2usb? Does the directory boot/grmlmedium on your usb device exist?
I prepared it manually but boot/grmlmedium/linux26 exists.
Ok.
JFYI: The "Prepare system" instructions on http://wiki.grml.org/doku.php?id=usb aren't up2date in those hours because we had to rework the directory layout on grml due to a problem with syslinux. grml2usb should work though, if not it's a bug. :)
Well, I formatted the partition and tried grml2usb but still get the same error. :-)
Ok sorry, looks like syslinux has a problem with the /boot/... instruction.
I've to check this out on my own (I'm just running out of time). If you need a fix in the meanwhile: just move linux26 and initrd.gz from boot/grmlmedium/ to the root directory of your usb stick and replace the /boot/grmlmedium/ occurences inside your syslinux.cfg - then it should work for you.
regards, -mika-
On Mon, Feb 18, 2008 at 11:30:11PM +0100, Michael Prokop wrote:
JFYI: The "Prepare system" instructions on http://wiki.grml.org/doku.php?id=usb aren't up2date in those hours because we had to rework the directory layout on grml due to a problem with syslinux. grml2usb should work though, if not it's a bug. :)
Well, I formatted the partition and tried grml2usb but still get the same error. :-)
Ok sorry, looks like syslinux has a problem with the /boot/... instruction.
I've to check this out on my own (I'm just running out of time). If you need a fix in the meanwhile: just move linux26 and initrd.gz from boot/grmlmedium/ to the root directory of your usb stick and replace the /boot/grmlmedium/ occurences inside your syslinux.cfg - then it should work for you.
Indeed, that got it to boot.
Regarding the earlier issues - scripts/* are now being executed properly, but bootparams still aren't showing up.
There's absolutely no rush with any of this by the way. Thanks for the help.
* Jon iroquoi@gmail.com [20080219 00:06]:
On Mon, Feb 18, 2008 at 11:30:11PM +0100, Michael Prokop wrote:
I've to check this out on my own (I'm just running out of time). If you need a fix in the meanwhile: just move linux26 and initrd.gz from boot/grmlmedium/ to the root directory of your usb stick and replace the /boot/grmlmedium/ occurences inside your syslinux.cfg - then it should work for you.
Indeed, that got it to boot.
Great.
Regarding the earlier issues - scripts/* are now being executed properly, but bootparams still aren't showing up.
Hm, "toram" for example won't work because it's being executed at the wrong stage (a known limitiation), though "ssh=..." for example is expected to work.
Can you please run:
. /etc/grml/autoconfig.functions echo $CMDLINE
on the booted system and provide me output of "$CMDLINE"?
regards, -mika-
On Tue, Feb 19, 2008 at 12:14:48AM +0100, Michael Prokop wrote:
- Jon iroquoi@gmail.com [20080219 00:06]:
On Mon, Feb 18, 2008 at 11:30:11PM +0100, Michael Prokop wrote:
I've to check this out on my own (I'm just running out of time). If you need a fix in the meanwhile: just move linux26 and initrd.gz from boot/grmlmedium/ to the root directory of your usb stick and replace the /boot/grmlmedium/ occurences inside your syslinux.cfg - then it should work for you.
Indeed, that got it to boot.
Great.
Regarding the earlier issues - scripts/* are now being executed properly, but bootparams still aren't showing up.
Hm, "toram" for example won't work because it's being executed at the wrong stage (a known limitiation), though "ssh=..." for example is expected to work.
After formatting & using grml2usb I changed it to just read 'scripts'.
Can you please run:
. /etc/grml/autoconfig.functions echo $CMDLINE
Ah, it's there. I can't copy/paste from QEMU (I don't think?), but it's the APPEND line from syslinux.cfg + 'BOOT_IMAGE=linux26 scripts'.
The scripts don't run though. Booting with 'grml scripts' *does* work, and the tail of $CMDLINE is now 'scripts scripts'.
Teilnehmer (2)
-
Jon -
Michael Prokop