[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#27007: boot-parameters are not documented

From: Mathieu Othacehe
Subject: bug#27007: boot-parameters are not documented
Date: Tue, 23 May 2017 11:31:12 +0200
User-agent: mu4e 0.9.18; emacs 25.2.1


> So how does the ‘menu-entry’ example that Tomáš gave translate with this
> new API?  (Apologies for asking, I admit I haven’t fully adjusted to the
> new API mentally.  :-))

Well it's still moving :)

We can ask him but I guess something like that :

--8<---------------cut here---------------start------------->8---
  (label "openSUSE")
  (root-device #f)
  (boot-name 'grub)
  (store-device #f)
  (store-mount-point "/")
  (kernel "(hd0,msdos1)/vmlinuz")
  (kernel-arguments (list  "root=/dev/penguin/opensuse"  
  (initrd "(hd0,msdos1)/initrd"))
--8<---------------cut here---------------end--------------->8---

Note that root-device, boot-name, store-device and store-mount-point are
useless here.

> Sounds good in general, as long as we have default values that make
> sense.


> Can we assume that all the bootloaders have a notion of “menu” and “menu
> entries”?  Or do you think that very notion is not shared by all of
> them?

We can suppose that it's always possible to add custom entries to
generated bootloader configuration. That would allow someone switching
from grub to extlinux to keep his custom entries.

> Sure; having the implementations in (gnu bootloader xyz) follow the same
> model sounds like a good idea.

Ok !



reply via email to

[Prev in Thread] Current Thread [Next in Thread]