No Subject
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Parallel port Zip drive
I hope this hasn't already been pounded to death, checked the archives with no results. I just upgraded to 4.0 and everything works fine so far except the zip drive. Here's my dmesg: 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: Tue Mar 7 16:17:46 EST 2000 root@:/usr/src/sys/compile/NEWKERN -snip- ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 vpo0: Iomega Matchmaker Parallel to SCSI interface on ppbus0 imm0: EPP 1.9 mode sbc0: Creative SB16/SB32 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: SB DSP 4.16 on sbc0 unknown0: Game at port 0x200-0x207 on isa0 unknown1: Cqm at port 0x620-0x623 on isa0 ad0: 17206MB WDC AC418000D [34960/16/63] at ata0-master using UDMA33 ad1: 8693MB WDC AC29100D [17662/16/63] at ata0-slave using UDMA33 acd0: CDROM BCD-48SB CD-ROM at ata1-master using WDMA2 vpo0: VP0 error/timeout (5) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (2) vpo0: VP0 error/timeout (2) Mounting root from ufs:/dev/ad1s1a Any idea what these errors may indicate? Although now I notice that ppc0 is in NIBBLE-only, and vpo0 is showing EPP 1.9. Could that be my problem. Thanks. -- Walter Brameld Join the Army. Meet interesting people. Kill them. TANSTAAFL To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
On Mon, 06 Mar 2000, Kris Kennaway wrote: On Mon, 6 Mar 2000, R Joseph Wright wrote: I just built a new world today and openssh does not appear to be installed. I have the directories /etc/ssh and /etc/ssl but they are empty. There is no /usr/bin/ssh. I've been trying to follow the discussions on this issue and I understood that this is now part of the default base system. Do you have the crypto sources installed? Kris Do you still need to install the rsaref port before openssh? (/usr/ports/security) -- Walter Brameld Join the Army. Meet interesting people. Kill them. TANSTAAFL To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
On Tue, 07 Mar 2000, Walter Brameld wrote: On Mon, 06 Mar 2000, Kris Kennaway wrote: On Mon, 6 Mar 2000, R Joseph Wright wrote: I just built a new world today and openssh does not appear to be installed. I have the directories /etc/ssh and /etc/ssl but they are empty. There is no /usr/bin/ssh. I've been trying to follow the discussions on this issue and I understood that this is now part of the default base system. Do you have the crypto sources installed? Kris Do you still need to install the rsaref port before openssh? (/usr/ports/security) Ah, sorry. That's for SSL. Not awake yet, I guess.. -- Walter Brameld Join the Army. Meet interesting people. Kill them. TANSTAAFL To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ssh strangeness in -current...
At 9:29 PM +0100 2000/3/7, Udo Erdelhoff wrote: Are you using OpenSSH or the 'normal' ssh on your Solaris box? The Solaris box is the only place where I have tried installing OpenSSH so far. @work: SunOS [...] 5.6 Generic_105181-05 [...] SSH Version 1.2.27 [sparc-sun-solaris2.6], protocol version 1.5. Standard version. Does not use RSAREF. Have you tried this side with OpenSSH? It's using OpenSSH on Solaris that is giving me problems -- These are my opinions and should not be taken as official Skynet policy = Brad Knowles, [EMAIL PROTECTED] Sys. Arch., Mail/News/FTP/Proxy Admin Note: No Microsoft programs were used in the creation or distribution of this message. If you are using a Microsoft program to view this message, be forewarned that I am not responsible for any harm you may encounter as a result. See http://i-want-a-website.com/about-microsoft/twelve-step.html for details. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Parallel port Zip drive
It works if you can switch your parallel port to EPP (???) mode in the bios. Transfer speed raises also under windows with this configuration btw. -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Parallel port Zip drive
On Wed, 08 Mar 2000, F. Heinrichmeyer wrote: It works if you can switch your parallel port to EPP (???) mode in the bios. Transfer speed raises also under windows with this configuration btw. Thank you for the reply, I will try that. What I find odd is that it worked fine on 3.4-STABLE. -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh -- Walter Brameld Join the Army. Meet interesting people. Kill them. TANSTAAFL To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: YA ssh question (ssh-askpass?)
Kris Kennaway writes: On Tue, 7 Mar 2000, Richard J Kuhns wrote: So does all this mean that I now have to start using ssh-add/ssh-agent? Not at all; it's there as an option for people who have "secure" workstations and/or want single-signon for SSH. I often use ssh-agent if I have lots of remote CVS commits to do consecutively, e.g. do 'ssh-agent tcsh' and then ssh-add in the subshell, and exit when I'm done. ssh-add will also only invoke ssh-askpass if invoked with no controlling terminal, e.g. ssh-add /dev/null or if called during the X login process. Otherwise it uses the good old (internal) text prompt. Kris But then I'm back to my original question/problem: how to get ssh to ask for a password using ssh-askpass. I've looked through the code (a little); how would you feel about a patch to openssh/readpass.c that caused it to call ssh-askpass if there's no controlling tty but DISPLAY is set? -- Richard Kuhns [EMAIL PROTECTED] PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Roadx319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
In either case, the answer is that you do not need to install the rsaref port before any builds. It is only a runtime dependency now. Jim Bloom [EMAIL PROTECTED] Walter Brameld wrote: Do you still need to install the rsaref port before openssh? (/usr/ports/security) Ah, sorry. That's for SSL. Not awake yet, I guess.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD 4.0 release candidate #3 now available.
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-2307-CURRENT ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2307-CURRENT With ISO images available from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-2307-CURRENT/ .. just as soon as they finish uploading (the i386 image is already there and the alpha image is about 8% there and should be in place by the time most of you read this message). This will probably be the last release candidate image before release day unless folks find some real show-stoppers here, so please look thoroughly :). Thanks! - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Remote upgrade from 3.4-STABLE to 4.0
Ian Whalley wrote:
In reading UPDATING (and -current), I can't see any way to upgrade
from 3.4-STABLE to (the future) 4.0-STABLE. This is fair enough,
it being a major revision upgrade (can't see an easy way to
upgrade {AIX,Solaris,HPUX} through a major revision without access
to the console...), but in an effort to save several hour drive,
I figured I'd ask if anyone had had any success doing an upgrade
remotely...
1) There is no 4.0-STABLE. The only 4.0 that exists is -CURRENT.
2) This is described in UPDATING, so go back there and read it again.
And if you don't find it, you have the wrong version of UPDATING.
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone bind them.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
4.0-20000308-CURRENT crypto
I tried an FTP SNAP install this morning, and all the crypto libs from current were unavailable. I switched over to the debug console, but there was no additional info. The files seem to be on the ftp site just fine. Is this a known issue ? ---Mike Mike Tancsa, tel +1 519 651 3400 Network Administrator,[EMAIL PROTECTED] Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000308-CURRENT crypto
I tried an FTP SNAP install this morning, and all the crypto libs from current were unavailable. I switched over to the debug console, but there was no additional info. The files seem to be on the ftp site just fine. Is this a known issue ? Please try again - I *just* fixed this problem and updated the floppies in-place. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
CC's trimmed... At 07:42 AM 3/8/00 -0500, Jim Bloom wrote: In either case, the answer is that you do not need to install the rsaref port before any builds. It is only a runtime dependency now. Jim Bloom [EMAIL PROTECTED] Walter Brameld wrote: Do you still need to install the rsaref port before openssh? (/usr/ports/security) Ah, sorry. That's for SSL. Not awake yet, I guess.. My last build I didn't try, but about a week or so back I did not have RSAref installed, built world, installed RSAref, and it "just worked" as advertised for RSA authentication with OpenSSH. Didn't check on SSLv2, but presume it would. Time to check again with RC3. 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. 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-20000308-CURRENT crypto
At 07:39 AM 3/8/00 -0800, Jordan K. Hubbard wrote: I tried an FTP SNAP install this morning, and all the crypto libs from current were unavailable. I switched over to the debug console, but there was no additional info. The files seem to be on the ftp site just fine. Is this a known issue ? Please try again - I *just* fixed this problem and updated the floppies in-place. :) Will do. Also, a _very_ minor point, I think on the screen where it says, "Do you want only normal users to have ftp access (e.g. disable anon ftp)" or something like that. Should it not be _i.e._ instead of _e.g_ ? Also, does the ISO image have the same issue ? ---Mike Mike Tancsa, tel +1 519 651 3400 Network Administrator,[EMAIL PROTECTED] Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: howto for 3.4-STABLE - 4.0-CURRENT?
Comments: I wanna share my results for those who want to do this via remote. I slightly modified the procedure below for upgrading a box several hundred miles away, where single user mode means a long distance phone call. cvsup to current make buildworld make buildkernel make installkernel - change - I just rebooted normally, the network came up fine, if you have any special kernel needs, make sure you have di lines in /boot/kernel.conf (i.e. your system hangs when trying to detect a device) at this point you are very safe, Its just a new kernel, if it doesnt work, just load from the old one and give up or tweak, or whatever. make -DNOINFO installworld make installworld ok, here is where I discovered something nobody told me about. 4.0 moved me from DES to MD5. the effect was that none of the passwords worked. luckily I was logged in as root already, and only had 4 accts, I just ran the passwd command and reset them. if its a nightmare to move your accounts, and/or you want to keep DES, I have been told that adding the line "auth_default = des" in /etc/auth.conf will keep you on DES. (I didnt read the dev changes till after I did this, so it would prob be better to do it here.) reboot now after the reboot, I had a weird error that nobody has mentioned as far as I can see. Whenever I tried to make in /usr/ports I would get an error on two libraries: /usr/libexec/ld-elf.so.1, /usr/lib/libm.so.2 after that everything was pretty sane, little cleanups, but nothing really scary. I dont know if I recommend this or not, but I hope anyone who tries it will learn from my experience and have a smoother ride ;) so, first solution I can think of is, copy the files from an existing current box". /usr/libexec/ld-elf.so.1 wouldnt let me overwrite it, even as root, but /usr/lib/libm.so.2 did, amazingly enough it only took the libm replacement. Quoting Eugene M. Kim ([EMAIL PROTECTED]): On Thu, 10 Feb 2000, John Baldwin wrote: | You need a -current kernel for installworld to work. In fact, | if you aren't running a -current kernel installworld will blow | up on your machine. Try this instead: | | - cvsup -current | - make buildworld | - make buildkernel | - make installkernel - backup /dev to /dev.orig - mkdir /dev - copy /usr/src/etc/MAKEDEV* into /dev - remake all devices in /dev (don't forget to make the disk slice entries separately) | - reboot into single user mode | - make -DNOINFO installworld | - make installworld | - merge over /etc changes, etc. | - reboot -- Eugene M. Kim [EMAIL PROTECTED] "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Adriel Ickler Network Administrator - [EMAIL PROTECTED] Self Trading Securities - Voice: 512-263-2769 www.selftrading.com - Fax: 512-263-2141 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Small bug in chown and chgrp ?
On Mon, Mar 06, 2000 at 08:36:08PM +0100, Dave Boers wrote: It seems that chown's behavior is inconsistent with both the usage message and the man page. The same goes for chgrp. Fixed! I have no idea how I managed to not commit all the "-v" code. -- -- David([EMAIL PROTECTED]) 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], Donn Miller [EMAIL PROTECTED] wrote: John Polstra wrote: Below is a patch for "src/libexec/rtld-elf" which should fix the assert failures in wine. I'd appreciate hearing from anybody who tests this with multithreaded packages such as wine, JDK, Mozilla, and linuxthreads. [snipped patch] OK, here's some of the errors I get with Mozilla. It looks like it happens when Gdk runs out os SysV shared memory. Otherwise, if I don't get the "Gdk-WARNING **: shmget failed!", the ld.so erros never occur, and Mozilla runs OK. It seems as if Wine is working OK so far, though, although I probably haven't tested Wine enough: [...] /usr/libexec/ld-elf.so.1: Application locking error: 1 readers and 1 writers in dynamic linker. See DLLOCKINIT(3) in manual pages. This means that one thread was in the middle of a dlopen() call when another thread either called a new function for the first time (invoking the dynamic linker for lazy binding) or called dlsym(). Really the only _right_ place I can find to fix this kind of thing is in the application itself, by calling dllockinit() to set up locking for the dynamic linker invocations. I keep trying to come up with solutions that will work without that, but I'm not at all sure it's possible. I'll take another look at Mozilla and see what's done for other platforms. They must have this same problem, at least potentially. Thanks very much for testing this! John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000308-CURRENT crypto
At 07:39 AM 3/8/00 -0800, Jordan K. Hubbard wrote: I tried an FTP SNAP install this morning, and all the crypto libs from current were unavailable. I switched over to the debug console, but there was no additional info. The files seem to be on the ftp site just fine. Is this a known issue ? Please try again - I *just* fixed this problem and updated the floppies in-place. :) For just ftp (wizard) or on current (usw2) as well? Seems to be that 4.0-2307-CURRENT differ from wizard to usw2 and the 3/7 version on wizard falls between the 3/7 and 3/8 version on usw2. Huh? Aren't they supposed to be same? Will the ISO's reside on usw2 as well? It is faster after all. ;) Also a problem... Not sure when this started, but there is a problem with using mget. It works just fine on wizard, but on usw2 it only will grab the files in 4.0-MMDD-CURRENT and the src directory: ncftpmget [A-U]* [b-m]* p[or]* src p[or]*: No match. It doen't like globbing for directories anymore. They must be explicit. 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
Parallel port Zip drive and EPP mode
Here is a concern i have. I had a hard time getting my parallel port zip to work under 3.4. It turned out there may be a bug in my bios that required me to change from EPP mode to standard bi-directional. Walter noted that EPP mode worked OK for him under 3.4, but did not under -current. Oddly enough, EPP mode worked fine under win95, so there doesn't seem to be some innate incompatiblity between my laptop and Zip drives in EPP mode. Is this worth looking into? -- -= jm =- --- The opinions expressed in this message are the opinions of the mail program only, and not of the writer, his employer, or freebsd-uk.eu.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ERRATA on the 4.0-20000307-CURRENT release candidate (#3)
There were a couple of sysinstall related bogons, one related to variable toggling in rc.conf and another related to the crypto distribution (it was still looking in des/). Both of these have been fixed and rolled into the updated boot floppies as well as the ISO images, which are still uploading. The next errata item has to do with the rsaref package, which will not display its license properly when added through sysinstall. I understand the problem and am working on a fix right now. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000308-CURRENT crypto
For just ftp (wizard) or on current (usw2) as well? These snapshots are only going up on ftp, sorry for the confusion. The stuff on current is just the daily snapshot stuff and not entirely equivalent to the URLs I specifically gave out. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
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. 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: More ld-elf.so.1: assert failed messages
John Polstra wrote: In article [EMAIL PROTECTED], Donn Miller wrote: OK, here's some of the errors I get with Mozilla. It looks like it happens when Gdk runs out os SysV shared memory. Otherwise, if I don't get the "Gdk-WARNING **: shmget failed!", the ld.so erros never occur, and Mozilla runs OK. It seems as if Wine is working OK so far, though, although I probably haven't tested Wine enough: [...] /usr/libexec/ld-elf.so.1: Application locking error: 1 readers and 1 writers in dynamic linker. See DLLOCKINIT(3) in manual pages. This means that one thread was in the middle of a dlopen() call when another thread either called a new function for the first time (invoking the dynamic linker for lazy binding) or called dlsym(). Really the only _right_ place I can find to fix this kind of thing is in the application itself, by calling dllockinit() to set up locking for the dynamic linker invocations. I just reverted back to the "normal" version of ld-elf.so, the version without the patch. Mozilla doesn't have the problem with the "non-patch" version. So, maybe it isn't the application. Or, maybe the original, "non-patch" version wasn't doing something right. Just wondering, in case the problem isn't with Mozilla. I'm using Mozilla right now, with the original ld-elf.so.1. (The fonts are hard on my eyes.) - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FTP globbing bug (Re: 4.0-20000308-CURRENT crypto)
On Wed, 8 Mar 2000, Jeffrey J. Mountin wrote: Not sure when this started, but there is a problem with using mget. It works just fine on wizard, but on usw2 it only will grab the files in 4.0-MMDD-CURRENT and the src directory: ncftpmget [A-U]* [b-m]* p[or]* src p[or]*: No match. It doen't like globbing for directories anymore. They must be explicit. Yes! I had noticed this as well and wanted to check more carefully before opening my mouth to make sure I wasn't just smoking crack. This definitely needs to be looked at. 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-20000308-CURRENT crypto
At 09:26 AM 3/8/00 -0800, Jordan K. Hubbard wrote: For just ftp (wizard) or on current (usw2) as well? These snapshots are only going up on ftp, sorry for the confusion. The stuff on current is just the daily snapshot stuff and not entirely equivalent to the URLs I specifically gave out. OK, So I take it that the 0308 SNAP on current.freebsd.org still has this bug ? ---Mike Mike Tancsa, tel +1 519 651 3400 Network Administrator,[EMAIL PROTECTED] Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: howto for 3.4-STABLE - 4.0-CURRENT?
On Wed, 8 Mar 2000, Adriel Ickler wrote: cvsup to current make buildworld make buildkernel make installkernel - change - I just rebooted normally, the network came up fine, if you have any special kernel needs, make sure you have di lines in This may screw you because some device nodes (e.g. ATA drives) have changed from 3.x to 4.x. You really need to mergemaster and re-MAKEDEV before rebooting, which requires you to install mknod as described in UPDATING. You should also do the rest of the upgrade in single-user mode (e.g. I forgot and tried to boot multi-user, and the system paniced at boot trying to load the linux KLD from /etc/rc.). ok, here is where I discovered something nobody told me about. 4.0 moved me from DES to MD5. the effect was that none of the passwords worked. This is because you presumably didn't install the crypto sources and/or build them. luckily I was logged in as root already, and only had 4 accts, I just ran the passwd command and reset them. if its a nightmare to move your accounts, and/or you want to keep DES, I have been told that adding the line "auth_default = des" in /etc/auth.conf will keep you on DES. This won't do anything. 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: world breakage with NO_OPENSSL
On Wed, 8 Mar 2000, Matthew N. Dodd wrote: usr.sbin/ppp/ usr.sbin/pppd/ secure/libexec/telnetd/ (actually the Makefile below telnetd/ is the problem.) secure/usr.bin/telnet/ These all require simple !defined(NO_OPENSSL) additions. Known problem - see the patch I posted about 2 days ago which I already referred to in an earlier reply to you in this meta-thread. I think it's hit a bug in jordan.pl which means it isn't spitting out automatic commit approval; perhaps I should re-send 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: no openssh after build
Sheldon Hearn wrote: On Mon, 06 Mar 2000 16:38:44 PST, R Joseph Wright wrote: I just built a new world today and openssh does not appear to be installed. I have the directories /etc/ssh and /etc/ssl but they are empty. There is no /usr/bin/ssh. Last night's ``make world'' scored me a /usr/bin/ssh, but an empty /etc/ssh . I'm curious to know how /etc/ssh will be populated, since mergemaster won't pick up an sshd_config in src/etc . mm only knows about what's in /usr/src/etc/Makefile. ssh_config and sshd_config are in there, so if you run mm and you have those bits in your tree it'll install them. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000308-CURRENT crypto
At 09:26 AM 3/8/00 -0800, Jordan K. Hubbard wrote: For just ftp (wizard) or on current (usw2) as well? These snapshots are only going up on ftp, sorry for the confusion. The stuff on current is just the daily snapshot stuff and not entirely equivalent to the URLs I specifically gave out. Bummer. The xfer rate is so much better. ;) 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
RC3: APM on IBM Thinkpad 600E (2645,5A0)
Hi, I just installed RC3, and I have the same problem as on RC2, when I run "zzz" my machine turns off the monitor, stops the disk, etc etc. Actually is does everything it´s supposed to, except go to stand-by mode (give the beep and turn off). So when i press any key, the machine wakes up again?? Is this a know problem? All I did was to add apm_enable="YES" to rc.conf and remove the diskable in the KERNEL line, my dmesg looks like this: 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-2307-CURRENT #2: Wed Mar 8 20:07:09 CET 2000 root@:/usr/src/sys/compile/SOS Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (363.96-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV, PAT,PSE36,MMX,FXSR real memory = 200278016 (195584K bytes) avail memory = 190607360 (186140K bytes) Preloaded elf kernel "kernel" at 0xc0367000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: NeoMagic MagicMedia 256AV SVGA controller at 0.0 irq 11 pcic-pci0: TI PCI-1251 PCI-CardBus Bridge mem 0x50102000-0x50102fff irq 11 at device 2.0 on pci0 pcic-pci1: TI PCI-1251 PCI-CardBus Bridge mem 0x50101000-0x50101fff irq 11 at device 2.1 on pci0 csa0: Crystal Semiconductor CS4610/4611 Audio accelerator mem 0x5000-0x500f,0x5010-0x50100fff irq 11 at device 6.0 on pci0 pcm0: CS461x PCM Audio on csa0 pcm0: ac97 codec reports dac not ready isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xfcf0-0xfcff at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: Intel 82371AB/EB (PIIX4) USB controller at 7.2 irq 11 chip1: Intel 82371AB Power management controller port 0xefa0-0xefaf at device 7.3 on pci0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 pcic: management irq 10 pcic0: Intel i82365 at port 0x3e0 iomem 0xd irq 10 on isa0 pccard0: PC Card bus -- kludge version on pcic0 pccard1: PC Card bus -- kludge version on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: cannot reserve I/O port range pccard: card inserted, slot 1 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6149MB HITACHI_DK228A-65B [13328/15/63] at ata0-master using UDMA33 acd0: DVD-ROM TOSHIBA DVD-ROM SD-C2102 at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s3a ep0: 3Com Etherlink III 3C589 at port 0x240-0x24f irq 3 slot 1 on pccard1 ep0: Ethernet address 00:a0:24:60:02:36 ep0: supplying EUI64: 00:a0:24:ff:fe:60:02:36 ep0: unload stray irq 3 pccard: card disabled, slot 1 resumed from suspended mode (slept 00:00:10) pccard: card inserted, slot 1 ata0: resetting devices .. done ata1: resetting devices .. done ep0: 3Com Etherlink III 3C589 at port 0x240-0x24f irq 3 slot 1 on pccard1 ep0: Ethernet address 00:a0:24:60:02:36 ep0: starting DAD for fe80:0009::02a0:24ff:fe60:0236 ep0: DAD complete for fe80:0009::02a0:24ff:fe60:0236 - no duplicates found /\/\orten $eeberg, Systems Consultant @ Merkantildata - Enterprise Solutions #echo 'System Administrators suck :)' /dev/console To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RC3: APM on IBM Thinkpad 600E (2645,5A0)
On Wed, Mar 08, 2000 at 08:45:34PM +0100, Morten Seeberg wrote: Hi, I just installed RC3, and I have the same problem as on RC2, when I run "zzz" my machine turns off the monitor, stops the disk, etc etc. Actually is does everything it´s supposed to, except go to stand-by mode (give the beep and turn off). So when i press any key, the machine wakes up again?? Is this a know problem? All I did was to add apm_enable="YES" to rc.conf and remove the diskable in the KERNEL line, my dmesg looks like this: I have the exact same problem on my Thinkpad 600E, earlier I tracked it down to a change in the below interval. Only my wakes up without me touching anything ... *default date=2000.01.13.23.00.00 ok *default date=2000.01.15.23.00.00 cannot build *default date=2000.01.15.03.00.00 cannot build *default date=2000.01.14.12.00.00 cannot build *default date=2000.01.14.06.00.00 cannot build *default date=2000.01.16.18.00.00 cannot build *default date=2000.01.17.02.00.00 cannot build *default date=2000.01.17.23.00.00 cannot build *default date=2000.01.17.13.00.00 cannot build *default date=2000.01.14.03.00.00 cannot build *default date=2000.01.16.08.00.00 cannot build *default date=2000.01.18.22.00.00 builds - no suspend Is there any debug'ing we can enable, that will be enable us to track down what 'awakens it' ? /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work:Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek@ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RC3: No support for 3C589B/C (ep0) during install?
I just installed RC3 on my laptop, and I wasn´t able to use my 3Com PCMCIA 3C589C card during install?? Hmm this couldn´t be true, so I tried booting the floppies again, and this I actually read the text, and it really doesn´t make much sense :) *headlinePlease select IRQs that can be used by PC-cards/headline *Please specify an IRQs that CANNOT be used by PC-card for example, if you have a *soundcard that can't be probed by this installation floppy and it uses IRQ 10, you *have to choose "Option 1" or "Option 2" at this menu. * *Default IRQ 10, 11 *Option 1 IRQ 5, 11 (ex. soundcard on IRQ 10) *Option 2 IRQ 11 (ex. something on IRQ 5 and 10) Is it just me, or does the headline and description say the exact opposite of each other? Now, I got my card working by choosing Option 1, but Im not really sure why, as you can see below, my card uses IRQ 3 for some odd reason. Why doesn´t my PCMCIA card automatically use a higher free IRQ? (IRQ 3 is used by my serial ports AFAIK) IRQ 3 isn´t even mentioned in the Options above (only 5, 10 and 11) *This is how it shows itself after install, when enabling PCCARD: *ep0: 3Com Etherlink III 3C589 at port 0x240-0x24f irq 3 slot 1 on pccard1 *ep0: Ethernet address 00:a0:24:60:02:36 *ep0: supplying EUI64: 00:a0:24:ff:fe:60:02:36 *ep0: unload *stray irq 3 What is EUI64 BTW? And BTW; what does this mean? (DAD???): *ep0: starting DAD for fe80:0009::02a0:24ff:fe60:0236 *ep0: DAD complete for fe80:0009::02a0:24ff:fe60:0236 - no duplicates found /\/\orten $eeberg, Systems Consultant @ Merkantildata - Enterprise Solutions #echo 'System Administrators suck :)' /dev/console To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/etc/periodic/daily/200.backup-passwd and MD5
All flames welcome as a learning experience ;-) I am currently running a -current on a group of machines where I work. I decided to use the MD5 libscrypt passwords, and noticed something strange in the daily output e-mail. When the MD5 passwords are used the daily output e-mail fails to truncate the encrypted passwd from the /etc/master.passwd file before e-mailing out the diffs. This is the case even on a machine which was built today. I haven't seen any info on -current about it so I thought I would bring it up. I also wrote and attached small patch to take care of the issue in the short term. all it does is change: diff $bak/master.passwd.bak /etc/master.passwd |\ sed 's/^\([] [^:]*\):[^:]*:/\1:(password):/' to: diff $bak/master.passwd.bak /etc/master.passwd |\ sed 's/^\([^:]*\):[^:]*:/\1:(password):/' My logic could be messed up, so if there are any issues that I overlooked in the patch I would love to hear about them. I thought it might be a good thing to take care of quick before -RELEASE (yea!) Thanks all... Damieon Stark [EMAIL PROTECTED] *** /var/backups/200.backup-passwd Mon Feb 21 09:19:00 2000 --- /etc/periodic/daily/200.backup-passwd Mon Feb 21 09:19:28 2000 *** *** 16,22 if cmp -s $bak/master.passwd.bak /etc/master.passwd; then :; else echo "$host passwd diffs:" diff -u $bak/master.passwd.bak /etc/master.passwd |\ ! sed 's/^\([] [^:]*\):[^:]*:/\1:(password):/' mv $bak/master.passwd.bak $bak/master.passwd.bak2 cp -p /etc/master.passwd $bak/master.passwd.bak fi --- 16,22 if cmp -s $bak/master.passwd.bak /etc/master.passwd; then :; else echo "$host passwd diffs:" diff -u $bak/master.passwd.bak /etc/master.passwd |\ ! sed 's/^\([^:]*\):[^:]*:/\1:(password):/' mv $bak/master.passwd.bak $bak/master.passwd.bak2 cp -p /etc/master.passwd $bak/master.passwd.bak fi
Re: ssh strangeness in -current...
Oliver Fromme [EMAIL PROTECTED] writes: Apart from my stupidness of not checking the location of the binary first -- what did I do wrong, and what's the recommended way of handling this? Am I supposed to rm /usr/bin/ssh each time I install a new release or snapshot? I can't believe that. You could use /usr/bin/ssh, for a start. Note that this is OpenSSH, though, so there may be incompatibilities with ssh1. The other alternative is to put /usr/local/bin in the front of the path. A third alternative is to build without OpenSSH by tweaking make.conf. (Note that there is now /etc/default/make.conf which means that you can't look in /etc/make.conf for the new option.) 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: Parallel port Zip drive
On Wed, 08 Mar 2000, Walter Brameld wrote: On Wed, 08 Mar 2000, F. Heinrichmeyer wrote: It works if you can switch your parallel port to EPP (???) mode in the bios. Transfer speed raises also under windows with this configuration btw. Thanks again for the advice. For the record, that fixed it. Guess if I hadn't been so sleepy last night I might have noticed the settings. --Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh -- Walter Brameld Join the Army. Meet interesting people. Kill them. TANSTAAFL To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: RC3: No support for 3C589B/C (ep0) during install?
On 08-Mar-00 Morten Seeberg wrote: Now, I got my card working by choosing Option 1, but Im not really sure why, as you can see below, my card uses IRQ 3 for some odd reason. Why doesn´t my PCMCIA card automatically use a higher free IRQ? (IRQ 3 is used by my serial ports AFAIK) IRQ 3 isn´t even mentioned in the Options above (only 5, 10 and 11) I'm not sure why it works either but it does. FWIW, on the DuncePad I have here, the PC-Card controller (pcic0) uses irq 10. *This is how it shows itself after install, when enabling PCCARD: *ep0: 3Com Etherlink III 3C589 at port 0x240-0x24f irq 3 slot 1 on pccard1 *ep0: Ethernet address 00:a0:24:60:02:36 *ep0: supplying EUI64: 00:a0:24:ff:fe:60:02:36 *ep0: unload *stray irq 3 What is EUI64 BTW? Has to do with IPv6. And BTW; what does this mean? (DAD???): *ep0: starting DAD for fe80:0009::02a0:24ff:fe60:0236 *ep0: DAD complete for fe80:0009::02a0:24ff:fe60:0236 - no duplicates found More IPv6 stuff. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ 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
upgraded to -CURRENT (?) et al.
Dear users, I (last) cvupped -CURRENT on 6 March at about 11:00 pm GMT, and, with few (necessary) variations, I tried to follow the instructions in UPDATING on the next day. I *seem* to have upgraded to -CURRENT. FWIW, here is what I did: 1) /usr/src/make -j48 buildworld 2) /usr/src/sbin/mknod/make install 3) followed the directions to build/install a kernel. Remark: config -r core dumps (bad system call); config (no option) does not. 4) rebuilt disk /dev entries; updated the relevant files (/etc/fstab). In order not to forget anything, I issued various grep -r commands. 5) reboot in s.u.m. Remark I : the root partition is seen as wd1s2a; the others are seen correctly. Remark II: if one happens to reboot, one meets a FATAL TRAP; after rebooting, one is denied access to / . Workaround: I booted from another installation of mine (-STABLE) on another slice, and ran fsck from there. 6) /usr/src/make installworld I got this error: lib/libcom_errdoc [omissis] unrecognized option `--defsection=Programming development tools.' Error code 1 (six times) 7) /usr/src/usr.bin/xinstall/make clean all install NOSHARED=YES 8) /usr/src/make installworld It failed with the same errors as sub 6). 9) /usr/src/make -DNOINFO installworld I got another error: install: genassym: no such file or directory. Error code 71. Error code 1 (five times.) It was time to use ... the Force. 10) /usr/src/make -DNOINFO -k installworld 11) /usr/src/make -k installworld Alas, I did not log the sessions sub 10) and sub 11) because ... I did NOT believe I would succeed in making installworld #@[]*^§ [severely censored] 12) mergemaster, devices, sysinstall and (yet another) kernel by the book. Remark I: making sysintall failed: undefined reference in pccard Initialize. Error code 1. Remark II: this time config -r worked. If I had used -k properly, I would have finished earlier. I suppose I am somehow running -CURRENT (?) N.B. I am Italian and I chose MD5, discarding everything DES-related. I suppose this has automagically eliminated a few problems. Under -STABLE, I used to compile my kernels with a0ffa0ff flags for my IDE disks 0 and 1, and b0ff for my third IDE disk. Under -CURRENT, I specified the ata driver as per the suggestions in LINT, and I did NOT specified ata0 and ata1; which are indicated for older systems. The log messages show that all three disks are accessed in UDMA 33 mode and are seen as having **16** heads. However, I must miss something obvious here (yawn) how can I specify the LBA mode for my third disk ? Is it automagically set ??? I fear I can corrupt part of my filesytems: my /usr lives on my third IDE disk (formerly accessed in LBA mode.) Another problem. I get "isa0: unexpected tag 14" while booting. What am I missing ? There are other questions: e.g. X authentication fails. Pam.conf and ttys are all right, though. Before attacking all of them (grepping -r the d***ed wd disks and recompiling the related ports ...), I would like to be in a position to recompile things in /usr without running any risks to destroy that filesystem. In this way, I will also be able te remake the world once more ... I thank you very much in advance for any help. Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Parallel port Zip drive and EPP mode
On Wed, 08 Mar 2000, in a never-ending search for enlightenment, J McKitrick wrote: Here is a concern i have. I had a hard time getting my parallel port zip to work under 3.4. It turned out there may be a bug in my bios that required me to change from EPP mode to standard bi-directional. Walter noted that EPP mode worked OK for him under 3.4, but did not under -current. Oddly enough, EPP mode worked fine under win95, so there doesn't seem to be some innate incompatiblity between my laptop and Zip drives in EPP mode. Is this worth looking into? -- -= jm =- --- The opinions expressed in this message are the opinions of the mail program only, and not of the writer, his employer, or freebsd-uk.eu.org Let me try to add a little info to that. When I installed my zip on 3.4-STABLE, it worked right off the bat so I didn't pay any attention as to what dmesg said about the drive or the parallel port. I wish I had so I could provide the information for completeness. Initially under 4.0-CURRENT, my port came up NIBBLE and the drive as EPP 1.9. ON Fritz Heinrichmeyer's (Hope I got that right) advice, I changed the BIOS setting of my port to EPP 1.7, my only other choice. Here is the dmesg that resulted: 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: Tue Mar 7 16:17:46 EST 2000 root@:/usr/src/sys/compile/NEWKERN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon (463.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM - snip - ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 vpo0: Iomega Matchmaker Parallel to SCSI interface on ppbus0 imm0: EPP 1.9 mode sbc0: Creative SB16/SB32 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: SB DSP 4.16 on sbc0 unknown0: Game at port 0x200-0x207 on isa0 unknown1: Cqm at port 0x620-0x623 on isa0 ad0: 17206MB WDC AC418000D [34960/16/63] at ata0-master using UDMA33 ad1: 8693MB WDC AC29100D [17662/16/63] at ata0-slave using UDMA33 acd0: CDROM BCD-48SB CD-ROM at ata1-master using WDMA2 da0 at vpo0 bus 0 target 5 lun 0 da0: IOMEGA ZIP 100 PLUS J.66 Removable Direct Access SCSI-2 device da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) Mounting root from ufs:/dev/ad1s1a cd9660: Joliet Extension The Mobo is an ABIT BX6 Revision 2. Hope this may be of some help. -- 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: FreeBSD 4.0 release candidate #3 now available.
On Wed, 8 Mar 2000, Jordan K. Hubbard wrote: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-2307-CURRENT ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2307-CURRENT With ISO images available from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-2307-CURRENT/ I tried to burn this image and it was too big for a standard 74 min CD. 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
upgraded to -CURRENT (?) et al. III
Dear users, I forgot to specify another point in my first letter: "N.B. I am Italian and I chose MD5, discarding everything DES-related. I suppose this has automagically eliminated a few problems." I chose MD5 when installing FreeBSD-3.3-Release, whence I upgraded to -STABLE and finally to -CURRENT. Sorry for these omissions :-( I should really go to bed *sigh* Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Kerberos 5 in 4.0?
Hello, I have been searching through deja.com for over a week now and I can't find an answer to this question. I was wondering if 4.0 comes with kerberos 5 built-in? Or do I just use the kr5 port? Does it have a PAM? I want to use k5 and a PAM for k5 logins. I know this is "doable" with k4, but I keep seeing comments about how bad k4 is compared to k5. The sticking point seems to be the PAM. I've not seen a k5 PAM for FBSD. thanks, Ron++ PS. No flames please. I'm new to the mailing list. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 4.0 release candidate #3 now available.
On Wed, Mar 08, 2000 at 04:45:39PM -0800, Brian Beattie wrote: On Wed, 8 Mar 2000, Jordan K. Hubbard wrote: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-2307-CURRENT ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2307-CURRENT With ISO images available from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-2307-CURRENT/ I tried to burn this image and it was too big for a standard 74 min CD. Fit fine on the cdr that I burned (~549MB as I recall). -- Bob Willcox What is wanted is not the will-to-believe, [EMAIL PROTECTED] but the wish to find out, which is the exact Austin, TX opposite. -- Bertrand Russell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 4.0 release candidate #3 now available.
Urk! Geeze, how did I not notice that. Must have been the hour. I'm fixing this now, sorry guys. - Jordan On Wed, 8 Mar 2000, Jordan K. Hubbard wrote: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-2307-CURRENT ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2307-CURRENT With ISO images available from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-2307-CURRENT / I tried to burn this image and it was too big for a standard 74 min CD. 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: FreeBSD 4.0 release candidate #3 now available.
On Wed, 8 Mar 2000, Bob Willcox wrote: On Wed, Mar 08, 2000 at 04:45:39PM -0800, Brian Beattie wrote: On Wed, 8 Mar 2000, Jordan K. Hubbard wrote: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-2307-CURRENT ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2307-CURRENT With ISO images available from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-2307-CURRENT/ I tried to burn this image and it was too big for a standard 74 min CD. Fit fine on the cdr that I burned (~549MB as I recall). The image I got was 655MB, I suspect you grabbed it while it was uploading. 500 'EPRT |1|138.95.12.36|49359|': command not understood. 200 PORT command successful. 150 Opening ASCII mode data connection for 'file list'. total 1297625 -rw-r--r-- 1 root 207 117 Mar 8 23:42 CHECKSUM.MD5 -rw-r--r-- 1 2035 207641435648 Mar 8 22:18 install-alpha.iso -rw-r--r-- 1 2035 207687331328 Mar 8 22:27 install-i386.iso 226 Transfer complete. -- Bob Willcox What is wanted is not the will-to-believe, [EMAIL PROTECTED] but the wish to find out, which is the exact Austin, TX opposite. -- Bertrand Russell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message 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: upgraded to -CURRENT (?) et al. III
On Wed, 08 Mar 2000, in a never-ending search for enlightenment, Salvo Bartolotta wrote: Dear users, I forgot to specify another point in my first letter: "N.B. I am Italian and I chose MD5, discarding everything DES-related. I suppose this has automagically eliminated a few problems." I chose MD5 when installing FreeBSD-3.3-Release, whence I upgraded to -STABLE and finally to -CURRENT. Sorry for these omissions :-( I should really go to bed *sigh* Best regards, Salvo Yeah, join the club. Read some of my screw-ups -- 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: FreeBSD 4.0 release candidate #3 now available.
On Wed, Mar 08, 2000 at 05:34:02PM -0800, Brian Beattie wrote: On Wed, 8 Mar 2000, Bob Willcox wrote: On Wed, Mar 08, 2000 at 04:45:39PM -0800, Brian Beattie wrote: On Wed, 8 Mar 2000, Jordan K. Hubbard wrote: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-2307-CURRENT ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2307-CURRENT With ISO images available from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-2307-CURRENT/ I tried to burn this image and it was too big for a standard 74 min CD. Fit fine on the cdr that I burned (~549MB as I recall). The image I got was 655MB, I suspect you grabbed it while it was uploading. Quite possible. I have not yet tried to use it. I notice now that the install-i386.iso file is gone. Oh, well. Looks like I probably have another coaster. :-( Bob 500 'EPRT |1|138.95.12.36|49359|': command not understood. 200 PORT command successful. 150 Opening ASCII mode data connection for 'file list'. total 1297625 -rw-r--r-- 1 root 207 117 Mar 8 23:42 CHECKSUM.MD5 -rw-r--r-- 1 2035 207641435648 Mar 8 22:18 install-alpha.iso -rw-r--r-- 1 2035 207687331328 Mar 8 22:27 install-i386.iso 226 Transfer complete. -- Bob Willcox What is wanted is not the will-to-believe, [EMAIL PROTECTED] but the wish to find out, which is the exact Austin, TX opposite. -- Bertrand Russell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
more question about make release
hi, Finallly I got make release work :^) thx to everyone who helping me about. After make release, I believe nothing about X has been add into. I am just woundring about how do I make a release which is just the same as those SNAP released on the net? So I can use it to burn a CD, and use it to install on a system with no NIC. thanks in advance... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
4.0 RC3 install problem from ftp.FreeBSD.org
Says, it can't chdir into the 4.0-2307-CURRENT directory. It does work from current.FreeBSD.org. Looking on ftp.freebsd.org I do not see a link under /pub/FreeBSD/releases/i386/ ? that maybe the missing link ? -- Regards, Ulf. - Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bridging broken in -current AND -stable
On Thu, 9 Mar 2000, Boris Staeblow wrote:
On Wed, Mar 08, 2000 at 11:15:23PM +0100, Luigi Rizzo wrote:
Is it possible that bridging is broken in -current and -stable?
no, but the "de" driver on bridging is now unsupported and i could not
find the time to make it work after recent fixes to the bridging code.
Ooo n! :-((
The best nic´s all around are unsupported? ;)
can you switch to some supported card ("ed" or "fxp") ?
Hmm, "ed" is lousy and "fxp" is too expensive for me now...
How great is the chance that good old dec is coming back?
I could help you testing your code... :)
I would like to prevent to buy new hardware again.
I have what appear to be functional patches to provide support for if_dc,
used in the common and cheap PCI Linksys ethernet cards (LNE100TX?). If
jkh approves the commit, I can stick it in before the release. I don't
have access to an if_de card where I am currently, so won't be able to
look at that for at least a week or two.
The patch for if_dc is below.
Robert N M Watson
[EMAIL PROTECTED] http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services
Index: if_dc.c
===
RCS file: /home/ncvs/src/sys/pci/if_dc.c,v
retrieving revision 1.7
diff -u -r1.7 if_dc.c
--- if_dc.c 2000/01/24 17:19:37 1.7
+++ if_dc.c 2000/03/08 18:15:55
@@ -122,6 +122,11 @@
#include net/bpf.h
+#include "opt_bdg.h"
+#ifdef BRIDGE
+#include net/bridge.h
+#endif
+
#include vm/vm.h /* for vtophys */
#include vm/pmap.h/* for vtophys */
#include machine/clock.h /* for DELAY */
@@ -2099,14 +2104,30 @@
ifp-if_ipackets++;
eh = mtod(m, struct ether_header *);
- /*
-* Handle BPF listeners. Let the BPF user see the packet, but
-* don't pass it up to the ether_input() layer unless it's
+ /* Handle BPF listeners. Let the BPF user see the packet */
+ if (ifp-if_bpf)
+ bpf_mtap(ifp, m);
+
+#ifdef BRIDGE
+ if (do_bridge) {
+ struct ifnet *bdg_ifp ;
+ bdg_ifp = bridge_in(m);
+ if (bdg_ifp != BDG_LOCAL bdg_ifp != BDG_DROP)
+ bdg_forward(m, bdg_ifp);
+ if (((bdg_ifp != BDG_LOCAL) (bdg_ifp != BDG_BCAST)
+ (bdg_ifp != BDG_MCAST)) || bdg_ifp == BDG_DROP) {
+ m_freem(m);
+ continue;
+ }
+ }
+
+ eh = mtod(m, struct ether_header *);
+#endif
+
+ /* Don't pass it up to the ether_input() layer unless it's
* a broadcast packet, multicast packet, matches our ethernet
* address or the interface is in promiscuous mode.
*/
if (ifp-if_bpf) {
- bpf_mtap(ifp, m);
if (ifp-if_flags IFF_PROMISC
(bcmp(eh-ether_dhost, sc-arpcom.ac_enaddr,
ETHER_ADDR_LEN)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
building ports
within the last 4 days ive upgraded my system from 3.4-stable to -current. until this morning, i had no problems really, but then (this morning) i no longer was able to build any ports, kept receiving error: Your system is too old to use this bsd.port.mk. You need a fresh make world or an upgrade kit. Please go to http://www.FreeBSD.org/ports/ or a mirror site and follow the instructions. now there is obviously no upgrade kit for -current and i just did a make world, yet i still get this error. ive also tried deleting my entire ports collection and recvsuping fresh, but still same error. any ideas how to rectify? Jeremy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: building ports
Howdy, Have a look in bsd.port.mk for the version number that it needs to build with. Then make a copy of /var/db/port.mkversion. Edit /var/db/port.mkversion with the version number that bsd.port.mk requires. I had this same problem when the 34upgrade package had been altered with a new version number, but had not been released as a new package... Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ishmael Sent: Tuesday, 9 March 1999 14:44 To: [EMAIL PROTECTED] Subject: building ports within the last 4 days ive upgraded my system from 3.4-stable to -current. until this morning, i had no problems really, but then (this morning) i no longer was able to build any ports, kept receiving error: Your system is too old to use this bsd.port.mk. You need a fresh make world or an upgrade kit. Please go to http://www.FreeBSD.org/ports/ or a mirror site and follow the instructions. now there is obviously no upgrade kit for -current and i just did a make world, yet i still get this error. ive also tried deleting my entire ports collection and recvsuping fresh, but still same error. any ideas how to rectify? Jeremy 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: More ld-elf.so.1: assert failed messages
In article [EMAIL PROTECTED], Donn Miller [EMAIL PROTECTED] wrote: I just reverted back to the "normal" version of ld-elf.so, the version without the patch. Mozilla doesn't have the problem with the "non-patch" version. So, maybe it isn't the application. Or, maybe the original, "non-patch" version wasn't doing something right. Just wondering, in case the problem isn't with Mozilla. I'm using Mozilla right now, with the original ld-elf.so.1. (The fonts are hard on my eyes.) Well, the whole situation is very complicated. I'll append a long-winded mail about it that I sent to Jordan and Peter. (No answer yet, but then Jordan was out of the country and Peter only answers 20% of his mail as a rather crude form of flow control. ;-) Briefly, we've been through 3 phases with the dynamic linker. 1. The olden days. Resolving symbols was a read-only operation, so it was re-entrant. Dlopen was a "write" operation, so if any thread was doing a dlopen then no other thread could be doing a dlopen or a symbol lookup. There weren't very many multi-threaded apps, and there were even fewer that used dlopen. So nobody saw any problems, even though the potential was there. 2. What is in current today. Resolving symbols is a "write" operation, and so is dlopen. So two threads trying to resolve symbols simultaneously need mutual exclusion or problems can manifest themselves. (Resolving symbols being a "write" operation is basically an implementation screw-up on my part, which is corrected in the patch I posted.) Meanwhile, there are a lot more multi-threaded applications. So we're seeing problems. In an attempt to solve the problems, I did two things: (a) provided the dllockinit(3) interface so threads packages could tell the dynamic linker how to do locking, and (b) implemented some default locking that would work in some cases when threads packages didn't use dllockinit. The default locking works for userland threads packages, but not for kernel threads or rfork threads. 3. The patch I posted. It made symbol resolution read-only again, but it also removed the default locking. I was hoping that with re-entrant symbol resolution, the default locking wouldn't be needed any more. The default locking is extremely bogus, because it makes assumptions about how threads work which there's no real reason to believe are correct. John [Here's the mail I sent that explains things in more detail.] Sorry for this long mail, but I need your advice about a situation that's kind of complicated. I don't know whether you've been following -current, but there's a new chapter in the continuing saga of "The Dynamic Linker Breaks Some Random Multi-threaded Program During a Code Freeze." This time it's wine. These breakages are all connected, and I'll try to explain the whole story below, if only so you won't think I just do shoddy work. :-) What I am looking for from you is some guidance as to how much we want to mess with the rtld at the 11th hour to fix wine. There are two ways a program can enter the dynamic linker: either (A) by innocently calling some external function for the first time, causing lazy binding to be done for that function, or (B) by deliberately calling dlopen() or one of its friends. In long ago olden times, A was effectively a read-only operation, while B mucked with a bunch of data structures in the dynamic linker. So a program could safely have lots of threads doing A at the same time, or just one thread doing B, but not both. Then the need for better-scoped symbol lookups began to arise, and I finally bit the bullet and made the lookup algorithm quite a bit more complicated, a la Solaris and Linux. This was the change we decided to merge into 3.4 just before release, because it fixed some important application -- which one I can't remember any more. The changes I put in to do this unfortunately changed operation "A" above into a write operation too. I.e., the lazy binding was no longer reentrant. Soon I started receiving reports of strange failures in multi-threaded programs. I attacked this problem by introducing calls to reader/writer locking functions in key places. Since locking depends on the underlying threads package, I also created the dllockinit() API through which each threads package could tell the dynamic linker how to do locking. At the same time I added default locking methods which would make their best effort to lock (basically by masking a bunch of signals) in case the threads package hadn't been modified to call dllockinit(). That's where things stand in -current today. Unfortunately, wine uses rfork() to make threads, so each thread is in its own process. Consequently, the signal masking in the default locking methods is ineffective. Occasionally the dynamic linker gets reentered and an assert fails. I have changes in my local tree which fix the lookup algorithm so it is reentrant again. I didn't think it was possible before, but then I found
Paralle mode ZIP support
Will NIBBLE mode still be supported in 4.0? Has anyone tried a ZIP drive with bios set at ECP or standard setting? I would like to know what to expect if i upgrade. -- -= jm =- --- Student Loan Officer: "Mr. Wright? We'd like to know what you did with the $30,000 dollars we gave you for college." Steven Wright: "I gave it to my friend Bob, and he built a nuclear weapon with it. And i'd really appreciate it if you didn't call me anymore." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bridging broken in -current AND -stable
Is it possible that bridging is broken in -current and -stable?
no, but the "de" driver on bridging is now unsupported and i could not
find the time to make it work after recent fixes to the bridging code.
Ooo n! :-((
The best nic_s all around are unsupported? ;)
let me doubt it. i have had a fair amount of trouble with these nics,
maybe it's driver's fault, but still... anyways, the driver is
not as easy to work on as others.
can you switch to some supported card ("ed" or "fxp") ?
Hmm, "ed" is lousy and "fxp" is too expensive for me now...
at 10Mbit the ed does a reasonable job considering todays machines.
will try and have a look at the de driver some time in the future.
cannot tell how far asway, sorry.
cheers
luigi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
enabling APIC without SMP
Hi, I'm using a FreeBSD-current snapshot from 3rd January 2000. It seems that in order to enable APICs (option APIC_IO in kernel configuration file), one needs to also compile the kernel with SMP support (option SMP in kernel configuration file). While enabling the APIC is desirable even on a uniprocessor (provides more IRQs, interrupt ovhd becomes less, provides on-chip timer), enabling SMP support on a uniprocessor brings down the performance (I've noticed a degradation of 22% in performance of a webserver when a kernel was compiled with SMP support than without). Would it be possible to allow enabling the APIC without requiring support for SMP in future versions of FreeBSD ? Since I'm using a snapshot that's about two months old, I apologize if the above has already been addressed in the latest snapshots. - Mohit To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
