Hi,
Can somebody explain the newly introduced bootid option?
I know,
bootid is used "for verifying the ISO through bootid=.... bootoption" and the logic behind bootoptions and possible combinations:
* bootid.txt + wrong bootid=... => fails to boot * bootid.txt + right bootid=... => boots * bootid.txt + ignore_bootid => boots * bootid.txt + no bootid=... + no ignore_bootid => fails to boot * no bootid.txt + no bootid=... + no ignore_bootid => boots * no bootid.txt + bootid=... => fails to boot * no bootid.txt + ignore_bootid=... => boots
I mean to ask,
- what exactly does the bootid stand for? - how does the file /conf/bootid.txt generated? - how would bootid work with integrating multiple-grml on the same USB?
Is there somewhere to read more about it?
Thanks
* T o n g wrote [13.06.10 18:50]: Hi,
I mean to ask,
- what exactly does the bootid stand for?
An id identifying the correct boot device.
- how does the file /conf/bootid.txt generated?
grml-live, like everything else.
- how would bootid work with integrating multiple-grml on the same USB?
grml2usb takes care of it. Basically the process is: If no /conf/bootid.txt is present, generate a random id and write it to /conf/bootid.txt. Read /conf/bootid.txt and adjust the bootid parameter for every specified iso.
Is there somewhere to read more about it?
What do you want to know? IMO it is quite simple, it is an identifier to identify the system.
regards, Ulrich
On Sun, 13 Jun 2010 21:24:00 +0200, Ulrich Dangel wrote:
- how would bootid work with integrating multiple-grml on the same USB?
grml2usb takes care of it. Basically the process is: If no /conf/bootid.txt is present, generate a random id and write it to /conf/bootid.txt. Read /conf/bootid.txt and adjust the bootid parameter for every specified iso.
Thanks for the reply.
OK, if I build my own flavour of grml via grml-live, and I want to install it to the same USB key that an official flavour of grml has been installed, would it be possible?
According to the above, it seems impossible to me because there is only one /conf/bootid.txt file on the USB key and the content in mine would be different than the official one.
Is that so?
Thanks
* T o n g mlist4suntong@yahoo.com [Wed Jul 21, 2010 at 03:56:24PM +0000]:
On Sun, 13 Jun 2010 21:24:00 +0200, Ulrich Dangel wrote:
- how would bootid work with integrating multiple-grml on the same USB?
grml2usb takes care of it. Basically the process is: If no /conf/bootid.txt is present, generate a random id and write it to /conf/bootid.txt. Read /conf/bootid.txt and adjust the bootid parameter for every specified iso.
Thanks for the reply.
OK, if I build my own flavour of grml via grml-live, and I want to install it to the same USB key that an official flavour of grml has been installed, would it be possible?
According to the above, it seems impossible to me because there is only one /conf/bootid.txt file on the USB key and the content in mine would be different than the official one.
grml2usb generates the bootid for you, so it's supposed to "just work" for your own flavour of grml. If it doesn't work it's a bug.
Enjoy. :)
regards, -mika-
On Wed, 21 Jul 2010 22:11:32 +0200, Michael Prokop wrote:
- how would bootid work with integrating multiple-grml on the same
USB?
grml2usb takes care of it. Basically the process is: If no /conf/bootid.txt is present, generate a random id and write it to /conf/bootid.txt. Read /conf/bootid.txt and adjust the bootid parameter for every specified iso.
Thanks for the reply.
OK, if I build my own flavour of grml via grml-live, and I want to install it to the same USB key that an official flavour of grml has been installed, would it be possible?
According to the above, it seems impossible to me because there is only one /conf/bootid.txt file on the USB key and the content in mine would be different than the official one.
grml2usb generates the bootid for you, so it's supposed to "just work" for your own flavour of grml. If it doesn't work it's a bug.
Sorry I still don't get it.
Say when grml2usb installing grml-small and generates a bootid of grml- small-123. Then when grml2usb installing my own flavour of grml, it generates another bootid of my-own-456. Now grml-small expect that the bootid is grml-small-123, and mine being my-own-456. My understand is that only one of them can boot now. which part I've figured wrong?
Thanks
On Thursday 22 July 2010 01:04:06 T o n g wrote:
Sorry I still don't get it.
Say when grml2usb installing grml-small and generates a bootid of grml- small-123. Then when grml2usb installing my own flavour of grml, it generates another bootid of my-own-456. Now grml-small expect that the bootid is grml-small-123, and mine being my-own-456. My understand is that only one of them can boot now. which part I've figured wrong?
All flavours will be adjusted to expect bootid small-123.
To be more clear: * No bootid.txt exists on the target - generate one * read the first line of bootid.txt and use it as bootid * Adjust bootid parameter on $FLAVOUR to read bootid
Ulrich
On Thu, 22 Jul 2010 10:33:06 +0200, Ulrich Dangel wrote:
Say when grml2usb installing grml-small and generates a bootid of grml- small-123. Then when grml2usb installing my own flavour of grml, it generates another bootid of my-own-456. Now grml-small expect that the bootid is grml-small-123, and mine being my-own-456. My understand is that only one of them can boot now. which part I've figured wrong?
All flavours will be adjusted to expect bootid small-123.
To be more clear:
- No bootid.txt exists on the target - generate one * read the first
line of bootid.txt and use it as bootid * Adjust bootid parameter on $FLAVOUR to read bootid
Ok, got it. Thanks for the clarification.
Yeah, it's a nice feature that I've been looking for long time ago, so that I know exactly which one to boot if HD, USB, CD all have bootable grml images.
However, IMHO, it only goes half the way. It still isn't able to solve the problem that I want to boot two different version of grml-medium off the same device. I think a better approach is to use, say boot-signature, which is per boot folder, not per disk.
just my 2c.
* T o n g wrote [23.07.10 01:50]:
However, IMHO, it only goes half the way. It still isn't able to solve the problem that I want to boot two different version of grml-medium off the same device. I think a better approach is to use, say boot-signature, which is per boot folder, not per disk.
Yes it does not, as this solution is designed for determine the correct boot medium and has nothing to do with several versions of one flavour on one disk. It is btw. possible to do this manually without a problem.
Ulrich
participants (3)
-
Michael Prokop -
T o n g -
Ulrich Dangel