On a related topic... how do you tell which of your filesystems are mounted
UFS1 -vs- UFS2? 'mount -v' just says ufs.
-Steve
- Original Message -
From: Ray Kohler [EMAIL PROTECTED]
To: Vitaly Markitantov [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, December 17, 2002 6:54 AM
Thus spake Lucky Green [EMAIL PROTECTED]:
I therefore believe that the 5.0 release represents a perfect
opportunity to remove ssh1 fallback from the default distribution of
FreeBSD and hope the FreeBSD team will consider this change.
Making SSH 2 the default is one thing. Removing SSH 1
- Original Message -
From: Terry Lambert [EMAIL PROTECTED]
So I upgrade, and I can't get back into the box from my SSH1
client machine to reenable SSH1 services on the box. Genius!
8-) 8-).
Its somewhat less than genious not to look over any new config
files you've installed to make
No update on the cpp0 error but I can get bind9 to stay running if I disable
threads in the Makefile... no more signal 6.
-Steve
New datapoint:
If I compile the kernel in the old fashion (config SB; cd ../compile/SB;
make depend all install) then the kernel compiles and installs fine.
Edit line 92 of sql/mysqld.cc:
--#ifdef __linux__
++ #ifdef __FreeBSD__
However that'll only get you past this set of errors. And then it gets
tricky and has something to do with the new C++ compiler that I haven't
quite wrapped my mind around yet.
-Steve
- Original Message -
Last night switched from 3.1 to 4.0. Smooth transition. The only
error I've seen is one of my ethernet cards is no longer detected.
In the previous kernel (3.1-STABLE) I had the following config
line:
device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000
When the system booted it would detect
device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000
You should probably show the list what device lines you are using for
current, since config barfs on the above line under current:
config: line 52: `net' interrupt label obsolete
Fair enough:
device ed1 at isa? port 0x280 irq 10
On 18-May-99 Steven Ames wrote:
Wow. I don't think that should ever happen but at this point I'll
try a lot of things :)
Tried it. didn't work.
really, isn't there a way to enable more verbose probing so that
it says 'ed0 not found at 0x280' or some such?
When I upgraded
*sigh* No suprise here. As 90% of these things are this was yet
another Dumb User Error. I had a base address conflict that kept
the card from being probed.
Thanks for everyone's help. As always FreeBSD is working just
great!
-Steve
To
