Subject: what to do with improvements?
To: None <current-users@sun-lamp.cs.berkeley.edu>
From: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
List: current-users
Date: 07/15/1994 14:40:39
I've made some changes to the kernel that I believe are improvements.
What should I do with the changes? One of them is SPARC-specific,
which I could just send to port-sparc (or maybe deraadt :-), but the
other two are changes to the diskless support, and I'm not sure what to
do with those.
If it matters, the changes are:
- "options RCONS_WONB" makes the framebuffer console come up
white-on-black rather than black-on-white.
Five lines added to arch/sparc/rcons/rcons_kern.c.
- "options NFS_BOOTSERV_GATE" makes the kernel use its boot server as
its default gateway, rather than the server-supplied gateway that the
comment claims is usually bogus. (I also discovered while doing this
that NFS_BOOT_GATEWAY will not work if turned on; I didn't fix it.)
About 30 lines added to nfs/nfs_boot.c.
- "options NFS_ROOT_OPTIONS=xxx", if defined, supplies xxx as options
in nfs_mount_diskless. In our environment, I needed NFSMNT_NOCONN
here, and it seemed cleaner to do it this way than to hardwire
NFSMNT_NOCONN into nfs_mount_diskless under control of a special
option. (Why is it necessary? The boot server is also the NFS
server, but in the bootparams exchange it returns its "remote"
address, and NFS requests go to the "remote" address, but the replies
come from the "local" address. I suppose I could have added
interface-specific names and used those in the bootparams database,
but the kernel should be configurable to tolerate this.)
Three lines added to nfs/nfs_vfsops.c.
der Mouse
mouse@collatz.mcrcim.mcgill.edu
------------------------------------------------------------------------------