Re: New version of TAP driver for FreeBSD -current
Long time back i sent request to the list and asked about including this driver into the source tree. i still did not receive any reply. Some people seems to be using this driver for Ethernet tunneling (with VTUN software). Somebody even requested for OpenBSD port. So it would be really nice to hear from one of the commiters. Hi Maksim, I've looked at this driver and think it looks useful, though I'm a little concerned about the handling of bridge support. We don't really encourage users to edit module Makefiles just to enable a given feature in the compiled module since that naturally leads to situations where one /modules directory is not the same as another (where you might want to copy things), even though all the same module names appear. It also leads to version skew between the kernel and the modules since sliding a new kernel into place which doesn't have BRIDGE support would now mysteriously break a module, leading to some confusion to any admin new on the scene. Isn't there a better way of enabling support in the module all the time and conditionally using it only if the kernel also provides the right support? At that point it would be my opinion (and mine only) that it was ready to come into FreeBSD-current as a new feature. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_de as a module...
Any file called opt_*.h that is not present is created (empty). ...except the removed opt_*.h are not empty; hence the added headers in my patch. 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
HEADS UP: recent panics fixed
Please let me know if any of you still have spontaneous panics! -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' -- Forwarded message -- Date: Mon, 10 Jul 2000 23:47:38 -0700 (PDT) From: Brian Feldman [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: cvs commit: src/sys/dev/randomdev yarrow.c green 2000/07/10 23:47:38 PDT Modified files: sys/dev/randomdevyarrow.c Log: One should never allocate 4-kilobyte structs and such on the interrupt stack. It's bad for your machine's health. Make the two huge structs in reseed() static to prevent crashes. This is the bug that people have been running into and panic()ing on for the past few days. Reviewed by: phk Revision ChangesPath 1.8 +7 -3 src/sys/dev/randomdev/yarrow.c To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d things...
On Mon, 10 Jul 2000, Mikel wrote: Kelly Yancey wrote: How about rather then separate directories, you prefix the symlink names with 'S' for startup scripts and 'K' (for "kill") for shutdown scripts. Then, you rename rc.d to rc3.d... I like it. It's clean and simple, almost to the point of being elegant. But why bother adding rc?.d if you are going to right it to handle s or k then the present home should be fine, no? It was a reference to how SysV organized it's rc scripts. SysV implements 'run-levels' for which there is a rcX.d for each run-level. The startup/shutdown scripts for a run-level are executed at transitions between levels. In any event, it was a poor attempt at humor on my part. Don't go down this road, read the archives to see why (search for init and runlevels). 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
Re: etc/rc.d things...
Cyrille Lefevre wrote: http://www.freebsd.org/~dfr/devices.html off topic. M... I must have copied the wrong link, then... http://www.freebsd.org/~eivind/newrc.html well. what about a mix of the SystemV approach (ala HP-UX) and the IRIX one (using something like chconfig). HP-UX : /sbin/init.d/script start_msg|stop_msg|start|stop (FMPOV, there isn't not enough possible choises, such as status, restart, config, command, etc.) /sbin/rc[S0-5].d/[SK][0-9][0-9][0-9]script linked to /sbin/init.d/script ^^ This is confusing and difficult ot manage. /sbin/rc (+ /sbin/rc.util) sources /etc/rc.config then runs /sbin/rc?.d startup files /etc/rc.config.d/services are configuration files (ala bourne shell). Non-centralized configuration is frowned upon. Having to find which file has something, or having to read through multiple files to understand how the system is configured is a disadvantage wrt to the present system. /sbin/rc.config sources /etc/rc.config.d configuration files. /usr/sbin/ch_rc is not so easy to use to modify /etc/rc.config.d/services. IRIX : oops, don't remember how works startup scripts. I just remember me configurations files : /sbin/chconfig [on|off] service or something like that. (don't remember if it's possible to change options through chconfig, but I guess no). /etc/config/services enable or disable services. /etc/config/services.options just contains arguments to services. so, a mix of both w/o the levels stuffs + a /etc/rc.default.d (a synonym to /etc/defaults/rc.conf but in separate files between HP-UX and IRIX configuration files) would be a begining. It would be a waste of time. Without the levels, we are gaining nothing, and we loose in additional useless complexity. Alas, "levels" is a half-assed solution, because the states in which a system can be in are in a graph. The above proposal doesn't have an ink of a chance. Please, read Eivind's page, and read the numerous previous post on this topic. and my favorite substitute proposal: http://www.roguetrader.com/~brandon/sas/. effectively, the last one is interresting. a major problem w/ this one is the use of "perl" which is not available a boot time since it is located in /usr. I'm sure it can be easily done as a C program. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] jkh _DES: The Book of Bruce has only one sentence in it, and it says "the actual directives of my cult are left as an exercise for the reader. Good luck." EE jkh: does it really include the 'good luck' part? jkh EE: OK, I made that part up. jkh EE: I figured it should sound a bit more cheery than how Bruce initially dictated it to me. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d things...
"Daniel C. Sobral" [EMAIL PROTECTED] writes: Cyrille Lefevre wrote: HP-UX : /sbin/init.d/script start_msg|stop_msg|start|stop (FMPOV, there isn't not enough possible choises, such as status, restart, config, command, etc.) /sbin/rc[S0-5].d/[SK][0-9][0-9][0-9]script linked to /sbin/init.d/script ^^ This is confusing and difficult ot manage. I'm just explaining HP-UX and IRIX implementations for someone who don't know them. /sbin/rc (+ /sbin/rc.util) sources /etc/rc.config then runs /sbin/rc?.d startup files /etc/rc.config.d/services are configuration files (ala bourne shell). Non-centralized configuration is frowned upon. Having to find which file has something, or having to read through multiple files to understand how the system is configured is a disadvantage wrt to the present system. not so difficult if a command do that for you. (show, change, start and stop) Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "%no-spam" pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "%no-spam" to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_de as a module...
On Mon, 10 Jul 2000, Nick Hibma wrote: The opt_ files can be generated by the makefiles, so there is no reason to remove those, see sys/modules/usb/Makefile SRCS = bus_if.h device_if.h usb_if.h usb_if.c \ vnode_if.h \ opt_usb.h \ ... Any file called opt_*.h that is not present is created (empty). The opt_ files are used includes, so removing them breaks certain functionality in both the statically compiled version and the module. Empty ones for the module only break this functionality for the module. Modules shouldn't depend on options. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0 pod2man ports
On 10 Jul, Will Andrews wrote: Only if ports-base isn't anymore in ports-all or my local CVS tree is ports-base was/has never [been] in ports-all, for some strange reason. Really? /usr/share/examples/cvsup/ports-supfile: ---snip--- ## Ports Collection. # # The easiest way to get the ports tree is to use the "ports-all" # mega-collection. It includes all of the individual "ports-*" # collections, ports-all # These are the individual collections that make up "ports-all". If you # use these, be sure to comment out "ports-all" above. # # Be sure to ALWAYS cvsup the ports-base collection if you use any of the # other individual collections below. ports-base is a mandatory collection # for the ports collection, and your ports may not build correctly if it # is not kept up to date. #ports-base ---snip--- I read this as: If you didn't use "ports-all", you have to use "ports-base". If you use "ports-all", "ports-base" is already included. And: ---snip--- (2) netchild@ttyp2% ident /usr/ports/Mk/bsd.port.mk /usr/ports/Mk/bsd.port.mk: $FreeBSD: ports/Mk/bsd.port.mk,v 1.341 2000/07/04 08:47:50 asami Exp $ ---snip--- If it isn't included, I would have trouble because of the DISTNAME - PORTNAME/PORTVERSION change. Bye, Alexander. P.S.: Ade: the patch works, thanks. -- http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
IPv6 support for installer
Hi, I wrote IPv6 support code for FreeBSD installer. It was tested by Japanese IPv6 guys and seems OK. So, I'd like to commit it. Could someone please review it before commit? There are the diff against 5.0-CURRENT and FD images built under 4.0-STABLE here: http://www.imasy.or.jp/~ume/ipv6/test/flp/ However, there is few mirror servers which is IPv6 capable in the world yet. It is too sad. So, I wish to added `IPv6 ready' section to FTP server list. But, I know only one server ftp7.jp.freebsd.org. I don't know if there are any other IPv6 ready mirror servers. If available, please let me know. -- Hajimu UMEMOTO @ Business Solution System Development Div., Hitachi Ltd. E-Mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] URL: http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: New version of TAP driver for FreeBSD -current
Jordan, I've looked at this driver and think it looks useful, though I'm a little concerned about the handling of bridge support. We don't really encourage users to edit module Makefiles just to enable a given feature in the compiled module [...] i think that whole ``#ifdef BRIDGE'' section can be removed from the code. ``ether_input'' seems to be take care of it. it also feeds frame to ``bpf'', so it also can be removed. thanks to Nick Sayer for the hint :) i just got e-mail that makes a good point about Ethernet bridging quote it seems freebsd 4.x bridgin code is somewhat broken.. (it initializes the tables of devices it can bridge at boot time).. thus tap0 isnt available yet.. so basically bridging doesnt work ;( /quote ooops :) will check on it :) seems to me we need some interface to add/remove interfaces to/from bridge. Thanks, emax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Update IPv6 support for tcp_wrappers
Hi, I updated the patch for tcp_wrappers to support IPv6 scoped address. It enables us to control link-local connections by interface like this: ALL : ALL@[fe80::%ed0]/10 : allow ALL : ALL@[fe80::]/10 : deny I'd like to commit it. Though, new IPv6 support code is running without any problems over two months, it has many changes and is not reviewed. I think tcp_wrapper is nervous part of security. Could someone pleace review it? The patch is available from: http://www.imasy.or.jp/~ume/ipv6/FreeBSD/tcp_wrappers-scopeid.diff Thanks, -- Hajimu UMEMOTO @ Business Solution System Development Div., Hitachi Ltd. E-Mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] URL: http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
*weird* post-upgrade problem
Before I start digging into this, I thought someone might have a lead
for me. The archives say nothing, although I'm not sure how to search
on something like this. ("Just Plain Weird" generates too many hits.)
I just upgraded to yesterday's -current from last week's -current.
via make buildworld, make buildkernel, make installkernel, and make
installworld, mergemaster, blah blah blah.
Now, when I boot, I get:
No /boot/loader
FreeBSD/i386 BOOT
Default: 0:ad(0,a)/kernel
boot:
So, I typed in the default. Nothing seemed to happen, but the hard
drive lit up, so I figured that I'd leave it be. No dmesg appeared.
Moments later, however, a login prompt appears. The keyboard is still
nonresponsive. I can access network services the laptop offers, but I
don't have telnetd or sshd installed. :(
Does anyone have *any* clue on where I should start to look? I'm
rigging up a serial console as soon as I'm done here.
Thanks,
==ml
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: KAME integration and plans
Kris Kennaway wrote: In this vein, I'd like to suggest a new "hands-off" policy of not committing gratuitous changes to KAME-derived code, including manpage changes, unless: a) The commit is required for operation on FreeBSD (in which case it's not really gratuitous) I'd like to commit this: --- stf.4 2000/07/04 16:39:23 1.4 +++ stf.4 2000/07/11 13:44:47 @@ -36,7 +36,7 @@ .Nd .Tn 6to4 tunnel interface .Sh SYNOPSIS -.Cd "pseudo-device stf" +.Cd "pseudo-device gif" .Sh DESCRIPTION The .Nm 'pseudo-device stf' gives an error, stf lives in the gif driver, so this is required really. Is that ok? Is there anyone at KAME I should send this to as well? Sheldon Hearn will be taking care of passing the manpage diffs back to KAME. ah... right. I guess that answers my question. :-) Sheldon - you can commit this yourself if you want, or shall I do it and you just take care of passing it back to KAME? It's releated to PR 19163 by the way. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D PGP signature
re: *weird* post-upgrade problem
Well, I fixed the problem with a serial console, and doing cp /boot/loader.old /boot/loader Has anyone else seen anything like this? Or is it flat-out pilot error? Thanks, ==ml To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: KAME integration and plans
On Tue, 11 Jul 2000 14:56:35 +0100, Ben Smithurst wrote: 'pseudo-device stf' gives an error, stf lives in the gif driver, so this is required really. Is that ok? Is there anyone at KAME I should send this to as well? I'm interested to see how the KAME folks react to our chucking out the pseudo-device keyword from config(8). :-) Sheldon Hearn will be taking care of passing the manpage diffs back to KAME. ah... right. I guess that answers my question. :-) Sheldon - you can commit this yourself if you want, or shall I do it and you just take care of passing it back to KAME? It's releated to PR 19163 by the way. For now, I'll be looking at passing back to the KAME folks all those fixes that this pending merge will blow away. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d things...
On Mon, 10 Jul 2000, Mike Meyer wrote: :Daniel C. Sobral writes: : Mike Meyer wrote: : The multiple levels are there to deal with changes in state. In BSD, for : instance, we have single user/multi-user. A number of other variations : can exist, both in heavy duty servers where you might want to bring : certain services down for upgrade and then back up, and "desktop" : machines, such as notebooks where you can be stand-alone, docked into : different networks (eg. home/work). : :I'm familiar with why mutliple levels exist. I've never run into a :system that had a real use for more than three run levels - powered :off, maintenance, and up - though I've not dealt with Some of the machines I work on have three useful multi-user states. Runlevel 2 is plain-old multi-user mode, where filesystems are mounted, and the normal collection of services (mail, telnetd, ftpd, etc) are running. Run level 3 adds the DBMS, run level 4 adds the database dependent application. :P.S. - anyone else remember rc.single? Anyone care? Haven't seen one since Ultirx. shudder. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: Inode numbers in daily security output.
I've just changed the daily security secipt to include the inode numbers of suid files. This means the first time you run the updated script you will see lots of files have "changed" - this is just the inclusion of the inode numbers in the listing. I'd like to MFC this to 4.X in a few days, but I'm not sure if I should wait 'till after 4.1 is released. Opinions? David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
re: *weird* post-upgrade problem
If you dont use the loader, then the device.hints wont load and you wont have a console for the kernel to print to. I had the same symptoms the other day when I typo'ed the name of the device.hints file. Don't know where your loader went but if I were you I'd try compiling it and sticking it in instead of the old one. If you dont like the device.hints thing, there is some way to compile it in staticly. On Tue, 11 Jul 2000, Michael Lucas wrote: Well, I fixed the problem with a serial console, and doing cp /boot/loader.old /boot/loader Has anyone else seen anything like this? Or is it flat-out pilot error? Thanks, ==ml 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
ppp-related panic in sbdrop()
Hi,
I've finally managed to capture a crashdump after a panic in sbdrop(). The
machine in question uses ppp/ipfw/natd to connect a small LAN to the
outside world via a DSL link. ppp started to misbehave: NS queries were
sent out but didn't come back (I had tcpdumps running on both tun0 and
ed1). I tried to terminate ppp by sending a SIGTERM. ppp (pid 78) was
still around after a minute, so I send a SIGTERM. The machine crashed
immediately.
The machine world as of 7/7, I've only added the latest type fix to
ppp/bundle.c (rev 1.99).
The point of doom:
bash# gdb -k /sys/compile/UE/kernel.debug /var/crash/vmcore.0
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 3952640
initial pcb at 325320
panicstr: sbdrop
panic messages:
---
panic: sbdrop
syncing disks...
done
Uptime: 1h4m5s
dumping to dev #da/0x20001, offset 190228
dump 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38
37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9
8 7 6 5 4 3 2 1
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
(kgdb) wwhheerree
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
#1 0xc01717f4 in poweroff_wait (junk=0xc02b3a26, howto=-946356848)
at ../../kern/kern_shutdown.c:553
#2 0xc01931c8 in sbdrop (sb=0xc797bd90, len=158)
at ../../kern/uipc_socket2.c:793
#3 0xc0193058 in sbflush (sb=0xc797bd90) at ../../kern/uipc_socket2.c:772
#4 0xc0192b11 in sbrelease (sb=0xc797bd90, so=0xc6d59b40)
at ../../kern/uipc_socket2.c:455
#5 0xc0191443 in sorflush (so=0xc6d59b40) at ../../kern/uipc_socket.c:988
#6 0xc01900ad in sofree (so=0xc6d59b40) at ../../kern/uipc_socket.c:262
#7 0xc01901de in soclose (so=0xc6d59b40) at ../../kern/uipc_socket.c:327
#8 0xc018553a in soo_close (fp=0xc0f8fe40, p=0xc74b32a0)
at ../../kern/sys_socket.c:193
#9 0xc0166165 in fdrop (fp=0xc0f8fe40, p=0xc74b32a0) at ../../sys/file.h:212
#10 0xc01660ab in closef (fp=0xc0f8fe40, p=0xc74b32a0)
at ../../kern/kern_descrip.c:1079
#11 0xc0165dfc in fdfree (p=0xc74b32a0) at ../../kern/kern_descrip.c:945
#12 0xc016854d in exit1 (p=0xc74b32a0, rv=9) at ../../kern/kern_exit.c:186
#13 0xc01732d2 in sigexit (p=0xc74b32a0, sig=9) at ../../kern/kern_sig.c:1499
#14 0xc017304c in postsig (sig=9) at ../../kern/kern_sig.c:1402
#15 0xc028e6f0 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = -1077940036, tf_esi = 134920284, tf_ebp = -1077940004,
tf_isp = -946356268, tf_ebx = 672838652, tf_edx = 134909952,
tf_ecx = 2048, tf_eax = 29, tf_trapno = 7, tf_err = 2,
tf_eip = 673074366, tf_cs = 31, tf_eflags = 647, tf_esp = -1077940096,
tf_ss = 47}) at ../../i386/i386/trap.c:164
#16 0xc02838f5 in Xint0x80_syscall ()
#17 0x80781c6 in ?? ()
#18 0x806eaa9 in ?? ()
#19 0x806e1fb in ?? ()
#20 0x8078778 in ?? ()
#21 0x805996f in ?? ()
#22 0x804ccd8 in ?? ()
#23 0x806a776 in ?? ()
#24 0x806a35f in ?? ()
#25 0x804b0a1 in ?? ()
(kgdb) frame 2
#2 0xc01931c8 in sbdrop (sb=0xc797bd90, len=158)
at ../../kern/uipc_socket2.c:793
793 panic("sbdrop");
(kgdb) print sb
$1 = (struct sockbuf *) 0xc797bd90
(kgdb) print *sb
$2 = {sb_cc = 158, sb_hiwat = 20480, sb_mbcnt = 512, sb_mbmax = 163840,
sb_lowat = 1, sb_mb = 0x0, sb_sel = {si_pid = 0, si_note = {
slh_first = 0x0}, si_flags = 0}, sb_flags = 64, sb_timeo = 0}
(kgdb) print len
$3 = 158
(kgdb) print m
$4 = (struct mbuf *) 0xc02b3a26
(kgdb) print *m
$5 = {m_hdr = {mh_next = 0x72646273, mh_nextpkt = 0x4e00706f,
mh_data = 0x63706900 Address 0x63706900 out of bounds,
mh_len = -1377828864, mh_type = -16336, mh_flags = 73}, M_dat = {MH = {
MH_pkthdr = {rcvif = 0x6d6d7564, len = -1373634439,
header = 0x616dc030 Address 0x616dc030 out of bounds,
csum_flags = 1668248440, csum_data = 1718968939, aux = 0xae60},
MH_dat = {MH_ext = {
ext_buf = 0x616dc030 Address 0x616dc030 out of bounds,
ext_free = 0x636f7378, ext_size = 1937007979, ext_ref = 0xaea0},
MH_databuf =
"0Àmaxsockets\000\000 ®0Àsockbuf_waste_factor\000\000\000\000à®0Àkern.ipc.maxsockets\000\004¯0À\000\000\000\000\000\000\000\000\024¯0Àaccept\000connec\000sfbufa\000\000\000\000\000\000\000\000sf_buf_ref:
referencing a free sf_buf", '\000' repeats 27 times, "sf_buf_free: freeing free
sf_buf\000sfpbs"}},
M_databuf = "dummy\000
®0Àmaxsockbuf\000\000`®0Àmaxsockets\000\000
Re: KAME integration and plans
Sheldon Hearn wrote: On Tue, 11 Jul 2000 14:56:35 +0100, Ben Smithurst wrote: 'pseudo-device stf' gives an error, stf lives in the gif driver, so this is required really. Is that ok? Is there anyone at KAME I should send this to as well? I'm interested to see how the KAME folks react to our chucking out the pseudo-device keyword from config(8). :-) Ah, good point... I did my test on -stable where pseudo-device still exists. I'll wait for a while for this one then. There's another PR open on this problem, which asmodai is looking at (18852). -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D PGP signature
Re: HEADS UP: Inode numbers in daily security output.
On Tue, Jul 11, 2000 at 15:28:45 +0100, David Malone wrote: I've just changed the daily security secipt to include the inode numbers of suid files. This means the first time you run the updated script you will see lots of files have "changed" - this is just the inclusion of the inode numbers in the listing. I think this is a very good idea. I'd like to MFC this to 4.X in a few days, but I'm not sure if I should wait 'till after 4.1 is released. Opinions? Give us at least two days with it, but I think it is too tight to 4.1 release date to get MFC'ed. Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
syscons hangs with -current
I am getting freezes on -current as of my last two updates, Jul. 9 and today, Jul. 10. My previous update was around Jun 14. I can boot the kernel from the last update just fine, though ppp doesn't work due to net changes. (I'm stuck using the mac with a modem as a natting router. ugh.) Bootblocks are from the Jul 9 update. The system is a BP6 with non-overclocked Celeron 366s, 256MB ram, voodoo3 pci. I've tried both GENERIC and my configured kernel, I've tried swapping video cards to an s3, and changed every other card in the system one time or another while examining this. I played with the video irq in the bios, the pnp bios options, and the hints. The hints are from GENERIC with the addition of my soundblaster pcm entries. I tried unsetting various hints related to sc from the loader, but there was never any change (a boot without any extra hints at all gives the same error, too). I compiled up a kernel with pcvt rather than sc, but that just panicked at the atkbd area, as reported by someone else in the mail archives. I can't find anything in the archives or UPDATING about this situation. All kernels were compiled with default optimization. (copying by hand, junk left out) pci0: 3dfx Voodoo 3 graphics accelerator at 15.0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xv on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 fdc0: ... fdc0: ... fd0: ... isa0: @@@ found isa0: @@@ found isa0: @@@ found atkbdc0: Keyboard controller (i8042) at port 0x60, 0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga1: Generic ISA VGA at port 0x3v0-0x3bb iomem 0xb-0xb7fff on isa0 sc1: System console at flags 0x100 on isa0 _ At this point, the cursor shows but the kb doesn't respond. A few bits of the hints, as reported by "show" from the loader console=vidconsole hint.atkbd.at=atkbdc hint.atkbd.0.flags=0x1 hint.atkbd.0.irq=1 hint.atkbdc.0.at=isa hint.atkbdc.0.port=0x060 hint.sc.0.at=isa hint.sc.0.flags=0x100 hint.vga.0.at=isa hint.vt.0.at=isa Any help would be greatly appreciated. -- -- Eric Anholt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: KAME integration and plans
On Tue, 11 Jul 2000 14:56:35 +0100 Ben Smithurst [EMAIL PROTECTED] said: ben 'pseudo-device stf' gives an error, stf lives in the gif driver, so this ben is required really. Is that ok? Is there anyone at KAME I should send ben this to as well? No. Before merging latest KAME, that is true. In that days, stf was quick hack version of gif. But, stf is NOT gif but stf, now. My config contains: device stf # 6to4 IPv6 over IPv4 encapsulation -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Recent syscons weirdness (nervous /dev/sysmouse)
I'm using moused in conjunction with XFree86 4.0.1 and /dev/sysmouse. Recently, my mouse pointer has been extremely jumpy in XFree86. I think this is a syscons problem, as I have this problem with moused at the console as well. Also, cursor movement is very jumpy. -- - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NETGRAPH changes
Hello All, Does anybody knows when -current NETGRAPH changes will be back ported to 4.X branch (if they ever will)? Thanks, emax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bug: kernel hangs at boot
On Fri, Jun 30, 2000 at 06:29:11AM -0700, Andrey A. Chernov wrote: On Wed, Jun 28, 2000 at 11:03:22PM -0700, Andrey A. Chernov wrote: Fresh -current kernel with fresh -current bootblocks loaded ok but hangs in boot (no diagnostics even printed, just silent hang with "/" on the screen). Kernel from Jun14 with fresh -current bootblocks (i.e. the same bootblocks) booted Ok. The reason found. I have "-O2 pipe" instead of default "-O pipe", but I have it working all the time from very beginning. Why this becomes broken? I've been having the same problem for weeks on my Sony Vaio Z505RX, and recently reproduced it on my K6 300. Changing -O2 to -O doesn't help. The spinner freezes (sometimes on "/", but not always), but the system still seems to boot without displaying anything on the console. The disk spins as if fsck is running, but the system is essentially unusable. It's almost as if the console is not being detected. This problem began after Peter Wemm's config changes. Both my own kernel configuration nor GENERIC behave similarly. New boot blocks did not help for either of my systems. -- Andrew J. Korty, Principal Security Engineer Office of the Vice President for Information Technology Indiana University To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syscons hangs with -current
On Mon, 10 Jul 2000 11:14:16 MST, Eric Anholt wrote: I am getting freezes on -current as of my last two updates, Jul. 9 and today, Jul. 10. My previous update was around Jun 14. I can boot the kernel from the last update just fine, though ppp doesn't work due to net changes. Just as a datapoint, I'm getting reboots and hard locks shortly after reboot (no more than 20 minutes) using a kernel built from sources from around 22H30 last night. A kernel from around the same time on Friday last week does not exhibit the problem. sc1: System console at flags 0x100 on isa0 Note, though, that my box _does_ make it _well_ past the kernel probe stage and doesn't show the peculiar sc1 device at probe time. Any idea what that is, by the way? You haven't perhaps got ``device sc 2'' or something crazy in your kernel config file? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0 pod2man ports
In article [EMAIL PROTECTED], Alexander Leidinger [EMAIL PROTECTED] wrote: On 10 Jul, Will Andrews wrote: Only if ports-base isn't anymore in ports-all or my local CVS tree is ports-base was/has never [been] in ports-all, for some strange reason. Really? [...] I read this as: If you didn't use "ports-all", you have to use "ports-base". If you use "ports-all", "ports-base" is already included. You are correct. The ports-all collection includes ports-base, and that has always been the case. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: KAME integration and plans
Hajimu UMEMOTO wrote: On Tue, 11 Jul 2000 14:56:35 +0100 Ben Smithurst [EMAIL PROTECTED] said: ben 'pseudo-device stf' gives an error, stf lives in the gif driver, so this ben is required really. Is that ok? Is there anyone at KAME I should send ben this to as well? No. Before merging latest KAME, that is true. In that days, stf was quick hack version of gif. But, stf is NOT gif but stf, now. My config contains: device stf # 6to4 IPv6 over IPv4 encapsulation Ok. I guess all that needs doing is s/pseudo-device/device/ in the SYNOPSIS then. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D PGP signature
Recent -current Performance Drop?
I don't know if this belongs in -current or -smp, so here goes. I am running -current SMP, cvsup, etc. late last night PDT. # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Tue Jul 11 09:53:15 PDT 2000 \ tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 I have been using 'make world' as a stability/performance indicator. The stability has been good. I have had no recent panics, etc., during 'make world'. I choose the times to update carefully. Good work core team. I seem to see somewhat of a performance drop in the past week. I save the output of 'make world' I know this is not a benchmark nor a very accurate indicator. However, I believe 'make world' is a pretty good torque tool for a lightly loaded, interactive, 'play' system. And, disk I/O, compiling and executing user code is what interactive users do. If 'make world' puts out approximately the same number of lines, I think it is doing about the same amount of work. I see an increase in 'make world' time over the past week, or so. The number of lines of output has gone up slightly. The time elapsed has gone up more. # world_time.sh Make World Statistics -current SMP, 2xP133, 96MB RAM, IBM Superstor 9G disk. Lines is the number of lines of output produced by 'make world'. Date Lines Make Time Lines/Minute - - 19991018 35281 6h40m16s 88.20 2401 39490 7h56m18s 82.96 2402 39427 7h28m41s 88.01 2412 39404 7h10m21s 91.64 2621 38679 7h20m20s 87.91 2630 39530 7h56m20s 83.05 2709 39679 8h40m28s 76.31 2710 39568 9h13m46s 71.55 2711 41178 9h22m05s 73.27 tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent -current Performance Drop?
phk turned on some extra malloc options by default that a) catch more bugs b) make it slower. I hope you are reading cvs-all when you are using -current. On Tue, 11 Jul 2000, Thomas D. Dean wrote: I don't know if this belongs in -current or -smp, so here goes. I am running -current SMP, cvsup, etc. late last night PDT. # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Tue Jul 11 09:53:15 PDT 2000 \ tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 I have been using 'make world' as a stability/performance indicator. The stability has been good. I have had no recent panics, etc., during 'make world'. I choose the times to update carefully. Good work core team. I seem to see somewhat of a performance drop in the past week. I save the output of 'make world' I know this is not a benchmark nor a very accurate indicator. However, I believe 'make world' is a pretty good torque tool for a lightly loaded, interactive, 'play' system. And, disk I/O, compiling and executing user code is what interactive users do. If 'make world' puts out approximately the same number of lines, I think it is doing about the same amount of work. I see an increase in 'make world' time over the past week, or so. The number of lines of output has gone up slightly. The time elapsed has gone up more. # world_time.sh Make World Statistics -current SMP, 2xP133, 96MB RAM, IBM Superstor 9G disk. Lines is the number of lines of output produced by 'make world'. Date Lines Make Time Lines/Minute - - 19991018 35281 6h40m16s 88.20 2401 39490 7h56m18s 82.96 2402 39427 7h28m41s 88.01 2412 39404 7h10m21s 91.64 2621 38679 7h20m20s 87.91 2630 39530 7h56m20s 83.05 2709 39679 8h40m28s 76.31 2710 39568 9h13m46s 71.55 2711 41178 9h22m05s 73.27 tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-smp" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent -current Performance Drop?
I seem to see somewhat of a performance drop in the past week. You should have read the commit messages :-) I enabled malloc flags AJ by default, this has a performance cost. It will be turned off for releases of course. It has already exposed on bug (see peters commit). You can disable it if you want to run benchmarks: ln -sf aj /etc/malloc.conf -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SCSI DAT tape question
I'm running an adaptec controller (1542CF) with a Sony SDT-5000. I'm running: reeBSD (5.0-2511-CURRENT FreeBSD 5.0-2511-CURRENT #4: Thu Jul 6 20:31:41 CDT 2000) When I issue the command "camcontrol eject sa0" I receive: Error received from stop unit command When I issue the command "camcontrol stop sa0" I receive" Error received from stop unit command I can boot the system into Windows or System Commander and eject the tape using the eject button. Any ideas? Robert To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SCSI DAT tape question
If memory serves me right, "Robert Small" wrote: I'm running an adaptec controller (1542CF) with a Sony SDT-5000. I'm running: reeBSD (5.0-2511-CURRENT FreeBSD 5.0-2511-CURRENT #4: Thu Jul 6 20:31:41 CDT 2000) When I issue the command "camcontrol eject sa0" I receive: Error received from stop unit command When I issue the command "camcontrol stop sa0" I receive" Error received from stop unit command I can boot the system into Windows or System Commander and eject the tape using the eject button. Any ideas? Is there some reason why "mt -f /dev/nsa0 offline" won't do what you want? Bruce. PGP signature
Re: NETGRAPH changes
Yevmenkin, Maksim N, CSCIO writes: Does anybody knows when -current NETGRAPH changes will be back ported to 4.X branch (if they ever will)? Which changes in particular are you asking about? -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: NETGRAPH changes
Which changes in particular are you asking about? the attach/detach ``ng_ether'' nodes thanks, emax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SCSI DAT tape question
On Tue, Jul 11, 2000 at 14:50:08 -0500, Robert Small wrote: I'm running an adaptec controller (1542CF) with a Sony SDT-5000. I'm running: reeBSD (5.0-2511-CURRENT FreeBSD 5.0-2511-CURRENT #4: Thu Jul 6 20:31:41 CDT 2000) When I issue the command "camcontrol eject sa0" I receive: Error received from stop unit command When I issue the command "camcontrol stop sa0" I receive" Error received from stop unit command I can boot the system into Windows or System Commander and eject the tape using the eject button. Any ideas? Well, why not use 'mt rewoffl'? That's the normal way to eject a tape. If you want to know why camcontrol can't eject the tape, use the -v switch to enable verbose error messages. i.e.: camcontrol eject sa0 -v Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NETGRAPH changes
Yevmenkin, Maksim N, CSCIO writes: Which changes in particular are you asking about? the attach/detach ``ng_ether'' nodes I was planning on MFC'ing that soon. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent -current Performance Drop?
Actually in the past week or two I have seen a make buildworld drop from 205-210 minutes to 180-190 minutes. But I would be more inclined to attribute that to changes in the source tree itself, not performance. On Tue, 11 Jul 2000, Thomas D. Dean wrote: I don't know if this belongs in -current or -smp, so here goes. I am running -current SMP, cvsup, etc. late last night PDT. # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Tue Jul 11 09:53:15 PDT 2000 \ tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 I have been using 'make world' as a stability/performance indicator. The stability has been good. I have had no recent panics, etc., during 'make world'. I choose the times to update carefully. Good work core team. I seem to see somewhat of a performance drop in the past week. I save the output of 'make world' I know this is not a benchmark nor a very accurate indicator. However, I believe 'make world' is a pretty good torque tool for a lightly loaded, interactive, 'play' system. And, disk I/O, compiling and executing user code is what interactive users do. If 'make world' puts out approximately the same number of lines, I think it is doing about the same amount of work. I see an increase in 'make world' time over the past week, or so. The number of lines of output has gone up slightly. The time elapsed has gone up more. # world_time.sh Make World Statistics -current SMP, 2xP133, 96MB RAM, IBM Superstor 9G disk. Lines is the number of lines of output produced by 'make world'. Date Lines Make Time Lines/Minute - - 19991018 35281 6h40m16s 88.20 2401 39490 7h56m18s 82.96 2402 39427 7h28m41s 88.01 2412 39404 7h10m21s 91.64 2621 38679 7h20m20s 87.91 2630 39530 7h56m20s 83.05 2709 39679 8h40m28s 76.31 2710 39568 9h13m46s 71.55 2711 41178 9h22m05s 73.27 tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Didn't mean to slight anyone - good work all who worked on it.
The subject says it all. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SCSI DAT tape question
I like to use: tar cvpf /dev/ersa0 . >> /var/log/bu.log so that it ejects the tape automatically after the archive is complete. -- Cheers, Mikel +~+ | Optimized Computer Solutions, Inc http://www.ocsny.com | 39 W14th Street, Suite 203 212 727 2238 x132 | New York, NY 10011 +~+ Robert Small wrote: I'm running an adaptec controller (1542CF) with a Sony SDT-5000. I'm running: reeBSD (5.0-2511-CURRENT FreeBSD 5.0-2511-CURRENT #4: Thu Jul 6 20:31:41 CDT 2000) When I issue the command "camcontrol eject sa0" I receive: Error received from stop unit command When I issue the command "camcontrol stop sa0" I receive" Error received from stop unit command I can boot the system into Windows or System Commander and eject the tape using the eject button. Any ideas? Robert To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message begin:vcard n:King;Mikel tel;fax:2124638402 tel;home:http://www.upan.org tel;work:2127272100 x-mozilla-html:TRUE org:Optimized Computer Solutions version:2.1 email;internet:[EMAIL PROTECTED] title:Director of Network Operations Technology adr;quoted-printable:;;39 W14th St.=0D=0ASte 203;New York;NY;10011;US note;quoted-printable:fBSD, PHP, MySql and OCS Rule!!!=0D=0A=0D=0AGoal is to be MS free by the end of 2k. x-mozilla-cpt:;7312 fn:Mikel King end:vcard
Re: syscons hangs with -current
On Tue, Jul 11, 2000 at 07:00:52PM +0200, Sheldon Hearn wrote: On Mon, 10 Jul 2000 11:14:16 MST, Eric Anholt wrote: I am getting freezes on -current as of my last two updates, Jul. 9 and today, Jul. 10. My previous update was around Jun 14. I can boot the kernel from the last update just fine, though ppp doesn't work due to net changes. Just as a datapoint, I'm getting reboots and hard locks shortly after reboot (no more than 20 minutes) using a kernel built from sources from around 22H30 last night. I had the same problem beginning yesterday. My sources were updated at 1500 UTC Jul 10. System would run for between 15 and 25 minutes before a panic (something about supervisor mode, sorry I didn't do any tracking, I assumed I'd missed the SMP commits HEADS UP).. Retrieved sources as of 1700UTC Jul 11 built cleanly and have been running fine. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: KAME integration and plans
On Tue, 11 Jul 2000, Ben Smithurst wrote: I'd like to commit this: --- stf.4 2000/07/04 16:39:23 1.4 +++ stf.4 2000/07/11 13:44:47 @@ -36,7 +36,7 @@ .Nd .Tn 6to4 tunnel interface .Sh SYNOPSIS -.Cd "pseudo-device stf" +.Cd "pseudo-device gif" .Sh DESCRIPTION The .Nm 'pseudo-device stf' gives an error, stf lives in the gif driver, so this is required really. Is that ok? Is there anyone at KAME I should send this to as well? Um, "device stf" certainly does work. 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: fetch is strange
Dag-Erling Smorgrav [EMAIL PROTECTED] wrote: It seems that fetch(1) can not fetch any file. In this case, the downloaded(?) file size is zero. DES Make sure you have revision 1.2 (or newer) of src/usr.bin/fetch/fetch.c: I cvsupped 20 minutes ago and remade libfetch and fetch. It works good. Thanks! -- NAKAJI Hiroyuki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ssh not working after upgrading OS?
Hi! All, I upgraded my OS to FreeBSD 5.0-CURRENT #20, everything seems fine except ssh. Every time if I try to ssh to another host, the system gives me an error message says, "ssh: no RSA support in libssl and libcrypto. See ssl(8). Disabling protocol version 1 DH_generate_key" What is wrong and how to fix it? Any help will be gratefull! Thanks! Sam To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
malloc() bug in ld
Since setting my malloc.conf flags to AJ I'm getting spontaneous sig10's in ld(1) - in fact I can't link anything with those flags set. Can anyone else confirm? 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: malloc() bug in ld
On Tue, 11 Jul 2000, Kris Kennaway wrote: Since setting my malloc.conf flags to AJ I'm getting spontaneous sig10's in ld(1) - in fact I can't link anything with those flags set. Can anyone else confirm? Hmm, well it went away after a binutils recompile. So maybe I just still had the old version or something. *shrug* 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: malloc() bug in ld
On Tue, 11 Jul 2000, Kris Kennaway wrote: Hmm, well it went away after a binutils recompile. So maybe I just still had the old version or something. *shrug* Yes, I did: ld -V GNU ld version 2.10-anoncvs-2512 (with BFD 2.10-anoncvs-2512) Supported emulations: elf_i386 ld -V GNU ld version 2.10.0 (with BFD 2.10.0) Supported emulations: elf_i386 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: KAME integration and plans
Kris Kennaway wrote: On Tue, 11 Jul 2000, Ben Smithurst wrote: 'pseudo-device stf' gives an error, stf lives in the gif driver, so this is required really. Is that ok? Is there anyone at KAME I should send this to as well? Um, "device stf" certainly does work. Ah. I'm using -STABLE here... AFAICT you still need 'pseudo-device gif' there. -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D PGP signature
Re: ssh not working after upgrading OS?
Sam Xie wrote: Hi! All, I upgraded my OS to FreeBSD 5.0-CURRENT #20, everything seems fine except ssh. Every time if I try to ssh to another host, the system gives me an error message says, "ssh: no RSA support in libssl and libcrypto. See ssl(8). Disabling protocol version 1 DH_generate_key" What is wrong and how to fix it? Any help will be gratefull! You are probably using a -CURRENT with a broken randomness device. For more information you can try and search the mailing list archives. Try updating to a more recent -CURRENT, that should help. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _ \_ _(_) (_)/_\_| \ _|/' \/ (_)(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Burned by config changes?
I've somehow been burned by the config changes when I build world yesterday. The build went fine, and then I followed the instructions on: http://people.freebsd.org/~imp/config-upd.html But when I rebooted, it freezes right when I type "boot". Typing "boot -v" does not reveal anything more. I've gone in with an old kernel which lets me boot, and tried building a new GENERIC one, with no luck. It freezes at the same place. I have in place my /boot/device.hints, and it looks right. Any pointers to get the system back up and running? (I do have a backup, but I'd rather learn how to fix this!) Patrick Gardella To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Burned by config changes?
In article [EMAIL PROTECTED], Patrick Gardella [EMAIL PROTECTED] wrote: I've somehow been burned by the config changes when I build world yesterday. The build went fine, and then I followed the instructions on: http://people.freebsd.org/~imp/config-upd.html But when I rebooted, it freezes right when I type "boot". Typing "boot -v" does not reveal anything more. One thing that can get you is if you have customized "/boot/loader.rc" in the past. The make install for the bootloader won't replace this file if one is already present. I had a very old one I had hacked up, and it didn't do the same things as the standard version. I saw the same symptoms you're describing. I deleted my old loader.rc, reinstalled the bootloader, and then everything worked. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
