Messages in this thread |  | | From | (H. Peter Anvin) | Subject | Re: Can CONFIG_MAX_16M be removed? | Date | 25 Sep 1996 23:55:41 GMT |
| |
Followup to: <Pine.LNX.3.91.960924021403.4269E-100000@neuromancer.pixel.co.il> By author: Paolo Supino <paolo@neuromancer.pixel.co.il> In newsgroup: linux.dev.kernel > > On Fri, 20 Sep 1996, Andrew E. Mileski wrote: > > > > Since we have the "mem=" command line option to overrride the amount > > > of memory used, is the CONFIG_MAX_16M option necessary anymore? It > > > would seem to me that CONFIG_MAX_16M just causes confusion to new > > > Linux users. > > > > I'd rather see an option for compiling in the max memory, as some people > > boot linux directly and can't pass anything. This is real simple to add > > too - I'll even do it if necessary. > > > Don't remove the option. I have an old 386 that uses this setting and > I'd really like to be able to upgrade kernels in the future. >
You can get the same effect by using the "mem=16M" option. If you want to boot from a floppy, you can use the SYSLINUX boot loader to allow you to pass options.
-hpa -- Not speaking for Transmeta in any shape, way, or form.
|  |