Re: Keyboard troubles
>> Why not just get a decent monitor/keyboard switch? Belkin makes a >> nice 4-port in the $200 range that makes your motherboard think >> there's a keyboard attached even if you are not currently switched >> onto the system. > >I have something quite similar.. Still, seems like some individuals >remain adamantly opposed to the idea of keyboard swapping, however >careful one is. :-) For the record,... I never said that I was against using console switch products. (They are designed to be safe. If it causes the problem, we can categorically say that it is the manufacturer's fault.) I am against hot-plugging and swapping the keyboard. You may be careful and you know the risk. But, others may not. I don't like to spread the false impression that the PC keyboard interface is designed for hot-plugging/unplugging, and will repeat (or even shout :-) as many times as necessary, "It is not recommended to attach or detach the PC keyboard while the power is on". If you want to hot-plug the keyboard, do it at your own risk. But, please, please, please do not advice other users that it is a safe thing to do; it simply is not. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
IPv6 setup...
How/Where is the setup for the IPv6? Shaun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
At 09:19 PM 3/10/00 -0600, Ryan Thompson wrote: >Me as well...For at least a decade. I used to do it manually all the >time, but had occasional glitches with funny scan codes and indicator >statuses. With a mid-range priced switch, though, I have had no problems >whatsoever. The only glitches I ever see are with a mouse. Tap me on the shoulder while my hand is on the mouse and it will seize. For my use at home there isn't a need for a switch. Could use one at times, but it's simple enough to swap around at need. Warner mentions static. As someone that builds up a good charge, it is always prudent to ground before (dis)connecting anything that is on or off. > > If/when this does change, wishing there will be a way to override back to > > the current behaviour. IMO, serial console should be explicitly called > for. > >Amen. If I can't boot a system to the local console without a keyboard, >that system isn't very useful. > >If the default DOES change, you should be able to change your boot.config >to remove the -P option. There have been a few times where I needed a video card from one system in another and ended up with a truly "headless" system with no other system near. Log in, shutdown, power off, pop in card, do what I need to do, and off with it's head. Mind I was waiting for some basic cards and didn't care to use a Matrox for 25X80. My dispute is more for the scrap systems I tinker around with at home. If someone else is paying the bill 8-) Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
On Fri, 10 Mar 2000, Walter Brameld wrote: > On Fri, 10 Mar 2000, in a never-ending search for enlightenment, R Joseph Wright >wrote: > > > > > > Regardless, this is typically syptomatic of either a very old > > > /boot/loader, non-use of the loader eg. through a /boot.config file, or > > > an error in the entry for / in /etc/fstab. > > > > > > > Isn't /boot/loader updated upon making a new world? If so, it ought to be > > current. I don't know any way of finding out since it's a binary file. > > > > /etc/fstab: > > > > /dev/ad0s4b noneswapsw 0 0 > > /dev/ad0s4a / ufs rw 1 1 > > /dev/ad0s4e /usrufs rw 2 2 > > /dev/acd0c /cdrom cd9660 ro,noauto 0 0 > > /dev/ad0s1 /dosmsdos ro,noauto 0 0 > > proc/proc procfs rw 0 0 > > > Shouldn't all those "4"s be "1"s ? No, because I'm using the 4th slice for FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
In message <[EMAIL PROTECTED]> "Jeffrey J. Mountin" writes: : Can't safely? Why the hell not? The spec doesn't allow for it. And most mobo mfg don't properly ground things so that you won't accidentally introduce a large static zap into the system. : Been hot-swapping keyboards for many years without *any* problems. Old DIN : style and PS2, doesn't matter. Even Doze doesn't mind. Usually it doesn't matter. However, sometimes it does. I've done it myself up until recently. Recently, I just killed two mobo keyboard controllers for reasons unknown. Maybe it was hot plugging, maybe it was a bad keyboard, who knows. Strangest thing I've ever seen. Only thing that in common is that my wife was using both of the machines at the time. BTW, That's why the mechanical keyboard work most of the time. They don't have the static problem that normal plugging has... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
Jeffrey J. Mountin wrote to Mike Smith: > At 05:54 PM 3/10/00 -0800, Mike Smith wrote: > >Since you can't safely hot-plug the PC keyboard, that wouldn't be very > >smart. The only way to auto-detect the use of a serial console is to > >look for a keyboard; if one isn't plugged in, there's no local console, > >end of story. > > Can't safely? Why the hell not? > > Been hot-swapping keyboards for many years without *any* problems. Old DIN > style and PS2, doesn't matter. Even Doze doesn't mind. Me as well...For at least a decade. I used to do it manually all the time, but had occasional glitches with funny scan codes and indicator statuses. With a mid-range priced switch, though, I have had no problems whatsoever. > If/when this does change, wishing there will be a way to override back to > the current behaviour. IMO, serial console should be explicitly called for. Amen. If I can't boot a system to the local console without a keyboard, that system isn't very useful. If the default DOES change, you should be able to change your boot.config to remove the -P option. -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Keyboard troubles
Brian Dean wrote to Ryan Thompson: > Ryan Thompson wrote: > > Thanks for the info. When I have another $500 burning a hole in my > > checkbook, I will probably order another keyboard, just so I have > > another one, if nothing else. :-) > > Why not just get a decent monitor/keyboard switch? Belkin makes a > nice 4-port in the $200 range that makes your motherboard think > there's a keyboard attached even if you are not currently switched > onto the system. I have something quite similar.. Still, seems like some individuals remain adamantly opposed to the idea of keyboard swapping, however careful one is. :-) > Just a thought ... and it's a lot cheaper than more convenient that > swapping your $500 keyboards (which must be _really_ impressive BTW :). They are... A small electronics firm in Saskatchewan was nice enough to help me design and manufacture something to fit my needs. (They even let me play with their expensive CAD tools to design the hardware key repeat :-). Actually, they gave me a really good price, considering their costs. I programmed it with a custom key layout (actually, something very close to Dvorak), but some key positions are different, and I've even got a few extra keys that I've wired macros to. I used to nicely exceed 100WPM on a $20 QWERTY keyboard. My QWERTY speed, understandably, has dropped to ~80, while my customized Dvorak speed jumped to about 110 sustained. -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Keyboard troubles
Ryan Thompson wrote: > Thanks for the info. When I have another $500 burning a hole in my > checkbook, I will probably order another keyboard, just so I have > another one, if nothing else. :-) Why not just get a decent monitor/keyboard switch? Belkin makes a nice 4-port in the $200 range that makes your motherboard think there's a keyboard attached even if you are not currently switched onto the system. Just a thought ... and it's a lot cheaper than more convenient that swapping your $500 keyboards (which must be _really_ impressive BTW :). -Brian -- Brian Dean [EMAIL PROTECTED] SAS Institute Inc. [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
At 05:54 PM 3/10/00 -0800, Mike Smith wrote: >Since you can't safely hot-plug the PC keyboard, that wouldn't be very >smart. The only way to auto-detect the use of a serial console is to >look for a keyboard; if one isn't plugged in, there's no local console, >end of story. Can't safely? Why the hell not? Been hot-swapping keyboards for many years without *any* problems. Old DIN style and PS2, doesn't matter. Even Doze doesn't mind. If/when this does change, wishing there will be a way to override back to the current behaviour. IMO, serial console should be explicitly called for. As for USB, mentioned elsewhere, still leery of it. Not to snub all the work that has been to support it, but it has done a return-of-the-living-dead act (mini-disc anyone?). Wonder if FireWire will do the same thing, which has been on my "wondering when" list for many years now. my .02 rant Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
>> It's indeed inconvenient that you cannot safely hot-plug the keyboard. >> And the world is heading for the USB standard... :-) > >This actually opens another entire can of worms; detecting a USB keyboard >at the bootstrap level is _not_ easy. It looks like at least some >systems aren't setting the 'extended keyboard' flag. 8( I wasn't talking about specific implementation which should be in FreeBSD. But, the general technological trend the world is following :-) Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Keyboard troubles
>I don't make a habit of keyboard swapping, and I HAVE experienced some >minor glitches before (such as weird scan codes being sent, or the state >of caps lock changing). You have been lucky that you didn't broke the motherboard when swapping the keyboard. The fact that you only had minor problems does not mean the rest of the world should be Ok too. >In any case, though, a keyboard reset or even >just a few key presses would fix. In the last 10 years, I have NEVER had >to reboot a system because they keyboard wasn't responding. Well, as I wrote before, I suspect that the keyboard interface of your motherboard is becoming flaky. This is a hardware problem, rather than software. It is not certainly the FreeBSD boot loader problem as it relies on the BIOS to detect the presense of the keyboard. >> Even if the keyboard interface survives hot-plugging, there is no >> assurance that the keyboard and the keyboard controller on the >> motherboard can communicate properly after hot-plugging; they are >> simply not designed to cope with such situation. >> >> I personally know a couple of people who broke their motherboard this >> way. > >Bummer for them.. Really, though, I would rather fry a $200 motherboard >than my $500CDN keyboard (my fingers have developed expensive tastes). >:-) None of my motherboard documentation warns agains swapping keyboards, >either. That doens't mean the motherboard manufacturer recommend keyboard swapping :-) I certainly don't like the idea that we encourage users something which may break their motherboard. I will tell more. Many motherboard, if not all, has a small fuse around the keyboard connector. This fuse will burn if large current runs in the keyboard interface. This may happen when you hot-plug/unplug the keyboard. The trouble is that this fuse cannot be easily replaced on many motherboard. Some old motherboards have a socketed fuse, so it's not hard to replace it (but it is still a hassle for non-engineering type folks). Many recent motherboard has the fuse SOLDERED on the motherboard, and the fuse itself is a small chip. This makes it hard for us to identify the fuse and repair it when it goes off. It is certainly unreasonable to assume any user can fix it himself. >In any case, I never had problems swapping keyboards between prior FreeBSD >releases, other UNIX platforms, Windows machines, DOS machines. Hell, >even my old Nintendo never complained if you plugged in a different >controller while it was powered on. :-) I was just wondering if >something had been done to 4.0 that didn't handle this situation like >previous releases. Nothing changed in the 4.0 boot loader. # Other UNIX boxes and the Nintendo game console are not relevant here. # They use different keyboard interface circuit. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
Mike Smith wrote to Ryan Thompson: > > "Don't have a keyboard" != "No keyboard detected" != "Serial Console". > > No keyboard detected -> local console won't be used -> use serial console Yes, that would seem to sum up the current behavior quite well. :-) > > Ok, so they can't be probed. However, I HAVE thought about it for a > > minute, and, to be honest, I still don't see why my proposal is entirely > > nonsensical. :-) Would you mind explaning your argument? For clarity, > > I'll explain mine again... Perhapas we're just not on the same wavelength: > > > > >From boot(8): > > > >-P probe the keyboard. If no keyboard is found, the -D and > > -h options are automatically set. > > > > Instead of that behaviour, I am suggesting a more forgiving behaviour: > > > > 1. Probe for a keyboard. > > 2. Is there a keyboard? > > Yes - Boot from the local console > > No - Display "Keyboard not found. Using serial console in 10 seconds, > > press any key to abort" > > This is as stupid as the "Keyboard error - Press F1 to continue" message > that several BIOS vendors are so fond of. If there's no keyboard > attached, you can't hit a key. Not very smart. :-) I just mentioned that in another (now closely related) thread. > > 3. Was a key pressed in 10 seconds? > > Yes - Boot from the local console > > No - Display "Booting from serial console" > >Boot from the serial console > > There's also not enough code space in the bootstrap for this frippery. > If you want to use a local keyboard, make sure it's plugged in. We don't > have a diagnostic for when you forget eg. to install your disk drive > either... That's a concern that I stated in my previous post. If it's not feasable, then it's not feasable. (And I can infer from your responses that you wouldn't be the one to commit such frippery to the codebase, anyway :-) It was but an idle query from someone mildly inconvenienced by -P. Thanks for the input. - Ryan -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world error.....
John Polstra wrote: > I don't believe I've ever used any special options, and my make.conf > file is "normal" except that it has "USA_RESIDENT=YES" in it. I know for certain that when I ran into this that I did not do anything other than a "make world" on a standard -current system, i.e., nothing special in make.conf or elsewhere, except that I too had USA_RESIDENT=YES in my environment. Since all my worlds worked fine afterwards, I suspect it is what Kris suggested originally which was that the perl script was perhaps running before the openssl/*.h files (or at least openssl/des.h) were installed, and was thus a sort of bootstrapping issue. But I must admint, I have not investigated it further. -Brian -- Brian Dean [EMAIL PROTECTED] SAS Institute Inc. [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
> It's indeed inconvenient that you cannot safely hot-plug the keyboard. > And the world is heading for the USB standard... :-) This actually opens another entire can of worms; detecting a USB keyboard at the bootstrap level is _not_ easy. It looks like at least some systems aren't setting the 'extended keyboard' flag. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USA_RESIDENT and sysinstall
At 12:23 PM 3/10/00 -0800, Jordan K. Hubbard wrote: > > I installed a -current snap from internat.freebsd.org that was built > > with crypto source from internat. I answered yes when sysinstall asked > > me if I want the crypto stuff, but then found that it marked me as an > > USA_RESIDENT=YES in /etc/make.conf and it also asked me later if I > > want to install the rsaref libraries. > > > > I think the test for USA_RESIDENT should be a bit more clever or the > > message should be a bit more clear. At the moment it is: > >Yes, I screwed this up - I'm fixing it now! When installing from the installation floppies, is the line supposed to be uncommented if you did answer yes? It did nothing for me. Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Keyboard troubles
Kazutaka YOKOTA wrote to Ryan Thompson: > It sounds like the keyboard interface of your motherboard has somewhat > become flaky; it may even be broken. > > It is NOT recommended that you attach or detach the keyboard while the > power is on. The keyboard interface of the PC motherboard is not > designed for hot-plugging/unplugging. It is too easy to fry the > keyboard interface and/or controller by doing so. I don't make a habit of keyboard swapping, and I HAVE experienced some minor glitches before (such as weird scan codes being sent, or the state of caps lock changing). In any case, though, a keyboard reset or even just a few key presses would fix. In the last 10 years, I have NEVER had to reboot a system because they keyboard wasn't responding. > Even if the keyboard interface survives hot-plugging, there is no > assurance that the keyboard and the keyboard controller on the > motherboard can communicate properly after hot-plugging; they are > simply not designed to cope with such situation. > > I personally know a couple of people who broke their motherboard this > way. Bummer for them.. Really, though, I would rather fry a $200 motherboard than my $500CDN keyboard (my fingers have developed expensive tastes). :-) None of my motherboard documentation warns agains swapping keyboards, either. In any case, I never had problems swapping keyboards between prior FreeBSD releases, other UNIX platforms, Windows machines, DOS machines. Hell, even my old Nintendo never complained if you plugged in a different controller while it was powered on. :-) I was just wondering if something had been done to 4.0 that didn't handle this situation like previous releases. Thanks for the info. When I have another $500 burning a hole in my checkbook, I will probably order another keyboard, just so I have another one, if nothing else. :-) - Ryan -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
>> >And, if not, could >> >the loader at least not display a message on the local monitor like >> >"Switching output to serial console...", or better yet, "Switching output >> >to serial console in 10 seconds.. press any key to abort"? >> >> Which key do you mean? The system has found no keyboard, you know :-) >> >> Kazu > >Exactly... My suggestion resembles the common BIOS boot message from days >of old: > > Keyboard not found. Press [F1] to continue. The PC BIOS prints "Press [F1] to continue" for ANY error detected during POST. I found it damm stupid. As I wrote in another posting, the keyboard interface on the PC motherboard is not designed for hot-plugging/unplugging. And I don't think the BIOS is expecting you to attach the keyboard without turning off the system in the above situation. You may say it works. But, I can say, with confidence, it is not generally the case with the average PC motherboard. I strongly object to the idea to put some logic or message to actively "encourage" users to hot-plug the keyboard. That will certainly lead to breakage of many motherboards. If the user hot-plug the keyboard, knowing involved risks, that's his problem; he is expected to know what he is doing and is prepared to accept the risks. It's indeed inconvenient that you cannot safely hot-plug the keyboard. And the world is heading for the USB standard... :-) Kazu >The novice reads, laughs out loud, and wonders if the joke is really on >them. After all, how COULD they press F1 if a keyboard does not exist? > >The expert checks his/her keyboard connection, (or plugs a keyboard in) >and, indeed, hits F1 to continue. BIOS programmers have been doing it >for about two decades. Why not the FreeBSD boot loader? :-) > >My idea is a similar one. Have the boot loader (with a reasonably >configured timeout--we don't want to wait indefinitely) display a similar >message (perhaps with copious beeping), giving the busy sysadmin a chance >to switch keyboards, or at least notice that a keyboard was not detected. > >If I install FreeBSD on multiple systems, I might throw boot disks in a >dozen machines so I don't have to wait for each one. I come around with >my $370 keyboard later to start the actual installs over NFS. I call it >'pipelining' :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
> > > > >Isn't there a better way to identify a serial console? > > > > > > > > I don't understand. What do you expect the boot loader to do? > > > > > > I'm not sure, that's why I asked the list :-) Really, what I was asking > > > is if there is a better way to detect a serial console.. Rather than the > > > current logic of "If there is no keyboard, there must be a serial > > > console". I can think of N reasons why a box would have no keyboard > > > attached, besides having a serial console. > > > > Actually, there aren't very many. If you don't have a keyboard, you need > > a console of some sort. If you don't have a console, you've made enough > > modifications to be undaunted by removing two bytes from /boot.config. > > "Don't have a keyboard" != "No keyboard detected" != "Serial Console". No keyboard detected -> local console won't be used -> use serial console > Ok, so they can't be probed. However, I HAVE thought about it for a > minute, and, to be honest, I still don't see why my proposal is entirely > nonsensical. :-) Would you mind explaning your argument? For clarity, > I'll explain mine again... Perhapas we're just not on the same wavelength: > > >From boot(8): > > -P probe the keyboard. If no keyboard is found, the -D and > -h options are automatically set. > > Instead of that behaviour, I am suggesting a more forgiving behaviour: > > 1. Probe for a keyboard. > 2. Is there a keyboard? > Yes - Boot from the local console > No - Display "Keyboard not found. Using serial console in 10 seconds, > press any key to abort" This is as stupid as the "Keyboard error - Press F1 to continue" message that several BIOS vendors are so fond of. If there's no keyboard attached, you can't hit a key. Not very smart. > 3. Was a key pressed in 10 seconds? > Yes - Boot from the local console > No - Display "Booting from serial console" >Boot from the serial console There's also not enough code space in the bootstrap for this frippery. If you want to use a local keyboard, make sure it's plugged in. We don't have a diagnostic for when you forget eg. to install your disk drive either... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
> At 05:06 PM 3/10/00 -0800, Mike Smith wrote: > >Note also that the probe-for-keyboard feature is only used on the > >installation media; it's not the default for system behaviour (yet). > > Hopefully that "yet" will be "never" so one can boot sans keyboard and > later hook one up if need be. Since you can't safely hot-plug the PC keyboard, that wouldn't be very smart. The only way to auto-detect the use of a serial console is to look for a keyboard; if one isn't plugged in, there's no local console, end of story. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
At 05:06 PM 3/10/00 -0800, Mike Smith wrote: >Note also that the probe-for-keyboard feature is only used on the >installation media; it's not the default for system behaviour (yet). Hopefully that "yet" will be "never" so one can boot sans keyboard and later hook one up if need be. Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
At 05:35 PM 3/8/00 +, Kris Kennaway wrote: >On Wed, 8 Mar 2000, Jeffrey J. Mountin wrote: > > > What I did not check is removing RSAref after a buildworld and checking for > > breakage, but that smacks of shooting one's self in the foot. > >That should just revert to the previous case of complaining loudly if you >try and make use of RSA. Well, so it does. Think I'll go soak my foot. ;) Tried it with RC3 and what is better than the last time is that after installing RSAref one does *not* have to restart sshd in order for RSA authentication to work. Very nice. Still has the problem with other not having permissions on the .ssh dir and authorized_keys file. Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world error.....
In article <[EMAIL PROTECTED]>, Kris Kennaway <[EMAIL PROTECTED]> wrote: > On Fri, 10 Mar 2000, John Polstra wrote: > > > This is still broken. I ran into it when upgrading a Feb. 29 -current > > system to today's -current. I didn't use make -j and I didn't take > > any shortcuts. > > Both were compiled with the same options (i.e. you didn't do the first one > NO_OPENSSL or something)? Correct. On this machine I've always done it the same way: make buildworld make installworld I don't believe I've ever used any special options, and my make.conf file is "normal" except that it has "USA_RESIDENT=YES" in it. > I'll try and replicate this once I verify my current buildworld > changes. Thanks. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
On Fri, 10 Mar 2000, in a never-ending search for enlightenment, R Joseph Wright wrote: > > > > Regardless, this is typically syptomatic of either a very old > > /boot/loader, non-use of the loader eg. through a /boot.config file, or > > an error in the entry for / in /etc/fstab. > > > > Isn't /boot/loader updated upon making a new world? If so, it ought to be > current. I don't know any way of finding out since it's a binary file. > > /etc/fstab: > > /dev/ad0s4b noneswapsw 0 0 > /dev/ad0s4a / ufs rw 1 1 > /dev/ad0s4e /usrufs rw 2 2 > /dev/acd0c/cdrom cd9660 ro,noauto 0 0 > /dev/ad0s1/dosmsdos ro,noauto 0 0 > proc /proc procfs rw 0 0 > Shouldn't all those "4"s be "1"s ? -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter:Where the hell am I? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feedback on 4.0-RC3 (mostly good! :)
On Fri, 10 Mar 2000, Walter Brameld wrote: > Yeah, I'll buy that. Now I gather it was not written by the commiters > and it's not their responsibility (?) to rewrite it. But is there any > point in keeing it? This is FreeBSD, no-one has any resposibilities whatsoever :-) It should probably either be removed or updated. Submitting a PR would be best. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world error.....
On Fri, 10 Mar 2000, John Polstra wrote: > This is still broken. I ran into it when upgrading a Feb. 29 -current > system to today's -current. I didn't use make -j and I didn't take > any shortcuts. Both were compiled with the same options (i.e. you didn't do the first one NO_OPENSSL or something)? I'll try and replicate this once I verify my current buildworld changes. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
Mike Smith wrote to Ryan Thompson: > > > >Isn't there a better way to identify a serial console? > > > > > > I don't understand. What do you expect the boot loader to do? > > > > I'm not sure, that's why I asked the list :-) Really, what I was asking > > is if there is a better way to detect a serial console.. Rather than the > > current logic of "If there is no keyboard, there must be a serial > > console". I can think of N reasons why a box would have no keyboard > > attached, besides having a serial console. > > Actually, there aren't very many. If you don't have a keyboard, you need > a console of some sort. If you don't have a console, you've made enough > modifications to be undaunted by removing two bytes from /boot.config. "Don't have a keyboard" != "No keyboard detected" != "Serial Console". I understand the reasoning and rationale behind the logic used, and I agree with it, to a point. Read below. I have indeed disabled the keyboard probe in /boot.config when doing many installs to avoid the problem that I mentioned... But I always yearned for something a little less awkward, when I can otherwise still use install disks from the distribution images. > > I know very little about serial consoles, but can they not be probed > > somehow to determine their existence? If that's not possible, at least, > > what I'm suggesting below still sounds reasonable. > > No, they can't be probed, and no, if you think about it for a minute, > what you're proposing is entirely nonsensical. Ok, so they can't be probed. However, I HAVE thought about it for a minute, and, to be honest, I still don't see why my proposal is entirely nonsensical. :-) Would you mind explaning your argument? For clarity, I'll explain mine again... Perhapas we're just not on the same wavelength: >From boot(8): -P probe the keyboard. If no keyboard is found, the -D and -h options are automatically set. Instead of that behaviour, I am suggesting a more forgiving behaviour: 1. Probe for a keyboard. 2. Is there a keyboard? Yes - Boot from the local console No - Display "Keyboard not found. Using serial console in 10 seconds, press any key to abort" 3. Was a key pressed in 10 seconds? Yes - Boot from the local console No - Display "Booting from serial console" Boot from the serial console Nothing is lost, besides an extra 10 seconds at bootup, and a smidgen of the code segment. If no keyboard is detected, and there is indeed a serial console, it will still be used automatically. If, however, there was a temporary probing problem (i.e., the keyboard was not yet plugged in), the installer can smack a key and continue on. I'm open to the idea that I'm being nonsensical (I'll usually be the first one to admit it), but, in this case, I just don't see your reasoning, Mike. Please clarify. -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world error.....
In article <[EMAIL PROTECTED]>, Kris Kennaway <[EMAIL PROTECTED]> wrote: > On Sun, 5 Mar 2000, Brian Dean wrote: > > > The perl script h2ph does not exit immediately on des.h, it sets it's > > $Exit value to 1, but continues processing. If the original poster > > would check further back in his log file, he'll see: > > Ah, okay. There might be an ordering problem with the des.h symlink being > created before the openssl/des.h file which it points to. Any ideas, > Mark? This is still broken. I ran into it when upgrading a Feb. 29 -current system to today's -current. I didn't use make -j and I didn't take any shortcuts. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Keyboard troubles
>On my -current system, after rebooting, the keyboard was in a funny state >(all 4 LEDs were turned on. My keyboard also has an internal click >mechanism, which was no longer functional) I plugged the keyboard into >another machine at that point, and it reset itself and worked fine on that >machine. Plugging it back into the -current box, however, produced the >same results as before. > >Fearing incompatibility, I dug out an old AT keyboard and plugged it >in. No LEDs lit, and also no response from keypresses (including the >obvious escape characters). > >The machine didn't hang... console message were still being displayed. I >ended up rebooting the thing remotely, and after that, the keyboard >functioned normally. > >If somebody can tell me what else to check, I can try and provide a few >mroe details. It sounds like the keyboard interface of your motherboard has somewhat become flaky; it may even be broken. It is NOT recommended that you attach or detach the keyboard while the power is on. The keyboard interface of the PC motherboard is not designed for hot-plugging/unplugging. It is too easy to fry the keyboard interface and/or controller by doing so. Even if the keyboard interface survives hot-plugging, there is no assurance that the keyboard and the keyboard controller on the motherboard can communicate properly after hot-plugging; they are simply not designed to cope with such situation. I personally know a couple of people who broke their motherboard this way. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feedback on 4.0-RC3 (mostly good! :)
On Fri, 10 Mar 2000, in a never-ending search for enlightenment, Walter Brameld wrote: > On Fri, 10 Mar 2000, in a never-ending search for enlightenment, Kris Kennaway wrote: > > On Fri, 10 Mar 2000, Walter Brameld wrote: > > > > > I wonder about other nit-picky things, like why is sound.doc (to > > > which I've seen numorous RTFM references) still written for > > > configurations under FreeBSD 2.1 ? > > > > Because no-one has rewritten it? > > > > Kris > > Yeah, I'll buy that. Now I gather it was not written by the commiters > and it's not their responsibility (?) to rewrite it. But is there any > point in keeing it? > Er, keeping. -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter:Where the hell am I? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feedback on 4.0-RC3 (mostly good! :)
On Fri, 10 Mar 2000, in a never-ending search for enlightenment, Kris Kennaway wrote: > On Fri, 10 Mar 2000, Walter Brameld wrote: > > > I wonder about other nit-picky things, like why is sound.doc (to > > which I've seen numorous RTFM references) still written for > > configurations under FreeBSD 2.1 ? > > Because no-one has rewritten it? > > Kris Yeah, I'll buy that. Now I gather it was not written by the commiters and it's not their responsibility (?) to rewrite it. But is there any point in keeing it? -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter:Where the hell am I? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
On Fri, 10 Mar 2000, Jim Bloom wrote: > I believe it is a build order and dependency problem that shouldn't > exist. libkrb is built before libRSAglue and then the shared library is > built with -LRSAglue which is only found in /usr/lib. > kerberosIV/Makefile.inc has a line "LDADD+= -LRSAglue". > > This whole issue should not exist simply because libRSAglue is a dummy > stub and there is no reson to link anything against it. The quick fix > is to remove libRSAglue from the makefiles where it is used. The > following makefiles need to have the references to RSAglue removed: Ack, I thought I had committed this already, but I see it's only in one of my trees. I'll test this with the current failure mode and without and try and get it committed ASAP. Thanks! Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RC3
On Fri, 10 Mar 2000, Brian Beattie wrote: > 2) When I tried to install CRYPTO from the CD I got errors for a number of > them, something about not being able to read a script of something (it was > 2am so I do not have the exact error message), so i installed from FTP. ... > 3) First time i declined DES because I did not want DES passwords, hoping > it would install crypto (ssl, ssh) or would ask me. This is still an issue. DES crypt is really an ugly wart on the side of the FreeBSD nose..it's really a "legacy support" library and not something we should be installing by default along with the rest of the actually-useful crypto collection. Jordan, I wonder if it would be possible at this late stage to have sysinstall ask a separate question about DES password support, and use that to point the libcrypt symlinks to one or the other? Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Keyboard troubles
Why does it seem like I'm posting a lot of messages about keyboards, today? :-) I seem to remember hearing a similar problem a month or two ago, and do not remember if it was resolved. I couldn't remember enough about it to find it in the list archives. In any case, I at least want to say "me too". On my -current system, after rebooting, the keyboard was in a funny state (all 4 LEDs were turned on. My keyboard also has an internal click mechanism, which was no longer functional) I plugged the keyboard into another machine at that point, and it reset itself and worked fine on that machine. Plugging it back into the -current box, however, produced the same results as before. Fearing incompatibility, I dug out an old AT keyboard and plugged it in. No LEDs lit, and also no response from keypresses (including the obvious escape characters). The machine didn't hang... console message were still being displayed. I ended up rebooting the thing remotely, and after that, the keyboard functioned normally. If somebody can tell me what else to check, I can try and provide a few mroe details. -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
> > >Isn't there a better way to identify a serial console? > > > > I don't understand. What do you expect the boot loader to do? > > I'm not sure, that's why I asked the list :-) Really, what I was asking > is if there is a better way to detect a serial console.. Rather than the > current logic of "If there is no keyboard, there must be a serial > console". I can think of N reasons why a box would have no keyboard > attached, besides having a serial console. Actually, there aren't very many. If you don't have a keyboard, you need a console of some sort. If you don't have a console, you've made enough modifications to be undaunted by removing two bytes from /boot.config. > I know very little about serial consoles, but can they not be probed > somehow to determine their existence? If that's not possible, at least, > what I'm suggesting below still sounds reasonable. No, they can't be probed, and no, if you think about it for a minute, what you're proposing is entirely nonsensical. Note also that the probe-for-keyboard feature is only used on the installation media; it's not the default for system behaviour (yet). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feedback on 4.0-RC3 (mostly good! :)
On Fri, 10 Mar 2000, Walter Brameld wrote: > I wonder about other nit-picky things, like why is sound.doc (to > which I've seen numorous RTFM references) still written for > configurations under FreeBSD 2.1 ? Because no-one has rewritten it? Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
Kazutaka YOKOTA wrote to Ryan Thompson: > >Maybe there is a valid reason for this, but when I attempt to boot the 4.0 > >kern.flp without a keyboard attached (I share one keyboard between four > >systems, here), it displays keyboard: no and the BTX loader message, and > >ceases to display ANY output on the attached monitor (though it does > >continue to access the disk, I'm assuming, until the MFS root floppy is > >needed)? > > > >I assume this is because, without a keyboard, the loader assumes a serial > >console is attached. > > Yes. And this has been the behavior since FreeBSD 2.X. I thought as much. > >This is not the case in my situation. > > > >Isn't there a better way to identify a serial console? > > I don't understand. What do you expect the boot loader to do? I'm not sure, that's why I asked the list :-) Really, what I was asking is if there is a better way to detect a serial console.. Rather than the current logic of "If there is no keyboard, there must be a serial console". I can think of N reasons why a box would have no keyboard attached, besides having a serial console. I know very little about serial consoles, but can they not be probed somehow to determine their existence? If that's not possible, at least, what I'm suggesting below still sounds reasonable. > >And, if not, could > >the loader at least not display a message on the local monitor like > >"Switching output to serial console...", or better yet, "Switching output > >to serial console in 10 seconds.. press any key to abort"? > > Which key do you mean? The system has found no keyboard, you know :-) > > Kazu Exactly... My suggestion resembles the common BIOS boot message from days of old: Keyboard not found. Press [F1] to continue. The novice reads, laughs out loud, and wonders if the joke is really on them. After all, how COULD they press F1 if a keyboard does not exist? The expert checks his/her keyboard connection, (or plugs a keyboard in) and, indeed, hits F1 to continue. BIOS programmers have been doing it for about two decades. Why not the FreeBSD boot loader? :-) My idea is a similar one. Have the boot loader (with a reasonably configured timeout--we don't want to wait indefinitely) display a similar message (perhaps with copious beeping), giving the busy sysadmin a chance to switch keyboards, or at least notice that a keyboard was not detected. If I install FreeBSD on multiple systems, I might throw boot disks in a dozen machines so I don't have to wait for each one. I come around with my $370 keyboard later to start the actual installs over NFS. I call it 'pipelining' :-) -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feedback on 4.0-RC3 (mostly good! :)
On Fri, 10 Mar 2000, in a never-ending search for enlightenment, Shaun (UNIX) wrote: > Hello, > > You are using RC3 ? Hmm...I wonder why you are not getting the ATA prob > problems like alot of us are. What is your system config? > > Yes it is FAST! and I love itI see that the 64MB memory problem has > been fix at the install level. 3.x only reads 64MB of RAM at the floppy > install. 4.0 reads all of my 128MB. > > Cheers > Shaun Odd, 3.x always read all of my 128MB. I didn't get any ata probe problems and didn't read the posts. I wonder about other nit-picky things, like why is sound.doc (to which I've seen numorous RTFM references) still written for configurations under FreeBSD 2.1 ? > On Thu, 9 Mar 2000, John Reynolds wrote: > > > > > OK, finally had a chance to frag the hard drive and install 4.0-RC3 from cdrom > > and see how it went. Here's my observations on the good: > > > > 1) On the same hardware as I tested 4.0-RC and 4.0-RC2 on, now I no longer get > > those "long ATA probes"! This is awesome! Whatever was done, is great, now > > the machine boots very speedily. > > > > 2) The "Standard Installation" is much better than "Novice". It was good to > > rename this. > > > > 3) I chose the "A" option for partition/label and good, reasonable defaults > > were given to me. > > > > 4) The "Standard Install" went flawlessly (despite my best attempts at pilot > > error :). > > > > Now observations on a few nit-picky things: > > > > 1) There is a typo (spelling error) in one of the dialogs I was presented. I > > was trying to force pilot error into the situation :) and got a dialog that > > contained the following line: > > > > "You can also chose "No" at the next prompt and go back into the > > installation menus to try and retry whichever operations failed." > > > > The word "chose" should be "choose." I'd supply a patch, but I only > > installed kernel source :( > > > > 2) Again, while trying to inject pilot error, I created a FreeBSD partition of > > only 10Mb and gave that as the only slice the Label editor could deal > > with. When I hit 'A' to have it auto-decide, it came back with a dialog > > box: > > > > "Unable to create root partition. Too big?" > > > > I assume by what I gave to it, that it means to say "dummy, you didn't give > > me a big enough slice with which to work, try again." If that is the case, > > perhaps a small re-write of the dialog message is in order to help explain > > what has gone on and a possible course of action to correct the > > problem--like "give me a larger slice to work with here". In all honesty, I > > *meant* to create a 10Gb partition and typed so fast that my brain didn't > > snap that "10M" != "10G" ... and thus I presented a wierd situation to the > > Label editor. > > > > The system is fast, GNOME+E. desktop is usable, kernel config went like a > > charm. Looks *real* good from where I'm sittin'. Good work to all! Let's ship > > this puppy. :) > > > > -Jr > > > > -- > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation > > [EMAIL PROTECTED] My opinions are mine, not Intel's. Running > > [EMAIL PROTECTED] FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. > > http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter:Where the hell am I? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000307-CURRENT kern.flp keyboard probe questions
>Maybe there is a valid reason for this, but when I attempt to boot the 4.0 >kern.flp without a keyboard attached (I share one keyboard between four >systems, here), it displays keyboard: no and the BTX loader message, and >ceases to display ANY output on the attached monitor (though it does >continue to access the disk, I'm assuming, until the MFS root floppy is >needed)? > >I assume this is because, without a keyboard, the loader assumes a serial >console is attached. Yes. And this has been the behavior since FreeBSD 2.X. >This is not the case in my situation. > >Isn't there a better way to identify a serial console? I don't understand. What do you expect the boot loader to do? >And, if not, could >the loader at least not display a message on the local monitor like >"Switching output to serial console...", or better yet, "Switching output >to serial console in 10 seconds.. press any key to abort"? Which key do you mean? The system has found no keyboard, you know :-) Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kde2pre: is it FreeBSD or Kde fault?
On Thu, 2 Mar 2000, Theo van Klaveren wrote: > stereofftscope.cpp:~80: sorry, not implemented. (something about symbol > to big for symbol table). Recompile all your sources with -fhuge-objects. > > I finished the build with make -k, but I have no arts :( I suspect this to > be a FreeBSD problem, as the Linux guys don't seem to have this (or it > would have been fixed in the previous two/three weeks). > > I noticed the same problem with libkhtml, b.t.w. Pfft. Last time I tried to compile arts, I only needed to make a few changes, and it worked fine. I haven't tried in a while. But if you're getting weird errors, then report them, as I haven't seen any such bug reports. If you don't report stuff, how do you expect it to be fixed? FWIW, I haven't seen the problems with eh_rtime_match being undefined either. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with Linksys NIC and the new dc driver.
I am currently experiencing problems with the 0307 -CURRENT snapshot, and the dc driver. I previously have had no problems with the pn driver I had been using in 3.4-STABLE. I installed current on this machine because as of now, the wd driver in stable doesn't like my larger IDE drive very much. So I got the drive working, but I simply cannot get the network card to cooperate with this new driver. It's detected, dmesg lines as follows: dc0: <82c168 PNIC 10/100BaseTX> port 0xd00-0xdeff mem dc0: starting DAD for fe80:0001::02a0:ccff:fe21:9357 dc0: DAD complete for fe80:0001::02a0ccff:fe21:9357 - no duplicates found I've toyed with various mediatype settings, hasn't seen to make a difference. ifconfig dc0 media auto results in the error ifconfig: SIOSIFMEDIA: Device not configured Standard ifconfig -a output shows media: 10baseT/UTP status: no carrier, though the lights are on on my hub. If I configure it to 100baseTX, and bring the interface back up again, it shows the status as active, but the lights immediately die. Trying to toy with the duplex settings in 10baseT/UTP mode also give me the SIOSIFMEDIA error. Does anyone have any insight into this? As I said, this card has always served me well with the pn driver, but then I am unable to gain access to my drive with the wd driver. I'm really hoping there's some way I will be able to configure the NIC properly under 4.0. - Jay Oliver Please at least cc all replies to this email address, as until I resolve this problem with the NIC, my mail servers offline, and I can't read the lists. I don't think the owner of this shell would appreciate me subscribing it to relatively high traffic lists. Thank you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dvd playback
I've been playing with it using the original sources and the patches that were posted a long time ago on this list. On my DVD drive (Sony DDU220E), the software fails on gettitlekey. I've chatted with Soren and he left me with something to try that I never did (can you say, busy busy busy :( For the record, using Mandrake Linux (hedrat optimised for pentiums) with a hedrat kernel, I got far worse errors and it didn't even come close to appearing like working ;) jon smith -- Close your eyes. Now forget what you see. What do you feel? -- My heart. -- Come here. -- Your heart. -- See? We're exactly the same. Jon Smith -- Senior Math Major @ Purdue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured inrc.conf?
> And here is the patches. The last patches should work but I found a improvement related to coexistence with gif, so this is the updated patches. Thanks, Yoshinobu Inoue I applied a variant of your patch to my NetBSD/i386 -currentish box that also uses the KAME stack and was able to ping6 your 6to4 address. Brad Spencer - [EMAIL PROTECTED] http://anduin.eldar.org [finger [EMAIL PROTECTED] for PGP public key] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mylex Support
> I have 4 different Mylex DAC960 controllers that I cannot install Current > onto. (Tried from Late December to 2307). Sysinstall seems to get the > geometry wrong, and even telling sysinstall the "correct" geometry, it gives > a "tied to write beyond end of drive" error. Booting from a running -current > and formatting does the same. They all have the latest BIOS, and they have > been tried with various drive combinations. Has anyone else got this to work > successfully or is it just me?. Obviously; you're actually the _only_ person I've heard from with this problem. > And if it is just me, anyone got any ideas? I have been pestering Mike Smith > about this for ages, and have probably driven him mad! More or less. As I've said - I have no idea what's going on for you at the moment; everything here "just works" like it should. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
KDE kdm problem with packaged version (make release issue?)
For a long time I have noticed that when I build kdm from the kdebase port, it works. But if I used packages off either the CDs or ftp sites, it doesn't work. Specifically if I do a 'strings' on the binary and grep for /, some of the paths I see have XBINDIR rather than explicit references to /usr/X11R6/bin. I am not enough a ports guru to grok what is to be done, but before the freeze maybe someone could look into it? Another suggestion is that two patches to the xdm config files be made at the time that kdebase is installed -- One needs to add a call to kdmdesktop to Xsetup_0, and one needs to add kde) exec /usr/local/bin/startkde ;; right above the failsafe case in Xsession. If the port doesn't make these two patches itself at install time, it might at least _suggest_ them to the user, IMHO. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCI modems
BTW, my latest patches can be found at http://people.freebsd.org/~imp/sio-current-pci-patch and it works for me on my 3com model 5610 and actiontek pci controller based modem. If your 3com modem isn't a 5610, then it is almost certianly a winmodem, despite what you've been told. If it isn't a 5610 and it does work, please let me know what the card ID so I can add it to my driver. It would also be good to have the output of at1, ati2, ati3, ati4, etc up to ati10 if you can get that for me. Maybe I should just commit it. Jordan did say a while ago to use my best judgement, but I could just do it anyway. :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RC3 install floppies: panic: resource_list_alloc: resource entry is busy
Soren Schmidt wrote: > [...] > Hmm, seems to be a resource conflict problem, question is what is > causing this. Could you do a verbose boot both with the old > working kernel, and the new failing one ? > Attached are two files. Both kernels used are built from the same config file, which is mostly GENERIC with devices removed that I do not have. The file "new" results from booting a kernel built completely from sources cvsupped yesterday. For "old" I replaced the contents of /sys/dev/ata by the files of February 17, i.e. before the major changes. I must remark that this is one of the machines that reports its IDE IRQ as 0 when asked for it. About two months ago there were problems when the ata driver took the timer interrupt. This was fixed by a special clause in ata-all.c, at least up to February 17. Maybe the current problem is related. > > This machine has an Intel motherboard with a Mercury chipset, 64 Mbyte > > RAM, Matrox Millenium II, two Western Digital disks, and it ran all > > previous FreeBSD releases perfectly for almost five years. > > Yeah I notice the RZ 1000 chips in there, BE CAREFULL, I wouldn't > use this for anything I cared about... For serious work I now have two BP6 based machines, this became just a testmachine. I know about the possible data corruption problems with RZ1000 chips, but I have never seen them with FreeBSD, despite the fact that I did a "make world" every other week for more than two years. However, if you run Linux or Solaris on this machine, and forget to switch off the EIDE prefetch buffers, the results can be quite dramatic... Kind regards, Hans SMAP type=01 base= len= 0009fc00 SMAP type=01 base= 0010 len= 03f0 SMAP type=02 base= fffc len= 0004 Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Mar 10 21:43:07 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/CUSTOM Calibrating clock(s) ... TSC clock: 66643091 Hz, i8254 clock: 1300543 Hz 1300543 Hz differs from default of 1193182 Hz by more than 1% Timecounter "i8254" frequency 1193182 Hz TSC clock: 48650664 Hz (Method B) Timecounter "TSC" frequency 48650664 Hz CPU: Pentium/P5 (48.65-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x517 Stepping = 7 Features=0x1bf real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x002d1000 - 0x03ff7fff, 64122880 bytes (15655 pages) avail memory = 62267392 (60808K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f0120 bios32: Entry = 0xf145c (c00f145c) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x1440 pnpbios: Found PnP BIOS data at 0xc00f0130 pnpbios: Entry = f:1245 Rev = 1.0 Other BIOS signatures found: ACPI: Preloaded elf kernel "kernel" at 0xc02b8000. Intel Pentium detected, installing workaround for F00F bug pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x (0x8000) pci_open(1b): mode1res=0x (0xff01) pci_open(2):mode 2 enable port (0x0cf8) is 0x00 pci_open(2a): mode2res=0x0e (0x0e) pci_open(2a): now trying mechanism 2 pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=04a38086) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 54761513 bytes/sec bzero() bandwidth = 27416038 bytes/sec pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x (0x8000) pci_open(1b): mode1res=0x (0xff01) pci_open(2):mode 2 enable port (0x0cf8) is 0x00 pci_open(2a): mode2res=0x0e (0x0e) pci_open(2a): now trying mechanism 2 pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=04a38086) pcib0: on motherboard found-> vendor=0x8086, dev=0x04a3, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found-> vendor=0x1042, dev=0x1000, revid=0x01 class=01-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[10]: type 1, range 32, base 01f0, size 3 map[14]: type 1, range 32, base 03f4, size 2 found-> vendor=0x8086, dev=0x0484, revid=0x03 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found-> vendor=0x102b, dev=0x051b, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base a000, size 24 map[14]: type 1, range 32, base a100, size 14 map[18]: type 1, range 32, base a180, size 23 found-> vendor=0x10b7, dev=0x9200, revid=0x74 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base fc80, size 7 map[14]: type 1, range 3
Re: PCI modems
In message <[EMAIL PROTECTED]> Kent Hauser writes: : I've tried hard to get my PCI internal modem work with current. Well, there's no support for that yet. : I've tried editing /sys/isa/sio.c with the all possible byte : and word swaps of the vendor/dev printouts from the kernel : probe. The documentation for this USR modem says it's *not* : a winmodem, but a "standalone" modem. Yes. It works with my driver. However, I finished it during the freeze and Bruce requested that I hold off until after 4.0. I'll likely commit it after 4.0 goes golden. Although I have a "fix a pccard panic" fix for sio that's been approved, but not reviewed yet. I could sneak this into that commit :-). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
$B1c2q$N1i=P$K!"!X4{B8(J$B$N%S!<%k$,!"$"$J$?MM$@$1$N%S(J$B!<%k$K%o%s%?%C%A$GJQ?H!#!Y(J
$BEbFM$J%a!<%k$*5v$72<$5$$!#(J
$B4?Aw7^2q$d7k:'<0$N%7!<%:%s$G$9!#(J
$B$=$3$G!"1c2q44;vMM$K$*CN$i$;$G$9!#(J
$B$46=L#$N$J$$J}$K$O?4$+$i$*OM$S?=$7>e$2$^$9$H$H$b$K!"(J
$B:o=|$N$*4j$$$r?=$7>e$2$^$9!#(J
$B!|!|!|4{B8$N%S!<%k$,$"$J$?MM$@$1$N%S!<%k$K%o%s%?%C%A$GJQ?H!#!|!|!|(J
$B!Je$K!"%7!<%k$rE=$j$^$9$,!"E=$C$F$$(J
$B$k0cOB46$,A4$/$"$j$^$;$s!#(J
$B%"%5%R%9!<%Q!<%I%i%$!"%5%C%]%m9u@8$KBP1~$G$9!#$^$?!"#1#0Kg(J
$B!J#1#0K\J,!K$+$i\$7$/$O2<5-$N%[!<%`%Z!<%8$r$4Mw2<$5$$!#(J
=$B!!(Jhttp://www.ican21.com/o_messe/indexf.html$B!!(J===
$B4k6HL>(J $B3t<02q!!(J $BEOJUE/IW(J
$B%a!<%k(J [EMAIL PROTECTED]
TEL$B!!(J 018-823-9928
FAX$B!!(J 018-865-6898
$B=;=j!!(J $B=)ED;T?720A%>lD.(J2-18
$BC4Evhttp://www.ican21.com
$BO"Mm2DG=;~4VBS!!(J9$B!'(J00$B!A(J18$B!'(J00
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Mylex Support
On Fri, 10 Mar 2000, Lawrence Farr wrote: > I have 4 different Mylex DAC960 controllers that I cannot install Current > onto. (Tried from Late December to 2307). Sysinstall seems to get the > geometry wrong, and even telling sysinstall the "correct" geometry, it gives > a "tied to write beyond end of drive" error. Booting from a running -current > and formatting does the same. They all have the latest BIOS, and they have > been tried with various drive combinations. Has anyone else got this to work > successfully or is it just me?. I know it sounds wierd, but if you boot with a dos floppy and fdisk a small partition onto the drives, it might work. We used to have a problem (not on Mylex controllers though) that sounds the same. After putting on the small partition, boot the install and it will (hopefully) detect the right geometry. Anyone else have any ideas? -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
> > > > Regardless, this is typically syptomatic of either a very old > > /boot/loader, non-use of the loader eg. through a /boot.config file, or > > an error in the entry for / in /etc/fstab. > > > > Isn't /boot/loader updated upon making a new world? If so, it ought to be > current. I don't know any way of finding out since it's a binary file. That's correct. If the loader is run, there is no way for 'wd' to become involved in the process unless a disk error occurs reading from the 'ad' driver. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: building ports
* From: Edwin Kremer <[EMAIL PROTECTED]> * On Mon, Mar 08, 1999 at 09:44:26PM -0600, Ishmael wrote: * * : Your system is too old to use this bsd.port.mk. * * According to the mail headers, your system clock is about one year * behind actual time. That might have screwed up the `make'... Yes, that certainly would have. The "date" written in /var/db/pkg/port.mkversion will be one year old! Satoshi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
On Fri, Mar 10, 2000 at 11:21:15AM -0800, R Joseph Wright wrote: > > > > Regardless, this is typically syptomatic of either a very old > > /boot/loader, non-use of the loader eg. through a /boot.config file, or > > an error in the entry for / in /etc/fstab. > > > > Isn't /boot/loader updated upon making a new world? If so, it ought to be > current. I don't know any way of finding out since it's a binary file. > sorry if this is a stupid reply, but you don't happen to have this line in your kerne config file do you? config kernel root on wd0 regards, -oscar -- pgp public key: finger [EMAIL PROTECTED] pgp fingerprint: 6D 18 8C 90 4C DF F0 4B DF 35 1F 69 A1 33 C7 BC To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More "ld-elf.so.1: assert failed" messages
In article <[EMAIL PROTECTED]>, Jim Bloom <[EMAIL PROTECTED]> wrote: [when dllockinit() should be called] > It should be called somewhere between the starting of the process > and the creation of the second thread. There is no problem if there > is only one thread. > > THREAD Create would be fine as long as it sets a variable accessible > to all threads indicating dllockinit has been called. > > Another possible location would be a routine that initialize the > multithreading for the process. This routine may not exist in all > thread packages though. That is all correct. Dllockinit has to be called once only, before any threads have been forked but late enough so that it's safe to call the thread sychronization primitives. Ideally, a reader/writer lock should be used. But it will also work to use a simple mutex. In that case, rlock_acquire and wlock_aquire will be the same (lock the mutex). I'd recommend using a simple mutex unless the threads package already implements reader/writer locks. I really hope I can render all this nonsense unnecessary after the code freeze ends. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
4.0-20000307-CURRENT kern.flp keyboard probe questions
Hi all... Maybe there is a valid reason for this, but when I attempt to boot the 4.0 kern.flp without a keyboard attached (I share one keyboard between four systems, here), it displays keyboard: no and the BTX loader message, and ceases to display ANY output on the attached monitor (though it does continue to access the disk, I'm assuming, until the MFS root floppy is needed)? I assume this is because, without a keyboard, the loader assumes a serial console is attached. This is not the case in my situation. Isn't there a better way to identify a serial console? And, if not, could the loader at least not display a message on the local monitor like "Switching output to serial console...", or better yet, "Switching output to serial console in 10 seconds.. press any key to abort"? IMO, something like the above might avoid some confusion in the future. -- Ryan Thompson <[EMAIL PROTECTED]> Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
dvd playback
Hi, I was looking around the internet to see how the opensource people were getting along with all the suits against them, and I found a site with a freebsd css-auth patch and nist archive tared; I was wondering how well dvd playback was at this point? all those wondering, the site is linked from http://www.opendvd.org/. - kevin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured inrc.conf?
> > > I tried deleting the 6to4 address from an interface on the > > > interior node and did a ping6, but I get no replies (I think > > > you have to configure the route on your end first?). > > > > Yes, I have configured it, so it should work now. > > Yes, it does. It all looks good. > > PING6(56=40+8+8 bytes) c000::2a0:c9ff:feb1:23ae --> >3ffe:501:4819:2000:210:5aff:fe86:b65a > 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=0 hlim=63 time=452.312 >ms > 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=1 hlim=63 time=361.945 >ms Much thanks for your help! :-) Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PCI modems
Hi all, I've tried hard to get my PCI internal modem work with current. I've tried editing /sys/isa/sio.c with the all possible byte and word swaps of the vendor/dev printouts from the kernel probe. The documentation for this USR modem says it's *not* a winmodem, but a "standalone" modem. The 3.x FAQ suggests fiddling with/enabling the PNP driver -- which seems integrated in current. Any suggestions? Thanks. Kent To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured in rc.conf?
On Sat, Mar 11, 2000 at 02:50:28AM +0900, Yoshinobu Inoue wrote: > > I also had to adjust my ipv4 firewall rules to allow protocol > > ipv6 through. Strange that I didn't have to do that when > > doing a gif tunnel to freenet6.net. Also, what do I have to > > do to enable ip6fw? > > Wmmm, it is strange that freenet6 was OK. Just to clarify, I had to configure a hole in ipfw for freenet6.net too. I had just forgotten about it. :) -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RC3
On Fri, Mar 10, 2000 at 09:26:12PM +0200, Daniel Mpolokoso wrote: > I've managed to install RC3 without a hitch. The only problem I have is that > I can't get the XFree86 setup to configure X to run on my graphics hardware: > > pci0: at 1.0 irq 11 > > My Compaq desktop using the Intel 810e motherboard. > > Any pointers? This requires a special module that only works with Linux, AFAIK. I have no idea if an effort to port it exists. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured in rc.conf?
On Sat, Mar 11, 2000 at 05:22:09AM +0900, Yoshinobu Inoue wrote: > > I tried deleting the 6to4 address from an interface on the > > interior node and did a ping6, but I get no replies (I think > > you have to configure the route on your end first?). > > Yes, I have configured it, so it should work now. Yes, it does. It all looks good. PING6(56=40+8+8 bytes) c000::2a0:c9ff:feb1:23ae --> 3ffe:501:4819:2000:210:5aff:fe86:b65a 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=0 hlim=63 time=452.312 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=1 hlim=63 time=361.945 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=2 hlim=63 time=421.628 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=4 hlim=63 time=341.997 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=5 hlim=63 time=582.145 ms --- 3ffe:501:4819:2000:210:5aff:fe86:b65a ping6 statistics --- 7 packets transmitted, 5 packets received, 28% packet loss round-trip min/avg/max = 341.997/432.005/582.145 ms -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mylex Support
I have 4 different Mylex DAC960 controllers that I cannot install Current onto. (Tried from Late December to 2307). Sysinstall seems to get the geometry wrong, and even telling sysinstall the "correct" geometry, it gives a "tied to write beyond end of drive" error. Booting from a running -current and formatting does the same. They all have the latest BIOS, and they have been tried with various drive combinations. Has anyone else got this to work successfully or is it just me?. And if it is just me, anyone got any ideas? I have been pestering Mike Smith about this for ages, and have probably driven him mad! Lawrence Farr EPC Direct To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USA_RESIDENT and sysinstall
> I installed a -current snap from internat.freebsd.org that was built > with crypto source from internat. I answered yes when sysinstall asked > me if I want the crypto stuff, but then found that it marked me as an > USA_RESIDENT=YES in /etc/make.conf and it also asked me later if I > want to install the rsaref libraries. > > I think the test for USA_RESIDENT should be a bit more clever or the > message should be a bit more clear. At the moment it is: Yes, I screwed this up - I'm fixing it now! - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured inrc.conf?
> > By the way, I'm now very much interested in next round of > > test, that non 6to4 IPv6 prefix routing via 6to4 cloud. > > > > Could you please assign some non 6to4 prefix inside your > > environment? > > Ok. c000::/64 > > > route add -inet6 3ffe:501:4819:2000:: -prefixlen 64 2002:cbb2:8dd8::1 > > Did it on the router. > > > Then I believe I can ping to some of your non 6to4 addresses > > from my non 6to4 address. > > Try: > > c000::2a0:c9ff:feb1:23ae (border router) > c000::200:c0ff:fe34:41c6 (interior box) Either seems to be OK. % ping6 c000::2a0:c9ff:feb1:23ae PING6(56=40+8+8 bytes) 3ffe:501:4819:2000:200:eff:fe2e:def6 --> c000::2a0:c9ff:feb1:23ae 16 bytes from c000::2a0:c9ff:feb1:23ae, icmp_seq=0 hlim=62 time=1136.08 ms 16 bytes from c000::2a0:c9ff:feb1:23ae, icmp_seq=2 hlim=62 time=351.348 ms 16 bytes from c000::2a0:c9ff:feb1:23ae, icmp_seq=3 hlim=62 time=352.258 ms 16 bytes from c000::2a0:c9ff:feb1:23ae, icmp_seq=4 hlim=62 time=346.276 ms 16 bytes from c000::2a0:c9ff:feb1:23ae, icmp_seq=5 hlim=62 time=342.058 ms ^C --- c000::2a0:c9ff:feb1:23ae ping6 statistics --- 6 packets transmitted, 5 packets received, 16% packet loss round-trip min/avg/max = 342.058/505.603/1136.08 ms phoenix% ping6 c000::200:c0ff:fe34:41c6 PING6(56=40+8+8 bytes) 3ffe:501:4819:2000:200:eff:fe2e:def6 --> c000::200:c0ff:fe34:41c6 16 bytes from c000::200:c0ff:fe34:41c6, icmp_seq=0 hlim=63 time=385.097 ms 16 bytes from c000::200:c0ff:fe34:41c6, icmp_seq=1 hlim=63 time=372.819 ms 16 bytes from c000::200:c0ff:fe34:41c6, icmp_seq=2 hlim=63 time=361.545 ms ^C --- c000::200:c0ff:fe34:41c6 ping6 statistics --- 4 packets transmitted, 3 packets received, 25% packet loss round-trip min/avg/max = 361.545/373.153/385.097 ms > > Also, I think you can ping to my non > > 6to4 addr, 3ffe:501:4819:2000:210:5aff:fe86:b65a, from your > > non 6to4 address. > > I tried deleting the 6to4 address from an interface on the > interior node and did a ping6, but I get no replies (I think > you have to configure the route on your end first?). Yes, I have configured it, so it should work now. > Is > there a simpler way to force ping6 to use the non 6to4 > address as the source? Woops, ping6 don't have "-S" option. I also tried it from internal machine, and enabled the 6to4 machine as router. > I can ping6 your non 6to4 address from my 6to4 address, see > attached. Thanks, thus, this stf interface seems to be working very well. Also I believe, your machine can setup other gif tunnel to other IPv4 addr at the same time. It seems to be OK for my machine. The gif src addr and dst addr need to be explicitly defined, but the src addr can be same with stf interface addr. Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured in rc.conf?
On Sat, Mar 11, 2000 at 02:50:28AM +0900, Yoshinobu Inoue wrote: > By the way, I'm now very much interested in next round of > test, that non 6to4 IPv6 prefix routing via 6to4 cloud. > > Could you please assign some non 6to4 prefix inside your > environment? Ok. c000::/64 > route add -inet6 3ffe:501:4819:2000:: -prefixlen 64 2002:cbb2:8dd8::1 Did it on the router. > Then I believe I can ping to some of your non 6to4 addresses > from my non 6to4 address. Try: c000::2a0:c9ff:feb1:23ae (border router) c000::200:c0ff:fe34:41c6 (interior box) > Also, I think you can ping to my non > 6to4 addr, 3ffe:501:4819:2000:210:5aff:fe86:b65a, from your > non 6to4 address. I tried deleting the 6to4 address from an interface on the interior node and did a ping6, but I get no replies (I think you have to configure the route on your end first?). Is there a simpler way to force ping6 to use the non 6to4 address as the source? I can ping6 your non 6to4 address from my 6to4 address, see attached. -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 PING6(56=40+8+8 bytes) 2002:cc5f:bb02:0:2a0:c9ff:feb1:23ae --> 3ffe:501:4819:2000:210:5aff:fe86:b65a 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=0 hlim=63 time=530.244 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=1 hlim=63 time=360.666 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=2 hlim=63 time=360.621 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=3 hlim=63 time=410.744 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=4 hlim=63 time=350.658 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=5 hlim=63 time=350.743 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=6 hlim=63 time=350.836 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=7 hlim=63 time=350.761 ms --- 3ffe:501:4819:2000:210:5aff:fe86:b65a ping6 statistics --- 9 packets transmitted, 8 packets received, 11% packet loss round-trip min/avg/max = 350.658/383.159/530.244 ms
Re: single user mode problem
> > Regardless, this is typically syptomatic of either a very old > /boot/loader, non-use of the loader eg. through a /boot.config file, or > an error in the entry for / in /etc/fstab. > Isn't /boot/loader updated upon making a new world? If so, it ought to be current. I don't know any way of finding out since it's a binary file. /etc/fstab: /dev/ad0s4b noneswapsw 0 0 /dev/ad0s4a / ufs rw 1 1 /dev/ad0s4e /usrufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 /dev/ad0s1 /dosmsdos ro,noauto 0 0 proc/proc procfs rw 0 0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RC3
Hi, I've managed to install RC3 without a hitch. The only problem I have is that I can't get the XFree86 setup to configure X to run on my graphics hardware: pci0: at 1.0 irq 11 My Compaq desktop using the Intel 810e motherboard. Any pointers? Daniel. Daniel Mpolokoso - Managing Director (Act.),Email: [EMAIL PROTECTED] ZAMNET Communication Systems Limited, Phone: +260 - 1 - 763065 P.O. Box 38299, Lusaka, Zambia. Fax: +260 - 1 - 224775 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ida driver in -current and eisa bus attachment
On Fri, 10 Mar 2000, Alejandro Ramirez wrote: > > Note that I just committed some more changes to the IDA driver to > > 4.0-RC yesterday. The changes are: > > > > - support for EISA controllers (untested) > > - support for newer S2400 controllers (untested) > > - addition of IDA to the GENERIC kernel > > - support for installing directly onto the RAID array. > > Are there any plans to add some utility to configure (or reconfigure) the > array under FreeBSD??? The interfaces for configuring volumes aren't available from Compaq due to IP issues. Its possible that they might be reverse engineered. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RAID 5 Failure dumps all terminals
> We use A Mylex DAC960PD RAID 5 controller, attached to 7 > harddrives. One of the drives have had permanent failures, so > we changed it. Well, as I understand RAID 5, rebuilding the defective > drive should not involve the system, but On console (it ttyv0) I get > a message like "mlx0: error reading message log - invalid log entry request". The controller has told us that there's a message waiting for us, but when we go to get the message, it claims that it doesn't exist. The driver doesn't handle being lied to very well; you're probably getting a storm of these messages based on your followups. I'll take a look at this and see if I can reproduce it. > On all other ttyv* a logged in user (root) gets the same message > from kernel. Is this eloquence of the kernel and the mlx-driver a preliminary > feature or is the code still buggy, instable or anything else? I feel a little bit > confused about that, while other systems using RAID 5 are completely quiet > while rebuilding the defective and changed device. I have no idea what "other systems" you're talking about. I consider it prudent to log hardware failures, rather than letting them slip silently by. > On the other hand, how can I redirect console output to another console, on which > nobody never can log in (it should not be ttyv0)? How to prevent users and root > on some ttyv* from getting that much error messages, except on a bunch of > declared ttys? You would want to read the syslogd manpage, which will make this very standard part of your system's configuration somewhat clearer. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ida driver in -current and eisa bus attachment
> Hi Jonathan, > > > Note that I just committed some more changes to the IDA driver to > > 4.0-RC yesterday. The changes are: > > > > - support for EISA controllers (untested) > > - support for newer S2400 controllers (untested) > > - addition of IDA to the GENERIC kernel > > - support for installing directly onto the RAID array. > > Are there any plans to add some utility to configure (or reconfigure) the > array under FreeBSD??? Compaq claimed that the documentation necessary to do this was available, but it's not. I've tried to contact the individual that I spoke to about this, but he's not returning email or phone calls. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Alternative way to do -stable to -current upgrade
On Tue, 7 Mar 2000, Doug Barton wrote: > I've been meaning to post this for a while. I recently upgraded two way > old 4.0 systems to post-signal changes -current. It's not quite a 3.x -> > 4.0-Current upgrade, but it's close. I had to do a few things > differently than what's in Updating, and I wanted to test the > feasability of not going single user mode since I keep remote upgrades > in the back of my mind even though I don't do a lot of them anymore. > This is assuming that you've done all the right things with upgrading > sources, double-checked /etc/make.conf, using clean /usr/src, clean > /usr/obj, etc. > > 1. make buildworld > 2. make buildkernel > I actually updated my kernel config file while world was building so I > did 'make KERNEL=MYKERNELFILE buildkernel, and below, but that's not for > the faint of heart. As someone already pointed out, GENERIC is a better > choice, and doesn't require any options. > 3. make installkernel > 4. cd /usr/src/sbin/mknod && make install > I had to do this or the next step didn't work. > 5. cp /usr/src/etc/MAKEFILE /dev ; cd /dev ; /bin/sh MAKEFILE all > 6. Update /etc/fstab and new disk devices per instructions in Updating > 7. reboot > 8. make -k installworld > 9. make installworld > 10. mergemaster > 11. rebuilt my kernel (make sure to update your kernel config file) and > rebooted > > I did one system this way feeling my way through, then did another > following these instructions and didn't have any problems. I never had > to go single user, although these were workstation machines. For servers > you'd probably want to use /var/run/nologin, or similar. (Just make sure > you open plenty of shells for yourself first. :) > > I hope this is useful, > > Doug I just wanted to let you know that I used this procedure on a very recent 3.4-STABLE to -CURRENT upgrade and it worked flawlessly. The whole procedure was performed multi-user and remotely (the two boxes are sitting right next to each other though). I had been following the upgrade threads on -current and reading UPDATING, and this procedure appeared to be the most coherent I had seen. Thanks Doug. - Matt -- Matt Loschert [EMAIL PROTECTED] Software Engineer voice (703) 847-1381 ServInt Internet Services fax (703) 847-1383 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Again, RAID 5 failure ...
Well ... more confused! I posted some messages here before ... after I though the RAID has been rebuilt I tried to shutdown the server. On console I still got massive dumps of the same message, as I posted before. Shutdown was blocked, but I don't know by what, only thing to bring back the server alive was: power cycle. I think that's not in sensu strictu of what we understand when we say hot swap RAID 5? Gruss O. Hartmann --- [EMAIL PROTECTED] Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ida driver in -current and eisa bus attachment
On Fri, Mar 10, 2000 at 11:45:19AM -0600, Alejandro Ramirez wrote: > Hi Jonathan, > > > Note that I just committed some more changes to the IDA driver to > > 4.0-RC yesterday. The changes are: > > > > - support for EISA controllers (untested) > > - support for newer S2400 controllers (untested) > > - addition of IDA to the GENERIC kernel > > - support for installing directly onto the RAID array. > > Are there any plans to add some utility to configure (or reconfigure) the > array under FreeBSD??? Unfortunately, no. That would require documentation on the controller, and so far, Compaq hasn't shown any inclination to release information. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
> This has been going on for awhile, and I've looked everywhere for a > solution. When I boot single user, the / filesystem gets mounted on > wd0s4a even though /dev does not even have such an entry nor does > /etc/fstab, since these have all been updated. > This is not really such a problem until I try to exit from single user > mode. Then, it tries to remount / on ad0s4a and can't find it. Since there's no extra mounting activity that goes on on single-user mode vs. multi-user mode, I'm suspicious that you've probably gone and done something else as well that we're not hearing about. Regardless, this is typically syptomatic of either a very old /boot/loader, non-use of the loader eg. through a /boot.config file, or an error in the entry for / in /etc/fstab. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: inetd broken w/o INET6
> It appears inetd is broken if you don't have INET6 defined. This is > the case for picoBSD, for example: Woops, sorry. I'll reflect it. Thanks for the patches. Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured inrc.conf?
> > > 6to4 support seems to be very important for initial IPv6 > > > deployment on FreeBSD4.0, so I tried small additinal patches > > > to make it available. And It seems to work. > > > > > > Could some FreeBSD4.0 user with direct internet connectivity > > > please try this patches and try to ping6 to my host's 6to4 > > > address? > > > The procedure is, > > > > For the benefit of the lists, and confirming private mail I sent, > > ping6 works using the second of the patches sent (I didn't try the > > first). Thanks very much for your confirmations! > Ok. In addition to your instructions I also configured the > box as an IPv6 router (using the rc.conf switches) and > used a prefix of 2002:cc5f:bb02::0/64 on the interior > ethernet interface de0 with 2002:cc5f:bb02::1/16 on stf0. I'm > not sure if this is quite right. Maybe it is OK. > Anyway, I can ping6 to 2002:cbb2:8dd8::1 from my interior ipv6 > box as well as from the router box. I also configured DNS > for the two boxes, assigning ipv6 addresses to test.ipv6.tar.com > and ns.ipv6.tar.com. One of my DNS secondaries does not update > immediately on notification, so you might not get the ipv6 > resolution until it updates on schedule if you happen to query > that box. However, once all the secondaries are up, i hope > you can ping6 to both ns.ipv6.tar.com (router) and > test.ipv6.tar.com (interior). Yes I could successfully ping them! % ping6 test.ipv6.tar.com PING6(56=40+8+8 bytes) 2002:cbb2:8dd8::1 --> 2002:cc5f:bb02:0:2a0:c9ff:feb1:23ae 16 bytes from 2002:cc5f:bb02:0:2a0:c9ff:feb1:23ae, icmp_seq=0 hlim=63 time=715.85 ms 16 bytes from 2002:cc5f:bb02:0:2a0:c9ff:feb1:23ae, icmp_seq=1 hlim=63 time=426.515 ms ^C --- test.ipv6.tar.com ping6 statistics --- 3 packets transmitted, 2 packets received, 33% packet loss round-trip min/avg/max = 426.515/571.182/715.85 ms % ping6 ns.ipv6.tar.com PING6(56=40+8+8 bytes) 2002:cbb2:8dd8::1 --> 2002:cc5f:bb02:0:200:c0ff:fe34:41c6 16 bytes from 2002:cc5f:bb02:0:200:c0ff:fe34:41c6, icmp_seq=0 hlim=64 time=396.449 ms 16 bytes from 2002:cc5f:bb02:0:200:c0ff:fe34:41c6, icmp_seq=1 hlim=64 time=363.181 ms ^C --- ns.ipv6.tar.com ping6 statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 363.181/379.815/396.449 ms > I also had to adjust my ipv4 firewall rules to allow protocol > ipv6 through. Strange that I didn't have to do that when > doing a gif tunnel to freenet6.net. Also, what do I have to > do to enable ip6fw? Wmmm, it is strange that freenet6 was OK. About ip6fw, I think you can enable ip6fw over 6to4 by specifying "via stf" for each rules for IPv6. Here are some examples. (I belive following examples will work, but not tested yet.) If you want to allow 1:2:3::/48, add 10 allow ipv6 from 1:2:3:::/48 to any via stf* in add 15 allow ipv6 from any to 1:2:3::/48 via stf* out If you want to allow only ssh from 3:4:5::/48 outside to 6:7:8:9::/64 inside, (stf0 below can be stf*. Choosed it just for variety.) add 700 allow tcp from 3:4:5::/48 to 6:7:8:9::/64 ssh via stf0 in add 800 allow tcp from 6:7:8:9::/64 ssh to 3:4:5::/48 via stf0 out By the way, I'm now very much interested in next round of test, that non 6to4 IPv6 prefix routing via 6to4 cloud. Could you please assign some non 6to4 prefix inside your environment? If your non 6to4 prefix is 1:2:3:4::/64 for example, then I would like to configure a route for it, like below. route add -inet6 1:2:3:4:: -prefixlen 64 2002:cc5f:bb02::1 And my non 6to4 prefix is 3ffe:501:4819:2000::/64. So please assigne following route. route add -inet6 3ffe:501:4819:2000:: -prefixlen 64 2002:cbb2:8dd8::1 Then I believe I can ping to some of your non 6to4 addresses from my non 6to4 address. Also, I think you can ping to my non 6to4 addr, 3ffe:501:4819:2000:210:5aff:fe86:b65a, from your non 6to4 address. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
Out of da blue Jim Bloom aka ([EMAIL PROTECTED]) said: > Kris Kennaway wrote: > > > > On Thu, 9 Mar 2000, Bush Doctor wrote: > > > > > Again my libRSAglue libraries before the above were: > > > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* > > > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a > > > lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so -> >libRSAglue.so.1 > > > -r--r--r-- 1 root wheel5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 > > > -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a > > > > This was very helpful - I've been able to replicate the problem by install > > an old libRSAglue of this vintage. It still doesn't answer why on earth > > make world is trying to link with it, but at least now I have something to > > look at. Thanks! > > I looked into this problem a bit as well. > > I believe it is a build order and dependency problem that shouldn't > exist. libkrb is built before libRSAglue and then the shared library is > built with -LRSAglue which is only found in /usr/lib. > kerberosIV/Makefile.inc has a line "LDADD+= -LRSAglue". > > This whole issue should not exist simply because libRSAglue is a dummy > stub and there is no reson to link anything against it. The quick fix > is to remove libRSAglue from the makefiles where it is used. The > following makefiles need to have the references to RSAglue removed: Hmmm ..., I just helped a co-worker upgrade from -release to -current and he ran into a problem where 'make buildworld' failed in building Kerberos IV. I seem to recall a similiar problem a few weeks back on my -current box. I wound up commenting out the kerberos IV build in make.conf, performed a 'make buildworld' and 'make installworld' without kerberos IV, and rebuilt world afterwards with kerberos IV enabled. I really must be more proactive in reporting -current hiccups I come across :( Unfortunately, my co-worker has already overwritten the buildworld log :( > > usr.sbin/ppp/Makefile > usr.sbin/pppd/Makefile > secure/libexec/sshd/Makefile > kerberosIV/Makefile.inc > > I don't know how to change ld (compile time?) so that it doesn't look in > the standard locations for files during buildworld. That is what is > required to guarantee this problem doesn't happen again. > > Kris, would you like patches or will you edit these yourself? > > Jim Bloom > [EMAIL PROTECTED] #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ida driver in -current and eisa bus attachment
Hi Jonathan, > Note that I just committed some more changes to the IDA driver to > 4.0-RC yesterday. The changes are: > > - support for EISA controllers (untested) > - support for newer S2400 controllers (untested) > - addition of IDA to the GENERIC kernel > - support for installing directly onto the RAID array. Are there any plans to add some utility to configure (or reconfigure) the array under FreeBSD??? Greetings Ales To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
Jim Bloom wrote: > > The > following makefiles need to have the references to RSAglue removed: > > usr.sbin/ppp/Makefile > usr.sbin/pppd/Makefile > secure/libexec/sshd/Makefile > kerberosIV/Makefile.inc > Ignore secure/libexec/sshd/Makefile. That was left over from when I was trying to integrate OpenSSH into the base system before Mark's work was included. Jim Bloom [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
Kris Kennaway wrote: > > On Thu, 9 Mar 2000, Bush Doctor wrote: > > > Again my libRSAglue libraries before the above were: > > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* > > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a > > lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so -> >libRSAglue.so.1 > > -r--r--r-- 1 root wheel5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 > > -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a > > This was very helpful - I've been able to replicate the problem by install > an old libRSAglue of this vintage. It still doesn't answer why on earth > make world is trying to link with it, but at least now I have something to > look at. Thanks! I looked into this problem a bit as well. I believe it is a build order and dependency problem that shouldn't exist. libkrb is built before libRSAglue and then the shared library is built with -LRSAglue which is only found in /usr/lib. kerberosIV/Makefile.inc has a line "LDADD+= -LRSAglue". This whole issue should not exist simply because libRSAglue is a dummy stub and there is no reson to link anything against it. The quick fix is to remove libRSAglue from the makefiles where it is used. The following makefiles need to have the references to RSAglue removed: usr.sbin/ppp/Makefile usr.sbin/pppd/Makefile secure/libexec/sshd/Makefile kerberosIV/Makefile.inc I don't know how to change ld (compile time?) so that it doesn't look in the standard locations for files during buildworld. That is what is required to guarantee this problem doesn't happen again. Kris, would you like patches or will you edit these yourself? Jim Bloom [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
Out of da blue Kris Kennaway aka ([EMAIL PROTECTED]) said: > On Thu, 9 Mar 2000, Bush Doctor wrote: > > > Again my libRSAglue libraries before the above were: > > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* > > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a > > lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so -> >libRSAglue.so.1 > > -r--r--r-- 1 root wheel5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 > > -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a > > This was very helpful - I've been able to replicate the problem by install > an old libRSAglue of this vintage. It still doesn't answer why on earth > make world is trying to link with it, but at least now I have something to > look at. Thanks! You're welcome. I'm interested in what you find out. > > Kris > > > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe <[EMAIL PROTECTED]> > > #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
>
> > This has been going on for awhile, and I've looked everywhere for a
> > solution. When I boot single user, the / filesystem gets mounted on
> > wd0s4a even though /dev does not even have such an entry nor does
> > /etc/fstab, since these have all been updated.
> > This is not really such a problem until I try to exit from single user
> > mode. Then, it tries to remount / on ad0s4a and can't find it.
>
>
> Dear Joseph,
>
> as I have recently written, I met an analogous problem while upgrading
> to CURRENT: the "wdNsMa syndrome" appeared when I rebooted in s.u.m.
> with the shining gleaming roaring freshly-made 4.0-CURRENT kernel in
> order to (somehow) make installworld. Well, I did NOT care about it
> and I went ahead ruthlessly ...
>
> By the way, I made another kernel at the end of the process ("by the
> book"). I suppose (?) this cleared the problem. In fact, I was able to
> boot with no weird messages: all my filesystems were correctly
> identified as adNsM (e.g. ad1s2a, ad1s2e ...)
Hi Salvo,
I did read your recent post on this. For me, however, the problem
persists even with a new kernel. I've looked through all the boot and
init files for some clue as to where it's getting the idea that / is on
wd0s4a but I can't find anything ):-(.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: The pw command
On Fri, 10 Mar 2000, Paul Richards wrote: > So what I'm puzzled about now is how come yours is different and do we > think its correct that pwd.db and /etc/passwd have different information > in them? Oops, that was a cut-n-paste-o. I didn't notice the extra two fields the second time :-) It's for backwards-compatability, you're right. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mylex RAID 5 failure ...
Well, Iposted prior a message here because of the failure of our Mylex DAC960PD based RAID 5. After changing the faulty drive, the Mylex controller started rebuilding the defective drive (hot-swapped the drive). On console I got (and still get!) the message mlx0: error reading message log - invalid log entry request This message is still dumped out of the console although all activities on the RAID has been stopped and it seems to be 'repaired'. But the whole system is really slow now! what is going on? RAID 5 controller is Mylex DAC960PD mlx0: DAC960P/PD, 3 channels, firmware 3.51-0-12, 4MB RAM. The system is based on the cvsupdated source of Tuesday, 07th March. Gruss O. Hartmann --- [EMAIL PROTECTED] Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured in rc.conf?
On Fri, Mar 10, 2000 at 07:35:08AM -0600, Richard Seaman, Jr. wrote: > On Fri, Mar 10, 2000 at 08:09:04PM +0900, Yoshinobu Inoue wrote: > > > 6to4 support seems to be very important for initial IPv6 > > deployment on FreeBSD4.0, so I tried small additinal patches > > to make it available. And It seems to work. > > > > Could some FreeBSD4.0 user with direct internet connectivity > > please try this patches and try to ping6 to my host's 6to4 > > address? > > The procedure is, > > For the benefit of the lists, and confirming private mail I sent, > ping6 works using the second of the patches sent (I didn't try the > first). Ok. In addition to your instructions I also configured the box as an IPv6 router (using the rc.conf switches) and used a prefix of 2002:cc5f:bb02::0/64 on the interior ethernet interface de0 with 2002:cc5f:bb02::1/16 on stf0. I'm not sure if this is quite right. Anyway, I can ping6 to 2002:cbb2:8dd8::1 from my interior ipv6 box as well as from the router box. I also configured DNS for the two boxes, assigning ipv6 addresses to test.ipv6.tar.com and ns.ipv6.tar.com. One of my DNS secondaries does not update immediately on notification, so you might not get the ipv6 resolution until it updates on schedule if you happen to query that box. However, once all the secondaries are up, i hope you can ping6 to both ns.ipv6.tar.com (router) and test.ipv6.tar.com (interior). I also had to adjust my ipv4 firewall rules to allow protocol ipv6 through. Strange that I didn't have to do that when doing a gif tunnel to freenet6.net. Also, what do I have to do to enable ip6fw? -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
inetd broken w/o INET6
It appears inetd is broken if you don't have INET6 defined. This is
the case for picoBSD, for example:
> make -DRELEASE_CRUNCH
cc -O -pipe -Wall -DLOGIN_CAP -c /usr/source/src/usr.sbin/inetd/inetd.c
/usr/source/src/usr.sbin/inetd/inetd.c: In function `getconfigent':
/usr/source/src/usr.sbin/inetd/inetd.c:1594: syntax error before `else'
/usr/source/src/usr.sbin/inetd/inetd.c:1435: warning: unused variable `s'
/usr/source/src/usr.sbin/inetd/inetd.c:1434: warning: unused variable `argc'
/usr/source/src/usr.sbin/inetd/inetd.c: At top level:
/usr/source/src/usr.sbin/inetd/inetd.c:1601: syntax error before `->'
/usr/source/src/usr.sbin/inetd/inetd.c:1601: warning: type defaults to `int' in
declaration of
`se_family'
/usr/source/src/usr.sbin/inetd/inetd.c:1601: warning: data definition has no type or
storage class
/usr/source/src/usr.sbin/inetd/inetd.c:1602: syntax error before `}'
*** Error code 1
Stop in /usr/source/src/usr.sbin/inetd.
I've fixed this and another INET6-related warning with this patch:
Index: builtins.c
===
RCS file: /usr/cvs/src/usr.sbin/inetd/builtins.c,v
retrieving revision 1.17
diff -u -r1.17 builtins.c
--- builtins.c 2000/01/25 14:52:09 1.17
+++ builtins.c 2000/03/10 15:13:35
@@ -335,7 +335,9 @@
struct utsname un;
struct stat sb;
struct sockaddr_in sin[2];
+#ifdef INET6
struct sockaddr_in6 sin6[2];
+#endif
struct sockaddr_storage ss[2];
struct ucred uc;
struct timeval tv = {
Index: inetd.c
===
RCS file: /usr/cvs/src/usr.sbin/inetd/inetd.c,v
retrieving revision 1.79
diff -u -r1.79 inetd.c
--- inetd.c 2000/02/22 00:27:53 1.79
+++ inetd.c 2000/03/10 15:13:08
@@ -1590,8 +1590,8 @@
if (v4bind == 0 || no_v4bind != 0)
sep->se_nomapped = 1;
}
-#endif
else { /* default to v4 bind if not v6 bind */
+#endif
if (no_v4bind != 0) {
syslog(LOG_INFO, "IPv4 bind is ignored for %s",
sep->se_service);
@@ -1599,7 +1599,9 @@
goto more;
}
sep->se_family = AF_INET;
+#ifdef INET6
}
+#endif
/* init ctladdr */
switch(sep->se_family) {
case AF_INET:
This patch can also be found at
http://people.FreeBSD.org/~jhb/patches/inetd.patch
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.cslab.vt.edu/~jobaldwi/
PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RC3
A couple of comments on the RC3 CD image. 1) I tried to install by moving things out od the way: cd /;mkdir save;mv * save;cd /usr;mkdir save;mv * save and then boot from CD. Because I did not newfs /, it assumed /dev was built and failed. 2) When I tried to install CRYPTO from the CD I got errors for a number of them, something about not being able to read a script of something (it was 2am so I do not have the exact error message), so i installed from FTP. 3) First time i declined DES because I did not want DES passwords, hoping it would install crypto (ssl, ssh) or would ask me. Over the install went well, I will finish configuring tonight and see how it goes. Brian Beattie| This email was produced using professional quality, [EMAIL PROTECTED] | standards based software. Users of Microsoft [EMAIL PROTECTED] | products or other substandard software should www.aracnet.com/~beattie | contact the author about receiving a Free upgrade to | FreeBSD or Linux. "FreeBSD: The power to serve" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ida driver in -current and eisa bus attachment
In article you write: >> > Work on this driver is stalled owing to the fact that nobody that can >and >> > wants to work on it has access to the Compaq hardware required. You >> > can't use these controllers except in Compaq systems, which makes things >> > very difficult. >> that's true :-( > >Again I would like to point out, that only the newest controllers, 3200 and >up is difficult getting to work in non-Compaq systems: > >http://seeberg.dk/freebsd/idaraid Note that I just committed some more changes to the IDA driver to 4.0-RC yesterday. The changes are: - support for EISA controllers (untested) - support for newer S2400 controllers (untested) - addition of IDA to the GENERIC kernel - support for installing directly onto the RAID array. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RAID 5 Failure dumps all terminals
We use A Mylex DAC960PD RAID 5 controller, attached to 7 harddrives. One of the drives have had permanent failures, so we changed it. Well, as I understand RAID 5, rebuilding the defective drive should not involve the system, but On console (it ttyv0) I get a message like "mlx0: error reading message log - invalid log entry request". On all other ttyv* a logged in user (root) gets the same message from kernel. Is this eloquence of the kernel and the mlx-driver a preliminary feature or is the code still buggy, instable or anything else? I feel a little bit confused about that, while other systems using RAID 5 are completely quiet while rebuilding the defective and changed device. On the other hand, how can I redirect console output to another console, on which nobody never can log in (it should not be ttyv0)? How to prevent users and root on some ttyv* from getting that much error messages, except on a bunch of declared ttys? Thanks in advance ... Gruss O. Hartmann --- [EMAIL PROTECTED] Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The pw command
Kris Kennaway wrote: > > On Fri, 10 Mar 2000, Paul Richards wrote: > > > Non-root users can use the pw command to get information from the > > master.passwd file e.g. > > > > ps showuser paul > > paul:*:1000:1000::0:0:& Richards:/home/paul:/usr/local/bin/bash > > % pw showuser kkenn > > kkenn:*:1000:0::0:0:Kris Kennaway:/home/kkenn:/usr/local/bin/tcsh > > % grep kkenn /etc/passwd > > kkenn:*:1000:0::0:0:Kris Kennaway:/home/kkenn:/usr/local/bin/tcsh > > % ls -l /usr/bin/pw > -r-xr-xr-x 1 root wheel 53180 Mar 4 00:49 /usr/sbin/pw* > > In other words, pw(8) runs with no special privileges and can only read > what the user can normally read. Ok, as Mike mentioned in his email pw gets its info from pwd.db, I knew that. What I had assumed was that pwd.db was the same as the contents of /etc/passwd. I spent most of last night trying to work out how a non-root user was getting access to master.passwd based on that flawed assumption :-) My /etc/passwd does not have the class and expiry fields in it. I've deleted it and let it be recreated and it still doesn't have those fields. I've browsed through the code in pwd_mkdb and it looks to me like it deliberately creates the old style /etc/passwd file, which makes sense from a comatibility perspective. So what I'm puzzled about now is how come yours is different and do we think its correct that pwd.db and /etc/passwd have different information in them? Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured in rc.conf?
On Fri, Mar 10, 2000 at 08:09:04PM +0900, Yoshinobu Inoue wrote: > 6to4 support seems to be very important for initial IPv6 > deployment on FreeBSD4.0, so I tried small additinal patches > to make it available. And It seems to work. > > Could some FreeBSD4.0 user with direct internet connectivity > please try this patches and try to ping6 to my host's 6to4 > address? > The procedure is, For the benefit of the lists, and confirming private mail I sent, ping6 works using the second of the patches sent (I didn't try the first). -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feedback on 4.0-RC3 (mostly good! :)
John Reynolds wrote: > 1) There is a typo (spelling error) in one of the dialogs I was presented. I > was trying to force pilot error into the situation :) and got a dialog that > contained the following line: > > "You can also chose "No" at the next prompt and go back into the > installation menus to try and retry whichever operations failed." > > The word "chose" should be "choose." I'd supply a patch, but I only > installed kernel source :( > Also, this sentence should either have "try and" removed or replaced with "attempt to". Either of these is much better grammatically. Jim Bloom [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
[EMAIL PROTECTED] (FreeBSD mailing list) writes: > You know people, it's quite sad that those with knowledge simply > refuse to answer simple questions without "RTFM" attitudes and > indirect (and more frequently direct) insults to intelligence and > sensibilities. The answer `run mergemaster' will work for the next, similar, problem. The answer you gave won't work for anything but ssh. kai -- ~/.signature: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPv6: can a link-site (or global) address be configured inrc.conf?
> And here is the patches.
The last patches should work but I found a improvement related
to coexistence with gif, so this is the updated patches.
Thanks,
Yoshinobu Inoue
Index: net/if_gif.c
===
RCS file: /home/ncvs/src/sys/net/if_gif.c,v
retrieving revision 1.3
diff -u -r1.3 if_gif.c
--- net/if_gif.c2000/02/27 18:36:30 1.3
+++ net/if_gif.c2000/03/10 11:32:38
@@ -83,7 +83,7 @@
/*
* gif global variable definitions
*/
-int ngif = NGIF; /* number of interfaces */
+int ngif = NGIF + 1; /* number of interfaces. +1 for stf. */
struct gif_softc *gif = 0;
void
@@ -95,7 +95,7 @@
gif = sc = malloc (ngif * sizeof(struct gif_softc), M_DEVBUF, M_WAIT);
bzero(sc, ngif * sizeof(struct gif_softc));
- for (i = 0; i < ngif; sc++, i++) {
+ for (i = 0; i < ngif - 1; sc++, i++) { /* leave last one for stf */
sc->gif_if.if_name = "gif";
sc->gif_if.if_unit = i;
sc->gif_if.if_mtu= GIF_MTU;
@@ -107,6 +107,16 @@
if_attach(&sc->gif_if);
bpfattach(&sc->gif_if, DLT_NULL, sizeof(u_int));
}
+ sc->gif_if.if_name = "stf";
+ sc->gif_if.if_unit = 0;
+ sc->gif_if.if_mtu= GIF_MTU;
+ sc->gif_if.if_flags = IFF_MULTICAST;
+ sc->gif_if.if_ioctl = gif_ioctl;
+ sc->gif_if.if_output = gif_output;
+ sc->gif_if.if_type = IFT_GIF;
+ sc->gif_if.if_snd.ifq_maxlen = ifqmaxlen;
+ if_attach(&sc->gif_if);
+ bpfattach(&sc->gif_if, DLT_NULL, sizeof(u_int));
}
PSEUDO_SET(gifattach, if_gif);
@@ -322,6 +332,11 @@
/* only one gif can have dst = INADDR_ANY */
#definesatosaddr(sa) (((struct sockaddr_in *)(sa))->sin_addr.s_addr)
+
+#ifdef INET6
+ if (bcmp(ifp->if_name, "stf", 3) == 0)
+ satosaddr(dst) = INADDR_BROADCAST;
+#endif
if (satosaddr(dst) == INADDR_ANY) {
int i;
Index: netinet/in_gif.c
===
RCS file: /home/ncvs/src/sys/netinet/in_gif.c,v
retrieving revision 1.3
diff -u -r1.3 in_gif.c
--- netinet/in_gif.c1999/12/22 19:13:18 1.3
+++ netinet/in_gif.c2000/03/10 11:32:38
@@ -84,6 +84,9 @@
SYSCTL_INT(_net_inet_ip, IPCTL_GIF_TTL, gifttl, CTLFLAG_RW,
&ip_gif_ttl,0, "");
+#define IN6_IS_ADDR_6TO4(x)(ntohs((x)->s6_addr16[0]) == 0x2002)
+#define GET_V4(x) ((struct in_addr *)(&(x)->s6_addr16[1]))
+
int
in_gif_output(ifp, family, m, rt)
struct ifnet*ifp;
@@ -98,6 +101,9 @@
struct ip iphdr;/* capsule IP header, host byte ordered */
int proto, error;
u_int8_t tos;
+#ifdef INET6
+ struct ip6_hdr *ip6 = NULL;
+#endif
if (sin_src == NULL || sin_dst == NULL ||
sin_src->sin_family != AF_INET ||
@@ -124,7 +130,6 @@
#ifdef INET6
case AF_INET6:
{
- struct ip6_hdr *ip6;
proto = IPPROTO_IPV6;
if (m->m_len < sizeof(*ip6)) {
m = m_pullup(m, sizeof(*ip6));
@@ -147,6 +152,24 @@
bzero(&iphdr, sizeof(iphdr));
iphdr.ip_src = sin_src->sin_addr;
+#ifdef INET6
+ /* XXX: temporal stf support hack */
+ if (bcmp(ifp->if_name, "stf", 3) == 0 && ip6 != NULL) {
+ if (IN6_IS_ADDR_6TO4(&ip6->ip6_dst))
+ iphdr.ip_dst = *GET_V4(&ip6->ip6_dst);
+ else if (rt && rt->rt_gateway->sa_family == AF_INET6) {
+ struct in6_addr *dst6;
+
+ dst6 = &((struct sockaddr_in6 *)
+(rt->rt_gateway))->sin6_addr;
+ if (IN6_IS_ADDR_6TO4(dst6))
+ iphdr.ip_dst = *GET_V4(dst6);
+ } else {
+ m_freem(m);
+ return ENETUNREACH;
+ }
+ } else
+#endif
if (ifp->if_flags & IFF_LINK0) {
/* multi-destination mode */
if (sin_dst->sin_addr.s_addr != INADDR_ANY)
@@ -232,6 +255,19 @@
if ((sc->gif_if.if_flags & IFF_UP) == 0)
continue;
+
+#ifdef INET6
+ /* XXX: temporal stf support hack */
+ if (proto == IPPROTO_IPV6 &&
+ bcmp(sc->gif_if.if_name, "stf", 3) == 0 &&
+ satosin(sc->gif_psrc)->sin_addr.s_addr ==
+ ip->ip_dst.s_addr &&
+ satosin(sc->gif_pdst)->sin_addr.s_addr ==
+ INADDR_BROADCAST) {
+ gifp = &sc->gif_if;
+ break;
+ }
+#endif
if ((sc->gif_if.if_flags & IFF_LINK0)
&& satosin(sc->gif_psrc)->sin_addr.s_addr == ip->ip_dst.s_addr
To Unsubscribe: send mail to
Re: IPv6: can a link-site (or global) address be configured inrc.conf?
> >Very unfortunately, 6to4 is not yet supported in FreeBSD/KAME.
> >So now available options will be,
> > -Use freenet6 (for one hosts).
> > -Get IPv6 address block and connect to 6bone using gif tunnel.
>
> We hope to add 6to4 support for KAME/FreeBSD very soon (next week is a
> good guess). We may need some more testing before real use,
> but it should work. it is in KAME/NetBSD already, I just don't have
> time to make it work on othre *BSDs yet...
6to4 support seems to be very important for initial IPv6
deployment on FreeBSD4.0, so I tried small additinal patches
to make it available. And It seems to work.
Could some FreeBSD4.0 user with direct internet connectivity
please try this patches and try to ping6 to my host's 6to4
address?
The procedure is,
(1)apply this patch and rebuild your kernel
(2)configure 6to4 interface
I suppose that your IPv4 address is 1.2.3.4
-configure stf interface's outer addr, using gifconfig
gifconfig stf0 1.2.3.4 255.255.255.255
(The destination IPv4 addr can be anything.)
-encode your IPv4 address to hex format per 2 byte, for
later use
If it is 1.2.3.4, then it will be, 0102:0304.
-encode your IPv6 address on stf interface, for later
configuration
The format is, like below.
2002: 4byte v4 addr : 2byte SLA ID : 8byte interface ID
For simplicity, I choose 0 for SLA ID, and 1 for interface ID.
Then, if your IPv4 addr is 1.2.3.4, then your IPv6 addr on stf is,
2002:0102:0304::1
-configure stf interface's IPv6 addr
Please use ifconfig.
ifconfig stf0 inet6 2002:0102:0304::1 prefixlen 16
(3)try pinging to my host's 6to4 address
My machine's 6to4 address is 2002:cbb2:8dd8::1.
Please try,
ping6 2002:cbb2:8dd8::1
I hope there is reply from my machine.
And here is the patches.
Thanks,
Yoshinobu Inoue
Index: net/if_gif.c
===
RCS file: /home/ncvs/src/sys/net/if_gif.c,v
retrieving revision 1.3
diff -u -r1.3 if_gif.c
--- net/if_gif.c2000/02/27 18:36:30 1.3
+++ net/if_gif.c2000/03/10 10:09:25
@@ -83,7 +83,7 @@
/*
* gif global variable definitions
*/
-int ngif = NGIF; /* number of interfaces */
+int ngif = NGIF + 1; /* number of interfaces. +1 for stf. */
struct gif_softc *gif = 0;
void
@@ -95,7 +95,7 @@
gif = sc = malloc (ngif * sizeof(struct gif_softc), M_DEVBUF, M_WAIT);
bzero(sc, ngif * sizeof(struct gif_softc));
- for (i = 0; i < ngif; sc++, i++) {
+ for (i = 0; i < ngif - 1; sc++, i++) { /* leave last one for stf */
sc->gif_if.if_name = "gif";
sc->gif_if.if_unit = i;
sc->gif_if.if_mtu= GIF_MTU;
@@ -107,6 +107,16 @@
if_attach(&sc->gif_if);
bpfattach(&sc->gif_if, DLT_NULL, sizeof(u_int));
}
+ sc->gif_if.if_name = "stf";
+ sc->gif_if.if_unit = 0;
+ sc->gif_if.if_mtu= GIF_MTU;
+ sc->gif_if.if_flags = IFF_MULTICAST;
+ sc->gif_if.if_ioctl = gif_ioctl;
+ sc->gif_if.if_output = gif_output;
+ sc->gif_if.if_type = IFT_GIF;
+ sc->gif_if.if_snd.ifq_maxlen = ifqmaxlen;
+ if_attach(&sc->gif_if);
+ bpfattach(&sc->gif_if, DLT_NULL, sizeof(u_int));
}
PSEUDO_SET(gifattach, if_gif);
@@ -322,6 +332,11 @@
/* only one gif can have dst = INADDR_ANY */
#definesatosaddr(sa) (((struct sockaddr_in *)(sa))->sin_addr.s_addr)
+
+#ifdef INET6
+ if (bcmp(ifp->if_name, "stf", 3) == 0)
+ satosaddr(dst) = INADDR_BROADCAST;
+#endif
if (satosaddr(dst) == INADDR_ANY) {
int i;
Index: netinet/in_gif.c
===
RCS file: /home/ncvs/src/sys/netinet/in_gif.c,v
retrieving revision 1.3
diff -u -r1.3 in_gif.c
--- netinet/in_gif.c1999/12/22 19:13:18 1.3
+++ netinet/in_gif.c2000/03/10 10:09:25
@@ -84,6 +84,9 @@
SYSCTL_INT(_net_inet_ip, IPCTL_GIF_TTL, gifttl, CTLFLAG_RW,
&ip_gif_ttl,0, "");
+#define IN6_IS_ADDR_6TO4(x)(ntohs((x)->s6_addr16[0]) == 0x2002)
+#define GET_V4(x) ((struct in_addr *)(&(x)->s6_addr16[1]))
+
int
in_gif_output(ifp, family, m, rt)
struct ifnet*ifp;
@@ -98,6 +101,9 @@
struct ip iphdr;/* capsule IP header, host byte ordered */
int proto, error;
u_int8_t tos;
+#ifdef INET6
+ struct ip6_hdr *ip6 = NULL;
+#endif
if (sin_src == NULL || sin_dst == NULL ||
sin_src->sin_family != AF_INET ||
@@ -124,7 +130,6 @@
#ifdef INET6
case AF_INET6:
{
- struct ip6_hdr *ip6;
proto = IPPROTO_IPV6;
if (m->m_len < sizeof(*ip6)) {
m = m_pullup(m,
USA_RESIDENT and sysinstall
Hi, I installed a -current snap from internat.freebsd.org that was built with crypto source from internat. I answered yes when sysinstall asked me if I want the crypto stuff, but then found that it marked me as an USA_RESIDENT=YES in /etc/make.conf and it also asked me later if I want to install the rsaref libraries. I think the test for USA_RESIDENT should be a bit more clever or the message should be a bit more clear. At the moment it is: Do you wish to install cryptographic software? If you choose No, FreeBSD will use an MD5 based password scheme which, while perhaps more secure, is not interoperable with the traditional DES-based passwords on other Unix systems. There will also be some differences in the type of RSA code you use. Please do NOT choose Yes at this point if you are outside the United States and Canada and are installing from a U.S. FTP server. Instead, install everything but the crypto bits from the U.S. site and then switch to an international FTP server to install crypto on a second pass with the Custom Installation option. Maybe we can have some kind of flag in the crypto distribution to mark if it is USA or non-USA and use that to decide how to set USA_RESIDENT or maybe someone clever enough can figure out if the dowloaded crypto libraries still need rsaref and use that to set it? Also it would be nice to have an option to install the crypto ditribution (to get openssh) but still have md5 passwords, ie. the libcrypt.* links don't get extracted out of the crypto distribution or something can just link them back to libscrypt.*. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
3.4 vs. 4.0 NFS Code performance
Hi, I need to use a quite big NFS server, serving ~120GB for ~200 clients, all OS's mixed (*BSD, Linux, HP-UX, IRIX, Solaris, Xterminals). Is it worth it to use the -current branch (-release on next monday perhaps?) for this important server, or should I rather use the 3.4-STABLE NFS implementation ? Thanks for all the tips you could give me. Jerome Oufella Network administration team ESIL To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ida driver in -current and eisa bus attachment
> > Work on this driver is stalled owing to the fact that nobody that can and > > wants to work on it has access to the Compaq hardware required. You > > can't use these controllers except in Compaq systems, which makes things > > very difficult. > that's true :-( Again I would like to point out, that only the newest controllers, 3200 and up is difficult getting to work in non-Compaq systems: http://seeberg.dk/freebsd/idaraid To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
>> Original Message <<
On 3/10/00, 9:51:06 AM, R Joseph Wright <[EMAIL PROTECTED]> wrote
regarding single user mode problem:
> This has been going on for awhile, and I've looked everywhere for a
> solution. When I boot single user, the / filesystem gets mounted on
> wd0s4a even though /dev does not even have such an entry nor does
> /etc/fstab, since these have all been updated.
> This is not really such a problem until I try to exit from single user
> mode. Then, it tries to remount / on ad0s4a and can't find it.
Dear Joseph,
as I have recently written, I met an analogous problem while upgrading
to CURRENT: the "wdNsMa syndrome" appeared when I rebooted in s.u.m.
with the shining gleaming roaring freshly-made 4.0-CURRENT kernel in
order to (somehow) make installworld. Well, I did NOT care about it
and I went ahead ruthlessly ...
By the way, I made another kernel at the end of the process ("by the
book"). I suppose (?) this cleared the problem. In fact, I was able to
boot with no weird messages: all my filesystems were correctly
identified as adNsM (e.g. ad1s2a, ad1s2e ...)
HTH,
Salvo
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
On Thu, 9 Mar 2000, Bush Doctor wrote: > Again my libRSAglue libraries before the above were: > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a > lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so -> >libRSAglue.so.1 > -r--r--r-- 1 root wheel5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 > -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a This was very helpful - I've been able to replicate the problem by install an old libRSAglue of this vintage. It still doesn't answer why on earth make world is trying to link with it, but at least now I have something to look at. Thanks! Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP on Alpha?
On Fri, 10 Mar 2000, Peter Jeremy wrote: > On 2000-Mar-10 12:06:18 +1100, Mikhail Teterin <[EMAIL PROTECTED]> wrote: > >Will the -current version of FreeBSD run on a multi-CPU axp machine and > >use all of the CPUs? > > Not yet, but Real Soon Now. > > > Would that be a reliable box (assuming the admin > >sometimes knows what he is doing)? > > -current comes with all the usual `not for production use' caveats, > and (without any slur on Doug Rabson, who's doing the work), you'd > be very game taking FreeBSD's first cut at Alpha/SMP and putting it > into production. On the other hand, a uniprocessor alpha has a decent amount of horsepower and should be suitable for use in production. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
