[1233] in netbsd-help mailing list archive
Re: ALPHA TESTERS: Autoupdate release
daemon@ATHENA.MIT.EDU (Nathan J. Williams)
Sun Apr 12 02:36:47 1998
To: Jacob B Schwartz <quark@MIT.EDU>
Cc: netbsd-help@MIT.EDU
From: "Nathan J. Williams" <nathanw@MIT.EDU>
In-Reply-To: Your message of "Sun, 12 Apr 1998 00:59:50 EDT."
<199804120459.AAA14907@spleen.mit.edu>
Date: Sun, 12 Apr 1998 02:36:38 EDT
[Whoops. One emacs keystroke too many on that last one.]
> This is pretty cool, except I have a custom kernel. What should I do?
> Do I need to relink /usr/src to a new place so I can build a kernel
> for 1.3.1? And will my 1.3 config file work, or will I need to update
> that too?
The update system does have a mechanisim for dealing with
custom kernels. If you make a file /netbsd.custom (probably a link to
your /netbsd) the update will not replace the kernel. However, when an
OS update happens, a kernel upgrade is often necessary to keep
programs from breaking. Hence, when a OS upgrade is taking place, the
update system won't proceed if there is a custom kernel in
place... unless you create a /netbsd.custom.update kernel for it to
move into place during the update process.
In short, you'll want to link your kernel to netbsd.custom,
and put your 1.3.1 kernel in /netbsd.custom.update.
You'll need to use a 1.3.1 source tree, which you can find at
/afs/dev/project/sipb/netbsd/1.3.1/src/sys (very close to where the
1.3 sources were). The same config file should be fine; none of the
changes from 1.3 to 1.3.1 were major enough to warrant config file
adjustments.
> Oh, wait, the update should have already happened, right? I don't
> see anything in /var/log/messages to indicate that anything did,
> and I have AUTOUPDATE set to true.
If you have run mkserv (probably as "mkserv remote"), it
didn't happen, because of a bug that was discovered today. You need to
run "ln -s /srvd/bin/athena/attach /bin/athena/attachandrun" to keep
the update from failing very early on and rescheduling itself
indefinitely.
- Nathan
