Remote upgrade from 3.4-STABLE to 4.0
I am already running 4.0-CURRENT on machines to which I have
access, and have been doing for some time. It's great stuff,
of course [!].
However, I have one machine (which is at the other end of
a few hours of driving involving the New Jersey Turnpike,
which is not my idea of fun) running 3.4-STABLE. I update
it every so often via SSH, and everything is fine.
In reading UPDATING (and -current), I can't see any way to upgrade
from 3.4-STABLE to (the future) 4.0-STABLE. This is fair enough,
it being a major revision upgrade (can't see an easy way to
upgrade {AIX,Solaris,HPUX} through a major revision without access
to the console...), but in an effort to save several hour drive,
I figured I'd ask if anyone had had any success doing an upgrade
remotely...
So... anyone done it?
Best;
inw
--
Ian Whalley
first name @ last name . org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Anyone using mars_nwe with -CURRENT ?
I ask because I'm not having much luck getting it to work! I followed the instructions in README.FREEBSD, and none of the machines on my network can see the fake netware server. My requirement, incidentally, is to have a networking client, for DOS, that will fit on a boot floppy. The server is FreeBSD. I tried the LANMAN client (which I have used successfully in the past) for DOS, and it work, and it does connect to the Samba shares on the FreeBSD machine, but it's amazingly slow. That is the DOS LANMAN drivers' fault, because Samba is fine with Windows clients. I have previously used mars_nwe on Linux to accomplish precisely the same thing, and it worked great. Now my home server is FreeBSD, and I want to do the same thing again. Any advice? Best; inw -- Ian Whalley first name @ last name . org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone using mars_nwe with -CURRENT ?
I ask because I'm not having much luck getting it to work! I followed the instructions in README.FREEBSD, and none of the machines on my network can see the fake netware server. After some experimentation and playing around with debug options on IPXrouted and mars_nwe, it turns out that it's only nearest server discovery that doesn't want to work (in spite of mars_nwe being configured to respond to nearest server broadcasts). If I specify the preferred server for the DOS clients, it all works. Normal service is resumed. Best; inw -- Ian Whalley first name @ last name . org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with the latest changes to ifconfig (I guess) - Bad guess...
[Niels Chr. Bank-Pedersen wrote:] After the recent changes to ifconfig and the xl driver I am getting a panic when rc.network runs ifconfig: Anybody else seeing this, or should I look somewhere else alltogether? I am seeing exactly the same breakage -- cvsup as of today, mid-evening EDT. This is the first -current build I've done since if_xl was converted to miibus. My card is identified as 3Com 3c905B-TX Fast Etherlink XL. Best; inw -- Ian Whalley first name @ last name . org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
