Re: Symbolic links to kernel image files and initial RAM file system image files

To: debian-kernel@lists.debian.org
Subject: Re: Symbolic links to kernel image files and initial RAM file system image files
From: Bdale Garbee <bdale@gag.com>
Date: Sat, 23 Jul 2011 17:16:23 +0200
Message-id: <[🔎] 874o2djad4.fsf@gag.com>
In-reply-to: <[🔎] 1702198171.779349.1311119811090.JavaMail.root@md01.wow.synacor.com>

> o  Eliminate symbolic links entirely and require boot loader hook
> scripts to edit their configuration files

As much as I would like to support this, what about embedded systems
where the bootloader is in flash and does not have a configuration file
in the root filesystem at all?  Right now, it is common to depend on
symlinks in such a situation to avoid forcing the user to have to
manually update the flash config.

I'm working today on an armel-based FreedomBox target using u-boot in flash.

Bdale

Attachment: pgpVkUOFK68W9.pgp
Description: PGP signature

Reply to:

Follow-Ups:
- Re: Symbolic links to kernel image files and initial RAM file system image files
  - From: Ben Hutchings <ben@decadent.org.uk>

References:
- Symbolic links to kernel image files and initial RAM file system image files
  - From: Stephen Powell <zlinuxman@wowway.com>

Prev by Date: Uploading linux-2.6 (3.0.0-1)
Next by Date: Re: Symbolic links to kernel image files and initial RAM file system image files
Previous by thread: Re: Symbolic links to kernel image files and initial RAM file system image files
Next by thread: Re: Symbolic links to kernel image files and initial RAM file system image files
Index(es):
- Date
- Thread