#271180 aboot ought to ignore single digit options in favour of built-in args

Package:
aboot
Source:
aboot
Submitter:
Date:
2017-12-07 22:33:04 UTC
Severity:
wishlist
#271180#5
Date:
2004-09-11 18:40:15 UTC
From:
To:
the example output provided by netabootwrap suggests passing kernel
arguments with the -a option:

Following shows options and default values or example value
netabootwrap -t netboot.img -k vmlinux.gz -i initrd.gz -a "root=/dev/hda1 single"

i generated an image with:

netabootwrap -t vmlinuz.nb -k vmlinuz -i initrd.img -a "ip=dhcp root=/dev/nfs ro console=ttyS0,9600"

when attempting to netboot the generated image from the SRM prompt, i
get the following:
(boot ewa0.0.0.8.0 -file alpha-root/boot/vmlinuz.nb -flags 0)

Trying BOOTP boot.

Broadcasting BOOTP Request...
Switching network ewa0.0.0.8.0 from Thin Wire to Twisted Pair...
.local inet address: 10.3.3.204
remote inet address: 10.3.3.9
TFTP Read File Name: alpha-root/boot/vmlinuz.nb
...................................................................................................................................................................................
bootstrap code read in
base = 166000, image_start = 0, image_bytes = 78ca00
initializing HWRPB at 2000
initializing page table at 158000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
aboot: Linux/Alpha SRM bootloader version 0.9b
aboot: switching to OSF/1 PALcode version 1.35
aboot: loading initrd (6619136 bytes/12928 blocks) at 0xfffffc00038c6000
aboot: starting kernel network with arguments 0

and i get nothing...

it works fine if i manually specify the options from the bootprompt,
like this:

so i don't know if this is a really bug in netabootwrap or if there is a
SRM command to use the options specified by netabootwrap?

thanks.

live well,
  vagrant
#271180#10
Date:
2004-09-13 00:41:55 UTC
From:
To:
                                                      ^^^^^^^^

Yes, your SRM config is overriding the built-in OS args with "0".

You want

 >>>boot ewa0 -fl ""

to keep the options included in the image.
#271180#15
Date:
2004-09-14 22:11:44 UTC
From:
To:
thanks.  that worked great.

maybe this could find it's way into debian's aboot documentation
somehow?

live well,
  vagrant
#271180#20
Date:
2004-09-14 22:31:07 UTC
From:
To:
I believe aboot ought to be able to handle the special case where
os_flags is set to a single digit and ignore it in favor of the built-in
args, equivalent to its ability to map single-digit flags to aboot.conf
entries.
#271180#25
Date:
2004-09-15 15:52:10 UTC
From:
To:
retitle 271180 aboot ought to ignore single digit options in favour of built-in args
severity 271180 wishlist
thanks

I informed upstream to include netabootwrap. Once that is happening,
I'll see to get aboot to behave "as expected". But this is definitly
post-sarge.

Greetings

          Helge
#271180#34
Date:
2005-04-18 10:19:39 UTC
From:
To:
It's more subtle then that. aboot treats the contents of booted_osflags
differently depending on how it was loaded. When netbooting the contents
is passed as kernel parameter, except if it is a single 'i', which
causes it to ask for the kernel commandline on the console. When booting
from disk or cdrom, the contents is used by aboot to select the
aboot.conf entry to boot. (it's somewhat more complicated then what I
describe here, look at get_aboot_options in disk.c for full details). A
good solution might be to make netboot behaviour similar to disk boot
behaviour by including a single entry aboot.conf in the netboot image.

Cheers,

Peter (p2).