Alan Cox wrote:
> Use that argument 50 times and your kernel has grown 100K. Unfortunately
> everyone keeps using the argument and forgetting the cumulative effect
:-) The thing is that this information is something you access when
something is already going wrong. So avoiding a few possible failure
conditions (e.g. determining the image name either requires a priori
knowledge or depends on the boot loader) seems rather desirable to me.
Or can we have a standard, reasonably reliable way for determining the
path name of the currently running image ? (E.g. for LILO, the command
is lilo -I `sed '/.*BOOT_IMAGE=\([^ ]*\).*/s//\1/' </proc/cmdline`
But what about GRUB, LOADLIN, SILO, MILO, ... ?)
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, ICA, EPFL, CH [EMAIL PROTECTED] /
/_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
