Hello,
as I already described before, my prefered solution to the problem
is the use of a kind of variables in GRUB like
$MEM, $IP, $SERVER_IP, etc, etc,...
So the user can decide himeself using kernel paramters, like
kernel /boot/vmlinuz mem=$MEM root=/dev/hda2
etc.... If there is enough information, also things like NFSROOT
and IP configuration can be setup.
These variables ('$MEM', etc..) should be usable in all builtin
command.
This varibles cannot be used to do calculations (like $MEM-20) as
we hove *NO* shell script language here. It should only do a
replacing in the command line.
Cheers
Christoph P.
Pavel Roskin wrote:
>
> Hello, Jeff!
>
> > > It's up to the kernel to decide what to do with this information.
> >
> > mem=XXX overrides the memory map provided by BIOS with a two-region
> > memory map, one region below 640k, and one region above 1MB.
> >
> > For newer machines this is -fatally- wrong. Linux must use the memory
> > map provided by BIOS, otherwise it will address regions which should not
> > be addressed. Newer laptops and server machines require utilization of
> > the BIOS e820 map.
>
> GRUB uses this call but it doesn't know how to pass this information to
> the Linux kernel.
>
> I believe that "--no-mem-option" should become default. "--mem-option"
> should be introduced instead for the kernels that still need it.
>
> A kernel that can boot from a floppy without relying on anything but a
> 16-bit BIOS can and should be trusted with the hardware detection.
>
> Regards,
> Pavel Roskin
>
> _______________________________________________
> Bug-grub mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/bug-grub
--
+--------V--------+ [EMAIL PROTECTED]
| A L C A T E L | -----------------------------
+-----------------+ Phone: +43 1 27722 3706
T A S Fax: +43 1 27722 3955
_______________________________________________
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub