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

Bug#388591: nobootloader: [powerpc]



On Thu, Sep 21, 2006 at 02:54:34PM +0200, Frans Pop wrote:
> On Thursday 21 September 2006 13:55, Sven Luther wrote:
> > The attached patch clarifies the wording of the nobootloader
> > chrp_pegasos case, in order to adapt to future non-pegasos Genesi
> > models.
> 
> I have one comment on the patch. As the templates are now worded, I see no 
> reason why "Firmware" should have a capital as it is no longer a name, 
> but just a generic term.
> So I would suggest to s/Firmware/firmware/ in the new strings.
> 
> Is that OK with you?

Let me check, ..., yes, fine with me, this makes more sense as this,
OpenFirmware used to be capitalized, since it is trademark or something.

The other point, i was told that we should capitalize Linux, because it is a
trademarked word :

  Some variables need to be set in the Genesi Firmware in order for your
  system to boot linux automatically.

Also, we speak about system in the next sentence :

  At the end of the installation, the system will reboot.

And finally : 

  Alternatively, you will be able to boot the kernel manually by entering :

This is confusing and maybe problematic. We should maybe change the first to
the "linux kernel", and maybe drop the kernel in the last sentence ? Or maybe
drop linux everywhere and just use boot ? 

Something like this ? 

 Some variables need to be set in the Genesi firmware in order for your
 system to boot automatically.  At the end of the installation, the
 system will reboot.  At the firmware prompt, set the following firmware
 variables to enable auto-booting:
 .
  setenv boot-device ${OF_BOOT_DEVICE}
  setenv boot-file ${OF_BOOT_FILE}
  setenv auto-boot-timeout 5000
  setenv auto-boot? true
 .
 You will only need to do this once.  Afterwards, enter the "boot" command
 or reboot the system to proceed to the next installation stage.
 .
 Alternatively, you will be able to boot manually by entering :
 .
  ${KERNEL_BOOT}
 .
 at the firmware prompt.

Friendly,

Sven Luther



Reply to: