Re: Problems with nlist on -current?
Bernd Luevelsmeyer wrote: > > Dampure, Pierre Y. wrote: > > > > I installed 5.0-2621-CURRENT on a new system (OR840, 2x733EB, 512MB > > RDRAM) and had problems with top / systat / vmstat all failing after > > reporting problems with nlist: > [...] > > At a guess, you don't use /boot/loader? > The loader seems to be no longer optional, see > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17422 > > This problem has been discussed several times in the "questions" mailing > list, and R. Ermilov kindly mailed 2 patches: > >http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=1186602+1196206+/usr/local/www/db/text/2000/freebsd-questions/2409.freebsd-questions > > (While I'm at it, may I suggest that the patches be committed? I'm using > them for more than a month now on 4.0-Stable, and they work just fine.) My system has 4 SCSI disks, W2K on disk 0, FreeBSD on 1, 2 and 3 (FreeBSD Multiboot installed on disk 0; disks 1, 2 and 3 all in dedicated mode). At boot time, boo2 throws out a 'No /boot/loader' messages, then proceeds to load the kernel normally. So... I guess indeed I do not use /boot/loader, though not of my own will. Thanks for the pointers! PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Vendor import of Perl 5.6
> This indicates to me that configpm is not reading Config.pm from the obj > directory, which does contain the correct value that configpm is looking > for at line 433. > > I'm not sure what the fix is, but hopefully this'll help mark down the > road. Thanks! You're building threads, right? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help! can't 'startx' - missing libc.so
On Mon, Jun 26, 2000 at 12:54:53AM -0400, John Daniels wrote: > Thanks everyone. I'll try your suggestions. Including using a mailing list that is appropriate for your version of FreeBSD (4.x is -stable, not -current) and your subject matter (this is questions@) material in the future, right? -- Bill Fumerola - Network Architect / Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
On Mon, 26 Jun 2000, Mark Murray wrote: > > That's okay with me too. People should just not upgrade their work > > machines for the next few days until entropy is fixed. > > Upgrading is fine; just don't build certificates/credentials. Or use ssh 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: HEADS UP! New (incomplete) /dev/random device!
> On Sun, 25 Jun 2000, Warner Losh wrote: > > > Some days is OK, imho. Much more than that and I'd begin to worry. > > Much more than a week or two and I'd worry a lot. I'll go put a note > > in updating right now. > > That's okay with me too. People should just not upgrade their work > machines for the next few days until entropy is fixed. Upgrading is fine; just don't build certificates/credentials. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
Kris Kennaway wrote: > > On Sun, 25 Jun 2000, Warner Losh wrote: > > > Some days is OK, imho. Much more than that and I'd begin to worry. > > Much more than a week or two and I'd worry a lot. I'll go put a note > > in updating right now. > > That's okay with me too. People should just not upgrade their work > machines for the next few days until entropy is fixed. It would be interesting to see how many people are using FreeBSD-current as a "work" machine, if you mean "work" to be a production machine doing actual server work. A lot of times, -current has been pretty stable for me, and I avoided a lot of "make world" and stability problems by following what's going on in this mailing list. I've only had a couple problems over the past 3 1/2 years with stability in FreeBSD-current, starting with 3.0-current. Granted, it's not generally recommended to use -current boxes as your main machine, but if you're careful, it's doable. I say FreeBSD-current makes a pretty decent production machine if the admin is smart enough to follow the mailing list and is knowledegeable enough to recognize the pitfalls of running such a beast. All others should be running 4.0-release or -stable, of course. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help! can't 'startx' - missing libc.so
On Mon, 26 Jun 2000, John Daniels wrote: >Hi: > > >>From: Adam <[EMAIL PROTECTED]> >>Try installing the compat3x distribution portion of freebsd >> >You are the second person who has suggested this. How can I best do this? >I don't have a CD, but I did keep some system sources. (but I think it >might've only been 'kernel source'). Is it possible to 1) ftp the file, 2) >compile it from /usr/src/lib/libc, (if the souce is there)? Do you have a net connect? If so, ftp to ftp.freebsd.org/pub/FreeBSD in your version dir, look for compat3x, grab the files in the dir, and run the .sh. If you have a direct connect, run /stand/sysinstall and goto configure, distributions. 2) no. it would compile libc.so.4 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help! can't 'startx' - missing libc.so
Using /stand/sysinstall to (re-) install compat3x solved the problem! It was really pretty quick and easy. Thanks again, everyone! John Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with nlist on -current?
Dampure, Pierre Y. wrote: > > I installed 5.0-2621-CURRENT on a new system (OR840, 2x733EB, 512MB > RDRAM) and had problems with top / systat / vmstat all failing after > reporting problems with nlist: [...] At a guess, you don't use /boot/loader? The loader seems to be no longer optional, see http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17422 This problem has been discussed several times in the "questions" mailing list, and R. Ermilov kindly mailed 2 patches: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=1186602+1196206+/usr/local/www/db/text/2000/freebsd-questions/2409.freebsd-questions (While I'm at it, may I suggest that the patches be committed? I'm using them for more than a month now on 4.0-Stable, and they work just fine.) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help! can't 'startx' - missing libc.so
Thanks everyone. I'll try your suggestions. John Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
I'm catching up on email, sorry if this was answered... are you talking OBP/Forth on Suns? Try ok sifting foo to get a list of words with foo in them (kinda like grep foo). Try ok see foo to see the details of the word (if you get forth this will help.) If you're not doing forth/obp... my apologies for the irrelevancy. Mike Williams Mike Smith wrote: > > Uh, 'help' doesn't give you a list of commands I believe. > > Damn, it doesn't either. 'help' is the same as 'help help'. > > Suggestions for a better replacement for ? 'commands'? > > -- > \\ 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help! can't 'startx' - missing libc.so
On Mon, 26 Jun 2000, John Daniels wrote: >Hi: > > >>From: Adam <[EMAIL PROTECTED]> >>Try installing the compat3x distribution portion of freebsd >> >You are the second person who has suggested this. How can I best do this? >I don't have a CD, but I did keep some system sources. (but I think it >might've only been 'kernel source'). Is it possible to 1) ftp the file, 2) >compile it from /usr/src/lib/libc, (if the souce is there)? > >John Run /stand/sysinstall, go to the Post-Install Configuration menu, select Install additional FreeBSD distribution sets, and when asked for a media type, select FTP. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Config problems
Well, I think maybe you have to put a number in if you want stuff wired down.. but basically I'm not sure if all the kinks have been worked out yet... = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 25 Jun 2000, Chuck Robey wrote: > On Sun, 25 Jun 2000, Kenneth Wayne Culver wrote: > > > Hey chuck, except for the SMP stuff, your config looks mostly like mine (I > > only have a cpu line for i686) Let me know if there's anything I can do to > > help though. > > I'm about ready to post again, so this is good timing. > > I got the totally vague warning from gethints.pl to quiet by making my > disk section look much like the NOTES file. I then ran it by a brand new > config, and out spewed more than 25 errors. The entire section on wiring > down disks fails, and also all the stuff on npx, even tho that part was > copied verbatim from NOTES. > > I have an Adaptec dual channel controller on my motherboard, and I have 3 > disks and 2 cdroms, which I want to wire down. There's lines in the NOTES > examples whose meanings just make no sense to me. Let me do a bit of > quoting: > > [from NOTES] > hint.scbus.0.at="ahc0" > hint.scbus.1.at="ahc1" > hint.scbus.1.bus="0" > hint.scbus.3.at="ahc2" > hint.scbus.3.bus="0" > hint.scbus.2.at="ahc2" > hint.scbus.2.bus="1" > hint.da.0.at="scbus0" > hint.da.0.target="0" > hint.da.0.unit="0" > hint.da.1.at="scbus3" > hint.da.1.target="1" > hint.da.2.at="scbus2" > hint.da.2.target="3" > hint.sa.1.at="scbus1" > hint.sa.1.target="6" > > > What does ``hint.scbus.1.bus="0"'' mean? Do I have to stick a number > after the "device ahc" and "device scbus" lines (the NOTES file > doesn't). Are there any other oddities I ought to know of? > > > Chuck Robey| Interests include C & Java programming, FreeBSD, > [EMAIL PROTECTED] | electronics, communications, and signal processing. > > New Year's Resolution: I will not sphroxify gullible people into looking up > fictitious words in the dictionary. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help! can't 'startx' - missing libc.so
/stand/sysinstall go to the post install configure option then to Distribution sets and then to 3x compat libraries. It will prompt you to choose your install preference.FTP, CDROM, etc. On 26 Jun 2000, at 0:36, John Daniels wrote: > Hi: > > > >From: Adam <[EMAIL PROTECTED]> > >Try installing the compat3x distribution portion of freebsd > > > You are the second person who has suggested this. How can I best do this? > I don't have a CD, but I did keep some system sources. (but I think it > might've only been 'kernel source'). Is it possible to 1) ftp the file, 2) > compile it from /usr/src/lib/libc, (if the souce is there)? > > John > > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com > > > > 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
Re: Help! can't 'startx' - missing libc.so
Hi: >From: Adam <[EMAIL PROTECTED]> >Try installing the compat3x distribution portion of freebsd > You are the second person who has suggested this. How can I best do this? I don't have a CD, but I did keep some system sources. (but I think it might've only been 'kernel source'). Is it possible to 1) ftp the file, 2) compile it from /usr/src/lib/libc, (if the souce is there)? John Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help! can't 'startx' - missing libc.so
Try installing the compat3x distribution portion of freebsd On Sun, 25 Jun 2000, John Daniels wrote: >Hi: > >I apologize for posting this to -current, but I really need to know how bad >the damage is ASAP because I may need to reinstall. > >When I type 'startx' I get a message that libc.so.3 cannot be found and also >a note about /usr/libexec/ld-elf.so.1 > >I'm not sure how these two files are related. Is libc.so.3 contained in >ld-elf.so, or called from it? > >I'm not sure what happened to this file(s) but I did a 'make' on XFree86 to >see if the file(s) are produced there, but they don't seem to be a part of >XFree86. I believe that libc.so may be a C-library provided by the system, >and I may need to either ftp a new one or install a new system. > >Any help is very welcome. > >John > > >Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com > > > >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
Re: Help! can't 'startx' - missing libc.so
Hi: >This would probably be more appropriate on -questions. > Yes, that's why I apologized for posting it here. It has been posted on -questions for several hours but I haven't got an answer, it is getting very late on the east coast and I need to resolve this by tomorrow. Again, I apologize for the post, and I thank you for responding. >I take it the problem started when you updated? Sounds >like you may need to recompile your X server or install >compat3x (the latter is the sane choice) > The problem did not start when I updated (as of May 27th). I believe that I must have accidentally removed the file today. I did a 'make' in XFree86 to see if the libc.so file was created, but it wasn't. I don't want to go on and do 'make install' unless that is definitely be the correct solution. Can I compile the libc.so.3 from /usr/src/lib/libc? What would be the exact command? John Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Vendor import of Perl 5.6
"Dampure, Pierre Y." wrote: > > Apologies if this has already been reported, but `make world` is > currently failing when trying to generate Config.pm for the newly > imported Perl 5.6 (failure at line 20 of configpm) Second that. Clean /usr/obj, make cleandir in /usr/src, problem still there. cd /usr/amd/realmounts/slave/usr/current/src/gnu/usr.bin/perl; make build-tools cd /usr/amd/realmounts/slave/usr/current/src/gnu/usr.bin/perl/libperl && make build-tools Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Extracting myconfig (with variable substitutions) Invalid conversion in sprintf: "%v" at /usr/amd/realmounts/slave/usr/current/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm line 20. Use of uninitialized value at /usr/amd/realmounts/slave/usr/current/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm line 432. /usr/amd/realmounts/slave/usr/current/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm: Config.pm not valid at /usr/amd/realmounts/slave/usr/current/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm line 432. *** Error code 255 Even when I got past that problem by setting '$myver = $];' in configpm, the next problem that came up was: Use of uninitialized value at /usr/amd/realmounts/slave/usr/current/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm line 433. /usr/amd/realmounts/slave/usr/current/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm: Config.pm not valid at /usr/amd/realmounts/slave/usr/current/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm line 433. *** Error code 255 This indicates to me that configpm is not reading Config.pm from the obj directory, which does contain the correct value that configpm is looking for at line 433. I'm not sure what the fix is, but hopefully this'll help mark down the road. Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? Index: configpm === RCS file: /usr/ncvs/src/contrib/perl5/configpm,v retrieving revision 1.1.1.2 diff -u -r1.1.1.2 configpm --- configpm2000/06/25 11:02:51 1.1.1.2 +++ configpm2000/06/26 03:58:14 @@ -17,7 +17,8 @@ open CONFIG, ">$config_pm" or die "Can't open $config_pm: $!\n"; -$myver = sprintf "v%vd", $^V; +#$myver = sprintf "v%vd", $^V; +$myver = $]; print CONFIG <<'ENDOFBEG_NOQ', <<"ENDOFBEG"; package Config;
Re: Help! can't 'startx' - missing libc.so
This would probably be more appropriate on -questions. I take it the problem started when you updated? Sounds like you may need to recompile your X server or install compat3x (the latter is the sane choice) -Dan On Sun, Jun 25, 2000 at 11:46:24PM -0400, John Daniels wrote: > Hi: > > I am using 4.0-STABLE > > John > > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com > > > > 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
Re: Config problems
On Sun, 25 Jun 2000, Kenneth Wayne Culver wrote: > Hey chuck, except for the SMP stuff, your config looks mostly like mine (I > only have a cpu line for i686) Let me know if there's anything I can do to > help though. I'm about ready to post again, so this is good timing. I got the totally vague warning from gethints.pl to quiet by making my disk section look much like the NOTES file. I then ran it by a brand new config, and out spewed more than 25 errors. The entire section on wiring down disks fails, and also all the stuff on npx, even tho that part was copied verbatim from NOTES. I have an Adaptec dual channel controller on my motherboard, and I have 3 disks and 2 cdroms, which I want to wire down. There's lines in the NOTES examples whose meanings just make no sense to me. Let me do a bit of quoting: [from NOTES] hint.scbus.0.at="ahc0" hint.scbus.1.at="ahc1" hint.scbus.1.bus="0" hint.scbus.3.at="ahc2" hint.scbus.3.bus="0" hint.scbus.2.at="ahc2" hint.scbus.2.bus="1" hint.da.0.at="scbus0" hint.da.0.target="0" hint.da.0.unit="0" hint.da.1.at="scbus3" hint.da.1.target="1" hint.da.2.at="scbus2" hint.da.2.target="3" hint.sa.1.at="scbus1" hint.sa.1.target="6" What does ``hint.scbus.1.bus="0"'' mean? Do I have to stick a number after the "device ahc" and "device scbus" lines (the NOTES file doesn't). Are there any other oddities I ought to know of? Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Help! can't 'startx' - missing libc.so
Hi: I am using 4.0-STABLE John Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Config problems
Hey chuck, except for the SMP stuff, your config looks mostly like mine (I only have a cpu line for i686) Let me know if there's anything I can do to help though. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 25 Jun 2000, Chuck Robey wrote: > I am getting a config error with the new gethints.pl stuff: > > unrecognized config token 1 > > This is with a newly cvsupped system, and I checked the version of > gethints.pl: > > ROOT:/usr/src/sys/i386/conf:472 >cvs status gethints.pl > === > File: gethints.pl Status: Up-to-date > >Working revision:1.4 Sun Jun 18 01:43:22 2000 >Repository revision: 1.4 /home/ncvs/src/sys/i386/conf/gethints.pl,v >Sticky Tag: (none) >Sticky Date: (none) >Sticky Options: (none) > > So I think that's right. My config file before had worked just fine, but > as a test, I went thru it and really tried to make it squeaky clean, but > it didn't seem to get rid of that error. I don't know if this message > indicates a fatal problem or just is a leftover printf, there's damned > little in the way of info in it. > > I don't know, maybe that error message is referring to line 1 of my config > file? Here's the start of the config file: > > machine i386 > > cpu I586_CPU > cpu I686_CPU > ident CH > maxusers64 > > # Create a SMP capable kernel (mandatory options): > options SMP # Symmetric MultiProcessor Kernel > options APIC_IO # Symmetric (APIC) I/O > > If that doesn't do it, I'm attaching the entire config file to this mail. > > Sure would appreciate a hint; I'm not a perl hacker, but if I gotta become > one to puzzle this out, it's going to take me an long extra while trying > to get me a new kernel. > > > Chuck Robey| Interests include C & Java programming, FreeBSD, > [EMAIL PROTECTED] | electronics, communications, and signal processing. > > New Year's Resolution: I will not sphroxify gullible people into looking up > fictitious words in the dictionary. > > > > > 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
Help! can't 'startx' - missing libc.so
Hi: I apologize for posting this to -current, but I really need to know how bad the damage is ASAP because I may need to reinstall. When I type 'startx' I get a message that libc.so.3 cannot be found and also a note about /usr/libexec/ld-elf.so.1 I'm not sure how these two files are related. Is libc.so.3 contained in ld-elf.so, or called from it? I'm not sure what happened to this file(s) but I did a 'make' on XFree86 to see if the file(s) are produced there, but they don't seem to be a part of XFree86. I believe that libc.so may be a C-library provided by the system, and I may need to either ftp a new one or install a new system. Any help is very welcome. John Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/usr.sbin/ancontrol ancontrol.c
According to Nickolay Dudorov: > The first line of the resulting file (with the $OpenBSD: tag) > close the comment and makes this file uncompilable. [back from USENIX] Green fixed this in time but I'll remove the comment anyway as it wasn't supposed to be committed (we don't use the OpenBSD file verbatim). /me should edit diffs more carefully -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
prod for PR 15251
Please review/commit PR 15251. It addresses a number of signedness issues in the sysctl code. While originally submitted almost 7 months ago, I have updated the PR with patches against a fairly recent -current. Thank you, Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Config problems
I am getting a config error with the new gethints.pl stuff: unrecognized config token 1 This is with a newly cvsupped system, and I checked the version of gethints.pl: ROOT:/usr/src/sys/i386/conf:472 >cvs status gethints.pl === File: gethints.pl Status: Up-to-date Working revision:1.4 Sun Jun 18 01:43:22 2000 Repository revision: 1.4 /home/ncvs/src/sys/i386/conf/gethints.pl,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) So I think that's right. My config file before had worked just fine, but as a test, I went thru it and really tried to make it squeaky clean, but it didn't seem to get rid of that error. I don't know if this message indicates a fatal problem or just is a leftover printf, there's damned little in the way of info in it. I don't know, maybe that error message is referring to line 1 of my config file? Here's the start of the config file: machine i386 cpu I586_CPU cpu I686_CPU ident CH maxusers64 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O If that doesn't do it, I'm attaching the entire config file to this mail. Sure would appreciate a hint; I'm not a perl hacker, but if I gotta become one to puzzle this out, it's going to take me an long extra while trying to get me a new kernel. Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
On Sun, 25 Jun 2000, Warner Losh wrote: > Some days is OK, imho. Much more than that and I'd begin to worry. > Much more than a week or two and I'd worry a lot. I'll go put a note > in updating right now. That's okay with me too. People should just not upgrade their work machines for the next few days until entropy is fixed. 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: HEADS UP! New (incomplete) /dev/random device!
> In message <[EMAIL PROTECTED]> Mark Murray writes: > : > Yes. Me too. Mark, how long is this period going to be? > : > : Some days. Certainly a lot shorter that the SMP destabilization. > > Some days is OK, imho. Much more than that and I'd begin to worry. > Much more than a week or two and I'd worry a lot. I'll go put a note > in updating right now. Thanks! :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
In message <[EMAIL PROTECTED]> Mark Murray writes: : > Yes. Me too. Mark, how long is this period going to be? : : Some days. Certainly a lot shorter that the SMP destabilization. Some days is OK, imho. Much more than that and I'd begin to worry. Much more than a week or two and I'd worry a lot. I'll go put a note in updating right now. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
world dies in libperl
cd /usr/src/gnu/usr.bin/perl/libperl && make build-tools Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Extracting myconfig (with variable substitutions) Invalid conversion in sprintf: "%v" at /usr/src/gnu/usr.bin/perl/libperl/../../. ./../contrib/perl5/configpm line 20. Use of uninitialized value at /usr/src/gnu/usr.bin/perl/libperl/../../../../cont rib/perl5/configpm line 432. /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm: Config.pm not valid at /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configp m line 432. *** Error code 255 Stop in /usr/src/gnu/usr.bin/perl/libperl. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA [EMAIL PROTECTED] [EMAIL PROTECTED] Never, "for the sake of peace and quiet," deny your own experience or convictions. -- Dag Hammarskjold To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup/cvs oddities?
> On Sun, 25 Jun 2000, Matthew Jacob wrote: > > > > > Can anyone shed light on why a CVSUP'd dirtree I have now always > > falls down with the following error?... Because it's CVSUP'd, the > > local repository is just /home/ncvs (NFS mounted). I cannot figure out why it > > all of a sudden wants to run off the Freefall . > > Check CVS/Root in that directory. If you do a remote cvs operation it > sometimes likes to update the repository to point to freefall, which then > screws up cvs update unless you specify "-d /home/ncvs". I have aliases > lcvs and rcvs which explicitly state the -d to use (I think this advice > came from the committer's guide) Oops. Somehow I had a couple of bad CVS/Root files creep in. The odd thing is that they weren't anywhere &near& where things died. I had to use find/grep to hunt 'em down. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
On Sun, 25 Jun 2000, Mark Murray wrote: > > I must say I'm not all that comfortable with this series of commits - I > > was expecting this to stay in Mark's tree until it at least tries to do > > everything the old driver did. Weakening system security like this for an > > indeterminate period really bothers me. > > 1) I whined for reviews for long enough. Where were you? Waiting until the code was complete and nominally commitworthy before spending time reviewing 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: HEADS UP! New (incomplete) /dev/random device!
> Yes. Me too. Mark, how long is this period going to be? Some days. Certainly a lot shorter that the SMP destabilization. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
> > It complains about libcrypto & libssl not containing RSA, but it > > might be because make world is broken due to perl... > > This happens when a test RSA operation fails - but OpenSSH doesn't try to > check why it fails and assumes it was because no RSA code even > exists. It's probably more likely it's failing an internal check related > to /dev/random (this is the signature which caused me to notice the > missing /dev/random on alpha recently) Looks like we (er, you! :-) ) have a job to do fixing this? ;-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
> I must say I'm not all that comfortable with this series of commits - I > was expecting this to stay in Mark's tree until it at least tries to do > everything the old driver did. Weakening system security like this for an > indeterminate period really bothers me. 1) I whined for reviews for long enough. Where were you? 2) With the SMP "Destabilization" of the tree coming, I took the opportunity because a) Merging differences was going to get harder; and b) folk were already warned off the use off CURRENT for production purposes. 3) I fully recognise that this needs to be worked on; now that I have gotten rid of a lot of mess, I can give it my attention; the time is not "indeterminate", it is "work in progress" (Ya, Ya, semantics). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
> And the one to yarrow.c ?? Done! > > What are the symptoms? > > It complains about libcrypto & libssl not containing RSA, but it > might be because make world is broken due to perl... That means the /dev/random driver is not loaded. /../../contrib/perl5/configpm line 20. > Use of uninitialized value at /u1/src/gnu/usr.bin/perl/libperl/../../../../co ntrib/perl5/configpm line 432. Fix coming now... > > > Seems phk's extended Murphy field has found a new victim :) > > > > Always, with a big commit. > > Nah, not if tested proberly :) Dunno. There seems to be a limit on commit size, after which glitches are bound to come. I see my job as staying awake long enough to make things stable enough. :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
In message <[EMAIL PROTECTED]> Kris Kennaway writes: : I must say I'm not all that comfortable with this series of commits - I : was expecting this to stay in Mark's tree until it at least tries to do : everything the old driver did. Weakening system security like this for an : indeterminate period really bothers me. Yes. Me too. Mark, how long is this period going to be? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
On Sun, 25 Jun 2000, Soren Schmidt wrote: > It complains about libcrypto & libssl not containing RSA, but it > might be because make world is broken due to perl... This happens when a test RSA operation fails - but OpenSSH doesn't try to check why it fails and assumes it was because no RSA code even exists. It's probably more likely it's failing an internal check related to /dev/random (this is the signature which caused me to notice the missing /dev/random on alpha recently) 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: cvsup/cvs oddities?
On Sun, 25 Jun 2000, Matthew Jacob wrote: > > Can anyone shed light on why a CVSUP'd dirtree I have now always > falls down with the following error?... Because it's CVSUP'd, the > local repository is just /home/ncvs (NFS mounted). I cannot figure out why it > all of a sudden wants to run off the Freefall . Check CVS/Root in that directory. If you do a remote cvs operation it sometimes likes to update the repository to point to freefall, which then screws up cvs update unless you specify "-d /home/ncvs". I have aliases lcvs and rcvs which explicitly state the -d to use (I think this advice came from the committer's guide) 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: HEADS UP! New (incomplete) /dev/random device!
On Sun, 25 Jun 2000, Mark Murray wrote: > > I don't know which applications depend on /dev/random providing entropy > > and which gather their own. > > Right. SSH and SSL should not be used: PGP should be okay. I must say I'm not all that comfortable with this series of commits - I was expecting this to stay in Mark's tree until it at least tries to do everything the old driver did. Weakening system security like this for an indeterminate period really bothers me. 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: HEADS UP! New (incomplete) /dev/random device!
It seems Mark Murray wrote: > > He he :) remember the patch to i386/i386/mem.c as that is also > > broken, the default statement is best used _inside_ a switch :) > > Yeah - I got that :-). And the one to yarrow.c ?? > > That makes my kernel compile, but ssh doesn't work anymore, > > What are the symptoms? It complains about libcrypto & libssl not containing RSA, but it might be because make world is broken due to perl... > > which might be due to world being broken due to your import > > of the latest ugliest perl version, it doesn't compile either :) > > Symptoms? cd /u1/src/gnu/usr.bin/perl/libperl && make build-tools Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Extracting myconfig (with variable substitutions) Invalid conversion in sprintf: "%v" at /u1/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm line 20. Use of uninitialized value at /u1/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm line 432. /u1/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm: Config.pm not valid at /u1/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/configpm line 432. > > Seems phk's extended Murphy field has found a new victim :) > > Always, with a big commit. Nah, not if tested proberly :) -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cvsup/cvs oddities?
Can anyone shed light on why a CVSUP'd dirtree I have now always falls down with the following error?... Because it's CVSUP'd, the local repository is just /home/ncvs (NFS mounted). I cannot figure out why it all of a sudden wants to run off the Freefall . U usr.sbin/ypset/Makefile U usr.sbin/ypset/ypset.8 U usr.sbin/ypset/ypset.c cvs update: Updating usr.sbin/zic U usr.sbin/zic/Arts.htm U usr.sbin/zic/Makefile U usr.sbin/zic/Makefile.inc U usr.sbin/zic/README U usr.sbin/zic/Theory U usr.sbin/zic/WWW.htm U usr.sbin/zic/ialloc.c U usr.sbin/zic/private.h U usr.sbin/zic/scheck.c U usr.sbin/zic/zdump.8 U usr.sbin/zic/zdump.c U usr.sbin/zic/zic.8 U usr.sbin/zic/zic.c cvs update: Updating usr.sbin/zic/zdump U usr.sbin/zic/zdump/Makefile cvs update: Updating usr.sbin/zic/zic U usr.sbin/zic/zic/Makefile freefall.freebsd.org: Connection refused cvs [update aborted]: end of file from server (consult above messages if any) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fwd: WuFTPD: Providing *remote* root since at least1994
On Fri, Jun 23, 2000 at 04:34:11PM -0400, Keith Stevenson wrote: > On Fri, Jun 23, 2000 at 03:48:48PM -0400, Mike Tancsa wrote: > > What about > > > > --enable-paranoid > > > > as part of the config ? As so much seems to be related to the site exec > > command, perhaps its best to just disable this ? > > While I'm all for actually fixing the problems in the code, I've found that > the --enable-paranoid options to be a good one. I've been tinkering around > with the exploit and the paranoid option seems to defend against it. I don't > think that any of my users will miss the SITE EXEC commands. > If one were interested in improving the ftpd which ships with the base system, which features would make it a viable replacement those currently running wu-ftpd? Perhaps one- Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
> He he :) remember the patch to i386/i386/mem.c as that is also > broken, the default statement is best used _inside_ a switch :) Yeah - I got that :-). > That makes my kernel compile, but ssh doesn't work anymore, What are the symptoms? > which might be due to world being broken due to your import > of the latest ugliest perl version, it doesn't compile either :) Symptoms? > Seems phk's extended Murphy field has found a new victim :) Always, with a big commit. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
It seems Mark Murray wrote: > > > I'm not sure about that rule anymore; AFAIK, it is not possible. > > > > Hmm, we also have another rule, and that is to test before commit, > > the following patch is needed to make a current kernel with > > your resent commits compile :) > > Fooey. :-( > > This is what you get from too-heavy testing in modules, and > not-heavy-enough in LINT. He he :) remember the patch to i386/i386/mem.c as that is also broken, the default statement is best used _inside_ a switch :) That makes my kernel compile, but ssh doesn't work anymore, which might be due to world being broken due to your import of the latest ugliest perl version, it doesn't compile either :) Seems phk's extended Murphy field has found a new victim :) -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
> > I'm not sure about that rule anymore; AFAIK, it is not possible. > > Hmm, we also have another rule, and that is to test before commit, > the following patch is needed to make a current kernel with > your resent commits compile :) Fooey. :-( This is what you get from too-heavy testing in modules, and not-heavy-enough in LINT. Thanks! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
It seems Mark Murray wrote: > > > Do you have a full crypto distribution (kernel also)? > > > > Nope, just figured that out myself :) > > Aren't we supposed to be able to build without crypto ?? > > I'm not sure about that rule anymore; AFAIK, it is not possible. Hmm, we also have another rule, and that is to test before commit, the following patch is needed to make a current kernel with your resent commits compile :) Index: dev/randomdev//randomdev.c === RCS file: /home/ncvs/src/sys/dev/randomdev/randomdev.c,v retrieving revision 1.1 diff -u -r1.1 randomdev.c --- dev/randomdev//randomdev.c 2000/06/25 08:38:58 1.1 +++ dev/randomdev//randomdev.c 2000/06/25 18:39:10 @@ -44,7 +44,7 @@ #include #include -#include "yarrow.h" +#include "dev/randomdev/yarrow.h" static d_read_t randomread; static d_write_t randomwrite; Index: dev/randomdev//yarrow.c === RCS file: /home/ncvs/src/sys/dev/randomdev/yarrow.c,v retrieving revision 1.1 diff -u -r1.1 yarrow.c --- dev/randomdev//yarrow.c 2000/06/25 08:38:58 1.1 +++ dev/randomdev//yarrow.c 2000/06/25 18:38:58 @@ -39,7 +39,7 @@ #include #include -#include "yarrow.h" +#include "dev/randomdev/yarrow.h" void generator_gate(void); void reseed(void); Index: i386/i386//mem.c === RCS file: /home/ncvs/src/sys/i386/i386/mem.c,v retrieving revision 1.86 diff -u -r1.86 mem.c --- i386/i386//mem.c2000/06/25 17:26:47 1.86 +++ i386/i386//mem.c2000/06/25 18:42:13 @@ -217,10 +217,10 @@ /* minor device 1 is kernel memory */ case 1: return i386_btop(vtophys(offset)); - } default: return -1; + } } /* -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Vendor import of Perl 5.6
Apologies if this has already been reported, but `make world` is currently failing when trying to generate Config.pm for the newly imported Perl 5.6 (failure at line 20 of configpm) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
> > Do you have a full crypto distribution (kernel also)? > > Nope, just figured that out myself :) > Aren't we supposed to be able to build without crypto ?? I'm not sure about that rule anymore; AFAIK, it is not possible. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with nlist on -current?
I installed 5.0-2621-CURRENT on a new system (OR840, 2x733EB, 512MB RDRAM) and had problems with top / systat / vmstat all failing after reporting problems with nlist: When using top: top: nlist failed When using systat: systat: nlist: can't find following symbols: _ccpu _fscale When using vmstat: vmstat: undefined symbols: _kmemstatistics _bucket _zlist Later CVsup did not cure the issue. The problems happen regardless of the kernel used (original GENERIC, recompiled GENERIC, custom UP or custom MP) Any clues? PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
It seems Mark Murray wrote: > > > Without knowing what you typed (and where), I can't help. > > > > Well, I thought that was obvious :) > > Not really; folks do the darndest things. :-) > > > Just added options RANDOMDEV as pr your instructions and made > > a new kernel with config -r and make depend then make > > Do you have a full crypto distribution (kernel also)? Nope, just figured that out myself :) Aren't we supposed to be able to build without crypto ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
> > Without knowing what you typed (and where), I can't help. > > Well, I thought that was obvious :) Not really; folks do the darndest things. :-) > Just added options RANDOMDEV as pr your instructions and made > a new kernel with config -r and make depend then make Do you have a full crypto distribution (kernel also)? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
It seems Mark Murray wrote: > Hi > > Without knowing what you typed (and where), I can't help. Well, I thought that was obvious :) Just added options RANDOMDEV as pr your instructions and made a new kernel with config -r and make depend then make > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions > -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_g > lobal.h -elf -mpreferred-stack-boundary=2 ../../dev/randomdev/randomdev.c > > ../../dev/randomdev/randomdev.c:45: crypto/blowfish/blowfish.h: No such file > or directory > > ../../dev/randomdev/randomdev.c:47: yarrow.h: No such file or directory > > ../../dev/randomdev/randomdev.c:85: invalid use of undefined type `struct sta > te' > > ../../dev/randomdev/randomdev.c:85: initializer element is not constant > > ../../dev/randomdev/randomdev.c:85: (near initialization for `sysctl___kern_r > andom_yarrow_gengateinterval.oid_arg1') > > *** Error code 1 -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
Hi Without knowing what you typed (and where), I can't help. M > Uhm, what about this: > > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_g lobal.h -elf -mpreferred-stack-boundary=2 ../../dev/randomdev/randomdev.c > ../../dev/randomdev/randomdev.c:45: crypto/blowfish/blowfish.h: No such file or directory > ../../dev/randomdev/randomdev.c:47: yarrow.h: No such file or directory > ../../dev/randomdev/randomdev.c:85: invalid use of undefined type `struct sta te' > ../../dev/randomdev/randomdev.c:85: initializer element is not constant > ../../dev/randomdev/randomdev.c:85: (near initialization for `sysctl___kern_r andom_yarrow_gengateinterval.oid_arg1') > *** Error code 1 > > -Søren > -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
It seems Mark Murray wrote: > Hola Mondo! > > The New /dev/random device is in but there are come caveats. > > 1) It is not yet cryptographically secure, so those of you using >CURRENT for "live" projects, please be careful! > > 2) If you do not have the randomdev module loaded, ssh will >fail in strange and creative ways (like RSA or DH not working >for strange reasons). > > 3) It is not built by default (except as a kernel module), so you >either need to add the "options RANDOMDEV" like to your kernel >config, or load it at boot time in /dev/loader.conf > > 4) Make sure that you update your /etc area (mergemaster is your >friend). The rndcontrol(8) utility is now OBE, and no longer of >relevance. > > You have been warned! Uhm, what about this: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/randomdev/randomdev.c ../../dev/randomdev/randomdev.c:45: crypto/blowfish/blowfish.h: No such file or directory ../../dev/randomdev/randomdev.c:47: yarrow.h: No such file or directory ../../dev/randomdev/randomdev.c:85: invalid use of undefined type `struct state' ../../dev/randomdev/randomdev.c:85: initializer element is not constant ../../dev/randomdev/randomdev.c:85: (near initialization for `sysctl___kern_random_yarrow_gengateinterval.oid_arg1') *** Error code 1 -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
> I guess it follows that it is not a good idea to generate keys or > certificates on -CURRENT for a while (until entropy comes back to town)? Correct if they rely on /dev/random for entropy. > I don't know which applications depend on /dev/random providing entropy > and which gather their own. Right. > If so, I think this needs an UPDATING entry, particularly since the > symptoms could outlive the cause. i.e. something to the effect of > ``Keys and certificates generated on -CURRENT on or after m/d/y should > not be used'' and updated again when the entropy is again available. Agreed. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! New (incomplete) /dev/random device!
On Sun, Jun 25, 2000 at 12:35:12PM +0200, Mark Murray wrote: > 1) It is not yet cryptographically secure, so those of you using >CURRENT for "live" projects, please be careful! I guess it follows that it is not a good idea to generate keys or certificates on -CURRENT for a while (until entropy comes back to town)? I don't know which applications depend on /dev/random providing entropy and which gather their own. If so, I think this needs an UPDATING entry, particularly since the symptoms could outlive the cause. i.e. something to the effect of ``Keys and certificates generated on -CURRENT on or after m/d/y should not be used'' and updated again when the entropy is again available. -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP! New (incomplete) /dev/random device!
Hola Mondo! The New /dev/random device is in but there are come caveats. 1) It is not yet cryptographically secure, so those of you using CURRENT for "live" projects, please be careful! 2) If you do not have the randomdev module loaded, ssh will fail in strange and creative ways (like RSA or DH not working for strange reasons). 3) It is not built by default (except as a kernel module), so you either need to add the "options RANDOMDEV" like to your kernel config, or load it at boot time in /dev/loader.conf 4) Make sure that you update your /etc area (mergemaster is your friend). The rndcontrol(8) utility is now OBE, and no longer of relevance. You have been warned! M To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/contrib/softupdates softdep.h ffs_softdep.c
On Sat, Jun 24, 2000, Kirk McKusick wrote: [snip] > Kirk, do you still want to keep things that way ? > > Adrian > > Yes, I do want it kept as a yunefs option. [snip] > Your above proposal would work, though that is not how NetBSD > implemented it. I feel that it is a lot of extra mechanism for very > little gain. Administrators generally make a one-time decision to > run soft updates on a filesystem. It is not the sort of thing that > they want to change on a regular basis. It is possible to run tunefs > on a filesystem that is mounted read-only, so it no more difficult > to use tunefs than it is to make it a mount-time option (i.e., they > still have to down-grade to read-only, set the option, then upgrade). > Finally, I expect that soft updates will eventually just be defaulted > to `on' when a filesystem is built, and in a few rare instances an > administrator will want to turn it off. I do not want to have an > option that needs to be added to nearly every fstab entry to get > the default behavior. Plus it is just one more bit of trivia that > new system administrators need to learn to make their systems run > well. The more of those details that need not be learned because > they just do the right thing, the better. There we go. If someone has a better argument against this, feel free to post it to the list. I'm calling this one dead. Thanks, Kirk. Adrian -- Adrian ChaddBuild a man a fire, and he's warm for the <[EMAIL PROTECTED]>rest of the evening. Set a man on fire and he's warm for the rest of his life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Mike Pritchard wrote: > > I just noticed that this change has now made a lot of the section 4 > man pages out of date. > > What is the best way to represent these changes in the man pages? > A good example is ata(4). Currently it reads like this: > > SYNOPSIS > device isa > device ata0 at isa? port IO_WD1 irq 14 > device ata1 at isa? port IO_WD2 irq 15 > > Should this become: > > SYNOPSIS > device isa > device ata > hint.ata.0.at="isa" > hint.ata.0.port="0x1F0" > hint.ata.0.irq="14" > hint.ata.1.at="isa" > hint.ata.1.port="0x170" > > Or some much mess? When will the hints file syntax be nailed down, > so that someone can go in and fix all the man pages without having > to worry about having to go through and do it all again when the > syntax changes? > > Something in the loader man pages should be updated to provide info > on the new hints stuff. Having a man page dedicated to describing the > hints stuff probably would also be a good idea to make it easy for people > to figure out how it works. This definitely needs some work. I'm not sure the hints syntax will change much, if at all. OTOH, I don't know how to approach this. In other words, suggestions (and specially patches) are welcome. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Windows works, for sufficently small values of "works". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vnode_if.h: how should it be done ?
In message <[EMAIL PROTECTED]> Assar Westerlund writes:
: Warner Losh <[EMAIL PROTECTED]> writes:
: > In message <[EMAIL PROTECTED]> Assar Westerlund writes:
: > : The problem is that the source files are hidden in the kernel source
: > : directory and not installed. Where should vnode_if.{src,pl} get
: > : installed? It seems much simpler just to install vnode_if.h in
: > : /usr/include/sys. Patch appended.
: >
: > No.
:
: > We don't install kenrel internal files.
:
: But it's not kernel internal. It's used by modules/KLDs ? Where
: should these expect to find it?
'.'
: > Use SYSDIR instead.
:
: I'm not sure what you mean by this? Should vnode_if.h just reside in
: /sys/sys and be used from there or what?
No. I mean that you need to have a kernel in $SYSDIR (or in /sys or
/usr/src) and that vnode_if.h will get built in '.'.
: > : + ${INSTALL} -C -o ${BINOWN} -g ${BINGRP} -m 444 \
: > : + ${.OBJDIR}/vnode_if.h \
: > : + ${DESTDIR}/usr/include/sys
: >
: > I object to this part of the patch. We shouldn't install this file.
: > It isn't needed by anything outside of the kernel/drivers.
:
: Well, depends on your point of view if that's outside kernel/drivers,
: but it's sure used by modules/KLDs.
No. That's part of the kernel, for the purposes of this discussion.
It isn't used by userland at all. It should be build by the kld
system, and if it isn't, then it is a bug. Go look at
sys/modules/msdos/Makefile for an example of how it is supposed to
work.
: > For drivers, it should be built automatically as part of the modules
: > build system ala the *_if.m stuff.
:
: Where are these files installed so that they can be used by
: third-party KLDs?
They aren't installed. You must have a kernel tree to build the kld.
Just add vnode_if.h to your SRCS and the rest happens automatically
via bsd.kmod.mk. It works great. I do it all the time. In fact, I
added SYSDIR support to bsd.kmod.mk at Timing Solutions so that we
could compile our drivers outside of the tree.
There are lots of generated files like this that aren't installed, nor
should they be.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
