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
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,
* 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.
* T o n g mlist4sunt...@yahoo.com [Wed Jul 21, 2010 at 03:56:24PM +]:
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
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
* 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