>
> Hmm, I have exactly the same situation, a mission-critical server that
> can't be taken offline to do an upgrade. It's running 3.4,
> but with a few binaries from 4.0 that I needed to make our CGIs work
> (development is done on 4.2 :).
>
Euh... Mission Critical(tm) without a backup machine? Your boss did sign the
"will not whine when it dies"--agreement, right?
Kees Jan
================================================
You are only young once,
but you can stay immature all your life.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
- Re: syscall kernel modules on 3.0-release Dag-Erling Smorgrav
- Re: syscall kernel modules on 3.0-release Matthew Luckie
- Re: syscall kernel modules on 3.0-release Dag-Erling Smorgrav
- Re: syscall kernel modules on 3.0-release Matthew Emmerton
- Re: syscall kernel modules on 3.0-rel... Dan Langille
- Re: syscall kernel modules on 3.... Matthew Emmerton
- Re: syscall kernel modules o... Dag-Erling Smorgrav
- Re: syscall kernel modules on 3.0-rel... Dan Feldman
- Re: syscall kernel modules on 3.0-rel... Julian Elischer
- Re: syscall kernel modules on 3.0-rel... Dag-Erling Smorgrav
- Koster, K.J.

