From owner-freebsd-current Sun Mar 5 1:59:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.fsbdial.co.uk (s25.athenenet.co.uk [195.89.137.31]) by hub.freebsd.org (Postfix) with ESMTP id 074CA37B9A9; Sun, 5 Mar 2000 01:59:47 -0800 (PST) (envelope-from parish@ukgateway.net) Received: from [195.89.137.91] by mail.freenet.co.uk (NTMail 5.03.0001/NT0619.00.fa900c19) with ESMTP id beffpaaa for questions@freebsd.org; Sat, 4 Mar 2000 21:48:43 +0000 Message-ID: <38C1857A.59FD9BD@ukgateway.net> Date: Sat, 04 Mar 2000 21:51:54 +0000 From: Mark Ovens X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: questions@freebsd.org Cc: current@freebsd.org Subject: Modem no longer found after u/g to 4.0-current - help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just done a relatively painless upgrade from 3.4-STABLE to 4.0, kudos to all he developers. However, one thing that doesn't work is causing me great problems. My ISA PnP modem is found as "unknown0", instead of sio2 no matter what I do: unknown0: at port 0x3e8-0x3ef irq 5 on isa0 The full dmseg output is at the end of this post. I've tried changing the PnP-OS seting in the BIOS, but it's no different. I thought I'd found the solution in LINT: # PnP `flags' (set via userconfig using pnp x flags y) # 0x1 disable probing of this device. Used to # prevent your modem from being attached # as a PnP modem. # which appears to be what is needed but ``boot -c'' and ``pnp 1 flags 0x1'' at the ``config>'' prompt gives: Invalid command or syntax. type '?' for help. Does anyone know the solution to this? This modem has worked flawlessly on this PC from 2.2.8 to 3.4-STABLE and it would be a shame to have to replace it now. TIA BTW, please Cc: me diractly as I'm not subscribed to any lists under this temporary Internet account, thanks. dmesg output: 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 #3: Sat Mar 4 19:45:35 GMT 2000 root@parish:/usr/src/sys/compile/PARISH Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 233864767 Hz CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping = 2 Features=0x8001bf AMD Features=0x400<> real memory = 67108864 (65536K bytes) avail memory = 61726720 (60280K bytes) Preloaded elf kernel "kernel" at 0xc0311000. Preloaded elf module "vesa.ko" at 0xc031109c. Preloaded userconfig_script "/kernel.config" at 0xc0311138. VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc030e102 (1000022) VESA: ATI MACH64 md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 7.1 pci0: at 7.2 irq 11 chip1: port 0x5f00-0x5f0f at device 7.3 on pci0 pci0: at 8.0 sym0: <875> port 0x6600-0x66ff mem 0xe1002000-0xe1002fff,0xe1001000-0xe10010ff irq 10 at device 9.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: SCAN AT BOOT disabled for targets 1 2 3 4 5 9 10 11 12 13 14 15. xl0: <3Com 3c900-COMBO Etherlink XL> port 0x6700-0x673f irq 9 at device 10.0 on pci0 xl0: Ethernet address: 00:60:08:73:4e:e0 xl0: selecting 10baseT transceiver, half duplex pcm0: port 0x6800-0x683f irq 11 at device 11.0 on pci0 fdc0: 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: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: configured irq 5 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: MLC,PCL,PML plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 unknown0: at port 0x3e8-0x3ef irq 5 on isa0 Waiting 10 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/da0s3a cd0 at sym0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da1 at sym0 bus 0 target 8 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) -- Q. How many Software Engineers does it take to change a light bulb? A. None. It's a hardware problem FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 3:22:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from afs.itc.keio.ac.jp (afs.itc.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with SMTP id 9DCDD37B9C8 for ; Sun, 5 Mar 2000 03:22:53 -0800 (PST) (envelope-from hosokawa@itc.keio.ac.jp) Received: (qmail 21300 invoked from network); 5 Mar 2000 11:22:50 -0000 Received: from ppp135.dialup.st.keio.ac.jp (HELO ringo.FromTo.Cc) (131.113.27.135) by afs.itc.keio.ac.jp with SMTP; 5 Mar 2000 11:22:50 -0000 Date: Sun, 05 Mar 2000 20:23:28 +0900 Message-ID: <86g0u5mzin.wl@ringo.FromTo.Cc> From: Tatsumi Hosokawa To: atrens@nortelnetworks.com Cc: current@freebsd.org Subject: Re: VMWare 2.0R broken - linux ioctl(13, 1260, *) not implemented In-Reply-To: In your message of "Sun, 5 Mar 2000 01:32:39 -0500 (EST)" References: User-Agent: Wanderlust/2.2.13 (Keep The Faith) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Sun, 5 Mar 2000 01:32:39 -0500 (EST), Andrew Atrens wrote: > > A missing (not implemented) linux ioctl is breaking VMWare 2.0 - > > > linux: 'ioctl' fd=13, cmd=1260 ('^R',96) not implemented > > > After rummaging around in the 2.3 kernel, I found the following in > `linux/include/linux/fs.h': Hmm? I'm using Win98 (Japanese), Win2K (Japanese), and FreeBSD-current on vmware 2.0 with linux emulator of yesterday's -current without any problems. Am I wrong? --------------------------- Tatsumi Hosokawa hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 3:26:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id BEDD737B9BE for ; Sun, 5 Mar 2000 03:26:15 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id LAA22006; Sun, 5 Mar 2000 11:26:55 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id LAA01876; Sun, 5 Mar 2000 11:21:11 GMT (envelope-from n_hibma@calcaphon.com) Date: Sun, 5 Mar 2000 11:21:11 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: USB BSD list Cc: Guido van Rooij , FreeBSD CURRENT Mailing List Subject: Unplugging the floppy (Re: Support for USB floppy drives) In-Reply-To: <20000303235109.A88642@gvr.gvr.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had a look at the problem described by Guido and it is reprodicuble here. Somehow a transfer is not descheduled when it should and this make uhci_done bomb because of a stale pointer. So, do not unplug the drive without a drive until this has been fixed. Nick On Fri, 3 Mar 2000, Guido van Rooij wrote: > On Thu, Mar 02, 2000 at 08:32:00PM +0000, Nick Hibma wrote: > > > > camcontrol rescan 0 > > dd if=/dev/zero of=/dev/da0 bs=10k count=100 > > disklabel -r -w da0 fd1440 > > newfs /dev/da0 > > > > Keep me posted on the results or any problems you have. > > > > Bij deze: > > plug in floppy drive op een vaio. > camcontrol rescan 0 > unplug de floppy drive > wacht 2-3 seconden > panic...en wel zodanig erg dat hij geen dump meer kan maken > > -Guido > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 5: 1:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by hub.freebsd.org (Postfix) with ESMTP id 824D937B9C3; Sun, 5 Mar 2000 05:01:47 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 12RafJ-000ANm-0W; Sun, 5 Mar 2000 13:01:46 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id NAA37816; Sun, 5 Mar 2000 13:07:08 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 5 Mar 2000 13:04:23 +0000 (GMT) From: Doug Rabson To: Mark Ovens Cc: questions@freebsd.org, current@freebsd.org Subject: Re: Modem no longer found after u/g to 4.0-current - help In-Reply-To: <38C1857A.59FD9BD@ukgateway.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 4 Mar 2000, Mark Ovens wrote: > I've just done a relatively painless upgrade from 3.4-STABLE to 4.0, > kudos to all he developers. However, one thing that doesn't work is > causing me great problems. My ISA PnP modem is found as "unknown0", > instead of sio2 no matter what I do: > > unknown0: at port > 0x3e8-0x3ef irq 5 on isa0 > > The full dmseg output is at the end of this post. > > I've tried changing the PnP-OS seting in the BIOS, but it's no > different. > > I thought I'd found the solution in LINT: > > # PnP `flags' (set via userconfig using pnp x flags y) > # 0x1 disable probing of this device. Used to > # prevent your modem from being attached > # as a PnP modem. > # > > which appears to be what is needed but ``boot -c'' and ``pnp 1 flags > 0x1'' at the ``config>'' prompt gives: > > Invalid command or syntax. type '?' for help. > > Does anyone know the solution to this? This modem has worked > flawlessly on this PC from 2.2.8 to 3.4-STABLE and it would be a shame > to have to replace it now. Could you send me the output of pnpinfo. I think we are missing a PnP ID in the sio driver. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 5:23: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [170.1.70.2]) by hub.freebsd.org (Postfix) with ESMTP id 0008137B9A9; Sun, 5 Mar 2000 05:23:02 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (icarus.kfu.com [170.1.70.17]) by quack.kfu.com (8.9.2/8.9.3) with ESMTP id FAA58584; Sun, 5 Mar 2000 05:22:52 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.9.3//ident-1.0) id FAA01257; Sun, 5 Mar 2000 05:22:51 -0800 (PST) Message-ID: <38C25FAB.1680D620@quack.kfu.com> Date: Sun, 05 Mar 2000 13:22:51 +0000 From: Nick Sayer Reply-To: freebsd-emulation@freebsd.org X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Atrens , freebsd-emulation@freebsd.org, freebsd-current@freebsd.org Subject: Re: VMWare 2.0R broken - linux ioctl(13, 1260, *) not implemented References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Atrens wrote: > > A missing (not implemented) linux ioctl is breaking VMWare 2.0 - > > > linux: 'ioctl' fd=13, cmd=1260 ('^R',96) not implemented I implemented this ioctl. It's not as hard as you think. You do a DIOCGDINFO and return d_secperunit. But unfortunately, when I did this, a warning went away from the vmware log file, but vmware _still_ segfaulted immediately after, so I think there's more to it. Fortunately, this only affects raw disks. Virtual ones still work. I would attach my implementation for the missing ioctl below, but I can't find it. I send a copy to Marcel, but I I lost mine in my latest cvsup. :-( In the meantime, you can still fetch build 438 (I think), which is one of the 2.0 betas. It doesn't have this problem. Take a look at the freebsd-emulation mailing list archive. > > After rummaging around in the 2.3 kernel, I found the following in > `linux/include/linux/fs.h': > > /* the read-only stuff doesn't really belong here, but any other place is > probably as bad and I don't want to create yet another include file. */ > > #define BLKROSET _IO(0x12,93) /* set device read-only (0 = read-write) */ > #define BLKROGET _IO(0x12,94) /* get read-only status (0 = read_write) */ > #define BLKRRPART _IO(0x12,95) /* re-read partition table */ > #define BLKGETSIZE _IO(0x12,96) /* return device size */ > #define BLKFLSBUF _IO(0x12,97) /* flush buffer cache */ > #define BLKRASET _IO(0x12,98) /* Set read ahead for block device */ > #define BLKRAGET _IO(0x12,99) /* get current read ahead setting */ > #define BLKFRASET _IO(0x12,100)/* set filesystem (mm/filemap.c) read-ahead */ > #define BLKFRAGET _IO(0x12,101)/* get filesystem (mm/filemap.c) read-ahead */ > #define BLKSECTSET _IO(0x12,102)/* set max sectors per request (ll_rw_blk.c) */ > #define BLKSECTGET _IO(0x12,103)/* get max sectors per request (ll_rw_blk.c) */ > #define BLKSSZGET _IO(0x12,104)/* get block device sector size */ > > So it looks like BLKGETSIZE is the missing ioctl. > > I'm not sure how to fix this, because well, we don't have block devices, > the ATA driver doesn't support ioctls _or_ have a useful psize attribute > in its cdevsw struct. > > I naively thought I could use fstat() then devsw() to map the file > descriptor to a device, and then interrogate the device's psize. But that > goofy attempt just resulted in a kernel panic. :) Please don't dis me on > how stupid that was - instead tell me what I should do :) > > Seriously though, any help y'all could provide would be greatly > appreciated. :) > > Andrew. > > -- > > +-- > | Andrew Atrens Nortel Networks, Ottawa, Canada. | > | All opinions expressed are my own, not those of any employer. | > --+ > Berkeley had what we called "copycenter", which is "take it down > to the copy center and make as many copies as you want". > -- Kirk McKusick > +-- --+ > Bill Gates is a white Persian cat and a monocle away from becoming > another James Bond villain. "No Mr Bond, I expect you to upgrade." > -- Dennis Miller > +-- --+ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 5:35:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [170.1.70.2]) by hub.freebsd.org (Postfix) with ESMTP id 0DAB137B9AF; Sun, 5 Mar 2000 05:35:29 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (icarus.kfu.com [170.1.70.17]) by quack.kfu.com (8.9.2/8.9.3) with ESMTP id FAA58634; Sun, 5 Mar 2000 05:35:28 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.9.3//ident-1.0) id FAA01298; Sun, 5 Mar 2000 05:35:27 -0800 (PST) Message-ID: <38C2629F.FD2290E0@quack.kfu.com> Date: Sun, 05 Mar 2000 13:35:27 +0000 From: Nick Sayer Reply-To: freebsd-emulation@freebsd.org X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Atrens , freebsd-emulation@freebsd.org, freebsd-current@freebsd.org Subject: Re: VMWare 2.0R broken - linux ioctl(13, 1260, *) not implemented References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ah! I found it! --- linux_ioctl.h.orig Mon Feb 28 11:50:23 2000 +++ linux_ioctl.h Mon Feb 28 11:24:08 2000 @@ -32,6 +32,25 @@ #define _LINUX_IOCTL_H_ /* + * disk + */ +#define LINUX_BLKROSET 0x125d +#define LINUX_BLKROGET 0x125e +#define LINUX_BLKRRPART 0x125f +#define LINUX_BLKGETSIZE 0x1260 +#define LINUX_BLKFLSBUF 0x1261 +#define LINUX_BLKRASET 0x1262 +#define LINUX_BLKRAGET 0x1263 +#define LINUX_BLKFRASET 0x1264 +#define LINUX_BLKFRAGET 0x1265 +#define LINUX_BLKSECTSET 0x1266 +#define LINUX_BLKSECTGET 0x1267 +#define LINUX_BLKSSZGET 0x1268 + +#define LINUX_IOCTL_DISK_MIN LINUX_BLKROSET +#define LINUX_IOCTL_DISK_MAX LINUX_BLKSSZGET + +/* * cdrom */ #define LINUX_CDROMPAUSE 0x5301 --- linux_ioctl.c.orig Mon Feb 28 11:50:07 2000 +++ linux_ioctl.c Mon Feb 28 11:11:09 2000 @@ -46,6 +46,7 @@ #include #include #include +#include #include @@ -55,12 +56,15 @@ #include #include +static linux_ioctl_function_t linux_ioctl_disk; static linux_ioctl_function_t linux_ioctl_cdrom; static linux_ioctl_function_t linux_ioctl_console; static linux_ioctl_function_t linux_ioctl_socket; static linux_ioctl_function_t linux_ioctl_sound; static linux_ioctl_function_t linux_ioctl_termio; +static struct linux_ioctl_handler disk_handler = +{ linux_ioctl_disk, LINUX_IOCTL_DISK_MIN, LINUX_IOCTL_DISK_MAX }; static struct linux_ioctl_handler cdrom_handler = { linux_ioctl_cdrom, LINUX_IOCTL_CDROM_MIN, LINUX_IOCTL_CDROM_MAX }; static struct linux_ioctl_handler console_handler = @@ -72,6 +76,7 @@ static struct linux_ioctl_handler termio_handler = { linux_ioctl_termio, LINUX_IOCTL_TERMIO_MIN, LINUX_IOCTL_TERMIO_MAX }; +DATA_SET(linux_ioctl_handler_set, disk_handler); DATA_SET(linux_ioctl_handler_set, cdrom_handler); DATA_SET(linux_ioctl_handler_set, console_handler); DATA_SET(linux_ioctl_handler_set, socket_handler); @@ -87,6 +92,23 @@ static TAILQ_HEAD(, handler_element) handlers = TAILQ_HEAD_INITIALIZER(handlers); + +static int +linux_ioctl_disk(struct proc *p, struct linux_ioctl_args *args) +{ + struct file *fp = p->p_fd->fd_ofiles[args->fd]; + int error; + struct disklabel dl; + + switch (args->cmd & 0xffff) { + case LINUX_BLKGETSIZE: + error = fo_ioctl(fp, DIOCGDINFO, (caddr_t)&dl, p); + if (error) + return (error); + return copyout(&(dl.d_secperunit), (caddr_t)args->arg, sizeof(dl.d_secperunit)); + } + return (ENOIOCTL); +} /* * termio related ioctls To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 5:53:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from plan9.cs.bell-labs.com (plan9.bell-labs.com [204.178.31.2]) by hub.freebsd.org (Postfix) with SMTP id 6FA1737BA06 for ; Sun, 5 Mar 2000 05:53:50 -0800 (PST) (envelope-from ches@plan9.bell-labs.com) Subject: subscribe Date: Sun, 5 Mar 2000 08:53:43 -0500 From: ches@plan9.bell-labs.com To: freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Message-Id: <20000305135350.6FA1737BA06@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 6: 0:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id 733BD37BA14 for ; Sun, 5 Mar 2000 06:00:15 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 11819 invoked from network); 5 Mar 2000 14:00:13 -0000 Received: from useraj14.uk.uudial.com (HELO parish.my.domain) (62.188.133.143) by smtp.dial.pipex.com with SMTP; 5 Mar 2000 14:00:13 -0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id OAA00419; Sun, 5 Mar 2000 14:00:23 GMT (envelope-from mark) Date: Sun, 5 Mar 2000 14:00:23 +0000 From: Mark Ovens To: Doug Rabson Cc: questions@freebsd.org, current@freebsd.org Subject: Re: Modem no longer found after u/g to 4.0-current - help Message-ID: <20000305140022.B204@parish> Reply-To: mark@ukug.uk.freebsd.org References: <38C1857A.59FD9BD@ukgateway.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dfr@nlsystems.com on Sun, Mar 05, 2000 at 01:04:23PM +0000 Organization: Total lack of Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 05, 2000 at 01:04:23PM +0000, Doug Rabson wrote: > On Sat, 4 Mar 2000, Mark Ovens wrote: > > > I've just done a relatively painless upgrade from 3.4-STABLE to 4.0, > > kudos to all he developers. However, one thing that doesn't work is > > causing me great problems. My ISA PnP modem is found as "unknown0", > > instead of sio2 no matter what I do: > > > > unknown0: at port > > 0x3e8-0x3ef irq 5 on isa0 > > > > The full dmseg output is at the end of this post. > > > > I've tried changing the PnP-OS seting in the BIOS, but it's no > > different. > > > > I thought I'd found the solution in LINT: > > > > # PnP `flags' (set via userconfig using pnp x flags y) > > # 0x1 disable probing of this device. Used to > > # prevent your modem from being attached > > # as a PnP modem. > > # > > > > which appears to be what is needed but ``boot -c'' and ``pnp 1 flags > > 0x1'' at the ``config>'' prompt gives: > > > > Invalid command or syntax. type '?' for help. > > > > Does anyone know the solution to this? This modem has worked > > flawlessly on this PC from 2.2.8 to 3.4-STABLE and it would be a shame > > to have to replace it now. > > Could you send me the output of pnpinfo. I think we are missing a PnP ID > in the sio driver. > The line I've added to sio.c is: {0x3024a341, NULL}, /* PMC2430 - Pace 56 Voice Internal Modem */ Output of pnpinfo: Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID PMC2430 (0x3024a341), Serial Number 0xffffffff PnP Version 1.0, Vendor Version 0 Device Description: Pace 56 Voice Internal Plug & Play Modem Logical Device ID: PMC2430 0x3024a341 #0 Device supports I/O Range Check TAG Start DF I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 4 - only one type (true/edge) TAG Start DF I/O Range 0x2f8 .. 0x2f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 - only one type (true/edge) TAG Start DF I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 4 - only one type (true/edge) TAG Start DF I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 - only one type (true/edge) TAG Start DF I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 5 7 9 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x2f8 .. 0x2f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 5 7 9 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 5 7 9 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 5 7 9 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x100 .. 0xfff8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 4 5 7 9 10 11 12 15 - only one type (true/edge) TAG End DF End Tag Successfully got 31 resources, 1 logical fdevs -- card select # 0x0001 CSN PMC2430 (0x3024a341), Serial Number 0xffffffff Logical device #0 IO: 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 IRQ 5 0 DMA 4 0 IO range check 0x00 activate 0x01 > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 6:47:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id CB37237BA20 for ; Sun, 5 Mar 2000 06:47:07 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 73D471CD7; Sun, 5 Mar 2000 22:47:03 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: 3.x/4.x branch date? In-Reply-To: Message from Warner Losh of "Sat, 04 Mar 2000 20:43:45 MST." <200003050343.UAA40026@harmony.village.org> Date: Sun, 05 Mar 2000 22:47:03 +0800 From: Peter Wemm Message-Id: <20000305144703.73D471CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message Kris Ke nnaway writes: > : Can someone tell me the exact date that 4.x was split from 3.x? I couldn't > : seem to pin it down based on the CVS repository. > > Based on sys/i386/conf/files.i386: > 1/20/99 to 2/10/99 > Based on sys/conf/files: > 1/17/99 to 1/21/99 > > So I'd say it was somewhere between 1/20/99 and 1/21/99. Is that > close enough for you to "exact"? The branching proccess takes a > while, so I think this is as close as you may get. sys/conf/newvers.sh is (or was) the best spot to look at: revision 1.42 date: 1999/01/21 03:07:33; author: jkh; state: Exp; lines: +2 -2 This is now 4.0-current revision 1.41.2.1 date: 1999/01/21 05:33:18; author: jkh; state: Exp; lines: +2 -2 Now we're -STABLE Note that this is GMT. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 7:26:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id A9C0237BA32 for ; Sun, 5 Mar 2000 07:26:14 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id PAA23512; Sun, 5 Mar 2000 15:26:57 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id PAA02179; Sun, 5 Mar 2000 15:07:20 GMT (envelope-from n_hibma@calcaphon.com) Date: Sun, 5 Mar 2000 15:07:20 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: USB BSD list Cc: Guido van Rooij , FreeBSD CURRENT Mailing List Subject: Re: [usb-bsd] Re: Unplugging the floppy (Support for USB floppy drives) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've had a look at the problem described by Guido and it is reprodicuble > here. Somehow a transfer is not descheduled when it should and this make > uhci_done bomb because of a stale pointer. > > So, do not unplug the drive without a drive until this has been fixed. ^^^^^ reboot. Sorry. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 7:41: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from snail.ite.mh.se (snail.nts.mh.se [193.10.250.30]) by hub.freebsd.org (Postfix) with ESMTP id 472D237B7EF for ; Sun, 5 Mar 2000 07:41:05 -0800 (PST) (envelope-from forda@ite.mh.se) Received: from oden (forda@oden [10.14.4.5]) by snail.ite.mh.se (8.9.1/8.9.1) with ESMTP id QAA26301 for ; Sun, 5 Mar 2000 16:40:12 +0100 (MET) Date: Sun, 5 Mar 2000 16:37:04 +0100 (MET) From: Daniel Forsgren X-Sender: forda@oden To: freebsd-current@freebsd.org Subject: WaveLAN on RC2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying to get a Lucent WaveLAN card to work on a Dell Latitude CPxH450GT laptop running 4.0-Current RC2 (20000214). As the generic kernel seem to include the wi driver from the start, I figured it would work if I just copied pccard.conf.sample to pccard.conf (removing all unnecessary entries), but it doesn't. When I boot the system I get: wi0: No irq?! pccardd[46]: driver allocation failed for Lucent Technologies (WaveLAN/IEEE): Device not configured pccardd[46]: pccardd started Then, if i remove and re-insert the card I get: wi0: No I/O space?! pccardd[46]: driver allocation .... I'm not sure wether this is a kernel config problem or a pccard.conf problem, I've tried to change IRQ:s etc in pccard.conf, but to no avail. Does anyone have an idea of what to try/change? Thanks in advance, /Daniel F. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 7:43:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from bugg.strangled.net (c705742-a.htfdw1.ct.home.com [24.2.137.94]) by hub.freebsd.org (Postfix) with ESMTP id DD48937B564 for ; Sun, 5 Mar 2000 07:43:11 -0800 (PST) (envelope-from bugg@bugg.strangled.net) Received: (from bugg@localhost) by bugg.strangled.net (8.9.3/8.9.3) id KAA17802; Sun, 5 Mar 2000 10:45:16 -0500 (EST) (envelope-from bugg) Date: Sun, 5 Mar 2000 10:45:15 -0500 From: Dan Papasian To: Arun Sharma Cc: freebsd-current@FreeBSD.ORG Subject: Re: current lockups Message-ID: <20000305104515.A17749@moe.c705742-a.htfdw1.ct.home.com> References: <20000304235010.B10778@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000304235010.B10778@sharmas.dhs.org>; from adsharma@sharmas.dhs.org on Sat, Mar 04, 2000 at 11:50:10PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1. Is your computer overclocked? 2. Is the computer totally frozen? (i.e. scroll lock doesn't turn the light on) 3. Does similar load crash the box as well? (try make -j2 world) 4. Does it freeze in the same spot? 5. Is the computer not responding to pings? If you've answered yes to a good amount of these questions, there is a good chance that your processor(s) are overheating. Try improving the airflow to the case (But using a household fan isn't recommended due to EMI) -Dan Papasian On Sat, Mar 04, 2000 at 11:50:10PM -0800, Arun Sharma wrote: > Compiling Mozilla with make -j 2 got -current to lock up, twice in > succession. I'm running a fairly recent snapshot (a week or two old) > on a Dual celeron box (BP6) with UDMA66 enabled. > > The kernel had DDB enabled. I was running X, but I didn't see any > signs of the kernel attempting to get into the debugger. > > Has this been fixed ? Is anyone interested in investigating ? > I'll post more info if I find anything. > > -Arun > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 8: 2:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id B371837B84C; Sun, 5 Mar 2000 08:02:22 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 12RdU5-0006jd-0A; Sun, 5 Mar 2000 16:02:21 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id QAA38584; Sun, 5 Mar 2000 16:07:46 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 5 Mar 2000 16:04:59 +0000 (GMT) From: Doug Rabson To: Mark Ovens Cc: questions@freebsd.org, current@freebsd.org Subject: Re: Modem no longer found after u/g to 4.0-current - help In-Reply-To: <20000305140022.B204@parish> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Mar 2000, Mark Ovens wrote: > On Sun, Mar 05, 2000 at 01:04:23PM +0000, Doug Rabson wrote: > > Could you send me the output of pnpinfo. I think we are missing a PnP ID > > in the sio driver. > > > > The line I've added to sio.c is: > > > {0x3024a341, NULL}, /* PMC2430 - Pace 56 Voice Internal Modem */ Does the modem work with this addition? If so, I'll commit the change. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 8:10:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from dervish.mail.pipex.net (dervish.mail.pipex.net [158.43.192.70]) by hub.freebsd.org (Postfix) with SMTP id DA99437BA5D for ; Sun, 5 Mar 2000 08:10:42 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 12586 invoked from network); 5 Mar 2000 16:10:37 -0000 Received: from userca65.uk.uudial.com (HELO parish.my.domain) (62.188.150.133) by smtp.dial.pipex.com with SMTP; 5 Mar 2000 16:10:37 -0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id QAA00330; Sun, 5 Mar 2000 16:10:47 GMT (envelope-from mark) Date: Sun, 5 Mar 2000 16:10:47 +0000 From: Mark Ovens To: Doug Rabson Cc: questions@freebsd.org, current@freebsd.org Subject: Re: Modem no longer found after u/g to 4.0-current - help Message-ID: <20000305161047.B211@parish> References: <20000305140022.B204@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dfr@nlsystems.com on Sun, Mar 05, 2000 at 04:04:59PM +0000 Organization: Total lack of Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 05, 2000 at 04:04:59PM +0000, Doug Rabson wrote: > On Sun, 5 Mar 2000, Mark Ovens wrote: > > > On Sun, Mar 05, 2000 at 01:04:23PM +0000, Doug Rabson wrote: > > > Could you send me the output of pnpinfo. I think we are missing a PnP ID > > > in the sio driver. > > > > > > > The line I've added to sio.c is: > > > > > > {0x3024a341, NULL}, /* PMC2430 - Pace 56 Voice Internal Modem */ > > Does the modem work with this addition? If so, I'll commit the change. > Yes :) sio2: at port 0x3e8-0x3ef irq 5 on isa0 sio2: type 16550A Why did it work before though, under 3.x, without this line in sio.c? > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 8:52: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from cgi.norcom2000.com (cgi.norcom2000.com [208.18.247.5]) by hub.freebsd.org (Postfix) with ESMTP id BBCD337BA73 for ; Sun, 5 Mar 2000 08:52:03 -0800 (PST) (envelope-from jon@cgi.norcom2000.com) Received: (from jon@localhost) by cgi.norcom2000.com (8.8.7/8.8.7) id KAA07257 for freebsd-current@freebsd.org; Sun, 5 Mar 2000 10:51:32 -0600 Message-ID: <20000305105127.A7254@cgi.norcom2000.com> Date: Sun, 5 Mar 2000 10:51:27 -0600 From: jon@cgi.norcom2000.com To: freebsd-current@freebsd.org Subject: ad0 Time Out Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've encountered a problem when booting my -current kernel. I'd include parts of the /var/log/messages, but it does not write to it when I boot up current. I installed the -current kernel, and made the devices for ad0 and ad1 including all the slices that I need, besides making all devices. I changed the /etc/fstab from wd to ad. I manually enter my root device when it's booting. Here's the problem I have: (I bet it's because of somethign stupid i did, or did not do...) It detects ad0 and ad1 allright, but then when it tries to mount root (ad0s3a) it gives me an error like the following: ad0: WRITE timed out. It then proceeds to crash. If anybody can help me I'd appreciate that, I know I don't have a whole lot of information, but I'll provide it if anybody needs specific things.. It's just a little harder to include it when it doesn't save it to the hard drive. Thanks, Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 8:54:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from monsoon.mail.pipex.net (monsoon.mail.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id 333B137BA73 for ; Sun, 5 Mar 2000 08:54:30 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 12126 invoked from network); 5 Mar 2000 16:54:23 -0000 Received: from userai65.uk.uudial.com (HELO parish.my.domain) (62.188.133.95) by smtp.dial.pipex.com with SMTP; 5 Mar 2000 16:54:23 -0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id QAA00576 for current@freebsd.org; Sun, 5 Mar 2000 16:54:05 GMT (envelope-from mark) Date: Sun, 5 Mar 2000 16:54:04 +0000 From: Mark Ovens To: current@freebsd.org Subject: Feedback: Minor problems u/g 3.4-STABLE -> 4.0 Message-ID: <20000305165404.C388@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: Total lack of Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Firstly, a big thank-you to all the developers for their work on 4.x. I've just u/g 3.4-STABLE -> 4.0, following the instructions in /usr/source/UPDATING using sources cvsup'd 10:00GMT 4th March, and although it went quite smoothly came across a few minor problems which I'm posting here in case anyone is interested. 1. This message appeared 166 times during ``make buildworld'': /usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found It also caused config(8) on the new kernel to fail, but ldconfig -R /usr/obj/usr/src/lib/libc cured that. 2. UPDATING includes the following in the instructions to build the new kernel: cd src/usr.bin/genassym make depend all install clean cd ../../usr.sbin/config make depend all install clean however doing a ``make clean'' at this point then causes ``make installworld'' fail in those directories. 3. This probably won't affect most people but I'm including it so it's in the mail archives. I have a Diamond Fireport 40 SCSI card (NCR/Symbios 53c875j chip) and my 2nd (UW SCSI) disk is a single slice (although *not* dangerously dedicated) mounted as /usr. As this disk is not a boot device I had not enabled boot probing for it in the SCSI BIOS but under 2.2.x and 3.x it was still found by the old ncr driver. The new sym driver, however, failed to find the disk and caused a "device not configured" error from mount(8) which resulted in the boot-up dropping to single-user. It took me a while to find the cause (I thought it was a problem, or my mistake, when making the new device nodes for the disks). -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 8:57:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id BB5B137B8AB; Sun, 5 Mar 2000 08:57:52 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 47A711CD7; Mon, 6 Mar 2000 00:57:50 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Mark Ovens Cc: Doug Rabson , questions@freebsd.org, current@freebsd.org Subject: Re: Modem no longer found after u/g to 4.0-current - help In-Reply-To: Message from Mark Ovens of "Sun, 05 Mar 2000 16:10:47 GMT." <20000305161047.B211@parish> Date: Mon, 06 Mar 2000 00:57:50 +0800 From: Peter Wemm Message-Id: <20000305165750.47A711CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Ovens wrote: > On Sun, Mar 05, 2000 at 04:04:59PM +0000, Doug Rabson wrote: > > On Sun, 5 Mar 2000, Mark Ovens wrote: > > > > > On Sun, Mar 05, 2000 at 01:04:23PM +0000, Doug Rabson wrote: > > > > Could you send me the output of pnpinfo. I think we are missing a PnP I D > > > > in the sio driver. > > > > > > > > > > The line I've added to sio.c is: > > > > > > > > > {0x3024a341, NULL}, /* PMC2430 - Pace 56 Voice Internal Modem */ > > > > Does the modem work with this addition? If so, I'll commit the change. > > > > Yes :) > > sio2: at port 0x3e8-0x3ef irq 5 on isa0 > sio2: type 16550A Heh, it's already committed. (oops! :-) > Why did it work before though, under 3.x, without this line in sio.c? The PNP bios preconfigured it and left it laying around in port space, so the old-style isa probes "found" it there. Under 4.0, the isa code is much more pnp centric. It was possible for an isa probe to find a "stray" device and then for the PNP device id to match and then fail due to resource conflicts. So, it disables the programmable cards first so this double probing cannot happen. It also means that it needs to know the PNP id's for supported pnp hardware. Making this more user tweakable is on the TODO list. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 9: 4:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from monsoon.mail.pipex.net (monsoon.mail.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id 5D1E537BA88 for ; Sun, 5 Mar 2000 09:04:08 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 12808 invoked from network); 5 Mar 2000 17:04:06 -0000 Received: from userai65.uk.uudial.com (HELO parish.my.domain) (62.188.133.95) by smtp.dial.pipex.com with SMTP; 5 Mar 2000 17:04:06 -0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id RAA00754; Sun, 5 Mar 2000 17:04:17 GMT (envelope-from mark) Date: Sun, 5 Mar 2000 17:04:17 +0000 From: Mark Ovens To: Peter Wemm Cc: Doug Rabson , questions@freebsd.org, current@freebsd.org Subject: Re: Modem no longer found after u/g to 4.0-current - help Message-ID: <20000305170417.G388@parish> References: <20000305165750.47A711CD7@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000305165750.47A711CD7@overcee.netplex.com.au>; from peter@netplex.com.au on Mon, Mar 06, 2000 at 12:57:50AM +0800 Organization: Total lack of Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 12:57:50AM +0800, Peter Wemm wrote: > Mark Ovens wrote: > > On Sun, Mar 05, 2000 at 04:04:59PM +0000, Doug Rabson wrote: > > > On Sun, 5 Mar 2000, Mark Ovens wrote: > > > > > > > On Sun, Mar 05, 2000 at 01:04:23PM +0000, Doug Rabson wrote: > > > > > Could you send me the output of pnpinfo. I think we are missing a PnP I > D > > > > > in the sio driver. > > > > > > > > > > > > > The line I've added to sio.c is: > > > > > > > > > > > > {0x3024a341, NULL}, /* PMC2430 - Pace 56 Voice Internal Modem */ > > > > > > Does the modem work with this addition? If so, I'll commit the change. > > > > > > > Yes :) > > > > sio2: at port 0x3e8-0x3ef irq 5 on > isa0 > > sio2: type 16550A > > Heh, it's already committed. (oops! :-) > > > Why did it work before though, under 3.x, without this line in sio.c? > > The PNP bios preconfigured it and left it laying around in port space, > so the old-style isa probes "found" it there. > > Under 4.0, the isa code is much more pnp centric. It was possible for an > isa probe to find a "stray" device and then for the PNP device id to match > and then fail due to resource conflicts. So, it disables the programmable > cards first so this double probing cannot happen. It also means that it > needs to know the PNP id's for supported pnp hardware. Making this more > user tweakable is on the TODO list. > Thanks for the explanation. > Cheers, > -Peter > -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 9:46:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (Postfix) with ESMTP id A90DA37BAAB for ; Sun, 5 Mar 2000 09:46:52 -0800 (PST) (envelope-from andreasd@ifi.uio.no) Received: from levding.ifi.uio.no (3034@levding.ifi.uio.no [129.240.64.43]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id SAA28325 for ; Sun, 5 Mar 2000 18:46:50 +0100 (MET) Received: (from andreasd@localhost) by levding.ifi.uio.no ; Sun, 5 Mar 2000 18:46:50 +0100 (MET) To: current@FreeBSD.org Subject: "fatal trap 12" with 4.0-CURRENT From: Andreas Dobloug Date: 05 Mar 2000 18:46:49 +0100 Message-ID: Lines: 22 X-Mailer: Gnus v5.4.37/XEmacs 19.15 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I keep getting 'trap 12' with 4.0-CURRENT when running rvplayer5. Has anyone else experienced this? I haven't got a remote terminal for debugging, but it looks like this bug is emanating from the fxp driver: fxp_start+0x110 movl %edx,0(%ecx, %eax ,1) System: % uname -a FreeBSD motsognir.unik.no 4.0-CURRENT FreeBSD 4.0-CURRENT #31: Thu Mar 2 15:34:17 CET 2000 root@motsognir.unik.no:/usr/src/sys/compile/ZEUS i386 % dmesg | grep fxp fxp0: port 0xb400-0xb41f mem 0xdf000000-0xdf0fffff,0xe2000000-0xe2000fff irq 17 at device 11.0 on pci0 XFree version 3.3.5 I can try to borrow remote terminal to get a trace if anyone's interested. -- Andreas Dobloug : email: andreasd@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 10:59:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id C7B1E37BAC8 for ; Sun, 5 Mar 2000 10:59:36 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.13 #1) id 12RgFc-000CY2-00 for freebsd-current@freebsd.org; Sun, 05 Mar 2000 10:59:36 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: libcrypto.a - deja vu? Message-Id: Date: Sun, 05 Mar 2000 10:59:36 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i know i have been here before, but i forget the magic. and i checked UPDATING and mail archive (the restoration thereof is much appreciated!) cc -fpic -DPIC -O -pipe -Wall -I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/libpam/include -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/modules/pam_deny/pam_deny.c -o pam_deny.So building standard pam_deny library ranlib libpam_deny.a building shared library pam_deny.so ===> libpam/modules/pam_kerberosIV make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libcrypto.a. Stop *** Error code 2 randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 11:27:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from funkthat.com (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213]) by hub.freebsd.org (Postfix) with ESMTP id 7E57E37BAB7; Sun, 5 Mar 2000 11:27:42 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by funkthat.com (8.9.3/8.8.7) id LAA53977; Sun, 5 Mar 2000 11:26:58 -0800 (PST) Message-ID: <20000305112658.59344@hydrogen.funkthat.com> Date: Sun, 5 Mar 2000 11:26:58 -0800 From: John-Mark Gurney To: Lauri Laupmaa Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: plist/glist query & proposal Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.4-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White forwarded this message to me.... I actually have done this but I have not cleaned the code up for committing to the tree... I have been running this code for over a half year now... if people want, I can comitte this as is, but I'm using old daily routines on my box, not the newer ones... bak=/var/backups echo "" echo "" echo "checking disks for defects:" for i in `camcontrol devlist | awk '/(da|sd)/ { if (match($0, "(da|sd)[[:digit:]]+") != 0) { diskname = substr($0, RSTART, RLENGTH); match(diskname, "[[:digit:]]+"); print substr(diskname, RSTART, RLENGTH) } }' | sort -u`; do if [ -f ${bak}/da${i}.glist ]; then mv ${bak}/da${i}.glist ${bak}/da${i}.glist.bak fi echo -n "da${i}: " camcontrol defects -u $i -f phys -G 2>&1 > ${bak}/da${i}.glist if [ -f ${bak}/da${i}.glist.bak ]; then if ! cmp -s ${bak}/da${i}.glist ${bak}/da${i}.glist.bak; then diff ${bak}/da${i}.glist.bak ${bak}/da${i}.glist fi fi done -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 13:40:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id B86FC37B87F for ; Sun, 5 Mar 2000 13:40:16 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id VAA26403; Sun, 5 Mar 2000 21:40:47 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id VAA04075; Sun, 5 Mar 2000 21:35:42 GMT (envelope-from n_hibma@calcaphon.com) Date: Sun, 5 Mar 2000 21:35:42 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Iwasa Kazmi , USB BSD list , FreeBSD CURRENT Mailing List Cc: rio500-users@lists.sourceforge.net, Dirk-Willem van Gulik Subject: Rio500 USB driver for FreeBSD In-Reply-To: <200003051852.DAA25899@mail.ca2.so-net.ne.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The USB patchset for FreeBSD now contains the driver for the Diamond Rio 500 MP3 Player as well. Any comments on the driver? Please contact to the author: Iwasa Kazmi The patchset is available from http://www.etla.net/~n_hibma/usb/usb.pl#URIODriver and is made against CURRENT as of 2000/03/05 02:00. Instructions are included in the file. Keep us posted! Nick On Mon, 6 Mar 2000, Iwasa Kazmi wrote: > Hello all, > > I put a new FreeBSD driver on my web page. > http://www02.u-page.so-net.ne.jp/ca2/kzmi/rio-tools/rio-fbsd-0306.tar.gz > > It includes Dirk's code for FreeBSD 4.0. > > Now this driver has 143 as its major number. > Nick Hibma, a member of FreeBSD USB project, says that he would like to > add this driver to the FreeBSD source repository. > It's very nice. I'm going to do something for it. > > > Iwasa Kazmi > kzmi@ca2.so-net.ne.jp > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 13:40:54 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id CEADE37BB16; Sun, 5 Mar 2000 13:40:50 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id CAE562E8158; Sun, 5 Mar 2000 13:40:50 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 5 Mar 2000 13:40:50 -0800 (PST) From: Kris Kennaway To: Randy Bush Cc: FreeBSD Current Subject: Re: libcrypto.a - deja vu? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Mar 2000, Randy Bush wrote: > > cc -fpic -DPIC -O -pipe -Wall -I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/libpam/include -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/modules/pam_deny/pam_deny.c -o pam_deny.So > building standard pam_deny library > ranlib libpam_deny.a > building shared library pam_deny.so > ===> libpam/modules/pam_kerberosIV > make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libcrypto.a. Stop > *** Error code 2 Are you building with NO_OPENSSL? I just ran into this exact problem myself overnight with my buildworld with NO_OPENSSL enabled. Try this patch: Index: Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/Makefile,v retrieving revision 1.7 diff -u -r1.7 Makefile --- Makefile 2000/02/28 21:00:50 1.7 +++ Makefile 2000/03/05 21:30:35 @@ -26,10 +26,10 @@ SUBDIR+= pam_cleartext_pass_ok SUBDIR+= pam_deny -.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberosIV .endif -.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberos5 .endif SUBDIR+= pam_permit ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 13:47:42 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 806CA37B853; Sun, 5 Mar 2000 13:47:39 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7C57D2E8158; Sun, 5 Mar 2000 13:47:39 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 5 Mar 2000 13:47:39 -0800 (PST) From: Kris Kennaway To: Randy Bush Cc: FreeBSD Current Subject: Re: libcrypto.a - deja vu? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, my buildworld -DNOCLEAN just failed again. Updated patch: Index: libpam/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/libpam/Makefile,v retrieving revision 1.11 diff -u -r1.11 Makefile --- libpam/Makefile 2000/02/28 21:00:48 1.11 +++ libpam/Makefile 2000/03/05 21:46:10 @@ -62,16 +62,16 @@ # Static PAM modules: STATIC_MODULES+= ${MODOBJDIR}/pam_cleartext_pass_ok/libpam_cleartext_pass_ok.a STATIC_MODULES+= ${MODOBJDIR}/pam_deny/libpam_deny.a -.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) && !defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_kerberosIV/libpam_kerberosIV.a .endif -.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) && !defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_kerberos5/libpam_kerberos5.a .endif STATIC_MODULES+= ${MODOBJDIR}/pam_permit/libpam_permit.a STATIC_MODULES+= ${MODOBJDIR}/pam_radius/libpam_radius.a STATIC_MODULES+= ${MODOBJDIR}/pam_skey/libpam_skey.a -.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NO_OPENSSL) +.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NOCRYPT) && !defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_ssh/libpam_ssh.a .endif STATIC_MODULES+= ${MODOBJDIR}/pam_tacplus/libpam_tacplus.a Index: modules/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/Makefile,v retrieving revision 1.7 diff -u -r1.7 Makefile --- modules/Makefile 2000/02/28 21:00:50 1.7 +++ modules/Makefile 2000/03/05 21:46:25 @@ -26,16 +26,16 @@ SUBDIR+= pam_cleartext_pass_ok SUBDIR+= pam_deny -.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberosIV .endif -.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberos5 .endif SUBDIR+= pam_permit SUBDIR+= pam_radius SUBDIR+= pam_skey -.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NO_OPENSSL) +.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_ssh .endif SUBDIR+= pam_tacplus ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 13:49:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 7590F37BB8C; Sun, 5 Mar 2000 13:49:27 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id QAA87475; Sun, 5 Mar 2000 16:49:16 -0500 (EST) Date: Sun, 5 Mar 2000 16:49:16 -0500 (EST) From: "Matthew N. Dodd" To: John-Mark Gurney Cc: Lauri Laupmaa , scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: plist/glist query & proposal In-Reply-To: <20000305112658.59344@hydrogen.funkthat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Mar 2000, John-Mark Gurney wrote: > Doug White forwarded this message to me.... I actually have done this > but I have not cleaned the code up for committing to the tree... > > I have been running this code for over a half year now... > > if people want, I can comitte this as is, but I'm using old daily > routines on my box, not the newer ones... I like it, though you may want to have an /etc/glist.conf and let the user add stuff with a script that tests to make sure a drive supports the format. A script to test and populate this file wouldn't be difficult. # # /etc/glist.conf # # Drive name Format (block, bfi, phys) da0 phys da1 block ... > bak=/var/backups > echo "" > echo "" > echo "checking disks for defects:" > for i in `camcontrol devlist | awk '/(da|sd)/ { if (match($0, "(da|sd)[[:digit:]]+") != 0) { diskname = substr($0, RSTART, RLENGTH); match(diskname, "[[:digit:]]+"); print substr(diskname, RSTART, RLENGTH) } }' | sort -u`; do > if [ -f ${bak}/da${i}.glist ]; then > mv ${bak}/da${i}.glist ${bak}/da${i}.glist.bak > fi > echo -n "da${i}: " > camcontrol defects -u $i -f phys -G 2>&1 > ${bak}/da${i}.glist > if [ -f ${bak}/da${i}.glist.bak ]; then > if ! cmp -s ${bak}/da${i}.glist ${bak}/da${i}.glist.bak; then > diff ${bak}/da${i}.glist.bak ${bak}/da${i}.glist > fi > fi > done > > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 13:53:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id D9B6A37BBDB; Sun, 5 Mar 2000 13:53:42 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.13 #1) id 12Riy6-0004iC-00; Sun, 05 Mar 2000 13:53:42 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Kris Kennaway Cc: FreeBSD Current Subject: Re: libcrypto.a - deja vu? References: Message-Id: Date: Sun, 05 Mar 2000 13:53:42 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> cc -fpic -DPIC -O -pipe -Wall -I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/libpam/include -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/modules/pam_deny/pam_deny.c -o pam_deny.So >> building standard pam_deny library >> ranlib libpam_deny.a >> building shared library pam_deny.so >> ===> libpam/modules/pam_kerberosIV >> make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libcrypto.a. Stop >> *** Error code 2 > Are you building with NO_OPENSSL? I just ran into this exact problem > myself overnight with my buildworld with NO_OPENSSL enabled. that's the cause. > Try this patch: thanks. will do. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 13:59:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id B79B837BB26 for ; Sun, 5 Mar 2000 13:59:32 -0800 (PST) (envelope-from dirkx@webweaving.org) Received: from kim.ispra.webweaving.org (va-151.skylink.it [194.185.55.151]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA24227; Sun, 5 Mar 2000 23:00:44 +0100 Received: from kim.ispra.webweaving.org (kim.ispra.webweaving.org [10.0.0.2]) by kim.ispra.webweaving.org (8.8.8/8.8.5) with ESMTP id VAA27139; Sun, 5 Mar 2000 21:58:22 GMT X-Passed: MX on Ispra.WebWeaving.org Sun, 5 Mar 2000 21:58:22 GMT and masked X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Sun, 5 Mar 2000 21:58:22 GMT Date: Sun, 5 Mar 2000 22:58:21 +0100 (CET) From: Dirk-Willem van Gulik X-Sender: dirkx@kim.ispra.webweaving.org To: USB BSD list Cc: FreeBSD CURRENT Mailing List Subject: Re: [usb-bsd] Rio500 USB driver for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-125556415-952293501=:27133" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-125556415-952293501=:27133 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT On Sun, 5 Mar 2000, Nick Hibma wrote: > > The USB patchset for FreeBSD now contains the driver for the > > Diamond Rio 500 MP3 Player > > as well. Any comments on the driver? Please contact to the author: Iwasa > Kazmi > > The patchset is available from > > http://www.etla.net/~n_hibma/usb/usb.pl#URIODriver > > and is made against CURRENT as of 2000/03/05 02:00. Instructions are > included in the file. Thanks Nick. Meanwhile in addition to the ./configure command on that page, until the rio500-linux boys have commited a small patch, the above ports.tgz should more or less build the much needed userland tools; which requires just a <-> patch. > Keep us posted! Dw. > On Mon, 6 Mar 2000, Iwasa Kazmi wrote: > > > Hello all, > > > > I put a new FreeBSD driver on my web page. > > http://www02.u-page.so-net.ne.jp/ca2/kzmi/rio-tools/rio-fbsd-0306.tar.gz > > > > It includes Dirk's code for FreeBSD 4.0. > > > > Now this driver has 143 as its major number. > > Nick Hibma, a member of FreeBSD USB project, says that he would like to > > add this driver to the FreeBSD source repository. > > It's very nice. I'm going to do something for it. > > > > > > Iwasa Kazmi > > kzmi@ca2.so-net.ne.jp > > > > -- > n_hibma@webweaving.org > n_hibma@freebsd.org USB project > http://www.etla.net/~n_hibma/ > > > ------------------------------------------------------------------------ > Get paid for the computing stuff you know! > Get answers for the stuff you don’t. And get $10 to spend on the site! > http://click.egroups.com/1/2197/4/_/85983/_/952292433/ > > -- Create a poll/survey for your group! > -- http://www.egroups.com/vote?listname=usb-bsd&m=1 > > > --0-125556415-952293501=:27133 Content-Type: APPLICATION/octet-stream; name="rio500.tgz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="rio500.tgz" H4sIAF/CwjgAA+1ZbXPaSBL2V+lXdBRqncSHkBCCHFm8JiATKga7AGevKklR QhqBykLj00scx+G/38wggYTZ2N4KbO3ePGVb8sz0y/TT3SNE4GJdUUoHuwRU lJquwwFQKBvX5B+oKVVFJwsr5F5Vyop6APpOvUoQh5EZABwEGEc/WnczQ8jb h0P7RbDk33E9FO4qCx7Nf0VXq6pG+Fc1ReP87wM5/uf2TkKuKkq1UvkB/9Va Uv9aTavqlP9atXIAyi6c2cT/Of+9tg4vlkkgk0DI028voQGvHUWvOq+VsqqZ pmKaNU1zJspE/XfNUjXL0sW/2m2On4Sk/q/NyJrt6gR4/Pmv1aq0F6hqtVLl /X8f2OCfXYum+VNtPND/VeLA6vlPL1P+Na2s8/6/D9iu40Ax7gcgy6XVj+2G 0fKRIMmP5OL6lhfbqOS5Ewf78gzke0NisVj8U7qEUYzgFE0AXoOi19XXdV2F sqIo4tHR0RZDwjD2oUe506Gs1tVaXaks15+cQLFc/lcNjshfVYWTExFEeJ4o gF/DyHaxPDveGCOK6eDRc9exkQPj8WmA0NthezymY6uFt7RKAnO+XIu8EG3q 9qNkzifRzZmWLOw77lSeSWT4aaEPA4vejsneo7HrO1i2SFC2jD6agC2ywmng Mg5I1BStrlfqmp7lYJvIPRq0aoYGldGgpjRkAxW4/vQ+C/tkJi8b3V6jcNM4 GScNIsoPS2kOSn/7B6G0/19Nd/cO4Omf/5RatczP/30gw3/rvNcz+qOfb+PB z3/lanr+q4pOP/+VlUqZn//7wJJ/uAxR4Jm+DRHGXvi372ocj0Wm/tvGsDXY hY0H65/WfFr/Ffb+T6/VeP3vA0n9x/n6L26DyNvCPw+Z+r846w53cPo/ov7X 3/+oSrnC63+PSPjvmVeIfkbciY0H+NdVTV3xry75r2ka538feA4XOIhCsLDn IStysQ/zJBfAwUGdErTMEfE5fEBBSFcE6L+xGyCbzQKZaJsRAitA5JIMJhO/ z/B8PbCeIFOFrl0gN2KbdJ1+s2c0hMROqzkyOueDrjFsCGZsu1jsNbv9Efk1 Bg3BjmcnNp6bri9beC5S4/FMlmXwENnGjelG1G+IZmhODjOYoojeQ/KCkyx3 fZggsoTsz/3q+lMy7YYydCO4cT0PbnBwxTT4+Ebsn49b74zW++FlryHcojCz hdaH4bhNPG0IklbSS/SNh8QGh90R9bx+TY7ULyiomz72b+c4Dk+sL6GcfNUS 4jiwqBdTJPsoqpfIHM3A5N2MKHb6l+PWef+027kcGMy2eDk0xp1e873RWLpA xzpn3bfJut/ocOHu7LzVPHvbHBqL0sT1S1PPnajl4vK9k7jSODb6H8j61ulZ szNsSMVuib7psNGXUhxOJMiobUiFu8y/CymjpDkgwkKxeONGsyIRdi1E4jxr HFJNh5CbQH4U3DYOY7JB5VCkJP/WEATmo2VGoiiv3rlMQlu+JkkpXwdInl8d iyysrV6bCJAwQfGbJg6NNhOPw4CpCJG9YmT8rCEU7ozWu/MFFH0g/qczCwm+ kxAR4QUchqWP8Cmqfy6NS9NDcThq9i5Ou2cGlaUp2e4OFqXC3cX7Dk3ORUkm fWJ+LYo2LjqI5FJdFE5cBz7CMygiqjRVsIDP8P07fBIFStJHkP6Tc+BZg44U XpDB5miRE3wpwec3NFt9Kp3sYdwbdhYg9TEwB4BV5guSnziOADtgk5p7Kb1h Eswf5s2WHchrN8aL5Lu+nD3BsjOSS43EiVFzsICvzjd4QBVbDiwHqQ66o+Fa yx/QcZwLQLIafXWj5a3jLq+xH5I6pnKD4Tt2HRqDD8aA3Z6dd7p9GnLi6+Ay 1bKMBbN3cT4YkQRaSi/yQSbGaK6luhv3l+c9Kdz13tPwbI8x/PILW5WLZGY+ 0UXYSzsFbUfLiLC+QVbYOBuzhP7jY2hGEZpfR6xjYSoPpKFZVzQNnADPobBW s5ATrwXLDBEJQWZKohbZ3KpDvXq5HBBW0WyQ3pJoEN4kN1tW+XhzEQpNK7ll BNBUv1sJEOM0+4nyDRI2N/vqFVx4iPo+I/2ctA4UwAwFKG3tpJ2HIenU9mqj ArJmOIkkaRUk1excRMDDU9d/szL343XwK7Bm6Meel8ikCfCgISvhTyi24VM2 2z9JK+vpmbdYx+qRGjP61hWX15gJ65M4eCAqNNHuh2Udl2yRZ73cWuICfej6 Zjn5MlltIu0p2X0lNK96w9ryEzPt6ZtMLdnYR2kbyBdnC8ee7R9G+brMdExI E5qcgrR+AxQFLvqCpO36TAh98zqcYfpUEs1IItGnMmAnTxhYJDwT0/NIRrHP 7ESlOaVPRIk2GiRQ2b3jsiMLfY0C04rooZXpYL8P2B0bbF2QgATb21aWmozY 1jMbhxE7tP/qB1sODg4ODg4ODg4ODg4ODg4ODg4ODg4ODg4ODg4ODg4ODg4O Dg4Ojn8w/gcLsdvNAFAAAA== --0-125556415-952293501=:27133-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 13:59:51 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 7E78F37BB6F; Sun, 5 Mar 2000 13:59:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7C0C02E815B; Sun, 5 Mar 2000 13:59:49 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 5 Mar 2000 13:59:49 -0800 (PST) From: Kris Kennaway To: Jeff Palmer Cc: freebsd-current@freebsd.org Subject: Re: Buildworld failures In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 4 Mar 2000, Jeff Palmer wrote: > I have cvsupped and tried to build world mutiple times over the past 3 > days, each time I get the same error. I have been following the mailing > lists and don't see any other complaints.. So I'm sure the trouble is > with my machine... Are you building with NO_OPENSSL? Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 14: 3:41 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 6DA7237BB4B; Sun, 5 Mar 2000 14:03:39 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 513F92E815B; Sun, 5 Mar 2000 14:03:39 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 5 Mar 2000 14:03:39 -0800 (PST) From: Kris Kennaway To: Brian Dean Cc: bwoods2@uswest.net, freebsd-current@FreeBSD.ORG Subject: Re: Make world error..... In-Reply-To: <200003041520.KAA11567@dean.pc.sas.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 4 Mar 2000, Brian Dean wrote: > William Woods wrote: > > vm/vnode_pager.h -> vm/vnode_pager.ph > > *** Error code 1 > > > > Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. > > *** Error code 1 > > I got the same thing here. h2ph does not like /usr/include/des.h > which is a symlink to /usr/include/openssl/des.h, complaining about > "no such file or directory". I fixed mine by hacking h2ph in What is the difference between des.h and the 19 other symlinks we have in /usr/include? i.e. why does it just hate this one? The original poster also seemed to not be having this problem, at least from the fragment of the log above: it's dying nowhere near perlifying des.h. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 14:15:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from funkthat.com (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213]) by hub.freebsd.org (Postfix) with ESMTP id CBE7637BB2D; Sun, 5 Mar 2000 14:15:41 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by funkthat.com (8.9.3/8.8.7) id OAA56560; Sun, 5 Mar 2000 14:15:20 -0800 (PST) Message-ID: <20000305141520.52809@hydrogen.funkthat.com> Date: Sun, 5 Mar 2000 14:15:20 -0800 From: John-Mark Gurney To: "Matthew N. Dodd" Cc: Lauri Laupmaa , scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: plist/glist query & proposal References: <20000305112658.59344@hydrogen.funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Matthew N. Dodd on Sun, Mar 05, 2000 at 04:49:16PM -0500 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.4-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG make sure to keep me on the cc list, I'm not on -current or -scsi Matthew N. Dodd scribbled this message on Mar 5: > On Sun, 5 Mar 2000, John-Mark Gurney wrote: > > Doug White forwarded this message to me.... I actually have done this > > but I have not cleaned the code up for committing to the tree... > > > > I have been running this code for over a half year now... > > > > if people want, I can comitte this as is, but I'm using old daily > > routines on my box, not the newer ones... > > I like it, though you may want to have an /etc/glist.conf and let the > user add stuff with a script that tests to make sure a drive supports the > format. A script to test and populate this file wouldn't be > difficult. yeh, I originally was using block for a while, and ONE of my drives didn't support it, then I switched to phys, and haven't had a problem.. and I have quite a range of drives: hydrogen,ttyq3,~,502$grep 'Direct Access' /var/run/dmesg.boot da3: Fixed Direct Access SCSI-CCS device da0: Fixed Direct Access SCSI-2 device da5: Fixed Direct Access SCSI-CCS device da6: Fixed Direct Access SCSI-CCS device da2: Fixed Direct Access SCSI-2 device da1: Fixed Direct Access SCSI-2 device da4: Fixed Direct Access SCSI-2 device which is a selection of scsi-1 (scsi-ccs), fast scsi, and ultra scsi drives... I'm sure that just using phys will keep all drives usable.. and if the user wants a different format, they can manually run camcontrol... bad disk blocks SHOULDN'T appear that often... :) > # > # /etc/glist.conf > # > # Drive name Format (block, bfi, phys) > da0 phys > da1 block > ... something like: `awk '$1 ~ /(da|sd)'"${i}"'/ { type = $2 } END { if (type == "" ) echo "phys"; else echo type; }'` should do perfectly fine... :) > > bak=/var/backups > > echo "" > > echo "" > > echo "checking disks for defects:" > > for i in `camcontrol devlist | awk '/(da|sd)/ { if (match($0, "(da|sd)[[:digit:]]+") != 0) { diskname = substr($0, RSTART, RLENGTH); match(diskname, "[[:digit:]]+"); print substr(diskname, RSTART, RLENGTH) } }' | sort -u`; do > > if [ -f ${bak}/da${i}.glist ]; then > > mv ${bak}/da${i}.glist ${bak}/da${i}.glist.bak > > fi > > echo -n "da${i}: " > > camcontrol defects -u $i -f phys -G 2>&1 > ${bak}/da${i}.glist > > if [ -f ${bak}/da${i}.glist.bak ]; then > > if ! cmp -s ${bak}/da${i}.glist ${bak}/da${i}.glist.bak; then > > diff ${bak}/da${i}.glist.bak ${bak}/da${i}.glist > > fi > > fi > > done -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 14:26:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id F300537B824; Sun, 5 Mar 2000 14:26:39 -0800 (PST) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id RAA11520; Sun, 5 Mar 2000 17:26:34 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AB13686; Sun, 5 Mar 2000 17:26:03 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.1) id RAA15870; Sun, 5 Mar 2000 17:26:03 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <200003052226.RAA15870@dean.pc.sas.com> Subject: Re: Make world error..... In-Reply-To: from Kris Kennaway at "Mar 5, 2000 02:03:39 pm" To: Kris Kennaway Date: Sun, 5 Mar 2000 17:26:03 -0500 (EST) Cc: bwoods2@uswest.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The perl script h2ph does not exit immediately on des.h, it sets it's $Exit value to 1, but continues processing. If the original poster would check further back in his log file, he'll see: [...] ===> gnu/usr.bin/perl/utils/h2ph install -c -o root -g wheel -m 555 h2ph /usr/bin install -c -o root -g wheel -m 444 h2ph.1.gz /usr/share/man/man1 cd /usr/include; miniperl /usr/obj/usr/src/gnu/usr.bin/perl/utils/h2ph/h2ph -d /usr/libdata/perl/5.00503/mach * */* Skipping directory `arpa' Skipping directory `cam' Can't open des.h: No such file or directory Skipping directory `dev' Skipping directory `g++' Skipping directory `isofs' Skipping directory `machine' Skipping directory `msdosfs' [...] vm/vm_prot.h -> vm/vm_prot.ph vm/vm_zone.h -> vm/vm_zone.ph vm/vnode_pager.h -> vm/vnode_pager.ph *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. *** Error code 1 Unfortunately, I don't remember if the thing des.h pointed to (openssl/des.h) existed at the time. After I modified h2ph to not complain about that file, I did another make world a little bit later, and it completed without incident. I suspected that I had merely sup'd at a bad time and just caught things in transition. -Brian Kris Kennaway wrote: > > William Woods wrote: > > > vm/vnode_pager.h -> vm/vnode_pager.ph > > > *** Error code 1 > > > > > > Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. > > > *** Error code 1 > > > > I got the same thing here. h2ph does not like /usr/include/des.h > > which is a symlink to /usr/include/openssl/des.h, complaining about > > "no such file or directory". I fixed mine by hacking h2ph in > > What is the difference between des.h and the 19 other symlinks we have in > /usr/include? i.e. why does it just hate this one? > > The original poster also seemed to not be having this problem, at least > from the fragment of the log above: it's dying nowhere near > perlifying des.h. > > Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 14:34:31 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id EA50837BB26; Sun, 5 Mar 2000 14:34:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E7EF02E815B; Sun, 5 Mar 2000 14:34:29 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 5 Mar 2000 14:34:29 -0800 (PST) From: Kris Kennaway To: Brian Dean Cc: bwoods2@uswest.net, markm@freebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: Make world error..... In-Reply-To: <200003052226.RAA15870@dean.pc.sas.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Mar 2000, Brian Dean wrote: > The perl script h2ph does not exit immediately on des.h, it sets it's > $Exit value to 1, but continues processing. If the original poster > would check further back in his log file, he'll see: Ah, okay. There might be an ordering problem with the des.h symlink being created before the openssl/des.h file which it points to. Any ideas, Mark? Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 14:41:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from area51.v-wave.com (area51.v-wave.com [24.108.26.39]) by hub.freebsd.org (Postfix) with SMTP id 19CC337BB6F for ; Sun, 5 Mar 2000 14:40:35 -0800 (PST) (envelope-from flatline@area51.v-wave.com) Received: (qmail 1567 invoked by uid 1001); 5 Mar 2000 22:41:18 -0000 Date: Sun, 5 Mar 2000 15:41:18 -0700 From: Chris Wasser To: current@FreeBSD.ORG Subject: AWE64 & PCM Message-ID: <20000305154118.A1550@area51.v-wave.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, hate to post something this insignificant to the mailing list, but I've search the entire src tree with no luck in resolving this myself (well, grepping for awe64,wavetable,game .. found the AWE64 define in /usr/src/sys/dev/sound/isa/sbc.c easily enough) .. I'm sure it's due to some braindeadness on my behalf, but I'd sure appriciate someone steering me in the right direction on this. I also searched for the matching/compatible ID strings, no luck. Hopefully I provided enough information here... FreeBSD area51.v-wave.com 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Sun Mar 5 12:02:16 MST 2000 root@area51.v-wave.com:/usr/src/sys/compile/AREA51 i386 (cvsupped today -- well, at time of this posting.) joy0 at port 0x201 on isa0 sbc0: 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: on sbc0 joy1: at port 0x208-0x20f on isa0 unknown0: at port 0x620-0x623 on isa0 Now I tried enabling PNPBIOS in the kernel config, but that just produced a screenful of crap [PNP OS is disabled in the BIOS], here are the relevant kernel config options (no, I didn't add anything else for sound but this): [I read somewhere that the PCM driver doesn't support MIDI yet, not sure if this is related] device pcm device joy0 at isa? port IO_GAME Adding the sbc driver into the config didn't help either, produced the same dmesg output as above. I didn't use anything from the Voxware drivers like I used to under 3.x, I also tried using the pnp directives for userconfig at boot time, but that only produced syntax errors [same config I used for 3.x]: in /boot/kernel.conf: pnp 1 0 os enable irq0 5 drq0 1 drq1 5 port0 0x220 port1 0x330 port2 0x388 pnp 1 1 os disable pnp 1 2 os enable port0 0x620 port1 0xa20 port2 0xe20 pnp 1 3 os disable devices in /dev: (sh MAKEDEV snd0) 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/mixer@ -> mixer0 0 crw-rw-rw- 1 root wheel 30, 0 Feb 24 02:05 /dev/mixer0 0 lrwxrwxrwx 1 root wheel 10 Feb 24 02:05 /dev/sequencer@ -> sequencer0 0 crw-rw-rw- 1 root wheel 30, 1 Feb 24 02:05 /dev/sequencer0 0 crw-rw-rw- 1 root wheel 30, 2 Feb 24 02:05 /dev/midi0 0 lrwxrwxrwx 1 root wheel 4 Feb 24 02:05 /dev/dsp@ -> dsp0 0 crw-rw-rw- 1 root wheel 30, 3 Mar 5 12:43 /dev/dsp0 0 lrwxrwxrwx 1 root wheel 5 Feb 24 02:05 /dev/dspW@ -> dspW0 0 crw-rw-rw- 1 root wheel 30, 5 Feb 24 02:05 /dev/dspW0 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/audio@ -> audio0 0 crw-rw-rw- 1 root wheel 30, 4 Feb 24 02:05 /dev/audio0 0 crw-rw-rw- 1 root wheel 30, 6 Feb 24 02:05 /dev/sndstat 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/music@ -> music0 0 crw-rw-rw- 1 root wheel 30, 8 Feb 24 02:05 /dev/music0 0 lrwxrwxrwx 1 root wheel 4 Feb 24 02:05 /dev/pss@ -> pss0 0 crw-rw-rw- 1 root wheel 30, 9 Feb 24 02:05 /dev/pss0 /dev/sndstat reports: FreeBSD Audio Driver (newpcm) Mar 5 2000 12:00:51 Installed devices: pcm0: at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex) And finally, a pnpinfo dump: Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CTL00c3 (0xc3008c0e), Serial Number 0x1fa45429 PnP Version 1.0, Vendor Version 16 Device Description: Creative SB AWE64 PnP *** Small Vendor Tag Detected Logical Device ID: CTL0045 0x45008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x10, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x394, alignment 0x4, len 0x4 [16-bit addr] TAG End DF Logical Device ID: CTL7002 0x02708c0e #1 Compatible Device ID: PNPb02f (2fb0d041) Device Description: Game TAG Start DF Good Configuration I/O Range 0x200 .. 0x200, alignment 0x1, len 0x8 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x200 .. 0x208, alignment 0x8, len 0x8 [16-bit addr] TAG End DF Logical Device ID: CTL0022 0x22008c0e #2 Device Description: WaveTable TAG Start DF Good Configuration I/O Range 0x620 .. 0x620, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x620 .. 0x680, alignment 0x20, len 0x4 [16-bit addr] TAG End DF *** Small Vendor Tag Detected End Tag Successfully got 69 resources, 3 logical fdevs -- card select # 0x0001 CSN CTL00c3 (0xc3008c0e), Serial Number 0x1fa45429 Logical device #0 IO: 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 IRQ 5 0 DMA 1 5 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #2 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 14:55:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.apro.co.jp (name.apro.co.jp [210.141.99.130]) by hub.freebsd.org (Postfix) with ESMTP id 77F3F37BB75; Sun, 5 Mar 2000 14:55:19 -0800 (PST) (envelope-from manami@po.apro.co.jp) Received: from nh (host1.manga509-unet.ocn.ne.jp [210.226.103.154]) by ns.apro.co.jp (8.8.8/3.6W) with SMTP id HAA06154; Mon, 6 Mar 2000 07:33:58 +0900 (JST) Message-ID: <031601bf86f2$a8427b00$1401a8c0@nh> From: "manami" To: Subject: =?iso-2022-jp?B?GyRCTS1MPiU/JWwlcyVINktIaxsoQlNNGyRCMUdBfBsoQg==?= Date: Mon, 6 Mar 2000 06:17:56 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://k.manami.tripod.com/ $B$r$4Mw2<$5$$!#4|4V8BDj!#(B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 16:10:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 28D4537B7D5 for ; Sun, 5 Mar 2000 16:10:31 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id BAA98138; Mon, 6 Mar 2000 01:10:30 +0100 (CET) (envelope-from olli) Date: Mon, 6 Mar 2000 01:10:30 +0100 (CET) Message-Id: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: ssh strangeness in -current... X-Newsgroups: list.freebsd-current User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have upgraded a machine to the latest -current snapshot (it was running a -current from the end of January before). Every- thing went fine, except for one thing: ssh didn't work anymore. It used to work fine before. At first I was very suprised and had no clue what was going on. I couldn't imagine how the new -current base system could affect my ssh binary which had been installed from the ports long before. I even pkg_deleted it and re-installed it from the ports (yeah, stupid me), to no avail. It complained about some RSA library missing. Finally I got the great idea to type "which ssh", showing me that there now was a (non-functional) ssh binary in /usr/bin. I removed it, and everything started working again, picking up the ports version from /usr/local/bin. 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. By the way, _why_ is ssh in the base system now, and what is wrong with having it in the ports? I'm sorry if there was a "HEADS UP" on this list, then I must have missed it. Regards Oliver PS: Just in case if it matters, I have USA_RESIDENT=NO in my make.conf. -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 16:22:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 570E437BBB3 for ; Sun, 5 Mar 2000 16:22:44 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id BAA00966; Mon, 6 Mar 2000 01:22:41 +0100 (CET) (envelope-from olli) Date: Mon, 6 Mar 2000 01:22:41 +0100 (CET) Message-Id: <200003060022.BAA00966@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: kern/16487: please apply newpcm fix X-Newsgroups: list.freebsd-current User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Would someone please (pretty please) have a look at kern/16487 and commit the trivial fix in it? It's just one line, and it makes AvanceLogic-100 soundcards work again. On a related note (unfortunately I don't have a fix for this): The ALS-100 cards have a volume problem with newpcm. They're much too soft. Even if I push the mixer settings all the way to 100%, I have to turn the volume on the amplifier very high, which results in a lot of static and noise. I can literally hear every disk access and window movement through the speakers. It's horrible. :-( That did not happen with Luigi's "oldpcm": I could keep the amplifier at a moderate level, and the mixer was at about 60% to get decent audio playback -- no static, no noise. Same machine, same soundcard. Is this a known problem? I didn't find anything in the PR DB, so I should probably submit a PR about this. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 16:58:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id F3C9037BB66 for ; Sun, 5 Mar 2000 16:58:38 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id TAA89401; Sun, 5 Mar 2000 19:57:53 -0500 (EST) Date: Sun, 5 Mar 2000 19:57:52 -0500 (EST) From: "Matthew N. Dodd" To: Oliver Fromme Cc: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, Oliver Fromme wrote: > By the way, _why_ is ssh in the base system now, and what is wrong > with having it in the ports? I'm sorry if there was a "HEADS UP" on > this list, then I must have missed it. I keep asking myself this question; a default sysinstall package would give us the same end result. I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with breakage. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 16:59:14 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id C345D37BB66; Sun, 5 Mar 2000 16:59:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id BEA5E2E815B; Sun, 5 Mar 2000 16:59:07 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 5 Mar 2000 16:59:07 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Cc: markm@freebsd.org, jkh@freebsd.org Subject: NO_OPENSSL world fixes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, these patches were sufficient to allow me to build world with NO_OPENSSL defined. I'd like to commit these ASAP. After the release, I want to look at condensing the mass of .if defined(...) options we have, at least with respect to crypto. At the moment we have to test everywhere for things like .if !defined(NOCRYPT) && !defined(NOSECURE) && !defined(NO_OPENSSL) && defined(MAKE_KERBEROS4) when all we really want to know is whether or not OpenSSL is available to be linked with. In addition to normalizing all of the NO* options to NO_* (or other way round if I get shouted down :), they should obey the correct covering hierarchy automatically so we don't have to explicitly test for all the covering options in each instance. For example, NO_CRYPT should imply NO_OPENSSL, which in turn implies NO_OPENSSH, etc. NOSECURE should be removed since it's nonfunctional. NO_CRYPT or NO_OPENSSL should conflict with MAKE_KERBEROS?, etc. Kris Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.140 diff -u -r1.140 Makefile.inc1 --- Makefile.inc1 2000/02/28 21:04:38 1.140 +++ Makefile.inc1 2000/03/05 22:32:04 @@ -57,11 +57,11 @@ SUBDIR+= gnu .endif .if exists(${.CURDIR}/kerberosIV) && exists(${.CURDIR}/crypto) && \ - !defined(NOCRYPT) && defined(MAKE_KERBEROS4) + !defined(NOCRYPT) && !defined(NO_OPENSSL) && defined(MAKE_KERBEROS4) SUBDIR+= kerberosIV .endif .if exists(${.CURDIR}/kerberos5) && exists(${.CURDIR}/crypto) && \ - !defined(NOCRYPT) && defined(MAKE_KERBEROS5) + !defined(NOCRYPT) && !defined(NO_OPENSSL) && defined(MAKE_KERBEROS5) SUBDIR+= kerberos5 .endif .if exists(${.CURDIR}/libexec) @@ -203,7 +203,7 @@ # success, regardless of how old your existing system is. # buildworld: -.if !defined(NOSECURE) && exists(${.CURDIR}/secure) && \ +.if !defined(NOSECURE) && !defined(NO_OPENSSL) && exists(${.CURDIR}/secure) && \ (!defined(USA_RESIDENT) || (${USA_RESIDENT} != NO && \ ${USA_RESIDENT} != YES)) @echo Index: lib/Makefile =================================================================== RCS file: /home/ncvs/src/lib/Makefile,v retrieving revision 1.106 diff -u -r1.106 Makefile --- lib/Makefile 2000/01/21 02:00:53 1.106 +++ lib/Makefile 2000/02/27 00:21:50 @@ -43,7 +43,7 @@ .endif _libcrypt= libcrypt -.if exists(${.CURDIR}/../secure) && !defined(NOSECURE) && !defined(NOCRYPT) +.if exists(${.CURDIR}/../secure) && !defined(NOSECURE) && !defined(NOCRYPT) && !defined(NO_DESCRYPT) # Build both libraries. They have different names, so no harm, # and this avoids having stale libscrypt.* _libcrypt+= ../secure/lib/libcrypt Index: lib/libpam/libpam/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/libpam/Makefile,v retrieving revision 1.11 diff -u -r1.11 Makefile --- lib/libpam/libpam/Makefile 2000/02/28 21:00:48 1.11 +++ lib/libpam/libpam/Makefile 2000/03/05 22:32:04 @@ -62,16 +62,16 @@ # Static PAM modules: STATIC_MODULES+= ${MODOBJDIR}/pam_cleartext_pass_ok/libpam_cleartext_pass_ok.a STATIC_MODULES+= ${MODOBJDIR}/pam_deny/libpam_deny.a -.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) && !defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_kerberosIV/libpam_kerberosIV.a .endif -.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) && !defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_kerberos5/libpam_kerberos5.a .endif STATIC_MODULES+= ${MODOBJDIR}/pam_permit/libpam_permit.a STATIC_MODULES+= ${MODOBJDIR}/pam_radius/libpam_radius.a STATIC_MODULES+= ${MODOBJDIR}/pam_skey/libpam_skey.a -.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NO_OPENSSL) +.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NOCRYPT) && !defined(NO_OPENSSL) STATIC_MODULES+= ${MODOBJDIR}/pam_ssh/libpam_ssh.a .endif STATIC_MODULES+= ${MODOBJDIR}/pam_tacplus/libpam_tacplus.a Index: lib/libpam/modules/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/Makefile,v retrieving revision 1.7 diff -u -r1.7 Makefile --- lib/libpam/modules/Makefile 2000/02/28 21:00:50 1.7 +++ lib/libpam/modules/Makefile 2000/03/05 22:32:04 @@ -26,16 +26,16 @@ SUBDIR+= pam_cleartext_pass_ok SUBDIR+= pam_deny -.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberosIV .endif -.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) +.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_kerberos5 .endif SUBDIR+= pam_permit SUBDIR+= pam_radius SUBDIR+= pam_skey -.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NO_OPENSSL) +.if exists(${.CURDIR}/../../../crypto/openssh) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_ssh .endif SUBDIR+= pam_tacplus Index: secure/usr.bin/Makefile =================================================================== RCS file: /home/ncvs/src/secure/usr.bin/Makefile,v retrieving revision 1.13 diff -u -r1.13 Makefile --- secure/usr.bin/Makefile 2000/02/24 18:59:33 1.13 +++ secure/usr.bin/Makefile 2000/03/05 22:36:02 @@ -1,14 +1,14 @@ # $FreeBSD: src/secure/usr.bin/Makefile,v 1.13 2000/02/24 18:59:33 markm Exp $ SUBDIR= bdes -.if !defined(NOCRYPT) && !defined(MAKE_KERBEROS4) && !defined(MAKE_KERBEROS5) +.if !defined(NOCRYPT) && !defined(NO_OPENSSL) && !defined(MAKE_KERBEROS4) && !defined(MAKE_KERBEROS5) SUBDIR+=telnet .endif .if !defined(NO_OPENSSL) SUBDIR+=openssl -.endif .if !defined(NO_OPENSSH) SUBDIR+=scp ssh ssh-add ssh-agent ssh-keygen +.endif .endif .include Index: usr.bin/passwd/Makefile =================================================================== RCS file: /home/ncvs/src/usr.bin/passwd/Makefile,v retrieving revision 1.39 diff -u -r1.39 Makefile --- usr.bin/passwd/Makefile 2000/02/24 21:06:16 1.39 +++ usr.bin/passwd/Makefile 2000/03/05 22:35:04 @@ -79,7 +79,7 @@ LINKS=${BINDIR}/passwd ${BINDIR}/yppasswd MLINKS=passwd.1 yppasswd.1 -.if exists(${DESTDIR}${LIBDIR}/libkrb.a) && (defined(MAKE_KERBEROS4)) +.if exists(${DESTDIR}${LIBDIR}/libkrb.a) && !defined(NOCRYPT) && !defined(NO_OPENSSL) && defined(MAKE_KERBEROS4) SRCS+= kpasswd_standalone.c .PATH: ${.CURDIR}/../../usr.bin/chpass ${.CURDIR}/../../usr.sbin/vipw \ ${.CURDIR}/../../usr.bin/rlogin ${.CURDIR}/../../usr.bin/passwd \ Index: usr.bin/rlogin/Makefile =================================================================== RCS file: /home/ncvs/src/usr.bin/rlogin/Makefile,v retrieving revision 1.20 diff -u -r1.20 Makefile --- usr.bin/rlogin/Makefile 2000/02/24 21:06:17 1.20 +++ usr.bin/rlogin/Makefile 2000/03/05 22:32:04 @@ -9,7 +9,7 @@ BINMODE=4555 INSTALLFLAGS=-fschg -.if exists(${DESTDIR}${LIBDIR}/libkrb.a) && defined(MAKE_KERBEROS4) +.if exists(${DESTDIR}${LIBDIR}/libkrb.a) && defined(MAKE_KERBEROS4) && !defined(NO_OPENSSL) && !defined(NOCRYPT) SRCS+= krcmd.c kcmd.c rcmd_util.c DPADD= ${LIBUTIL} ${LIBKRB} ${LIBCRYPTO} ${LIBCRYPT} ${LIBCOM_ERR} CFLAGS+=-DKERBEROS -DCRYPT -DHAVE_CONFIG_H \ Index: usr.bin/rsh/Makefile =================================================================== RCS file: /home/ncvs/src/usr.bin/rsh/Makefile,v retrieving revision 1.16 diff -u -r1.16 Makefile --- usr.bin/rsh/Makefile 2000/02/24 21:06:19 1.16 +++ usr.bin/rsh/Makefile 2000/03/05 22:32:04 @@ -6,7 +6,7 @@ CFLAGS+=-Wall CFLAGS+=-I${.CURDIR}/../../libexec/rlogind -.if exists(${DESTDIR}${LIBDIR}/libkrb.a) && defined(MAKE_KERBEROS4) +.if exists(${DESTDIR}${LIBDIR}/libkrb.a) && defined(MAKE_KERBEROS4) && !defined(NO_OPENSSL) && !defined(NOCRYPT) SRCS+= krcmd.c kcmd.c rcmd_util.c CFLAGS+=-DKERBEROS -DCRYPT -DHAVE_CONFIG_H \ -I${.CURDIR}/../rlogin -I${.CURDIR} -I- \ Index: usr.sbin/ppp/Makefile =================================================================== RCS file: /home/ncvs/src/usr.sbin/ppp/Makefile,v retrieving revision 1.71 diff -u -r1.71 Makefile --- usr.sbin/ppp/Makefile 2000/02/29 11:44:18 1.71 +++ usr.sbin/ppp/Makefile 2000/03/05 22:32:04 @@ -33,7 +33,7 @@ .endif .endif -.if exists(${.CURDIR}/../../secure) && !defined(NOCRYPT) && !defined(NOSECURE) && !defined(RELEASE_CRUNCH) +.if exists(${.CURDIR}/../../secure) && !defined(NOCRYPT) && !defined(NOSECURE) && !defined(NO_OPENSSL) && !defined(RELEASE_CRUNCH) DISTRIBUTION=crypto CFLAGS+=-DHAVE_DES SRCS+= chap_ms.c Index: usr.sbin/pppd/Makefile =================================================================== RCS file: /home/ncvs/src/usr.sbin/pppd/Makefile,v retrieving revision 1.17 diff -u -r1.17 Makefile --- usr.sbin/pppd/Makefile 2000/02/29 11:45:48 1.17 +++ usr.sbin/pppd/Makefile 2000/03/05 22:32:04 @@ -28,7 +28,7 @@ DPADD+= ${LIBPCAP} # MS-CHAP support. Requires the DES library. -.if exists(${.CURDIR}/../../secure) && !defined(NOCRYPT) && !defined(NOSECURE) && !defined(RELEASE_CRUNCH) +.if exists(${.CURDIR}/../../secure) && !defined(NOCRYPT) && !defined(NOSECURE) && !defined(NO_OPENSSL) && !defined(RELEASE_CRUNCH) DISTRIBUTION=crypto CFLAGS+=-DCHAPMS SRCS+= chap_ms.c ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 17: 6:40 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 2899D37BA71; Sun, 5 Mar 2000 17:06:39 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 26DD02E815B for ; Sun, 5 Mar 2000 17:06:39 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 5 Mar 2000 17:06:39 -0800 (PST) From: Kris Kennaway To: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, Oliver Fromme wrote: > the ports (yeah, stupid me), to no avail. It complained about some > RSA library missing. Did you read the error message? Perhaps you should. Perhaps reporting it here would help someone to actually fix your problem instead of having to guess. > PS: Just in case if it matters, I have USA_RESIDENT=NO in my > make.conf. Hmm. Can you try cvsupping your src-crypto and src-secure collections from another (non-US) cvsup server? One of the mirror sites in germany was bogusly fetching crypto from the US - I assumed it had been fixed by now after multiple emails to the maintainer, but perhaps it hasn't. SSH should work out of the box for International people. > 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. Read /etc/defaults/make.conf > By the way, _why_ is ssh in the base system now, and what is > wrong with having it in the ports? I'm sorry if there was a > "HEADS UP" on this list, then I must have missed it. Enough people wanted it in the base system - in fact, when the question was asked about importing it, I don't recall any objections - certainly it was not a significant opposition. I'm quite surprised you've missed any discussion of OpenSSH here though, since it's probably been one of the most discussed topics here for the past few weeks. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 17: 7:11 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 092EE37BBDB; Sun, 5 Mar 2000 17:07:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 06CBF2E815B; Sun, 5 Mar 2000 17:07:05 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 5 Mar 2000 17:07:04 -0800 (PST) From: Kris Kennaway To: "Matthew N. Dodd" Cc: Oliver Fromme , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > breakage. I can't fix this if you don't tell me what it is! Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 17:10: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 2800D37BB14; Sun, 5 Mar 2000 17:10:04 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id UAA89592; Sun, 5 Mar 2000 20:10:03 -0500 (EST) Date: Sun, 5 Mar 2000 20:10:03 -0500 (EST) From: "Matthew N. Dodd" To: Kris Kennaway Cc: Oliver Fromme , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Mar 2000, Kris Kennaway wrote: > On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > > breakage. > > I can't fix this if you don't tell me what it is! What? Nobody else is test compiling with NO_OPENSSL/NO_OPENSSH? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 17:15:46 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 5CC4A37BA4F; Sun, 5 Mar 2000 17:15:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5A06F2E815B; Sun, 5 Mar 2000 17:15:45 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 5 Mar 2000 17:15:45 -0800 (PST) From: Kris Kennaway To: "Matthew N. Dodd" Cc: Oliver Fromme , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > > > breakage. > > > > I can't fix this if you don't tell me what it is! > > What? Nobody else is test compiling with NO_OPENSSL/NO_OPENSSH? Your message wasn't clear you were talking about _world_ breakage. If this is your only problem, see my other message. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 17:54:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id A7F7D37BBF9 for ; Sun, 5 Mar 2000 17:54:20 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id BCB611962; Sun, 5 Mar 2000 17:54:18 -0800 (PST) Date: Sun, 5 Mar 2000 17:54:18 -0800 From: Chris Piazza To: FreeBSD-Current Subject: pam_ssh is broken! Would someone please review/commit PR 17191? Message-ID: <20000305175418.A964@norn.ca.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's all contained in the subject. I've built world with the change and tested it and it all works fine now. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 18: 2: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5366B37B564 for ; Sun, 5 Mar 2000 18:01:43 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA27249; Sun, 5 Mar 2000 18:01:38 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA85727; Sun, 5 Mar 2000 18:01:37 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 5 Mar 2000 18:01:37 -0800 (PST) Message-Id: <200003060201.SAA85727@vashon.polstra.com> To: dmmiller@cvzoom.net Subject: Re: More "ld-elf.so.1: assert failed" messages In-Reply-To: <38BB1E9C.CF44EC93@cvzoom.net> References: <38BA5751.2396AE87@cvzoom.net> <200002290104.RAA60914@vashon.polstra.com> <38BB1E9C.CF44EC93@cvzoom.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Just a reminder -- be extra careful when messing with the dynamic linker. It's easy to paint yourself into a corner if it's broken badly. Make a backup copy of your current working dynamic linker (/usr/libexec/ld-elf.so.1) before installing the experimental version. Then if things fall apart you can recover with something like this: cd /usr/libexec chflags 0 ld-elf.so.1* mv ld-elf.so.1.good ld-elf.so.1 Thanks in advance for any testing you folks can make time to do. John Index: Makefile =================================================================== RCS file: /home/ncvs/src/libexec/rtld-elf/Makefile,v retrieving revision 1.10 diff -u -r1.10 Makefile --- Makefile 2000/01/29 03:16:54 1.10 +++ Makefile 2000/03/01 02:39:13 @@ -3,7 +3,7 @@ # MAINTAINER= jdp PROG= ld-elf.so.1 -SRCS= rtld_start.S rtld.c lockdflt.c map_object.c malloc.c \ +SRCS= rtld_start.S rtld.c map_object.c malloc.c \ xmalloc.c debug.c reloc.c MAN1= rtld.1 CFLAGS+= -Wall -DFREEBSD_ELF -I${.CURDIR}/${MACHINE_ARCH} -I${.CURDIR} Index: lockdflt.c =================================================================== RCS file: lockdflt.c diff -N lockdflt.c --- /tmp/cvscXuMc22613 Sun Mar 5 17:48:37 2000 +++ /dev/null Sun Mar 5 02:02:18 2000 @@ -1,89 +0,0 @@ -/*- - * Copyright 1999, 2000 John D. Polstra. - * All rights reserved. - * - * Redistribution and use in source and binary forms, with or without - * modification, are permitted provided that the following conditions - * are met: - * 1. Redistributions of source code must retain the above copyright - * notice, this list of conditions and the following disclaimer. - * 2. Redistributions in binary form must reproduce the above copyright - * notice, this list of conditions and the following disclaimer in the - * documentation and/or other materials provided with the distribution. - * - * THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR - * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES - * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. - * IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, - * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT - * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, - * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY - * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT - * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF - * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - * - * $FreeBSD: src/libexec/rtld-elf/lockdflt.c,v 1.4 2000/01/25 01:32:56 jdp Exp $ - */ - -/* - * Default thread locking implementation for the dynamic linker. It - * is used until the client registers a different implementation with - * dllockinit(). The default implementation does mutual exclusion by - * blocking almost all signals. This is based on the observation that - * most userland thread packages use signals to support preemption. - */ - -#include -#include -#include - -#include "debug.h" -#include "rtld.h" - -typedef struct Struct_LockDflt { - sigset_t lock_mask; - sigset_t old_mask; - int depth; -} LockDflt; - -void -lockdflt_acquire(void *lock) -{ - LockDflt *l = (LockDflt *)lock; - sigprocmask(SIG_BLOCK, &l->lock_mask, &l->old_mask); - assert(l->depth == 0); - l->depth++; -} - -void * -lockdflt_create(void *context) -{ - LockDflt *l; - - l = NEW(LockDflt); - l->depth = 0; - sigfillset(&l->lock_mask); - sigdelset(&l->lock_mask, SIGTRAP); - sigdelset(&l->lock_mask, SIGABRT); - sigdelset(&l->lock_mask, SIGBUS); - sigdelset(&l->lock_mask, SIGSEGV); - sigdelset(&l->lock_mask, SIGKILL); - sigdelset(&l->lock_mask, SIGSTOP); - return l; -} - -void -lockdflt_destroy(void *lock) -{ - LockDflt *l = (LockDflt *)lock; - free(l); -} - -void -lockdflt_release(void *lock) -{ - LockDflt *l = (LockDflt *)lock; - assert(l->depth == 1); - l->depth--; - sigprocmask(SIG_SETMASK, &l->old_mask, NULL); -} Index: rtld.c =================================================================== RCS file: /home/ncvs/src/libexec/rtld-elf/rtld.c,v retrieving revision 1.43 diff -u -r1.43 rtld.c --- rtld.c 2000/01/29 01:26:59 1.43 +++ rtld.c 2000/03/06 01:44:11 @@ -61,6 +61,9 @@ typedef struct Struct_LockInfo { void *context; /* Client context for creating locks */ void *thelock; /* The one big lock */ + /* Debugging aids. */ + volatile int rcount; /* Number of readers holding lock */ + volatile int wcount; /* Number of writers holding lock */ /* Methods */ void (*rlock_acquire)(void *lock); void (*wlock_acquire)(void *lock); @@ -70,6 +73,16 @@ } LockInfo; /* + * This structure provides a reentrant way to keep a list of objects and + * check which ones have already been processed in some way. + */ +typedef struct Struct_DoneList { + Obj_Entry **objs; /* Array of object pointers */ + unsigned int num_alloc; /* Allocated size of the array */ + unsigned int num_used; /* Number of array slots used */ +} DoneList; + +/* * Function declarations. */ static const char *basename(const char *); @@ -77,6 +90,7 @@ static void digest_dynamic(Obj_Entry *); static Obj_Entry *digest_phdr(const Elf_Phdr *, int, caddr_t, const char *); static Obj_Entry *dlcheck(void *); +static bool donelist_check(DoneList *, Obj_Entry *); static char *find_library(const char *, const Obj_Entry *); static void funclist_call(Funclist *); static void funclist_clear(Funclist *); @@ -85,7 +99,7 @@ static void funclist_push_tail(Funclist *, InitFunc); static const char *gethints(void); static void init_dag(Obj_Entry *); -static void init_dag1(Obj_Entry *root, Obj_Entry *obj); +static void init_dag1(Obj_Entry *root, Obj_Entry *obj, DoneList *); static void init_rtld(caddr_t); static bool is_exported(const Elf_Sym *); static void linkmap_add(Obj_Entry *); @@ -93,6 +107,7 @@ static int load_needed_objects(Obj_Entry *); static int load_preload_objects(void); static Obj_Entry *load_object(char *); +static void lock_check(void); static void lock_nop(void *); static Obj_Entry *obj_from_addr(const void *); static void objlist_add(Objlist *, Obj_Entry *); @@ -104,7 +119,7 @@ static char *search_library_path(const char *, const char *); static void set_program_var(const char *, const void *); static const Elf_Sym *symlook_list(const char *, unsigned long, - Objlist *, const Obj_Entry **, bool in_plt); + Objlist *, const Obj_Entry **, bool in_plt, DoneList *); static void trace_loaded_objects(Obj_Entry *obj); static void unload_object(Obj_Entry *); static void unref_dag(Obj_Entry *); @@ -128,7 +143,7 @@ static Obj_Entry **obj_tail; /* Link field of last object in list */ static Obj_Entry *obj_main; /* The main program shared object */ static Obj_Entry obj_rtld; /* The dynamic linker shared object */ -static unsigned long curmark; /* Current mark value */ +static unsigned int obj_count; /* Number of objects in obj_list */ static Objlist list_global = /* Objects dlopened with RTLD_GLOBAL */ STAILQ_HEAD_INITIALIZER(list_global); @@ -167,21 +182,44 @@ char *__progname; char **environ; +/* + * Fill in a DoneList with an allocation large enough to hold all of + * the currently-loaded objects. Keep this as a macro since it calls + * alloca and we want that to occur within the scope of the caller. + */ +#define donelist_init(dlp) \ + ((dlp)->objs = alloca(obj_count * sizeof (dlp)->objs[0]), \ + assert((dlp)->objs != NULL), \ + (dlp)->num_alloc = obj_count, \ + (dlp)->num_used = 0) + static __inline void rlock_acquire(void) { lockinfo.rlock_acquire(lockinfo.thelock); + atomic_incr_int(&lockinfo.rcount); + lock_check(); } static __inline void wlock_acquire(void) { lockinfo.wlock_acquire(lockinfo.thelock); + atomic_incr_int(&lockinfo.wcount); + lock_check(); +} + +static __inline void +rlock_release(void) +{ + atomic_decr_int(&lockinfo.rcount); + lockinfo.lock_release(lockinfo.thelock); } static __inline void -lock_release(void) +wlock_release(void) { + atomic_decr_int(&lockinfo.wcount); lockinfo.lock_release(lockinfo.thelock); } @@ -316,6 +354,7 @@ /* Link the main program into the list of objects. */ *obj_tail = obj_main; obj_tail = &obj_main->next; + obj_count++; obj_main->refcount++; /* Initialize a fake symbol for resolving undefined weak references. */ @@ -366,7 +405,7 @@ funclist_call(&initlist); wlock_acquire(); funclist_clear(&initlist); - lock_release(); + wlock_release(); dbg("transferring control to program entry point = %p", obj_main->entry); @@ -385,7 +424,7 @@ Elf_Addr *where; Elf_Addr target; - wlock_acquire(); + rlock_acquire(); if (obj->pltrel) rel = (const Elf_Rel *) ((caddr_t) obj->pltrel + reloff); else @@ -403,7 +442,7 @@ (void *)target, basename(defobj->path)); reloc_jmpslot(where, target); - lock_release(); + rlock_release(); return target; } @@ -671,6 +710,28 @@ } /* + * If the given object is already in the donelist, return true. Otherwise + * add the object to the list and return false. + */ +static bool +donelist_check(DoneList *dlp, Obj_Entry *obj) +{ + unsigned int i; + + for (i = 0; i < dlp->num_used; i++) + if (dlp->objs[i] == obj) + return true; + /* + * Our donelist allocation should always be sufficient. But if a + * threads package hasn't set up its locking properly, more shared + * objects could have been loaded since we allocated the list. + */ + if (dlp->num_used < dlp->num_alloc) + dlp->objs[dlp->num_used++] = obj; + return false; +} + +/* * Hash function for symbol table lookup. Don't even think about changing * this. It is specified by the System V ABI. */ @@ -741,6 +802,7 @@ find_symdef(unsigned long symnum, Obj_Entry *refobj, const Obj_Entry **defobj_out, bool in_plt) { + DoneList donelist; const Elf_Sym *ref; const Elf_Sym *def; const Elf_Sym *symp; @@ -755,11 +817,11 @@ hash = elf_hash(name); def = NULL; defobj = NULL; - curmark++; + donelist_init(&donelist); - if (refobj->symbolic) { /* Look first in the referencing object */ + /* Look first in the referencing object if linked symbolically. */ + if (refobj->symbolic && !donelist_check(&donelist, refobj)) { symp = symlook_obj(name, hash, refobj, in_plt); - refobj->mark = curmark; if (symp != NULL) { def = symp; defobj = refobj; @@ -768,7 +830,7 @@ /* Search all objects loaded at program start up. */ if (def == NULL || ELF_ST_BIND(def->st_info) == STB_WEAK) { - symp = symlook_list(name, hash, &list_main, &obj, in_plt); + symp = symlook_list(name, hash, &list_main, &obj, in_plt, &donelist); if (symp != NULL && (def == NULL || ELF_ST_BIND(symp->st_info) != STB_WEAK)) { def = symp; @@ -780,7 +842,8 @@ STAILQ_FOREACH(elm, &refobj->dldags, link) { if (def != NULL && ELF_ST_BIND(def->st_info) != STB_WEAK) break; - symp = symlook_list(name, hash, &elm->obj->dagmembers, &obj, in_plt); + symp = symlook_list(name, hash, &elm->obj->dagmembers, &obj, in_plt, + &donelist); if (symp != NULL && (def == NULL || ELF_ST_BIND(symp->st_info) != STB_WEAK)) { def = symp; @@ -790,7 +853,7 @@ /* Search all RTLD_GLOBAL objects. */ if (def == NULL || ELF_ST_BIND(def->st_info) == STB_WEAK) { - symp = symlook_list(name, hash, &list_global, &obj, in_plt); + symp = symlook_list(name, hash, &list_global, &obj, in_plt, &donelist); if (symp != NULL && (def == NULL || ELF_ST_BIND(symp->st_info) != STB_WEAK)) { def = symp; @@ -919,23 +982,24 @@ static void init_dag(Obj_Entry *root) { - curmark++; - init_dag1(root, root); + DoneList donelist; + + donelist_init(&donelist); + init_dag1(root, root, &donelist); } static void -init_dag1(Obj_Entry *root, Obj_Entry *obj) +init_dag1(Obj_Entry *root, Obj_Entry *obj, DoneList *dlp) { const Needed_Entry *needed; - if (obj->mark == curmark) + if (donelist_check(dlp, obj)) return; - obj->mark = curmark; objlist_add(&obj->dldags, root); objlist_add(&root->dagmembers, obj); for (needed = obj->needed; needed != NULL; needed = needed->next) if (needed->obj != NULL) - init_dag1(root, needed->obj); + init_dag1(root, needed->obj, dlp); } /* @@ -971,6 +1035,7 @@ */ obj_list = &obj_rtld; obj_tail = &obj_rtld.next; + obj_count = 1; relocate_objects(&obj_rtld, true); } @@ -978,6 +1043,7 @@ /* Make the object list empty again. */ obj_list = NULL; obj_tail = &obj_list; + obj_count = 0; /* Replace the path with a dynamically allocated copy. */ obj_rtld.path = xstrdup(obj_rtld.path); @@ -1118,6 +1184,7 @@ *obj_tail = obj; obj_tail = &obj->next; + obj_count++; linkmap_add(obj); /* for GDB */ dbg(" %p .. %p: %s", obj->mapbase, @@ -1131,6 +1198,26 @@ return obj; } +/* + * Check for locking violations and die if one is found. + */ +static void +lock_check(void) +{ + int rcount, wcount; + + rcount = lockinfo.rcount; + wcount = lockinfo.wcount; + assert(rcount >= 0); + assert(wcount >= 0); + if (wcount > 1 || (wcount != 0 && rcount != 0)) { + _rtld_error("Application locking error: %d readers and %d writers" + " in dynamic linker. See DLLOCKINIT(3) in manual pages.", + rcount, wcount); + die(); + } +} + static void lock_nop(void *lock) { @@ -1317,7 +1404,7 @@ wlock_acquire(); root = dlcheck(handle); if (root == NULL) { - lock_release(); + wlock_release(); return -1; } @@ -1336,7 +1423,7 @@ if (obj->refcount == 0 && obj->fini != NULL) funclist_push_tail(&finilist, obj->fini); - lock_release(); + wlock_release(); funclist_call(&finilist); wlock_acquire(); funclist_clear(&finilist); @@ -1346,7 +1433,7 @@ unload_object(root); GDB_STATE(RT_CONSISTENT); } - lock_release(); + wlock_release(); return 0; } @@ -1373,10 +1460,8 @@ if (lock_create == NULL) { is_dflt = true; context = NULL; - lock_create = lockdflt_create; - rlock_acquire = wlock_acquire = lockdflt_acquire; - lock_release = lockdflt_release; - lock_destroy = lockdflt_destroy; + rlock_acquire = wlock_acquire = lock_release = lock_nop; + lock_destroy = NULL; context_destroy = NULL; } @@ -1394,17 +1479,15 @@ /* * Make sure the shared objects containing the locking methods are * fully bound, to avoid infinite recursion when they are called - * from the lazy binding code. + * from the lazy binding code. Then allocate the lock we will use. */ if (!is_dflt) { prebind((void *)rlock_acquire); prebind((void *)wlock_acquire); prebind((void *)lock_release); + lockinfo.thelock = lock_create(lockinfo.context); } - /* Allocate our lock. */ - lockinfo.thelock = lock_create(lockinfo.context); - /* Record the new method information. */ lockinfo.context = context; lockinfo.rlock_acquire = rlock_acquire; @@ -1482,11 +1565,11 @@ GDB_STATE(RT_CONSISTENT); /* Call the init functions with no locks held. */ - lock_release(); + wlock_release(); funclist_call(&initlist); wlock_acquire(); funclist_clear(&initlist); - lock_release(); + wlock_release(); return obj; } @@ -1502,14 +1585,14 @@ def = NULL; defobj = NULL; - wlock_acquire(); + rlock_acquire(); if (handle == NULL || handle == RTLD_NEXT) { void *retaddr; retaddr = __builtin_return_address(0); /* __GNUC__ only */ if ((obj = obj_from_addr(retaddr)) == NULL) { _rtld_error("Cannot determine caller's shared object"); - lock_release(); + rlock_release(); return NULL; } if (handle == NULL) { /* Just the caller's shared object. */ @@ -1525,14 +1608,17 @@ } } else { if ((obj = dlcheck(handle)) == NULL) { - lock_release(); + rlock_release(); return NULL; } if (obj->mainprog) { + DoneList donelist; + /* Search main program and all libraries loaded by it. */ - curmark++; - def = symlook_list(name, hash, &list_main, &defobj, true); + donelist_init(&donelist); + def = symlook_list(name, hash, &list_main, &defobj, true, + &donelist); } else { /* * XXX - This isn't correct. The search should include the whole @@ -1544,12 +1630,12 @@ } if (def != NULL) { - lock_release(); + rlock_release(); return defobj->relocbase + def->st_value; } _rtld_error("Undefined symbol \"%s\"", name); - lock_release(); + rlock_release(); return NULL; } @@ -1561,11 +1647,11 @@ void *symbol_addr; unsigned long symoffset; - wlock_acquire(); + rlock_acquire(); obj = obj_from_addr(addr); if (obj == NULL) { _rtld_error("No shared object contains address"); - lock_release(); + rlock_release(); return 0; } info->dli_fname = obj->path; @@ -1604,7 +1690,7 @@ if (info->dli_saddr == addr) break; } - lock_release(); + rlock_release(); return 1; } @@ -1695,7 +1781,7 @@ static const Elf_Sym * symlook_list(const char *name, unsigned long hash, Objlist *objlist, - const Obj_Entry **defobj_out, bool in_plt) + const Obj_Entry **defobj_out, bool in_plt, DoneList *dlp) { const Elf_Sym *symp; const Elf_Sym *def; @@ -1705,9 +1791,8 @@ def = NULL; defobj = NULL; STAILQ_FOREACH(elm, objlist, link) { - if (elm->obj->mark == curmark) + if (donelist_check(dlp, elm->obj)) continue; - elm->obj->mark = curmark; if ((symp = symlook_obj(name, hash, elm->obj, in_plt)) != NULL) { if (def == NULL || ELF_ST_BIND(symp->st_info) != STB_WEAK) { def = symp; @@ -1877,6 +1962,7 @@ munmap(obj->mapbase, obj->mapsize); linkmap_delete(obj); *linkp = obj->next; + obj_count--; obj_free(obj); } else linkp = &obj->next; Index: rtld.h =================================================================== RCS file: /home/ncvs/src/libexec/rtld-elf/rtld.h,v retrieving revision 1.15 diff -u -r1.15 rtld.h --- rtld.h 2000/01/29 01:26:59 1.15 +++ rtld.h 2000/03/01 02:39:27 @@ -149,7 +149,6 @@ Objlist dagmembers; /* DAG has these members (%) */ dev_t dev; /* Object's filesystem's device */ ino_t ino; /* Object's inode number */ - unsigned long mark; /* Set to "curmark" to avoid repeat visits */ } Obj_Entry; #define RTLD_MAGIC 0xd550b87a @@ -170,10 +169,6 @@ const Elf_Sym *find_symdef(unsigned long, Obj_Entry *, const Obj_Entry **, bool); void init_pltgot(Obj_Entry *); -void lockdflt_acquire(void *); -void *lockdflt_create(void *); -void lockdflt_destroy(void *); -void lockdflt_release(void *); void obj_free(Obj_Entry *); Obj_Entry *obj_new(void); int reloc_non_plt(Obj_Entry *, Obj_Entry *); Index: alpha/rtld_machdep.h =================================================================== RCS file: /home/ncvs/src/libexec/rtld-elf/alpha/rtld_machdep.h,v retrieving revision 1.3 diff -u -r1.3 rtld_machdep.h --- alpha/rtld_machdep.h 1999/08/28 00:10:13 1.3 +++ alpha/rtld_machdep.h 2000/03/06 01:37:22 @@ -34,4 +34,8 @@ void reloc_jmpslot(Elf_Addr *, Elf_Addr); +/* Atomically increment / decrement an int. */ +void atomic_incr_int(volatile int *); +void atomic_decr_int(volatile int *); + #endif Index: alpha/rtld_start.S =================================================================== RCS file: /home/ncvs/src/libexec/rtld-elf/alpha/rtld_start.S,v retrieving revision 1.3 diff -u -r1.3 rtld_start.S --- alpha/rtld_start.S 1999/08/28 00:10:13 1.3 +++ alpha/rtld_start.S 2000/03/06 01:37:58 @@ -166,6 +166,24 @@ jmp $31, ($27) .end _rtld_bind_start +/* Atomically increment an int. */ +LEAF(atomic_incr_int, 1) +0: ldl_l t0, 0(a0) + addq t0, 1, t0 + stl_c t0, 0(a0) + beq t0, 1f + mb + RET +1: br 0b + END(atomic_incr_int) - - +/* Atomically decrement an int. */ +LEAF(atomic_decr_int, 1) +0: ldl_l t0, 0(a0) + subq t0, 1, t0 + stl_c t0, 0(a0) + beq t0, 1f + mb + RET +1: br 0b + END(atomic_decr_int) Index: i386/rtld_machdep.h =================================================================== RCS file: /home/ncvs/src/libexec/rtld-elf/i386/rtld_machdep.h,v retrieving revision 1.3 diff -u -r1.3 rtld_machdep.h --- i386/rtld_machdep.h 1999/08/28 00:10:14 1.3 +++ i386/rtld_machdep.h 2000/03/06 01:40:47 @@ -41,4 +41,18 @@ (*(Elf_Addr *)(where) = (Elf_Addr)(target)); \ } while (0) +/* Atomically increment / decrement an int. */ + +static __inline void +atomic_incr_int(volatile int *p) +{ + __asm __volatile("lock; incl %0" : "=m" (*p) : "0" (*p)); +} + +static __inline void +atomic_decr_int(volatile int *p) +{ + __asm __volatile("lock; decl %0" : "=m" (*p) : "0" (*p)); +} + #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 18:10:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 8306737BBDE for ; Sun, 5 Mar 2000 18:10:08 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.251.241]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id VAA08570; Sun, 5 Mar 2000 21:09:02 -0500 (EST) Message-ID: <38C3133E.E6CC2099@acm.org> Date: Sun, 05 Mar 2000 21:09:02 -0500 From: Jim Bloom X-Mailer: Mozilla 4.72 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Chris Wasser Cc: current@FreeBSD.ORG Subject: Re: AWE64 & PCM References: <20000305154118.A1550@area51.v-wave.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The only minor problem I see is that your game port is detected twice. Other than that, the hardware is detected correctly. You have asked for help, but what problem(s) are you seeing? I believe to get everything currently support on the AWE64, your config file should look like this: device pcm device sbc device joy There is no support for the wave table part of the card at this time. Jim Bloom bloom@acm.org Chris Wasser wrote: > > Hi all, hate to post something this insignificant to the mailing list, but > I've search the entire src tree with no luck in resolving this myself > (well, grepping for awe64,wavetable,game .. found the AWE64 define in > /usr/src/sys/dev/sound/isa/sbc.c easily enough) .. I'm sure it's due to > some braindeadness on my behalf, but I'd sure appriciate someone steering > me in the right direction on this. I also searched for the > matching/compatible ID strings, no luck. > > Hopefully I provided enough information here... > > FreeBSD area51.v-wave.com 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Sun Mar 5 > 12:02:16 MST 2000 root@area51.v-wave.com:/usr/src/sys/compile/AREA51 > i386 > > (cvsupped today -- well, at time of this posting.) > > joy0 at port 0x201 on isa0 > sbc0: 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: on sbc0 > joy1: at port 0x208-0x20f on isa0 > unknown0: at port 0x620-0x623 on isa0 > > Now I tried enabling PNPBIOS in the kernel config, but that just produced > a screenful of crap [PNP OS is disabled in the BIOS], here are the > relevant kernel config options (no, I didn't add anything else for sound > but this): > > [I read somewhere that the PCM driver doesn't support MIDI yet, not sure > if this is related] > > device pcm > device joy0 at isa? port IO_GAME > > Adding the sbc driver into the config didn't help either, produced the > same dmesg output as above. > > I didn't use anything from the Voxware drivers like I used to under 3.x, I > also tried using the pnp directives for userconfig at boot time, but that > only produced syntax errors [same config I used for 3.x]: > > in /boot/kernel.conf: > > pnp 1 0 os enable irq0 5 drq0 1 drq1 5 port0 0x220 port1 0x330 port2 0x388 > pnp 1 1 os disable > pnp 1 2 os enable port0 0x620 port1 0xa20 port2 0xe20 > pnp 1 3 os disable > > devices in /dev: > > (sh MAKEDEV snd0) > > 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/mixer@ -> mixer0 > 0 crw-rw-rw- 1 root wheel 30, 0 Feb 24 02:05 /dev/mixer0 > 0 lrwxrwxrwx 1 root wheel 10 Feb 24 02:05 /dev/sequencer@ -> > sequencer0 > 0 crw-rw-rw- 1 root wheel 30, 1 Feb 24 02:05 /dev/sequencer0 > 0 crw-rw-rw- 1 root wheel 30, 2 Feb 24 02:05 /dev/midi0 > 0 lrwxrwxrwx 1 root wheel 4 Feb 24 02:05 /dev/dsp@ -> dsp0 > 0 crw-rw-rw- 1 root wheel 30, 3 Mar 5 12:43 /dev/dsp0 > 0 lrwxrwxrwx 1 root wheel 5 Feb 24 02:05 /dev/dspW@ -> dspW0 > 0 crw-rw-rw- 1 root wheel 30, 5 Feb 24 02:05 /dev/dspW0 > 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/audio@ -> audio0 > 0 crw-rw-rw- 1 root wheel 30, 4 Feb 24 02:05 /dev/audio0 > 0 crw-rw-rw- 1 root wheel 30, 6 Feb 24 02:05 /dev/sndstat > 0 lrwxrwxrwx 1 root wheel 6 Feb 24 02:05 /dev/music@ -> music0 > 0 crw-rw-rw- 1 root wheel 30, 8 Feb 24 02:05 /dev/music0 > 0 lrwxrwxrwx 1 root wheel 4 Feb 24 02:05 /dev/pss@ -> pss0 > 0 crw-rw-rw- 1 root wheel 30, 9 Feb 24 02:05 /dev/pss0 > > /dev/sndstat reports: > > FreeBSD Audio Driver (newpcm) Mar 5 2000 12:00:51 > Installed devices: > pcm0: at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex) > > And finally, a pnpinfo dump: > > Checking for Plug-n-Play devices... > > Card assigned CSN #1 > Vendor ID CTL00c3 (0xc3008c0e), Serial Number 0x1fa45429 > PnP Version 1.0, Vendor Version 16 > Device Description: Creative SB AWE64 PnP > *** Small Vendor Tag Detected > > Logical Device ID: CTL0045 0x45008c0e #0 > Device Description: Audio > TAG Start DF > Good Configuration > IRQ: 5 - only one type (true/edge) > DMA: channel(s) 1 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 > [16-bit addr] > I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5 6 7 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5 6 7 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5 6 7 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > TAG Start DF > Sub-optimal Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5 6 7 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x10, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x394, alignment 0x4, len 0x4 > [16-bit addr] > TAG End DF > > Logical Device ID: CTL7002 0x02708c0e #1 > Compatible Device ID: PNPb02f (2fb0d041) > Device Description: Game > TAG Start DF > Good Configuration > I/O Range 0x200 .. 0x200, alignment 0x1, len 0x8 > [16-bit addr] > TAG Start DF > Acceptable Configuration > I/O Range 0x200 .. 0x208, alignment 0x8, len 0x8 > [16-bit addr] > TAG End DF > > Logical Device ID: CTL0022 0x22008c0e #2 > Device Description: WaveTable > TAG Start DF > Good Configuration > I/O Range 0x620 .. 0x620, alignment 0x1, len 0x4 > [16-bit addr] > TAG Start DF > Acceptable Configuration > I/O Range 0x620 .. 0x680, alignment 0x20, len 0x4 > [16-bit addr] > TAG End DF > *** Small Vendor Tag Detected > End Tag > > Successfully got 69 resources, 3 logical fdevs > -- card select # 0x0001 > > CSN CTL00c3 (0xc3008c0e), Serial Number 0x1fa45429 > > Logical device #0 > IO: 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 > IRQ 5 0 > DMA 1 5 > IO range check 0x00 activate 0x01 > > Logical device #1 > IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 > IRQ 0 0 > DMA 4 4 > IO range check 0x00 activate 0x01 > > Logical device #2 > IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 > IRQ 0 0 > DMA 4 4 > IO range check 0x00 activate 0x01 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 18:11:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id B8B8237BBF1 for ; Sun, 5 Mar 2000 18:11:47 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (tanimura@localhost.r.dl.itc.u-tokyo.ac.jp [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-rina.r-0.1-11.01.2000) with ESMTP id LAA04876; Mon, 6 Mar 2000 11:11:39 +0900 (JST) Date: Mon, 06 Mar 2000 11:11:38 +0900 Message-ID: <14531.5082.963565.29321F@rina.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: freebsd-current@FreeBSD.ORG Cc: olli@dorifer.heim3.tu-clausthal.de Subject: Re: kern/16487: please apply newpcm fix In-Reply-To: In your message of "Mon, 6 Mar 2000 01:22:41 +0100 (CET)" <200003060022.BAA00966@dorifer.heim3.tu-clausthal.de> References: <200003060022.BAA00966@dorifer.heim3.tu-clausthal.de> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000 01:22:41 +0100 (CET), Oliver Fromme said: Oliver> Would someone please (pretty please) have a look at kern/16487 Oliver> and commit the trivial fix in it? It's just one line, and it Oliver> makes AvanceLogic-100 soundcards work again. The logical ID of ALS100 conflicts with the one of CMI8330(mss), so we also have to check the vendor ID. Could you please give it to me? It is likely to be 0x00019305. (ALS110 is 0x10019305 and ALS120 is 0x20019305, so...) -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 18:55:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B2BD437B9EA; Sun, 5 Mar 2000 18:55:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA64974; Sun, 5 Mar 2000 18:55:15 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA32598; Sun, 5 Mar 2000 18:55:18 -0800 (PST) (envelope-from obrien) Date: Sun, 5 Mar 2000 18:55:17 -0800 From: "David O'Brien" To: Nick Sayer Cc: freebsd-emulation@freebsd.org, freebsd-current@freebsd.org Subject: Re: VMWare 2.0R broken - linux ioctl(13, 1260, *) not implemented Message-ID: <20000305185517.C15849@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <38C2629F.FD2290E0@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38C2629F.FD2290E0@quack.kfu.com>; from nsayer@quack.kfu.com on Sun, Mar 05, 2000 at 01:35:27PM +0000 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 05, 2000 at 01:35:27PM +0000, Nick Sayer wrote: > Ah! I found it! > > --- linux_ioctl.h.orig Mon Feb 28 11:50:23 2000 > +++ linux_ioctl.h Mon Feb 28 11:24:08 2000 > @@ -32,6 +32,25 @@ > #define _LINUX_IOCTL_H_ This patch is fubar'ed. Your mailer wrapped lines and turned into 's. Can you repost this patch w/o damaging it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 19: 2:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id DFCC737BBE1 for ; Sun, 5 Mar 2000 19:02:53 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA65007; Sun, 5 Mar 2000 19:02:53 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA32639; Sun, 5 Mar 2000 19:02:59 -0800 (PST) (envelope-from obrien) Date: Sun, 5 Mar 2000 19:02:59 -0800 From: "David O'Brien" To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: diskprep beta -- comments wanted. Message-ID: <20000305190259.E15849@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <49982.952128913@axl.ops.uunet.co.za> <200003040040.RAA26239@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003040040.RAA26239@harmony.village.org>; from imp@village.org on Fri, Mar 03, 2000 at 05:40:17PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 03, 2000 at 05:40:17PM -0700, Warner Losh wrote: > > sysinstall doesn't work at all for me. On three different machines, > it tells me that it found no disks. So I can't comment on this. Every time that happens to me, I just build and install a new sysinstall on that machine and all of a sudden it works again. I'm guessing there is something in the disk code that is sensitive to some structure size or placement. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 19: 4:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from area51.v-wave.com (area51.v-wave.com [24.108.26.39]) by hub.freebsd.org (Postfix) with SMTP id D8D6A37BBF3 for ; Sun, 5 Mar 2000 19:04:13 -0800 (PST) (envelope-from flatline@area51.v-wave.com) Received: (qmail 3326 invoked by uid 1001); 6 Mar 2000 03:04:47 -0000 Date: Sun, 5 Mar 2000 20:04:47 -0700 From: Chris Wasser To: Jim Bloom Cc: current@FreeBSD.ORG Subject: Re: AWE64 & PCM Message-ID: <20000305200447.A3307@area51.v-wave.com> References: <20000305154118.A1550@area51.v-wave.com> <38C3133E.E6CC2099@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38C3133E.E6CC2099@acm.org>; from bloom@acm.org on Sun, Mar 05, 2000 at 09:09:02PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 05, 2000 at 09:09:02PM -0500, Jim Bloom wrote: > The only minor problem I see is that your game port is detected twice. Other > than that, the hardware is detected correctly. You have asked for help, but > what problem(s) are you seeing? Yeah, I realized that after the fact, thanks however :) > There is no support for the wave table part of the card at this time. Ok, that's the answer I was looking for, thought perhaps I was missing something there. Thanks again. Also, I was reading somewhere that turning on 3D Stereo Enhancement was simply by turning on a register somewhere (I forgot the exact explanation) is this possible also with newpcm? I kinda miss the feature of it. [I know my AWE64 supports it]. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 19:16:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DE71E37B794; Sun, 5 Mar 2000 19:16:14 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA52038; Sun, 5 Mar 2000 20:16:12 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA54669; Sun, 5 Mar 2000 20:16:06 -0700 (MST) Message-Id: <200003060316.UAA54669@harmony.village.org> To: obrien@FreeBSD.ORG Subject: Re: diskprep beta -- comments wanted. Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 05 Mar 2000 19:02:59 PST." <20000305190259.E15849@dragon.nuxi.com> References: <20000305190259.E15849@dragon.nuxi.com> <49982.952128913@axl.ops.uunet.co.za> <200003040040.RAA26239@harmony.village.org> Date: Sun, 05 Mar 2000 20:16:06 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000305190259.E15849@dragon.nuxi.com> "David O'Brien" writes: : > sysinstall doesn't work at all for me. On three different machines, : > it tells me that it found no disks. So I can't comment on this. : : Every time that happens to me, I just build and install a new sysinstall : on that machine and all of a sudden it works again. I'm guessing there : is something in the disk code that is sensitive to some structure size or : placement. This was on the machine I built it on... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 20:23:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 3A6B637BC12; Sun, 5 Mar 2000 20:23:42 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id XAA01323; Sun, 5 Mar 2000 23:23:39 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200003060423.XAA01323@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 05 Mar 2000 23:23:39 -0500 (EST) From: John Baldwin To: Kris Kennaway Subject: Re: ssh strangeness in -current... Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Mar-00 Kris Kennaway wrote: > On Mon, 6 Mar 2000, Oliver Fromme wrote: > >> the ports (yeah, stupid me), to no avail. It complained about some >> RSA library missing. > > Did you read the error message? Perhaps you should. Perhaps reporting it > here would help someone to actually fix your problem instead of having to > guess. I think you've kind of missed the point though, Kris. How many other people are going to upgrade only to find that their previously working system is now broken. We should at least mention this in UPDATING so people have a ghost of a chance. >> 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. > > Read /etc/defaults/make.conf > >> By the way, _why_ is ssh in the base system now, and what is >> wrong with having it in the ports? I'm sorry if there was a >> "HEADS UP" on this list, then I must have missed it. > > Enough people wanted it in the base system - in fact, when the question > was asked about importing it, I don't recall any objections - certainly it > was not a significant opposition. Actually, I don't recall a question. Rather, I recall Jordan saying that once openssl had finally been all fixed, we might as well add openssh so it would be useful. Had a vote been taken, I would have voted to pull openssl and wait until after 4.0 to straighten all this out. From other discussions I've had several other people I know would have voted the same way. Thankfully it is now in a working state for new installs and for upgrades if you sacrafice the proper animal and dance under a full moon, yada, yada, yada. :) > I'm quite surprised you've missed any discussion of OpenSSH here though, > since it's probably been one of the most discussed topics here for the > past few weeks. > > Kris -- John Baldwin -- 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 20:49:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C920D37B847 for ; Sun, 5 Mar 2000 20:49:16 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id UAA65730; Sun, 5 Mar 2000 20:49:16 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id UAA38022; Sun, 5 Mar 2000 20:49:23 -0800 (PST) (envelope-from obrien) Date: Sun, 5 Mar 2000 20:49:22 -0800 From: "David O'Brien" To: Matthew Hunt Cc: current@FreeBSD.ORG Subject: Re: which(1), rewritten in C? Message-ID: <20000305204922.H15849@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <38BF334F.2F10D4B0@confusion.net> <20000303120441.A56070@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000303120441.A56070@wopr.caltech.edu>; from mph@astro.caltech.edu on Fri, Mar 03, 2000 at 12:04:41PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 03, 2000 at 12:04:41PM -0800, Matthew Hunt wrote: > > and the "type" builtin is too verbose, saying "which is hashed alias which='type -p' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 21:21:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 458D737B847; Sun, 5 Mar 2000 21:21:47 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA07432; Sun, 5 Mar 2000 21:21:43 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38C34065.B4E16DD4@gorean.org> Date: Sun, 05 Mar 2000 21:21:41 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-CURRENT-0302 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: Kris Kennaway , Oliver Fromme , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > On Sun, 5 Mar 2000, Kris Kennaway wrote: > > On Sun, 5 Mar 2000, Matthew N. Dodd wrote: > > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > > > breakage. > > > > I can't fix this if you don't tell me what it is! > > What? Nobody else is test compiling with NO_OPENSSL/NO_OPENSSH? I am. I found an error, sent it to the list, and Kris came up with a fix. The whole point of gamma testing the release candidates is that when people find problems they report them and they get fixed. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 22:18:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8F12837BC15 for ; Sun, 5 Mar 2000 22:18:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA52540 for ; Sun, 5 Mar 2000 23:18:46 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA56131 for ; Sun, 5 Mar 2000 23:18:39 -0700 (MST) Message-Id: <200003060618.XAA56131@harmony.village.org> To: current@freebsd.org Subject: openssh question Date: Sun, 05 Mar 2000 23:18:39 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually two. First, how does one enable TIS/SKEY authorization for ssh? It appears that the frst step would be to add -DSKEY to the Makefile conditional on something. Are there other steps? Second, how does one specify options on the command line? In ssh 1.2.x, I say ssh -o ForwardX11=yes, but that doesn't work in OpenSSH. Bug or feature? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 5 23:16:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from area51.v-wave.com (area51.v-wave.com [24.108.26.39]) by hub.freebsd.org (Postfix) with SMTP id 69DBB37BC15 for ; Sun, 5 Mar 2000 23:16:23 -0800 (PST) (envelope-from flatline@area51.v-wave.com) Received: (qmail 34770 invoked by uid 1001); 6 Mar 2000 07:17:07 -0000 Date: Mon, 6 Mar 2000 00:17:06 -0700 From: Chris Wasser To: current@FreeBSD.ORG Subject: oddness in -current Message-ID: <20000306001706.A32145@area51.v-wave.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just watching a buildworld happen when I noticed (specifically in gcc, and a few other places) the following warning several times: warning: mktemp() possibly used unsafely; consider using mkstemp() I'm not sure if it's a big deal or not, but in the interests of satisfying my own interests, I thought I would mention it. If this has been covered already in this list, then please disregard. Next time I'll capture the entire build process to a file. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 0:17:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 341AF37BC65; Mon, 6 Mar 2000 00:17:36 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id DAA359312; Mon, 6 Mar 2000 03:17:33 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200003060423.XAA01323@server.baldwin.cx> References: <200003060423.XAA01323@server.baldwin.cx> Date: Mon, 6 Mar 2000 03:17:51 -0500 To: John Baldwin , Kris Kennaway From: Garance A Drosihn Subject: Re: ssh strangeness in -current... Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:23 PM -0500 3/5/00, John Baldwin wrote: >On 06-Mar-00 Kris Kennaway wrote: > > On Mon, 6 Mar 2000, Oliver Fromme wrote: > > > >> the ports (yeah, stupid me), to no avail. It complained about some > >> RSA library missing. > > > > Did you read the error message? Perhaps you should. Perhaps reporting > > it here would help someone to actually fix your problem instead > > of having to guess. > >I think you've kind of missed the point though, Kris. How many other >people are going to upgrade only to find that their previously working >system is now broken. We should at least mention this in UPDATING >so people have a ghost of a chance. My guess is that when he said "help someone to actually fix your problem", his desire was to fix it so people would NOT have a problem updating. From the activity on the current list, it's clear that he has been putting in a lot of hours trying to fix all the various odds and ends which broke when this went in. (and yes, there have been a lot of loose ends, but people have definitely been working on them). This must have been the most discussed topic on the current mailing list for the past two weeks, and I (for one) appreciate all the work people have been doing to get openssh as part of the base system. It's been a bit bumpy, but it is (IMO) a worthwhile addition for 4.0-release. I would have been happy to vote for openssh as part of the base system, even though that means a delay in 4.0-release. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 0:23:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 0910337BCC3 for ; Mon, 6 Mar 2000 00:23:27 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id DAA363620; Mon, 6 Mar 2000 03:23:23 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000306001706.A32145@area51.v-wave.com> References: <20000306001706.A32145@area51.v-wave.com> Date: Mon, 6 Mar 2000 03:23:44 -0500 To: Chris Wasser , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: oddness in -current Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:17 AM -0700 3/6/00, Chris Wasser wrote: >I was just watching a buildworld happen when I noticed (specifically >in gcc, and a few other places) the following warning several times: > >warning: mktemp() possibly used unsafely; consider using mkstemp() > >I'm not sure if it's a big deal or not, but in the interests of >satisfying my own interests, I thought I would mention it. If this >has been covered already in this list, then please disregard. Next >time I'll capture the entire build process to a file. This probably has not been discussed a lot on current, but the freebsd-audit group has been trying to track down and change all uses of mktemp which might lead to any kind of security problem. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 0:34:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 9044437BCBD for ; Mon, 6 Mar 2000 00:34:33 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 14EE54CE09; Mon, 6 Mar 2000 03:34:29 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id DAA05361; Mon, 6 Mar 2000 03:34:28 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id AAA18027; Mon, 6 Mar 2000 00:33:57 -0800 (PST) Message-Id: <200003060833.AAA18027@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: imp@village.org Subject: Re: openssh question Cc: current@freebsd.org Date: Mon, 6 Mar 2000 00:33:56 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Second, how does one specify options on the command line? In ssh >1.2.x, I say ssh -o ForwardX11=yes, but that doesn't work in OpenSSH. >Bug or feature? Browsing the source, it looks like "ssh -o 'ForwardX11 yes'" should work. Both ssh and openssh define -o as: -o 'option' Can be used to give options in the format used in the config file. This is useful for specifying options for which there is no separate command-line flag. The option has the same format as a line in the configuration file. However, ssh allows lines in the configuration file to be of the form "keyword = arguments" but openssh only allows "keyword arguments". So you're really running into a difference in configuration file parsing. Ugh =) Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 0:56:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id EE14437BCBD for ; Mon, 6 Mar 2000 00:56:48 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id UAA48815 for current@freebsd.org; Sun, 5 Mar 2000 20:24:35 GMT (envelope-from nik) Date: Sun, 5 Mar 2000 20:24:35 +0000 From: Nik Clayton To: current@freebsd.org Subject: Alternative way to do -stable to -current upgrade Message-ID: <20000305202435.A39101@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, I had an abortive -stable to -current upgrade late last week, despite following the directions in UPGRADING, the two kernels I built (one custom, one GENERIC) both froze on me during the reboot process. I'm a little wary of doing it again like that, because it does take some time to fix. So I had an alternative idea. How about doing the following: 1. Download -current boot.flp, mfsroot.flp, fixit.flp, and write to floppies 2. cd /usr/src && make buildworld 3. Reboot from boot/mfsroot.flp 4. When prompted, use the fixit floppy to get a shell 5. Mount all the fixed disk partitions, and then (assuming they're all mounted under /mnt/root) cd /mnt/root/usr/src && make DESTDIR=/mnt/root 6. Mergemaster 7. Build and install a new kernel This has the added advantage that if there's something in your system that was OK in -stable, but doesn't work in -current, you're going to find out about it before you've done an installworld, and before you've overwritten a working -stable /kernel, because boot.flp will fail to work. The only problem is that mergemaster assumes it's merging in to /etc, when that wouldn't be the case here -- mergemaster would need another config option ($DEST_ETC ?) to specify where to install to. Can anyone see anything there that's likely not to work? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 1:19:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 363EB37BCCE; Mon, 6 Mar 2000 01:19:50 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id CAA53194; Mon, 6 Mar 2000 02:19:47 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id CAA57690; Mon, 6 Mar 2000 02:19:40 -0700 (MST) Message-Id: <200003060919.CAA57690@harmony.village.org> To: Garance A Drosihn Subject: Re: ssh strangeness in -current... Cc: John Baldwin , Kris Kennaway , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Mar 2000 03:17:51 EST." References: <200003060423.XAA01323@server.baldwin.cx> Date: Mon, 06 Mar 2000 02:19:40 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Garance A Drosihn writes: : My guess is that when he said "help someone to actually fix your problem", : his desire was to fix it so people would NOT have a problem updating. I've added a blurb to UPDATING. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 1:20:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8087B37BCE4 for ; Mon, 6 Mar 2000 01:20:44 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id CAA53206; Mon, 6 Mar 2000 02:20:43 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id CAA57713; Mon, 6 Mar 2000 02:20:36 -0700 (MST) Message-Id: <200003060920.CAA57713@harmony.village.org> To: Bill Fenner Subject: Re: openssh question Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Mar 2000 00:33:56 PST." <200003060833.AAA18027@windsor.research.att.com> References: <200003060833.AAA18027@windsor.research.att.com> Date: Mon, 06 Mar 2000 02:20:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks Bill. I forgot that old versions of ssh were this picky... OpenSSH inherited this from the 1.2.12 version it started from. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 1:37:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (dhcp137.iafrica.com [196.31.1.137]) by hub.freebsd.org (Postfix) with ESMTP id D172737BCDE; Mon, 6 Mar 2000 01:37:22 -0800 (PST) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id LAA43455; Mon, 6 Mar 2000 11:37:20 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200003060937.LAA43455@grimreaper.grondar.za> To: Kris Kennaway Cc: Brian Dean , bwoods2@uswest.net, markm@freebsd.org, freebsd-current@freebsd.org Subject: Re: Make world error..... References: In-Reply-To: ; from Kris Kennaway "Sun, 05 Mar 2000 14:34:29 PST." Date: Mon, 06 Mar 2000 11:37:20 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 5 Mar 2000, Brian Dean wrote: > > > The perl script h2ph does not exit immediately on des.h, it sets it's > > $Exit value to 1, but continues processing. If the original poster > > would check further back in his log file, he'll see: > > Ah, okay. There might be an ordering problem with the des.h symlink being > created before the openssl/des.h file which it points to. Any ideas, > Mark? Don't shortcut make world. The files are correctly added there, and not if you try to "get clever" :-). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 1:39:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (dhcp137.iafrica.com [196.31.1.137]) by hub.freebsd.org (Postfix) with ESMTP id 89EB337BCE5; Mon, 6 Mar 2000 01:39:45 -0800 (PST) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id LAA43479; Mon, 6 Mar 2000 11:39:44 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200003060939.LAA43479@grimreaper.grondar.za> To: Kris Kennaway Cc: current@freebsd.org, markm@freebsd.org, jkh@freebsd.org Subject: Re: NO_OPENSSL world fixes References: In-Reply-To: ; from Kris Kennaway "Sun, 05 Mar 2000 16:59:07 PST." Date: Mon, 06 Mar 2000 11:39:44 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Okay, these patches were sufficient to allow me to build world with > NO_OPENSSL defined. I'd like to commit these ASAP. No objections. > After the release, I want to look at condensing the mass of > .if defined(...) options we have, at least with respect to crypto. At the > moment we have to test everywhere for things like > > .if !defined(NOCRYPT) && !defined(NOSECURE) && !defined(NO_OPENSSL) && > defined(MAKE_KERBEROS4) > > when all we really want to know is whether or not OpenSSL is available to > be linked with. > > In addition to normalizing all of the NO* options to NO_* (or other way > round if I get shouted down :), they should obey the correct covering > hierarchy automatically so we don't have to explicitly test for all the > covering options in each instance. For example, NO_CRYPT should imply > NO_OPENSSL, which in turn implies NO_OPENSSH, etc. NOSECURE should be > removed since it's nonfunctional. NO_CRYPT or NO_OPENSSL should conflict > with MAKE_KERBEROS?, etc. Right. Sounds good! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 2:23:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id A336E37BD10 for ; Mon, 6 Mar 2000 02:23:09 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id LAA47996; Mon, 6 Mar 2000 11:22:54 +0100 (CET) (envelope-from asmodai) Date: Mon, 6 Mar 2000 11:22:54 +0100 From: Jeroen Ruigrok van der Werven To: Garance A Drosihn Cc: Chris Wasser , current@FreeBSD.ORG Subject: Re: oddness in -current Message-ID: <20000306112253.F46955@lucifer.bart.nl> References: <20000306001706.A32145@area51.v-wave.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from drosih@rpi.edu on Mon, Mar 06, 2000 at 03:23:44AM -0500 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000306 09:25], Garance A Drosihn (drosih@rpi.edu) wrote: >At 12:17 AM -0700 3/6/00, Chris Wasser wrote: >>I was just watching a buildworld happen when I noticed (specifically >>in gcc, and a few other places) the following warning several times: >> >>warning: mktemp() possibly used unsafely; consider using mkstemp() >> >>I'm not sure if it's a big deal or not, but in the interests of >>satisfying my own interests, I thought I would mention it. If this >>has been covered already in this list, then please disregard. Next >>time I'll capture the entire build process to a file. > >This probably has not been discussed a lot on current, but the >freebsd-audit group has been trying to track down and change >all uses of mktemp which might lead to any kind of security >problem. And in this case those are probably warnings issued by programs from the contrib directory. Possible suspects: cvs, groff, etc. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl Tel: +31 - (0) 10 - 240 39 70 http://www.via-net-works.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 2:29:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from NOC.cs.uu.nl (magic.cs.uu.nl [131.211.80.22]) by hub.freebsd.org (Postfix) with ESMTP id 18F1037BD09 for ; Mon, 6 Mar 2000 02:29:41 -0800 (PST) (envelope-from edwin@cs.uu.nl) Received: by NOC.cs.uu.nl (Postfix, from userid 164) id 9EF9C3E8C2; Mon, 6 Mar 2000 11:29:39 +0100 (MET) Date: Mon, 6 Mar 2000 11:29:39 +0100 From: Edwin Kremer To: freebsd-current@FreeBSD.ORG Subject: Re: openssh question Message-ID: <20000306112939.A24401@cs.uu.nl> References: <200003060833.AAA18027@windsor.research.att.com> <200003060920.CAA57713@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.7i In-Reply-To: <200003060920.CAA57713@harmony.village.org>; from imp@village.org on Mon, Mar 06, 2000 at 02:20:35AM -0700 X-Organization: Department of Computer Science, Utrecht University X-Phone: +31-30-2534104 (telefax: +31-30-2513791) X-PGP-DSS-Key: http://horowitz.surfnet.nl:11371/pks/lookup?op=get&search=0x33E1E549 X-PGP-RSA-Key: http://horowitz.surfnet.nl:11371/pks/lookup?op=get&search=0xAD4B1845 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 02:20:35AM -0700, Warner Losh wrote: : OpenSSH inherited this from the 1.2.12 version it started from. On a side note: last week, Tatu Ylonen, principal author of SSH, posted a message on the SSH mailing-list (in the thread about the new SSH2 license) saying that: " OpenSSH is based on my version from back in 1995 or 1996. The OpenSSH " folks have fixed many of the (security) bugs in that version, but not " all of them when I last checked. Some of the problems in SSH1 are " very fundamental. " " I do not recommend use of OpenSSH (or SSH1 generally, for that matter). There hasn't been much followup on this. Anybody here who cares to comment on this? What issues are relevant here and how bad is it? Best regards, -- Edwin H. Kremer, senior systems- and network administrator. Dept. of Computer Science, Utrecht University, The Netherlands [WHOIS: ehk3] -------------------- http://www.cs.uu.nl/people/edwin/ ----------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 2:37:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with SMTP id 7AAB537BD09 for ; Mon, 6 Mar 2000 02:37:15 -0800 (PST) (envelope-from me@camtech.net.au) Received: from dialup-ad-13-47.camtech.net.au ([203.55.243.175]) by camtech.net.au ; Mon, 06 Mar 2000 21:07:11 +1030 Date: Mon, 6 Mar 2000 21:08:43 +1030 (CST) From: Matthew Sean Thyer X-Sender: me@dx4.my-unregistered-domain.com Reply-To: thyerm@camtech.net.au To: Dan Papasian Cc: Arun Sharma , freebsd-current@FreeBSD.ORG Subject: Re: current lockups In-Reply-To: <20000305104515.A17749@moe.c705742-a.htfdw1.ct.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll second this email... My computer had been stable all winter (with setiathome runnning full time) but suddenly come the Australian summer it started freezing. Not panicing, just totally freezing under load. I could reproduce it by trying to build the whole of KDE and each time it was a freeze, never a panic. Windows 98 was freezing too but I didn't think that was abormal ;/ It turned out to be heat related as the machine is now stable after I installed a case fan (before I only had the power supply fan and CPU fan). I see that the internal case temperature still gets up to about 50 or 51 degrees celcius whereas it was getting to 52 degrees before. Note that I AM overclocking a Celeron 300a to 450 MHz by running with a 100 MHz FSB instead of 66 MHz so I suppose I shouldn't be surprised at the need for better cooling. As I'd prefer better CPU cooling to the case fan on the grounds of noise, can people recommend good CPU fans (over the standard Intel retail version Celeron 300a fan) ? How about these Peltier (sp ?) cooling devices I have heard about ? On Sun, 5 Mar 2000, Dan Papasian wrote: > 1. Is your computer overclocked? > > 2. Is the computer totally frozen? (i.e. scroll lock doesn't turn the light on) > > 3. Does similar load crash the box as well? (try make -j2 world) > > 4. Does it freeze in the same spot? > > 5. Is the computer not responding to pings? > > If you've answered yes to a good amount of these questions, there is a good > chance that your processor(s) are overheating. Try improving the airflow to the > case (But using a household fan isn't recommended due to EMI) > > -Dan Papasian > > > On Sat, Mar 04, 2000 at 11:50:10PM -0800, Arun Sharma wrote: > > Compiling Mozilla with make -j 2 got -current to lock up, twice in > > succession. I'm running a fairly recent snapshot (a week or two old) > > on a Dual celeron box (BP6) with UDMA66 enabled. > > > > The kernel had DDB enabled. I was running X, but I didn't see any > > signs of the kernel attempting to get into the debugger. > > > > Has this been fixed ? Is anyone interested in investigating ? > > I'll post more info if I find anything. > > > > -Arun > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 2:38:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 8B32B37BD8E for ; Mon, 6 Mar 2000 02:37:55 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id MAA00366 for freebsd-current@freebsd.org; Mon, 6 Mar 2000 12:37:15 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200003061037.MAA00366@zibbi.mikom.csir.co.za> Subject: ipv6 and rc.conf questions To: freebsd-current@freebsd.org Date: Mon, 6 Mar 2000 12:37:15 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have been playing with IPv6 on a few machines and I must say that it is very easy to get the basic IPv6 configuration on the "endpoints" ie. machines with just a ethernet connection. Just a line with 'ipv6_enable="YES"' /etc/rc.conf and it is done. But how do you configure an IPv6 in IPv4 tunnel in rc.conf? I can do it on the commandline, I'm just trying to figure out how to do it in rc.conf. I can get the IPv4 part configured with something like this: gif_interfaces="gif0" gifconfig_gif0="146.64.84.9 146.64.8.68" But how/where do you configure the IPv6 part of the tunnel? Do you have to put it in the network_interfaces= section where the normal IPv4 configuration is done? Another question, how do you add a default IPv6 route in rc.conf? There is an ipv6_default_interface= variable, but from the comments it looks like it is only meant for link local multicast addresses. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 2:53:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id E524237BD3B for ; Mon, 6 Mar 2000 02:53:16 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 5079ECB6A; Mon, 6 Mar 2000 11:53:07 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Mon, 6 Mar 2000 11:15:01 +0100 To: Kris Kennaway , freebsd-current@FreeBSD.ORG From: Brad Knowles Subject: Re: ssh strangeness in -current... Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:06 PM -0800 2000/3/5, Kris Kennaway wrote: > Enough people wanted it in the base system - in fact, when the question > was asked about importing it, I don't recall any objections - certainly it > was not a significant opposition. In fact, there are a lot of us that explicitly *did* want it in the base system, and were very glad to see it go in. I got the chance this weekend to personally thank Jordan for making the tough decision to delay the release of 4.0 in order to get it in, and I'd like to now take this chance to publicly thank Kris and the rest of the guys for all their hard work in this area. Well done! Now, about some of those bugs.... ;-) -- These are my opinions and should not be taken as official Skynet policy ========================================================================= Brad Knowles, 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 for details. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 3:18:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 3400337BC51 for ; Mon, 6 Mar 2000 03:18:11 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id UAA28558; Mon, 6 Mar 2000 20:18:08 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id UAA21073; Mon, 6 Mar 2000 20:18:06 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id UAA22982; Mon, 6 Mar 2000 20:18:06 +0900 (JST) To: jhay@mikom.csir.co.za Cc: freebsd-current@FreeBSD.ORG Subject: Re: ipv6 and rc.conf questions In-Reply-To: <200003061037.MAA00366@zibbi.mikom.csir.co.za> References: <200003061037.MAA00366@zibbi.mikom.csir.co.za> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000306201859K.shin@nd.net.fujitsu.co.jp> Date: Mon, 06 Mar 2000 20:18:59 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 91 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Hi, > > I have been playing with IPv6 on a few machines and I must say that it > is very easy to get the basic IPv6 configuration on the "endpoints" ie. > machines with just a ethernet connection. Just a line with > 'ipv6_enable="YES"' /etc/rc.conf and it is done. I'm glad to know that is working. :-) > But how do you configure an IPv6 in IPv4 tunnel in rc.conf? I can do it > on the commandline, I'm just trying to figure out how to do it in rc.conf. > I can get the IPv4 part configured with something like this: > > gif_interfaces="gif0" > gifconfig_gif0="146.64.84.9 146.64.8.68" > > But how/where do you configure the IPv6 part of the tunnel? Do you have to > put it in the network_interfaces= section where the normal IPv4 > configuration is done? After gif tunnel is configured by the above setup, you can just use ifconfig to assigne any IPv4 and/or IPv6 addresses to the gif p2p link. Such as, ifconfig gif0 10.0.0.1 10.0.0.2 netmask 255.255.255.0 ifconfig gif0 inett6 fec0:0:0:1000::1 fec0:0:0:1000::2 prefixlen 64 alias However, an IPv6 machine already has each IPv6 link local address on all of its interfaces by default, so it is found that no more additional IPv6 addr is necessary on p2p links. When you ping6 on a gif tunnel, you will see replies from IPv6 link local addresses of local machin and remote machine like below. (if the tunnel is setup correctly on each side.) hoge% ping6 ff02::1%gif0 PING6(56=40+8+8 bytes) fe80::200:eff:fe2e:dfe1 --> ff02::1 16 bytes from fe80::200:eff:fe2e:dfe1%lo0, icmp_seq=0 hlim=64 time=5.2 ms 16 bytes from fe80::200:e2ff:fe0d:bd18%gif0, icmp_seq=0 hlim=64 time=22.185 ms(DUP!) 16 bytes from fe80::200:eff:fe2e:dfe1%lo0, icmp_seq=1 hlim=64 time=8.127 ms 16 bytes from fe80::200:e2ff:fe0d:bd18%gif0, icmp_seq=1 hlim=64 time=33.705 ms(DUP!) ^C --- ff02::1%gif0 ping6 statistics --- 2 packets transmitted, 2 packets received, +2 duplicates, 0% packet loss round-trip min/avg/max = 5.2/17.304/33.705 ms If you need to reach other addrs over the tunnel, then, -just assigne IPv6 route to the gif tunnel using "route add -inet6 xxxx" command. or -enable following lines on each end of machines, and reboot them. ipv6_gateway_enable="YES" ipv6_router_enable="YES" If you did update and make world recently, please check /usr/share/examples/IPv6/USAGE. There will be more detailed info. A handbook chapter version is now under preparation. > Another question, how do you add a default IPv6 route in rc.conf? There is > an ipv6_default_interface= variable, but from the comments it looks like > it is only meant for link local multicast addresses. In IPv6, a host's default router is automatically registered by receiving Router Advertisement messages from routers. To let routers send Router Advertisement, you need to invoke rtadvd on your router. It will be available by enabling the following config line on the router. rtadvd_enable="YES" If you want to enable it after the reboot, then please invoke rtadvd as root, and give it list of interface names to which you want Router Advertisement messages to be sent over. Such as, rtadvd ed0 ed1 ep0 ep1 Wmmm, should rtadvd always be invoked when 'ipv6_gateway_enable="YES" ? Cheers, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 3:46: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 6153237BD3B; Mon, 6 Mar 2000 03:46:04 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id GAA01954; Mon, 6 Mar 2000 06:45:47 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200003061145.GAA01954@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200003060919.CAA57690@harmony.village.org> Date: Mon, 06 Mar 2000 06:45:47 -0500 (EST) From: John Baldwin To: Warner Losh Subject: Re: ssh strangeness in -current... Cc: freebsd-current@FreeBSD.org, Kris Kennaway , Garance A Drosihn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Mar-00 Warner Losh wrote: > In message Garance A Drosihn writes: >: My guess is that when he said "help someone to actually fix your problem", >: his desire was to fix it so people would NOT have a problem updating. > > I've added a blurb to UPDATING. > > Warner Thanks, Warner. -- John Baldwin -- 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 5:58:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id 46CD637BD6F for ; Mon, 6 Mar 2000 05:58:04 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id IAA08880; Mon, 6 Mar 2000 08:57:54 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38C3B962.F44E0B92@acm.org> Date: Mon, 06 Mar 2000 08:57:54 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: openssh question References: <200003060618.XAA56131@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > First, how does one enable TIS/SKEY authorization for ssh? It appears > that the frst step would be to add -DSKEY to the Makefile conditional > on something. Are there other steps? > Yes, there are other steps. openssh depends upon functions in the openbsd libskey that we do not have. These functions appear to have been added somewhere between our initial version of skey and openbsd's as they exist in openbsd's initial version, but not ours. The skey support in the openssh port has the exact same problems. That being said, if there is some demand for this, I could merge openbsd's libskey into ours and get the skey authentication working. Jim Bloom bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 6:15: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id 4364A37BDB0; Mon, 6 Mar 2000 06:14:50 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id JAA14600; Mon, 6 Mar 2000 09:14:45 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38C3BD54.D169B3D7@acm.org> Date: Mon, 06 Mar 2000 09:14:44 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: Kris Kennaway , freebsd-current@FreeBSD.ORG, imp@village.org Subject: Re: ssh strangeness in -current... References: <200003060423.XAA01323@server.baldwin.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > > On 06-Mar-00 Kris Kennaway wrote: > > On Mon, 6 Mar 2000, Oliver Fromme wrote: > > > >> the ports (yeah, stupid me), to no avail. It complained about some > >> RSA library missing. > > > > Did you read the error message? Perhaps you should. Perhaps reporting it > > here would help someone to actually fix your problem instead of having to > > guess. > > I think you've kind of missed the point though, Kris. How many other people > are going to upgrade only to find that their previously working system is > now broken. We should at least mention this in UPDATING so people have a > ghost of a chance. > One possible source of breakage is not bringing over the existing server key. The key will need to be moved from /usr/local/etc to /etc/ssh. Did Warner include this with his changes to UPDATING about openssh in the base system (which I haven't seen yet). Jim Bloom bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 6:47:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 4B38237BCB1 for ; Mon, 6 Mar 2000 06:47:24 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p22-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.151]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id XAA08505; Mon, 6 Mar 2000 23:47:13 +0900 (JST) Message-ID: <38C3C4A9.57282E2C@newsguy.com> Date: Mon, 06 Mar 2000 23:46:02 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Joseph Jacobson Cc: freebsd-current@FreeBSD.ORG Subject: Re: things I noticed w/ 4.0 References: <200003040309.WAA03110@home.my.domain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joseph Jacobson wrote: > > VESA is compiled into the kernel. I don't have a /boot/loader.conf > file. Is there any other way for the VESA module to be loaded at boot, > before /etc/rc runs? Also, none of the vidcontrol VESA modes work for > me. (All this isn't a big deal, but the error message is weird). Nope. Might be what Mike said. Nowadays, an increasing number of video cards aren't VESA, or only do VESA with software drivers. > I didn't express myself very well in the above paragraph. :) Here is the > behavior exhibited by my box with apm. When apm is enabled in the bios, > and 'apm -e enable' is run, 'halt -p' causes the system to reboot. 'zzz' > causes the system to hang (unresponsive to keyboard and mouse input). > (I didn't try all permutations of my apm bios settings with 'zzz' to see > if I can work around the hang, but I don't think that's the cause). > Pushing my power button during the hang state caused the system to reboot. > Also, when apm is enabled, after a regular 'halt' or 'shutdown', pushing > the power button causes the machine to reset, not turn off. Might be a apm option thingy. I haven't tweaked this in quite a while, but... in the past, by default APM 2.0 was _not_ activated, because some older stuff would crash. The default in the kernel had some flags or missed some flags that enabled it. Look up GENERIC/LINT, and check for those flags. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 7: 7:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 28B5837BD1B for ; Mon, 6 Mar 2000 07:07:38 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id QAA19416 for ; Mon, 6 Mar 2000 16:07:20 +0100 (MET) Message-ID: <38C3C9A6.28E3A38@we.lc.ehu.es> Date: Mon, 06 Mar 2000 16:07:18 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: IPv6: can a link-site (or global) address be configured in rc.conf? Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Now that I have several machines running FreeBSD 4.0, I started to play with IPv6. It's fun! I have plans to set up a v6-over-v4 tunnel and connect to the 6Bone. I read /usr/share/examples/IPv6/USAGE, /usr/share/doc/IPv6/IMPLEMENTATION and some documents at the KAME web site. However, I still have to figure out how to assign a not-link-local address (i.e., a site or global address) to the [unique] Ethernet interface of each host in an automatic manner (from /etc/rc.conf). After reading /etc/rc.network6 I concluded that no addresses apart from the link-local ones are assigned to the interfaces. I am using ifconfig manually to do this (BTW, I found that there is no need to specify "alias"). I am new to IPv6, so maybe I am asking for something with no sense... My congratulations to the IPv6 team. Great job! TIA, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 7:40:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadows.aeon.net (shadows.aeon.net [195.197.32.30]) by hub.freebsd.org (Postfix) with ESMTP id 1695837BDB2 for ; Mon, 6 Mar 2000 07:40:40 -0800 (PST) (envelope-from bsdcur@shadows.aeon.net) Received: (from bsdcur@localhost) by shadows.aeon.net (8.9.3/8.8.3) id RAA97683 for current@freebsd.org; Mon, 6 Mar 2000 17:43:45 +0200 (EET) From: mika ruohotie Message-Id: <200003061543.RAA97683@shadows.aeon.net> Subject: about releng3.freebsd.org To: current@freebsd.org Date: Mon, 6 Mar 2000 17:43:45 +0200 (EET) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG just a thought, would it be possible to have ls-lR and ls-lR.gz over there? it'd make it easier/possible for me to make proper mirror site... mickey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 7:45:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 0527337BD22 for ; Mon, 6 Mar 2000 07:45:46 -0800 (PST) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.10.0.Beta12/8.10.0.Beta12) id e26FhxC20024; Mon, 6 Mar 2000 07:43:59 -0800 (PST) Message-Id: <200003061543.e26FhxC20024@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.1-cvs 10/15/1999 To: "Jose M. Alcaide" Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? In-Reply-To: <38C3C9A6.28E3A38@we.lc.ehu.es> References: <38C3C9A6.28E3A38@we.lc.ehu.es> Comments: In-reply-to "Jose M. Alcaide" message dated "Mon, 06 Mar 2000 16:07:18 +0100." From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_614585453P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 06 Mar 2000 07:43:59 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_614585453P Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit If memory serves me right, "Jose M. Alcaide" wrote: > Now that I have several machines running FreeBSD 4.0, I started to > play with IPv6. It's fun! I have plans to set up a v6-over-v4 tunnel > and connect to the 6Bone. > > I read /usr/share/examples/IPv6/USAGE, /usr/share/doc/IPv6/IMPLEMENTATION > and some documents at the KAME web site. However, I still have to figure out > how to assign a not-link-local address (i.e., a site or global address) to > the [unique] Ethernet interface of each host in an automatic manner (from > /etc/rc.conf). After reading /etc/rc.network6 I concluded that no addresses > apart from the link-local ones are assigned to the interfaces. I am using > ifconfig manually to do this (BTW, I found that there is no need to specify > "alias"). /etc/rc.network6 assumes that you'll get your non-link-local address(es) from your router(s) using rtsol(8). The router, in turn, needs to be running something like rtadvd(8). > I am new to IPv6, so maybe I am asking for something with no > sense... IPv6 autoconfiguration is very roughly analogous to using DHCP in the IPv4 world. (It's not exactly the same though. In fact, there exists a DHCP for IPv6.) Hope this helps, Bruce. --==_Exmh_614585453P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: BF+zbfruw8DoZ1OTG6AWPi9tldTGx3M6 iQA/AwUBOMPSP9jKMXFboFLDEQLAQQCgyuSF4pTuzPceTJBt5kPYxNBYELIAniq3 37s0EY49eL/V4J+wTeOCiIaG =saGo -----END PGP SIGNATURE----- --==_Exmh_614585453P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 7:50:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 9E30837B6D7 for ; Mon, 6 Mar 2000 07:50:49 -0800 (PST) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.10.0.Beta12/8.10.0.Beta12) id e26FoLS20060; Mon, 6 Mar 2000 07:50:21 -0800 (PST) Message-Id: <200003061550.e26FoLS20060@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.1-cvs 10/15/1999 To: Yoshinobu Inoue Cc: jhay@mikom.csir.co.za, freebsd-current@FreeBSD.ORG Subject: Re: ipv6 and rc.conf questions In-Reply-To: <20000306201859K.shin@nd.net.fujitsu.co.jp> References: <200003061037.MAA00366@zibbi.mikom.csir.co.za> <20000306201859K.shin@nd.net.fujitsu.co.jp> Comments: In-reply-to Yoshinobu Inoue message dated "Mon, 06 Mar 2000 20:18:59 +0900." From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_627758591P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 06 Mar 2000 07:50:21 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_627758591P Content-Type: text/plain; charset=us-ascii If memory serves me right, Yoshinobu Inoue wrote: > If you did update and make world recently, please check > /usr/share/examples/IPv6/USAGE. There will be more detailed info. > A handbook chapter version is now under preparation. That's good to hear. I was thinking about this a little bit, but I'm glad someone (presumably more qualified than me) is doing this. > Wmmm, should rtadvd always be invoked when 'ipv6_gateway_enable="YES" ? Hmmm...two things come to mind. 1) What happens if there are two routers running rtadvd on a single subnet? 2) Are there environments in which a netadmin might not want to use router advertisements? I have this fuzzy feeling that always invoking rtadvd on routers might not be a good idea, but that perhaps making it the default might be good (right now, rtadvd is turned off by default). Bruce. --==_Exmh_627758591P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: X3Z1+efNLXKJhLA+7IbrsEv91hYTvxCo iQA/AwUBOMPTvdjKMXFboFLDEQKhigCfYP+GTZ+Mp2Dak18KP7pVddyR57oAnj++ KHdQG99t3yhFXQt7vbqKvDWx =nvvQ -----END PGP SIGNATURE----- --==_Exmh_627758591P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 8:28:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 9D50437BC02 for ; Mon, 6 Mar 2000 08:28:39 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id AD6AA4CE16; Mon, 6 Mar 2000 11:28:34 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id LAA01913; Mon, 6 Mar 2000 11:28:33 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id IAA19733; Mon, 6 Mar 2000 08:28:00 -0800 (PST) Message-Id: <200003061628.IAA19733@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: jose@we.lc.ehu.es Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? Cc: freebsd-current@freebsd.org Date: Mon, 6 Mar 2000 08:28:00 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce is right that machines expect to learn their prefixes from their local router; however if you're just playing around you might want to set it yourself. The easiest way I've found to do this is to say that this machine is a router: # sysctl -w net.inet6.ip6.forwarding=1 net.inet6.ip6.forwarding: 0 -> 1 and then run "prefix" to set a site-local prefix: # prefix dc0 fec0:0:0:1:: # ifconfig dc0 dc0: flags=8843 mtu 1500 inet6 fe80::2a0:ccff:fe36:7410%dc0 prefixlen 64 scopeid 0x1 inet6 fec0::1:2a0:ccff:fe36:7410 prefixlen 64 Of course, if you have global address space too you can assign that prefix too. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 8:32:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from rattlehead.accs.wayne.edu (rattlehead.accs.wayne.edu [141.217.25.92]) by hub.freebsd.org (Postfix) with ESMTP id B89D737BB5E for ; Mon, 6 Mar 2000 08:32:44 -0800 (PST) (envelope-from ab3189@wayne.edu) Received: from [141.217.25.93] (roadwarrior.accs.wayne.edu [141.217.25.93]) by rattlehead.accs.wayne.edu (8.9.3/8.9.3) with ESMTP id KAA51978 for ; Mon, 6 Mar 2000 10:30:03 -0500 (EST) (envelope-from ab3189@wayne.edu) User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630) Date: Mon, 06 Mar 2000 11:32:18 -0500 Subject: subscribe From: "Charles A. Plater" To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe -- Charles A. Plater | "You think it's a conspiracy by the networks to put Systems Analyst | bad shows on TV. But the shows are bad because that's Wayne State Univ. | what people want. It's not like Windows users don't ab3189@wayne.edu | have any power; I think they are happy with Windows, http://www.wayne.edu | and that's an incredibly depressing thought...." +1 (313) 577 4730 | -- Steve Jobs [NeXT] NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 9: 1:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from astralblue.com (adsl-209-76-108-39.dsl.snfc21.pacbell.net [209.76.108.39]) by hub.freebsd.org (Postfix) with ESMTP id DD5EC37BDF0 for ; Mon, 6 Mar 2000 09:01:45 -0800 (PST) (envelope-from ab@astralblue.com) Received: from localhost (ab@localhost) by astralblue.com (8.9.3/8.9.3) with ESMTP id JAA53049; Mon, 6 Mar 2000 09:00:45 -0800 (PST) (envelope-from ab@astralblue.com) Date: Mon, 6 Mar 2000 09:00:44 -0800 (PST) From: "Eugene M. Kim" To: Bill Fenner Cc: jose@we.lc.ehu.es, FreeBSD-current Mailing List , 6bone@isi.edu Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? In-Reply-To: <200003061628.IAA19733@windsor.research.att.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Cc'ed to the 6BONE mailing list in the hope that someone there could answer my question as well) Speaking of the address allocation, is there a way for an individual to get a non-local address space (so that all of my machines can get an unique IPv6 address)? I've read through the 6BONE website, and it seems to me that I somehow have to `qualify' in order to get one. (And the fact that I just need <10 addresses makes me feel guilty; AFAIK the minimum allocation unit is 2^64-address block :-p.) Thank you in advance, Eugene On Mon, 6 Mar 2000, Bill Fenner wrote: | Bruce is right that machines expect to learn their prefixes from their | local router; however if you're just playing around you might want to | set it yourself. The easiest way I've found to do this is to say that | this machine is a router: | | # sysctl -w net.inet6.ip6.forwarding=1 | net.inet6.ip6.forwarding: 0 -> 1 | | and then run "prefix" to set a site-local prefix: | | # prefix dc0 fec0:0:0:1:: | # ifconfig dc0 | dc0: flags=8843 mtu 1500 | inet6 fe80::2a0:ccff:fe36:7410%dc0 prefixlen 64 scopeid 0x1 | inet6 fec0::1:2a0:ccff:fe36:7410 prefixlen 64 | | Of course, if you have global address space too you can assign that prefix | too. | | Bill -- Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 9: 8:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 008C237BE31 for ; Mon, 6 Mar 2000 09:08:47 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 23164 invoked from network); 6 Mar 2000 17:08:45 -0000 Received: from lcm212.cvzoom.net (HELO cvzoom.net) (208.230.69.212) by ns.cvzoom.net with SMTP; 6 Mar 2000 17:08:45 -0000 Message-ID: <38C3E603.95B78E66@cvzoom.net> Date: Mon, 06 Mar 2000 12:08:19 -0500 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: mika ruohotie Cc: current@freebsd.org Subject: Re: about releng3.freebsd.org References: <200003061543.RAA97683@shadows.aeon.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mika ruohotie wrote: > > just a thought, would it be possible to have ls-lR and ls-lR.gz > over there? You could just ftp into the server, and at the root directory, do: ls -lR ls-lR It will ask you if you want to save to local file ls-lR. Press y. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 9:12:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id BD70537BE3F; Mon, 6 Mar 2000 09:12:21 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id MAA40849; Mon, 6 Mar 2000 12:12:19 -0500 (EST) Message-Id: <200003061712.MAA40849@cs.rpi.edu> To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Cc: crossd@cs.rpi.edu Subject: rpc.lockd and xdr. Date: Mon, 06 Mar 2000 12:12:19 -0500 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Version 2 of the lock manager is ready to be released. Amitha says that it passes all of the tests in the suite posted by Drew (thanks Drew). A noteable exception to this is on SGI where some lock requests are never even received from the remote host. Also DOS sharing is not yet complete. On a side note, it would appear that at least some of the problems of the previous version were in FreeBSD's XDR library. The xdr_*_int64 routines do not correctly do network byte order conversions. Included below is Amitha's 'hack fix'. ==== My hack fix (this is to /usr/src/lib/libc/xdr/xdr.c) is below. A similar fix needs to be applied to xdr_int64_t. Note that xdr_opaque takes care of swapping the bits in the byte. #define SWAP(a,b,t) t=a;a=b;b=t bool_t my_xdr_u_int64_t(xdrs, uint64_p) register XDR *xdrs; u_int64_t *uint64_p; { u_int64_t x; unsigned char* b= &x; unsigned char t; switch (xdrs->x_op) { case XDR_ENCODE: SWAP(b[0], b[7], t); SWAP(b[1], b[6], t); SWAP(b[2], b[5], t); SWAP(b[3], b[4], t); return (xdr_opaque(xdrs, (caddr_t)uint64_p, sizeof(u_int64_t))) ; case XDR_DECODE: if (!xdr_opaque(xdrs, (caddr_t)&x, sizeof x)) { return (FALSE); } SWAP(b[0], b[7], t); SWAP(b[1], b[6], t); SWAP(b[2], b[5], t); SWAP(b[3], b[4], t); *uint64_p = x; return (TRUE); case XDR_FREE: return (TRUE); } return (FALSE); } ===== -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 9:13:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from shadows.aeon.net (shadows.aeon.net [195.197.32.30]) by hub.freebsd.org (Postfix) with ESMTP id 233D137BE4F for ; Mon, 6 Mar 2000 09:13:14 -0800 (PST) (envelope-from bsdcur@shadows.aeon.net) Received: (from bsdcur@localhost) by shadows.aeon.net (8.9.3/8.8.3) id TAA01011; Mon, 6 Mar 2000 19:16:10 +0200 (EET) From: mika ruohotie Message-Id: <200003061716.TAA01011@shadows.aeon.net> Subject: Re: about releng3.freebsd.org In-Reply-To: <38C3E603.95B78E66@cvzoom.net> from Donn Miller at "Mar 6, 2000 12:08:19 pm" To: dmmiller@cvzoom.net (Donn Miller) Date: Mon, 6 Mar 2000 19:16:10 +0200 (EET) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > just a thought, would it be possible to have ls-lR and ls-lR.gz > > over there? > You could just ftp into the server, and at the root directory, do: > ls -lR ls-lR > It will ask you if you want to save to local file ls-lR. Press y. yeah, i know. but it's not the same. besides, i would expect the site not to let me to do that, it could be used as a DoS-attack. like, most ftp-sites, incliding ftp.freebsd.org, have that file... > - Donn mickey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 9:13:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 29A7737BE65 for ; Mon, 6 Mar 2000 09:13:30 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id SAA20196; Mon, 6 Mar 2000 18:12:42 +0100 (MET) Message-ID: <38C3E709.2031D012@we.lc.ehu.es> Date: Mon, 06 Mar 2000 18:12:41 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Bill Fenner Cc: freebsd-current@freebsd.org, "Bruce A. Mah" Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? References: <200003061628.IAA19733@windsor.research.att.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fenner wrote: > > Bruce is right that machines expect to learn their prefixes from their > local router; however if you're just playing around you might want to > set it yourself. The easiest way I've found to do this is to say that > this machine is a router: > > # sysctl -w net.inet6.ip6.forwarding=1 > net.inet6.ip6.forwarding: 0 -> 1 > > and then run "prefix" to set a site-local prefix: > > # prefix dc0 fec0:0:0:1:: > # ifconfig dc0 > dc0: flags=8843 mtu 1500 > inet6 fe80::2a0:ccff:fe36:7410%dc0 prefixlen 64 scopeid 0x1 > inet6 fec0::1:2a0:ccff:fe36:7410 prefixlen 64 > > Of course, if you have global address space too you can assign that prefix > too. > Thanks Bruce and Bill!. I suspected something like this. I read about IPv6 autoconfiguration, but since I am playing with site-local addresses and I have no IPv6 router [yet], I wondered about how to configure the IPv6 site-local address. Well, my problem is solved, and now I understand IPv6 better. Thanks again, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 9:20:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 50F5C37BE67 for ; Mon, 6 Mar 2000 09:20:38 -0800 (PST) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 6B5C81C57; Mon, 6 Mar 2000 12:20:36 -0500 (EST) Date: Mon, 6 Mar 2000 12:20:36 -0500 From: Bill Fumerola To: Edwin Kremer Cc: freebsd-current@FreeBSD.ORG Subject: Re: openssh question Message-ID: <20000306122036.I25438@jade.chc-chimes.com> References: <200003060833.AAA18027@windsor.research.att.com> <200003060920.CAA57713@harmony.village.org> <20000306112939.A24401@cs.uu.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000306112939.A24401@cs.uu.nl>; from edwin+freebsd-current@cs.uu.nl on Mon, Mar 06, 2000 at 11:29:39AM +0100 X-Operating-System: FreeBSD 3.2-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 11:29:39AM +0100, Edwin Kremer wrote: > " I do not recommend use of OpenSSH (or SSH1 generally, for that matter). > > There hasn't been much followup on this. Anybody here who cares to > comment on this? What issues are relevant here and how bad is it? I'm sure he'd much prefer you use the version that puts money in his pocket. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: billf@chc-chimes.com / billf@FreeBSD.org Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 9:22:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail1.es.net (mail1.es.net [198.128.3.181]) by hub.freebsd.org (Postfix) with SMTP id 5B72D37BE45 for ; Mon, 6 Mar 2000 09:22:55 -0800 (PST) (envelope-from fink@es.net) Received: from truckee.wins.lbl.gov (Truckee) [128.3.9.221] by mail1.es.net with esmtp (Exim 1.81 #2) id 12S1DV-0003ms-00; Mon, 6 Mar 2000 09:22:49 -0800 Message-Id: <4.2.2.20000306091731.02b974d8@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 06 Mar 2000 09:22:45 -0800 To: "Eugene M. Kim" , Bill Fenner From: Bob Fink Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? Cc: jose@we.lc.ehu.es, FreeBSD-current Mailing List , 6bone@ISI.EDU In-Reply-To: References: <200003061628.IAA19733@windsor.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eugene, At 09:00 AM 3/6/2000 -0800, Eugene M. Kim wrote: >(Cc'ed to the 6BONE mailing list in the hope that someone there could >answer my question as well) > >Speaking of the address allocation, is there a way for an individual to >get a non-local address space (so that all of my machines can get an >unique IPv6 address)? I've read through the 6BONE website, and it seems >to me that I somehow have to `qualify' in order to get one. (And the >fact that I just need <10 addresses makes me feel guilty; AFAIK the >minimum allocation unit is 2^64-address block :-p.) IPv6 "sites" own the right-most 80 bits of the 128 bits for local use (you know that, just restating for the wide list you have emailed to). The external routing prefixes are the left-most 48 bits of the 128 and come from your IPv6 service provider... normally. These are currently either in the 3FFE::/16 or 2001::/16 TLA space. The exception is for "6to4" prefixes which are in the 2002::/16 TLA space. See the I-D: Please read, then ask any questions you may have. 6to4 is currently supported, and there are relay routers up and running. Thanks, Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 9:54:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 9A01E37BE72 for ; Mon, 6 Mar 2000 09:54:42 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 7AB8B1CDF; Tue, 7 Mar 2000 01:54:40 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Bill Fumerola Cc: Edwin Kremer , freebsd-current@FreeBSD.ORG Subject: Re: openssh question In-Reply-To: Message from Bill Fumerola of "Mon, 06 Mar 2000 12:20:36 EST." <20000306122036.I25438@jade.chc-chimes.com> Date: Tue, 07 Mar 2000 01:54:40 +0800 From: Peter Wemm Message-Id: <20000306175440.7AB8B1CDF@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > On Mon, Mar 06, 2000 at 11:29:39AM +0100, Edwin Kremer wrote: > > > " I do not recommend use of OpenSSH (or SSH1 generally, for that matter) . > > > > There hasn't been much followup on this. Anybody here who cares to > > comment on this? What issues are relevant here and how bad is it? > > I'm sure he'd much prefer you use the version that puts money in his pocket. To be fair, there *are* weaknesses in the ssh1 protocols. However, as you point out, it doesn't change the fact that Tatu Ylonen has a conflict of interest here. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 9:57:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from oldserver.demon.nl (oldserver.demon.nl [212.238.105.241]) by hub.freebsd.org (Postfix) with ESMTP id 9774137BE72; Mon, 6 Mar 2000 09:57:19 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from localhost (localhost [127.0.0.1]) by oldserver.demon.nl (8.9.3/8.9.3) with ESMTP id SAA19238; Mon, 6 Mar 2000 18:57:17 +0100 (CET) (envelope-from marc@oldserver.demon.nl) Date: Mon, 6 Mar 2000 18:57:16 +0100 (CET) From: Marc Schneiders X-Sender: marc@propro.freebeastie.org To: Kris Kennaway Cc: freebsd-current@freebsd.org Subject: Discussions and "facts" [Was: Re: ssh strangeness in -current...] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Mar 2000, Kris Kennaway wrote: > I'm quite surprised you've missed any discussion of OpenSSH here though, > since it's probably been one of the most discussed topics here for the > past few weeks. > I find it quite a problem that one is supposed to read very long threads of discussions (which one may not be interested in, does not have the time for, or cannot understand) in order to find the information necessary to run and keep up with current without problems. Or to solve any occuring problems. I know current is not for those who do not want to read this list as well as cvs-all. Nevertheless it may be a good thing if plain facts and fixes related to problems were posted as separate messages with a clear subject line and not buried somewhere inside a long thread (war). Or a separate list? The above remarks do not necessarily apply to the OpenSSH discussion on this list. I did not follow it intensely, as I have had no problems with ssh. It is something I wanted to write earlier. The quote at the top was what made me do it now. -- Marc Schneiders *-*-* marc@venster.nl *-*-* http://superputer.com *-*-* *-*-* marc@freebeastie.org *-*-* http://secureasy.com *-*-* propro 2:50pm up 2 days, 16:23, load average: 2.17 2.04 2.01 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 10: 8:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id CB83237BD69 for ; Mon, 6 Mar 2000 10:08:44 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 1717 invoked from network); 6 Mar 2000 18:08:42 -0000 Received: from lcm212.cvzoom.net (HELO cvzoom.net) (208.230.69.212) by ns.cvzoom.net with SMTP; 6 Mar 2000 18:08:42 -0000 Message-ID: <38C3F412.5080700@cvzoom.net> Date: Mon, 06 Mar 2000 13:08:18 -0500 From: Donn Miller User-Agent: Mozilla 5.0 X-Accept-Language: en MIME-Version: 1.0 To: Marc Schneiders Cc: Kris Kennaway , freebsd-current@freebsd.org Subject: Re: Discussions and "facts" [Was: Re: ssh strangeness in -current...] References: Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Schneiders wrote: > = > I find it quite a problem that one is supposed to read very long > threads of discussions (which one may not be interested in, does not > have the time for, or cannot understand) in order to find the > information necessary to run and keep up with current without > problems. Or to solve any occuring problems. In that case, I would just follow -current on muc.lists.freebsd.current, = or one of the other usenet mirrors.=A0 If you want to reply to something,= = just reply to the person directly, and add current@freebsd.org in your = cc.=A0 That would be one solution. [using mozilla's mail reader, so sorry if this looks screwed up] - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 10:33:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from tmtowtdi.perl.org (tmtowtdi.perl.org [209.85.3.25]) by hub.freebsd.org (Postfix) with SMTP id 96A1937BEA0 for ; Mon, 6 Mar 2000 10:33:55 -0800 (PST) (envelope-from richard@tmtowtdi.perl.org) Received: (qmail 6640 invoked by uid 511); 6 Mar 2000 18:33:55 -0000 Subject: [ID 20000306.004] unpack(NaN) big baddaboom To: perl5-porters@perl.org Reply-To: iang@systemics.com From: Ian Grigg Delivered-To: perlmail-perlbug@perl.org Cc: current@freebsd.org Date: Mon, 6 Mar 2000 14:31:57 -0400 (AST) Message-Id: <200003061831.OAA74965@systemics.com> Received: (qmail 6632 invoked by uid 508); 6 Mar 2000 18:33:54 -0000 X-loop: perlbug@perl.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a bug report for perl from iang@systemics.com, generated with the help of perlbug 1.26 running under perl 5.00503. ----------------------------------------------------------------- [Please enter your report here] Running following program causes "Floating point exception" on FreeBSD 3.2-STABLE *and* 4.0-CURRENT #0: Tue Feb 29 02:11:52 AST 2000 (but not on Linux "2.3.44 #12 SMP") (all 5.00503) ===8<======8<======8<======8<==== #!/usr/bin/perl my $packed = "\0\0\xc0\x7f"; print STDERR "len: ", length($packed), " bytes: ", unpack("H*", $packed), "\n"; my $float = unpack("f", $packed); print STDERR "float done\n"; print STDERR "float: $float\n"; exit 0; ===8<======8<======8<======8<==== hayek$ ./moo.pl len: 4 bytes: 0000c07f float done Floating point exception hayek$ echo $? 136 hayek$ ===8<======8<======8<======8<==== [Please do not change anything below this line] ----------------------------------------------------------------- --- This perlbug was built using Perl 5.00502 - Mon Oct 26 16:01:51 AST 1998 It is being executed now by Perl 5.00503 - $Date: 1999/05/05 19:42:40 $. Site configuration information for perl 5.00503: Configured by markm at $Date: 1999/05/05 19:42:40 $. Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: Platform: osname=freebsd, osvers=4.0-current, archname=i386-freebsd uname='freebsd freefall.freebsd.org 4.0-current freebsd 4.0-current #0: $Date: 1999/05/05 19:42:40 $' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='undef', gccversion=egcs-2.91.66 19990314 (egcs-1.1.2 release) cppflags='' ccflags ='' stdchar='char', d_stdstdio=undef, usevfork=true intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='cc', ldflags ='-Wl,-E' libpth=/usr/lib libs=-lm -lc -lcrypt libc=/usr/lib/libc.so, so=so, useshrplib=true, libperl=libperl.so.3 Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-DPIC -fpic', lddlflags='-shared' Locally applied patches: --- @INC for perl 5.00503: /data/ricardo/perl /home/iang/src/hayek/ricardo/blib/lib /usr/libdata/perl/5.00503/mach /usr/libdata/perl/5.00503 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 . --- Environment for perl 5.00503: HOME=/home/iang LANG (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=/home/iang/src/hayek/market/cmd:/home/iang/src/hayek/market/bin:/data/ricardo/perl/cmd:/home/iang/src/hayek/ricardo/cmd:/home/iang/bin:/home/iang/cmd:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/java/bin:/sbin:/usr/sbin:/usr/local/sbin PERLLIB=/data/ricardo/perl:/home/iang/src/hayek/ricardo/blib/lib PERL_BADLANG (unset) SHELL=/usr/local/bin/bash To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 10:34: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from systemics.com (hayek.ai [209.88.68.42]) by hub.freebsd.org (Postfix) with ESMTP id 4528637BEB1 for ; Mon, 6 Mar 2000 10:33:58 -0800 (PST) (envelope-from iang@systemics.com) Received: (from iang@localhost) by systemics.com (8.9.3/8.9.1) id OAA74965; Mon, 6 Mar 2000 14:31:57 -0400 (AST) (envelope-from iang) Date: Mon, 6 Mar 2000 14:31:57 -0400 (AST) From: Ian Grigg Message-Id: <200003061831.OAA74965@systemics.com> To: perlbug@perl.com Subject: unpack(NaN) big baddaboom Cc: current@freebsd.org Reply-To: iang@systemics.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a bug report for perl from iang@systemics.com, generated with the help of perlbug 1.26 running under perl 5.00503. ----------------------------------------------------------------- [Please enter your report here] Running following program causes "Floating point exception" on FreeBSD 3.2-STABLE *and* 4.0-CURRENT #0: Tue Feb 29 02:11:52 AST 2000 (but not on Linux "2.3.44 #12 SMP") (all 5.00503) ===8<======8<======8<======8<==== #!/usr/bin/perl my $packed = "\0\0\xc0\x7f"; print STDERR "len: ", length($packed), " bytes: ", unpack("H*", $packed), "\n"; my $float = unpack("f", $packed); print STDERR "float done\n"; print STDERR "float: $float\n"; exit 0; ===8<======8<======8<======8<==== hayek$ ./moo.pl len: 4 bytes: 0000c07f float done Floating point exception hayek$ echo $? 136 hayek$ ===8<======8<======8<======8<==== [Please do not change anything below this line] ----------------------------------------------------------------- --- This perlbug was built using Perl 5.00502 - Mon Oct 26 16:01:51 AST 1998 It is being executed now by Perl 5.00503 - $Date: 1999/05/05 19:42:40 $. Site configuration information for perl 5.00503: Configured by markm at $Date: 1999/05/05 19:42:40 $. Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: Platform: osname=freebsd, osvers=4.0-current, archname=i386-freebsd uname='freebsd freefall.freebsd.org 4.0-current freebsd 4.0-current #0: $Date: 1999/05/05 19:42:40 $' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='undef', gccversion=egcs-2.91.66 19990314 (egcs-1.1.2 release) cppflags='' ccflags ='' stdchar='char', d_stdstdio=undef, usevfork=true intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='cc', ldflags ='-Wl,-E' libpth=/usr/lib libs=-lm -lc -lcrypt libc=/usr/lib/libc.so, so=so, useshrplib=true, libperl=libperl.so.3 Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-DPIC -fpic', lddlflags='-shared' Locally applied patches: --- @INC for perl 5.00503: /data/ricardo/perl /home/iang/src/hayek/ricardo/blib/lib /usr/libdata/perl/5.00503/mach /usr/libdata/perl/5.00503 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 . --- Environment for perl 5.00503: HOME=/home/iang LANG (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=/home/iang/src/hayek/market/cmd:/home/iang/src/hayek/market/bin:/data/ricardo/perl/cmd:/home/iang/src/hayek/ricardo/cmd:/home/iang/bin:/home/iang/cmd:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/java/bin:/sbin:/usr/sbin:/usr/local/sbin PERLLIB=/data/ricardo/perl:/home/iang/src/hayek/ricardo/blib/lib PERL_BADLANG (unset) SHELL=/usr/local/bin/bash To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 10:44:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 9C9D337B83F for ; Mon, 6 Mar 2000 10:44:11 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id TAA09713; Mon, 6 Mar 2000 19:43:56 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: iang@systemics.com Cc: perl5-porters@perl.org, current@FreeBSD.ORG Subject: Re: [ID 20000306.004] unpack(NaN) big baddaboom In-reply-to: Your message of "Mon, 06 Mar 2000 14:31:57 -0400." <200003061831.OAA74965@systemics.com> Date: Mon, 06 Mar 2000 19:43:56 +0100 Message-ID: <9711.952368236@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That is because FreeBSD correctly traps operations on the value NaN. Depending on your religion the bug is either in perl itself which should be more careful about NaN and Inf values, or in the perl script you supply which does something which is patently bogus, but nothing which should provoke a FP trap according to IEEE. I would argue that as long as your perl script doesn't use the NaN in an operation which IEEE documents as giving a trap ( compare of two floats for ordered magnitude for instance) then your perl interpreter shouldn't either. Poul-Henning In message <200003061831.OAA74965@systemics.com>, Ian Grigg writes: > >This is a bug report for perl from iang@systemics.com, >generated with the help of perlbug 1.26 running under perl 5.00503. > > >----------------------------------------------------------------- >[Please enter your report here] > >Running following program causes "Floating point exception" on >FreeBSD 3.2-STABLE *and* 4.0-CURRENT #0: Tue Feb 29 02:11:52 AST 2000 >(but not on Linux "2.3.44 #12 SMP") (all 5.00503) > >===8<======8<======8<======8<==== >#!/usr/bin/perl > >my $packed = "\0\0\xc0\x7f"; >print STDERR "len: ", length($packed), " bytes: ", unpack("H*", $packed), "\n"; >my $float = unpack("f", $packed); >print STDERR "float done\n"; >print STDERR "float: $float\n"; > >exit 0; >===8<======8<======8<======8<==== >hayek$ ./moo.pl >len: 4 bytes: 0000c07f >float done >Floating point exception >hayek$ echo $? >136 >hayek$ >===8<======8<======8<======8<==== > > >[Please do not change anything below this line] >----------------------------------------------------------------- > >--- >This perlbug was built using Perl 5.00502 - Mon Oct 26 16:01:51 AST 1998 >It is being executed now by Perl 5.00503 - $Date: 1999/05/05 19:42:40 $. > >Site configuration information for perl 5.00503: > >Configured by markm at $Date: 1999/05/05 19:42:40 $. > >Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: > Platform: > osname=freebsd, osvers=4.0-current, archname=i386-freebsd > uname='freebsd freefall.freebsd.org 4.0-current freebsd 4.0-current #0: $Date: 1999/05/05 19:42:40 $' > hint=recommended, useposix=true, d_sigaction=define > usethreads=undef useperlio=undef d_sfio=undef > Compiler: > cc='cc', optimize='undef', gccversion=egcs-2.91.66 19990314 (egcs-1.1.2 release) > cppflags='' > ccflags ='' > stdchar='char', d_stdstdio=undef, usevfork=true > intsize=4, longsize=4, ptrsize=4, doublesize=8 > d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 > alignbytes=4, usemymalloc=n, prototype=define > Linker and Libraries: > ld='cc', ldflags ='-Wl,-E' > libpth=/usr/lib > libs=-lm -lc -lcrypt > libc=/usr/lib/libc.so, so=so, useshrplib=true, libperl=libperl.so.3 > Dynamic Linking: > dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' > cccdlflags='-DPIC -fpic', lddlflags='-shared' > >Locally applied patches: > > >--- >@INC for perl 5.00503: > /data/ricardo/perl > /home/iang/src/hayek/ricardo/blib/lib > /usr/libdata/perl/5.00503/mach > /usr/libdata/perl/5.00503 > /usr/local/lib/perl5/site_perl/5.005/i386-freebsd > /usr/local/lib/perl5/site_perl/5.005 > . > >--- >Environment for perl 5.00503: > HOME=/home/iang > LANG (unset) > LD_LIBRARY_PATH (unset) > LOGDIR (unset) > PATH=/home/iang/src/hayek/market/cmd:/home/iang/src/hayek/market/bin:/data/ricardo/perl/cmd:/home/iang/src/hayek/ricardo/cmd:/home/iang/bin:/home/iang/cmd:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/java/bin:/sbin:/usr/sbin:/usr/local/sbin > PERLLIB=/data/ricardo/perl:/home/iang/src/hayek/ricardo/blib/lib > PERL_BADLANG (unset) > SHELL=/usr/local/bin/bash > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 11: 1:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 74A7637BF28 for ; Mon, 6 Mar 2000 11:01:06 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA25240; Mon, 6 Mar 2000 14:00:54 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000306112939.A24401@cs.uu.nl> References: <200003060833.AAA18027@windsor.research.att.com> <200003060920.CAA57713@harmony.village.org> <20000306112939.A24401@cs.uu.nl> Date: Mon, 6 Mar 2000 14:01:15 -0500 To: Edwin Kremer , freebsd-current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: openssh question Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:29 AM +0100 3/6/00, Edwin Kremer wrote: >On a side note: last week, Tatu Ylonen, principal author of SSH, posted a >message on the SSH mailing-list (in the thread about the new SSH2 license) >saying that: > > " OpenSSH is based on my version from back in 1995 or 1996. The > " OpenSSH folks have fixed many of the (security) bugs in that > " version, but not all of them when I last checked. Some of the > " problems in SSH1 are very fundamental. > " > " I do not recommend use of OpenSSH (or SSH1 generally, for that matter). > >There hasn't been much followup on this. Anybody here who cares to >comment on this? What issues are relevant here and how bad is it? What he is saying is that the ssh2 protocol is better than the ssh1 protocol, and that is true. On the other hand, most of us here have been sticking to ssh1 ("the product") because of licensing and pricing issues with ssh2, and I'd say openssh either beats or will soon beat the ssh1 product. Not only that, but if you check the web page at OpenSSH.COM, you'll see that they also claim to be working on ssh2 protocols for openssh. Once that is done, openssh will also have addressed the fundamental shortcomings of ssh1 that he is alluding to. Also note that the security shortcomings are that ssh1 is not as perfectly bullet-proof of a protocol as it could be. It is certainly much much much much better, security-wise, than running telnet. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 11:12:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from systemics.com (hayek.ai [209.88.68.42]) by hub.freebsd.org (Postfix) with ESMTP id 2CCA937C0F7 for ; Mon, 6 Mar 2000 11:12:04 -0800 (PST) (envelope-from iang@systemics.com) Received: (from iang@localhost) by systemics.com (8.9.3/8.9.1) id PAA75240; Mon, 6 Mar 2000 15:10:20 -0400 (AST) (envelope-from iang) Date: Mon, 6 Mar 2000 15:10:20 -0400 (AST) From: Ian Grigg Message-Id: <200003061910.PAA75240@systemics.com> To: phk@critter.freebsd.dk Subject: Re: [ID 20000306.004] unpack(NaN) big baddaboom Cc: current@FreeBSD.ORG, perl5-porters@perl.org Reply-To: iang@systemics.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG More on that! Lads here took this to heart and put the debugger over the code. Apparently, Linux uses glibc which sets the flags in FPU to ignore the cmp-NaN fault. Then, I guess, Perl picks it up and turns it into NaN. OTOH, FreeBSD libraries don't do that, and the FPU causes the cmp-NaN fault to cause a FP exception. (Recorded 2nd hand, you won't catch me using debuggers.) > That is because FreeBSD correctly traps operations on the value NaN. > > Depending on your religion the bug is either in perl itself which > should be more careful about NaN and Inf values, or in the perl > script you supply which does something which is patently bogus, > but nothing which should provoke a FP trap according to IEEE. I don't know much about religion, but this feels like a Perl bug to me. I feed a highlevel command a number I read off the wire, and it blows up. As I have no control over the wire (it's a network) I cannot *not* handle the number. > I would argue that as long as your perl script doesn't use the NaN > in an operation which IEEE documents as giving a trap ( compare of > two floats for ordered magnitude for instance) then your perl > interpreter shouldn't either. Well, in that sense, this is my workaround: my $data = $is->read(4); # # Damn, FreeBSD throws Floating Point Exception on NaN! # my $long = unpack("N", $data); if ($long == 2143289344) { return "NaN"; } So I'm fine with it for now. But, as Perl is an interpretive language, and they are supposed to, on some higher plain of thought, handle everything thrown at them, I'd rather it just returned "NaN" like Linux. Still, I'm fixed! Thanks for the confirmation. iang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 11:19:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 9894E37BEEB for ; Mon, 6 Mar 2000 11:19:15 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA09876; Mon, 6 Mar 2000 20:19:10 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: iang@systemics.com Cc: current@FreeBSD.ORG, perl5-porters@perl.org Subject: Re: [ID 20000306.004] unpack(NaN) big baddaboom In-reply-to: Your message of "Mon, 06 Mar 2000 15:10:20 -0400." <200003061910.PAA75240@systemics.com> Date: Mon, 06 Mar 2000 20:19:10 +0100 Message-ID: <9874.952370350@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003061910.PAA75240@systemics.com>, Ian Grigg writes: >> Depending on your religion the bug is either in perl itself which >> should be more careful about NaN and Inf values, or in the perl >> script you supply which does something which is patently bogus, >> but nothing which should provoke a FP trap according to IEEE. > >I don't know much about religion, but this feels like >a Perl bug to me. I feed a highlevel command a number >I read off the wire, and it blows up. As I have no >control over the wire (it's a network) I cannot *not* >handle the number. I would agree with that. >> I would argue that as long as your perl script doesn't use the NaN >> in an operation which IEEE documents as giving a trap ( compare of >> two floats for ordered magnitude for instance) then your perl >> interpreter shouldn't either. > >Well, in that sense, this is my workaround: > > my $data = $is->read(4); > # > # Damn, FreeBSD throws Floating Point Exception on NaN! > # > my $long = unpack("N", $data); > if ($long == 2143289344) > { > return "NaN"; > } That is not enough, NaN has multiple binary representations. isnan(3) is your friend. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 11:26:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop3.ptld.uswest.net (ptldpop3.ptld.uswest.net [198.36.160.3]) by hub.freebsd.org (Postfix) with SMTP id 70E8237BF23 for ; Mon, 6 Mar 2000 11:26:52 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 34616 invoked by alias); 6 Mar 2000 19:26:07 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 34587 invoked by uid 0); 6 Mar 2000 19:26:07 -0000 Received: from unknown (HELO laptop.cybcon.com) (63.163.56.46) by pop.ptld.uswest.net with SMTP; 6 Mar 2000 19:26:07 -0000 Content-Length: 543 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 06 Mar 2000 11:23:45 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Garance A Drosihn Subject: Re: openssh question Cc: freebsd-current@FreeBSD.ORG, Edwin Kremer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that openssh is in the base system, I assume it will no longer be in the ports. How do we update it, ie, when a updated version comes out. I would rather not make world just to update that. ---------------------------------- E-Mail: bwoods2@uswest.net Date: 06-Mar-00 Time: 11:22:26l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 11:27:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id C7FDB37B817 for ; Mon, 6 Mar 2000 11:27:09 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id 867385D7E; Mon, 6 Mar 2000 20:27:18 +0100 (CET) Date: Mon, 6 Mar 2000 20:27:18 +0100 From: Dave Boers To: Arun Sharma Cc: freebsd-current@freebsd.org Subject: Re: current lockups Message-ID: <20000306202718.A26973@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000304235010.B10778@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000304235010.B10778@sharmas.dhs.org>; from adsharma@sharmas.dhs.org on Sat, Mar 04, 2000 at 11:50:10PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Arun Sharma had the courage to say: > Compiling Mozilla with make -j 2 got -current to lock up, twice in > succession. I'm running a fairly recent snapshot (a week or two old) > on a Dual celeron box (BP6) with UDMA66 enabled. Finally. I've been complaining about this on several occasions. I'm also running UDMA66 and Dual Celeron BP6. No overclocking. > The kernel had DDB enabled. I was running X, but I didn't see any > signs of the kernel attempting to get into the debugger. Ditto here. > Has this been fixed ? Is anyone interested in investigating ? > I'll post more info if I find anything. I'm interested in the fix, of course :-) But where to start looking? I've had three lockups so far (none before january 2000) but I didn't find anything that reliably triggered it. Regards, Dave. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 11:36: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 1CCEB37BC3C for ; Mon, 6 Mar 2000 11:35:59 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id AF1A05D7D; Mon, 6 Mar 2000 20:36:08 +0100 (CET) Date: Mon, 6 Mar 2000 20:36:08 +0100 From: Dave Boers To: freebsd-current@freebsd.org Cc: dalroi@wit401310.student.utwente.nl Subject: Small bug in chown and chgrp ? Message-ID: <20000306203608.B26973@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've been bitten by the following: 44 relativity ~ % chown -v djb:wheel test chown: illegal option -- v usage: chown [-R [-H | -L | -P]] [-f] [-h] [-v] owner[:group] file ... chown [-R [-H | -L | -P]] [-f] [-h] [-v] :group file ... chgrp [-R [-H | -L | -P]] [-f] [-h] [-v] group file ... Where "test" is an ordinary directory. It seems that chown's behavior is inconsistent with both the usage message and the man page. The same goes for chgrp. Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 11:37:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhub2.ncal.verio.com (mailhub2.ncal.verio.com [204.247.247.54]) by hub.freebsd.org (Postfix) with ESMTP id 2E11F37B70E for ; Mon, 6 Mar 2000 11:37:22 -0800 (PST) (envelope-from jepace@pobox.com) Received: from shell1.ncal.verio.com (pace@shell1.ncal.verio.com [204.247.248.254]) by mailhub2.ncal.verio.com (8.8.8+Sun/8.8.7) with ESMTP id LAA25489 for ; Mon, 6 Mar 2000 11:37:21 -0800 (PST) Received: from localhost (pace@localhost) by shell1.ncal.verio.com (8.8.7/8.8.7) with ESMTP id LAA07255 for ; Mon, 6 Mar 2000 11:37:18 -0800 (PST) X-Authentication-Warning: shell1. ncal.verio.com: pace owned process doing -bs Date: Mon, 6 Mar 2000 11:37:18 -0800 (PST) From: "James E. Pace" Reply-To: "James E. Pace" To: current@freebsd.org Subject: /usr/bin/ssh and SOCKS Message-ID: X-Url: http://www.pobox.com/~jepace X-Pgp-Fingerprint: 8C E7 12 5A 3A 8C 5C 4D EC 15 7B 65 EA 82 D2 BF X-Pgp-Keyid: A49EA4D9 X-Files: The Truth Is Out There MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I rebuilt -current on Friday, and OpenSSH does not work through a SOCKS firewall. In my make.conf, I have "USE_SOCKS= YES", which is used in the ports/security/ssh port. Any help? Thanks, James This letter brought to you by: ************************************* ** James E. Pace ** ** http://www.pobox.com/~jepace ** ******************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 11:37:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail3.microsoft.com (mail3.microsoft.com [131.107.3.123]) by hub.freebsd.org (Postfix) with SMTP id 2117F37BFB4 for ; Mon, 6 Mar 2000 11:37:32 -0800 (PST) (envelope-from richdr@microsoft.com) Received: from 157.54.9.100 by mail3.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 06 Mar 2000 11:33:12 -0800 (Pacific Standard Time) Received: by INET-IMC-03 with Internet Mail Service (5.5.2651.58) id ; Mon, 6 Mar 2000 11:23:09 -0800 Message-ID: <4D0A23B3F74DD111ACCD00805F31D8101CA21D05@RED-MSG-50> From: Richard Draves To: 'Bob Fink' , "Eugene M. Kim" , Bill Fenner Cc: jose@we.lc.ehu.es, FreeBSD-current Mailing List , 6bone@ISI.EDU Subject: RE: IPv6: can a link-site (or global) address be configured in rc .conf? Date: Mon, 6 Mar 2000 11:23:02 -0800 X-Mailer: Internet Mail Service (5.5.2651.58) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The exception is for "6to4" prefixes which are in the > 2002::/16 TLA space. > See the I-D: > > > > Please read, then ask any questions you may have. 6to4 is currently > supported, and there are relay routers up and running. To summarize, with 6to4 all you need is one global/static IPv4 address and you get a /48 IPv6 prefix for yourself. Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 11:41:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 72ADD37BDC6 for ; Mon, 6 Mar 2000 11:41:08 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id MAA00617; Mon, 6 Mar 2000 12:12:17 -0800 (PST) Date: Mon, 6 Mar 2000 12:12:17 -0800 From: Alfred Perlstein To: Dave Boers Cc: freebsd-current@FreeBSD.ORG, dalroi@wit401310.student.utwente.nl Subject: Re: Small bug in chown and chgrp ? Message-ID: <20000306121217.Z14279@fw.wintelcom.net> References: <20000306203608.B26973@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000306203608.B26973@relativity.student.utwente.nl>; from djb@wit389306.student.utwente.nl on Mon, Mar 06, 2000 at 08:36:08PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dave Boers [000306 12:08] wrote: > Hi all, > > I've been bitten by the following: > > 44 relativity ~ % chown -v djb:wheel test > chown: illegal option -- v > usage: chown [-R [-H | -L | -P]] [-f] [-h] [-v] owner[:group] file ... > chown [-R [-H | -L | -P]] [-f] [-h] [-v] :group file ... > chgrp [-R [-H | -L | -P]] [-f] [-h] [-v] group file ... > > Where "test" is an ordinary directory. > > It seems that chown's behavior is inconsistent with both the usage message > and the man page. The same goes for chgrp. have you deleted your stale copies of chown/chgrp? hint look in /bin /sbin /usr/bin /usr/sbin and make sure the old ones aren't "in the way". -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 11:52:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw00.execpc.com (mailgw00.execpc.com [169.207.1.78]) by hub.freebsd.org (Postfix) with ESMTP id 5A1C537BC3C for ; Mon, 6 Mar 2000 11:52:55 -0800 (PST) (envelope-from rmukerji@execpc.com) Received: from earth.execpc.com (rmukerji@earth.execpc.com [169.207.16.1]) by mailgw00.execpc.com (8.9.1) id NAA02254; Mon, 6 Mar 2000 13:52:54 -0600 Received: (from rmukerji@localhost) by earth.execpc.com (8.9.0) id NAA28940; Mon, 6 Mar 2000 13:52:54 -0600 (CST) Date: Mon, 6 Mar 2000 13:52:53 -0600 From: Arindum Mukerji To: Dave Boers Cc: freebsd-current@freebsd.org Subject: Re: Small bug in chown and chgrp ? Message-ID: <20000306135253.A21186@earth.execpc.com> References: <20000306203608.B26973@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3us In-Reply-To: <20000306203608.B26973@relativity.student.utwente.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dave Boers (djb@relativity.student.utwente.nl) [000306 13:36]: > chown: illegal option -- v > usage: chown [-R [-H | -L | -P]] [-f] [-h] [-v] owner[:group] file ... > chown [-R [-H | -L | -P]] [-f] [-h] [-v] :group file ... > chgrp [-R [-H | -L | -P]] [-f] [-h] [-v] group file ... > A simple patch: --- chown.c.1.14 Sat Nov 27 13:25:07 1999 +++ chown.c Mon Mar 6 13:42:41 2000 @@ -86,7 +86,7 @@ ischown = myname[2] == 'o'; Hflag = Lflag = Pflag = hflag = 0; - while ((ch = getopt(argc, argv, "HLPRfh")) != -1) + while ((ch = getopt(argc, argv, "HLPRfhv")) != -1) switch (ch) { case 'H': Hflag = 1; @@ -108,6 +108,9 @@ break; case 'h': hflag = 1; + break; + case 'v': + vflag = 1; break; case '?': default: Regards, -- Arindum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 12: 0:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id E54A037BC3C for ; Mon, 6 Mar 2000 12:00:40 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id MAA16054; Mon, 6 Mar 2000 12:00:34 -0800 Date: Mon, 6 Mar 2000 12:00:34 -0800 From: Arun Sharma To: Dave Boers Cc: freebsd-current@freebsd.org Subject: Re: current lockups Message-ID: <20000306120033.A16043@sharmas.dhs.org> References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000306202718.A26973@relativity.student.utwente.nl>; from Dave Boers on Mon, Mar 06, 2000 at 08:27:18PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 08:27:18PM +0100, Dave Boers wrote: > > Has this been fixed ? Is anyone interested in investigating ? > > I'll post more info if I find anything. > > I'm interested in the fix, of course :-) But where to start looking? I've > had three lockups so far (none before january 2000) but I didn't find > anything that reliably triggered it. The cooling theory sounds the most plausible so far. I'm not over clocking my CPUs (Celeron 366s) and have appropriate cooling installed. But the machine is kept in a small room, with a bunch of other machines and gets a bit warm at times. There has been no reproducible case of locking up. Each one looks different. But most were trigerred by heavy compilation and I/O. One was a lockup overnight with no activity on the system. When it happens, it does not respond to pings or scroll lock. If you'd like to do something about it, working on getting a reproducible hang would be the most beneficial one. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 12:11: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 8D58637BFB4 for ; Mon, 6 Mar 2000 12:10:58 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id 80EA25D7D; Mon, 6 Mar 2000 21:11:06 +0100 (CET) Date: Mon, 6 Mar 2000 21:11:06 +0100 From: Dave Boers To: Alfred Perlstein Cc: Dave Boers , freebsd-current@FreeBSD.ORG, dalroi@wit401310.student.utwente.nl Subject: Re: Small bug in chown and chgrp ? Message-ID: <20000306211106.A27212@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000306203608.B26973@relativity.student.utwente.nl> <20000306121217.Z14279@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000306121217.Z14279@fw.wintelcom.net>; from bright@wintelcom.net on Mon, Mar 06, 2000 at 12:12:17PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Alfred Perlstein had the courage to say: > have you deleted your stale copies of chown/chgrp? hint look in > /bin /sbin /usr/bin /usr/sbin and make sure the old ones aren't > "in the way". Yes I have. Because I got a new disk, I did a fresh install of -current a few weeks ago. Well after the change of chown/chgrp from /bin and /sbin to /usr/bin and /usr/sbin. I double checked to make sure and the only versions of chown/chgrp are the ones in /usr/sbin and /usr/bin respectively. Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 12:19:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C3F7B37BED3; Mon, 6 Mar 2000 12:19:07 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA55337; Mon, 6 Mar 2000 13:19:05 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA61266; Mon, 6 Mar 2000 13:18:57 -0700 (MST) Message-Id: <200003062018.NAA61266@harmony.village.org> To: bloom@acm.org Subject: Re: ssh strangeness in -current... Cc: John Baldwin , Kris Kennaway , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Mar 2000 09:14:44 EST." <38C3BD54.D169B3D7@acm.org> References: <38C3BD54.D169B3D7@acm.org> <200003060423.XAA01323@server.baldwin.cx> Date: Mon, 06 Mar 2000 13:18:57 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38C3BD54.D169B3D7@acm.org> Jim Bloom writes: : Did Warner include this with his changes to UPDATING about openssh in : the base system (which I haven't seen yet). No. I didn't, but I will. Here's my current draft that I'll commit after a while... Index: UPDATING =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/UPDATING,v retrieving revision 1.71 diff -u -r1.71 UPDATING --- UPDATING 2000/02/23 05:51:02 1.71 +++ UPDATING 2000/03/06 19:37:45 @@ -5,6 +5,27 @@ done items, please see the end of the file. Search for 'COMMON ITEMS:' +20000303: + CMSG_XXX macros offset in has changed to + conform RFC-2292. All affected applications have been + corrected. The i386 platform's offsets haven't changed, but + the alpha's did. When you build and install new kernel on + FreeBSD/alpha, you must also do a make world. + +20000225: + OpenSSH has been added to FreeBSD. This may conflict with the + ssh port since it installs binaries into /usr/bin and the port + goes into /usr/local/bin. Most paths have /usr/bin in the path + before /usr/local/bin, so problems may arrise. If you don't + want OpenSSH, add NO_OPENSSH=yes to your make.conf. + + You will also need to enable openssh in /etc/rc.conf if you + want to run the new servers. You may need to move your key + and other config files from /usr/local/etc to /etc. + + Openssh isn't 100% compatible with ssh, so some care needs to + be taken in its operation. + 20000205: The xinstall problem has kinda sorta been corrected. The following is known to work by the author of UPDATING. It To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 12:26: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 4B96637BC6F for ; Mon, 6 Mar 2000 12:25:58 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id C87405D7D; Mon, 6 Mar 2000 21:26:07 +0100 (CET) Date: Mon, 6 Mar 2000 21:26:07 +0100 From: Dave Boers To: Arun Sharma Cc: Dave Boers , freebsd-current@freebsd.org Subject: Re: current lockups Message-ID: <20000306212607.B27212@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> <20000306120033.A16043@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000306120033.A16043@sharmas.dhs.org>; from adsharma@sharmas.dhs.org on Mon, Mar 06, 2000 at 12:00:34PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Arun Sharma had the courage to say: > The cooling theory sounds the most plausible so far. I'm not over clocking > my CPUs (Celeron 366s) and have appropriate cooling installed. But the > machine is kept in a small room, with a bunch of other machines and gets > a bit warm at times. My system has been 50 degrees Celcius for the past half year or so. Yet, the lockups only started occurring around January 2000. Once again, my system is not overclocked and the temperature is well within Intel's and Abit's temperature specifications, so there shouldn't be hardware problems. > There has been no reproducible case of locking up. Each one looks different. > But most were trigerred by heavy compilation and I/O. One was a lockup > overnight with no activity on the system. When it happens, it does not > respond to pings or scroll lock. Most of my lockups occurred when the system was relatively idle. Mostly they happened only after 9 - 11 days of uptime. As you say, each one looks different and there doesn't seem to be a pattern to it. When it locks up, there is no response to the console, the network or the serial terminal. Only the reset button is obeyed. I have DDB in my kernel, but there's no getting into it. Also, no log messages of any kind from just before the lockups. > If you'd like to do something about it, working on getting a reproducible > hang would be the most beneficial one. That's what I have been trying to do for the past few weeks, but I can't seem to trigger it. Uptime is now 2 days and I intend to let it run to 12 or so before make installworld again, to see if I can reproduce it. However, I did recently change from UDMA66 to an U2W SCSI disk for my main partitions (/, /usr, /var, /tmp and swap). It may have impact on the situation and it is the reason for the short uptime. If the problem has gone away now, it might indicate something with the ATA driver. I'll keep you informed. So far, since the disk change I've been putting my system under some heavy load from time to time (like building three large ports and make -j 12 buildworld at the same time). So far, the system is quite stable. Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 12:27:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id 009DA37B9D8; Mon, 6 Mar 2000 12:27:45 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id PAA16130; Mon, 6 Mar 2000 15:27:39 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38C414BB.8DAF8659@acm.org> Date: Mon, 06 Mar 2000 15:27:39 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: John Baldwin , Kris Kennaway , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... References: <38C3BD54.D169B3D7@acm.org> <200003060423.XAA01323@server.baldwin.cx> <200003062018.NAA61266@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > + You will also need to enable openssh in /etc/rc.conf if you > + want to run the new servers. You may need to move your key > + and other config files from /usr/local/etc to /etc. Looks fine except config files go in /etc/ssh, not /etc. Jim Bloom bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 12:29: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 268E537BBD3; Mon, 6 Mar 2000 12:29:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 247D92E815C; Mon, 6 Mar 2000 12:29:01 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 12:29:01 -0800 (PST) From: Kris Kennaway To: Warner Losh Cc: bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <200003062018.NAA61266@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, Warner Losh wrote: > + want to run the new servers. You may need to move your key > + and other config files from /usr/local/etc to /etc. /etc/ssh > + Openssh isn't 100% compatible with ssh, so some care needs to > + be taken in its operation. This sounds bad. Are you referring to the -o syntax differences, or actual incompatabilities? There have been unsubstantiated reports of interoperability problems, but nothing well documented here. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 12:29:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0F14237BE48 for ; Mon, 6 Mar 2000 12:29:43 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA55406; Mon, 6 Mar 2000 13:29:41 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA61443; Mon, 6 Mar 2000 13:29:32 -0700 (MST) Message-Id: <200003062029.NAA61443@harmony.village.org> To: "James E. Pace" Subject: Re: /usr/bin/ssh and SOCKS Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Mar 2000 11:37:18 PST." References: Date: Mon, 06 Mar 2000 13:29:32 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "James E. Pace" writes: : I rebuilt -current on Friday, and OpenSSH does not work through a : SOCKS firewall. : : In my make.conf, I have "USE_SOCKS= YES", which is used in the : ports/security/ssh port. : : Any help? Sure. Here's what I have in my uncommitted tree. It assumes that you have socks installed already. Known to work with the nec port, not known one way or the other on dante. Oh, there's lots of warnings from this, but it does work. Warner Index: scp/Makefile =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/secure/usr.bin/scp/Makefile,v retrieving revision 1.2 diff -u -r1.2 Makefile --- scp/Makefile 2000/02/25 08:21:09 1.2 +++ scp/Makefile 2000/03/04 06:00:12 @@ -16,3 +16,8 @@ LDADD+= -lcrypto -lutil -lz -L${.OBJDIR}/../../lib/libssh -lssh DPADD+= ${LIBCRYPTO} ${LIBUTIL} ${LIBZ} + +.if defined(USE_SOCKS) && ((${USE_SOCKS} == "yes") || (${USE_SOCKS} == "YES")) +LDADD+= -L/usr/local/lib -lsocks5 +CFLAGS+= -DSOCKS --include /usr/local/include/socks.h +.endif Index: ssh/Makefile =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/secure/usr.bin/ssh/Makefile,v retrieving revision 1.4 diff -u -r1.4 Makefile --- ssh/Makefile 2000/03/03 20:33:53 1.4 +++ ssh/Makefile 2000/03/05 05:58:06 @@ -37,3 +37,8 @@ LDADD+= -L${.OBJDIR}/../../lib/libssh -lssh -lcrypto -lutil -lz DPADD+= ${LIBCRYPTO} ${LIBUTIL} ${LIBZ} + +.if defined(USE_SOCKS) && ((${USE_SOCKS} == "yes") || (${USE_SOCKS} == "YES")) +LDADD+= -L/usr/local/lib -lsocks5 +CFLAGS+= -DSOCKS --include /usr/local/include/socks.h +.endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 12:32:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 479A637BBD3; Mon, 6 Mar 2000 12:32:13 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA55421; Mon, 6 Mar 2000 13:32:08 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA61484; Mon, 6 Mar 2000 13:32:00 -0700 (MST) Message-Id: <200003062032.NAA61484@harmony.village.org> To: Kris Kennaway Subject: Re: ssh strangeness in -current... Cc: bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Mar 2000 12:29:01 PST." References: Date: Mon, 06 Mar 2000 13:32:00 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : On Mon, 6 Mar 2000, Warner Losh wrote: : : > + want to run the new servers. You may need to move your key : > + and other config files from /usr/local/etc to /etc. : : /etc/ssh Thanks. : > + Openssh isn't 100% compatible with ssh, so some care needs to : > + be taken in its operation. : : This sounds bad. Are you referring to the -o syntax differences, or actual : incompatabilities? There have been unsubstantiated reports of : interoperability problems, but nothing well documented here. I'm talking about the -o syntax difference specifically. How does the following sound? Index: UPDATING =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/UPDATING,v retrieving revision 1.71 diff -u -r1.71 UPDATING --- UPDATING 2000/02/23 05:51:02 1.71 +++ UPDATING 2000/03/06 20:31:30 @@ -5,6 +5,27 @@ done items, please see the end of the file. Search for 'COMMON ITEMS:' +20000303: + CMSG_XXX macros offset in has changed to + conform RFC-2292. All affected applications have been + corrected. The i386 platform's offsets haven't changed, but + the alpha's did. When you build and install new kernel on + FreeBSD/alpha, you must also do a make world. + +20000225: + OpenSSH has been added to FreeBSD. This may conflict with the + ssh port since it installs binaries into /usr/bin and the port + goes into /usr/local/bin. Most paths have /usr/bin in the path + before /usr/local/bin, so problems may arrise. If you don't + want OpenSSH, add NO_OPENSSH=yes to your make.conf. + + You will also need to enable openssh in /etc/rc.conf if you + want to run the new servers. You may need to move your key + and other config files from /usr/local/etc to /etc/ssh. + + Openssh's command line parsing isn't 100% compatible with ssh, + so some care needs to be taken in its operation. + 20000205: The xinstall problem has kinda sorta been corrected. The following is known to work by the author of UPDATING. It Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 12:48:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 1349137BF9C for ; Mon, 6 Mar 2000 12:48:08 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 90912 invoked by uid 1001); 6 Mar 2000 20:47:59 +0000 (GMT) To: adsharma@sharmas.dhs.org Cc: djb@wit389306.student.utwente.nl, freebsd-current@freebsd.org Subject: Re: current lockups From: sthaug@nethelp.no In-Reply-To: Your message of "Mon, 6 Mar 2000 12:00:34 -0800" References: <20000306120033.A16043@sharmas.dhs.org> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 06 Mar 2000 21:47:59 +0100 Message-ID: <90910.952375679@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The cooling theory sounds the most plausible so far. I'm not over clocking > my CPUs (Celeron 366s) and have appropriate cooling installed. But the > machine is kept in a small room, with a bunch of other machines and gets > a bit warm at times. I have seen a couple of suggestions that this may not be the CPUs - but that the 82443BX chip (the one with the large green cooling fin) doesn't always get sufficient cooling on a BP6 board. Some thermal compound between the 82443BX and the cooling fin may be a good idea. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 12:51: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 9A57837BF4F for ; Mon, 6 Mar 2000 12:50:58 -0800 (PST) (envelope-from dgilbert@velocet.ca) Received: from velocet.ca (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id A9A23137F6B for ; Mon, 6 Mar 2000 15:50:57 -0500 (EST) Received: (from dgilbert@localhost) by velocet.ca (8.9.3/8.9.3) id PAA38834; Mon, 6 Mar 2000 15:50:58 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14532.6705.973327.980984@trooper.velocet.net> Date: Mon, 6 Mar 2000 15:50:57 -0500 (EST) To: freebsd-current@freebsd.org Subject: ports/net/tund not compiling. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like some very recent breakage: cc -O -pipe -g -DDEBUG -DNO_IDEA -static -o tund main.o tund.o secur.o scb.o utils.o md5.o alarm.o cipher.o search.o -L/usr/lib -lmd -lcrypto /usr/lib/libcrypto.a(rsa_lib.o): In function `RSA_new_method': rsa_lib.o(.text+0x91): undefined reference to `RSA_PKCS1' *** Error code 1 Stop in /usr/ports/net/tund/work/tund-0.20. *** Error code 1 Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13: 4: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id B4EBA37BEFE; Mon, 6 Mar 2000 13:03:51 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 6 Mar 2000 21:03:50 +0000 (GMT) Date: Mon, 6 Mar 2000 21:03:50 +0000 From: David Malone To: Warner Losh Cc: Kris Kennaway , bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... Message-ID: <20000306210349.A73029@walton.maths.tcd.ie> References: <200003062032.NAA61484@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003062032.NAA61484@harmony.village.org>; from imp@village.org on Mon, Mar 06, 2000 at 01:32:00PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 01:32:00PM -0700, Warner Losh wrote: > : > + Openssh isn't 100% compatible with ssh, so some care needs to > : > + be taken in its operation. > : > : This sounds bad. Are you referring to the -o syntax differences, or actual > : incompatabilities? There have been unsubstantiated reports of > : interoperability problems, but nothing well documented here. > > I'm talking about the -o syntax difference specifically. How does the > following sound? [SNIP] > + Openssh's command line parsing isn't 100% compatible with ssh, > + so some care needs to be taken in its operation. I'd leave it saying that it isn't 100% compatible - it may sound bad but it's true. There are several other things that aren't the same: default options are different, some options have been removed (AllowHosts is one that I know of), it produces warning messages where the old ssh wouldn't have. I'm sure there are other differences too. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13:15:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 0B34337C07D; Mon, 6 Mar 2000 13:15:34 -0800 (PST) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.10.0.Beta12/8.10.0.Beta12) id e26LFEq68238; Mon, 6 Mar 2000 13:15:14 -0800 (PST) Message-Id: <200003062115.e26LFEq68238@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.1-cvs 10/15/1999 To: David Malone Cc: Warner Losh , Kris Kennaway , bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <20000306210349.A73029@walton.maths.tcd.ie> References: <200003062032.NAA61484@harmony.village.org> <20000306210349.A73029@walton.maths.tcd.ie> Comments: In-reply-to David Malone message dated "Mon, 06 Mar 2000 21:03:50 +0000." From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1751912798P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 06 Mar 2000 13:15:14 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_1751912798P Content-Type: text/plain; charset=us-ascii If memory serves me right, David Malone wrote: > On Mon, Mar 06, 2000 at 01:32:00PM -0700, Warner Losh wrote: > > > : > + Openssh isn't 100% compatible with ssh, so some care needs to > > : > + be taken in its operation. > > : > > : This sounds bad. Are you referring to the -o syntax differences, or actua > l > > : incompatabilities? There have been unsubstantiated reports of > > : interoperability problems, but nothing well documented here. > > > > I'm talking about the -o syntax difference specifically. How does the > > following sound? > > [SNIP] > > > + Openssh's command line parsing isn't 100% compatible with ssh, > > + so some care needs to be taken in its operation. > > I'd leave it saying that it isn't 100% compatible - it may sound > bad but it's true. There are several other things that aren't the > same: default options are different, some options have been removed > (AllowHosts is one that I know of), it produces warning messages > where the old ssh wouldn't have. I'm sure there are other differences > too. Rather than let the users guess at various incompatabilities (imagined and real), why not give them a few examples, as in your (David's) last message? "Care needs to be taken when converting from ssh to OpenSSH. OpenSSH's command-line parsing isn't 100% compatible with ssh, some of the default options have been changed, some options (such as AllowHosts) have been removed, and it produces a few more warning messages than ssh." Bruce. --==_Exmh_1751912798P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: eGz8t7RAhR1hLdezOH4kUK6TAAlKdk46 iQA/AwUBOMQf4tjKMXFboFLDEQJxewCgpDjLUDw5STEZKecVJA42gg2NGZoAoM85 j1+jqyF/TgdRSEMQwd1JHMAx =8+8A -----END PGP SIGNATURE----- --==_Exmh_1751912798P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13:21: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from bugg.strangled.net (c705742-a.htfdw1.ct.home.com [24.2.137.94]) by hub.freebsd.org (Postfix) with ESMTP id 34A4B37C004 for ; Mon, 6 Mar 2000 13:20:56 -0800 (PST) (envelope-from bugg@bugg.strangled.net) Received: (from bugg@localhost) by bugg.strangled.net (8.9.3/8.9.3) id QAA21103; Mon, 6 Mar 2000 16:23:34 -0500 (EST) (envelope-from bugg) Date: Mon, 6 Mar 2000 16:23:33 -0500 From: Dan Papasian To: Dave Boers Cc: Arun Sharma , freebsd-current@FreeBSD.ORG Subject: Re: current lockups Message-ID: <20000306162333.A21037@moe.c705742-a.htfdw1.ct.home.com> References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000306202718.A26973@relativity.student.utwente.nl>; from djb@wit389306.student.utwente.nl on Mon, Mar 06, 2000 at 08:27:18PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 08:27:18PM +0100, Dave Boers wrote: > > on a Dual celeron box (BP6) with UDMA66 enabled. > > Finally. I've been complaining about this on several occasions. I'm also > running UDMA66 and Dual Celeron BP6. No overclocking. Can you people reproduce this on a kernel without SMP enabled? Perhaps there is a locking issue? However, that'd lead to a panic I'd imagine.. So see if you can reproduce this with one CPU running so we can at least eliminate one of the variables. -Dan Papasian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13:25:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.alpha1.net (mail.alpha1.net [216.88.112.3]) by hub.freebsd.org (Postfix) with ESMTP id 468BE37BFB4 for ; Mon, 6 Mar 2000 13:25:14 -0800 (PST) (envelope-from marius@alpha1.net) Received: from beaker.alpha1.net (marius@beaker.alpha1.net [216.88.237.14]) by mail.alpha1.net (8.9.3/8.9.3) with ESMTP id PAA22029; Mon, 6 Mar 2000 15:24:58 -0600 Date: Mon, 6 Mar 2000 15:24:57 -0600 (CST) From: Marius Strom To: Dan Papasian Cc: Dave Boers , Arun Sharma , freebsd-current@FreeBSD.ORG Subject: Re: current lockups In-Reply-To: <20000306162333.A21037@moe.c705742-a.htfdw1.ct.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm willing to bet a nickel (perhaps more) you people are running non-IBM UDMA66 drives on that BP6. Seems that most UDMA66 drives are not actually UDMA66 compliant, and they only drives that have been reported successful on the BP6 are IBM. Try taking your HD's off the UDMA66 controller and put them on the Standard UDMA33 controllers, and it should clear things up. -- Marius Strom Professional Geek/Unix System Administrator Alpha1 Internet http://www.marius.org/marius.pgp 0x42C74CBA *UPDATED PGP KEY 2/24/2000* In theory, there is no difference between theory and practice... ...In practice, there is a big difference. On Mon, 6 Mar 2000, Dan Papasian wrote: > On Mon, Mar 06, 2000 at 08:27:18PM +0100, Dave Boers wrote: > > > on a Dual celeron box (BP6) with UDMA66 enabled. > > > > Finally. I've been complaining about this on several occasions. I'm also > > running UDMA66 and Dual Celeron BP6. No overclocking. > > Can you people reproduce this on a kernel without SMP enabled? > Perhaps there is a locking issue? However, that'd lead to a panic I'd imagine.. > So see if you can reproduce this with one CPU running so we can at least > eliminate one of the variables. > > -Dan Papasian > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13:34:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.monterey.edu (firstclass.monterey.edu [198.189.5.44]) by hub.freebsd.org (Postfix) with ESMTP id AC4D537BA4D for ; Mon, 6 Mar 2000 13:34:10 -0800 (PST) (envelope-from Nora_Parker@monterey.edu) Message-id: Date: Mon, 06 Mar 2000 13:31:10 -0800 Subject: Re(2): IPv6: can a link-site (or global) address be configured in rc.conf? To: ab@astralblue.com Cc: fenner@research.att.com, jose@we.lc.ehu.es, current@freebsd.org, 6bone@isi.edu From: Nora_Parker@monterey.edu (Nora Parker) References: In-Reply-To: MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to get an ipv6 address. I tried a local source but have not heard any reply. Can anyone help me out with an address. I am a student at Cal State Monterey Bay working on a capstone project. I would appreciate any help in this matter. Thank You To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13:38: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 266F237BA03 for ; Mon, 6 Mar 2000 13:38:02 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id A973E5D7D; Mon, 6 Mar 2000 22:38:11 +0100 (CET) Date: Mon, 6 Mar 2000 22:38:11 +0100 From: Dave Boers To: Marius Strom Cc: Dan Papasian , Dave Boers , Arun Sharma , freebsd-current@FreeBSD.ORG Subject: Re: current lockups Message-ID: <20000306223811.A27499@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000306162333.A21037@moe.c705742-a.htfdw1.ct.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from marius@alpha1.net on Mon, Mar 06, 2000 at 03:24:57PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Marius Strom had the courage to say: > I'm willing to bet a nickel (perhaps more) you people are running non-IBM > UDMA66 drives on that BP6. Seems that most UDMA66 drives are not actually > UDMA66 compliant, and they only drives that have been reported successful > on the BP6 are IBM. Try taking your HD's off the UDMA66 controller and > put them on the Standard UDMA33 controllers, and it should clear things > up. I'm interested in the sources of your statement about IBM drivers vs. non IBM drives. In my case, I have a WD 18.2 Gb 7200 rpm disk which has been reported to be identical to the IBM 18.2 Gb 7200 rpm disk on more than one occasion. And by the way, my system has been running quite stable before January 2000 with the same disk on the same controller and the same mainboard. Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13:38:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 570E137BAAC for ; Mon, 6 Mar 2000 13:38:22 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id WAA12037 for freebsd-current@freebsd.org; Mon, 6 Mar 2000 22:38:21 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id WAA15722 for freebsd-current@freebsd.org; Mon, 6 Mar 2000 22:37:22 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: openssh question Date: 6 Mar 2000 22:37:22 +0100 Message-ID: <8a18ei$fb1$1@bigeye.rhein-neckar.de> References: To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods wrote: > Now that openssh is in the base system, I assume it will no longer > be in the ports. I expect the port to be maintained for the remaining lifetime of the 3.x branch. This is of no concern to 4.x users, of course. > How do we update it, ie, when a updated version comes out. OpenSSH doesn't really have releases. The upstream version is straight out of the OpenBSD repository. I assume several of our developers monitor the OpenBSD commits and will carry over any changes. > I would rather not make world just to update that. How do you handle updates to any other part of the system? Why do you consider openssh a special case? You can usually update individual parts of FreeBSD without doing a "make world". cd /usr/src/... && make -jX install && make clean. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13:46:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.alpha1.net (mail.alpha1.net [216.88.112.3]) by hub.freebsd.org (Postfix) with ESMTP id 365EE37B9F8 for ; Mon, 6 Mar 2000 13:46:32 -0800 (PST) (envelope-from marius@alpha1.net) Received: from beaker.alpha1.net (marius@beaker.alpha1.net [216.88.237.14]) by mail.alpha1.net (8.9.3/8.9.3) with ESMTP id PAA25192; Mon, 6 Mar 2000 15:46:25 -0600 Date: Mon, 6 Mar 2000 15:46:25 -0600 (CST) From: Marius Strom To: Dave Boers Cc: Dan Papasian , Arun Sharma , freebsd-current@FreeBSD.ORG Subject: Re: current lockups In-Reply-To: <20000306223811.A27499@relativity.student.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dave, Well, there was a discussion a few weeks back with Soren Schmidt and a few others. I believe the conclusion was made that this occurred with most WD drives (interesting about the WD == IBM part, I did notice he mentioned that in -current a few weeks ago as well). I had a WD20 gig that would just hang, and a number of other people had similar problems. (Theirs would log "Lost Disk Contact" in the dmesg as their root dev wasn't a UDMA66 drive) Unfortunately, the discussions occurred while the mailing list archive was kaput (WD Drive on UDMA66? =]) so it's not archived where I can find it. Seems to only happen with the ata driver, IIRC. -- Marius Strom Professional Geek/Unix System Administrator Alpha1 Internet http://www.marius.org/marius.pgp 0x42C74CBA *UPDATED PGP KEY 2/24/2000* In theory, there is no difference between theory and practice... ...In practice, there is a big difference. On Mon, 6 Mar 2000, Dave Boers wrote: > It is rumoured that Marius Strom had the courage to say: > > I'm willing to bet a nickel (perhaps more) you people are running non-IBM > > UDMA66 drives on that BP6. Seems that most UDMA66 drives are not actually > > UDMA66 compliant, and they only drives that have been reported successful > > on the BP6 are IBM. Try taking your HD's off the UDMA66 controller and > > put them on the Standard UDMA33 controllers, and it should clear things > > up. > > I'm interested in the sources of your statement about IBM drivers vs. non > IBM drives. > > In my case, I have a WD 18.2 Gb 7200 rpm disk which has been reported to be > identical to the IBM 18.2 Gb 7200 rpm disk on more than one occasion. And > by the way, my system has been running quite stable before January 2000 > with the same disk on the same controller and the same mainboard. > > Regards, > > Dave Boers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13:48: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 5FC0F37BA03; Mon, 6 Mar 2000 13:47:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5D7382E815C; Mon, 6 Mar 2000 13:47:58 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 13:47:58 -0800 (PST) From: Kris Kennaway To: Warner Losh Cc: bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <200003062032.NAA61484@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, Warner Losh wrote: > +20000225: > + OpenSSH has been added to FreeBSD. This may conflict with the > + ssh port since it installs binaries into /usr/bin and the port You probably should refer to the ports by name: /usr/ports/security/ssh and /usr/ports/security/openssh (which is obsoleted by having it in the base) > + goes into /usr/local/bin. Most paths have /usr/bin in the path > + before /usr/local/bin, so problems may arrise. If you don't arise > + want OpenSSH, add NO_OPENSSH=yes to your make.conf. > + > + You will also need to enable openssh in /etc/rc.conf if you > + want to run the new servers. You may need to move your key > + and other config files from /usr/local/etc to /etc/ssh. > + > + Openssh's command line parsing isn't 100% compatible with ssh, > + so some care needs to be taken in its operation. This is better. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13:48:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail1.es.net (mail1.es.net [198.128.3.181]) by hub.freebsd.org (Postfix) with SMTP id 819FA37BAC7 for ; Mon, 6 Mar 2000 13:47:58 -0800 (PST) (envelope-from fink@es.net) Received: from truckee.wins.lbl.gov (Truckee) [128.3.9.221] by mail1.es.net with esmtp (Exim 1.81 #2) id 12S5Lz-00009q-01; Mon, 6 Mar 2000 13:47:52 -0800 Message-Id: <4.2.2.20000306134701.00b1aa18@imap2.es.net> X-Sender: rlfink@imap2.es.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 06 Mar 2000 13:47:47 -0800 To: Nora_Parker@monterey.edu (Nora Parker), ab@astralblue.com From: Bob Fink Subject: Re(2): IPv6: can a link-site (or global) address be configured in rc.conf? Cc: fenner@research.att.com, jose@we.lc.ehu.es, current@freebsd.org, 6bone@ISI.EDU In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:31 PM 3/6/2000 -0800, Nora Parker wrote: >I am trying to get an ipv6 address. I tried a local source but have not >heard any reply. Can anyone help me out with an address. I am a student >at Cal State Monterey Bay working on a capstone project. I would >appreciate any help in this matter. Try the site. Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13:50:34 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A68FE37BD1A; Mon, 6 Mar 2000 13:50:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A3C392E815C; Mon, 6 Mar 2000 13:50:30 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 13:50:30 -0800 (PST) From: Kris Kennaway To: David Malone Cc: Warner Losh , bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <20000306210349.A73029@walton.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, David Malone wrote: > I'd leave it saying that it isn't 100% compatible - it may sound > bad but it's true. There are several other things that aren't the > same: default options are different, some options have been removed > (AllowHosts is one that I know of), it produces warning messages > where the old ssh wouldn't have. I'm sure there are other differences > too. None of these affect the operation of OpenSSH in your network. Sure, you have to check the config files when you migrate to it, but the point is it's not incompatible with other SSH implementations, and we don't want to scare people into thinking it has weird lurking bugs and they'd better not use it. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 13:54:39 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id CBC9B37BE1C; Mon, 6 Mar 2000 13:54:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C924B2E815C; Mon, 6 Mar 2000 13:54:34 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 13:54:34 -0800 (PST) From: Kris Kennaway To: Christian Weisgerber Cc: freebsd-current@freebsd.org Subject: Re: openssh question In-Reply-To: <8a18ei$fb1$1@bigeye.rhein-neckar.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 6 Mar 2000, Christian Weisgerber wrote: > > Now that openssh is in the base system, I assume it will no longer > > be in the ports. > > I expect the port to be maintained for the remaining lifetime of > the 3.x branch. This is of no concern to 4.x users, of course. Correct. We should probably mark the port BROKEN for 4.x and ask people to install the system version, which will likely be better supported. e.g. we don't support Perl5 in ports any more, either. > > How do we update it, ie, when a updated version comes out. > > OpenSSH doesn't really have releases. The upstream version is > straight out of the OpenBSD repository. I assume several of our > developers monitor the OpenBSD commits and will carry over any > changes. Right. Whenever something significant changes in the "upstream" version we'll update ours too. If you keep an eye on the commit messages you'll know when you might want to rebuild it, if you want to aggressively track OpenSSH but not track make world. > > I would rather not make world just to update that. > > How do you handle updates to any other part of the system? Why do > you consider openssh a special case? > > You can usually update individual parts of FreeBSD without doing > a "make world". cd /usr/src/... && make -jX install && make clean. Yep. In the case of SSH you might also need to rebuild secure/lib/libssh as well as secure/usr.bin/. Write a little script to do it if you like :-) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14: 1:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id D144C37BADF for ; Mon, 6 Mar 2000 14:01:17 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id 54E9F5D7D; Mon, 6 Mar 2000 23:01:27 +0100 (CET) Date: Mon, 6 Mar 2000 23:01:27 +0100 From: Dave Boers To: Marius Strom Cc: Dan Papasian , Arun Sharma , freebsd-current@FreeBSD.ORG Subject: Re: current lockups Message-ID: <20000306230127.A27622@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000306223811.A27499@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from marius@alpha1.net on Mon, Mar 06, 2000 at 03:46:25PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Marius Strom had the courage to say: > Well, there was a discussion a few weeks back with Soren Schmidt and a few > others. I believe the conclusion was made that this occurred with most WD > drives (interesting about the WD == IBM part, I did notice he mentioned > that in -current a few weeks ago as well). I had a WD20 gig that would > just hang, and a number of other people had similar problems. (Theirs > would log "Lost Disk Contact" in the dmesg as their root dev wasn't a > UDMA66 drive) Interesting. I'll check my own archives of -current to see if I can find the discussion. I always thought that the "Lost Disk Contact" messages were due to the disk recalibrating itself after six days of continued use. After Soren increased the timeout from 5 to 10 seconds, I never saw the problem again, IIRC. For the record, (see my mail elsewhere in the thread) I have recently added an U2W SCSI harddisk to the system (because I found that the UDMA effectively cuts off memory access for the two celeron's for long times and because the celeron's haven't got nearly enough cache they are effectively waiting for the IDE disk all the time) and I'm now running my root filesystem on that drive (as well as most of my other important filesystems). So I guess that if your assertion is right then my problem should have gone away now. I haven't seen any "Lost Disk Contact" messages recently, however, though the UDMA66 drive is still connected. BTW, are there any people out there that have similar hangs and are NOT using UDMA66 or the ATA driver ? > Unfortunately, the discussions occurred while the mailing list archive was > kaput (WD Drive on UDMA66? =]) so it's not archived where I can find it. :-) Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14: 4:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.alpha1.net (mail.alpha1.net [216.88.112.3]) by hub.freebsd.org (Postfix) with ESMTP id 6A69B37BB25 for ; Mon, 6 Mar 2000 14:04:41 -0800 (PST) (envelope-from marius@alpha1.net) Received: from beaker.alpha1.net (marius@beaker.alpha1.net [216.88.237.14]) by mail.alpha1.net (8.9.3/8.9.3) with ESMTP id QAA28240; Mon, 6 Mar 2000 16:04:35 -0600 Date: Mon, 6 Mar 2000 16:04:34 -0600 (CST) From: Marius Strom To: Dave Boers Cc: Dan Papasian , Arun Sharma , freebsd-current@FreeBSD.ORG Subject: Re: current lockups In-Reply-To: <20000306230127.A27622@relativity.student.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Interesting. I'll check my own archives of -current to see if I can find > the discussion. I always thought that the "Lost Disk Contact" messages were > due to the disk recalibrating itself after six days of continued use. After > Soren increased the timeout from 5 to 10 seconds, I never saw the problem > again, IIRC. Six days? Nah.. I had the problem occur anywhere from 5 minutes to 12 hours after a system boot. Moved the 20G WD to UDMA33 channel, works flawlessly. Usually, I could reproduce the problem doing heavy disk I/O. However, I one time was able to make it through a "make buildworld", so that's not entirely true either. > > For the record, (see my mail elsewhere in the thread) I have recently added > an U2W SCSI harddisk to the system (because I found that the UDMA > effectively cuts off memory access for the two celeron's for long times and > because the celeron's haven't got nearly enough cache they are effectively > waiting for the IDE disk all the time) and I'm now running my root > filesystem on that drive (as well as most of my other important > filesystems). So I guess that if your assertion is right then my problem > should have gone away now. I haven't seen any "Lost Disk Contact" messages > recently, however, though the UDMA66 drive is still connected. > For my record, I was unable to get dmesg output because the system was completely hung. Other people could get it because they had other drives to write logging information too when the UDMA drive was locked. --- Marius Strom Professional Geek/Unix System Administrator Alpha1 Internet http://www.marius.org/marius.pgp 0x42C74CBA *UPDATED PGP KEY 2/24/2000* In theory, there is no difference between theory and practice... ...In practice, there is a big difference. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14:13:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from axp5.physik.fu-berlin.de (axp5.physik.fu-berlin.de [160.45.34.3]) by hub.freebsd.org (Postfix) with ESMTP id DE92137BADF for ; Mon, 6 Mar 2000 14:13:23 -0800 (PST) (envelope-from dieringe@sirius.physik.fu-berlin.de) Received: from sirius.physik.fu-berlin.de (sirius.physik.fu-berlin.de [160.45.34.162]) by axp5.physik.fu-berlin.de (8.9.1a/8.9.1) with ESMTP id XAA08785 for ; Mon, 6 Mar 2000 23:13:18 +0100 (MET) Received: from localhost (dieringe@localhost) by sirius.physik.fu-berlin.de (8.9.1a/8.9.1) with ESMTP id XAA02364 for ; Mon, 6 Mar 2000 23:13:17 +0100 (MET) Date: Mon, 6 Mar 2000 23:13:17 +0100 (MET) From: Martin Dieringer To: current@freebsd.org Subject: vinum: CDEV_MAJOR undeclared Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG when making buildworld, I get an error: ===> sbin/vinum cc -O2 -pipe -m486 -I/usr/src/sbin/vinum/../../sys -Wall -DVINUMDEBUG -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sbin/vinum/v.c /usr/src/sbin/vinum/v.c: In function `make_devices': /usr/src/sbin/vinum/v.c:494: `CDEV_MAJOR' undeclared (first use in this function) /usr/src/sbin/vinum/v.c:494: (Each undeclared identifier is reported only once /usr/src/sbin/vinum/v.c:494: for each function it appears in.) *** Error code 1 1 error Am I missing some headerfile? I cvsup-ed current yesterday and did an install-world about a week ago. martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14:21:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 2866D37BB10 for ; Mon, 6 Mar 2000 14:21:47 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id QAA19644; Mon, 6 Mar 2000 16:21:06 -0600 (CST) (envelope-from dick) Date: Mon, 6 Mar 2000 16:21:06 -0600 From: "Richard Seaman, Jr." To: Bob Fink Cc: "Eugene M. Kim" , Bill Fenner , jose@we.lc.ehu.es, FreeBSD-current Mailing List , 6bone@ISI.EDU Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? Message-ID: <20000306162106.B347@tar.com> References: <200003061628.IAA19733@windsor.research.att.com> <4.2.2.20000306091731.02b974d8@imap2.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <4.2.2.20000306091731.02b974d8@imap2.es.net>; from fink@es.net on Mon, Mar 06, 2000 at 09:22:45AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 09:22:45AM -0800, Bob Fink wrote: > Please read, then ask any questions you may have. 6to4 is currently > supported, and there are relay routers up and running. My apologies if I sound like I need "IPv6 for Dummies". Just to clarify. You mean that 6to4 is currently supported in FreeBSD/KAME? Of course, I'm not quite sure what I mean by this. I guess, if I configure a FreeBSD/KAME host as an IPv6 router, will the router automatically do the IPv6->IPv4 encapsulation when it encounters a destination prefix of 2002::/16 and vice versa for incoming packets? Or, do I need to configure a pseudo interface somehow (gif doesn't look quite like the right thing?). Also, will FreeBSD/KAME hosts (both router and non-router hosts) somehow automatically do the proper address selection algorithm when they encounter multiple IPv6 addresses, or is that an application level requirement? Also, if I have (for example) IPv4 addresses of 204.95.187/24, I assume I can use any of the 2002:[V4ADDR]:/48 prefixes within my allocation, but for external 6to4 connectivity I should probably choose the V4ADDR of the external interface of the 6to4 router? And, finally, do some of the 6to4 relay routers that are "up and running" serve small isolated sites? I assume the best case is that one's ISP provides IPv6 connectivity in some shape or form. But, if thats not the case, I assume the main options are IPv6-IPv4 tunnel to a co-operative IPv6 site, or 6to4 with a default route to a relay router (who I assume must configure a static route back?). Or, run a more sophisticated routing protocol (BGP), but thats a little much for me, I think. Of course, if everyone configures 6to4 (or at least everyone you want to reach) then am I correct that you don't really need 6to4 "relay" routers? This is only for reaching native IPv6 sites without 6to4 addresses? Thanks. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14:32:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id DBDF937BA4D for ; Mon, 6 Mar 2000 14:32:06 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115229>; Tue, 7 Mar 2000 09:32:54 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: current lockups In-reply-to: ; from me@camtech.net.au on Mon, Mar 06, 2000 at 09:39:11PM +1100 To: thyerm@camtech.net.au Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Mar7.093254est.115229@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <20000305104515.A17749@moe.c705742-a.htfdw1.ct.home.com> Date: Tue, 7 Mar 2000 09:32:53 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Mar-06 21:39:11 +1100, Matthew Sean Thyer wrote: >My computer had been stable all winter (with setiathome runnning full >time) but suddenly come the Australian summer it started freezing. And it's been the coldest summer for something like 5 years... > How about these Peltier (sp ?) cooling devices I have heard about ? A Peltier cell is just a semiconductor heat pump. It effectively just reduces the junction-to-heatsink thermal resistance, allowing you (in theory) to use a less efficient heatsink (or have the CPU run cooler with the same heatsink. The downside is they they're relatively inefficient - your power supply will need to supply an extra 3-4A at 12v and you need to dissipate that extra power. Unless you significantly improve the airflow through the case, you'll probably find that the internal temperature rises significantly - further stressing everything except the CPU. Note that the chip that most needs cooling may not be the CPU - the big support chips can also run very hot. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14:45:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 8B74D37BB25 for ; Mon, 6 Mar 2000 14:45:06 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115210>; Tue, 7 Mar 2000 09:45:55 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: current lockups In-reply-to: <20000306202718.A26973@relativity.student.utwente.nl>; from djb@wit389306.student.utwente.nl on Tue, Mar 07, 2000 at 06:29:17AM +1100 To: Dave Boers Cc: Arun Sharma , freebsd-current@FreeBSD.ORG Message-Id: <00Mar7.094555est.115210@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> Date: Tue, 7 Mar 2000 09:45:55 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Mar-07 06:29:17 +1100, Dave Boers wrote: >It is rumoured that Arun Sharma had the courage to say: >> Compiling Mozilla with make -j 2 got -current to lock up, twice in >> succession. I'm running a fairly recent snapshot (a week or two old) >> on a Dual celeron box (BP6) with UDMA66 enabled. > >Finally. I've been complaining about this on several occasions. I'm also >running UDMA66 and Dual Celeron BP6. No overclocking. Later postings mention possible problems with UDMA66. The other possibility that has been discussed recently is potential priority inversions for processes using rtptio and idprio. Note that ntpd will use rtprio if the Posix P1003.1b extensions aren't enabled in the kernel. (These were enabled by default in GENERIC on i386 in mid-January). If you have the new ntpd (rather than xntpd) and are running a kernel without options P1003_1B, _KPOSIX_PRIORITY_SCHEDULING and _KPOSIX_VERSION=199309L, you could potentially get a lockup due to a priority inversion. (Though I think the probability is very small). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14:46:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3F5B437BAA8 for ; Mon, 6 Mar 2000 14:46:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA11151; Mon, 6 Mar 2000 23:45:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Jeremy Cc: thyerm@camtech.net.au, freebsd-current@FreeBSD.ORG Subject: Re: current lockups In-reply-to: Your message of "Tue, 07 Mar 2000 09:32:53 +1100." <00Mar7.093254est.115229@border.alcanet.com.au> Date: Mon, 06 Mar 2000 23:45:49 +0100 Message-ID: <11149.952382749@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00Mar7.093254est.115229@border.alcanet.com.au>, Peter Jeremy writes : >> How about these Peltier (sp ?) cooling devices I have heard about ? > >A Peltier cell is just a semiconductor heat pump. It effectively just >reduces the junction-to-heatsink thermal resistance, allowing you (in >theory) to use a less efficient heatsink (or have the CPU run cooler >with the same heatsink. This is actually not true, quite the contrary in fact: You need a better heat-sink with a Peltier because of the significant electrical power you pump into it. As a general rule you can expect to *raise* your CPU temperature if you put a peltier under anything less than a *very good* heat-sink. Example: A Celeron 500 disipates about 25W An average heatsink is about .8 C/W delta-T becomes 25W * .8C/W = 20C At 30C ambient that becomes 50C CPU temperature. Now, add a peltier. To remove 25W and keep a 25C temperature difference we need to feed it about 50W Now the heatsink has to deal with 25 + 50 W and the delta-T becomes: (25W + 50W) * .8C/W = 60C Subtract the 25C difference from the peltier and add the ambient temperature and we find: 30C + 60C - 25C = 65C We just raised our CPU temperature about 15 C :-( -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14:52:10 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 680CD37BB25; Mon, 6 Mar 2000 14:52:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6585A2E815C; Mon, 6 Mar 2000 14:52:08 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 14:52:08 -0800 (PST) From: Kris Kennaway To: Arindum Mukerji Cc: current@freebsd.org Subject: Re: ssh strangeness in -current... In-Reply-To: <20000306160912.A1303@earth.execpc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, Arindum Mukerji wrote: > Also, going from an OpenSSH 1.2.2 box to an SSH-1.2.27 box is fine - it > coughs up a hairball when going to the F-Secure 1.3.7 commercial variant > though. Ahh, so you can use the OpenSSH client to connect to some servers, but not the F-Secure one? That would definitely be a bug you should report to the OpenSSH developers. Is anyone else in the position to test this? Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14:53: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7153937BAA8; Mon, 6 Mar 2000 14:52:57 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA56002; Mon, 6 Mar 2000 15:52:52 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA62626; Mon, 6 Mar 2000 15:52:40 -0700 (MST) Message-Id: <200003062252.PAA62626@harmony.village.org> To: Kris Kennaway Subject: Re: ssh strangeness in -current... Cc: bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Mar 2000 12:29:01 PST." References: Date: Mon, 06 Mar 2000 15:52:39 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this any better? I've removed the emotionally charged compatibility word. 20000225: OpenSSH has been added to FreeBSD. This may conflict with the ports/security/ssh port since it installs binaries into /usr/bin and the port goes into /usr/local/bin. Most paths have /usr/bin in the path before /usr/local/bin, so problems may arrise. If you don't want OpenSSH, add NO_OPENSSH=yes to your make.conf. You will also need to enable openssh in /etc/rc.conf if you want to run the new servers. You may need to move your key and other config files from /usr/local/etc to /etc/ssh. Openssh's command line parsing, available options and default settings aren't the same as ssh, so some care needs to be taken in its operation. One should do a full audit of all configuration settings. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14:55: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 317C837BAA8; Mon, 6 Mar 2000 14:55:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 2F70E2E8110; Mon, 6 Mar 2000 14:55:05 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 14:55:05 -0800 (PST) From: Kris Kennaway To: Warner Losh Cc: "James E. Pace" , current@FreeBSD.ORG Subject: Re: /usr/bin/ssh and SOCKS In-Reply-To: <200003062029.NAA61443@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, Warner Losh wrote: > Sure. Here's what I have in my uncommitted tree. It assumes that you > have socks installed already. Known to work with the nec port, not > known one way or the other on dante. > > Oh, there's lots of warnings from this, but it does work. I'd like to get this committed - I'll try and take a look at it tonight, time permitting. I would definitely like to allow SSH to work with dante, though, since that's a better (BSDL) alternative than the restricted NEC version. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14:57:57 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 33D1E37BB41; Mon, 6 Mar 2000 14:57:55 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 31CBF2E8110; Mon, 6 Mar 2000 14:57:55 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 14:57:55 -0800 (PST) From: Kris Kennaway To: Warner Losh Cc: bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <200003062252.PAA62626@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, Warner Losh wrote: > Is this any better? I've removed the emotionally charged > compatibility word. Some more picking :) > 20000225: > OpenSSH has been added to FreeBSD. This may conflict with the > ports/security/ssh port since it installs binaries into > /usr/bin and the port goes into /usr/local/bin. Most paths > have /usr/bin in the path before /usr/local/bin, so problems > may arrise. If you don't want OpenSSH, add NO_OPENSSH=yes to arise :) > your make.conf. > > You will also need to enable openssh in /etc/rc.conf if you OpenSSH > want to run the new servers. You may need to move your key host key > and other config files from /usr/local/etc to /etc/ssh. > > Openssh's command line parsing, available options and default OpenSSH > settings aren't the same as ssh, so some care needs to be > taken in its operation. One should do a full audit of all > configuration settings. Apart from those small nits I think it's fine. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 14:59:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 3121337BB83 for ; Mon, 6 Mar 2000 14:59:12 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id CDB2C5D7D; Mon, 6 Mar 2000 23:59:21 +0100 (CET) Date: Mon, 6 Mar 2000 23:59:21 +0100 From: Dave Boers To: Peter Jeremy Cc: Dave Boers , Arun Sharma , freebsd-current@FreeBSD.ORG Subject: Re: current lockups Message-ID: <20000306235921.A27904@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> <00Mar7.094555est.115210@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <00Mar7.094555est.115210@border.alcanet.com.au>; from peter.jeremy@alcatel.com.au on Tue, Mar 07, 2000 at 09:45:55AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Peter Jeremy had the courage to say: > Note that ntpd will use rtprio if the Posix P1003.1b extensions aren't > enabled in the kernel. (These were enabled by default in GENERIC on > i386 in mid-January). If you have the new ntpd (rather than xntpd) > and are running a kernel without options P1003_1B, > _KPOSIX_PRIORITY_SCHEDULING and _KPOSIX_VERSION=199309L, you could > potentially get a lockup due to a priority inversion. (Though I > think the probability is very small). I don't use ntpd (I use ntpdate) and I do have those options enabled in my kernel (all three of them). IIRC they are needed to get either cdrdao or cdrecord to work. Seems that everything points to UDMA66 so far... Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 15: 9:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4C38637BB2B; Mon, 6 Mar 2000 15:09:14 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA56081; Mon, 6 Mar 2000 16:09:13 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA88816; Mon, 6 Mar 2000 16:09:04 -0700 (MST) Message-Id: <200003062309.QAA88816@harmony.village.org> To: Kris Kennaway Subject: Re: /usr/bin/ssh and SOCKS Cc: "James E. Pace" , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Mar 2000 14:55:05 PST." References: Date: Mon, 06 Mar 2000 16:09:04 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : On Mon, 6 Mar 2000, Warner Losh wrote: : : > Sure. Here's what I have in my uncommitted tree. It assumes that you : > have socks installed already. Known to work with the nec port, not : > known one way or the other on dante. : > : > Oh, there's lots of warnings from this, but it does work. : : I'd like to get this committed - I'll try and take a look at it tonight, : time permitting. I would definitely like to allow SSH to work with dante, : though, since that's a better (BSDL) alternative than the restricted NEC : version. Mark M has seen these patches and has asked that I hold off until after the freeze to commit them. At this point, I'm inclined to agree with him. They definitely do not work with Dante, because dante doesn't seem to install any header files, like the nec socks5 port does. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 15:11:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id A1BCA37BBA3 for ; Mon, 6 Mar 2000 15:11:55 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id F00FB199D; Mon, 6 Mar 2000 15:11:54 -0800 (PST) Date: Mon, 6 Mar 2000 15:11:54 -0800 From: Chris Piazza To: Dave Boers Cc: Peter Jeremy , Arun Sharma , freebsd-current@FreeBSD.ORG Subject: Re: current lockups Message-ID: <20000306151154.A21350@norn.ca.eu.org> References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> <00Mar7.094555est.115210@border.alcanet.com.au> <20000306235921.A27904@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000306235921.A27904@relativity.student.utwente.nl>; from djb@wit389306.student.utwente.nl on Mon, Mar 06, 2000 at 11:59:21PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 11:59:21PM +0100, Dave Boers wrote: > It is rumoured that Peter Jeremy had the courage to say: > > Note that ntpd will use rtprio if the Posix P1003.1b extensions aren't > > enabled in the kernel. (These were enabled by default in GENERIC on > > i386 in mid-January). If you have the new ntpd (rather than xntpd) > > and are running a kernel without options P1003_1B, > > _KPOSIX_PRIORITY_SCHEDULING and _KPOSIX_VERSION=199309L, you could > > potentially get a lockup due to a priority inversion. (Though I > > think the probability is very small). > > I don't use ntpd (I use ntpdate) and I do have those options enabled in my > kernel (all three of them). IIRC they are needed to get either cdrdao or > cdrecord to work. > > Seems that everything points to UDMA66 so far... ...maybe in certain combinations. I have a BP6 with dual celerons (466's @ 504) and have had no problems whatsoever. FreeBSD 4.0-CURRENT #4: Sun Mar 5 12:20:41 PST 2000 cpiazza@norn.ca.eu.org:/usr/src/sys/compile/NORN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (503.92-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 268369920 (262080K bytes) avail memory = 256987136 (250964K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 .... ad0: 9765MB [19841/16/63] at ata0-master using UDMA33 ad4: 12949MB [28064/15/63] at ata2-master using UDMA66 acd0: CDROM at ata1-slave using PIO4 ad0 is a DOS drive, ad4 is what I have FreeBSD on. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 15:18:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id B249237BED1 for ; Mon, 6 Mar 2000 15:18:55 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (postfix@[209.69.76.158]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id PAA38039; Mon, 6 Mar 2000 15:18:25 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id DDFFD1A1E; Mon, 6 Mar 2000 18:18:22 -0500 (EST) Date: Mon, 6 Mar 2000 18:18:22 -0500 From: Will Andrews To: bwoods2@uswest.net Cc: Garance A Drosihn , freebsd-current@FreeBSD.ORG, Edwin Kremer Subject: Re: openssh question Message-ID: <20000306181822.C82650@shadow.blackdawn.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from wwoods@cybcon.com on Mon, Mar 06, 2000 at 11:23:45AM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 11:23:45AM -0800, William Woods wrote: > Now that openssh is in the base system, I assume it will no longer be in the > ports. How do we update it, ie, when a updated version comes out. I would > rather not make world just to update that. # cvsup standard-supfile (until 4.0 becomes -stable) # cd /usr/src/secure/usr.bin/ssh && make clean depend all install Someone correct me if I'm wrong. :-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 15:26: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 6269337BBC5 for ; Mon, 6 Mar 2000 15:26:00 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115208>; Tue, 7 Mar 2000 10:26:43 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: [ID 20000306.004] unpack(NaN) big baddaboom In-reply-to: <200003061831.OAA74965@systemics.com>; from iang@systemics.com on Tue, Mar 07, 2000 at 05:35:04AM +1100 To: Ian Grigg Cc: perl5-porters@perl.org, current@FreeBSD.ORG Message-Id: <00Mar7.102643est.115208@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200003061831.OAA74965@systemics.com> Date: Tue, 7 Mar 2000 10:26:42 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Mar-07 05:35:04 +1100, Ian Grigg wrote: >my $packed = "\0\0\xc0\x7f"; >print STDERR "len: ", length($packed), " bytes: ", unpack("H*", $packed), "\n"; >my $float = unpack("f", $packed); >print STDERR "float done\n"; >print STDERR "float: $float\n"; Looking at the resultant core file, perl is getting SIGFPE inside cast_i32() (probably when it tries to cast the NaN to an int). Unfortunately, the code for cast_i32() does not handle NaNs (though it does handle infinity). (And it's not clear what integer value should be associated with NaN in any case). As to whether it should trap or not, that is less clear-cut. FreeBSD takes the view that trying to convert a NaN into an integer is not a sensible operation, so it signals SIGFPE (the i386 NPX gives an invalid operand exception). Other implementations may differ. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 16: 1:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.hcisp.net (Stargate.hcisp.net [208.60.89.18]) by hub.freebsd.org (Postfix) with SMTP id 37CCC37BC62 for ; Mon, 6 Mar 2000 16:01:28 -0800 (PST) (envelope-from tim@mysql.com) Received: (qmail 31138 invoked from network); 7 Mar 2000 00:07:42 -0000 Received: from modem5.hcisp.net (HELO threads.polyesthetic.msg) (208.60.89.71) by stargate.hcisp.net with SMTP; 7 Mar 2000 00:07:42 -0000 Received: (qmail 6241 invoked by uid 1001); 7 Mar 2000 00:01:15 -0000 From: "Thimble Smith" Date: Mon, 6 Mar 2000 19:01:15 -0500 To: Marius Strom Cc: freebsd-current@FreeBSD.ORG Subject: Re: current lockups Message-ID: <20000306190115.A6218@threads.polyesthetic.msg> References: <20000306223811.A27499@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from marius@alpha1.net on Mon, Mar 06, 2000 at 03:46:25PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 03:46:25PM -0600, Marius Strom wrote: >Unfortunately, the discussions occurred while the mailing list archive was >kaput (WD Drive on UDMA66? =]) so it's not archived where I can find it. I think this is the thread you're looking for: http://marc.theaimsgroup.com/?t=95037329500001&w=2&r=1 Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 16: 2:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (f121.law7.hotmail.com [216.33.237.121]) by hub.freebsd.org (Postfix) with SMTP id 8862437BD90 for ; Mon, 6 Mar 2000 16:02:13 -0800 (PST) (envelope-from jmd526@hotmail.com) Received: (qmail 53224 invoked by uid 0); 7 Mar 2000 00:02:12 -0000 Message-ID: <20000307000212.53223.qmail@hotmail.com> Received: from 209.220.228.2 by www.hotmail.com with HTTP; Mon, 06 Mar 2000 16:02:12 PST X-Originating-IP: [209.220.228.2] From: "John Daniels" To: freebsd-current@freebsd.org, freebsd-qa@freebsd.org Subject: FINAL: installation floppies and USB Date: Mon, 06 Mar 2000 19:02:12 EST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: My installation problem has been solved. For those of you who have not been following "Installation floppies and USB," I have written a short synopsis after my description of the resolution and conclusion. SOLUTION: I discovered that my Acer Aspire (model 6140) has two PS/2 ports (for keyboard and floppy). I purchased a PS/2 mouse and keyboard and I no longer get the "keyboard:no" message (instead it says: keyboard:yes)! (in fact, under W98, my USB keyboard and mouse, and my PS/2 keyboard and mouse all work simultaneously.) DISCUSSION: I have not seen any messages about this problem, since it turned into a BIOS discussion with the recommendation that I change the BIOS parameter "PnP OS" from YES to NO. FYI: Changing this parameter made no difference to the installation before or after I hooked up the PS/2 keyboard and mouse. It may make a difference at some later point. The PS/2 ports are hidden by a two different coverings: 1- a plastic molding that is screwed on and, 2- a plastic sheet that is glued on. No consumer-oriented documentation mentions the PS/2 ports. I only found out about them from: 1- a somewhat confusing email in which it was unclear if the writer had the same model and what the exact location of the ports were, 2- the motherboard specs which happened to be on the Acer Aspire website, which prompted a more through searching of my system. I had previously looked at the Acer website and knew it to have very little information. The Acer site doesn’t even have a search function. I only went back hoping to find if there were any BIOS updates (there were none). Two previous calls to Acer support describing my problems installing a new operation system ended with the response: "we don't support Linux or FreeBSD" -- with no mention of the possibility of using the PS/2 ports. As far as BIOS updates: I finally found that Acer Germany provided them (www.acer.de/support/techinfo/bios.htm) -- and one of these BIOS updates was specifically for “Linux support!” (this might also be needed for FreeBSD but I have not downloaded this because I don’t want to fool with my BIOS unless absolutely necessary.) I called Acer USA again but they had no idea that this site existed or why there was a BIOS update for Linux (even though the technician told me that he ran Linux (at home?)) I came to FreeBSD because I had learned that it “supported” USB but like Linux, USB support must be compiled in after installing the GENERIC kernel/system. I had purchased RedHat (before I found FreeBSD), but when I called RedHat support and described my system (with USB keyboard and mouse), I was told only that “Linux doesn’t support USB.” CONCLUSIONS: 1- “-Dh” at the boot loader’s “boot:” allowed the boot loader to load FreeBSD but when the FreeBSD GENERIC kernel was booted, the system may have been looking for input from the PS/2 port. (which I had no knowledge of!). Somehow NetBSD’s GENERIC kernel recognized my USB keyboard, because: 1- it could use the same mechanism as the boot loader (whatever that may be), 2- it has a better ability for finding devices dynamically (at least for keyboards), or 3- it supports USB. 2-Acer needs to provide better documentation. 3-Major Linux vendors, like RedHat, which have aspirations for Linux as a consumer "desktop" OS should have already come across this problem with Acer machines (along with quirkiness of other machines/manufacturers). I would have also liked to see a willingness on their part to find a solution, instead of just spouting policy. There was no willingness from RH or SuSE to provide a boot disk with a recompiled kernel (SuSE sponsored the backport that enables USB support in Linux’s STABLE kernel) 4- Although I was disappointed that FreeBSD did not support USB “out-of-the-box,” I did not expect a lot of support (like I had as a paying customer of RedHat’s). NetBSD’s installation floppy did work and that was my backup but I was encouraged to continue looking into my USB problem because I found that FreeBSD developers were willing to be helpful. This is especially true of John Barton, who first volunteered to help, but also of John Reynolds who elevated my problem to -current and Nick Hibma who responded quickly and cogently. 5- Perhaps I am naïve, but stating that an OS “supports” a device is confusing when that “support” has to be compiled in. There should be a sharper distinction between support out-of-the-box (in GENERIC) and otherwise. Part of the confusion stems from the fact that USB seems so basic. For example, almost any PC will “support” a hard disk and a printer but most people would expect a hard disk to come with the machine. In fact, hardware.txt states: “The FreeBSD kernel on the install floppy contains drivers for every piece of hardware that could conceivably be used to install the rest of the system with.” SYNOPSIS OF PROBLEM: When I booted the installation floopy I got the message: “keyboard: no” The floppy disk drive continued to work, then stopped. I was later told that my output (input,too?) was being redirected. In the file trouble.txt, I found a reference to this problem which said that when the “keyboard:no” message appears, the user should hit the spacebar then type “-Dh” at the “boot:” prompt. This worked -- I could then proceed with the installation until the FreeBSD kernel was booted and a screen appeared asking me if to choose a configuration type: none, full screen, or command line (CLI). Unfortunately, at this point my keyboard was not working. I believe that is because I have a USB keyboard but Nick Hibma has said that they have USB systems that could boot the installation disks without any keyboard problems. Thus, BIOS settings and IRQ settings became an issue: could there be conflicts or settings that needed to be changed? No BIOS setting changes made any difference and I came across the PS/2 ports while I was trying to learn more about BIOS for my system. John ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 16:10: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 2E5CD37BCD0 for ; Mon, 6 Mar 2000 16:09:56 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA707346; Mon, 6 Mar 2000 19:09:42 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <8a18ei$fb1$1@bigeye.rhein-neckar.de> References: <8a18ei$fb1$1@bigeye.rhein-neckar.de> Date: Mon, 6 Mar 2000 19:10:02 -0500 To: naddy@mips.rhein-neckar.de (Christian Weisgerber), freebsd-current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: openssh question Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:37 PM +0100 3/6/00, Christian Weisgerber wrote: >William Woods wrote: > > How do we update it, ie, when a updated version comes out. > >OpenSSH doesn't really have releases. The upstream version is >straight out of the OpenBSD repository. I assume several of our >developers monitor the OpenBSD commits and will carry over any >changes. Out of the OpenBSD repository, or out of the OpenSSH project? Note that www.openssh.COM currently says: *NEW* OpenSSH 1.2.3 released March 6, 2000 which sounds a lot like a new release to me... > > I would rather not make world just to update that. > >How do you handle updates to any other part of the system? Why do >you consider openssh a special case? I think openssh is a bit different than most things in the current base system, in that it is still in rapid development, and some of those developments WILL be of immediate interest to sites using openSSH (in particular, some of the improvements to compatibility with other implementations of ssh1). >You can usually update individual parts of FreeBSD without doing >a "make world". cd /usr/src/... && make -jX install && make clean. While I do think OpenSSH is something of a special case, this answer should be fine for my own purposes. I was also wondering how easy it would be to update just openssh without updating all of the world. Thanks. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 16:31:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id A31EE37BB18 for ; Mon, 6 Mar 2000 16:31:09 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip158.r14.d.bel.nwlink.com (ip158.r14.d.bel.nwlink.com [207.202.175.158]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id QAA05503 for ; Mon, 6 Mar 2000 16:30:56 -0800 (PST) Date: Mon, 6 Mar 2000 16:25:25 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: freebsd-current@FreeBSD.org Subject: single user weirdness Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A strange thing has happened while booting into single user mode. My / filesystem was mounted on wd0s4a even though I have updated /dev and /etc/fstab to use ad0s4a. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 16:34:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from holly.calldei.com (adsl-208-191-146-189.dsl.hstntx.swbell.net [208.191.146.189]) by hub.freebsd.org (Postfix) with ESMTP id 1A4A837BD3C for ; Mon, 6 Mar 2000 16:34:11 -0800 (PST) (envelope-from chris@holly.calldei.com) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id SAA09285; Mon, 6 Mar 2000 18:34:21 -0600 (CST) (envelope-from chris) Date: Mon, 6 Mar 2000 18:34:21 -0600 From: Chris Costello To: Matthew Hunt Cc: Garance A Drosihn , Laurence Berland , Chuck Robey , Alfred Perlstein , Dan Papasian , current@FreeBSD.ORG Subject: Re: which(1), rewritten in C? Message-ID: <20000306183420.A9184@holly.calldei.com> Reply-To: chris@calldei.com References: <38BF334F.2F10D4B0@confusion.net> <20000303120441.A56070@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: <20000303120441.A56070@wopr.caltech.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, March 03, 2000, Matthew Hunt wrote: > and the "type" builtin is too verbose, saying "which is hashed > (/usr/bin/which)." In ksh, `whence' is a bit equivalent to `which' (`type' in ksh is an alias to `whence -v'). From the AT&T ksh manual: whence [ -afpv ] name ... For each name, indicate how it would be interpreted if used as a command name. The -v option produces a more verbose report. The -f options skips the search for functions. The -p option does a path search for name even if name is an alias, a function, or a reserved word. The -a option is similar to the -v option but causes all interpretations of the given name to be reported. Which would yield the following behavior: $ whence pwd pwd $ whence -f pwd pwd $ whence -p pwd /bin/pwd $ whence -v pwd pwd is a shell builtin $ whence -a pwd pwd is a shell builtin pwd is a tracked alias for /bin/pwd -- |Chris Costello |A paperless office has about as much chance as a paperless bathroom. `-------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 16:35:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 3367937B9C1 for ; Mon, 6 Mar 2000 16:35:11 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id QAA14147; Mon, 6 Mar 2000 16:30:37 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id QAA75449; Mon, 6 Mar 2000 16:30:06 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200003070030.QAA75449@whistle.com> Subject: Re: /usr/bin/ssh and SOCKS In-Reply-To: from "James E. Pace" at "Mar 6, 2000 11:37:18 am" To: "James E. Pace" Date: Mon, 6 Mar 2000 16:30:06 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James E. Pace writes: | | I rebuilt -current on Friday, and OpenSSH does not work through a | SOCKS firewall. | | In my make.conf, I have "USE_SOCKS= YES", which is used in the | ports/security/ssh port. As mentioned we have ssh in the base system so your are picking that up. Another alternative is to remove the setuid bits /usr/bin/ssh and then do a "runsocks ssh". LP_PRELOAD in FreeBSD does not work on setuid binaries. This is a security feature. Solaris let's you do a LD_PRELOAD on setuid binaries if the library is from /usr/lib. So on Solaris if the libsocks_sh.so was in /usr/lib then LD_PRELOAD of it would work on setuid binaries like ssh and it would just work without recompiling/linking. However, now that Dante is available and has BSD licensing we could include it in the base OS. Yes it is bloat, but then people could sysinstall behind a Socks firewall and things like ssh etc could be linked to it. There are things I like and don't like with Dante but it is a pretty good package and has a better license. I could do the work if deemed usefull. I don't want to maintain my own branch and we use the Nec implementation here so I don't want to be bouncing between them for no good reason. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 16:42:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id 64C0F37BE1F for ; Mon, 6 Mar 2000 16:42:24 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id RAA16891 for ; Mon, 6 Mar 2000 17:03:29 -0800 (PST) Received: from dbm.wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with SMTP id QAA13821 for ; Mon, 6 Mar 2000 16:33:04 -0800 (PST) (envelope-from dbutter@wireless.net) From: Devin Butterfield Reply-To: dbutter@wireless.net To: current@FreeBSD.ORG Subject: Error: no such 386 instruction: `state' ??? Date: Mon, 6 Mar 2000 16:21:13 -0800 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00030616230000.06832@dbm.wireless.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm running a snap from 2/28: FreeBSD dbm.wireless.net 4.0-20000228-CURRENT FreeBSD 4.0-20000228-CURRENT #2: Fri Mar 3 22:19:33 PST 2000 Often when compiling a port, the process will fail with messages like the following: [...] Compiling smbd/noquotas.c Compiling smbd/reply.c {standard input}: Assembler messages: {standard input}:4939: Error: no such 386 instruction: `state' *** Error code 1 Stop in /usr/ports/net/samba/work/samba-2.0.6/source. *** Error code 1 Stop in /usr/ports/net/samba. *** Error code 1 Stop in /usr/ports/net/samba. *** Error code 1 Stop in /usr/ports/net/samba. *** Error code 1 Stop in /usr/ports/net/samba. [root@dbm /usr/ports/net/samba]# The strange thing is, if I just say "make" again, it will continue to compile where it left off without any problems. Anyone else see these errors? Any Ideas? -- Regards, Devin. P.S. Never had this problem under 3.x. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 16:42:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id 043F037BCC9 for ; Mon, 6 Mar 2000 16:42:40 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id RAA16895 for ; Mon, 6 Mar 2000 17:03:45 -0800 (PST) Received: from dbm.wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with SMTP id QAA13824 for ; Mon, 6 Mar 2000 16:33:20 -0800 (PST) (envelope-from dbutter@wireless.net) From: Devin Butterfield Reply-To: dbutter@wireless.net To: current@FreeBSD.ORG Subject: Error: no such 386 instruction: `state' ??? Date: Mon, 6 Mar 2000 16:25:14 -0800 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00030616310800.06859@dbm.wireless.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am running a current snap from 2/28. FreeBSD dbm.wireless.net 4.0-20000228-CURRENT FreeBSD 4.0-20000228-CURRENT #2: Fri Mar 3 22:19:33 PST 2000 Often when compiling a port, the process fails with messages like the following: [...] Compiling smbd/pipes.c Compiling smbd/predict.c Compiling smbd/noquotas.c Compiling smbd/reply.c {standard input}: Assembler messages: {standard input}:4939: Error: no such 386 instruction: `state' *** Error code 1 Stop in /usr/ports/net/samba/work/samba-2.0.6/source. *** Error code 1 Stop in /usr/ports/net/samba. *** Error code 1 Stop in /usr/ports/net/samba. *** Error code 1 Stop in /usr/ports/net/samba. *** Error code 1 Stop in /usr/ports/net/samba. [root@dbm /usr/ports/net/samba]# The strange thing is, if I just say make again, it will continue to compile where it left off without any problems. Has anyone seen messages like this before? Any ideas? -- Regards, Devin. P.S. I never had this problem under 3.x. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 16:44:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id BA4CB37C03B for ; Mon, 6 Mar 2000 16:44:19 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip158.r14.d.bel.nwlink.com (ip158.r14.d.bel.nwlink.com [207.202.175.158]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id QAA09072 for ; Mon, 6 Mar 2000 16:44:15 -0800 (PST) Date: Mon, 6 Mar 2000 16:38:44 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: freebsd-current@FreeBSD.org Subject: no openssh after build Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 16:47:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id 814B337BE1F for ; Mon, 6 Mar 2000 16:47:27 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id RAA16914 for ; Mon, 6 Mar 2000 17:08:32 -0800 (PST) Received: from dbm.wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with SMTP id QAA13857 for ; Mon, 6 Mar 2000 16:38:08 -0800 (PST) (envelope-from dbutter@wireless.net) From: Devin Butterfield Reply-To: dbutter@wireless.net To: current@FreeBSD.ORG Subject: Re: Error: no such 386 instruction: `state' ??? Date: Mon, 6 Mar 2000 16:41:35 -0800 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <00030616310800.06859@dbm.wireless.net> In-Reply-To: <00030616310800.06859@dbm.wireless.net> MIME-Version: 1.0 Message-Id: <00030616425801.06930@dbm.wireless.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops! Sorry for the double post. :( Kmail got stupid on me... -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 16:54:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id 34C7C37BE96 for ; Mon, 6 Mar 2000 16:54:31 -0800 (PST) (envelope-from saxonww@ufl.edu) Received: from n44-230.dhnet.ufl.edu (gremlin@[128.227.44.230]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id TAA46662; Mon, 6 Mar 2000 19:54:22 -0500 Date: Mon, 6 Mar 2000 19:54:22 -0500 (EST) From: Will Saxon X-Sender: gremlin@localhost To: Devin Butterfield Cc: current@FreeBSD.ORG Subject: Re: Error: no such 386 instruction: `state' ??? In-Reply-To: <00030616230000.06832@dbm.wireless.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was having this problem a few weeks ago while trying to make world. I had just gotten a new motherboard, that was letting me overclock my processor (it offered new bus speeds). I reset the processor to run at its default speed, and I have not seen this error since. So, if you are overclocked at all I would suggest trying to clock it down a little. -Will On Mon, 6 Mar 2000, Devin Butterfield wrote: > Hi, > > I'm running a snap from 2/28: > > FreeBSD dbm.wireless.net 4.0-20000228-CURRENT FreeBSD 4.0-20000228-CURRENT #2: > Fri Mar 3 22:19:33 PST 2000 > > Often when compiling a port, the process will fail with messages like > the following: > > [...] > Compiling smbd/noquotas.c > Compiling smbd/reply.c > {standard input}: Assembler messages: > {standard input}:4939: Error: no such 386 instruction: `state' > *** Error code 1 > > Stop in /usr/ports/net/samba/work/samba-2.0.6/source. > *** Error code 1 > > Stop in /usr/ports/net/samba. > *** Error code 1 > > Stop in /usr/ports/net/samba. > *** Error code 1 > > Stop in /usr/ports/net/samba. > *** Error code 1 > > Stop in /usr/ports/net/samba. > [root@dbm /usr/ports/net/samba]# > > The strange thing is, if I just say "make" again, it will continue to compile > where it left off without any problems. > > Anyone else see these errors? Any Ideas? > -- > Regards, Devin. > > P.S. Never had this problem under 3.x. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 17:17:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mojave.worldwide.lemis.com (dialup98.sydney.net.au [202.61.208.38]) by hub.freebsd.org (Postfix) with ESMTP id 8A7F537BD4C for ; Mon, 6 Mar 2000 17:17:29 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id MAA01170; Tue, 7 Mar 2000 12:17:48 +1100 (EST) (envelope-from grog) Date: Tue, 7 Mar 2000 12:17:48 +1100 From: Greg Lehey To: Martin Dieringer Cc: current@FreeBSD.ORG Subject: Re: vinum: CDEV_MAJOR undeclared Message-ID: <20000307121748.J346@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dieringe@physik.fu-berlin.de on Mon, Mar 06, 2000 at 11:13:17PM +0100 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 6 March 2000 at 23:13:17 +0100, Martin Dieringer wrote: > > when making buildworld, I get an error: > > ===> sbin/vinum > cc -O2 -pipe -m486 -I/usr/src/sbin/vinum/../../sys -Wall -DVINUMDEBUG > -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sbin/vinum/v.c > /usr/src/sbin/vinum/v.c: In function `make_devices': > /usr/src/sbin/vinum/v.c:494: `CDEV_MAJOR' undeclared (first use in this > function) > /usr/src/sbin/vinum/v.c:494: (Each undeclared identifier is reported only > once > /usr/src/sbin/vinum/v.c:494: for each function it appears in.) > *** Error code 1 > 1 error > > Am I missing some headerfile? I cvsup-ed current yesterday and did an > install-world about a week ago. You appear to be missing the latest version (1.26) of v.c, committed on 29 February: revision 1.26 date: 2000/02/29 06:21:38; author: grog; state: Exp; lines: +9 -11 Don't print any error message if we can't open the history file. This replaces an older attempt to silence vinum(8) when started in single-user mode. Add entries for vinum_raid[45]. Replace the preprocessor variable name CDEV_MAJOR with VINUM_CDEV_MAJOR. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 17:21:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 84E6D37BE4E for ; Mon, 6 Mar 2000 17:21:40 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id KAA25124; Tue, 7 Mar 2000 10:20:59 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id KAA22757; Tue, 7 Mar 2000 10:20:57 +0900 (JST) Received: from localhost ([192.168.245.223]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id KAA26391; Tue, 7 Mar 2000 10:20:55 +0900 (JST) To: jose@we.lc.ehu.es Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? In-Reply-To: <38C3C9A6.28E3A38@we.lc.ehu.es> References: <38C3C9A6.28E3A38@we.lc.ehu.es> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000307102149S.shin@nd.net.fujitsu.co.jp> Date: Tue, 07 Mar 2000 10:21:49 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 59 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Hello, > > Now that I have several machines running FreeBSD 4.0, I started to > play with IPv6. It's fun! I have plans to set up a v6-over-v4 tunnel > and connect to the 6Bone. > > I read /usr/share/examples/IPv6/USAGE, /usr/share/doc/IPv6/IMPLEMENTATION > and some documents at the KAME web site. However, I still have to figure out > how to assign a not-link-local address (i.e., a site or global address) to > the [unique] Ethernet interface of each host in an automatic manner (from > /etc/rc.conf). After reading /etc/rc.network6 I concluded that no addresses > apart from the link-local ones are assigned to the interfaces. I am using > ifconfig manually to do this (BTW, I found that there is no need to specify > "alias"). I am new to IPv6, so maybe I am asking for something with no > sense... There seems to be already another answers and I might be missing a point, but you might mean you want to assigne an address with simple number in its lower 8byte? Such as, 3ffe:501:100e:2000::1 or 3ffe:501:100e:2000::2 not like 3ffe:501:100e:2000:200:eff:fe74:41d2 ? In that case, yes, you need to do ifconfig to assign former kind of address. They are relatively easy to memorize and useful as server addr. But you don't necessarily need to manually assign it. You can use existing ifconfig_ifname= and ifconfig_ifname_aliasnum= also for IPv6. (But there is no example for IPv6. I'll add examles.) E.g. if you want to assign 3ffe:501:100e:2000::1 and 3ffe:501:100e:2000::2 to ed0, I think following configuration works. ifconfig_ed0_alias0="inet6 3ffe:501:100e:2000::1 prefixlen 64" ifconfig_ed0_alias1="inet6 3ffe:501:100e:2000::2 prefixlen 64" (By the way, this is local addr here, and please not use exactly same prefix at another place. :-) Cheers, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 17:23:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id CABB437BCAE for ; Mon, 6 Mar 2000 17:23:38 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id KAA16336; Tue, 7 Mar 2000 10:22:47 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id KAA15765; Tue, 7 Mar 2000 10:22:47 +0900 (JST) Received: from localhost ([192.168.245.223]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id KAA26553; Tue, 7 Mar 2000 10:22:45 +0900 (JST) To: bmah@CA.Sandia.GOV Cc: jhay@mikom.csir.co.za, freebsd-current@FreeBSD.ORG Subject: Re: ipv6 and rc.conf questions In-Reply-To: <200003061550.e26FoLS20060@nimitz.ca.sandia.gov> References: <200003061037.MAA00366@zibbi.mikom.csir.co.za> <20000306201859K.shin@nd.net.fujitsu.co.jp> <200003061550.e26FoLS20060@nimitz.ca.sandia.gov> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000307102338G.shin@nd.net.fujitsu.co.jp> Date: Tue, 07 Mar 2000 10:23:38 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 53 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > Wmmm, should rtadvd always be invoked when 'ipv6_gateway_enable="YES" ? > > Hmmm...two things come to mind. 1) What happens if there are two > routers running rtadvd on a single subnet? 2) Are there environments in > which a netadmin might not want to use router advertisements? (1): It is OK. Host randomly choose one of routers as its default router, and other routers are also kept as backup default routers. Host always send its packet to the default router, and if it is not correct router for the destination, then the packet is just redirected to the correct router. (2): Yes there is. Usually it is desirable that only upstream router invoke rtadvd to suppress too many redirects. In following case, only R-backbone should invoke rtadvd. (But there will be no serious problem even if R-local also invoke rtadvd.) backbone | R-backbone | --------------- my subnet | R-local | -------------- just one or two subnets But if you have more than 2 upstream routers, it might be desirable that either upstream router invoke rtadvd as redundancy. --------- backbone---- | | R-backbone1 R-backbone2 | | ---------------------------------- my subnet Yoshinobu Inoue > I have this fuzzy feeling that always invoking rtadvd on routers might > not be a good idea, but that perhaps making it the default might be good > (right now, rtadvd is turned off by default). > > Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 17:26:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 3643237BD39; Mon, 6 Mar 2000 17:26:26 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id KAA26345; Tue, 7 Mar 2000 10:26:18 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id KAA25097; Tue, 7 Mar 2000 10:26:17 +0900 (JST) Received: from localhost ([192.168.245.223]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id KAA26848; Tue, 7 Mar 2000 10:26:14 +0900 (JST) To: imp@village.org Cc: kris@hub.freebsd.org, jepace@pobox.com, current@FreeBSD.ORG Subject: Re: /usr/bin/ssh and SOCKS In-Reply-To: <200003062309.QAA88816@harmony.village.org> References: <200003062309.QAA88816@harmony.village.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000307102707G.shin@nd.net.fujitsu.co.jp> Date: Tue, 07 Mar 2000 10:27:07 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 263 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : I'd like to get this committed - I'll try and take a look at it tonight, > : time permitting. I would definitely like to allow SSH to work with dante, > : though, since that's a better (BSDL) alternative than the restricted NEC > : version. I don't know well about dante, but if it is one of socks implementation, then I think it will also need getaddrinfo wrapper support. In socks5 port case, the following patches are already added, so it should be able to support apps which use getaddrinfo(). Cheers, Yoshinobu Inoue --- lib/rld.c.orig Wed Aug 4 04:59:28 1999 +++ lib/rld.c Mon Feb 21 03:55:45 2000 @@ -197,6 +197,26 @@ lsInRLDFunctions = 0; S5LogUpdate(S5LogDefaultHandle, S5_LOG_DEBUG(10), 0, "RLD: gethostbyname2 results: %s %s", name, hp?hp->h_name:"???"); return hp; +} +#endif + +#ifdef HAVE_GETADDRINFO +int REAL(getaddrinfo)(const char *hostname, const char *servname, + const struct addrinfo *hints, struct addrinfo **aip) { + int error; + static void *func = NULL; + + S5LogUpdate(S5LogDefaultHandle, S5_LOG_DEBUG(10), 0, "RLD: getaddrinfo: %s", hostname); + GetOriginalFunc(&func, "_getaddrinfo", TRY_LIBC | TRY_LIBNSL | TRY_LIBRESOLV); + if (!func || func == (void *)-1) return NULL; + + lsInRLDFunctions = 1; + error = ((int (*)P((const char *, const char *, const struct addrinfo *, + struct addrinfo **)))func)(hostname, servname, + hints, aip); + lsInRLDFunctions = 0; + S5LogUpdate(S5LogDefaultHandle, S5_LOG_DEBUG(10), 0, "RLD: getaddrinfo results: %s %s", hostname, (*aip&&(*aip)->ai_canonname)?(*aip)->ai_canonname:"???"); + return error; } #endif --- lib/hostname.c.orig Wed Aug 4 04:59:29 1999 +++ lib/hostname.c Tue Feb 22 09:51:48 2000 @@ -17,6 +17,10 @@ #define S5_HOSTLIST_SIZE 256 #define S5_HOSTALIASES_SIZE 16 #define S5_FAKEHOSTFILE ".s5fakehost" + +#ifndef NI_WITHSCOPEID +#define NI_WITHSCOPEID 0 +#endif struct hostEntry { char name[S5_HOSTNAME_SIZE]; @@ -402,6 +406,129 @@ } #endif +#if defined(HAVE_GETADDRINFO) && defined(HAVE_GETNAMEINFO) +/* wrapper around the getaddrinfo call. */ +/* similar to getaddrinfo() except for: */ +/* *** if getaddrinfo() fails, then it returns a pointer to a addrinfo */ +/* structure filled with a special value, so that SOCKSxxxxxx() will */ +/* realize that this host was unresolved and fill in the protocol */ +/* accordingly... */ +/* */ +/* returns an error number on failure; 0 on success */ +int LIBPREFIX(getaddrinfo)(const char *hostname, const char *servname, + const struct addrinfo *hints, + struct addrinfo **aip) { + static char numaddrbuf[MAXHOSTNAMELEN]; + static struct addrinfo *ai; + char *local, *fake; + int error = 0, i; + int addrlen, namelen, family; + +#ifdef FOR_SHARED_LIBRARY + if (lsInRLDFunctions || lsInWrapFunction || lsInWrapHostname) return REAL(getaddrinfo)(hostname, servname, hints, aip); +#endif + + lsInWrapFunction = 1; + lsInWrapHostname = 1; + LIBPREFIX2(init)("libsocks5"); + S5LogUpdate(S5LogDefaultHandle, S5_LOG_DEBUG(10), 0, "SOCKS getaddrinfo: looking up %s", hostname); + + fake = getenv("SOCKS5_FAKEALLHOSTS"); + local = getenv("SOCKS5_LOCALDNSONLY"); + + if (!fake && + (error = REAL(getaddrinfo)(hostname, servname, hints, aip)) == NULL) { + getnameinfo((*aip)->ai_addr, (*aip)->ai_addrlen, numaddrbuf, + sizeof(numaddrbuf) - 1, NULL, 0, + NI_NUMERICHOST|NI_WITHSCOPEID); + S5LogUpdate(S5LogDefaultHandle, S5_LOG_DEBUG(10), 0, "SOCKS getaddrinfo: REAL: %s", numaddrbuf); + + lsInWrapFunction = 0; + lsInWrapHostname = 0; + return error; + } + + /* If your DNS is the same as the socks server, don't fake a correct */ + /* lookup when you know it won't work... */ + if (local) { + S5LogUpdate(S5LogDefaultHandle, S5_LOG_DEBUG(10), 0, "SOCKS getaddrinfo: REAL: Fake not configured"); + lsInWrapFunction = 0; + lsInWrapHostname = 0; + return (error != 0) ? error : EAI_FAIL; + } + + /* Fill in some UNRESOLVED values and let the daemon resolve it */ + if ((i = GetFakeHost(hostname)) <= 0) { + S5LogUpdate(S5LogDefaultHandle, S5_LOG_ERROR, 0, "SOCKS getaddrinfo: Get fake host failed"); + lsInWrapFunction = 0; + lsInWrapHostname = 0; + return (error != 0) ? error : EAI_FAIL; + } + + /* create fake for AF_INET. Fake for AF_INET6 is not yet */ + if (hints->ai_family == AF_UNSPEC || hints->ai_family == AF_INET) { + addrlen = sizeof(struct sockaddr_in); + family = AF_INET; + ai = (struct addrinfo *)malloc(sizeof(struct addrinfo) + addrlen); + if (ai == NULL) + return EAI_MEMORY; + memcpy(ai, hints, sizeof(struct addrinfo)); + ai->ai_family = family; + ai->ai_addr = (struct sockaddr *)(ai + 1); + memset(ai->ai_addr, 0, addrlen); + ai->ai_addr->sa_len = addrlen; + ai->ai_addrlen = addrlen; + ai->ai_addr->sa_family = family; + if (servname != NULL) { + struct servent *sp; + const char *p; + int is_number, port; + + p = servname; + is_number = 1; + while (*p) { + if (!isdigit(*p)) + is_number = 0; + p++; + } + if (is_number) { + port = htons(atoi(servname)); + if (port < 0 || port > 65535) { + free(ai); + return EAI_SERVICE; + } + } else { + sp = getservbyname(servname, NULL); + if (sp == NULL) { + free(ai); + return EAI_SERVICE; + } + port = sp->s_port; + } + ((struct sockaddr_in *)ai->ai_addr)->sin_port = port; + } + ((struct sockaddr_in *)ai->ai_addr)->sin_addr.s_addr = htonl(i); + if ((hints->ai_flags & AI_CANONNAME) != 0) { + ai->ai_canonname = (char *)malloc(strlen(hostname) + 1); + if (ai->ai_canonname == NULL) { + free(ai); + return EAI_MEMORY; + } + strncpy(ai->ai_canonname, hostname, strlen(hostname) + 1); + } + } else + return EAI_FAMILY; + *aip = ai; + + getnameinfo((*aip)->ai_addr, (*aip)->ai_addrlen, numaddrbuf, + sizeof(numaddrbuf) - 1, NULL, 0, NI_NUMERICHOST); + S5LogUpdate(S5LogDefaultHandle, S5_LOG_DEBUG(10), 0, "SOCKS getaddrinfo: FAKE: %s", numaddrbuf); + lsInWrapFunction = 0; + lsInWrapHostname = 0; + return 0; +} +#endif + int lsGetCachedAddress(const char *name, S5NetAddr *na) { int i; char hostname[S5_HOSTNAME_SIZE]; --- configure.in.orig Tue Aug 3 00:00:50 1999 +++ configure.in Sun Feb 20 21:24:32 2000 @@ -120,6 +120,7 @@ AC_CHECK_FUNCS(gethostbyname2) AC_CHECK_FUNCS(gethostbyname_r gethostbyaddr_r getpwuid_r getservbyname_r) +AC_CHECK_FUNCS(getaddrinfo getnameinfo) AC_CHECK_FUNCS(memset memcmp memmove strchr strrchr strdup strerror) AC_CHECK_FUNCS(bcopy bcmp bzero index rindex) AC_CHECK_FUNCS(setenv putenv unsetenv getenv) --- include/config.h.in.orig Mon Aug 2 23:57:28 1999 +++ include/config.h.in Sun Feb 20 21:20:53 2000 @@ -133,6 +133,12 @@ /* Define if you have the gethostbyname_r function. */ #undef HAVE_GETHOSTBYNAME_R +/* Define if you have the getaddrinfo function. */ +#undef HAVE_GETADDRINFO + +/* Define if you have the getnameinfo function. */ +#undef HAVE_GETNAMEINFO + /* Define if you have the getifaddrs function. */ #undef HAVE_GETIFADDRS --- include/hide.h.orig Wed Aug 4 04:59:30 1999 +++ include/hide.h Mon Feb 21 14:41:49 2000 @@ -19,6 +19,7 @@ #ifdef HAVE_GETHOSTBYNAME2 #define gethostbyname2 HIDE(gethostbyname2) #endif +#define getaddrinfo HIDE(getaddrinfo) #define gethostbyname HIDE(gethostbyname) #define getpeername HIDE(getpeername) #define getsockname HIDE(getsockname) @@ -53,6 +54,7 @@ #ifdef HAVE_GETHOSTBYNAME2 #undef gethostbyname2 #endif +#undef getaddrinfo #undef gethostbyname #undef getpeername #undef getsockname --- include/socks.h.orig Wed Aug 4 04:59:30 1999 +++ include/socks.h Mon Feb 21 14:44:03 2000 @@ -52,6 +52,9 @@ #ifdef HAVE_GETHOSTBYNAME2 extern struct hostent *LIBPREFIX(gethostbyname2) P((char *, int)); #endif +extern int LIBPREFIX(getaddrinfo) P((const char *, const char *, + const struct addrinfo *, + struct addrinfo **)); #endif /* include prototypes */ #ifndef LIBPREFIX @@ -93,6 +96,7 @@ #ifdef HAVE_GETHOSTBYNAME2 #define gethostbyname2 LIBPREFIX(gethostbyname2) #endif +#define getaddrinfo LIBPREFIX(getaddrinfo) #define gethostbyname LIBPREFIX(gethostbyname) #define rresvport LIBPREFIX(rresvport) #define connect LIBPREFIX(connect) --- include/system.h.orig Wed Aug 4 04:59:30 1999 +++ include/system.h Mon Feb 21 14:43:42 2000 @@ -24,6 +24,9 @@ #ifdef HAVE_GETHOSTBYNAME2 struct hostent * REAL(gethostbyname2) P((const char *, int)); #endif +int REAL(getaddrinfo) P((const char *, const char *, + const struct addrinfo *, + struct addrinfo **)); struct hostent * REAL(gethostbyname) P((const char *)); struct hostent * REAL(gethostbyaddr) P((const void *, int, int)); struct servent * REAL(getservbyname) P((const char *, const char *)); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 17:28:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id B95D437BCAE for ; Mon, 6 Mar 2000 17:28:36 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id KAA17020; Tue, 7 Mar 2000 10:25:38 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id KAA16958; Tue, 7 Mar 2000 10:25:37 +0900 (JST) Received: from localhost ([192.168.245.223]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id KAA26787; Tue, 7 Mar 2000 10:25:35 +0900 (JST) To: dick@tar.com Cc: fink@es.net, ab@astralblue.com, fenner@research.att.com, jose@we.lc.ehu.es, current@FreeBSD.ORG, 6bone@ISI.EDU Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? In-Reply-To: <20000306162106.B347@tar.com> References: <4.2.2.20000306091731.02b974d8@imap2.es.net> <20000306162106.B347@tar.com> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000307102628S.shin@nd.net.fujitsu.co.jp> Date: Tue, 07 Mar 2000 10:26:28 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 57 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Very unfortunately, 6to4 is not yet supported in FreeBSD/KAME. So now available options will be, -Use freenet6 (for one hosts). -Get IPv6 address block and connect to 6bone using gif tunnel. Cheers, Yoshinobu Inoue > > Please read, then ask any questions you may have. 6to4 is currently > > supported, and there are relay routers up and running. > > My apologies if I sound like I need "IPv6 for Dummies". > > Just to clarify. You mean that 6to4 is currently supported in FreeBSD/KAME? > Of course, I'm not quite sure what I mean by this. I guess, if I configure > a FreeBSD/KAME host as an IPv6 router, will the router automatically do the > IPv6->IPv4 encapsulation when it encounters a destination prefix of 2002::/16 > and vice versa for incoming packets? Or, do I need to configure a pseudo > interface somehow (gif doesn't look quite like the right thing?). Also, will > FreeBSD/KAME hosts (both router and non-router hosts) somehow automatically > do the proper address selection algorithm when they encounter multiple IPv6 > addresses, or is that an application level requirement? > > Also, if I have (for example) IPv4 addresses of 204.95.187/24, I assume > I can use any of the 2002:[V4ADDR]:/48 prefixes within my allocation, but > for external 6to4 connectivity I should probably choose the V4ADDR of the > external interface of the 6to4 router? > > And, finally, do some of the 6to4 relay routers that are "up and running" > serve small isolated sites? I assume the best case is that one's ISP > provides IPv6 connectivity in some shape or form. But, if thats not the > case, I assume the main options are IPv6-IPv4 tunnel to a co-operative > IPv6 site, or 6to4 with a default route to a relay router (who I assume > must configure a static route back?). Or, run a more sophisticated routing > protocol (BGP), but thats a little much for me, I think. > > Of course, if everyone configures 6to4 (or at least everyone you want to reach) > then am I correct that you don't really need 6to4 "relay" routers? This is > only for reaching native IPv6 sites without 6to4 addresses? > > Thanks. > > -- > Richard Seaman, Jr. email: dick@tar.com > 5182 N. Maple Lane phone: 262-367-5450 > Chenequa WI 53058 fax: 262-367-5852 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 18:14:55 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 9DFCA37BB5D; Mon, 6 Mar 2000 18:14:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D02512E815C; Mon, 6 Mar 2000 18:14:52 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 18:14:52 -0800 (PST) From: Kris Kennaway To: R Joseph Wright Cc: freebsd-current@FreeBSD.org Subject: Re: no openssh after build In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 18:21:52 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 821C037BE0D; Mon, 6 Mar 2000 18:21:50 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 804CF2E815C; Mon, 6 Mar 2000 18:21:50 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 18:21:50 -0800 (PST) From: Kris Kennaway To: Garance A Drosihn Cc: Christian Weisgerber , freebsd-current@FreeBSD.ORG Subject: Re: openssh question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, Garance A Drosihn wrote: > Out of the OpenBSD repository, or out of the OpenSSH project? Both are the same thing. > Note that www.openssh.COM currently says: > > *NEW* OpenSSH 1.2.3 released March 6, 2000 > > which sounds a lot like a new release to me... They (arbitrarily) bumped the version this morning. The version numbers don't really correspond to anything other than periodic checkpoints along the CVS branch. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 18:36: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from axp5.physik.fu-berlin.de (axp5.physik.fu-berlin.de [160.45.34.3]) by hub.freebsd.org (Postfix) with ESMTP id F084A37BE4C for ; Mon, 6 Mar 2000 18:36:03 -0800 (PST) (envelope-from dieringe@sirius.physik.fu-berlin.de) Received: from sirius.physik.fu-berlin.de (sirius.physik.fu-berlin.de [160.45.34.162]) by axp5.physik.fu-berlin.de (8.9.1a/8.9.1) with ESMTP id DAA13017 for ; Tue, 7 Mar 2000 03:35:52 +0100 (MET) Received: from localhost (dieringe@localhost) by sirius.physik.fu-berlin.de (8.9.1a/8.9.1) with ESMTP id DAA03683 for ; Tue, 7 Mar 2000 03:35:51 +0100 (MET) Date: Tue, 7 Mar 2000 03:35:50 +0100 (MET) From: Martin Dieringer To: current@FreeBSD.ORG Subject: Re: vinum: CDEV_MAJOR undeclared In-Reply-To: <20000307121748.J346@mojave.worldwide.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thanks for your responses. I seem to have commented out src-all and just fetched -sys and -release, then forgot about that. so my v.c (and everything else) was outdated... sorry to have bothered you with this stupid behaviour. martin On Tue, 7 Mar 2000, Greg Lehey wrote: > On Monday, 6 March 2000 at 23:13:17 +0100, Martin Dieringer wrote: > > > > when making buildworld, I get an error: > > > > ===> sbin/vinum > > cc -O2 -pipe -m486 -I/usr/src/sbin/vinum/../../sys -Wall -DVINUMDEBUG > > -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sbin/vinum/v.c > > /usr/src/sbin/vinum/v.c: In function `make_devices': > > /usr/src/sbin/vinum/v.c:494: `CDEV_MAJOR' undeclared (first use in this > > function) > > /usr/src/sbin/vinum/v.c:494: (Each undeclared identifier is reported only > > once > > /usr/src/sbin/vinum/v.c:494: for each function it appears in.) > > *** Error code 1 > > 1 error > > > > Am I missing some headerfile? I cvsup-ed current yesterday and did an > > install-world about a week ago. > > You appear to be missing the latest version (1.26) of v.c, committed > on 29 February: > > revision 1.26 > date: 2000/02/29 06:21:38; author: grog; state: Exp; lines: +9 -11 > Don't print any error message if we can't open the history file. This > replaces an older attempt to silence vinum(8) when started in > single-user mode. > > Add entries for vinum_raid[45]. > > Replace the preprocessor variable name CDEV_MAJOR with > VINUM_CDEV_MAJOR. > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > _____________________________________________________________________ Martin Dieringer mailto:dieringe@zedat.fu-berlin.de Moeckernstr. 76 http://userpage.fu-berlin.de/~dieringe/ 10965 Berlin Tel.: 030 / 78 99 21 99 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 18:43:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 1880737BD3C for ; Mon, 6 Mar 2000 18:43:10 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id DAA52008; Tue, 7 Mar 2000 03:43:08 +0100 (CET) (envelope-from olli) Date: Tue, 7 Mar 2000 03:43:08 +0100 (CET) Message-Id: <200003070243.DAA52008@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... X-Newsgroups: list.freebsd-current In-Reply-To: <89v0d4$9af$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote in list.freebsd-current: > On Mon, 6 Mar 2000, Oliver Fromme wrote: > > the ports (yeah, stupid me), to no avail. It complained about some > > RSA library missing. > > Did you read the error message? Yes, I did, it was not helpful. In fact, it was confusing. > Perhaps you should. Perhaps reporting it > here would help someone to actually fix your problem instead of having to > guess. I do not have a problem, I fixed it myself after some struggling. Did you read my whole message? Maybe I was a bit unclear. Sorry for that. My question was just what I am expected to do, and whether removing /usr/bin/ssh is the suggested solution. > Hmm. Can you try cvsupping your src-crypto and src-secure collections from > another (non-US) cvsup server? I can't cvsup on that -current box, it's too small for a "make world" (and probably too slow, too). I just downloaded the 20000228-current snapshot and installed it. > > 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. > > Read /etc/defaults/make.conf Why? I didn't compile anything. > > By the way, _why_ is ssh in the base system now, and what is > > wrong with having it in the ports? I'm sorry if there was a > > "HEADS UP" on this list, then I must have missed it. > > Enough people wanted it in the base system For what reason? I'm sorry, I can't find anything in the archives which is answering my question. > I'm quite surprised you've missed any discussion of OpenSSH here though, > since it's probably been one of the most discussed topics here for the > past few weeks. Hm. Strange. Regards, Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 18:43:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id BE62D37BD3C for ; Mon, 6 Mar 2000 18:43:27 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id LAA15842; Tue, 7 Mar 2000 11:43:13 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id LAA18298; Tue, 7 Mar 2000 11:43:12 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id LAA06786; Tue, 7 Mar 2000 11:43:11 +0900 (JST) To: bmah@CA.Sandia.GOV Cc: jhay@mikom.csir.co.za, freebsd-current@FreeBSD.ORG Subject: Re: ipv6 and rc.conf questions In-Reply-To: <20000307102338G.shin@nd.net.fujitsu.co.jp> References: <20000306201859K.shin@nd.net.fujitsu.co.jp> <200003061550.e26FoLS20060@nimitz.ca.sandia.gov> <20000307102338G.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000307114406M.shin@nd.net.fujitsu.co.jp> Date: Tue, 07 Mar 2000 11:44:06 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 46 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Wmmm, should rtadvd always be invoked when 'ipv6_gateway_enable="YES" ? Oh, I need to conclude about this. > (2): Yes there is. Usually it is desirable that only upstream > router invoke rtadvd to suppress too many redirects. > In following case, only R-backbone should invoke rtadvd. > (But there will be no serious problem even if R-local > also invoke rtadvd.) > > backbone > | > R-backbone > | > --------------- my subnet > | > R-local > | > -------------- just one or two subnets > > > I have this fuzzy feeling that always invoking rtadvd on routers might > > not be a good idea, but that perhaps making it the default might be good > > (right now, rtadvd is turned off by default). > > > > Bruce. To think about the above case, always enabling rtadvd might not be good idea. And now I think the problem is that entry name, rtadvd_enable="NO" is not intuitive for users. So how about changing the name to something like, ipv6_to_be_defaultrouter="NO" and if it is set to YES, then rc.network6 invoke rtadvd (and possibly do other works)? Please give me comments if it seems reasonable or not, and also if the name is good or bad. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 18:51:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id EA50A37BE4C for ; Mon, 6 Mar 2000 18:51:54 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id DAA54074; Tue, 7 Mar 2000 03:51:54 +0100 (CET) (envelope-from olli) Date: Tue, 7 Mar 2000 03:51:54 +0100 (CET) Message-Id: <200003070251.DAA54074@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: kern/16487: please apply newpcm fix X-Newsgroups: list.freebsd-current In-Reply-To: <89v48q$b9r$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seigo Tanimura wrote in list.freebsd-current: > On Mon, 6 Mar 2000 01:22:41 +0100 (CET), > Oliver Fromme said: > > Oliver> Would someone please (pretty please) have a look at kern/16487 > Oliver> and commit the trivial fix in it? It's just one line, and it > Oliver> makes AvanceLogic-100 soundcards work again. > > The logical ID of ALS100 conflicts with the one of CMI8330(mss), so we > also have to check the vendor ID. Could you please give it to me? It > is likely to be 0x00019305. (ALS110 is 0x10019305 and ALS120 is > 0x20019305, so...) pnpinfo says: Vendor ID ALS0001 (0x01009305), Serial Number 0x01000000 Logical Device ID: @@@0001 0x01000000 #0 But I think there is already a check for the vendor ID of the card, look at the beginning of sbc_probe() in sbc.c. So I think it's really sufficient to add that line to the array of logical IDs. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 19:14:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 210CD37BED2; Mon, 6 Mar 2000 19:14:01 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id WAA02926; Mon, 6 Mar 2000 22:13:58 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200003070313.WAA02926@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000307000212.53223.qmail@hotmail.com> Date: Mon, 06 Mar 2000 22:13:57 -0500 (EST) From: John Baldwin To: John Daniels Subject: RE: FINAL: installation floppies and USB Cc: freebsd-qa@FreeBSD.org, freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Mar-00 John Daniels wrote: > Hi: > My installation problem has been solved. For those of you who have not been > following "Installation floppies and USB," I have written a short synopsis > after my description of the resolution and conclusion. Good, glad you got your system working. > 4- Although I was disappointed that FreeBSD did not support USB > “out-of-the-box,” I did not expect a lot of support (like I had as a paying > customer of RedHat’s). NetBSD’s installation floppy did work and that was > my backup but I was encouraged to continue looking into my USB problem > because I found that FreeBSD developers were willing to be helpful. This is > especially true of John Barton, who first volunteered to help, but also of > John Reynolds who elevated my problem to -current and Nick Hibma who > responded quickly and cogently. This does need to be rectified. I still want to build a USB-enabled release and try to get it tested, or at least some custom boot floppies. If I get these built, I might ask to have you test them for me if you could. The thing is, while you may have been fortunate to find some PS/2 ports, a lot of new motherboads are USB only. I know because I have been looking at getting an Athlon, and most of the Athlon motherboards are USB only. Part of the problem is that apparently USB cannot be compiled directly into the kernel. Instead, doing so results in an unstable kernel. Instead, USB needs to be loaded via kld's, which complicates the boot disks somewhat. > 5- Perhaps I am naïve, but stating that an OS “supports” a device is > confusing when that “support” has to be compiled in. There should be a > sharper distinction between support out-of-the-box (in GENERIC) and > otherwise. Part of the confusion stems from the fact that USB seems so > basic. For example, almost any PC will “support” a hard disk and a printer > but most people would expect a hard disk to come with the machine. > In fact, hardware.txt states: > “The FreeBSD kernel on the install floppy contains drivers for every > piece of hardware that could conceivably be used to install the rest > of the system with. As mentioned above, this is a definite concern that needs to be addressed. -- John Baldwin -- 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 19:28:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (f197.law7.hotmail.com [216.33.237.197]) by hub.freebsd.org (Postfix) with SMTP id A41AA37BCF0 for ; Mon, 6 Mar 2000 19:28:46 -0800 (PST) (envelope-from jmd526@hotmail.com) Received: (qmail 21894 invoked by uid 0); 7 Mar 2000 03:28:47 -0000 Message-ID: <20000307032847.21893.qmail@hotmail.com> Received: from 209.220.228.2 by www.hotmail.com with HTTP; Mon, 06 Mar 2000 19:28:47 PST X-Originating-IP: [209.220.228.2] From: "John Daniels" To: freebsd-current@freebsd.org, freebsd-qa@freebsd.org Cc: jhb@freebsd.org Subject: Re: FINAL: Installation floppies and USB Date: Mon, 06 Mar 2000 22:28:47 EST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops: That's kudos for John *Baldwin,* NOT "Barton." A thousand pardons... John ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 19:47:16 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 5448537BEE5; Mon, 6 Mar 2000 19:47:14 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 527452E815C for ; Mon, 6 Mar 2000 19:47:14 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 6 Mar 2000 19:47:14 -0800 (PST) From: Kris Kennaway To: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <200003070243.DAA52008@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Oliver Fromme wrote: > > Did you read the error message? > > Yes, I did, it was not helpful. In fact, it was confusing. Without still having seen the error message you were confused by, I can't do much else to help. I can't think of a better way to explain how to fix the problem than what's currently there. > > Hmm. Can you try cvsupping your src-crypto and src-secure collections from > > another (non-US) cvsup server? > > I can't cvsup on that -current box, it's too small for a > "make world" (and probably too slow, too). I just downloaded > the 20000228-current snapshot and installed it. Well, the question then becomes: did you download the snapshot (including the crypto (formerly called 'DES') collection) from a US server, or non-US server? International people should be using the crypto collection from an internationally-produced snapshot for maximum openssl performance. > > Read /etc/defaults/make.conf > > Why? I didn't compile anything. Then, yes, you'll have to delete it after each new snapshot; just like you'd have to delete sendmail, perl, or anything else we have compile-time knobs for but which doesn't exist in a separate installation collection. Them's the breaks.. > > Enough people wanted it in the base system > > For what reason? I'm sorry, I can't find anything in the > archives which is answering my question. It is (very) useful to have out of the box, and making sysinstall depend on packages is ugly to special-case and difficult to maintain. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 20: 1:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id CFCF837BC70 for ; Mon, 6 Mar 2000 20:01:33 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115213>; Tue, 7 Mar 2000 15:02:27 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: ssh strangeness in -current... In-reply-to: <200003070243.DAA52008@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Tue, Mar 07, 2000 at 01:44:28PM +1100 To: olli@dorifer.heim3.tu-clausthal.de Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Mar7.150227est.115213@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <89v0d4$9af$1@atlantis.rz.tu-clausthal.de> <200003070243.DAA52008@dorifer.heim3.tu-clausthal.de> Date: Tue, 7 Mar 2000 15:02:26 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, Oliver Fromme wrote: > 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. I avoid the problem by structuring my paths along the lines of $HOME/bin:/usr/local/bin:/usr/bin:/bin (everythere, not just on FreeBSD). This way, if I (as sysadmin) install something in /usr/local, it over-rides whatever the vendor supplied. (Otherwise, I probably wouldn't have installed my own version). Likewise, anything I put in my private bin directory over-rides anything in the common areas. In this case, it would mean that the version of ssh installed (in /usr/local/bin) from the ports would over-ride the /usr/bin/ssh in the base system. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 20:27:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B16A737BDA7 for ; Mon, 6 Mar 2000 20:27:37 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA57041; Mon, 6 Mar 2000 21:27:32 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA91186; Mon, 6 Mar 2000 21:27:22 -0700 (MST) Message-Id: <200003070427.VAA91186@harmony.village.org> To: Doug Ambrisko Subject: Re: /usr/bin/ssh and SOCKS Cc: "James E. Pace" , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Mar 2000 16:30:06 PST." <200003070030.QAA75449@whistle.com> References: <200003070030.QAA75449@whistle.com> Date: Mon, 06 Mar 2000 21:27:22 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003070030.QAA75449@whistle.com> Doug Ambrisko writes: : Another alternative is to remove the setuid bits /usr/bin/ssh and : then do a "runsocks ssh". That's not really an option for my work patterns... : I could do the work if deemed usefull. I don't want to maintain : my own branch and we use the Nec implementation here so I don't : want to be bouncing between them for no good reason. I'd be up for that as well. Anything that works. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 21:33: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 81A0A37BE71 for ; Mon, 6 Mar 2000 21:32:56 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id AAA25412 for ; Tue, 7 Mar 2000 00:32:54 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA01103; Tue, 7 Mar 2000 00:32:24 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.3/8.9.1) id AAA83828; Tue, 7 Mar 2000 00:32:23 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <200003070532.AAA83828@bb01f39.unx.sas.com> Subject: sysinstall and the status of des encryption? To: freebsd-current@freebsd.org Date: Tue, 7 Mar 2000 00:32:23 -0500 (EST) Cc: jwd@sas.com X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, A quick question before I try to come up with a fix and patches for a problem that I believe to be a moving target. I have run 'make release' to create 4.0-20000306-SNAP with sources current as of 2am March 6th. When running sysinstall and selecting the encryption components, sysinstall fails trying to locate crypto/des.inf. When looking through /usr/src/release/Makefile, it doesn't appear that des.inf and des.?? are created anymore, but instead located in crypto.inf and crypto.??. So, I believe sysinstall needs to be updated so des.?? is not installed anymore. A 2nd question, do we need the concept of a default crypto mechanism when installing the encryption components? Currently, it appears that 'last untarred' wins for libcrypto. Comments Welcome! Thanks, John -- John W. De Boskey jwd@sasDOTcom Gates' Law: Every 18 months, the speed of software halves. Gates' Corollary: Every 18 months, the size of software doubles. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 22:23:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id F3A4F37BF69 for ; Mon, 6 Mar 2000 22:23:05 -0800 (PST) (envelope-from freebsd@mauibuilt.com) Received: (from freebsd@localhost) by mauibuilt.com (8.9.3/8.9.3) id UAA25335 for freebsd-current@freebsd.org; Mon, 6 Mar 2000 20:32:07 -1000 (HST) (envelope-from freebsd) From: FreeBSD MAIL Message-Id: <200003070632.UAA25335@mauibuilt.com> Subject: BookPC Intel 810 chipset To: freebsd-current@freebsd.org Date: Mon, 6 Mar 2000 20:32:06 -1000 (HST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG is there support for sound using the i810 chipset? I hear it isn't such a hot chipset but it does alott.. I have a BookPC here which would make a great work station reguardless of how much the chipset may suck.. support for X seems to exist in the linux world and the Davicomm 10/100 ethernet card works well under 4.0 Thanks in advance Richard Puga puga@mauibuilt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 22:45:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id E4C5D37BE0B for ; Mon, 6 Mar 2000 22:45:33 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 5BD6C2CE9B; Tue, 7 Mar 2000 08:45:29 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id E581F1C5629; Tue, 7 Mar 2000 08:45:30 +0200 (EET) Date: Tue, 7 Mar 2000 08:45:30 +0200 From: Vallo Kallaste To: Dave Boers Cc: Arun Sharma , freebsd-current@freebsd.org Subject: Re: current lockups Message-ID: <20000307084530.A27113@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000306202718.A26973@relativity.student.utwente.nl>; from Dave Boers on Mon, Mar 06, 2000 at 08:27:18PM +0100 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 08:27:18PM +0100, Dave Boers wrote: > I'm interested in the fix, of course :-) But where to start looking? I've > had three lockups so far (none before january 2000) but I didn't find > anything that reliably triggered it. I had a lockup yesterday while stress-testing new SMP machine. Tyan motherboard with Intel GX chipset, 256MB of memory, one 20GB IBM UDMA66 disk, but running at UDMA33. All power management disabled completely in the BIOS. I was doing massive parallel compiling of GENERIC kernels. Let the machine doing this overnight and on the morning the console had about 20 'microuptime() went backwards' messages, I was able to switch vty's but not login, machine responded to pings, no disk activity. I'm using ata driver and only one unusual kernel option HZ=1000. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 22:52:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from not.demophon.com (vpn.iscape.fi [195.170.146.67]) by hub.freebsd.org (Postfix) with ESMTP id 556E037BDCF for ; Mon, 6 Mar 2000 22:52:17 -0800 (PST) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id IAA72293; Tue, 7 Mar 2000 08:49:09 +0200 (EET) (envelope-from will) To: Edwin Kremer Cc: freebsd-current@freebsd.org Subject: Re: openssh question References: <200003060833.AAA18027@windsor.research.att.com> <200003060920.CAA57713@harmony.village.org> <20000306112939.A24401@cs.uu.nl.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 07 Mar 2000 08:49:09 +0200 In-Reply-To: Edwin Kremer's message of "6 Mar 2000 12:29:55 +0200" Message-ID: <86og8r2s2i.fsf@not.demophon.com> Lines: 23 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Kremer writes: > " OpenSSH is based on my version from back in 1995 or 1996. The OpenSSH > " folks have fixed many of the (security) bugs in that version, but not > " all of them when I last checked. Some of the problems in SSH1 are > " very fundamental. > " > " I do not recommend use of OpenSSH (or SSH1 generally, for that matter). > > > There hasn't been much followup on this. Anybody here who cares to > comment on this? What issues are relevant here and how bad is it? The uid-swapping code is still used by OpenSSH despite the fact that it can cause all sorts of security problems. Not all problems apply to all platforms, but I can't remember all of them and wouldn't rely on them not to cause problems on OpenBSD or FreeBSD (IIRC there are some that do). This has been fixed in later (less free) versions of ssh1. There are a number of ways to fix it. Basically switching uids from root to a user and back needs to be avoided. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 6 23: 0:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id A14B937BDF3; Mon, 6 Mar 2000 23:00:39 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip125.r6.d.bel.nwlink.com (ip125.r6.d.bel.nwlink.com [207.202.173.125]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id XAA26682; Mon, 6 Mar 2000 23:00:34 -0800 (PST) Date: Mon, 6 Mar 2000 22:55:02 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: Kris Kennaway Cc: freebsd-current@FreeBSD.org Subject: Re: no openssh after build In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 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? Why, that's a very good question. Why, no, I don't have them installed. :) It wasn't really clear to me, actually. From my tracking of the discussions, which can be very muddy and hard to follow, I thought that openssh was automagically installed but was not really an *active* thing unless the rsaref port was also installed. Thanks for your reply. Joseph To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 1: 9:18 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id DA92637BE74; Tue, 7 Mar 2000 01:09:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D82422E815A for ; Tue, 7 Mar 2000 01:09:15 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 7 Mar 2000 01:09:15 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: 3.4 -> 4.0 upgrade problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I did some testing on my new scratch box by first installing 3.4 from the CD and then attempting a source upgrade to 4.0: buildworld completed fine, but following the directions in UPDATING was not enough to get the kernel built. 1) genassym and config were complaining about not being able to find libc.so.4 when I installed them. Workaround: go back and rebuild with with CFLAGS="-static" 2) When trying to build a GENERIC kernel, the build died with: cc -c -x assembler-with-cpp -DLOCORE -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf ../../i386/i386/locore.s /var/tmp/ccZ79966.s: Assembler messages: /var/tmp/ccZ79966.s:2399: Error: operands given don't match any known 386 instruction /var/tmp/ccZ79966.s:2400: Error: operands given don't match any known 386 instruction /var/tmp/ccZ79966.s:2416: Error: operands given don't match any known 386 instruction /var/tmp/ccZ79966.s:2417: Error: operands given don't match any known 386 instruction /var/tmp/ccZ79966.s:2422: Error: operands given don't match any known 386 instruction /var/tmp/ccZ79966.s:2427: Error: operands given don't match any known 386 instruction /var/tmp/ccZ79966.s:2432: Error: operands given don't match any known 386 instruction /var/tmp/ccZ79966.s:2437: Error: operands given don't match any known 386 instruction *** Error code 1 Stop. Solution: 'make buildkernel' in /usr/src seemed to do the trick. 3) The upgrade steps don't mention mergemastering /etc Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 1: 9:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 69B5D37BD97; Tue, 7 Mar 2000 01:09:27 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12SFzM-000NSM-00; Tue, 07 Mar 2000 11:09:12 +0200 From: Sheldon Hearn To: R Joseph Wright Cc: freebsd-current@FreeBSD.ORG, Kris Kennaway Subject: Re: no openssh after build In-reply-to: Your message of "Mon, 06 Mar 2000 16:38:44 PST." Date: Tue, 07 Mar 2000 11:09:12 +0200 Message-ID: <90169.952420152@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 . Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 1:21:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 9994137BF25 for ; Tue, 7 Mar 2000 01:21:38 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id BDEC05D7D; Tue, 7 Mar 2000 10:21:49 +0100 (CET) Date: Tue, 7 Mar 2000 10:21:49 +0100 From: Dave Boers To: Devin Butterfield Cc: current@FreeBSD.ORG Subject: Re: Error: no such 386 instruction: `state' ??? Message-ID: <20000307102149.A29421@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <00030616230000.06832@dbm.wireless.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <00030616230000.06832@dbm.wireless.net>; from dbutter@wireless.net on Mon, Mar 06, 2000 at 04:21:13PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Devin Butterfield had the courage to say: > Compiling smbd/noquotas.c > Compiling smbd/reply.c > {standard input}: Assembler messages: > {standard input}:4939: Error: no such 386 instruction: `state' > *** Error code 1 I just solved a problem very similar to yours on one of my machines. It turned out to be a broken DIMM. The machine had 384 Mb of RAM and broke on compilations all the time (any ports, kernel or world) with strange compiler errors, like unknown 386 instructions, internal compiler errors, assembler errors and source code syntax errors. I took out all three 128 Mb DIMMS, put them back one at a time and soon found the problem. I replaced the faulty DIMM and the machine is running smoothly again. I Stresstested it by doing several make -j 36 buildworld's. > P.S. Never had this problem under 3.x. It has probably nothing to do with your version of FreeBSD, although differences in memory organization might have some influence on the symptoms. Incidentally, the machine I had problems with was also running 4.0-current. Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 1:25:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id B2ED737BAE2 for ; Tue, 7 Mar 2000 01:25:43 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id 3C8775D7D; Tue, 7 Mar 2000 10:25:55 +0100 (CET) Date: Tue, 7 Mar 2000 10:25:55 +0100 From: Dave Boers To: Vallo Kallaste Cc: Arun Sharma , freebsd-current@freebsd.org Subject: Re: current lockups Message-ID: <20000307102555.A29469@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> <20000307084530.A27113@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000307084530.A27113@myhakas.matti.ee>; from vallo@matti.ee on Tue, Mar 07, 2000 at 08:45:30AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Vallo Kallaste had the courage to say: > I had a lockup yesterday while stress-testing new SMP machine. Tyan > motherboard with Intel GX chipset, 256MB of memory, one 20GB IBM UDMA66 > disk, but running at UDMA33. All power management disabled completely in > the BIOS. I was doing massive parallel compiling of GENERIC kernels. > Let the machine doing this overnight and on the morning the console had > about 20 'microuptime() went backwards' messages, I was able to switch > vty's but not login, machine responded to pings, no disk activity. I'm > using ata driver and only one unusual kernel option HZ=1000. Your symptoms are not the same as mine. In my case the lockups are complete. No switching of vt's, no pings, nothing at all. I never saw any "microuptime() went backwards" messages either. But then again, I never had the machine lockup on the console; I was usually logged in over the network or working in X. Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 1:26:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 5631637BAE2; Tue, 7 Mar 2000 01:26:14 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12SGFf-000Ne0-00; Tue, 07 Mar 2000 11:26:03 +0200 From: Sheldon Hearn To: Warner Losh Cc: Kris Kennaway , bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-reply-to: Your message of "Mon, 06 Mar 2000 13:32:00 MST." <200003062032.NAA61484@harmony.village.org> Date: Tue, 07 Mar 2000 11:26:03 +0200 Message-ID: <90891.952421163@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 06 Mar 2000 13:32:00 MST, Warner Losh wrote: > : This sounds bad. Are you referring to the -o syntax differences, or > : actual incompatabilities? > > I'm talking about the -o syntax difference specifically. How does the > following sound? What about the off-by-one hostkey length problem? Is it supposed to be possible to drop a "1024-bit" host key from the old ssh1 port into /etc/ssh ? We don't seem to be having much luck with that over here. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 1:56:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 2135F37BF64; Tue, 7 Mar 2000 01:56:42 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id LAA81711; Tue, 7 Mar 2000 11:56:32 +0200 (EET) (envelope-from ru) Date: Tue, 7 Mar 2000 11:56:32 +0200 From: Ruslan Ermilov To: Kris Kennaway , imp@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: 3.4 -> 4.0 upgrade problems Message-ID: <20000307115632.A72634@relay.ucb.crimea.ua> Mail-Followup-To: Kris Kennaway , imp@FreeBSD.org, current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=MW5yreqqjyrRcusr X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Kris Kennaway on Tue, Mar 07, 2000 at 01:09:15AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --MW5yreqqjyrRcusr Content-Type: text/plain; charset=us-ascii On Tue, Mar 07, 2000 at 01:09:15AM -0800, Kris Kennaway wrote: > Okay, I did some testing on my new scratch box by first installing 3.4 > from the CD and then attempting a source upgrade to 4.0: buildworld > completed fine, but following the directions in UPDATING was not enough to > get the kernel built. > -current kernels are built just fine on 3.4 with -current src/Makefile after -current world has been built: # cd /usr/src # make buildworld # make buildkernel installkernel [KERNEL="kernels you want build"] > 1) genassym and config were complaining about not being able to find > libc.so.4 when I installed them. Workaround: go back and rebuild with with > CFLAGS="-static" > buildworld builds host versions of these tools, and they are used for building -current kernels with {build|install}kernel: /usr/obj/4.0/home/ru/src-4.0/i386/usr/sbin/config: libc.so.3 => /usr/lib/libc.so.3 (0x2806a000) /usr/obj/4.0/home/ru/src-4.0/i386/usr/bin/genassym: libc.so.3 => /usr/lib/libc.so.3 (0x28062000) > 2) When trying to build a GENERIC kernel, the build died with: > > cc -c -x assembler-with-cpp -DLOCORE -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf ../../i386/i386/locore.s > /var/tmp/ccZ79966.s: Assembler messages: > /var/tmp/ccZ79966.s:2399: Error: operands given don't match any known 386 instruction > /var/tmp/ccZ79966.s:2400: Error: operands given don't match any known 386 instruction > /var/tmp/ccZ79966.s:2416: Error: operands given don't match any known 386 instruction > /var/tmp/ccZ79966.s:2417: Error: operands given don't match any known 386 instruction > /var/tmp/ccZ79966.s:2422: Error: operands given don't match any known 386 instruction > /var/tmp/ccZ79966.s:2427: Error: operands given don't match any known 386 instruction > /var/tmp/ccZ79966.s:2432: Error: operands given don't match any known 386 instruction > /var/tmp/ccZ79966.s:2437: Error: operands given don't match any known 386 instruction > *** Error code 1 > > Stop. > The same for gcc. You need the -current gcc built in the host environment (usually, the one in /usr/obj/usr/src/i386). That's why you should use buildkernel target. > Solution: 'make buildkernel' in /usr/src seemed to do the trick. > We certainly need to update src/UPDATING accordingly, see the patch attached. > 3) The upgrade steps don't mention mergemastering /etc > > Kris -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --MW5yreqqjyrRcusr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p --- UPDATING~ Tue Mar 7 11:51:07 2000 +++ UPDATING Tue Mar 7 11:53:47 2000 @@ -14,7 +14,7 @@ 20000225: OpenSSH has been added to FreeBSD. This may conflict with the - ports/security/ssh port since it installs binaries into + ports/security/ssh port since FreeBSD installs binaries into /usr/bin and the port goes into /usr/local/bin. Most paths have /usr/bin in the path before /usr/local/bin, so problems may arise. If you don't want OpenSSH, add NO_OPENSSH=yes to @@ -648,9 +648,9 @@ -------------------------------- cd /usr/src make buildworld + make buildkernel installkernel KERNEL="NAME_OF_YOUR_KERNEL" cd sbin/mknod make install - [*] reboot --MW5yreqqjyrRcusr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 3:48:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from enterprise.sanyusan.se (enterprise.sanyusan.se [212.209.55.83]) by hub.freebsd.org (Postfix) with ESMTP id E2A6937BB1D; Tue, 7 Mar 2000 03:48:19 -0800 (PST) (envelope-from anders@enterprise.sanyusan.se) Received: (from anders@localhost) by enterprise.sanyusan.se (8.9.3/8.9.3) id MAA21751; Tue, 7 Mar 2000 12:47:45 +0100 (CET) (envelope-from anders) Date: Tue, 7 Mar 2000 12:47:45 +0100 From: Anders Andersson To: Sheldon Hearn Cc: R Joseph Wright , freebsd-current@FreeBSD.ORG, Kris Kennaway Subject: Re: no openssh after build Message-ID: <20000307124745.A21727@enterprise.sanyusan.se> References: <90169.952420152@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <90169.952420152@axl.ops.uunet.co.za>; from sheldonh@uunet.co.za on Tis, Mar 07, 2000 at 11:09:12am +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tis, Mar 07, 2000 at 11:09:12am +0200, Sheldon Hearn wrote: > 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 . mergemaster sure did pick up ssh_config and sshd_config for me. -- Anders Andersson anders@sanyusan.se Sanyusan International AB http://www.sanyusan.se/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 3:57:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 6353E37BEF0; Tue, 7 Mar 2000 03:57:13 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12SIbP-000OFk-00; Tue, 07 Mar 2000 13:56:39 +0200 From: Sheldon Hearn To: Anders Andersson Cc: R Joseph Wright , freebsd-current@FreeBSD.ORG, Kris Kennaway Subject: Re: no openssh after build In-reply-to: Your message of "Tue, 07 Mar 2000 12:47:45 +0100." <20000307124745.A21727@enterprise.sanyusan.se> Date: Tue, 07 Mar 2000 13:56:39 +0200 Message-ID: <93231.952430199@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 07 Mar 2000 12:47:45 +0100, Anders Andersson wrote: > On Tis, Mar 07, 2000 at 11:09:12am +0200, Sheldon Hearn wrote: > > 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 . > > mergemaster sure did pick up ssh_config and sshd_config for me. ?!?! So it's been fiddled to know about the crypto directories? Wow, I'm impressed! *runs.off.to.mergemaster* Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 4:23:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 515CC37BAE2 for ; Tue, 7 Mar 2000 04:23:12 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id NAA63857; Tue, 7 Mar 2000 13:23:11 +0100 (CET) (envelope-from olli) Date: Tue, 7 Mar 2000 13:23:11 +0100 (CET) Message-Id: <200003071223.NAA63857@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... X-Newsgroups: list.freebsd-current In-Reply-To: <8a1u5s$229t$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote in list.freebsd-current: > Without still having seen the error message you were confused by, I can't > do much else to help. I can't think of a better way to explain how to fix > the problem than what's currently there. As I said in my first message, it complained about a missing RSA library. (To reproduce the actual error message word by word, I'd have to install the whole stuff again.) > > I can't cvsup on that -current box, it's too small for a > > "make world" (and probably too slow, too). I just downloaded > > the 20000228-current snapshot and installed it. > > Well, the question then becomes: did you download the snapshot (including > the crypto (formerly called 'DES') collection) from a US server, or non-US > server? International people should be using the crypto collection from an > internationally-produced snapshot for maximum openssl performance. From ftp7.de.freebsd.org which mirrors from current.freebsd.org. I always use those snapshots, for many years now, and it worked fine so far (even though I never had an RSA library). What about the Release? Will 4.0-R be offered in two variants, one for the US and one for all others, so they get a working ssh? As far as I know, releases were the same for everyone, so far. > > > Enough people wanted it in the base system > > > > For what reason? I'm sorry, I can't find anything in the > > archives which is answering my question. > > It is (very) useful to have out of the box, That applies to a real lot of software which is now in the ports. For example, lsof would be very useful to have out of the box. And netcat. And sudo. And pgp. And a few hundreds of others. One of the first things I always did after a fresh install was cd /usr/ports/security/ssh; make install && make clean, just like I did with a bunch of other optional ports which are not there "out of the box" (and shouldn't). Well, sorry for my grumbling, I'll just keep removing the non-functional /usr/bin/ssh from now on. :-) Regards, Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 4:30:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 6025F37BFA4 for ; Tue, 7 Mar 2000 04:30:44 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id NAA24217; Tue, 7 Mar 2000 13:30:03 +0100 (MET) Message-ID: <38C4F649.501C98CA@we.lc.ehu.es> Date: Tue, 07 Mar 2000 13:30:01 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Yoshinobu Inoue Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6: can a link-site (or global) address be configured inrc.conf? References: <38C3C9A6.28E3A38@we.lc.ehu.es> <20000307102149S.shin@nd.net.fujitsu.co.jp> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yoshinobu Inoue wrote: > > There seems to be already another answers and I might be > missing a point, but you might mean you want to assigne an > address with simple number in its lower 8byte? > > Such as, > 3ffe:501:100e:2000::1 > or > 3ffe:501:100e:2000::2 > > not like > 3ffe:501:100e:2000:200:eff:fe74:41d2 > ? > > In that case, yes, you need to do ifconfig to assign former > kind of address. They are relatively easy to memorize and > useful as server addr. But you don't necessarily need to > manually assign it. You can use existing > > ifconfig_ifname= > > and > > ifconfig_ifname_aliasnum= > > also for IPv6. > (But there is no example for IPv6. I'll add examles.) > > E.g. if you want to assign > 3ffe:501:100e:2000::1 and 3ffe:501:100e:2000::2 > to ed0, I think following configuration works. > > ifconfig_ed0_alias0="inet6 3ffe:501:100e:2000::1 prefixlen 64" > ifconfig_ed0_alias1="inet6 3ffe:501:100e:2000::2 prefixlen 64" > > (By the way, this is local addr here, and please not use > exactly same prefix at another place. :-) > Yes, I am using site-local addresses like "fec0::9ee3:6b4", where I am coding the IPv4 address in the lower 32 bits, and I am using a prefixlen=120. Just wondering: is the "alias" necessary? I can add a site-local IPv6 address to the same interface without the "alias" ifconfig keyword. If this is valid, then something as ifconfig_fxp0="inet 158.227.6.180 netmask 255.255.255.0 inet6 fec0::9ee3:6b4 prefixlen 120" should be OK. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 4:50:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 6126D37BFE3 for ; Tue, 7 Mar 2000 04:50:25 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id NAA16148 for ; Tue, 7 Mar 2000 13:45:20 +0100 (CET) Message-Id: <200003071245.NAA16148@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-current@freebsd.org Subject: Re: ssh strangeness in -current... Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 07 Mar 2000 13:23:11 +0100." <200003071223.NAA63857@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Tue, 07 Mar 2000 13:45:20 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme writes: >Kris Kennaway wrote in list.freebsd-current: > > Without still having seen the error message you were confused by, I c= an't > > do much else to help. I can't think of a better way to explain how to= fix > > the problem than what's currently there. > >As I said in my first message, it complained about a missing >RSA library. (To reproduce the actual error message word by >word, I'd have to install the whole stuff again.) > you have to cvsup the secure stuff from internat. I did that and /usr/bin/ssh works just fine after copying the ssh_* stuff from /usr/local/etc to /etc/ssh. --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 4:58:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id EA39637BBE5 for ; Tue, 7 Mar 2000 04:58:01 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id NAA71716; Tue, 7 Mar 2000 13:57:48 +0100 (CET) (envelope-from olli) Date: Tue, 7 Mar 2000 13:57:48 +0100 (CET) Message-Id: <200003071257.NAA71716@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG, Gary Jennejohn Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... X-Newsgroups: list.freebsd-current In-Reply-To: <8a2u5j$2k8g$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Posted & mailed according to Reply-To) Gary Jennejohn wrote in list.freebsd-current: > Oliver Fromme writes: > >As I said in my first message, it complained about a missing > >RSA library. (To reproduce the actual error message word by > >word, I'd have to install the whole stuff again.) > > you have to cvsup the secure stuff from internat. I did that and *sigh* As I wrote in a past message in this thread, i did not and cannot cvsup on that machine at all. I can only do binary installs (i.e. releases and snapshots) on that piece of hard- ware. That's what probably 95% of FreeBSD users do, anyway. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 5: 5:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 7061037BAAD for ; Tue, 7 Mar 2000 05:05:31 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id WAA11705; Tue, 7 Mar 2000 22:05:30 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id WAA09500; Tue, 7 Mar 2000 22:05:29 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id WAA25780; Tue, 7 Mar 2000 22:05:28 +0900 (JST) To: jose@we.lc.ehu.es Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPv6: can a link-site (or global) address be configured inrc.conf? In-Reply-To: <38C4F649.501C98CA@we.lc.ehu.es> References: <38C3C9A6.28E3A38@we.lc.ehu.es> <20000307102149S.shin@nd.net.fujitsu.co.jp> <38C4F649.501C98CA@we.lc.ehu.es> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000307220623I.shin@nd.net.fujitsu.co.jp> Date: Tue, 07 Mar 2000 22:06:23 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 32 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > (By the way, this is local addr here, and please not use > > exactly same prefix at another place. :-) > > Yes, I am using site-local addresses like "fec0::9ee3:6b4", where I > am coding the IPv4 address in the lower 32 bits, and I am using > a prefixlen=120. I think there have been not much experiences in using non 64 prefixlen for IPv6 on LAN, so there might be some problem hidden behind the usage, or maybe not. > Just wondering: is the "alias" necessary? I can add a site-local IPv6 > address to the same interface without the "alias" ifconfig keyword. Yes, alias is not necessary for IPv6. > If this > is valid, then something as > ifconfig_fxp0="inet 158.227.6.180 netmask 255.255.255.0 inet6 fec0::9ee3:6b4 prefixlen 120" > should be OK. But above config does not seems work here. I think ifconfig_ifname_aliasnum is just necessary for configuring multiple addrs for one interface purpose. Cheers, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 5:18: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 1ABBB37BF32; Tue, 7 Mar 2000 05:17:34 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id LAA52407; Tue, 7 Mar 2000 11:01:10 GMT (envelope-from nik) Date: Tue, 7 Mar 2000 11:01:09 +0000 From: Nik Clayton To: Nik Clayton Cc: current@freebsd.org Subject: Re: Alternative way to do -stable to -current upgrade Message-ID: <20000307110109.A52023@catkin.nothing-going-on.org> References: <20000305202435.A39101@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000305202435.A39101@catkin.nothing-going-on.org>; from Nik Clayton on Sun, Mar 05, 2000 at 08:24:35PM +0000 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting the whole thing deliberately: On Sun, Mar 05, 2000 at 08:24:35PM +0000, Nik Clayton wrote: > I had an abortive -stable to -current upgrade late last week, despite > following the directions in UPGRADING, the two kernels I built (one > custom, one GENERIC) both froze on me during the reboot process. > > I'm a little wary of doing it again like that, because it does take > some time to fix. > > So I had an alternative idea. How about doing the following: > > 1. Download -current boot.flp, mfsroot.flp, fixit.flp, and write to > floppies > > 2. cd /usr/src && make buildworld > > 3. Reboot from boot/mfsroot.flp > > 4. When prompted, use the fixit floppy to get a shell > > 5. Mount all the fixed disk partitions, and then (assuming they're all > mounted under /mnt/root) > > cd /mnt/root/usr/src && make DESTDIR=/mnt/root > > 6. Mergemaster > > 7. Build and install a new kernel > > This has the added advantage that if there's something in your system > that was OK in -stable, but doesn't work in -current, you're going to > find out about it before you've done an installworld, and before you've > overwritten a working -stable /kernel, because boot.flp will fail to > work. > > The only problem is that mergemaster assumes it's merging in to /etc, > when that wouldn't be the case here -- mergemaster would need another > config option ($DEST_ETC ?) to specify where to install to. > > Can anyone see anything there that's likely not to work? To which the response has been nil. At this point, you're either all struck dumb by the staggering simplicity and elegance of this approach, or you're sat there slowly shaking your head, wondering how I could be quite so stupid :-) Come on then, which is it? N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 6: 2:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcat.heimat.gr.jp (pcat.heimat.gr.jp [211.0.53.98]) by hub.freebsd.org (Postfix) with ESMTP id AC87137C061 for ; Tue, 7 Mar 2000 06:02:50 -0800 (PST) (envelope-from nakaji@tutrp.tut.ac.jp) Received: from xa12.heimat.gr.jp (xa12.heimat.gr.jp [211.0.53.97]) by pcat.heimat.gr.jp (8.9.3/3.7W) with ESMTP id XAA82490 for ; Tue, 7 Mar 2000 23:01:42 +0900 (JST) To: current@FreeBSD.ORG Subject: XDM login using sessreg and last, uptime, w and so on... MIME-Version: 1.0 (generated by REMI 1.14.1 - =?ISO-8859-4?Q?=22Mushigawa=F2?= =?ISO-8859-4?Q?sugi=22?=) Content-Type: text/plain; charset=US-ASCII From: NAKAJI Hiroyuki Date: 07 Mar 2000 23:01:36 +0900 Message-ID: <86g0u2vpz3.fsf@xa12.heimat.gr.jp> Lines: 61 User-Agent: T-gnus/6.14.1 (based on Gnus v5.8.3) (revision 12) REMI/1.14.1 (=?ISO-8859-4?Q?Mushigawa=F2sugi?=) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.5 (i386--freebsd) MULE/4.0 (HANANOEN) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I forgot when I noticed this curious problem... It's not so serious but annoying. Any help is appreciated. Situation: 1. Running 4.0-current. Uname -a says FreeBSD xa12.heimat.gr.jp 4.0-CURRENT FreeBSD 4.0-CURRENT #8: Sat Mar 4 22:36:09 JST 2000 root@xa12.heimat.gr.jp:/export/src/sys/compile/NAKAJI i386 The system is upgraded by making world from 3.1-RELEASE. 2. XFree86 3.3.6 compiled by ports/x11/XFree86. 3. Xserver is X-TT. 4. Login via XDM and using sessreg to record logins into utmp. /usr/X11R6/lib/X11/xdm/GiveConsole is: chown $LOGNAME /dev/console sessreg -a -l $DISPLAY -x /usr/X11R6/lib/X11/xdm/Xservers $LOGNAME if [ -f /var/run/xdm.pids ]; then kill `cat /var/run/xdm.pids` rm -f /var/run/xdm.pids fi /usr/X11R6/lib/X11/xdm/TakeConsole is: /usr/X11R6/bin/sessreg -d -l $DISPLAY -x /usr/X11R6/lib/xdm/Xservers $LOGNAME chmod 622 /dev/console chown root /dev/console Problems: 1. w, uptime and finger complains about non-existence of /dev/:0, for example, $ w w: /dev/:0: No such file or directory 10:41PM up 29 mins, 1 user, load averages: 0.00, 0.08, 0.23 USER TTY FROM LOGIN@ IDLE WHAT nakaji p1 :0.0 10:32PM - w 2. 'sessreg -d' does not record my logout (the user is only me), that is, $ LC_TIME=C last | head nakaji :0 console Tue Mar 7 22:31 still logged in nakaji :0 console Tue Mar 7 22:22 still logged in nakaji :0 console Tue Mar 7 22:13 still logged in Until rebooting the system, I am always loging in on /dev/:0. Questions: 1. Why w and so on complain, "/dev/:0: No such file or directory"? (Why /dev/:0 is to be opened?) 2. Is my usage of sessreg wrong? Thanks in advance. -- NAKAJI Hiroyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 6:24:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mnw.eas.slu.edu (mnw.eas.slu.edu [165.134.8.248]) by hub.freebsd.org (Postfix) with ESMTP id D306E37C0E5 for ; Tue, 7 Mar 2000 06:24:20 -0800 (PST) (envelope-from ejh@ejhslu.eas.slu.edu) Received: from ejhslu.eas.slu.edu (ejhslu.eas.slu.edu [165.134.8.243]) by mnw.eas.slu.edu (8.9.3/8.9.3) with ESMTP id IAA02925 for ; Tue, 7 Mar 2000 08:24:19 -0600 (CST) Received: (from ejh@localhost) by ejhslu.eas.slu.edu (8.9.3+Sun/8.9.3) id IAA06582 for current@freebsd.org; Tue, 7 Mar 2000 08:24:18 -0600 (CST) Date: Tue, 7 Mar 2000 08:24:18 -0600 (CST) From: "Eric J. Haug" Message-Id: <200003071424.IAA06582@ejhslu.eas.slu.edu> To: current@freebsd.org Subject: anyone working on newbus version of Cyclades serial driver? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I recently purchased a Cyclades Cyclom-Yo4p serial adapter upon booting i noted: Mar 5 09:15:47 gumbo /kernel: cy0: port 0xf4 80-0xf4ff mem 0xffbe8000-0xffbebfff,0xffbee800-0xffbee87f irq 17 at device 15.0 on pci0 Mar 5 09:15:47 gumbo /kernel: pci_map_int: can't allocate interrupt Mar 5 09:15:47 gumbo /kernel: cy0: driver is using old-style compatability shims Moving it to a different slot and removing the CY_PCI_FASTINTR resulted in the pci_map_int message going away. However, after the system starts to transfer data on a ppp link on the COM1 port, i get a panic in the interrupt arena. I did not include the DDB trace info, because i suspect there may be some bitrot in cy.c, and thought i would just fix it myself. It appears that the cy.c is based on sio.c. Is the current sio.c sufficiently newbus correct so that it could again be used as a model to "fix" cy.c? I am going to try the card in a remote kernel GDB setup soon, so if someone wants the trace et.al info... eric haug Saint Louis Univ Earth and Atmospheric Sciences To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 6:32:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 8BA1A37BFB1 for ; Tue, 7 Mar 2000 06:32:36 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id PAA25142 for freebsd-current@freebsd.org; Tue, 7 Mar 2000 15:32:35 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id NAA45041 for freebsd-current@freebsd.org; Tue, 7 Mar 2000 13:01:52 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: ssh strangeness in -current... Date: 7 Mar 2000 13:01:51 +0100 Message-ID: <8a2r3f$1bv8$1@bigeye.rhein-neckar.de> References: <89v0d4$9af$1@atlantis.rz.tu-clausthal.de> <200003070243.DAA52008@dorifer.heim3.tu-clausthal.de> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme wrote: > I can't cvsup on that -current box, it's too small for a > "make world" (and probably too slow, too). I just downloaded > the 20000228-current snapshot and installed it. In that case: See section 6.5 of the handbook. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 6:41:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 0018737B849; Tue, 7 Mar 2000 06:41:45 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id PAA27259; Tue, 7 Mar 2000 15:41:40 +0100 (CET) Message-ID: <20000307154140.A27131@foobar.franken.de> Date: Tue, 7 Mar 2000 15:41:40 +0100 From: Harold Gutch To: Warner Losh , Kris Kennaway Cc: bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... References: <200003062252.PAA62626@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200003062252.PAA62626@harmony.village.org>; from Warner Losh on Mon, Mar 06, 2000 at 03:52:39PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 03:52:39PM -0700, Warner Losh wrote: > 20000225: > OpenSSH has been added to FreeBSD. This may conflict with the > ports/security/ssh port since it installs binaries into > /usr/bin and the port goes into /usr/local/bin. Most paths > have /usr/bin in the path before /usr/local/bin, so problems To be precise, it's ${PREFIX}/bin. bye, Harold -- Someone should do a study to find out how many human life spans have been lost waiting for NT to reboot. Ken Deboy on Dec 24 1999 in comp.unix.bsd.freebsd.misc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 7: 1:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from RedDust.BlueSky.net.au (reddust.bluesky.net.au [203.31.37.15]) by hub.freebsd.org (Postfix) with ESMTP id 58F3537BEC6; Tue, 7 Mar 2000 07:01:09 -0800 (PST) (envelope-from receiver@RedDust.BlueSky.net.au) Received: from localhost (receiver@localhost) by RedDust.BlueSky.net.au (8.9.3/8.9.3) with ESMTP id BAA21531; Wed, 8 Mar 2000 01:02:29 +1000 (EST) (envelope-from receiver@RedDust.BlueSky.net.au) Date: Wed, 8 Mar 2000 01:02:29 +1000 (EST) From: Idea Receiver To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: 3.4 -> 4.0 upgrade problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Kris Kennaway wrote: > Okay, I did some testing on my new scratch box by first installing 3.4 > from the CD and then attempting a source upgrade to 4.0: buildworld > completed fine, but following the directions in UPDATING was not enough to > get the kernel built. > > 1) genassym and config were complaining about not being able to find > libc.so.4 when I installed them. Workaround: go back and rebuild with with > CFLAGS="-static" what i did is just go to genassym directory, do "make clean depend all install". it will then fix the problem. > > 2) When trying to build a GENERIC kernel, the build died with: > > Solution: 'make buildkernel' in /usr/src seemed to do the trick. i was try to rebuild "config" and it will also fix the problem. jus do "make clean depend all install" :-) I dont know if "my solution" going to cause any problem, but it simply sovle both GENERIC kernel and genassym problem. btw, I have problem to make release, it kept complain about that i didnt set the USA_RESIDENT, however, I did! both in /etc and /etc/defaults. Can please someone help me out with this as well.. thanks :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 7: 6:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 2503237BAD6 for ; Tue, 7 Mar 2000 07:06:20 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id RAA66184; Tue, 7 Mar 2000 17:05:40 +0200 (EET) (envelope-from ru) Date: Tue, 7 Mar 2000 17:05:40 +0200 From: Ruslan Ermilov To: Idea Receiver Cc: current@FreeBSD.ORG Subject: Re: 3.4 -> 4.0 upgrade problems Message-ID: <20000307170540.A64753@relay.ucb.crimea.ua> Mail-Followup-To: Idea Receiver , current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Idea Receiver on Wed, Mar 08, 2000 at 01:02:29AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 08, 2000 at 01:02:29AM +1000, Idea Receiver wrote: [...] > btw, I have problem to make release, it kept complain about that i didnt > set the USA_RESIDENT, however, I did! both in /etc and /etc/defaults. Can > please someone help me out with this as well.. > > thanks :) Set USA_RESIDENT in environment rather than in /etc. -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 7: 7:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 9BC9737BB0C for ; Tue, 7 Mar 2000 07:07:35 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 1F896123F7 for ; Tue, 7 Mar 2000 16:07:26 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> References: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> Date: Tue, 7 Mar 2000 15:55:52 +0100 To: freebsd-current@FreeBSD.ORG From: Brad Knowles Subject: Re: ssh strangeness in -current... Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:10 AM +0100 2000/3/6, Oliver Fromme wrote: > I have upgraded a machine to the latest -current snapshot (it > was running a -current from the end of January before). Every- > thing went fine, except for one thing: ssh didn't work anymore. > It used to work fine before. I've been following this thread for a while, and I'd like to ask a related question -- can anyone else successfully use scp with OpenSSH? On the one machine on which I've installed OpenSSH so far, it appears that scp into the machine is totally broken. Of course, this machine isn't running FreeBSD, so I don't expect you folks to help me try to work this problem out, but I am wondering if scp with OpenSSH under FreeBSD does actually work. Thanks! -- These are my opinions and should not be taken as official Skynet policy ========================================================================= Brad Knowles, 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 for details. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 7:17:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.uunet.ca (mail2.uunet.ca [142.77.1.15]) by hub.freebsd.org (Postfix) with ESMTP id CF9ED37BC09 for ; Tue, 7 Mar 2000 07:17:18 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail2.uunet.ca with ESMTP id <600327-29342>; Tue, 7 Mar 2000 10:13:00 -0500 Date: Tue, 7 Mar 2000 10:17:05 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: Brad Knowles Cc: FreeBSD-CURRENT Subject: Re: ssh strangeness in -current... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I tried out OpenSSH on a 3.4-stable machine, I as well was unable to scp into the machine from another 3.4-stable machine using ssh 1.2.27, I didn't at the time attempt to discover much, I was in a rush and thus just installed 1.2.27 instead of OpenSSH which is too bad, I like the OpenSSH idea and development, gives me that safe warm feeling.. Matt -- Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] On Tue, 7 Mar 2000, Brad Knowles wrote: : Date: Tue, 7 Mar 2000 09:55:52 -0500 : From: Brad Knowles : To: freebsd-current@FreeBSD.ORG : Subject: Re: ssh strangeness in -current... : : At 1:10 AM +0100 2000/3/6, Oliver Fromme wrote: : : > I have upgraded a machine to the latest -current snapshot (it : > was running a -current from the end of January before). Every- : > thing went fine, except for one thing: ssh didn't work anymore. : > It used to work fine before. : : I've been following this thread for a while, and I'd like to ask : a related question -- can anyone else successfully use scp with : OpenSSH? On the one machine on which I've installed OpenSSH so far, : it appears that scp into the machine is totally broken. : : Of course, this machine isn't running FreeBSD, so I don't expect : you folks to help me try to work this problem out, but I am wondering : if scp with OpenSSH under FreeBSD does actually work. : : : Thanks! : : -- : These are my opinions and should not be taken as official Skynet policy : ========================================================================= : Brad Knowles, 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 for : details. : : : To Unsubscribe: send mail to majordomo@FreeBSD.org : with "unsubscribe freebsd-current" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 7:26:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 7681837BB9E for ; Tue, 7 Mar 2000 07:26:30 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id ADFA0123C9; Tue, 7 Mar 2000 16:26:04 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Tue, 7 Mar 2000 16:25:32 +0100 To: Matt Heckaman From: Brad Knowles Subject: Re: ssh strangeness in -current... Cc: FreeBSD-CURRENT Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:17 AM -0500 2000/3/7, Matt Heckaman wrote: > When I tried out OpenSSH on a 3.4-stable machine, I as well was unable to > scp into the machine from another 3.4-stable machine using ssh 1.2.27, I > didn't at the time attempt to discover much, I was in a rush and thus just > installed 1.2.27 instead of OpenSSH which is too bad, I like the OpenSSH > idea and development, gives me that safe warm feeling.. Hmm. What version of OpenSSH was that? Given that I've had conflicting reports already, I'd like to try to nail down which version people are using and having (or not having) what problems. This might help me figure out why I'm having problems on this other machine. Thanks! -- These are my opinions and should not be taken as official Skynet policy ========================================================================= Brad Knowles, 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 for details. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 7:27: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 8483F37BC18 for ; Tue, 7 Mar 2000 07:26:56 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id QAA27372; Tue, 7 Mar 2000 16:27:00 +0100 (CET) Message-ID: <20000307162700.A27285@foobar.franken.de> Date: Tue, 7 Mar 2000 16:27:00 +0100 From: Harold Gutch To: Brad Knowles , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... References: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Brad Knowles on Tue, Mar 07, 2000 at 03:55:52PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 03:55:52PM +0100, Brad Knowles wrote: > I've been following this thread for a while, and I'd like to ask > a related question -- can anyone else successfully use scp with > OpenSSH? On the one machine on which I've installed OpenSSH so far, > it appears that scp into the machine is totally broken. > > Of course, this machine isn't running FreeBSD, so I don't expect > you folks to help me try to work this problem out, but I am wondering > if scp with OpenSSH under FreeBSD does actually work. It works fine for me, I just tested scp in both ways between 2 machines running: - FreeBSD 2.2.8 from Dec. 1998, using SSH 1.2.25 without RSAREF from the ports - FreeBSD 3.4 as of Dec. 27th 1999, using OpenSSH 1.2.1 installed as a port bye, Harold -- Someone should do a study to find out how many human life spans have been lost waiting for NT to reboot. Ken Deboy on Dec 24 1999 in comp.unix.bsd.freebsd.misc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 7:44:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail5.uunet.ca (mail5.uunet.ca [142.77.1.28]) by hub.freebsd.org (Postfix) with ESMTP id B00F437BC3F for ; Tue, 7 Mar 2000 07:44:47 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail5.uunet.ca with ESMTP id <232273-2737>; Tue, 7 Mar 2000 10:46:35 -0500 Date: Tue, 7 Mar 2000 10:44:36 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: Brad Knowles Cc: FreeBSD-CURRENT Subject: Re: ssh strangeness in -current... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was using SSH 1.2.27 w/ RSAREF from 3.4-stable, and as for OpenSSH, I don't exactly recall, this was approximately 3-4 weeks after OpenSSH originally made it into the ports, I figured it was at worst a bug of the growing pain nature, I've been meaning to try it out again. Matt -- Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] On Tue, 7 Mar 2000, Brad Knowles wrote: : Date: Tue, 7 Mar 2000 10:25:32 -0500 : From: Brad Knowles : To: Matt Heckaman : Cc: FreeBSD-CURRENT : Subject: Re: ssh strangeness in -current... : : At 10:17 AM -0500 2000/3/7, Matt Heckaman wrote: : : > When I tried out OpenSSH on a 3.4-stable machine, I as well was unable to : > scp into the machine from another 3.4-stable machine using ssh 1.2.27, I : > didn't at the time attempt to discover much, I was in a rush and thus just : > installed 1.2.27 instead of OpenSSH which is too bad, I like the OpenSSH : > idea and development, gives me that safe warm feeling.. : : Hmm. What version of OpenSSH was that? Given that I've had : conflicting reports already, I'd like to try to nail down which : version people are using and having (or not having) what problems. : This might help me figure out why I'm having problems on this other : machine. : : : Thanks! : : -- : These are my opinions and should not be taken as official Skynet policy : ========================================================================= : Brad Knowles, 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 for : details. : : : To Unsubscribe: send mail to majordomo@FreeBSD.org : with "unsubscribe freebsd-current" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 8: 0:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from csmd2.cs.uni-magdeburg.de (csmd2.CS.Uni-Magdeburg.De [141.44.22.2]) by hub.freebsd.org (Postfix) with ESMTP id 34B3037C0CD for ; Tue, 7 Mar 2000 08:00:08 -0800 (PST) (envelope-from jesse@mail.CS.Uni-Magdeburg.De) Received: from knecht.cs.uni-magdeburg.de (jesse@knecht [141.44.21.3]) by csmd2.cs.uni-magdeburg.de (8.9.3/8.9.3) with ESMTP id RAA29258 for ; Tue, 7 Mar 2000 17:00:02 +0100 (MET) Received: (from jesse@localhost) by knecht.cs.uni-magdeburg.de (8.8.8+Sun/8.8.8) id QAA04025; Tue, 7 Mar 2000 16:58:57 +0100 (MET) X-Authentication-Warning: knecht.cs.uni-magdeburg.de: jesse set sender to jesse@cs.uni-magdeburg.de using -f To: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... References: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> From: Roland Jesse In-Reply-To: Brad Knowles's message of "Tue, 7 Mar 2000 15:55:52 +0100" Date: 07 Mar 2000 16:58:57 +0100 Message-ID: <0v3dq2py9q.fsf@cs.uni-magdeburg.de> Lines: 14 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles writes: > but I am wondering if scp with OpenSSH under FreeBSD does actually > work. Well, it works fine for me. r.arthur ~ % uname -rs FreeBSD 4.0-CURRENT r.arthur ~ % ssh -V SSH Version OpenSSH-1.2.2, protocol version 1.5. Compiled with SSL. Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 8: 2:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 2C46C37BB0C for ; Tue, 7 Mar 2000 08:02:22 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id SAA36939 for freebsd-current@FreeBSD.ORG; Tue, 7 Mar 2000 18:02:14 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200003071602.SAA36939@zibbi.mikom.csir.co.za> Subject: Re: ssh strangeness in -current... In-Reply-To: <200003071257.NAA71716@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Mar 7, 2000 01:57:48 pm" To: freebsd-current@FreeBSD.ORG Date: Tue, 7 Mar 2000 18:02:14 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Oliver Fromme writes: > > >As I said in my first message, it complained about a missing > > >RSA library. (To reproduce the actual error message word by > > >word, I'd have to install the whole stuff again.) > > > > you have to cvsup the secure stuff from internat. I did that and > > *sigh* As I wrote in a past message in this thread, i did not > and cannot cvsup on that machine at all. I can only do binary > installs (i.e. releases and snapshots) on that piece of hard- > ware. That's what probably 95% of FreeBSD users do, anyway. Internat also have daily snapshots of -current and -stable. Because of our slow link, it is probably best to install the rest from somewhere else and then just the crypto stuff from internat. Just note that I only keep the last 3 snaps, so don't expect to be able to get the same thing a week later. :-) To answer another question in this thread, we do build releases based on the international crypto code and they are placed on internat. No CDs though. :-/ John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 8:18:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 1ED4F37BBDF for ; Tue, 7 Mar 2000 08:18:50 -0800 (PST) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.10.0.Beta12/8.10.0.Beta12) id e27GIIx02901; Tue, 7 Mar 2000 08:18:18 -0800 (PST) Message-Id: <200003071618.e27GIIx02901@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.1-cvs 10/15/1999 To: Yoshinobu Inoue Cc: bmah@california.sandia.gov, jhay@mikom.csir.co.za, freebsd-current@FreeBSD.ORG Subject: Re: ipv6 and rc.conf questions In-Reply-To: <20000307114406M.shin@nd.net.fujitsu.co.jp> References: <20000306201859K.shin@nd.net.fujitsu.co.jp> <200003061550.e26FoLS20060@nimitz.ca.sandia.gov> <20000307102338G.shin@nd.net.fujitsu.co.jp> <20000307114406M.shin@nd.net.fujitsu.co.jp> Comments: In-reply-to Yoshinobu Inoue message dated "Tue, 07 Mar 2000 11:44:06 +0900." From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-1327064270P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 07 Mar 2000 08:18:18 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-1327064270P Content-Type: text/plain; charset=us-ascii If memory serves me right, Yoshinobu Inoue wrote: > And now I think the problem is that entry name, > rtadvd_enable="NO" > is not intuitive for users. > > So how about changing the name to something like, > > ipv6_to_be_defaultrouter="NO" > > and if it is set to YES, then rc.network6 invoke rtadvd (and > possibly do other works)? > > Please give me comments if it seems reasonable or not, and > also if the name is good or bad. I think that I know just enough about IPv6 to be dangerous, at this point. With that in mind, I think we should keep the name (because that describes exactly what it does), and just change the default to "YES". Cheers, Bruce. --==_Exmh_-1327064270P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: E+vKXS2gF73YZKGANY6eY8aRbERGswik iQA/AwUBOMUrytjKMXFboFLDEQLo3gCgtoyAM0s7MrhtejRBnh5lssbJ4J8AoJgs WpYOM48Fl4kd7/+HJePLTzbP =kb4I -----END PGP SIGNATURE----- --==_Exmh_-1327064270P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 8:52:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 9442437BBDF for ; Tue, 7 Mar 2000 08:52:27 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from pdx.cybcon.com (wwoods@pdx.cybcon.com [216.190.188.4]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id IAA24347 for ; Tue, 7 Mar 2000 08:53:12 -0800 (PST) Date: Tue, 7 Mar 2000 08:52:22 -0800 (PST) From: Bill Woods To: freebsd-current@freebsd.org Subject: sshd in current....no config files in /etc/ssh Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just finished a make world for -current todayd cvsup. All went well but I was planning on setting up ssh between my home systems and aneother system on the net, but I find there are no config files in /etc/ssh. I do have the crypto sources also. Thanks Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 8:54:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 5CCF437BBFC for ; Tue, 7 Mar 2000 08:54:44 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id BAA17112; Wed, 8 Mar 2000 01:53:40 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id BAA25770; Wed, 8 Mar 2000 01:53:39 +0900 (JST) Received: from localhost ([192.168.245.168]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id BAA17774; Wed, 8 Mar 2000 01:53:37 +0900 (JST) To: bmah@CA.Sandia.GOV Cc: bmah@california.sandia.gov, jhay@mikom.csir.co.za, freebsd-current@FreeBSD.ORG Subject: Re: ipv6 and rc.conf questions In-Reply-To: <200003071618.e27GIIx02901@nimitz.ca.sandia.gov> References: <20000307102338G.shin@nd.net.fujitsu.co.jp> <20000307114406M.shin@nd.net.fujitsu.co.jp> <200003071618.e27GIIx02901@nimitz.ca.sandia.gov> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000308015432W.shin@nd.net.fujitsu.co.jp> Date: Wed, 08 Mar 2000 01:54:32 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 9 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think that I know just enough about IPv6 to be dangerous, at this > point. With that in mind, I think we should keep the name (because that > describes exactly what it does), and just change the default to "YES". OK, I'll choose the option, and also add some more description for "rtadvd_enable". Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 9: 2:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from moran.grauel.com (dail-usr1-47.geetel.net [208.15.165.85]) by hub.freebsd.org (Postfix) with ESMTP id 4E7A937BC0B for ; Tue, 7 Mar 2000 09:02:26 -0800 (PST) (envelope-from rjk@moran.grauel.com) Received: (from rjk@localhost) by moran.grauel.com (8.9.3/8.9.3) id MAA00780; Tue, 7 Mar 2000 12:02:49 -0500 (EST) (envelope-from rjk) From: Richard J Kuhns MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14533.13881.134031.173029@localhost.grauel.com> Date: Tue, 7 Mar 2000 12:02:49 -0500 (EST) To: freebsd-current@freebsd.org Subject: YA ssh question (ssh-askpass?) X-Mailer: VM 6.75 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just built- and installed- world about an hour ago, and removed the ssh-1.2.27 port. The build and install went without a problem, but I've apparently lost some functionality. I spend most of my time in xemacs, and I make heavy use of CVS to access a couple of remote repositories. I've had CVS_RSH=ssh for quite some time, and use vc (the emacs/xemacs interface to CVS) to handle my sources. Up until this morning, it worked fine. Whenever I needed to access a remote repository, a window popped up to ask for my password. Now, I just get an error message saying "You have no controlling tty. Cannot read passphrase." I've installed a Tcl/Tk version of ssh-askpass in /usr/local/bin (which works by itself; I've tried it). I've also set SSH_ASKPASS_ENV to /usr/local/bin/ssh-askpass, but it hasn't made any difference. Any suggestions? Thanks... -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 9:15:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id 0ABA837C095; Tue, 7 Mar 2000 09:15:32 -0800 (PST) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id 427817555; Tue, 7 Mar 2000 09:15:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id 31FC01D89; Tue, 7 Mar 2000 09:15:38 -0800 (PST) Date: Tue, 7 Mar 2000 09:15:38 -0800 (PST) From: Jamie Bowden To: "David E. Cross" Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: rpc.lockd and xdr. In-Reply-To: <200003061712.MAA40849@cs.rpi.edu> Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, David E. Cross wrote: :Version 2 of the lock manager is ready to be released. Amitha :says that it passes all of the tests in the suite posted by Drew (thanks :Drew). A noteable exception to this is on SGI where some lock requests :are never even received from the remote host. Also DOS sharing is not :yet complete. Any idea why this is? I only ask because: 12:12pm banshee /home/jamie %uname -aR IRIX64 banshee 6.5 6.5.5m 07151433 IP25 I have some PC's that I'm interested in putting FreeBSD on (other than my laptop) that would be on the network fulltime, and working NFS locking is really the only stumbling bock for me now. Jamie Bowden -- "Of course, that's sort of like asking how other than Marketing, Microsoft is different from any other software company..." Kenneth G. Cavness To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 9:18:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id BA8F637BBC9; Tue, 7 Mar 2000 09:18:42 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id JAA74480; Tue, 7 Mar 2000 09:20:01 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200003071720.JAA74480@troutmask.apl.washington.edu> Subject: Re: Alternative way to do -stable to -current upgrade In-Reply-To: <20000307110109.A52023@catkin.nothing-going-on.org> from Nik Clayton at "Mar 7, 2000 11:01:09 am" To: Nik Clayton Date: Tue, 7 Mar 2000 09:20:01 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nik Clayton wrote: >> 5. Mount all the fixed disk partitions, and then (assuming they're all >> mounted under /mnt/root) >> >> cd /mnt/root/usr/src && make DESTDIR=/mnt/root >> >> >> 7. Build and install a new kernel >> > > Come on then, which is it? > Okay, here's some feedback ;-) In 5. above, is "make DESTDIR=/mnt/root" missing "world" or "installworld"? AFAIK, a plain "make DESTDIR=/mnt/root" will not do the install portion. If this is the case, then you better make sure the /modules agrees with your 7., or people loading modules during the reboot will be screwed. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 9:42:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1A98837B9C4 for ; Tue, 7 Mar 2000 09:42:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA91664; Tue, 7 Mar 2000 09:39:53 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Oliver Fromme Cc: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-reply-to: Your message of "Mon, 06 Mar 2000 01:10:30 +0100." <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> Date: Tue, 07 Mar 2000 09:39:52 -0800 Message-ID: <91661.952450792@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have upgraded a machine to the latest -current snapshot (it > was running a -current from the end of January before). Every- > thing went fine, except for one thing: ssh didn't work anymore. > It used to work fine before. You really need to read the -current mailing list if you're going to run -current. Saying that openssh took you by surprise as a -current user is sort of like saying you didn't know Elvis was dead. :-( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 9:44:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BCD5B37BBFC for ; Tue, 7 Mar 2000 09:44:37 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA92455; Tue, 7 Mar 2000 09:42:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Matthew N. Dodd" Cc: Oliver Fromme , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-reply-to: Your message of "Sun, 05 Mar 2000 19:57:52 EST." Date: Tue, 07 Mar 2000 09:42:16 -0800 Message-ID: <92448.952450936@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I keep asking myself this question; a default sysinstall package would > give us the same end result. > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > breakage. Would you guys quit spreading FUD and start actually giving us some DETAILS on this alleged breakage? You've been ridiculously silent on an issue which has been actively worked on and discussed for the last few weeks to come forward at this late stage and start waving your arms around. This entire thread has been content-free so far. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 9:49:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 37F6A37B8AC for ; Tue, 7 Mar 2000 09:49:31 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 6A37812468; Tue, 7 Mar 2000 18:49:21 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <0v3dq2py9q.fsf@cs.uni-magdeburg.de> References: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> <0v3dq2py9q.fsf@cs.uni-magdeburg.de> Date: Tue, 7 Mar 2000 18:48:56 +0100 To: Roland Jesse , freebsd-current@FreeBSD.ORG From: Brad Knowles Subject: Re: ssh strangeness in -current... Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:58 PM +0100 2000/3/7, Roland Jesse wrote: > Well, it works fine for me. Must be a FreeBSD vs. Solaris thing, because I've got the same version and it doesn't work for me. Sounds like I've got some more debugging to do. Thanks for all the info! -- These are my opinions and should not be taken as official Skynet policy ========================================================================= Brad Knowles, 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 for details. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 10: 4:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 721C537BCB6; Tue, 7 Mar 2000 10:04:41 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA06295; Tue, 7 Mar 2000 10:04:40 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA89683; Tue, 7 Mar 2000 10:04:39 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 7 Mar 2000 10:04:39 -0800 (PST) Message-Id: <200003071804.KAA89683@vashon.polstra.com> From: John Polstra To: kris@hub.freebsd.org Subject: Re: ssh strangeness in -current... In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Kris Kennaway wrote: > > Ahh, so you can use the OpenSSH client to connect to some servers, but not > the F-Secure one? That would definitely be a bug you should report to the > OpenSSH developers. > > Is anyone else in the position to test this? In the past I have had interoperability problems between F-Secure and the open source versions of ssh. But the cause then was simply that the F-Secure keys were too long (> 1024 bits) for ssh's rsaref to cope with. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 10: 9:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-198-202.guate.net [209.198.197.202]) by hub.freebsd.org (Postfix) with ESMTP id 1E64A37BBE5 for ; Tue, 7 Mar 2000 10:09:17 -0800 (PST) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id MAA53984; Tue, 7 Mar 2000 12:08:02 -0600 (CST) (envelope-from obonilla) Date: Tue, 7 Mar 2000 12:07:59 -0600 From: Oscar Bonilla To: Bill Woods Cc: freebsd-current@FreeBSD.ORG Subject: Re: sshd in current....no config files in /etc/ssh Message-ID: <20000307120758.A53972@fisicc-ufm.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 08:52:22AM -0800, Bill Woods wrote: > I just finished a make world for -current todayd cvsup. All went well but > I was planning on setting up ssh between my home systems and aneother > system on the net, but I find there are no config files in /etc/ssh. > > I do have the crypto sources also. > did you run mergemaster after the make world? regards, -oscar -- pgp public key: finger obonilla@fisicc-ufm.edu pgp fingerprint: 6D 18 8C 90 4C DF F0 4B DF 35 1F 69 A1 33 C7 BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 10:10:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-198-202.guate.net [209.198.197.202]) by hub.freebsd.org (Postfix) with ESMTP id 3815037BDAF for ; Tue, 7 Mar 2000 10:10:17 -0800 (PST) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id MAA53994; Tue, 7 Mar 2000 12:09:20 -0600 (CST) (envelope-from obonilla) Date: Tue, 7 Mar 2000 12:09:20 -0600 From: Oscar Bonilla To: Richard J Kuhns Cc: freebsd-current@FreeBSD.ORG Subject: Re: YA ssh question (ssh-askpass?) Message-ID: <20000307120920.B53972@fisicc-ufm.edu> References: <14533.13881.134031.173029@localhost.grauel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <14533.13881.134031.173029@localhost.grauel.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 12:02:49PM -0500, Richard J Kuhns wrote: > I just built- and installed- world about an hour ago, and removed the > ssh-1.2.27 port. The build and install went without a problem, but I've > apparently lost some functionality. > > I spend most of my time in xemacs, and I make heavy use of CVS to access a > couple of remote repositories. I've had CVS_RSH=ssh for quite some time, > and use vc (the emacs/xemacs interface to CVS) to handle my sources. Up > until this morning, it worked fine. Whenever I needed to access a remote > repository, a window popped up to ask for my password. Now, I just get an > error message saying "You have no controlling tty. Cannot read > passphrase." > > I've installed a Tcl/Tk version of ssh-askpass in /usr/local/bin (which > works by itself; I've tried it). I've also set SSH_ASKPASS_ENV to > /usr/local/bin/ssh-askpass, but it hasn't made any difference. > > Any suggestions? > # cd /usr/ports/security/OpenSSH-askpass/ # make all install clean regards, -oscar -- pgp public key: finger obonilla@fisicc-ufm.edu pgp fingerprint: 6D 18 8C 90 4C DF F0 4B DF 35 1F 69 A1 33 C7 BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 10:15:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 4C6C937BCC0; Tue, 7 Mar 2000 10:15:08 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p27-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.92]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA09845; Wed, 8 Mar 2000 03:14:58 +0900 (JST) Message-ID: <38C546D7.3571A497@newsguy.com> Date: Wed, 08 Mar 2000 03:13:43 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Kris Kennaway Cc: Warner Losh , bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > This sounds bad. Are you referring to the -o syntax differences, or actual > incompatabilities? There have been unsubstantiated reports of > interoperability problems, but nothing well documented here. I know for a fact that one flag I used with ssh (ssh-agent's -p, I think) does not exist in openssh. Nevertheless, I haven't had problems with openssh. Well, actually, I haven't *tested* it, so who knows. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 10:17: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 42D8E37B8AC for ; Tue, 7 Mar 2000 10:16:53 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id NAA16177; Tue, 7 Mar 2000 13:16:00 -0500 (EST) Date: Tue, 7 Mar 2000 13:16:00 -0500 (EST) From: "Matthew N. Dodd" To: "Jordan K. Hubbard" Cc: Oliver Fromme , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: <92448.952450936@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Jordan K. Hubbard wrote: > > I keep asking myself this question; a default sysinstall package would > > give us the same end result. > > > > I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with > > breakage. > > Would you guys quit spreading FUD and start actually giving us some > DETAILS on this alleged breakage? You've been ridiculously silent on > an issue which has been actively worked on and discussed for the last > few weeks to come forward at this late stage and start waving your > arms around. This entire thread has been content-free so far. I've been building and rebuilding in an attempt to make sure that its not some stupidity on my part. Be assured that when I'm positive I've got a reproducable error that I'll let everyone in on the details. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 10:20: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 9621437BCA0; Tue, 7 Mar 2000 10:19:58 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id KAA27287; Tue, 7 Mar 2000 10:19:57 -0800 (PST) Date: Tue, 7 Mar 2000 10:19:57 -0800 From: Brooks Davis To: Nik Clayton Cc: current@FreeBSD.ORG Subject: Re: Alternative way to do -stable to -current upgrade Message-ID: <20000307101957.A5565@orion.ac.hmc.edu> References: <20000305202435.A39101@catkin.nothing-going-on.org> <20000307110109.A52023@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000307110109.A52023@catkin.nothing-going-on.org>; from nik@FreeBSD.ORG on Tue, Mar 07, 2000 at 11:01:09AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 11:01:09AM +0000, Nik Clayton wrote: > Quoting the whole thing deliberately: > > On Sun, Mar 05, 2000 at 08:24:35PM +0000, Nik Clayton wrote: [snip] > > To which the response has been nil. At this point, you're either all > struck dumb by the staggering simplicity and elegance of this approach, > or you're sat there slowly shaking your head, wondering how I could be > quite so stupid :-) > > Come on then, which is it? To be honest it seems like a complete waste of time and a hugh pain in the rear. All you need to do is build a 4.0 kernel, install it under some random name (say /kernel.current) boot with it to insure that it works. If something goes wrong you just reboot and fall back to /kernel which should work. It's not like the boot floppies are going to work if GENERIC doesn't. What needs to be fixed is that users need to be reminded the cardinal rule of kernel building which is to always keep a known, working kernel around. I use /kernel.working, others use kernel.good. That way, if things go wrong they just switch back. None of this messing with floppies and redirecting installworlds. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 10:20:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 57E8E37BCA0; Tue, 7 Mar 2000 10:20:09 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA59605; Tue, 7 Mar 2000 11:20:06 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA95636; Tue, 7 Mar 2000 11:19:55 -0700 (MST) Message-Id: <200003071819.LAA95636@harmony.village.org> To: "Daniel C. Sobral" Subject: Re: ssh strangeness in -current... Cc: Kris Kennaway , bloom@acm.org, John Baldwin , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 08 Mar 2000 03:13:43 +0900." <38C546D7.3571A497@newsguy.com> References: <38C546D7.3571A497@newsguy.com> Date: Tue, 07 Mar 2000 11:19:55 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38C546D7.3571A497@newsguy.com> "Daniel C. Sobral" writes: : I know for a fact that one flag I used with ssh (ssh-agent's -p, I : think) does not exist in openssh. Nevertheless, I haven't had problems : with openssh. Well, actually, I haven't *tested* it, so who knows. :-) Other than the missing or different features, different default values, different error/warning message, pickier whining and the like, I've had no problem since I cut over :-). The programs interoperate, but there's definitely a learning curve for OpenSSH. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 10:38:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop3.ptld.uswest.net (ptldpop3.ptld.uswest.net [198.36.160.3]) by hub.freebsd.org (Postfix) with SMTP id B29AD37BD59 for ; Tue, 7 Mar 2000 10:38:04 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 22623 invoked by alias); 7 Mar 2000 18:37:16 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 22602 invoked by uid 0); 7 Mar 2000 18:37:14 -0000 Received: from unknown (HELO laptop.cybcon.com) (63.163.56.10) by pop.ptld.uswest.net with SMTP; 7 Mar 2000 18:37:14 -0000 Content-Length: 1149 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000307120758.A53972@fisicc-ufm.edu> Date: Tue, 07 Mar 2000 10:34:55 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Oscar Bonilla Subject: Re: sshd in current....no config files in /etc/ssh Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, I dident. I dident have old ssh (the port one) to merge. This is the 1st time use of ssh on this system. On 07-Mar-00 Oscar Bonilla wrote: > On Tue, Mar 07, 2000 at 08:52:22AM -0800, Bill Woods wrote: >> I just finished a make world for -current todayd cvsup. All went well but >> I was planning on setting up ssh between my home systems and aneother >> system on the net, but I find there are no config files in /etc/ssh. >> >> I do have the crypto sources also. >> > > did you run mergemaster after the make world? > > regards, > > -oscar > > -- > pgp public key: finger obonilla@fisicc-ufm.edu > pgp fingerprint: 6D 18 8C 90 4C DF F0 4B DF 35 1F 69 A1 33 C7 BC > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: bwoods2@uswest.net Date: 07-Mar-00 Time: 10:33:57l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 10:44:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231]) by hub.freebsd.org (Postfix) with ESMTP id 7C86A37C0F2 for ; Tue, 7 Mar 2000 10:44:38 -0800 (PST) (envelope-from insane@lunatic.oneinsane.net) Received: by lunatic.oneinsane.net (Postfix, from userid 1000) id 57637197; Tue, 7 Mar 2000 10:44:35 -0800 (PST) Date: Tue, 7 Mar 2000 10:44:35 -0800 From: Ron 'The InSaNe One' Rosson To: freebsd-current@freebsd.org Subject: Re: 3.4 -> 4.0 upgrade problems Message-ID: <20000307104434.A4503@lunatic.oneinsane.net> Reply-To: Ron Rosson References: <20000307170540.A64753@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000307170540.A64753@relay.ucb.crimea.ua>; from ru@ucb.crimea.ua on Tue, Mar 07, 2000 at 05:05:40PM +0200 X-Operating-System: FreeBSD lunatic.oneinsane.net 3.4-STABLE X-Moon: The Moon is Waxing Crescent (3% of Full) X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane2-pgp5i.txt X-Uptime: 10:38AM up 3:05, 2 users, load averages: 0.18, 0.07, 0.02 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 07 Mar 2000, Ruslan Ermilov was heard blurting out: > On Wed, Mar 08, 2000 at 01:02:29AM +1000, Idea Receiver wrote: > [...] > > btw, I have problem to make release, it kept complain about that i didnt > > set the USA_RESIDENT, however, I did! both in /etc and /etc/defaults. Can > > please someone help me out with this as well.. > > > > thanks :) > > Set USA_RESIDENT in environment rather than in /etc. > In /etc/make.conf you can set it like so: USA_RESIDENT= YES -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------- "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 10:49:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from moran.grauel.com (dail-usr1-47.geetel.net [208.15.165.85]) by hub.freebsd.org (Postfix) with ESMTP id 8CC7D37C107 for ; Tue, 7 Mar 2000 10:49:19 -0800 (PST) (envelope-from rjk@moran.grauel.com) Received: (from rjk@localhost) by moran.grauel.com (8.9.3/8.9.3) id NAA04651; Tue, 7 Mar 2000 13:48:51 -0500 (EST) (envelope-from rjk) From: Richard J Kuhns MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14533.20243.500587.31037@localhost.grauel.com> Date: Tue, 7 Mar 2000 13:48:51 -0500 (EST) To: Oscar Bonilla Cc: Richard J Kuhns , freebsd-current@FreeBSD.ORG Subject: Re: YA ssh question (ssh-askpass?) In-Reply-To: <20000307120920.B53972@fisicc-ufm.edu> References: <14533.13881.134031.173029@localhost.grauel.com> <20000307120920.B53972@fisicc-ufm.edu> X-Mailer: VM 6.75 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oscar Bonilla writes: > > # cd /usr/ports/security/OpenSSH-askpass/ > # make all install clean > > regards, > > -oscar > Well, that installed a C version of ssh-askpass in /usr/X11R6/bin. Running it directly, it looks different but functions identically to the Tcl/TK version I'd installed earlier (which I moved so it wouldn't interfere with anything). It also made no difference whatsoever. A quick grep through /usr/src/crypto/openssh seems to indicate that only ssh-add uses ssh-askpass. -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 10:52:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from havoc.scorched.com (kythorn2.upper.ul.warwick.net [208.228.96.45]) by hub.freebsd.org (Postfix) with ESMTP id 18D9437C2B0 for ; Tue, 7 Mar 2000 10:52:04 -0800 (PST) (envelope-from kythorn@scorched.com) Received: from CHAOS (chaos.scorched.com [208.228.96.34]) by havoc.scorched.com (8.9.3/8.9.3) with SMTP id NAA12368 for ; Tue, 7 Mar 2000 13:54:47 -0500 Message-ID: <001d01bf8866$64ded4b0$2260e4d0@CHAOS> From: "Jay Oliver" To: References: Subject: Re: sshd in current....no config files in /etc/ssh Date: Tue, 7 Mar 2000 13:53:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Regardless, without using mergemaster, the NEW config files will never have gotten placed into /etc Make world does not in and of itself in any way touch those configuration files. - Jay Oliver ----- Original Message ----- From: "William Woods" To: "Oscar Bonilla" Cc: Sent: Tuesday, March 07, 2000 1:34 PM Subject: Re: sshd in current....no config files in /etc/ssh > No, I dident. I dident have old ssh (the port one) to merge. This is the 1st > time use of ssh on this system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:13: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 6CCDB37BD8C; Tue, 7 Mar 2000 11:13:02 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id TAA19251; Tue, 7 Mar 2000 19:09:20 GMT (envelope-from nik) Date: Tue, 7 Mar 2000 19:09:19 +0000 From: Nik Clayton To: Steve Kargl Cc: Nik Clayton , current@FreeBSD.ORG Subject: Re: Alternative way to do -stable to -current upgrade Message-ID: <20000307190919.A19024@catkin.nothing-going-on.org> References: <20000307110109.A52023@catkin.nothing-going-on.org> <200003071720.JAA74480@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200003071720.JAA74480@troutmask.apl.washington.edu>; from Steve Kargl on Tue, Mar 07, 2000 at 09:20:01AM -0800 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 09:20:01AM -0800, Steve Kargl wrote: > Nik Clayton wrote: > >> 5. Mount all the fixed disk partitions, and then (assuming they're all > >> mounted under /mnt/root) > >> > >> cd /mnt/root/usr/src && make DESTDIR=/mnt/root > >> > >> 7. Build and install a new kernel > >> > > > > Come on then, which is it? > > Okay, here's some feedback ;-) > > In 5. above, is "make DESTDIR=/mnt/root" missing "world" or > "installworld"? Rats. It's missing the "installworld" bit. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:19: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id C893237BDAD; Tue, 7 Mar 2000 11:18:50 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id TAA19930; Tue, 7 Mar 2000 19:14:42 GMT (envelope-from nik) Date: Tue, 7 Mar 2000 19:14:42 +0000 From: Nik Clayton To: Brooks Davis Cc: Nik Clayton , current@FreeBSD.ORG Subject: Re: Alternative way to do -stable to -current upgrade Message-ID: <20000307191442.B19024@catkin.nothing-going-on.org> References: <20000305202435.A39101@catkin.nothing-going-on.org> <20000307110109.A52023@catkin.nothing-going-on.org> <20000307101957.A5565@orion.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000307101957.A5565@orion.ac.hmc.edu>; from Brooks Davis on Tue, Mar 07, 2000 at 10:19:57AM -0800 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 10:19:57AM -0800, Brooks Davis wrote: > On Tue, Mar 07, 2000 at 11:01:09AM +0000, Nik Clayton wrote: > > To which the response has been nil. At this point, you're either all > > struck dumb by the staggering simplicity and elegance of this approach, > > or you're sat there slowly shaking your head, wondering how I could be > > quite so stupid :-) > > > > Come on then, which is it? > > To be honest it seems like a complete waste of time and a hugh pain in > the rear. All you need to do is build a 4.0 kernel, install it under > some random name (say /kernel.current) boot with it to insure that it > works. That, at least, was not the case with an upgrade I attempted a few days ago. On booting with kernel.GENERIC (from -current) it hung mounting the disks. Trying to go back to kernel.stable didn't work, because I'd had to update the /dev entries for -current, and they wouldn't work with -stable. I had to dig out fixit floppies and restore from a backup. Ordinarily, you'd make sure that userland, /dev, and the kernel are all in sync before you reboot. However, in this case (and as advised by src/UPDATING) you have to reboot with a new kernel after updating /dev, but before you update the userland. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:19: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop3.ptld.uswest.net (ptldpop3.ptld.uswest.net [198.36.160.3]) by hub.freebsd.org (Postfix) with SMTP id 33B0F37C0EB for ; Tue, 7 Mar 2000 11:18:55 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 50215 invoked by alias); 7 Mar 2000 19:18:09 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 50204 invoked by uid 0); 7 Mar 2000 19:18:08 -0000 Received: from unknown (HELO laptop.cybcon.com) (63.163.56.38) by pop.ptld.uswest.net with SMTP; 7 Mar 2000 19:18:08 -0000 Content-Length: 1224 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <001d01bf8866$64ded4b0$2260e4d0@CHAOS> Date: Tue, 07 Mar 2000 11:15:49 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Jay Oliver Subject: Re: sshd in current....no config files in /etc/ssh Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, well, I useally merge files by hand because I am not familiar with mergemaster......how would I do this by hand? On 07-Mar-00 Jay Oliver wrote: > Regardless, without using mergemaster, the NEW config files will never have > gotten placed into /etc > Make world does not in and of itself in any way touch those configuration > files. > > - Jay Oliver > > ----- Original Message ----- > From: "William Woods" > To: "Oscar Bonilla" > Cc: > Sent: Tuesday, March 07, 2000 1:34 PM > Subject: Re: sshd in current....no config files in /etc/ssh > > >> No, I dident. I dident have old ssh (the port one) to merge. This is the > 1st >> time use of ssh on this system. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: bwoods2@uswest.net Date: 07-Mar-00 Time: 11:14:52l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:25:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id C7E9537BFF5 for ; Tue, 7 Mar 2000 11:25:09 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id LAA75252; Tue, 7 Mar 2000 11:26:07 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200003071926.LAA75252@troutmask.apl.washington.edu> Subject: Re: sshd in current....no config files in /etc/ssh In-Reply-To: from William Woods at "Mar 7, 2000 11:15:49 am" To: bwoods2@uswest.net Date: Tue, 7 Mar 2000 11:26:07 -0800 (PST) Cc: Jay Oliver , freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William Woods wrote: > OK, well, I useally merge files by hand because I am not familiar with > mergemaster......how would I do this by hand? > man mergemaster If you insist on doing it by hand, start with "diff -urN /etc /usr/src/etc" -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:34:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop3.ptld.uswest.net (ptldpop3.ptld.uswest.net [198.36.160.3]) by hub.freebsd.org (Postfix) with SMTP id 5392137BD12 for ; Tue, 7 Mar 2000 11:34:35 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 61748 invoked by alias); 7 Mar 2000 19:33:48 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 61711 invoked by uid 0); 7 Mar 2000 19:33:46 -0000 Received: from unknown (HELO laptop.cybcon.com) (63.163.56.164) by pop.ptld.uswest.net with SMTP; 7 Mar 2000 19:33:46 -0000 Content-Length: 910 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200003071926.LAA75252@troutmask.apl.washington.edu> Date: Tue, 07 Mar 2000 11:31:26 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Steve Kargl Subject: Re: sshd in current....no config files in /etc/ssh Cc: freebsd-current@FreeBSD.ORG, Jay Oliver , bwoods2@uswest.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good god, I am saying that the files to merger dont exist....there is nothing to merge... This is the eror I get when trying to run ssdd.... /etc/ssh/sshd_config: No such file or directory the file sshd_config does not exist on my system to merge... On 07-Mar-00 Steve Kargl wrote: > William Woods wrote: >> OK, well, I useally merge files by hand because I am not familiar with >> mergemaster......how would I do this by hand? >> > > man mergemaster > > If you insist on doing it by hand, start with > "diff -urN /etc /usr/src/etc" > > -- > Steve ---------------------------------- E-Mail: bwoods2@uswest.net Date: 07-Mar-00 Time: 11:29:42l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:36:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta.scient.com (mta.Scient.COM [208.29.209.245]) by hub.freebsd.org (Postfix) with SMTP id 4AB1E37B53F for ; Tue, 7 Mar 2000 11:36:14 -0800 (PST) (envelope-from cnielsen@scient.com) Received: (qmail 22885 invoked from network); 7 Mar 2000 19:36:08 -0000 Received: from tep01-sfo.scient.com (HELO ender.scient.com) (208.29.209.9) by mta.scient.com with SMTP; 7 Mar 2000 19:36:08 -0000 Received: (qmail 616 invoked by uid 1001); 7 Mar 2000 05:35:31 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14532.38179.208634.408231@ender.scient.com> Date: Mon, 6 Mar 2000 21:35:31 -0800 (PST) From: Christopher Nielsen To: current@freebsd.org Subject: Getty/Init weirdness X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Reply-To: cnielsen@pobox.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After much perusing of source code, scouring of cvs log messages, and searching the archives, I've determined I have no idea where else to look for this problem I'm having. The problem is this: After booting, starting all services, and getting to the point where init usually spawns the getty processes on ttyv[0-7], I get no login prompts and no virtual terminal sessions. I'm able to login over the network, and everything else looks normal once logged in, except there are no getty processes. This is with a -current of a few hours ago, including a new kernel, running on a ThinkPad 770X. Below is my kernel config file. Any help would be greatly appreciated, including pointers to relevant source files. -- Christopher Nielsen (enkhyl|cnielsen)@pobox.com Enkhyl on IRC --- Begin Kernel Config File --- machine i386 cpu I586_CPU cpu I686_CPU ident ENDER maxusers 32 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MAXMEM="(127*1024)" options INET #InterNETworking options INET6 #IPv6 options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options IPSEC_IPV6FWD #IP security tunnel for IPv6 options IPSEC_DEBUG #debug for IP security options NETGRAPH #netgraph(4) system options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MD_ROOT #MFS usable as root device, "MFS" req'ed options SOFTUPDATES options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options PQ_LARGECACHE #color for 512k/16k cache options INCLUDE_CONFIG_FILE #Include this file in kernel options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options MD5 options DDB options ICMP_BANDLIM options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options MSGBUF_SIZE=40960 options PNPBIOS device isa device pci device fdc0 at isa? port IO_FD1 irq 8 drq 2 device fd0 at fdc0 drive 0 device ata device atadisk device atapicd device scbus # SCSI bus (required) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x2 device psm0 at atkbdc? irq 12 device vga0 at isa? pseudo-device splash device sc0 at isa? options SC_HISTORY_SIZE=32768 options SC_NORM_ATTR=(FG_GREEN|BG_BLACK) options SC_NORM_REV_ATTR=(FG_YELLOW|BG_BLACK) options SC_KERNEL_CONS_ATTR=(FG_LIGHTGREEN|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_YELLOW|BG_BLACK) options SC_DEBUG_LEVEL=5 device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? flags 0x31 # Advanced Power Management device card device pcic0 at isa? device pcic1 at isa? device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device ep device xe0 device wi device aic0 at isa? device pcm device csa pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif 4 # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) pseudo-device streams pseudo-device bpf #Berkeley packet filter device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) --- End Kernel Config File --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:42: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.uunet.ca (mail2.uunet.ca [142.77.1.15]) by hub.freebsd.org (Postfix) with ESMTP id E961937B6AC for ; Tue, 7 Mar 2000 11:41:55 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail2.uunet.ca with ESMTP id <599861-9523>; Tue, 7 Mar 2000 14:37:31 -0500 Date: Tue, 7 Mar 2000 14:41:36 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: bwoods2@uswest.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: sshd in current....no config files in /etc/ssh In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That is what mergemaster does, it places everything you could ever need in a temporary root, diffs it against /etc, merges anything existing, tells you if there is a file that you do not have, you answer 'i' and it installs the default file. Despite the name, mergemaster is not only for merging, it's about the most handy tool I've ever come across for make worlds, makes updating configs a very easy task indeed. Doug definately deserves a few hundred pats on the back for that program. Matt -- Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] On Tue, 7 Mar 2000, William Woods wrote: : Date: Tue, 7 Mar 2000 14:31:26 -0500 : From: William Woods : Reply-To: bwoods2@uswest.net : To: Steve Kargl : Cc: freebsd-current@FreeBSD.ORG, Jay Oliver , : bwoods2@uswest.net : Subject: Re: sshd in current....no config files in /etc/ssh : : Good god, I am saying that the files to merger dont exist....there is nothing : to merge... : : This is the eror I get when trying to run ssdd.... : : /etc/ssh/sshd_config: No such file or directory : : the file sshd_config does not exist on my system to merge... : : On 07-Mar-00 Steve Kargl wrote: : > William Woods wrote: : >> OK, well, I useally merge files by hand because I am not familiar with : >> mergemaster......how would I do this by hand? : >> : > : > man mergemaster : > : > If you insist on doing it by hand, start with : > "diff -urN /etc /usr/src/etc" : > : > -- : > Steve : : : ---------------------------------- : E-Mail: bwoods2@uswest.net : Date: 07-Mar-00 : Time: 11:29:42l : ---------------------------------- : : NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, : Subchapter II, 227, and all unsolicited commercial e-mail sent to this : address is subject to a download and archival fee in the amount of $500 US : : : : To Unsubscribe: send mail to majordomo@FreeBSD.org : with "unsubscribe freebsd-current" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:43:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id EF4F237BD8C for ; Tue, 7 Mar 2000 11:43:16 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12SPse-000PYU-00; Tue, 07 Mar 2000 21:42:56 +0200 From: Sheldon Hearn To: cnielsen@pobox.com Cc: current@FreeBSD.ORG Subject: Re: Getty/Init weirdness In-reply-to: Your message of "Mon, 06 Mar 2000 21:35:31 PST." <14532.38179.208634.408231@ender.scient.com> Date: Tue, 07 Mar 2000 21:42:56 +0200 Message-ID: <98237.952458176@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 06 Mar 2000 21:35:31 PST, Christopher Nielsen wrote: > After booting, starting all services, and getting to the point where > init usually spawns the getty processes on ttyv[0-7], I get no login > prompts and no virtual terminal sessions. You should probably show us your /etc/ttys, not your kernel config. :-) Also, have a look in /var/log/messages for error messages from getty(8). Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:44: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id AE35E37C142; Tue, 7 Mar 2000 11:44:00 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id LAA04168; Tue, 7 Mar 2000 11:44:00 -0800 (PST) Date: Tue, 7 Mar 2000 11:44:00 -0800 From: Brooks Davis To: Nik Clayton Cc: Brooks Davis , current@freebsd.org Subject: Re: Alternative way to do -stable to -current upgrade Message-ID: <20000307114400.A27909@orion.ac.hmc.edu> References: <20000305202435.A39101@catkin.nothing-going-on.org> <20000307110109.A52023@catkin.nothing-going-on.org> <20000307101957.A5565@orion.ac.hmc.edu> <20000307191442.B19024@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000307191442.B19024@catkin.nothing-going-on.org>; from nik@freebsd.org on Tue, Mar 07, 2000 at 07:14:42PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 07:14:42PM +0000, Nik Clayton wrote: > On Tue, Mar 07, 2000 at 10:19:57AM -0800, Brooks Davis wrote: > > On Tue, Mar 07, 2000 at 11:01:09AM +0000, Nik Clayton wrote: > > > To which the response has been nil. At this point, you're either all > > > struck dumb by the staggering simplicity and elegance of this approach, > > > or you're sat there slowly shaking your head, wondering how I could be > > > quite so stupid :-) > > > > > > Come on then, which is it? > > > > To be honest it seems like a complete waste of time and a hugh pain in > > the rear. All you need to do is build a 4.0 kernel, install it under > > some random name (say /kernel.current) boot with it to insure that it > > works. > > That, at least, was not the case with an upgrade I attempted a few days > ago. On booting with kernel.GENERIC (from -current) it hung mounting the > disks. Trying to go back to kernel.stable didn't work, because I'd had > to update the /dev entries for -current, and they wouldn't work with > -stable. I had to dig out fixit floppies and restore from a backup. > > Ordinarily, you'd make sure that userland, /dev, and the kernel are all > in sync before you reboot. However, in this case (and as advised by > src/UPDATING) you have to reboot with a new kernel after updating /dev, > but before you update the userland. You don't need to update /dev though. As long as you don't change anything else, a 4.0 kernel will work just fine with a 3.x /dev and userland (other then top and friends). You can delay updating /dev until later as the ata code will deal with wd devices as well as ad devices. I built my current laptop configuration by installing 3.3 from CD, cvsuping to 4.0, installing a new kernel, and then building and installing world. I looked at UPDATING. I think it's wrong. It should have you test a new kernel before rebuilding /dev. You should do it, but like the scsi disk renaming it isn't mandatory, at least for now. I think the problem is that UPDATING is a bit to optomistic about things. If you have a system that works with the new ata driver it's correct, but otherwise it's a good way to waste your system. :-( -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:45:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id C4B7637B53F for ; Tue, 7 Mar 2000 11:45:20 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id LAA75408; Tue, 7 Mar 2000 11:46:22 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200003071946.LAA75408@troutmask.apl.washington.edu> Subject: Re: sshd in current....no config files in /etc/ssh In-Reply-To: from William Woods at "Mar 7, 2000 11:31:26 am" To: bwoods2@uswest.net Date: Tue, 7 Mar 2000 11:46:22 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG, Jay Oliver X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG troutmask:root[204] locate sshd_config /usr/local/etc/sshd_config /usr/src/crypto/openssh/sshd_config man locate man 8 sshd William Woods wrote: > Good god, I am saying that the files to merger dont exist....there is nothing > to merge... I don't see you making that statement below. You said "OK, well, I useally merge files by hand because I am not familiar with mergemaster......how would I do this by hand?" "man mergemaster" will familiarize you with the command. "diff ..." is how you might start to do it by hand. If a file does not appear to exist (oh, ah, such as /etc/sshd_config), try RTFM. > > This is the eror I get when trying to run ssdd.... > > /etc/ssh/sshd_config: No such file or directory > > the file sshd_config does not exist on my system to merge... > > On 07-Mar-00 Steve Kargl wrote: > > William Woods wrote: > >> OK, well, I useally merge files by hand because I am not familiar with > >> mergemaster......how would I do this by hand? > >> > > > > man mergemaster > > > > If you insist on doing it by hand, start with > > "diff -urN /etc /usr/src/etc" > > > > -- > > Steve > > > ---------------------------------- > E-Mail: bwoods2@uswest.net > Date: 07-Mar-00 > Time: 11:29:42l > ---------------------------------- > > NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, > Subchapter II, 227, and all unsolicited commercial e-mail sent to this > address is subject to a download and archival fee in the amount of $500 US > -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:47:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4DAA437BD4F for ; Tue, 7 Mar 2000 11:47:25 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id MAA04563; Tue, 7 Mar 2000 12:18:52 -0800 (PST) Date: Tue, 7 Mar 2000 12:18:52 -0800 From: Alfred Perlstein To: Christopher Nielsen Cc: current@FreeBSD.ORG Subject: Re: Getty/Init weirdness Message-ID: <20000307121852.H14279@fw.wintelcom.net> References: <14532.38179.208634.408231@ender.scient.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14532.38179.208634.408231@ender.scient.com>; from cnielsen@pobox.com on Mon, Mar 06, 2000 at 09:35:31PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Christopher Nielsen [000307 12:09] wrote: > After much perusing of source code, scouring of cvs log messages, and > searching the archives, I've determined I have no idea where else to > look for this problem I'm having. > > The problem is this: > > After booting, starting all services, and getting to the point where > init usually spawns the getty processes on ttyv[0-7], I get no login > prompts and no virtual terminal sessions. When was the last time you've cvsup'd and built world before it broke? I added some functionality to init, but that was about 2 weeks ago. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:47:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ruhr.de (ns.ruhr.de [141.39.224.34]) by hub.freebsd.org (Postfix) with SMTP id 30EF237B6AC for ; Tue, 7 Mar 2000 11:47:35 -0800 (PST) (envelope-from ue@nathan.ruhr.de) Received: (qmail 88969 invoked by alias); 7 Mar 2000 19:46:51 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.9.3/8.9.3) id SAA67777; Tue, 7 Mar 2000 18:36:19 +0100 (CET) (envelope-from ue) Date: Tue, 7 Mar 2000 18:36:18 +0100 From: Udo Erdelhoff To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... Message-ID: <20000307183618.E73925@nathan.ruhr.de> References: <200003062032.NAA61484@harmony.village.org> <90891.952421163@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <90891.952421163@axl.ops.uunet.co.za>; from sheldonh@uunet.co.za on Tue, Mar 07, 2000 at 11:26:03AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 11:26:03AM +0200, Sheldon Hearn wrote: > Is it supposed to be possible to drop a "1024-bit" host key from the old > ssh1 port into /etc/ssh? It works for me. I've created my host key with ssh-1.2.26 and the base system OpenSSH accepted it without any problems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:47:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ruhr.de (ns.ruhr.de [141.39.224.34]) by hub.freebsd.org (Postfix) with SMTP id 0AF6937C182 for ; Tue, 7 Mar 2000 11:47:39 -0800 (PST) (envelope-from ue@nathan.ruhr.de) Received: (qmail 88999 invoked by alias); 7 Mar 2000 19:46:56 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.9.3/8.9.3) id UAA80589; Tue, 7 Mar 2000 20:51:27 +0100 (CET) (envelope-from ue) Date: Tue, 7 Mar 2000 20:51:26 +0100 From: Udo Erdelhoff To: Ruslan Ermilov Cc: current@FreeBSD.ORG Subject: Re: 3.4 -> 4.0 upgrade problems Message-ID: <20000307205126.F73925@nathan.ruhr.de> References: <20000307115632.A72634@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: <20000307115632.A72634@relay.ucb.crimea.ua>; from ru@ucb.crimea.ua on Tue, Mar 07, 2000 at 11:56:32AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 11:56:32AM +0200, Ruslan Ermilov wrote: > + make buildkernel installkernel KERNEL="NAME_OF_YOUR_KERNEL" You should skip the "KERNEL=..." part. buildkernel and installkernel use KERNEL for *everything* - including the filename of the new kernel. In other words: root@nathan# ls -l / | grep '^-' [.profile, .cshrc, COPYRIGHT] -r-xr-xr-x 1 root wheel 2130036 5 Mär 18:00 kernel root@nathan# make buildkernel KERNEL=UE && make installkernel KERNEL=UE [several minutes later] root@nathan# ls -l / | grep '^-' [.profile, .cshrc, COPYRIGHT] -r-xr-xr-x 1 root wheel 2130036 7 Mär 19:39 UE -r-xr-xr-x 1 root wheel 2130036 5 Mär 18:00 kernel And upon reboot, the system will boot /kernel, not /UE. 4.0-current as of 05-MAR-2000. "make buildkernel" and "make installkernel" use GENERIC and kernel for the config file and the filename of the kernel. UPDATING should only contain this basic version. BTW, make buildkernel KERNEL=GENERIC;make installkernel KERNEL=GENERIC installs /GENERIC :( The big question: Is it a bug or is it a feature? Being able to create a kernel without messing with your existing kernel is an important feature for large installations: A dedicated build server could create WEBKERNEL, MAILKERNEL, FIREWALLKERNEL, SCSIKERNEL, IDEKERNEL etc. to be used by other machines. On the other hand, a lot of people will small/one-machine installations will wonder just why their new kernel doesn't work as expected. And yes, I've been there... /s/Udo (working on a possible solution for this problem) -- Eat the rich -- the poor are tough and stringy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:47:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 0B3A637C184 for ; Tue, 7 Mar 2000 11:47:41 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12SPsn-0003RE-00; Tue, 07 Mar 2000 19:43:05 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12SPsn-000CJe-00; Tue, 07 Mar 2000 19:43:05 +0000 Date: Tue, 7 Mar 2000 19:43:05 +0000 From: Ben Smithurst To: Richard J Kuhns Cc: freebsd-current@freebsd.org Subject: Re: YA ssh question (ssh-askpass?) Message-ID: <20000307194305.C62624@strontium.scientia.demon.co.uk> References: <14533.13881.134031.173029@localhost.grauel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14533.13881.134031.173029@localhost.grauel.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard J Kuhns wrote: > I've installed a Tcl/Tk version of ssh-askpass in /usr/local/bin (which > works by itself; I've tried it). I've also set SSH_ASKPASS_ENV to > /usr/local/bin/ssh-askpass, but it hasn't made any difference. ben@platinum:/usr/src/crypto/openssh$ grep ssh-askpass * ssh.h: * Default path to ssh-askpass used by ssh-add, ssh.h:#define SSH_ASKPASS_DEFAULT "/usr/X11R6/bin/ssh-askpass" have you tried putting it in that location? -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 11:53:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 457D237BB7F for ; Tue, 7 Mar 2000 11:53:34 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id VAA41732; Tue, 7 Mar 2000 21:53:04 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200003071953.VAA41732@zibbi.mikom.csir.co.za> Subject: Re: sysinstall and the status of des encryption? In-Reply-To: <200003070532.AAA83828@bb01f39.unx.sas.com> from "John W. DeBoskey" at "Mar 7, 2000 00:32:23 am" To: jwd@unx.sas.com (John W. DeBoskey) Date: Tue, 7 Mar 2000 21:53:04 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG, jwd@sas.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > A quick question before I try to come up with a fix and > patches for a problem that I believe to be a moving target. > > I have run 'make release' to create 4.0-20000306-SNAP with > sources current as of 2am March 6th. When running sysinstall > and selecting the encryption components, sysinstall > fails trying to locate crypto/des.inf. When looking through > /usr/src/release/Makefile, it doesn't appear that des.inf > and des.?? are created anymore, but instead located in > crypto.inf and crypto.??. > > So, I believe sysinstall needs to be updated so des.?? > is not installed anymore. Hmmmm, so that is what it is. I also saw it break when I tried to install a release with crypto stuff, but hadn't had a chance to find out why it happened. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12: 2:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [24.234.53.177]) by hub.freebsd.org (Postfix) with ESMTP id EB77C37BDC3 for ; Tue, 7 Mar 2000 12:02:39 -0800 (PST) (envelope-from freebsd@mrynet.com) Received: (from freebsd@localhost) by mrynet.com (8.9.3/8.9.3) id MAA09569 for freebsd-current@freebsd.org; Tue, 7 Mar 2000 12:02:38 -0800 (PST) (envelope-from freebsd) Posted-Date: Tue, 7 Mar 2000 12:02:38 -0800 (PST) Message-Id: <200003072002.MAA09569@mrynet.com> From: freebsd@mrynet.com (FreeBSD mailing list) Date: Tue, 7 Mar 2000 12:02:38 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@freebsd.org Subject: Re: sshd in current....no config files in /etc/ssh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did the following to manually set up ssh after the world build: cp /usr/src/crypto/openssh/sshd_config /etc/ssh It's as simple as that. Then when you reboot next, the host key will be regenerated by /etc/rc.network, provided you updated that from /usr/src/etc as well. If you don't want to wait until reboot to start sshd, do: /usr/bin/ssh-keygen -N "" -f /etc/ssh/ssh_host_key This is the command used by /etc/rc.network. It Worked For Me. You know people, it's quite sad that those with knowledge simply refuse to answer simple questions without "RTFM" attitudes and indirect (and more frequently direct) insults to intelligence and sensibilities. There is absolutely no reason why you can't submit the help, with suggestion toward ones perception of "the Right Way" to do it, rather than beat the issue to death with superior posturing. Pursue your Ideal Methodologies, but try some constructiveness rather than the Attitudes of the Norm common on other development lists. -scott -- Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com MRY Systems staylor@mrynet.lv (Skots Gregorijs Akmentins-Teilors -- just call me "Skots") ----- Labak miris neka sarkans ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12: 3:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop3.ptld.uswest.net (ptldpop3.ptld.uswest.net [198.36.160.3]) by hub.freebsd.org (Postfix) with SMTP id 5093A37B53F for ; Tue, 7 Mar 2000 12:03:26 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 81660 invoked by alias); 7 Mar 2000 20:02:42 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 81627 invoked by uid 0); 7 Mar 2000 20:02:40 -0000 Received: from unknown (HELO laptop.cybcon.com) (63.163.56.33) by pop.ptld.uswest.net with SMTP; 7 Mar 2000 20:02:40 -0000 Content-Length: 2940 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 07 Mar 2000 12:00:19 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Matt Heckaman Subject: Re: sshd in current....no config files in /etc/ssh Cc: freebsd-current@FreeBSD.ORG, bwoods2@uswest.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks....I used that "i" option and it worked...well, almost. I have the files I need in /etc/ssh but when I start sshd I get this now..... error: Could not load host key: /etc/ssh/ssh_host_key: No such file or directory On 07-Mar-00 Matt Heckaman wrote: > That is what mergemaster does, it places everything you could ever need in > a temporary root, diffs it against /etc, merges anything existing, tells > you if there is a file that you do not have, you answer 'i' and it installs > the default file. > > Despite the name, mergemaster is not only for merging, it's about the most > handy tool I've ever come across for make worlds, makes updating configs a > very easy task indeed. Doug definately deserves a few hundred pats on the > back for that program. > > Matt > -- > Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] > !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] > > On Tue, 7 Mar 2000, William Woods wrote: > >: Date: Tue, 7 Mar 2000 14:31:26 -0500 >: From: William Woods >: Reply-To: bwoods2@uswest.net >: To: Steve Kargl >: Cc: freebsd-current@FreeBSD.ORG, Jay Oliver , >: bwoods2@uswest.net >: Subject: Re: sshd in current....no config files in /etc/ssh >: >: Good god, I am saying that the files to merger dont exist....there is >: nothing >: to merge... >: >: This is the eror I get when trying to run ssdd.... >: >: /etc/ssh/sshd_config: No such file or directory >: >: the file sshd_config does not exist on my system to merge... >: >: On 07-Mar-00 Steve Kargl wrote: >: > William Woods wrote: >: >> OK, well, I useally merge files by hand because I am not familiar with >: >> mergemaster......how would I do this by hand? >: >> >: > >: > man mergemaster >: > >: > If you insist on doing it by hand, start with >: > "diff -urN /etc /usr/src/etc" >: > >: > -- >: > Steve >: >: >: ---------------------------------- >: E-Mail: bwoods2@uswest.net >: Date: 07-Mar-00 >: Time: 11:29:42l >: ---------------------------------- >: >: NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, >: Subchapter II, 227, and all unsolicited commercial e-mail sent to this >: address is subject to a download and archival fee in the amount of $500 US >: >: >: >: To Unsubscribe: send mail to majordomo@FreeBSD.org >: with "unsubscribe freebsd-current" in the body of the message >: > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: bwoods2@uswest.net Date: 07-Mar-00 Time: 11:59:10l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:12:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta.scient.com (mta.Scient.COM [208.29.209.245]) by hub.freebsd.org (Postfix) with SMTP id 4FF3837BB7F for ; Tue, 7 Mar 2000 12:12:08 -0800 (PST) (envelope-from cnielsen@scient.com) Received: (qmail 25840 invoked from network); 7 Mar 2000 20:12:00 -0000 Received: from tep01-sfo.scient.com (HELO ender.scient.com) (208.29.209.9) by mta.scient.com with SMTP; 7 Mar 2000 20:12:00 -0000 Received: (qmail 510 invoked by uid 1001); 7 Mar 2000 20:12:27 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14533.25259.297488.968412@ender.scient.com> Date: Tue, 7 Mar 2000 12:12:27 -0800 (PST) From: Christopher Nielsen To: Sheldon Hearn Cc: cnielsen@pobox.com, current@FreeBSD.ORG Subject: Re: Getty/Init weirdness In-Reply-To: <98237.952458176@axl.ops.uunet.co.za> References: <14532.38179.208634.408231@ender.scient.com> <98237.952458176@axl.ops.uunet.co.za> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Reply-To: cnielsen@pobox.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Sheldon" == Sheldon Hearn writes: Sheldon> You should probably show us your /etc/ttys, not your Sheldon> kernel config. :-) Doh! I meant to do that. :-) See below. Sheldon> Also, have a look in /var/log/messages for error messages Sheldon> from getty(8). No error messages from getty, but I also forgot to include that I turned on maximum debugging for the syscons driver. I'm attaching my dmesg output, too. --- Begin dmesg output --- 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 #24: Mon Mar 6 20:41:55 PST 2000 root@ender.scient.com:/usr/src/sys/compile/ENDER Calibrating clock(s) ... TSC clock: 297766253 Hz, i8254 clock: 1193106 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Pentium II Xeon/Celeron (297.79-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 133169152 (130048K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x0034d000 - 0x07ef5fff, 129667072 bytes (31657 pages) sc0: releasing kbd0 sc0: kbd_release returned 0 sc0: kbd != NULL!, index:0, unit:0, flags:0x150000 sc0: keyboard 0 sc0: kbd index:0, unit:0, flags:0x350000 avail memory = 120524800 (117700K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fd800 bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x0 pnpbios: Found PnP BIOS data at 0xc00fe700 pnpbios: Entry = f0000:e724 Rev = 1.0 pnpbios: Event flag at 415 Other BIOS signatures found: ACPI: 000fd6e0 Preloaded elf kernel "kernel" at 0xc0334000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 pci_open(1): mode 1 addr port (0x0cf8) is 0x000038c8 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 40000000, size 26 found-> vendor=0x8086, dev=0x7191, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x104c, dev=0xac1d, revid=0x00 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=4 secondarybus=2 intpin=a, irq=255 map[10]: type 1, range 32, base 50102000, size 12 found-> vendor=0x104c, dev=0xac1d, revid=0x00 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=7 secondarybus=5 intpin=b, irq=255 map[10]: type 1, range 32, base 50101000, size 12 found-> vendor=0x1013, dev=0x6001, revid=0x01 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=0 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000fcf0, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=255 map[20]: type 1, range 32, base 00008400, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 0000efa0, size 4 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x1023, dev=0x939a, revid=0xf3 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=255 map[10]: type 1, range 32, base 70800000, size 23 map[14]: type 1, range 32, base 71000000, size 17 map[18]: type 1, range 32, base 70000000, size 23 pci1: on pcib1 pci1: (vendor=0x1023, dev=0x939a) at 0.0 pcic-pci0: mem 0x50102000-0x50102fff at device 2.0 on pci0 PCI Config space: 00: ac1d104c 02100007 06070000 0082a808 10: 50102000 020000a0 b0040200 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 03c001ff 40: 00eb1014 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 00449060 00000000 01818148 fba97543 90: 606283c0 00000000 00000000 00000000 Cardbus Socket registers: 00: 0000000f: 00000000: 30000510: 00000000: 10: 00000000: 00000000: 00000000: 00000000: ExCa registers: 00: 83 0c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10: 00 00 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 pcic-pci1: mem 0x50101000-0x50101fff at device 2.1 on pci0 PCI Config space: 00: ac1d104c 02100007 06070000 0082a808 10: 50101000 020000a0 b0070500 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 03c002ff 40: 00eb1014 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 00449060 00000000 01818148 fba97543 90: 606282c0 00000000 00000000 00000000 Cardbus Socket registers: 00: 00000000: 00000000: 30000306: 00000000: 10: 00000000: 00000000: 00000000: 00000000: ExCa registers: 00: 83 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10: 00 00 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 csa0: irq 0 at device 6.0 on pci0 device_probe_and_attach: csa0 attach returned 6 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcf0-0xfcff at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 ata1: mask=03 status0=50 status1=01 ata1: mask=03 status0=00 status1=01 ata1: devices = 0x4 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x8400-0x841f at device 7.2 on pci0 uhci0: Invalid irq 255 uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS device_probe_and_attach: uhci0 attach returned 6 chip1: port 0xefa0-0xefaf at device 7.3 on pci0 pnpbios: 23 devices, largest 980 bytes PNP0000: adding io range 0x20-0x21, size=0x2, align=0x1 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0x1 PNP0000: adding irq mask 00x4 PNP0000: start dependant pnpbios: handle 0 device ID PNP0000 (0000d041) PNP0200: adding io range 0-0xf, size=0x10, align=0x1 PNP0200: adding io range 0x80-0x8f, size=0x10, align=0x1 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 PNP0200: adding dma mask 0x10 PNP0200: start dependant pnpbios: handle 1 device ID PNP0200 (0002d041) PNP0100: adding irq mask 00x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 PNP0100: start dependant pnpbios: handle 2 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x73, size=0x4, align=0x1 PNP0b00: start dependant pnpbios: handle 3 device ID PNP0b00 (000bd041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 PNP0800: start dependant pnpbios: handle 4 device ID PNP0800 (0008d041) PNP0303: adding irq mask 00x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 PNP0303: start dependant pnpbios: handle 5 device ID PNP0303 (0303d041) IBM3780: adding irq mask 0x1000 IBM3780: start dependant pnpbios: handle 6 device ID IBM3780 (80374d24) PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: adding irq mask 0x2000 PNP0c04: start dependant pnpbios: handle 7 device ID PNP0c04 (040cd041) PNP0700: adding irq mask 0x40 PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x80 PNP0700: adding dma mask 0x4 PNP0700: start dependant pnpbios: handle 8 device ID PNP0700 (0007d041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 PNP0a03: start dependant pnpbios: handle 9 device ID PNP0a03 (030ad041) PNP0c02: adding io range 0x22-0x22, size=0x1, align=0 PNP0c02: adding io range 0x2e-0x2f, size=0x2, align=0 PNP0c02: adding io range 0x92-0x92, size=0x1, align=0 PNP0c02: adding io range 0xb2-0xb3, size=0x2, align=0 PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0 PNP0c02: adding io range 0x15e0-0x15ef, size=0x10, align=0 PNP0c02: adding io range 0xef00-0xefaf, size=0xb0, align=0 PNP0c02: adding memory range 0-0x9ffff, size=0xa0000 PNP0c02: adding memory range 0xf0000-0xfffff, size=0x10000 PNP0c02: adding memory range 0x100000-0x7ffffff, size=0x7f00000 PNP0c02: adding memory range 0xffff0000-0xffffffff, size=0x10000 PNP0c02: start dependant pnpbios: handle 10 device ID PNP0c02 (020cd041) PNP0400: adding irq mask 0x80 PNP0400: adding io range 0x378-0x37b, size=0x4, align=0 PNP0400: start dependant pnpbios: handle 11 device ID PNP0400 (0004d041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 PNP0501: start dependant pnpbios: handle 13 device ID PNP0501 (0105d041) CSC0100: adding io range 0x530-0x537, size=0x8, align=0 CSC0100: adding io range 0x388-0x38b, size=0x4, align=0 CSC0100: adding io range 0x220-0x233, size=0x14, align=0x20 CSC0100: adding irq mask 0x400 CSC0100: adding dma mask 0x2 CSC0100: adding dma mask 0x1 CSC0100: start dependant pnpbios: handle 14 device ID CSC0100 (0001630e) CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 CSC0110: start dependant pnpbios: handle 15 device ID CSC0110 (1001630e) CSC0101: adding io range 0-0xffffffff, size=0, align=0 CSC0101: start dependant pnpbios: handle 16 device ID CSC0101 (0101630e) CSC0103: adding io range 0x330-0x333, size=0x4, align=0x10 CSC0103: adding irq mask 0x800 CSC0103: start dependant pnpbios: handle 17 device ID CSC0103 (0301630e) IBM3765: adding io range 0-0xffffffff, size=0, align=0 IBM3765: adding io range 0-0xffffffff, size=0, align=0 IBM3765: adding irq mask 0000 IBM3765: adding irq mask 0000 IBM3765: adding dma mask 00 IBM3765: start dependant pnpbios: handle 18 device ID IBM3765 (65374d24) IBM0071: adding irq mask 0000 IBM0071: adding io range 0-0xffffffff, size=0, align=0x1 IBM0071: adding dma mask 00 IBM0071: start dependant pnpbios: handle 19 device ID IBM0071 (71004d24) PNP0e03: adding io range 0x3e0-0x3e1, size=0x2, align=0 PNP0e03: start dependant pnpbios: handle 20 device ID PNP0e03 (030ed041) PNP0680: adding irq mask 0x4000 PNP0680: adding io range 0x1f0-0x1f7, size=0x8, align=0 PNP0680: adding io range 0x3f6-0x3f7, size=0x2, align=0 PNP0680: adding io range 0xfcf0-0xfcf7, size=0x8, align=0 PNP0680: start dependant pnpbios: handle 23 device ID PNP0680 (8006d041) PNP0680: adding irq mask 0x8000 PNP0680: adding io range 0x170-0x177, size=0x8, align=0 PNP0680: adding io range 0x376-0x376, size=0x1, align=0 PNP0680: adding io range 0xfcf8-0xfcff, size=0x8, align=0 PNP0680: start dependant pnpbios: handle 25 device ID PNP0680 (8006d041) PNP0c02: adding io range 0x2100-0x217f, size=0x80, align=0 PNP0c02: adding io range 0x2180-0x21ff, size=0x80, align=0 PNP0c02: skipping empty range PNP0c02: start dependant pnpbios: handle 27 device ID PNP0c02 (020cd041) Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 8 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold atkbdc0: at port 0x60-0x6f on isa0 atkbd0: flags 0x2 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x54ab (2) kbd0: atkbd0, AT 101/102 (2), config:0x2, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: status 10 00 64 psm: data 08 00 00 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k vga0: vga: WARNING: video mode switching is not fully supported on this adapter VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 04 b0 9c ce 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 04 b0 9c ce 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: releasing kbd0 sc0: kbd_release returned 0 sc0: kbd != NULL!, index:0, unit:0, flags:0x1d0000 sc0: keyboard 0 sc0: kbd index:0, unit:0, flags:0x3d0000 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic: management irq 3 pcic0: at irq 3 on isa0 pccard0: on pcic0 pccard1: on pcic0 sio0: irq maps: 0x49 0x59 0x49 0x49 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ppc0: parallel port found at 0x378 ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode isa_probe_children: probing PnP devices unknown: can't assign resources unknown0: at port 0-0xf,0x80-0x8f,0xc0-0xdf drq 4 on isa0 unknown1: at port 0x40-0x43 irq 0 on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown2: at port 0xf0-0xff irq 13 on isa0 unknown: can't assign resources unknown3: at port 0xcf8-0xcff on isa0 unknown4: at port 0x22,0x2e-0x2f,0x92,0xb2-0xb3,0x4d0-0x4d1,0x15e0-0x15ef,0xef00-0xefaf iomem 0-0x9ffff,0xf0000-0xfffff,0x100000-0x7ffffff,0xffff0000-0xffffffff on isa0 unknown: can't assign resources unknown: can't assign resources pcm0: at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 10 drq 1,0 on isa0 pcm: setmap 30000, ff00; 0xc8574000 -> 30000 pcm: setmap 40000, ff00; 0xc8584000 -> 40000 unknown5: at port 0x538-0x53f on isa0 unknown6: at port 0x10 on isa0 unknown7: at port 0x330-0x333 irq 11 on isa0 unknown: can't assign resources unknown: can't assign resources unknown8: at port 0x3e0-0x3e1 on isa0 unknown: can't assign resources unknown: can't assign resources unknown9: at port 0x2100-0x217f,0x2180-0x21ff on isa0 BIOS Geometries: 0:03feef3f 0..1022=1023 cylinders, 0..239=240 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: lo0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: faith0 attached IPsec: Initialized Security Association Processing. ata0-master: success setting up UDMA2 mode on PIIX4 chip ad0: ATA-3 disk at ata0 as master ad0: 7815MB (16006410 sectors), 16938 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1-master: success setting up PIO4 mode on generic chip acd0: DVD-ROM drive at ata1 as master acd0: read 3437KB/s (3437KB/s), 512KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA, DVD-ROM, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad0a pccard: card inserted, slot 0 ad0s1: type 0xa5, start 0, end = 16006409, size 16006410 : OK start_init: trying /sbin/init scopen: dev:12,255, unit:0, vty:255 Linux-ELF exec handler installed pcic: I/O win 0 flags 17 240-24f pcic: I/O win 0 flags 7 240-24f ep0: <3Com Etherlink III 3C589> at port 0x240-0x24f irq 9 slot 0 on pccard0 pcic: I/O win 0 flags 17 240-24f ep0: Ethernet address 00:10:4b:de:51:8c ep0: supplying EUI64: 00:10:4b:ff:fe:de:51:8c bpf: ep0 attached svr4 ELF exec handler installed scopen: dev:12,0, unit:0, vty:0 ep0: starting DAD for fe80:0007::0210:4bff:fede:518c sc0: scclose(), done. scopen: dev:12,0, unit:0, vty:0 sc0: scclose(), done. scopen: dev:12,1, unit:0, vty:1 sc0: scclose(), done. scopen: dev:12,2, unit:0, vty:2 sc0: scclose(), done. scopen: dev:12,3, unit:0, vty:3 sc0: scclose(), done. scopen: dev:12,4, unit:0, vty:4 sc0: scclose(), done. scopen: dev:12,5, unit:0, vty:5 ep0: DAD complete for fe80:0007::0210:4bff:fede:518c - no duplicates found --- End dmesg output --- --- Begin /etc/ttys --- # # $FreeBSD: src/etc/etc.i386/ttys,v 1.6 1999/08/27 23:23:57 peter Exp $ # @(#)ttys 5.1 (Berkeley) 4/17/89 # # This file specifies various information about terminals on the system. # It is used by several different programs. Common entries for the # various columns include: # # name The name of the terminal device. # # getty The program to start running on the terminal. Typically a # getty program, as the name implies. Other common entries # include none, when no getty is needed, and xdm, to start the # X Window System. # # type The initial terminal type for this port. For hardwired # terminal lines, this will contain the type of terminal used. # For virtual consoles, the correct type is cons25. Other # common values include network for network connections on # pseudo-terminals, dialup for incoming modem ports, and unknown # when the terminal type cannot be predetermined. # # status Must be on or off. If on, init will run the getty program on # the specified port. If the word "secure" appears, this tty # allows root login. # # name getty type status comments # # If console is marked "insecure", then init will ask for the root password # when going to single-user mode. console none unknown off insecure # ttyv0 "/usr/libexec/getty Pc" cons25 on secure # Virtual terminals ttyv1 "/usr/libexec/getty Pc" cons25 on insecure ttyv2 "/usr/libexec/getty Pc" cons25 on insecure ttyv3 "/usr/libexec/getty Pc" cons25 on insecure ttyv4 "/usr/libexec/getty Pc" cons25 on insecure ttyv5 "/usr/libexec/getty Pc" cons25 on insecure ttyv6 "/usr/libexec/getty Pc" cons25 on insecure ttyv7 "/usr/libexec/getty Pc" cons25 on insecure ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm on insecure # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyd0 "/usr/libexec/getty std.9600" dialup off secure ttyd1 "/usr/libexec/getty std.9600" dialup off secure ttyd2 "/usr/libexec/getty std.9600" dialup off secure ttyd3 "/usr/libexec/getty std.9600" dialup off secure # Pseudo terminals ttyp0 none network ttyp1 none network ttyp2 none network ttyp3 none network ttyp4 none network ttyp5 none network ttyp6 none network ttyp7 none network ttyp8 none network ttyp9 none network ttypa none network ttypb none network ttypc none network ttypd none network ttype none network ttypf none network ttypg none network ttyph none network ttypi none network ttypj none network ttypk none network ttypl none network ttypm none network ttypn none network ttypo none network ttypp none network ttypq none network ttypr none network ttyps none network ttypt none network ttypu none network ttypv none network ttyq0 none network ttyq1 none network ttyq2 none network ttyq3 none network ttyq4 none network ttyq5 none network ttyq6 none network ttyq7 none network ttyq8 none network ttyq9 none network ttyqa none network ttyqb none network ttyqc none network ttyqd none network ttyqe none network ttyqf none network ttyqg none network ttyqh none network ttyqi none network ttyqj none network ttyqk none network ttyql none network ttyqm none network ttyqn none network ttyqo none network ttyqp none network ttyqq none network ttyqr none network ttyqs none network ttyqt none network ttyqu none network ttyqv none network ttyr0 none network ttyr1 none network ttyr2 none network ttyr3 none network ttyr4 none network ttyr5 none network ttyr6 none network ttyr7 none network ttyr8 none network ttyr9 none network ttyra none network ttyrb none network ttyrc none network ttyrd none network ttyre none network ttyrf none network ttyrg none network ttyrh none network ttyri none network ttyrj none network ttyrk none network ttyrl none network ttyrm none network ttyrn none network ttyro none network ttyrp none network ttyrq none network ttyrr none network ttyrs none network ttyrt none network ttyru none network ttyrv none network ttys0 none network ttys1 none network ttys2 none network ttys3 none network ttys4 none network ttys5 none network ttys6 none network ttys7 none network ttys8 none network ttys9 none network ttysa none network ttysb none network ttysc none network ttysd none network ttyse none network ttysf none network ttysg none network ttysh none network ttysi none network ttysj none network ttysk none network ttysl none network ttysm none network ttysn none network ttyso none network ttysp none network ttysq none network ttysr none network ttyss none network ttyst none network ttysu none network ttysv none network ttyP0 none network ttyP1 none network ttyP2 none network ttyP3 none network ttyP4 none network ttyP5 none network ttyP6 none network ttyP7 none network ttyP8 none network ttyP9 none network ttyPa none network ttyPb none network ttyPc none network ttyPd none network ttyPe none network ttyPf none network ttyPg none network ttyPh none network ttyPi none network ttyPj none network ttyPk none network ttyPl none network ttyPm none network ttyPn none network ttyPo none network ttyPp none network ttyPq none network ttyPr none network ttyPs none network ttyPt none network ttyPu none network ttyPv none network ttyQ0 none network ttyQ1 none network ttyQ2 none network ttyQ3 none network ttyQ4 none network ttyQ5 none network ttyQ6 none network ttyQ7 none network ttyQ8 none network ttyQ9 none network ttyQa none network ttyQb none network ttyQc none network ttyQd none network ttyQe none network ttyQf none network ttyQg none network ttyQh none network ttyQi none network ttyQj none network ttyQk none network ttyQl none network ttyQm none network ttyQn none network ttyQo none network ttyQp none network ttyQq none network ttyQr none network ttyQs none network ttyQt none network ttyQu none network ttyQv none network ttyR0 none network ttyR1 none network ttyR2 none network ttyR3 none network ttyR4 none network ttyR5 none network ttyR6 none network ttyR7 none network ttyR8 none network ttyR9 none network ttyRa none network ttyRb none network ttyRc none network ttyRd none network ttyRe none network ttyRf none network ttyRg none network ttyRh none network ttyRi none network ttyRj none network ttyRk none network ttyRl none network ttyRm none network ttyRn none network ttyRo none network ttyRp none network ttyRq none network ttyRr none network ttyRs none network ttyRt none network ttyRu none network ttyRv none network ttyS0 none network ttyS1 none network ttyS2 none network ttyS3 none network ttyS4 none network ttyS5 none network ttyS6 none network ttyS7 none network ttyS8 none network ttyS9 none network ttySa none network ttySb none network ttySc none network ttySd none network ttySe none network ttySf none network ttySg none network ttySh none network ttySi none network ttySj none network ttySk none network ttySl none network ttySm none network ttySn none network ttySo none network ttySp none network ttySq none network ttySr none network ttySs none network ttySt none network ttySu none network ttySv none network --- End /etc/ttys --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:18:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta.scient.com (mta.Scient.COM [208.29.209.245]) by hub.freebsd.org (Postfix) with SMTP id E185037BFF5 for ; Tue, 7 Mar 2000 12:17:59 -0800 (PST) (envelope-from cnielsen@scient.com) Received: (qmail 26201 invoked from network); 7 Mar 2000 20:17:53 -0000 Received: from tep01-sfo.scient.com (HELO ender.scient.com) (208.29.209.9) by mta.scient.com with SMTP; 7 Mar 2000 20:17:53 -0000 Received: (qmail 519 invoked by uid 1001); 7 Mar 2000 20:18:20 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14533.25611.821257.320956@ender.scient.com> Date: Tue, 7 Mar 2000 12:18:19 -0800 (PST) From: Christopher Nielsen To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: Getty/Init weirdness In-Reply-To: <20000307121852.H14279@fw.wintelcom.net> References: <14532.38179.208634.408231@ender.scient.com> <20000307121852.H14279@fw.wintelcom.net> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Reply-To: cnielsen@pobox.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Alfred" == Alfred Perlstein writes: Alfred> When was the last time you've cvsup'd and built world Alfred> before it broke? I added some functionality to init, but Alfred> that was about 2 weeks ago. That's not the problem. I already tried backing it out of my local tree and rebuilding init. Same behavior. :-) I cvsup'd yesterday around 6PM. I built and installed world immediately after that and then built and installed a new kernel. -- Christopher Nielsen (enkhyl|cnielsen)@pobox.com Enkhyl on IRC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:21:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from css-1.cs.iastate.edu (css-1.cs.iastate.edu [129.186.3.24]) by hub.freebsd.org (Postfix) with ESMTP id E7B5D37C198 for ; Tue, 7 Mar 2000 12:21:29 -0800 (PST) (envelope-from ghelmer@cs.iastate.edu) Received: from popeye.cs.iastate.edu (ghelmer@popeye.cs.iastate.edu [129.186.3.4]) by css-1.cs.iastate.edu (8.9.0/8.9.0) with ESMTP id OAA13451; Tue, 7 Mar 2000 14:21:14 -0600 (CST) Received: from localhost (ghelmer@localhost) by popeye.cs.iastate.edu (8.9.0/8.9.0) with ESMTP id OAA04322; Tue, 7 Mar 2000 14:21:10 -0600 (CST) X-Authentication-Warning: popeye.cs.iastate.edu: ghelmer owned process doing -bs Date: Tue, 7 Mar 2000 14:21:09 -0600 (CST) From: Guy Helmer To: Richard J Kuhns Cc: freebsd-current@FreeBSD.ORG Subject: Re: YA ssh question (ssh-askpass?) In-Reply-To: <14533.13881.134031.173029@localhost.grauel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Richard J Kuhns wrote: > I just built- and installed- world about an hour ago, and removed the > ssh-1.2.27 port. The build and install went without a problem, but I've > apparently lost some functionality. > > I spend most of my time in xemacs, and I make heavy use of CVS to access a > couple of remote repositories. I've had CVS_RSH=ssh for quite some time, > and use vc (the emacs/xemacs interface to CVS) to handle my sources. Up > until this morning, it worked fine. Whenever I needed to access a remote > repository, a window popped up to ask for my password. Now, I just get an > error message saying "You have no controlling tty. Cannot read > passphrase." > > I've installed a Tcl/Tk version of ssh-askpass in /usr/local/bin (which > works by itself; I've tried it). I've also set SSH_ASKPASS_ENV to > /usr/local/bin/ssh-askpass, but it hasn't made any difference. I have the OpenSSH-ssh-askpass port installed (which created the program /usr/X11R6/bin/ssh-askpass), and I use the command env SSH_ASKPASS=/usr/X11R6/bin/ssh-askpass /usr/bin/ssh-add in my X session startup scripts to make ssh-add use ssh-askpass to request my ssh passphrase. It seems to me that the name of the environment variable you are using is incorrect (remove "_ENV" from the end). Guy Guy Helmer, Ph.D. Candidate, Iowa State University Dept. of Computer Science Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:23:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E783F37BB7F for ; Tue, 7 Mar 2000 12:23:28 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id MAA05382; Tue, 7 Mar 2000 12:54:57 -0800 (PST) Date: Tue, 7 Mar 2000 12:54:57 -0800 From: Alfred Perlstein To: Christopher Nielsen Cc: current@FreeBSD.ORG Subject: Re: Getty/Init weirdness Message-ID: <20000307125457.I14279@fw.wintelcom.net> References: <14532.38179.208634.408231@ender.scient.com> <20000307121852.H14279@fw.wintelcom.net> <14533.25611.821257.320956@ender.scient.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14533.25611.821257.320956@ender.scient.com>; from cnielsen@pobox.com on Tue, Mar 07, 2000 at 12:18:19PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Christopher Nielsen [000307 12:50] wrote: > >>>>> "Alfred" == Alfred Perlstein writes: > > Alfred> When was the last time you've cvsup'd and built world > Alfred> before it broke? I added some functionality to init, but > Alfred> that was about 2 weeks ago. > > That's not the problem. I already tried backing it out of my local > tree and rebuilding init. Same behavior. :-) > > I cvsup'd yesterday around 6PM. I built and installed world > immediately after that and then built and installed a new kernel. *phew* Thanks for testing this. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:27:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ruhr.de (ns.ruhr.de [141.39.224.34]) by hub.freebsd.org (Postfix) with SMTP id 688A537BD3F for ; Tue, 7 Mar 2000 12:27:29 -0800 (PST) (envelope-from ue@nathan.ruhr.de) Received: (qmail 98601 invoked by alias); 7 Mar 2000 20:26:43 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.9.3/8.9.3) id VAA81062; Tue, 7 Mar 2000 21:29:33 +0100 (CET) (envelope-from ue) Date: Tue, 7 Mar 2000 21:29:33 +0100 From: Udo Erdelhoff To: Brad Knowles Cc: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... Message-ID: <20000307212933.G73925@nathan.ruhr.de> References: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> <0v3dq2py9q.fsf@cs.uni-magdeburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from blk@skynet.be on Tue, Mar 07, 2000 at 06:48:56PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 06:48:56PM +0100, Brad Knowles wrote: > Must be a FreeBSD vs. Solaris thing Are you using OpenSSH or the 'normal' ssh on your Solaris box? I've just tried to copy files between my FreeBSD box @home and one of 'my' Solaris boxes @work. All four possible directions work exactly as expected with both binary and text files. @home: FreeBSD 4.0, 05-MAR-2000, USA_RESIDENT=NO SSH Version OpenSSH-1.2.2, protocol version 1.5. Compiled with SSL. @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. /s/Udo -- I'd like to meet the man who invented sex and see what he's working on now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:31:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id D0F3237BE2C for ; Tue, 7 Mar 2000 12:31:26 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id VAA07200 for freebsd-current@freebsd.org; Tue, 7 Mar 2000 21:31:25 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id TAA59586 for freebsd-current@freebsd.org; Tue, 7 Mar 2000 19:47:39 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: ssh strangeness in -current... Date: 7 Mar 2000 19:47:39 +0100 Message-ID: <8a3isb$1q5p$1@bigeye.rhein-neckar.de> References: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > I've been following this thread for a while, and I'd like to ask > a related question -- can anyone else successfully use scp with > OpenSSH? An emphatic YES--for incrementally improving versions of OpenSSH over the last couple of months, on FreeBSD/i386, OpenBSD/sparc, OpenBSD/alpha, and Red Hat Linux/alpha. Interoperability with Ylonen-SSH 1.2.xx on various platforms is also fine. I don't know why there are so many detractors. Since I also play around with OpenBSD, I've followed OpenSSH from relatively early on, and I've experienced some of the initial growing pains. However, OpenSSH has been rather mature for quite some time now, and I've replaced Ylonen-SSH with OpenSSH on all machines where I have the authority to do so. > On the one machine on which I've installed OpenSSH so far, > it appears that scp into the machine is totally broken. There's something broken in your ssh{,d} setup. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:33:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id AEE1637BE2C for ; Tue, 7 Mar 2000 12:33:31 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id OAA00074 for freebsd-current@freebsd.org; Tue, 7 Mar 2000 14:33:18 -0600 (CST) Date: Tue, 7 Mar 2000 14:33:18 -0600 (CST) From: Mohit Aron Message-Id: <200003072033.OAA00074@cs.rice.edu> To: freebsd-current@freebsd.org Subject: when is 4.0 up for release ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, is FreeBSD-4.0-RELEASE going to happen anytime soon ? - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:36: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A802B37B512; Tue, 7 Mar 2000 12:36:03 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6B7112E8155 for ; Tue, 7 Mar 2000 12:36:03 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 7 Mar 2000 12:36:03 -0800 (PST) From: Kris Kennaway To: John Polstra Subject: Re: ssh strangeness in -current... In-Reply-To: <200003071804.KAA89683@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, John Polstra wrote: > In the past I have had interoperability problems between F-Secure > and the open source versions of ssh. But the cause then was simply > that the F-Secure keys were too long (> 1024 bits) for ssh's rsaref > to cope with. That would certainly do it. OpenSSH should probably print a more helpful error message in this case, though. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:36:47 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 3511237BEA7; Tue, 7 Mar 2000 12:36:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 323D42E8155 for ; Tue, 7 Mar 2000 12:36:45 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 7 Mar 2000 12:36:45 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: Re: ssh strangeness in -current... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, John Polstra wrote: > In the past I have had interoperability problems between F-Secure > and the open source versions of ssh. But the cause then was simply > that the F-Secure keys were too long (> 1024 bits) for ssh's rsaref > to cope with. That would certainly do it. OpenSSH should probably print a more helpful error message in this case, though. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:44:25 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 2CD8B37BE2C; Tue, 7 Mar 2000 12:44:23 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 295A42E815B; Tue, 7 Mar 2000 12:44:23 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 7 Mar 2000 12:44:23 -0800 (PST) From: Kris Kennaway To: Richard J Kuhns Cc: freebsd-current@freebsd.org Subject: Re: YA ssh question (ssh-askpass?) In-Reply-To: <14533.13881.134031.173029@localhost.grauel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Richard J Kuhns wrote: > I've installed a Tcl/Tk version of ssh-askpass in /usr/local/bin (which > works by itself; I've tried it). I've also set SSH_ASKPASS_ENV to > /usr/local/bin/ssh-askpass, but it hasn't made any difference. There's an X11 version in /usr/ports/security/openssh-askpass, but it should probably work with other "equivalent" versions. By default it looks for it in /usr/X11R6/bin/ssh-askpass (compile-time define), but can be overridden using the SSH_ASKPATH environment variable. This is documented in the ssh-add(1) manpage :-) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:47:50 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id E76E337BEDE; Tue, 7 Mar 2000 12:47:48 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E53CD2E815B; Tue, 7 Mar 2000 12:47:48 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 7 Mar 2000 12:47:48 -0800 (PST) From: Kris Kennaway To: bwoods2@uswest.net Cc: Matt Heckaman , freebsd-current@FreeBSD.ORG Subject: Re: sshd in current....no config files in /etc/ssh In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, William Woods wrote: > Thanks....I used that "i" option and it worked...well, almost. I have the files > I need in /etc/ssh but when I start sshd I get this now..... > > error: Could not load host key: /etc/ssh/ssh_host_key: No such file or > directory It will be created for you next time you boot, or you can do it by hand (man ssh-keygen).. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:54:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop3.ptld.uswest.net (ptldpop3.ptld.uswest.net [198.36.160.3]) by hub.freebsd.org (Postfix) with SMTP id AA2DE37BB7F for ; Tue, 7 Mar 2000 12:53:57 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 17844 invoked by alias); 7 Mar 2000 20:53:13 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 17794 invoked by uid 0); 7 Mar 2000 20:53:11 -0000 Received: from unknown (HELO laptop.cybcon.com) (63.163.56.79) by pop.ptld.uswest.net with SMTP; 7 Mar 2000 20:53:11 -0000 Content-Length: 1045 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 07 Mar 2000 12:50:47 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Kris Kennaway Subject: Re: sshd in current....no config files in /etc/ssh Cc: freebsd-current@FreeBSD.ORG, Matt Heckaman , bwoods2@uswest.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you... On 07-Mar-00 Kris Kennaway wrote: > On Tue, 7 Mar 2000, William Woods wrote: > >> Thanks....I used that "i" option and it worked...well, almost. I have the >> files >> I need in /etc/ssh but when I start sshd I get this now..... >> >> error: Could not load host key: /etc/ssh/ssh_host_key: No such file or >> directory > > It will be created for you next time you boot, or you can do it by hand > (man ssh-keygen).. > > Kris > > ---- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: bwoods2@uswest.net Date: 07-Mar-00 Time: 12:50:01l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 12:57:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 045BB37BD12 for ; Tue, 7 Mar 2000 12:57:51 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.04) with ESMTP id FAA24053; Wed, 8 Mar 2000 05:57:43 +0900 (JST) To: Yoshinobu Inoue Cc: dick@tar.com, fink@es.net, ab@astralblue.com, fenner@research.att.com, jose@we.lc.ehu.es, current@FreeBSD.ORG, 6bone@ISI.EDU In-reply-to: shin's message of Tue, 07 Mar 2000 10:26:28 JST. <20000307102628S.shin@nd.net.fujitsu.co.jp> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? From: itojun@iijlab.net Date: Wed, 08 Mar 2000 05:57:43 +0900 Message-ID: <24051.952462663@coconut.itojun.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Very unfortunately, 6to4 is not yet supported in FreeBSD/KAME. >So now available options will be, > -Use freenet6 (for one hosts). > -Get IPv6 address block and connect to 6bone using gif tunnel. We hope to add 6to4 support for KAME/FreeBSD very soon (next week is a good guess). We may need some more testing before real use, but it should work. it is in KAME/NetBSD already, I just don't have time to make it work on othre *BSDs yet... itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 13: 7:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from cgi.norcom2000.com (cgi.norcom2000.com [208.18.247.5]) by hub.freebsd.org (Postfix) with ESMTP id 03B2A37B5AB for ; Tue, 7 Mar 2000 13:07:55 -0800 (PST) (envelope-from jon@cgi.norcom2000.com) Received: (from jon@localhost) by cgi.norcom2000.com (8.8.7/8.8.7) id PAA08513 for freebsd-current@freebsd.org; Tue, 7 Mar 2000 15:07:24 -0600 Message-ID: <20000307150718.A8510@cgi.norcom2000.com> Date: Tue, 7 Mar 2000 15:07:18 -0600 From: jon@cgi.norcom2000.com To: freebsd-current@freebsd.org Subject: Re: 3.4 -> 4.0 upgrade problems References: <20000307170540.A64753@relay.ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <20000307170540.A64753@relay.ucb.crimea.ua>; from Ruslan Ermilov on Tue, Mar 07, 2000 at 05:05:40PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oN tUE, mAR 07, 2000 AT 05:05:40PM +0200, Ruslan Ermilov wrote: > On Wed, Mar 08, 2000 at 01:02:29AM +1000, Idea Receiver wrote: > [...] > > btw, I have problem to make release, it kept complain about that i didnt > > set the USA_RESIDENT, however, I did! both in /etc and /etc/defaults. Can > > please someone help me out with this as well.. > > > > thanks :) > > Set USA_RESIDENT in environment rather than in /etc. Or just put USA_RESIDENT=YES in /etc/make.conf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 13:14:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id B6E5E37B533 for ; Tue, 7 Mar 2000 13:14:33 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip176.r7.d.bel.nwlink.com (ip176.r7.d.bel.nwlink.com [207.202.173.176]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id NAA02097; Tue, 7 Mar 2000 13:14:19 -0800 (PST) Date: Tue, 7 Mar 2000 13:08:47 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: bwoods2@uswest.net Cc: Steve Kargl , freebsd-current@FreeBSD.ORG, Jay Oliver Subject: Re: sshd in current....no config files in /etc/ssh In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, William Woods wrote: > Good god, I am saying that the files to merger dont exist....there is nothing > to merge... > > This is the eror I get when trying to run ssdd.... > > /etc/ssh/sshd_config: No such file or directory > > the file sshd_config does not exist on my system to merge... That's because it's not under /etc until *after* you've run mergemaster. Right now it's sitting in /var/tmp/tmproot/etc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 13:19:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from igw8.watson.ibm.com (igw8.watson.ibm.com [198.81.209.20]) by hub.freebsd.org (Postfix) with ESMTP id 0E68537B52F for ; Tue, 7 Mar 2000 13:19:19 -0800 (PST) (envelope-from ian@whalley.org) Received: from mailhub.watson.ibm.com (mailhub.watson.ibm.com [9.2.250.97]) by igw8.watson.ibm.com (8.9.3/8.9.3/05-14-1999) with ESMTP id QAA19440; Tue, 7 Mar 2000 16:19:15 -0500 Received: from whalley.org (ss7.pok.socks.ibm.com [9.14.3.72]) by mailhub.watson.ibm.com (8.8.7/Feb-20-98) with ESMTP id QAA12808; Tue, 7 Mar 2000 16:19:13 -0500 Message-ID: <38C5724E.84052394@whalley.org> Date: Tue, 07 Mar 2000 16:19:10 -0500 From: Ian Whalley X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Remote upgrade from 3.4-STABLE to 4.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am already running 4.0-CURRENT on machines to which I have access, and have been doing for some time. It's great stuff, of course [!]. However, I have one machine (which is at the other end of a few hours of driving involving the New Jersey Turnpike, which is not my idea of fun) running 3.4-STABLE. I update it every so often via SSH, and everything is fine. 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... So... anyone done it? Best; inw -- Ian Whalley @ . org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 13:27:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id C414837B511; Tue, 7 Mar 2000 13:27:10 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip176.r7.d.bel.nwlink.com (ip176.r7.d.bel.nwlink.com [207.202.173.176]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id NAA04217; Tue, 7 Mar 2000 13:27:08 -0800 (PST) Date: Tue, 7 Mar 2000 13:21:36 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: Kris Kennaway Cc: freebsd-current@FreeBSD.ORG Subject: Re: no openssh after build In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, R Joseph Wright wrote: > On Mon, 6 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? I just re-cvsupped today with crypto and rebuilt. Everything went as smooth as summer butter. I'm really impressed with how quickly and cleanly you developers are able to make things happen. I've only been observing for a short time but it is very interesting. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 13:27:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from moran.grauel.com (usr1-33.mintel.net [63.81.123.48]) by hub.freebsd.org (Postfix) with ESMTP id D4C7D37B74D; Tue, 7 Mar 2000 13:27:33 -0800 (PST) (envelope-from rjk@moran.grauel.com) Received: (from rjk@localhost) by moran.grauel.com (8.9.3/8.9.3) id QAA05231; Tue, 7 Mar 2000 16:27:21 -0500 (EST) (envelope-from rjk) From: Richard J Kuhns MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14533.29753.499155.780744@localhost.grauel.com> Date: Tue, 7 Mar 2000 16:27:21 -0500 (EST) To: Kris Kennaway Cc: Richard J Kuhns , freebsd-current@FreeBSD.ORG Subject: Re: YA ssh question (ssh-askpass?) In-Reply-To: References: <14533.13881.134031.173029@localhost.grauel.com> X-Mailer: VM 6.75 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: > On Tue, 7 Mar 2000, Richard J Kuhns wrote: > > > I've installed a Tcl/Tk version of ssh-askpass in /usr/local/bin (which > > works by itself; I've tried it). I've also set SSH_ASKPASS_ENV to > > /usr/local/bin/ssh-askpass, but it hasn't made any difference. > > There's an X11 version in /usr/ports/security/openssh-askpass, but it > should probably work with other "equivalent" versions. By default it looks > for it in /usr/X11R6/bin/ssh-askpass (compile-time define), but can be > overridden using the SSH_ASKPATH environment variable. This is documented > in the ssh-add(1) manpage :-) > > Kris So does all this mean that I now have to start using ssh-add/ssh-agent? Does that actually buy me anything? I was under the impression that ssh-agent was there to allow you to enter your passphrase once, and then not have to do it again that session. I *don't* want to do that; when I'm on-site, I *want* to be prompted for my password when I attempt to commit changes to a file (and I work with multiple repositories). Thanks... -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 13:42:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id 1FD8A37BE7A; Tue, 7 Mar 2000 13:42:52 -0800 (PST) (envelope-from freebsd@mauibuilt.com) Received: (from freebsd@localhost) by mauibuilt.com (8.9.3/8.9.3) id LAA26901; Tue, 7 Mar 2000 11:52:41 -1000 (HST) (envelope-from freebsd) From: FreeBSD MAIL Message-Id: <200003072152.LAA26901@mauibuilt.com> Subject: Adaptec 29160 To: freebsd-hardware@freebsd.org Date: Tue, 7 Mar 2000 11:52:40 -1000 (HST) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there support for the adaptec 29160 U2 scsi controller? will the 29xx driver work? Thanks in advance. RP puga@mauibuitl.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 13:49:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from io.yi.org (h24-67-218-186.xx.wave.shaw.ca [24.67.218.186]) by hub.freebsd.org (Postfix) with ESMTP id 82D5737C0DB for ; Tue, 7 Mar 2000 13:49:37 -0800 (PST) (envelope-from jburkhol@home.com) Received: from io.yi.org (localhost.gvcl1.bc.wave.home.com [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id 7F452BABB; Tue, 7 Mar 2000 13:49:35 -0800 (PST) X-Mailer: exmh version 2.1.1 10/15/1999 To: bwoods2@uswest.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: sshd in current....no config files in /etc/ssh In-Reply-To: Message from William Woods of "Tue, 07 Mar 2000 12:00:19 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Mar 2000 13:49:35 -0800 From: Jake Burkholder Message-Id: <20000307214935.7F452BABB@io.yi.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks....I used that "i" option and it worked...well, almost. I have the files > I need in /etc/ssh but when I start sshd I get this now..... > > error: Could not load host key: /etc/ssh/ssh_host_key: No such file or > directory If you want to track current you must use mergemaster. This is probably because you haven't updated rc.network... case ${sshd_enable} in [Yy][Ee][Ss]) if [ ! -f /etc/ssh/ssh_host_key ]; then echo ' creating ssh host key'; /usr/bin/ssh-keygen -N "" -f /etc/ssh/ssh_host_key fi ;; esac My host key was generated automatically when I rebooted and I was quite impressed. Just type 'mergemaster' as root. It's interactive and doesn't overwrite anything automatically. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 13:52:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 4D5AF37BEB9 for ; Tue, 7 Mar 2000 13:52:43 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id WAA01201 for freebsd-current@freebsd.org; Tue, 7 Mar 2000 22:52:41 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id WAA67839 for freebsd-current@freebsd.org; Tue, 7 Mar 2000 22:11:17 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: ssh strangeness in -current... Date: 7 Mar 2000 22:11:17 +0100 Message-ID: <8a3r9l$227m$1@bigeye.rhein-neckar.de> References: <200003062032.NAA61484@harmony.village.org> <90891.952421163@axl.ops.uunet.co.za> To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > What about the off-by-one hostkey length problem? The client gives a warning when you connect to an old server with this problem. > Is it supposed to be possible to drop a "1024-bit" host key from > the old ssh1 port into /etc/ssh ? I have switched several hosts from Ylonen-SSH to OpenSSH and have retained all host keys. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 14:13:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from dyn-9.blackbox-2.netaxs.com (dyn-9.blackbox-2.netaxs.com [207.106.60.9]) by hub.freebsd.org (Postfix) with ESMTP id BCE2C37BAFC for ; Tue, 7 Mar 2000 14:13:17 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from localhost (localhost [127.0.0.1]) by dyn-9.blackbox-2.netaxs.com (8.9.3/8.9.3) with ESMTP id RAA00213 for ; Tue, 7 Mar 2000 17:13:09 -0500 (EST) (envelope-from bleez@netaxs.com) Date: Tue, 7 Mar 2000 17:13:09 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net To: freebsd-current@freebsd.org Subject: Network problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently set up a network at home to share an internet connection with a win98 box. Currently it's ppp/nat with a modem, in a few days ADSL. It works just fine for a while, but I'm experiencing unexplained outages where I have to do an ifconfig dc1 down/up to wake it up again. No error messages on the console. I also installed Samba on the box which works great (as long as the network is up). I'm using a 3COM Home Connect hub. Here's the output from ifconfig: dc1: flags=8847 mtu 1500 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:80:c6:f9:70:ec media: autoselect (100baseTX) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX none dmesg: dc0: port 0xe800-0xe8ff mem 0xebfbfe00-0xebfbfeff irq 9 at device 4.0 on pci0 dc0: Ethernet address: 00:80:c6:f9:5b:0d miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc1: port 0xec00-0xecff mem 0xebfbff00-0xebfbffff irq 10 at device 5.0 on pci0 dc1: Ethernet address: 00:80:c6:f9:70:ec miibus1: on dc1 dcphy1: on miibus1 dcphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto I understand that this driver is new to 4.0, so I'm taking a shot here. Any ideas? Thanks, Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 14:17: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id C762B37BAFC for ; Tue, 7 Mar 2000 14:16:54 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (postfix@[209.69.195.170]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id OAA55402; Tue, 7 Mar 2000 14:16:50 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 28B441A11; Tue, 7 Mar 2000 17:16:47 -0500 (EST) Date: Tue, 7 Mar 2000 17:16:47 -0500 From: Will Andrews To: FreeBSD mailing list Cc: freebsd-current@FreeBSD.ORG Subject: Re: sshd in current....no config files in /etc/ssh Message-ID: <20000307171647.B64425@shadow.blackdawn.com> References: <200003072002.MAA09569@mrynet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003072002.MAA09569@mrynet.com>; from freebsd@mrynet.com on Tue, Mar 07, 2000 at 12:02:38PM +0000 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 12:02:38PM +0000, FreeBSD mailing list wrote: > You know people, it's quite sad that those with knowledge simply refuse > to answer simple questions without "RTFM" attitudes and indirect (and > more frequently direct) insults to intelligence and sensibilities. When you have more experience helping people on a frequent basis, perhaps you will revise this statement. Try helping folks out every day on IRC for 2 or 3 years and tell me what you think THEN. Alternative: answer every question asked on freebsd-questions for same period. You'll see the point once you accomplish this. > There is absolutely no reason why you can't submit the help, with > suggestion toward ones perception of "the Right Way" to do it, > rather than beat the issue to death with superior posturing. There is absolutely no reason why people should lift a finger to help somebody else when said question/inquiry has been documented somewhere on the web or in the manpages, or someplace else. It's all about the old quote, "Catch a man a fish and you feed him for a day. Teach a man how to fish and you feed him for a lifetime." I believe Mike Smith has an abortion of this aphorism in his sig. ;-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 14:20:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop3.ptld.uswest.net (ptldpop3.ptld.uswest.net [198.36.160.3]) by hub.freebsd.org (Postfix) with SMTP id 838EC37B539 for ; Tue, 7 Mar 2000 14:19:58 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 80620 invoked by alias); 7 Mar 2000 22:19:05 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 80591 invoked by uid 0); 7 Mar 2000 22:19:02 -0000 Received: from unknown (HELO laptop.cybcon.com) (63.163.56.169) by pop.ptld.uswest.net with SMTP; 7 Mar 2000 22:19:02 -0000 Content-Length: 1432 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000307214935.7F452BABB@io.yi.org> Date: Tue, 07 Mar 2000 14:16:41 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: Jake Burkholder Subject: Re: sshd in current....no config files in /etc/ssh Cc: freebsd-current@FreeBSD.ORG, bwoods2@uswest.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, I had been doing things manually for a while now. I dod look at mergemaster and used it for ssh and it worked well. I am planning on investigating it more later on today. On 07-Mar-00 Jake Burkholder wrote: >> Thanks....I used that "i" option and it worked...well, almost. I have the >> files >> I need in /etc/ssh but when I start sshd I get this now..... >> >> error: Could not load host key: /etc/ssh/ssh_host_key: No such file or >> directory > > If you want to track current you must use mergemaster. > This is probably because you haven't updated rc.network... > > case ${sshd_enable} in > [Yy][Ee][Ss]) > if [ ! -f /etc/ssh/ssh_host_key ]; then > echo ' creating ssh host key'; > /usr/bin/ssh-keygen -N "" -f /etc/ssh/ssh_host_key > fi > ;; > esac > > My host key was generated automatically when I rebooted and I was > quite impressed. > > Just type 'mergemaster' as root. It's interactive and doesn't overwrite > anything automatically. ---------------------------------- E-Mail: bwoods2@uswest.net Date: 07-Mar-00 Time: 14:15:25l ---------------------------------- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 14:21:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 42A0537BEA1; Tue, 7 Mar 2000 14:21:11 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA86313; Tue, 7 Mar 2000 15:20:36 -0700 (MST) (envelope-from ken) Date: Tue, 7 Mar 2000 15:20:36 -0700 From: "Kenneth D. Merry" To: FreeBSD MAIL Cc: freebsd-hardware@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Adaptec 29160 Message-ID: <20000307152036.A86294@panzer.kdm.org> References: <200003072152.LAA26901@mauibuilt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003072152.LAA26901@mauibuilt.com>; from freebsd@mauibuilt.com on Tue, Mar 07, 2000 at 11:52:40AM -1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 11:52:40 -1000, FreeBSD MAIL wrote: > Is there support for the adaptec 29160 U2 scsi controller? will > the 29xx driver work? Yes, but only in -current after January 6th or so. The ahc driver is the driver that supports the Adaptec Ultra160 boards. Right now it will only run those boards at Ultra2 speeds (80MB/sec), but Justin is working on full Ultra160 support. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 14:21:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcat.heimat.gr.jp (pcat.heimat.gr.jp [211.0.53.98]) by hub.freebsd.org (Postfix) with ESMTP id 54C3B37BAFC for ; Tue, 7 Mar 2000 14:21:20 -0800 (PST) (envelope-from nakaji@tutrp.tut.ac.jp) Received: from xa12.heimat.gr.jp (xa12.heimat.gr.jp [211.0.53.97]) by pcat.heimat.gr.jp (8.9.3/3.7W) with ESMTP id HAA96396; Wed, 8 Mar 2000 07:21:04 +0900 (JST) To: Jose Marques Cc: current@freebsd.org Subject: Re: XDM login using sessreg and last, uptime, w and so on... References: <86g0u2vpz3.fsf@xa12.heimat.gr.jp> MIME-Version: 1.0 (generated by REMI 1.14.1 - =?ISO-8859-4?Q?=22Mushigawa=F2?= =?ISO-8859-4?Q?sugi=22?=) Content-Type: text/plain; charset=US-ASCII From: NAKAJI Hiroyuki Date: 08 Mar 2000 07:21:00 +0900 In-Reply-To: (Jose Marques's message of "Tue, 7 Mar 2000 17:16:52 +0000 (GMT)") Message-ID: <86zosaxvzn.fsf@xa12.heimat.gr.jp> Lines: 23 User-Agent: T-gnus/6.14.1 (based on Gnus v5.8.3) (revision 12) REMI/1.14.1 (=?ISO-8859-4?Q?Mushigawa=F2sugi?=) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.5 (i386--freebsd) MULE/4.0 (HANANOEN) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> In >>>>> Jose Marques wrote: Jose> > /usr/X11R6/lib/X11/xdm/TakeConsole is: Jose> > Jose> > /usr/X11R6/bin/sessreg -d -l $DISPLAY -x /usr/X11R6/lib/xdm/Xservers $LOGNAME Jose> ^^^^^^^ Jose> Missing X11 in path? Ahhhhh... Thank you very much! One problem is solved but another '/dev/:0' problem still remains. $ w w: /dev/:0: No such file or directory 7:15AM up 9:04, 1 user, load averages: 0.31, 0.15, 0.06 USER TTY FROM LOGIN@ IDLE WHAT nakaji p1 :0.0 7:15AM - w $ last | head nakaji :0 console Wed Mar 8 07:15 still logged in nakaji :0 console Wed Mar 8 07:11 - 07:15 (00:03) -- NAKAJI Hiroyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 14:24:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1381737B539 for ; Tue, 7 Mar 2000 14:24:21 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA86404; Tue, 7 Mar 2000 15:24:18 -0700 (MST) (envelope-from ken) Date: Tue, 7 Mar 2000 15:24:17 -0700 From: "Kenneth D. Merry" To: Mohit Aron Cc: freebsd-current@FreeBSD.ORG Subject: Re: when is 4.0 up for release ? Message-ID: <20000307152417.A86322@panzer.kdm.org> References: <200003072033.OAA00074@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003072033.OAA00074@cs.rice.edu>; from aron@cs.rice.edu on Tue, Mar 07, 2000 at 02:33:18PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 14:33:18 -0600, Mohit Aron wrote: > Hi, > is FreeBSD-4.0-RELEASE going to happen anytime soon ? Looks like it is scheduled for Monday, March 13th. Obviously that could change if problems crop up. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 15: 2:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id BA56637C180 for ; Tue, 7 Mar 2000 15:02:38 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id PAA25884; Tue, 7 Mar 2000 15:02:17 -0800 (PST) (envelope-from Doug@gorean.org) Date: Tue, 7 Mar 2000 15:02:17 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: "Matthew N. Dodd" Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Matthew N. Dodd wrote: > I've been building and rebuilding in an attempt to make sure that its not > some stupidity on my part. > > Be assured that when I'm positive I've got a reproducable error that I'll > let everyone in on the details. If you give us an idea where your breakage is, we can tell you if it's a known problem. E.g., there is a known problem with PPP(D) and NO_OPENSSL that Kris and I have already worked out a fix for. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 15: 8: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 9D58637C11D; Tue, 7 Mar 2000 15:08:00 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id PAA25917; Tue, 7 Mar 2000 15:07:58 -0800 (PST) (envelope-from Doug@gorean.org) Date: Tue, 7 Mar 2000 15:07:58 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: John Daniels Cc: freebsd-current@freebsd.org, freebsd-qa@freebsd.org, jhb@freebsd.org Subject: Re: FINAL: Installation floppies and USB In-Reply-To: <20000307032847.21893.qmail@hotmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, John Daniels wrote: > Oops: That's kudos for John *Baldwin,* NOT "Barton." A thousand pardons... Hey... calling him Barton is a _compliment_! :) Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 15:37:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from renoa.home.allusion.net (cs2727-11.austin.rr.com [24.27.27.11]) by hub.freebsd.org (Postfix) with ESMTP id 2C37D37B5CC for ; Tue, 7 Mar 2000 15:37:13 -0800 (PST) (envelope-from bard@renoa.home.allusion.net) Received: by renoa.home.allusion.net via sendmail from stdin id (Debian Smail3.2.0.102) for freebsd-current@FreeBSD.ORG; Tue, 7 Mar 2000 17:52:07 -0600 (CST) Message-ID: <20000307175207.C3611@industrial-strength.net> Date: Tue, 7 Mar 2000 17:52:07 -0600 From: Dan Potter To: freebsd-current@FreeBSD.ORG Subject: Re: when is 4.0 up for release ? References: <200003072033.OAA00074@cs.rice.edu> <20000307152417.A86322@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mutt 0.91.1i-jp1 In-Reply-To: <20000307152417.A86322@panzer.kdm.org>; from Kenneth D. Merry on Tue, Mar 07, 2000 at 03:24:17PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recall waay back on Mar 07 when Kenneth D. Merry wrote: > On Tue, Mar 07, 2000 at 14:33:18 -0600, Mohit Aron wrote: > > Hi, > > is FreeBSD-4.0-RELEASE going to happen anytime soon ? > > Looks like it is scheduled for Monday, March 13th. > > Obviously that could change if problems crop up. Has anyone thought about the problem I posted a few days ago (getcwd() breaks on unionfs in some conditions)? That seems like a pretty big problem to me... maybe not too many people use unionfs though, I don't know. If someone would give me a tip about where I should look in the kernel I would fix the problem myself but I am lost when you move past the specific fs driver. Also I've seen a number of strange freezes with one development box that's running 20000223. That may have been fixed, but we've had to go hit reset on the thing several times. No, this isn't a FUD-filled-content-free "bug flame", I'm just pointing out that there have been problems that recently.. -- When a girl can read the handwriting on the wall, she may be in the wrong rest room. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 15:38:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 9490B37B555 for ; Tue, 7 Mar 2000 15:38:44 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115213>; Wed, 8 Mar 2000 10:39:25 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: ssh strangeness in -current... In-reply-to: <200003070243.DAA52008@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Tue, Mar 07, 2000 at 01:44:28PM +1100 To: olli@dorifer.heim3.tu-clausthal.de Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Mar8.103925est.115213@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <89v0d4$9af$1@atlantis.rz.tu-clausthal.de> <200003070243.DAA52008@dorifer.heim3.tu-clausthal.de> Date: Tue, 7 Mar 2000 15:02:26 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Mar 2000, Oliver Fromme wrote: > 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. I avoid the problem by structuring my paths along the lines of $HOME/bin:/usr/local/bin:/usr/bin:/bin (everythere, not just on FreeBSD). This way, if I (as sysadmin) install something in /usr/local, it over-rides whatever the vendor supplied. (Otherwise, I probably wouldn't have installed my own version). Likewise, anything I put in my private bin directory over-rides anything in the common areas. In this case, it would mean that the version of ssh installed (in /usr/local/bin) from the ports would over-ride the /usr/bin/ssh in the base system. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 15:38:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 2EA7E37B5DB for ; Tue, 7 Mar 2000 15:38:48 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115210>; Wed, 8 Mar 2000 10:39:28 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: current lockups In-reply-to: <20000306202718.A26973@relativity.student.utwente.nl>; from djb@wit389306.student.utwente.nl on Tue, Mar 07, 2000 at 06:29:17AM +1100 To: Dave Boers Cc: Arun Sharma , freebsd-current@FreeBSD.ORG Message-Id: <00Mar8.103928est.115210@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> Date: Tue, 7 Mar 2000 09:45:55 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Mar-07 06:29:17 +1100, Dave Boers wrote: >It is rumoured that Arun Sharma had the courage to say: >> Compiling Mozilla with make -j 2 got -current to lock up, twice in >> succession. I'm running a fairly recent snapshot (a week or two old) >> on a Dual celeron box (BP6) with UDMA66 enabled. > >Finally. I've been complaining about this on several occasions. I'm also >running UDMA66 and Dual Celeron BP6. No overclocking. Later postings mention possible problems with UDMA66. The other possibility that has been discussed recently is potential priority inversions for processes using rtptio and idprio. Note that ntpd will use rtprio if the Posix P1003.1b extensions aren't enabled in the kernel. (These were enabled by default in GENERIC on i386 in mid-January). If you have the new ntpd (rather than xntpd) and are running a kernel without options P1003_1B, _KPOSIX_PRIORITY_SCHEDULING and _KPOSIX_VERSION=199309L, you could potentially get a lockup due to a priority inversion. (Though I think the probability is very small). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 15:49:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7620937B598; Tue, 7 Mar 2000 15:49:20 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA60740; Tue, 7 Mar 2000 16:49:18 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA97583; Tue, 7 Mar 2000 16:49:06 -0700 (MST) Message-Id: <200003072349.QAA97583@harmony.village.org> To: Brooks Davis Subject: Re: Alternative way to do -stable to -current upgrade Cc: Nik Clayton , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 07 Mar 2000 11:44:00 PST." <20000307114400.A27909@orion.ac.hmc.edu> References: <20000307114400.A27909@orion.ac.hmc.edu> <20000305202435.A39101@catkin.nothing-going-on.org> <20000307110109.A52023@catkin.nothing-going-on.org> <20000307101957.A5565@orion.ac.hmc.edu> <20000307191442.B19024@catkin.nothing-going-on.org> Date: Tue, 07 Mar 2000 16:49:06 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000307114400.A27909@orion.ac.hmc.edu> Brooks Davis writes: : You don't need to update /dev though. As long as you don't change : anything else, a 4.0 kernel will work just fine with a 3.x /dev and : userland (other then top and friends). You can delay updating /dev : until later as the ata code will deal with wd devices as well as ad : devices. This is incorrect information. If you ever have a dirty filesystem, the new fsck will not be able to fix that and you'll be unable to mount that filesystem w/o reboot, iirc. : I built my current laptop configuration by installing 3.3 from : CD, cvsuping to 4.0, installing a new kernel, and then building and : installing world. I looked at UPDATING. I think it's wrong. It should : have you test a new kernel before rebuilding /dev. You should do it, : but like the scsi disk renaming it isn't mandatory, at least for now. : I think the problem is that UPDATING is a bit to optomistic about : things. If you have a system that works with the new ata driver it's : correct, but otherwise it's a good way to waste your system. :-( Alternative, accurate, text welcome :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 15:51:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3B85337B56D for ; Tue, 7 Mar 2000 15:51:13 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA60760; Tue, 7 Mar 2000 16:51:06 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA97620; Tue, 7 Mar 2000 16:50:54 -0700 (MST) Message-Id: <200003072350.QAA97620@harmony.village.org> To: Udo Erdelhoff Subject: Re: 3.4 -> 4.0 upgrade problems Cc: Ruslan Ermilov , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 07 Mar 2000 20:51:26 +0100." <20000307205126.F73925@nathan.ruhr.de> References: <20000307205126.F73925@nathan.ruhr.de> <20000307115632.A72634@relay.ucb.crimea.ua> Date: Tue, 07 Mar 2000 16:50:54 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000307205126.F73925@nathan.ruhr.de> Udo Erdelhoff writes: : "make buildkernel" and "make installkernel" use GENERIC and kernel for the : config file and the filename of the kernel. UPDATING should only contain : this basic version. BTW, make buildkernel KERNEL=GENERIC;make installkernel : KERNEL=GENERIC installs /GENERIC :( Because this is so error prone, I don't even touch it at all in UPDATING. I don't like the targets and have been burned by them. The explicit instructions, while longer to type, are known to work and don't have these gotchas. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 15:52:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0DCA637B633 for ; Tue, 7 Mar 2000 15:52:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA60769; Tue, 7 Mar 2000 16:52:12 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA97642; Tue, 7 Mar 2000 16:52:00 -0700 (MST) Message-Id: <200003072352.QAA97642@harmony.village.org> To: Mohit Aron Subject: Re: when is 4.0 up for release ? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 07 Mar 2000 14:33:18 CST." <200003072033.OAA00074@cs.rice.edu> References: <200003072033.OAA00074@cs.rice.edu> Date: Tue, 07 Mar 2000 16:52:00 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003072033.OAA00074@cs.rice.edu> Mohit Aron writes: : is FreeBSD-4.0-RELEASE going to happen anytime soon ? Yes, for a suitable definition of soon :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 15:54: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D317837B598 for ; Tue, 7 Mar 2000 15:53:57 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA60777; Tue, 7 Mar 2000 16:53:51 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA97662; Tue, 7 Mar 2000 16:53:39 -0700 (MST) Message-Id: <200003072353.QAA97662@harmony.village.org> To: Ian Whalley Subject: Re: Remote upgrade from 3.4-STABLE to 4.0 Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 07 Mar 2000 16:19:10 EST." <38C5724E.84052394@whalley.org> References: <38C5724E.84052394@whalley.org> Date: Tue, 07 Mar 2000 16:53:39 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38C5724E.84052394@whalley.org> Ian Whalley writes: : In reading UPDATING (and -current), I can't see any way to upgrade : from 3.4-STABLE to (the future) 4.0-STABLE. The now mythical build process for 4.0-stable cannot be commented upon until its mythic qualities have been reduced somewhat. In other words, UPDATING can't comment on vaporware. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 15:55:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0C7F837B55B; Tue, 7 Mar 2000 15:55:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA60789; Tue, 7 Mar 2000 16:55:07 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA97682; Tue, 7 Mar 2000 16:54:55 -0700 (MST) Message-Id: <200003072354.QAA97682@harmony.village.org> To: FreeBSD MAIL Subject: Re: Adaptec 29160 Cc: freebsd-hardware@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 07 Mar 2000 11:52:40 -1000." <200003072152.LAA26901@mauibuilt.com> References: <200003072152.LAA26901@mauibuilt.com> Date: Tue, 07 Mar 2000 16:54:55 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003072152.LAA26901@mauibuilt.com> FreeBSD MAIL writes: : Is there support for the adaptec 29160 U2 scsi controller? will : the 29xx driver work? 4.0 has this support. I have its younger brother the 19160 and it works great. One caveat is that ultra160 disks are only supported at ultra2 speeds. Not a huge deal as I don't have any ultra160 disks yet. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 16: 2: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 26EBA37B55B; Tue, 7 Mar 2000 16:02:01 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA60827; Tue, 7 Mar 2000 17:01:59 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA97744; Tue, 7 Mar 2000 17:01:47 -0700 (MST) Message-Id: <200003080001.RAA97744@harmony.village.org> To: Ruslan Ermilov Subject: Re: 3.4 -> 4.0 upgrade problems Cc: Kris Kennaway , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 07 Mar 2000 11:56:32 +0200." <20000307115632.A72634@relay.ucb.crimea.ua> References: <20000307115632.A72634@relay.ucb.crimea.ua> Date: Tue, 07 Mar 2000 17:01:47 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000307115632.A72634@relay.ucb.crimea.ua> Ruslan Ermilov writes: : > 1) genassym and config were complaining about not being able to find : > libc.so.4 when I installed them. Workaround: go back and rebuild with with : > CFLAGS="-static" A better work around is cd lib/libc and do a make install. : We certainly need to update src/UPDATING accordingly, see the patch : attached. : + make buildkernel installkernel KERNEL="NAME_OF_YOUR_KERNEL" I'm not sure that this is wise. When I tried this, I got /NAME_OF_YOUR_KERNEL rather than /kernel like I'd have expected. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 16: 5:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 1DEC437B6DA for ; Tue, 7 Mar 2000 16:05:17 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id TAA21090; Tue, 7 Mar 2000 19:05:05 -0500 (EST) Date: Tue, 7 Mar 2000 19:05:04 -0500 (EST) From: "Matthew N. Dodd" To: Doug Barton Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Doug Barton wrote: > If you give us an idea where your breakage is, we can tell you if it's > a known problem. E.g., there is a known problem with PPP(D) and > NO_OPENSSL that Kris and I have already worked out a fix for. Yep, thats one of them. We'll see if I find anything else. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 16: 8: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 49F4537BAFC for ; Tue, 7 Mar 2000 16:08:06 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA59006; Tue, 7 Mar 2000 16:08:00 -0800 (PST) (envelope-from dillon) Date: Tue, 7 Mar 2000 16:08:00 -0800 (PST) From: Matthew Dillon Message-Id: <200003080008.QAA59006@apollo.backplane.com> To: Peter Jeremy Cc: Dave Boers , Arun Sharma , freebsd-current@FreeBSD.ORG Subject: Re: current lockups References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> <00Mar8.103928est.115210@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On 2000-Mar-07 06:29:17 +1100, Dave Boers wrote: :>It is rumoured that Arun Sharma had the courage to say: :>> Compiling Mozilla with make -j 2 got -current to lock up, twice in :>> succession. I'm running a fairly recent snapshot (a week or two old) :>> on a Dual celeron box (BP6) with UDMA66 enabled. :> :>Finally. I've been complaining about this on several occasions. I'm also :>running UDMA66 and Dual Celeron BP6. No overclocking. : :Later postings mention possible problems with UDMA66. The other :possibility that has been discussed recently is potential priority :inversions for processes using rtptio and idprio. : :Note that ntpd will use rtprio if the Posix P1003.1b extensions aren't :enabled in the kernel. (These were enabled by default in GENERIC on :i386 in mid-January). If you have the new ntpd (rather than xntpd) :and are running a kernel without options P1003_1B, :_KPOSIX_PRIORITY_SCHEDULING and _KPOSIX_VERSION=199309L, you could :potentially get a lockup due to a priority inversion. (Though I :think the probability is very small). : :Peter p.s. the first thing anyone having potential IDE problems should do is try the older 'wd' driver (if it supports their chipset) and see if that solves the problem. At least then we can focus on the precise location of the problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 16: 9:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id C0D6837B6DA; Tue, 7 Mar 2000 16:08:58 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id QAA04666; Tue, 7 Mar 2000 16:08:51 -0800 (PST) Date: Tue, 7 Mar 2000 16:08:51 -0800 From: Brooks Davis To: Warner Losh Cc: Nik Clayton , current@FreeBSD.ORG Subject: Re: Alternative way to do -stable to -current upgrade Message-ID: <20000307160851.A27814@orion.ac.hmc.edu> References: <20000307114400.A27909@orion.ac.hmc.edu> <20000305202435.A39101@catkin.nothing-going-on.org> <20000307110109.A52023@catkin.nothing-going-on.org> <20000307101957.A5565@orion.ac.hmc.edu> <20000307191442.B19024@catkin.nothing-going-on.org> <20000307114400.A27909@orion.ac.hmc.edu> <200003072349.QAA97583@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200003072349.QAA97583@harmony.village.org>; from imp@village.org on Tue, Mar 07, 2000 at 04:49:06PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 04:49:06PM -0700, Warner Losh wrote: > In message <20000307114400.A27909@orion.ac.hmc.edu> Brooks Davis writes: > : You don't need to update /dev though. As long as you don't change > : anything else, a 4.0 kernel will work just fine with a 3.x /dev and > : userland (other then top and friends). You can delay updating /dev > : until later as the ata code will deal with wd devices as well as ad > : devices. > > This is incorrect information. If you ever have a dirty filesystem, > the new fsck will not be able to fix that and you'll be unable to > mount that filesystem w/o reboot, iirc. I haddn't realized that. > : I built my current laptop configuration by installing 3.3 from > : CD, cvsuping to 4.0, installing a new kernel, and then building and > : installing world. I looked at UPDATING. I think it's wrong. It should > : have you test a new kernel before rebuilding /dev. You should do it, > : but like the scsi disk renaming it isn't mandatory, at least for now. > : I think the problem is that UPDATING is a bit to optomistic about > : things. If you have a system that works with the new ata driver it's > : correct, but otherwise it's a good way to waste your system. :-( > > Alternative, accurate, text welcome :-) Here's a diff. It requires one more reboot, but it avoids backing yourself into a corner. A crash between reboots is a little messy, but if you only follow these directions that's not very likely. The directions are good, but just assume support is identical and I can think of at least one case where that's not true (defective IDE controlers). -- Brooks Index: UPDATING =================================================================== RCS file: /home/ncvs/src/UPDATING,v retrieving revision 1.71 diff -u -r1.71 UPDATING --- UPDATING 2000/02/23 05:51:02 1.71 +++ UPDATING 2000/03/07 23:58:09 @@ -624,9 +624,11 @@ -------------------------------- cd /usr/src make buildworld + + reboot + cd sbin/mknod make install - [*] reboot -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 16:18:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id 3855837BCB4 for ; Tue, 7 Mar 2000 16:18:47 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip176.r7.d.bel.nwlink.com (ip176.r7.d.bel.nwlink.com [207.202.173.176]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id QAA10096; Tue, 7 Mar 2000 16:18:33 -0800 (PST) Date: Tue, 7 Mar 2000 16:13:00 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: Will Andrews Cc: FreeBSD mailing list , freebsd-current@FreeBSD.ORG Subject: Re: sshd in current....no config files in /etc/ssh In-Reply-To: <20000307171647.B64425@shadow.blackdawn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Mar 07, 2000 at 12:02:38PM +0000, FreeBSD mailing list wrote: > > You know people, it's quite sad that those with knowledge simply refuse > > to answer simple questions without "RTFM" attitudes and indirect (and > > more frequently direct) insults to intelligence and sensibilities. > > When you have more experience helping people on a frequent basis, > perhaps you will revise this statement. Try helping folks out every day > on IRC for 2 or 3 years and tell me what you think THEN. Alternative: > answer every question asked on freebsd-questions for same period. > > You'll see the point once you accomplish this. > > > There is absolutely no reason why you can't submit the help, with > > suggestion toward ones perception of "the Right Way" to do it, > > rather than beat the issue to death with superior posturing. > > There is absolutely no reason why people should lift a finger to help > somebody else when said question/inquiry has been documented somewhere > on the web or in the manpages, or someplace else. You're right. However, there is no reason to lift a finger to not help someone either. If you don't want to help, simply don't. You save everyone energy. Being a jerk isn't going to keep people from posting elementary questions, that's a fact. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 16:19:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B533937B620 for ; Tue, 7 Mar 2000 16:19:50 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115267>; Wed, 8 Mar 2000 11:20:37 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: when is 4.0 up for release ? In-reply-to: <20000307175207.C3611@industrial-strength.net>; from shun@mail.utexas.edu on Wed, Mar 08, 2000 at 10:38:23AM +1100 To: Dan Potter Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Mar8.112037est.115267@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200003072033.OAA00074@cs.rice.edu> <20000307152417.A86322@panzer.kdm.org> <20000307175207.C3611@industrial-strength.net> Date: Wed, 8 Mar 2000 11:20:36 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Mar-08 10:38:23 +1100, Dan Potter wrote: >Has anyone thought about the problem I posted a few days ago (getcwd() >breaks on unionfs in some conditions)? That seems like a pretty big >problem to me... maybe not too many people use unionfs though, I don't >know. LINT contains the comment: # NB: The NULL, PORTAL, UMAP and UNION filesystems are known to be # buggy, and WILL panic your system if you attempt to do anything with # them. They are included here as an incentive for some enterprising # soul to sit down and fix them. This suggests that there are more serious problems that need fixing. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 16:22:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta.scient.com (mta.Scient.COM [208.29.209.245]) by hub.freebsd.org (Postfix) with SMTP id 045E437BDC1 for ; Tue, 7 Mar 2000 16:22:33 -0800 (PST) (envelope-from cnielsen@scient.com) Received: (qmail 13816 invoked from network); 8 Mar 2000 00:22:26 -0000 Received: from tep01-sfo.scient.com (HELO ender.scient.com) (208.29.209.9) by mta.scient.com with SMTP; 8 Mar 2000 00:22:26 -0000 Received: (qmail 1672 invoked by uid 1001); 8 Mar 2000 00:22:53 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14533.40284.842049.518938@ender.scient.com> Date: Tue, 7 Mar 2000 16:22:52 -0800 (PST) From: Christopher Nielsen To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: Getty/Init weirdness In-Reply-To: <98237.952458176@axl.ops.uunet.co.za> References: <14532.38179.208634.408231@ender.scient.com> <98237.952458176@axl.ops.uunet.co.za> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Reply-To: cnielsen@pobox.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Another data point regarding this problem. When booting an older kernel, circa Feb 20, 2000, I don't see this behavior. -- Christopher Nielsen (enkhyl|cnielsen)@pobox.com Enkhyl on IRC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 16:22:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BAACD37C25C for ; Tue, 7 Mar 2000 16:22:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA10855; Tue, 7 Mar 2000 16:21:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: bwoods2@uswest.net Cc: Steve Kargl , freebsd-current@FreeBSD.ORG, Jay Oliver Subject: Re: sshd in current....no config files in /etc/ssh In-reply-to: Your message of "Tue, 07 Mar 2000 11:31:26 PST." Date: Tue, 07 Mar 2000 16:21:40 -0800 Message-ID: <10852.952474900@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Good god, I am saying that the files to merger dont exist....there is nothing > to merge... You need to be reading -current or stop running it. The issue with /etc/ssh/sshd_config has been discussed to death. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 16:33:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5B40F37B584 for ; Tue, 7 Mar 2000 16:33:43 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA10938; Tue, 7 Mar 2000 16:32:37 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: freebsd@mrynet.com (FreeBSD mailing list) Cc: freebsd-current@FreeBSD.ORG Subject: Re: sshd in current....no config files in /etc/ssh In-reply-to: Your message of "Tue, 07 Mar 2000 12:02:38 GMT." <200003072002.MAA09569@mrynet.com> Date: Tue, 07 Mar 2000 16:32:37 -0800 Message-ID: <10935.952475557@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You know people, it's quite sad that those with knowledge simply refuse > to answer simple questions without "RTFM" attitudes and indirect (and What you and others don't seem to understand is that there are also "minimum responsibilities" that have been established for users of our non-mainstream branches. Those minimums are published in the Handbook and other documents and have been established in order to ensure that the developers don't spend more time answering the same questions over and over in email than they do in actually writing code and improving FreeBSD in various ways. Such a thing would be bad for everyone and so a number of people, including myself, take it upon ourselves to drive the right behavior by not simply answering "needless" questions and thus encouraging the querants, in their initial success, to follow those questions up with more. One of the requirements for running -current vs one of our mainstream releases is that people read this mailing list, for example, and that's a necessary requirement because we'd otherwise have to "announce" the same issues in -current over and over again for each person to run across some transitional thing. The -current branch is NOT intended for the average Joe, it's very directly aimed at developers and developers have to deal with the idea of minimum effective requirements every day so this shouldn't come as a shock to anyone either. If it does, you're in the wrong place and should go back to a mainstream release of FreeBSD with all due haste. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 16:36:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from RedDust.BlueSky.net.au (reddust.bluesky.net.au [203.31.37.15]) by hub.freebsd.org (Postfix) with ESMTP id 88AAB37BA8C for ; Tue, 7 Mar 2000 16:36:51 -0800 (PST) (envelope-from receiver@RedDust.BlueSky.net.au) Received: from localhost (receiver@localhost) by RedDust.BlueSky.net.au (8.9.3/8.9.3) with ESMTP id KAA22578; Wed, 8 Mar 2000 10:38:04 +1000 (EST) (envelope-from receiver@RedDust.BlueSky.net.au) Date: Wed, 8 Mar 2000 10:38:04 +1000 (EST) From: Idea Receiver To: jon@cgi.norcom2000.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.4 -> 4.0 upgrade problems In-Reply-To: <20000307150718.A8510@cgi.norcom2000.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000 jon@cgi.norcom2000.com wrote: > oN tUE, mAR 07, 2000 AT 05:05:40PM +0200, Ruslan Ermilov wrote: > > On Wed, Mar 08, 2000 at 01:02:29AM +1000, Idea Receiver wrote: > > [...] > > > btw, I have problem to make release, it kept complain about that i didnt > > > set the USA_RESIDENT, however, I did! both in /etc and /etc/defaults. Can > > > please someone help me out with this as well.. > > > > > > thanks :) > > > > Set USA_RESIDENT in environment rather than in /etc. > > Or just put USA_RESIDENT=YES in /etc/make.conf This is what i did before I come to the mailing-list and ask for help :) anyway, set the USA_RESIDENT in environment helps :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 16:51:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 87E3E37B543 for ; Tue, 7 Mar 2000 16:51:17 -0800 (PST) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id C63AF1C4A; Tue, 7 Mar 2000 19:51:16 -0500 (EST) Date: Tue, 7 Mar 2000 19:51:16 -0500 From: Bill Fumerola To: Dan Potter Cc: freebsd-current@FreeBSD.ORG Subject: Re: when is 4.0 up for release ? Message-ID: <20000307195116.U25438@jade.chc-chimes.com> References: <200003072033.OAA00074@cs.rice.edu> <20000307152417.A86322@panzer.kdm.org> <20000307175207.C3611@industrial-strength.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000307175207.C3611@industrial-strength.net>; from shun@mail.utexas.edu on Tue, Mar 07, 2000 at 05:52:07PM -0600 X-Operating-System: FreeBSD 3.2-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 05:52:07PM -0600, Dan Potter wrote: > Has anyone thought about the problem I posted a few days ago (getcwd() > breaks on unionfs in some conditions)? That seems like a pretty big > problem to me... maybe not too many people use unionfs though, I don't > know. > > If someone would give me a tip about where I should look in the kernel I > would fix the problem myself but I am lost when you move past the specific > fs driver. Someone else will probably point this out to you, but: BUGS THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: billf@chc-chimes.com / billf@FreeBSD.org Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 17:13:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E270E37B50B for ; Tue, 7 Mar 2000 17:13:24 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA59438; Tue, 7 Mar 2000 17:13:19 -0800 (PST) (envelope-from dillon) Date: Tue, 7 Mar 2000 17:13:19 -0800 (PST) From: Matthew Dillon Message-Id: <200003080113.RAA59438@apollo.backplane.com> To: Peter Jeremy Cc: Dan Potter , freebsd-current@FreeBSD.ORG Subject: Re: when is 4.0 up for release ? References: <200003072033.OAA00074@cs.rice.edu> <20000307152417.A86322@panzer.kdm.org> <20000307175207.C3611@industrial-strength.net> <00Mar8.112037est.115267@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On 2000-Mar-08 10:38:23 +1100, Dan Potter wrote: :>Has anyone thought about the problem I posted a few days ago (getcwd() :>breaks on unionfs in some conditions)? That seems like a pretty big :>problem to me... maybe not too many people use unionfs though, I don't :>know. : :LINT contains the comment: :# NB: The NULL, PORTAL, UMAP and UNION filesystems are known to be :# buggy, and WILL panic your system if you attempt to do anything with :# them. They are included here as an incentive for some enterprising :# soul to sit down and fix them. : :This suggests that there are more serious problems that need fixing. : :Peter Unionfs is somewhat useable but there are indeed still some serious bugs remaining. I did a considerable amount of work on it last year that fixes the more aggregious problems, but I still can't buildworld/installworld using unionfs overlays without getting data corruption. The main problem that unionfs suffers from is that the VFS stack was not designed to support transparent overlays and unionfs has to fake out the system to make it work, especially when it comes to the VM system. I think the getcwd() problem is worthy of a send-pr, but I don't know anyone who is currently working on unionfs (and I probably will not have any time to do so this year myself). It does sounds like it ought to be relatively easy to fix considering how repeatable it is. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 17:15: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 48FAD37BE62 for ; Tue, 7 Mar 2000 17:14:57 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 3379 invoked from network); 8 Mar 2000 01:14:55 -0000 Received: from lcm161.cvzoom.net (HELO cvzoom.net) (208.230.69.161) by ns.cvzoom.net with SMTP; 8 Mar 2000 01:14:55 -0000 Message-ID: <38C5A975.957756C4@cvzoom.net> Date: Tue, 07 Mar 2000 20:14:29 -0500 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: current@freebsd.org Subject: Re: More "ld-elf.so.1: assert failed" messages References: <38BA5751.2396AE87@cvzoom.net> <200002290104.RAA60914@vashon.polstra.com> <38BB1E9C.CF44EC93@cvzoom.net> <200003060201.SAA85727@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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: .//run-mozilla.sh ./mozilla-bin MOZILLA_FIVE_HOME=/wine/dmmiller/mozilla/dist/bin LD_LIBRARY_PATH=/wine/dmmiller/mozilla/dist/bin:/usr/local/qt/lib:/usr/local/lib/rvplayer5.0:/usr/local/RealPlayerG2/Common:/usr/local/RealPlayerG2/Codecs:/usr/local/kde/lib SHLIB_PATH=/wine/dmmiller/mozilla/dist/bin LIBPATH=/wine/dmmiller/mozilla/dist/bin MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= nNCL: registering deferred (0) Gdk-WARNING **: shmget failed! Profile Manager : Profile Wizard and Manager activites : Begin Profile Manager : Command Line Options : Begin Profile Manager : Command Line Options : End ProfileManager : GetProfileDir ProfileManager : GetProfileDir Profile Manager : Profile Wizard and Manager activites : End /usr/libexec/ld-elf.so.1: Application locking error: 1 readers and 1 writers in dynamic linker. See DLLOCKINIT(3) in manual pages. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 17:52: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from rothko.bestweb.net (rothko.bestweb.net [209.94.100.160]) by hub.freebsd.org (Postfix) with ESMTP id 9FC6B37B814 for ; Tue, 7 Mar 2000 17:51:57 -0800 (PST) (envelope-from ian@whalley.org) Received: from whalley.org (dialin-1133-tnt.nyc.bestweb.net [216.179.5.117]) by rothko.bestweb.net (8.9.1a/8.9.3) with ESMTP id UAA21802; Tue, 7 Mar 2000 20:51:47 -0500 (EST) Received: (from ian@localhost) by whalley.org (8.9.3/8.9.2) id UAA31193; Tue, 7 Mar 2000 20:51:45 -0500 (EST) (envelope-from ian) Date: Tue, 7 Mar 2000 20:51:45 -0500 From: Ian Whalley To: freebsd-current@FreeBSD.ORG Cc: Warner Losh Subject: Re: Remote upgrade from 3.4-STABLE to 4.0 Message-ID: <20000307205138.A23439@cromarty.whalley.org> References: <38C5724E.84052394@whalley.org> <200003072353.QAA97662@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003072353.QAA97662@harmony.village.org>; from imp@village.org on Tue, Mar 07, 2000 at 04:53:39PM -0700 X-OS: FreeBSD/i386 4.0-CURRENT (Sat Mar 4 11:07:33 EST 2000) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Warner Losh wrote:] >:In reading UPDATING (and -current), I can't see any way to upgrade >:from 3.4-STABLE to (the future) 4.0-STABLE. >The now mythical build process for 4.0-stable cannot be >commented upon until its mythic qualities have been reduced >somewhat. In other words, UPDATING can't comment on vaporware. Heh. That's fair enough -- I will wait until 4.0 is -STABLE. Cheers; inw -- Ian Whalley @ . org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 17:57:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 2CBEC37B543 for ; Tue, 7 Mar 2000 17:57:25 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id UAA329520; Tue, 7 Mar 2000 20:56:59 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <00Mar8.112037est.115267@border.alcanet.com.au> References: <200003072033.OAA00074@cs.rice.edu> <20000307152417.A86322@panzer.kdm.org> <20000307175207.C3611@industrial-strength.net> <00Mar8.112037est.115267@border.alcanet.com.au> Date: Tue, 7 Mar 2000 20:57:17 -0500 To: Peter Jeremy , Dan Potter From: Garance A Drosihn Subject: Re: when is 4.0 up for release ? Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On 2000-Mar-08 10:38:23 +1100, Dan Potter wrote: > > Has anyone thought about the problem I posted a few days ago > >(getcwd() breaks on unionfs in some conditions)? That seems like > >a pretty big problem to me... maybe not too many people use unionfs > >though, I don't know. There are some problems. I would be extremely surprised if 4.0-release were delayed until all known problems with unionfs are worked out. No one is against the idea of having them fixed, but as a practical matter the problems would take enough time to find, fix, and prove out that 4.0 should not be delayed that long. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 17:59: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 19E1E37C001 for ; Tue, 7 Mar 2000 17:59:06 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA27543; Tue, 7 Mar 2000 17:58:56 -0800 (PST) (envelope-from Doug@gorean.org) Date: Tue, 7 Mar 2000 17:58:56 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: "Matthew N. Dodd" Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Matthew N. Dodd wrote: > On Tue, 7 Mar 2000, Doug Barton wrote: > > > If you give us an idea where your breakage is, we can tell you if it's > > a known problem. E.g., there is a known problem with PPP(D) and > > NO_OPENSSL that Kris and I have already worked out a fix for. > > Yep, thats one of them. We'll see if I find anything else. Ok, if you don't need PPP just delete that from /usr/src/usr.sbin/Makefile (there are 4 lines). If you do need PPP write back and I'll send you the patch, I don't have the info handy right this second. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 18:14:19 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 00F0537BB31; Tue, 7 Mar 2000 18:14:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B606B2E815B; Tue, 7 Mar 2000 18:14:17 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 7 Mar 2000 18:14:17 -0800 (PST) From: Kris Kennaway To: Richard J Kuhns Cc: freebsd-current@FreeBSD.ORG Subject: Re: YA ssh question (ssh-askpass?) In-Reply-To: <14533.29753.499155.780744@localhost.grauel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 18:19: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1A12E37B549; Tue, 7 Mar 2000 18:19:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 181C32E815B; Tue, 7 Mar 2000 18:19:05 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 7 Mar 2000 18:19:05 -0800 (PST) From: Kris Kennaway To: Warner Losh Cc: Ruslan Ermilov , current@FreeBSD.ORG Subject: Re: 3.4 -> 4.0 upgrade problems In-Reply-To: <200003080001.RAA97744@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Warner Losh wrote: > In message <20000307115632.A72634@relay.ucb.crimea.ua> Ruslan Ermilov writes: > : > 1) genassym and config were complaining about not being able to find > : > libc.so.4 when I installed them. Workaround: go back and rebuild with with > : > CFLAGS="-static" > > A better work around is cd lib/libc and do a make install. I'm pretty sure I tried that - I can't remember if it screwed me up (signal 12 errors) or just didn't work. > : We certainly need to update src/UPDATING accordingly, see the patch > : attached. > > : + make buildkernel installkernel KERNEL="NAME_OF_YOUR_KERNEL" > > I'm not sure that this is wise. When I tried this, I got > /NAME_OF_YOUR_KERNEL rather than /kernel like I'd have expected. Sounds like a bug. However, IMO people should be building GENERIC as their first 4.0 kernel, because all the config file changes mean they won't be able to just use their old one, and chances are they might screw up and miss out something important and then blame it on 4.0 instead of their own ignorance. If we get them booting with GENERIC and prove they can (which is what the buildkernel target does by default), then it's more obviously user error when the next kernel they build doesn't work (plus, they have a working 4.0 kernel to fall back on, namely kernel.old :-) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 18:21:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from renoa.home.allusion.net (cs2727-11.austin.rr.com [24.27.27.11]) by hub.freebsd.org (Postfix) with ESMTP id 469C537B5FD for ; Tue, 7 Mar 2000 18:21:34 -0800 (PST) (envelope-from bard@renoa.home.allusion.net) Received: by renoa.home.allusion.net via sendmail from stdin id (Debian Smail3.2.0.102) for freebsd-current@freebsd.org; Tue, 7 Mar 2000 20:36:29 -0600 (CST) Message-ID: <20000307203629.B4266@industrial-strength.net> Date: Tue, 7 Mar 2000 20:36:29 -0600 From: Dan Potter To: freebsd-current@freebsd.org Subject: Unionfs fixes (was: when is 4.0 up for release ?) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mutt 0.91.1i-jp1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recall waay back on Mar 07 when Bill Fumerola wrote: > Someone else will probably point this out to you, but: > > BUGS > THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK) > AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN > RISK. BEWARE OF DOG. SLIPPERY WHEN WET. Yes, I understand... Rome was not built in a day though, we have to fix it one bug at a time if it's going to get fixed. ^_^; I guess not as many people use it as I thought, though. Also, the reason I posted my concerns is that this is the -current list and I figured if anywhere, this might be the place. It seems like half the fs' man pages have that disclaimer at the bottom =) I guess my next question is: is there a better list to take the discussion of fixing up unionfs (e.g., hackers? fs?), and is there any decent amount of information somewhere that I could use to get up to speed on VFS in FreeBSD and such? The functionality would be very useful at work, and so far it seems to be working fine minus a few hiccups. Because of that, it's somewhat likely that I could spend time getting paid to work on it =). So I guess if there's anyone who's interested in cleaning up after the dog at the moment (see above disclaimer from the man page =) it'd probably be me. Specifically I'd like to see the operation cleaned up if possible so that it's more truly transparent -- like no shadow directories, special files (e.g., device nodes) working, etc; if I can get my brain around it I might be able to work on some of that. I've studied the VFS model in Linux a bit, and BSD's seems somewhat similar, at least at first glance. It doesn't look too hard. Famous last words I guess... =) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 18:36:51 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 048BA37B5D6; Tue, 7 Mar 2000 18:36:50 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0299C2E815B; Tue, 7 Mar 2000 18:36:50 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 7 Mar 2000 18:36:49 -0800 (PST) From: Kris Kennaway To: Doug Barton Cc: "Matthew N. Dodd" , "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Doug Barton wrote: > If you give us an idea where your breakage is, we can tell you if > it's a known problem. E.g., there is a known problem with PPP(D) and > NO_OPENSSL that Kris and I have already worked out a fix for. I'm still waiting for Jordan's approval on that patch :-) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 18:53:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 25E1F37B5FD for ; Tue, 7 Mar 2000 18:53:50 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id DAA97113; Wed, 8 Mar 2000 03:53:48 +0100 (CET) (envelope-from olli) Date: Wed, 8 Mar 2000 03:53:48 +0100 (CET) Message-Id: <200003080253.DAA97113@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... X-Newsgroups: list.freebsd-current In-Reply-To: <8a447c$cfc$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote in list.freebsd-current: > I avoid the problem by structuring my paths along the lines of > $HOME/bin:/usr/local/bin:/usr/bin:/bin (everythere, not just on > FreeBSD). OK, I'll think I will do that (even though I didn't need it, until the /usr/bin/ssh problems appeared). However, this doesn't solve the problem completely. I also had to remove /etc/ssh. Somehow, /usr/local/bin/scp seems to pick up data from /etc/ssh and tries to invoke /usr/bin/ssh, no matter what. :-( I'm truly sorry I caused this lengthy thread. It was really not my intention to spread FUD. I stumbled over something that (I thought) could be a potential problem for 4.0-Release (and I still think so). I will re-install that machine from scratch and write down exactly what is going wrong. Maybe it has even been solved in the latest -current snapshot. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 20:10:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 1982937B6DD for ; Tue, 7 Mar 2000 20:10:30 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115221>; Wed, 8 Mar 2000 15:11:20 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: ssh strangeness in -current... In-reply-to: <200003080253.DAA97113@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Wed, Mar 08, 2000 at 01:55:45PM +1100 To: freebsd-current@FreeBSD.ORG Message-Id: <00Mar8.151120est.115221@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <8a447c$cfc$1@atlantis.rz.tu-clausthal.de> <200003080253.DAA97113@dorifer.heim3.tu-clausthal.de> Date: Wed, 8 Mar 2000 15:11:20 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Mar-08 13:55:45 +1100, Oliver Fromme wrote: > I also had to remove >/etc/ssh. Somehow, /usr/local/bin/scp seems to pick up data >from /etc/ssh and tries to invoke /usr/bin/ssh, no matter >what. :-( I can't explain that. My installed-from-ports scp exec's /usr/local/bin/ssh1 and that ssh doesn't know anything about /etc/ssh. Try running "ktrace -i" on the scp and looking at what is actually exec'd and opened. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 21: 1:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from RedDust.BlueSky.net.au (reddust.bluesky.net.au [203.31.37.15]) by hub.freebsd.org (Postfix) with ESMTP id 97B2D37B517 for ; Tue, 7 Mar 2000 21:01:28 -0800 (PST) (envelope-from receiver@RedDust.BlueSky.net.au) Received: from localhost (receiver@localhost) by RedDust.BlueSky.net.au (8.9.3/8.9.3) with ESMTP id PAA22922 for ; Wed, 8 Mar 2000 15:02:44 +1000 (EST) (envelope-from receiver@RedDust.BlueSky.net.au) Date: Wed, 8 Mar 2000 15:02:44 +1000 (EST) From: Idea Receiver To: current@freebsd.org Subject: problem of make release. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I was tring to make release (just for interests) yesterday. Which I receive an error "ln: /R/stage/kernels/GENERIC: No such file or directory" in release.3. I go back to check Makefile, I see "_R" been defined as "/R". Which looks doesnt make any sence, I do not believe the / would be touched. is this an bug or just i did something wrong? thx ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 21:25:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 8B3D637B53F for ; Tue, 7 Mar 2000 21:25:41 -0800 (PST) (envelope-from DougB@simplenet.com) Received: from simplenet.com (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA28553; Tue, 7 Mar 2000 21:25:37 -0800 (PST) (envelope-from DougB@simplenet.com) Message-ID: <38C5E450.3B4E9A78@simplenet.com> Date: Tue, 07 Mar 2000 21:25:37 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-CURRENT-0302 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matt Heckaman Cc: freebsd-current@FreeBSD.ORG Subject: Re: sshd in current....no config files in /etc/ssh References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Heckaman wrote: > Despite the name, mergemaster is not only for merging, it's about the most > handy tool I've ever come across for make worlds, makes updating configs a > very easy task indeed. Doug definately deserves a few hundred pats on the > back for that program. Well, kind words are always appreciated... of course money is the universal language of appreciation... *chuckle* Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 21:29:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 11F8337B53F for ; Tue, 7 Mar 2000 21:29:41 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id WAA19050; Tue, 7 Mar 2000 22:01:09 -0800 (PST) Date: Tue, 7 Mar 2000 22:01:09 -0800 From: Alfred Perlstein To: Idea Receiver Cc: current@FreeBSD.ORG Subject: Re: problem of make release. Message-ID: <20000307220109.V14279@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from receiver@RedDust.BlueSky.net.au on Wed, Mar 08, 2000 at 03:02:44PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Idea Receiver [000307 21:33] wrote: > > hi, > > I was tring to make release (just for interests) yesterday. Which > I receive an error "ln: /R/stage/kernels/GENERIC: No such file or > directory" in release.3. I go back to check Makefile, I see "_R" > been defined as "/R". Which looks doesnt make any sence, I do not > believe the / would be touched. > > is this an bug or just i did something wrong? > > thx ;) you want to make /R a symlink to a place with a helluva lot of free space. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 22: 1:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3752737B521 for ; Tue, 7 Mar 2000 22:01:33 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id WAA78795; Tue, 7 Mar 2000 22:00:59 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id WAA60836; Tue, 7 Mar 2000 22:01:09 -0800 (PST) (envelope-from obrien) Date: Tue, 7 Mar 2000 22:01:09 -0800 From: "David O'Brien" To: bwoods2@uswest.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: sshd in current....no config files in /etc/ssh Message-ID: <20000307220109.B60604@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200003071926.LAA75252@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from wwoods@cybcon.com on Tue, Mar 07, 2000 at 11:31:26AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 11:31:26AM -0800, William Woods wrote: > Good god, I am saying that the files to merger dont exist....there is nothing > to merge... .... > > If you insist on doing it by hand, start with > > "diff -urN /etc /usr/src/etc" Perhaps you are not familar with the "-N" option to diff. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 22:19:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E425937B59E; Tue, 7 Mar 2000 22:19:36 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA61856; Tue, 7 Mar 2000 23:19:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA99365; Tue, 7 Mar 2000 23:19:20 -0700 (MST) Message-Id: <200003080619.XAA99365@harmony.village.org> To: Kris Kennaway Subject: Re: 3.4 -> 4.0 upgrade problems Cc: Ruslan Ermilov , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 07 Mar 2000 18:19:05 PST." References: Date: Tue, 07 Mar 2000 23:19:20 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : On Tue, 7 Mar 2000, Warner Losh wrote: : > A better work around is cd lib/libc and do a make install. : : I'm pretty sure I tried that - I can't remember if it screwed me up : (signal 12 errors) or just didn't work. Odd. I actually tried it myself not to long ago and it worked great. : Sounds like a bug. However, IMO people should be building GENERIC as their : first 4.0 kernel, because all the config file changes mean they won't be : able to just use their old one, and chances are they might screw up and : miss out something important and then blame it on 4.0 instead of their own : ignorance. If we get them booting with GENERIC and prove they can (which : is what the buildkernel target does by default), then it's more obviously : user error when the next kernel they build doesn't work (plus, they : have a working 4.0 kernel to fall back on, namely kernel.old :-) Hmmm, I'll have to think about this... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 22:20: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 38D9337C1ED; Tue, 7 Mar 2000 22:19:55 -0800 (PST) (envelope-from DougB@simplenet.com) Received: from simplenet.com (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id WAA28612; Tue, 7 Mar 2000 22:19:53 -0800 (PST) (envelope-from DougB@simplenet.com) Message-ID: <38C5F109.476539B0@simplenet.com> Date: Tue, 07 Mar 2000 22:19:53 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-CURRENT-0302 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nik Clayton Cc: Brooks Davis , current@freebsd.org, Ian Whalley Subject: Re: Alternative way to do -stable to -current upgrade References: <20000305202435.A39101@catkin.nothing-going-on.org> <20000307110109.A52023@catkin.nothing-going-on.org> <20000307101957.A5565@orion.ac.hmc.edu> <20000307191442.B19024@catkin.nothing-going-on.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nik Clayton wrote: > That, at least, was not the case with an upgrade I attempted a few days > ago. On booting with kernel.GENERIC (from -current) it hung mounting the > disks. Trying to go back to kernel.stable didn't work, because I'd had > to update the /dev entries for -current, and they wouldn't work with > -stable. I had to dig out fixit floppies and restore from a backup. > > Ordinarily, you'd make sure that userland, /dev, and the kernel are all > in sync before you reboot. However, in this case (and as advised by > src/UPDATING) you have to reboot with a new kernel after updating /dev, > but before you update the userland. I've been meaning to post this for a while. I recently upgraded two way old 4.0 systems to post-signal changes -current. It's not quite a 3.x -> 4.0-Current upgrade, but it's close. I had to do a few things differently than what's in Updating, and I wanted to test the feasability of not going single user mode since I keep remote upgrades in the back of my mind even though I don't do a lot of them anymore. This is assuming that you've done all the right things with upgrading sources, double-checked /etc/make.conf, using clean /usr/src, clean /usr/obj, etc. 1. make buildworld 2. make buildkernel I actually updated my kernel config file while world was building so I did 'make KERNEL=MYKERNELFILE buildkernel, and below, but that's not for the faint of heart. As someone already pointed out, GENERIC is a better choice, and doesn't require any options. 3. make installkernel 4. cd /usr/src/sbin/mknod && make install I had to do this or the next step didn't work. 5. cp /usr/src/etc/MAKEFILE /dev ; cd /dev ; /bin/sh MAKEFILE all 6. Update /etc/fstab and new disk devices per instructions in Updating 7. reboot 8. make -k installworld 9. make installworld 10. mergemaster 11. rebuilt my kernel (make sure to update your kernel config file) and rebooted I did one system this way feeling my way through, then did another following these instructions and didn't have any problems. I never had to go single user, although these were workstation machines. For servers you'd probably want to use /var/run/nologin, or similar. (Just make sure you open plenty of shells for yourself first. :) I hope this is useful, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 22:51:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 4F42337B5BB; Tue, 7 Mar 2000 22:51:15 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id WAA78606; Tue, 7 Mar 2000 22:52:28 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200003080652.WAA78606@troutmask.apl.washington.edu> Subject: Re: sshd in current....no config files in /etc/ssh In-Reply-To: <20000307220109.B60604@dragon.nuxi.com> from "David O'Brien" at "Mar 7, 2000 10:01:09 pm" To: obrien@FreeBSD.ORG Date: Tue, 7 Mar 2000 22:52:28 -0800 (PST) Cc: bwoods2@uswest.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > On Tue, Mar 07, 2000 at 11:31:26AM -0800, William Woods wrote: > > Good god, I am saying that the files to merger dont exist....there is nothing > > to merge... > .... > > > If you insist on doing it by hand, start with > > > "diff -urN /etc /usr/src/etc" > > > Perhaps you are not familar with the "-N" option to diff. > Who is the "you" you're refer to? I'm quite familiar with the -N option, and if you want to compare /etc with /usr/src/etc -N is handy. If you're intimating that -N implies -r that is not contained in diff(1). -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 7 22:51:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from oxygen.yy.ics.keio.ac.jp (oxygen.yy.ics.keio.ac.jp [131.113.47.3]) by hub.freebsd.org (Postfix) with ESMTP id 69E5437B54D for ; Tue, 7 Mar 2000 22:51:46 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (lavender.rad.cc.keio.ac.jp [131.113.16.115]) by oxygen.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id PAA29906 for ; Wed, 8 Mar 2000 15:51:44 +0900 (JST) (envelope-from sanpei@sanpei.org) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id PAA52108; Wed, 8 Mar 2000 15:51:44 +0900 (JST) Date: Wed, 8 Mar 2000 15:51:44 +0900 (JST) Message-Id: <200003080651.PAA52108@lavender.yy.cs.keio.ac.jp> To: freebsd-current@FreeBSD.ORG Subject: libXThrStub.so.6.0 was missing in Xbin.tgz, in current.FreeBSD.org {Re: 4.0-20000222-CURRENT installation report} In-Reply-To: Your message of "Wed, 1 Mar 2000 14:00:16 JST". <20000301180016.C886@cs.waikato.ac.nz> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG joerg@cs.waikato.ac.nz wrote: >> X11R6 will not install as fetched with -current, libXThrStub.so.6 is >> missing. When compiling X11R6 from ports, everything works fine. I installed 4-current from current.FreeBSD.org, I also have above problem. Xbin.tgz only has aout libXThrStub.so.6 binary :-< % tar tzvf Xbin.tgz |grep libXThrStub -rw-r--r-- root/wheel 9043 Feb 22 14:37 2000 lib/aout/libXThrStub.so.6.0 MD5 (Xbin.tgz) = d7441882957dc7724d2d909f34fcd0f4 Does someone update Xbin.tgz in current.FreeBSD.org? ftp://current.FreeBSD.org/pub/FreeBSD/current/XF86336/Xbin.tgz ftp://current.FreeBSD.org/pub/FreeBSD/current/XF86336/FILES By the way, Xbin.tgz in ISO-IMAGES/4.0-20000214-CURRENT was solved this problem. I think we replace Xbin.tgz from ISO-IMAGES into current.FreeBSD.org. Thank you MIHIRA Yoshiro Yokohama, Japan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 0: 0:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8027C37BBD5 for ; Wed, 8 Mar 2000 00:00:53 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA79232; Wed, 8 Mar 2000 00:00:53 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA70488; Wed, 8 Mar 2000 00:01:03 -0800 (PST) (envelope-from obrien) Date: Wed, 8 Mar 2000 00:01:02 -0800 From: "David O'Brien" To: Steve Kargl Cc: freebsd-current@FreeBSD.ORG Subject: Re: sshd in current....no config files in /etc/ssh Message-ID: <20000308000102.C60604@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000307220109.B60604@dragon.nuxi.com> <200003080652.WAA78606@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003080652.WAA78606@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Tue, Mar 07, 2000 at 10:52:28PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 07, 2000 at 10:52:28PM -0800, Steve Kargl wrote: > > Who is the "you" you're refer to? I'm quite familiar with Generally when one says 'who' it refers to the person the in "To:" header. Which was not you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 0: 4:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 63B4637BA70 for ; Wed, 8 Mar 2000 00:04:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA79251; Wed, 8 Mar 2000 00:04:13 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA70505; Wed, 8 Mar 2000 00:04:12 -0800 (PST) (envelope-from obrien) Date: Wed, 8 Mar 2000 00:04:12 -0800 From: "David O'Brien" To: Idea Receiver Cc: current@freebsd.org Subject: Re: problem of make release. Message-ID: <20000308000412.D60604@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from receiver@RedDust.BlueSky.net.au on Wed, Mar 08, 2000 at 03:02:44PM +1000 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was tring to make release (just for interests) yesterday. Which > I receive an error "ln: /R/stage/kernels/GENERIC: No such file or > directory" in release.3. I go back to check Makefile, I see "_R" > been defined as "/R". Which looks doesnt make any sence, I do not > believe the / would be touched. _R is relative to the value you used for ${CHROOTDIR}. The message you got above, probably happened after the ``chroot ${CHROOTDIR}'' and thus is not your real / . -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 0: 7: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id EF37037BA70 for ; Wed, 8 Mar 2000 00:06:58 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 19327 invoked from network); 8 Mar 2000 08:06:55 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 8 Mar 2000 08:06:55 -0000 Date: Wed, 8 Mar 2000 19:06:45 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Dan Potter Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems with 'pwd' and unionfs In-Reply-To: <20000304215058.A7124@industrial-strength.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 4 Mar 2000, Dan Potter wrote: > ... > In libc there is a non-kernel version of getcwd that runs lstat() on each > directory and then searching its parent, trying to divine which sub-tree > is '.' at the time. I dumped a copy of that into a copy of pwd.c to trace > through it and see what happens. Basically for optimization purposes it > looks like it just uses the inode value from readdir() until it thinks > that it's changed volumes, and then it runs lstat() on each entry to make This is supposed to work. (st_dev, st_ino) pairs returned by lstat() and stat() are supposed to be unique. > sure which one it is. Well, this breaks unionfs mounts because the device > inode is the same, but the inode numbers are different since it's a mount > point. What a subtle problem! st_dev for a mount on non-device is normally copied from the fsid for the mount. See kern/vfs_vnops.c:vn_stat(). This works for nfs mounts. Unfortunately, for union mounts, VOP_GETTATTR() normally finds a non-VNOVAL va_fsid by going to the leaf filesystem, and st_dev is set to this. I think the fsid should be used in all cases (change f_fsid.val[0] for mounts on real devices if necessary). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 2:28:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by hub.freebsd.org (Postfix) with ESMTP id BF25337B57F for ; Wed, 8 Mar 2000 02:28:44 -0800 (PST) (envelope-from Alex.Challis@nokia.com) Received: from mgw-i1.ntc.nokia.com (mgw-i1.ntc.nokia.com [131.228.118.60]) by mgw-x2.nokia.com (8.9.3/8.9.3/o) with ESMTP id MAA26978 for ; Wed, 8 Mar 2000 12:28:36 +0200 (EET) From: Alex.Challis@nokia.com Received: from esebh03nok.ntc.nokia.com (esebh03nok.ntc.nokia.com [131.228.118.244]) by mgw-i1.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id MAA19822 for ; Wed, 8 Mar 2000 12:28:32 +0200 (EET) Received: by esebh03nok with Internet Mail Service (5.5.2650.10) id ; Wed, 8 Mar 2000 12:28:31 +0200 Message-ID: <20173FD03122D311B3C60008C7D9B29F8D7E05@caeis03nok> To: freebsd-current@FreeBSD.org Subject: Date: Wed, 8 Mar 2000 12:28:28 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.10) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 2:37:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from KIRA.TEAM400.IE (kira.team400.ie [193.120.161.242]) by hub.freebsd.org (Postfix) with ESMTP id 7326237B5F5; Wed, 8 Mar 2000 02:37:39 -0800 (PST) (envelope-from niall@pobox.com) Received: from trinityexch.team400.ie ("port 4892"@[193.120.161.222]) by kira.team400.ie (PMDF V5.2-32 #42663) with ESMTP id <01JMSCPZYU1G004L9G@kira.team400.ie>; Wed, 8 Mar 2000 10:38:39 BST Received: from pobox.com (193.120.161.91 [193.120.161.91]) by trinityexch.team400.ie with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id GMSTD4W1; Wed, 08 Mar 2000 10:32:35 +0000 Date: Wed, 08 Mar 2000 10:40:58 +0000 From: Niall Smart Subject: rtld breakage still in -stable, or is it me? To: current@freebsd.org Cc: hackers@freebsd.org Message-id: <38C62E3A.A3075967@pobox.com> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi A few days ago I upgraded by system to -stable from 3.2-RELEASE and several programs which use dlopen stopped working, most notably mod_perl. For example: # apachectl start [Wed Mar 8 10:19:35 2000] [error] Can't load '/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Time/HiRes/HiRes.so' for module Time::HiRes: /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Time/HiRes/HiRes.so: Undefined symbol "PL_stack_max" at /usr/libdata/perl/5.00503/DynaLoader.pm line 169. at /usr/local/lib/perl5/site_perl/5.005/HTML/Mason/Interp.pm line 25 BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.005/HTML/Mason.pm line 9. BEGIN failed--compilation aborted at /usr/local/web/mason/handler.pl line 3. Syntax error on line 1204 of /usr/local/apache-1.3/conf/httpd.conf: Can't load '/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Time/HiRes/HiRes.so' for module Time::HiRes: /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Time/HiRes/HiRes.so: Undefined symbol "PL_stack_max" at /usr/libdata/perl/5.00503/DynaLoader.pm line 169. at /usr/local/lib/perl5/site_perl/5.005/HTML/Mason/Interp.pm line 25 BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.005/HTML/Mason.pm line 9. BEGIN failed--compilation aborted at /usr/local/web/mason/handler.pl line 3. /usr/local/apache-1.3/bin/apachectl start: httpd could not be started Furthermore: niall% nm /usr/lib/libperl.so | grep PL_stack_max 00090630 B PL_stack_max The Time::HiRes module loads fine when I invoke perl from the command line. It appears I amn't the only one having this problem: http://x42.deja.com/getdoc.xp?AN=582680524 http://x30.deja.com/getdoc.xp?AN=591070824 http://x31.deja.com/getdoc.xp?AN=573655265 http://x31.deja.com/getdoc.xp?AN=565253105 A recompile of apache etc did not solve the problem, neither did a make world yesterday Any hints? Regards, Niall -- Niall Smart email: niall.smart@ebeon.com phone: (087) 8052390 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 3: 3:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 4123437B569 for ; Wed, 8 Mar 2000 03:03:37 -0800 (PST) (envelope-from brameld@twave.net) Received: from [12.21.241.81] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id qa032282 for ; Wed, 8 Mar 2000 06:03:31 -0500 Received: from Bozo_3.BozoLand.domain (localhost [127.0.0.1]) by Bozo_3.BozoLand.domain (8.9.3/8.9.3) with SMTP id XAA09304 for ; Tue, 7 Mar 2000 23:21:31 -0500 (EST) (envelope-from brameld@twave.net) From: Walter Brameld To: freebsd-current@Freebsd.org Subject: Parallel port Zip drive Date: Tue, 7 Mar 2000 23:11:47 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00030723213100.08909@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 vpo0: on ppbus0 imm0: EPP 1.9 mode sbc0: 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: on sbc0 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x620-0x623 on isa0 ad0: 17206MB [34960/16/63] at ata0-master using UDMA33 ad1: 8693MB [17662/16/63] at ata0-slave using UDMA33 acd0: CDROM 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 3: 4: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 5040B37BFBE for ; Wed, 8 Mar 2000 03:03:59 -0800 (PST) (envelope-from brameld@twave.net) Received: from [12.21.241.81] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id wa032288 for ; Wed, 8 Mar 2000 06:03:37 -0500 Received: from Bozo_3.BozoLand.domain (localhost.BozoLand.domain [127.0.0.1]) by Bozo_3.BozoLand.domain (8.9.3/8.9.3) with SMTP id GAA00799; Tue, 7 Mar 2000 06:26:14 -0500 (EST) (envelope-from brameld@twave.net) From: Walter Brameld To: Kris Kennaway , R Joseph Wright Subject: Re: no openssh after build Date: Tue, 7 Mar 2000 06:25:29 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-current@Freebsd.org References: In-Reply-To: MIME-Version: 1.0 Message-Id: <00030706261400.00767@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 3: 4:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 31A1537C025 for ; Wed, 8 Mar 2000 03:04:09 -0800 (PST) (envelope-from brameld@twave.net) Received: from [12.21.241.81] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id sa032284 for ; Wed, 8 Mar 2000 06:03:35 -0500 Received: from Bozo_3.BozoLand.domain (localhost.BozoLand.domain [127.0.0.1]) by Bozo_3.BozoLand.domain (8.9.3/8.9.3) with SMTP id GAA00811; Tue, 7 Mar 2000 06:31:07 -0500 (EST) (envelope-from brameld@twave.net) From: Walter Brameld To: Kris Kennaway , R Joseph Wright Subject: Re: no openssh after build Date: Tue, 7 Mar 2000 06:30:41 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-current@Freebsd.org References: <00030706261400.00767@Bozo_3.BozoLand.domain> In-Reply-To: <00030706261400.00767@Bozo_3.BozoLand.domain> MIME-Version: 1.0 Message-Id: <00030706310702.00767@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 3:13:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 2D76137B590 for ; Wed, 8 Mar 2000 03:13:52 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 1A23E1221D; Wed, 8 Mar 2000 12:13:45 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000307212933.G73925@nathan.ruhr.de> References: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> <0v3dq2py9q.fsf@cs.uni-magdeburg.de> <20000307212933.G73925@nathan.ruhr.de> Date: Wed, 8 Mar 2000 11:51:05 +0100 To: Udo Erdelhoff From: Brad Knowles Subject: Re: ssh strangeness in -current... Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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, 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 for details. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 3:28:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.originative.co.uk (mailgate.originative.co.uk [194.217.50.228]) by hub.freebsd.org (Postfix) with ESMTP id E93B337B590 for ; Wed, 8 Mar 2000 03:28:22 -0800 (PST) (envelope-from paul@originative.co.uk) Received: from originative.co.uk (lobster.originative.co.uk [194.217.50.241]) by mail.originative.co.uk (Postfix) with ESMTP id A251C1D131; Wed, 8 Mar 2000 11:28:21 +0000 (GMT) Message-ID: <38C63963.AA114CF8@originative.co.uk> Date: Wed, 08 Mar 2000 11:28:35 +0000 From: Paul Richards Organization: Originative Solutions Ltd X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en-GB, en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Oliver Fromme , freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... References: <91661.952450792@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > I have upgraded a machine to the latest -current snapshot (it > > was running a -current from the end of January before). Every- > > thing went fine, except for one thing: ssh didn't work anymore. > > It used to work fine before. > > You really need to read the -current mailing list if you're going to > run -current. Saying that openssh took you by surprise as a -current > user is sort of like saying you didn't know Elvis was dead. :-( but he isn't! He was working in a chip shop last I heard. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 3:28:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 6FC1037BA24 for ; Wed, 8 Mar 2000 03:28:27 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by jfh00.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id MAA00432; Wed, 8 Mar 2000 12:28:24 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <38C63957.CF484F5C@fernuni-hagen.de> Date: Wed, 08 Mar 2000 12:28:23 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: de-DE, German/Germany, en MIME-Version: 1.0 Cc: freebsd-current@FreeBSD.ORG Subject: Re: Parallel port Zip drive References: <00030723213100.08909@Bozo_3.BozoLand.domain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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:fritz.heinrichmeyer@fernuni-hagen.de 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 3:39:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id DE20A37B5FA for ; Wed, 8 Mar 2000 03:39:51 -0800 (PST) (envelope-from brameld@twave.net) Received: from [12.21.241.81] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id ma032616 for ; Wed, 8 Mar 2000 06:39:42 -0500 Received: from Bozo_3.BozoLand.domain (localhost [127.0.0.1]) by Bozo_3.BozoLand.domain (8.9.3/8.9.3) with SMTP id GAA00657; Wed, 8 Mar 2000 06:39:40 -0500 (EST) (envelope-from brameld@twave.net) From: Walter Brameld To: "F. Heinrichmeyer" Subject: Re: Parallel port Zip drive Date: Wed, 8 Mar 2000 06:38:45 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-current@FreeBSD.ORG References: <00030723213100.08909@Bozo_3.BozoLand.domain> <38C63957.CF484F5C@fernuni-hagen.de> In-Reply-To: <38C63957.CF484F5C@fernuni-hagen.de> MIME-Version: 1.0 Message-Id: <00030806394001.00611@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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:fritz.heinrichmeyer@fernuni-hagen.de > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 3:44:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcat.heimat.gr.jp (pcat.heimat.gr.jp [211.0.53.98]) by hub.freebsd.org (Postfix) with ESMTP id 61BFF37C00E for ; Wed, 8 Mar 2000 03:44:22 -0800 (PST) (envelope-from nakaji@tutrp.tut.ac.jp) Received: from xa12.heimat.gr.jp (xa12.heimat.gr.jp [211.0.53.97]) by pcat.heimat.gr.jp (8.9.3/3.7W) with ESMTP id UAA16038; Wed, 8 Mar 2000 20:43:33 +0900 (JST) To: "Sean O'Connell" Cc: current@freebsd.org Subject: Re: XDM login using sessreg and last, uptime, w and so on... References: <86g0u2vpz3.fsf@xa12.heimat.gr.jp> <86zosaxvzn.fsf@xa12.heimat.gr.jp> <20000307235759.A3636@stat.Duke.EDU> MIME-Version: 1.0 (generated by REMI 1.14.1 - =?ISO-8859-4?Q?=22Mushigawa=F2?= =?ISO-8859-4?Q?sugi=22?=) Content-Type: text/plain; charset=US-ASCII From: NAKAJI Hiroyuki Date: 08 Mar 2000 20:43:23 +0900 In-Reply-To: <20000307235759.A3636@stat.Duke.EDU> (Sean O'Connell's message of "Tue, 7 Mar 2000 23:57:59 -0500") Message-ID: <86r9dloffo.fsf@xa12.heimat.gr.jp> Lines: 63 User-Agent: T-gnus/6.14.1 (based on Gnus v5.8.3) (revision 12) REMI/1.14.1 (=?ISO-8859-4?Q?Mushigawa=F2sugi?=) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.5 (i386--freebsd) MULE/4.0 (HANANOEN) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you for your suggestion, Sean. I faced this kind of problem both on FreeBSD and FreeBSD(98) because I mis-upgraded to current system. Anyway I tried your suggestion for both. On FreeBSD it was successful and there seems no problem. On FreeBSD(98) there is still a '/dev/:0 problem'. I'll answer about pc98. >>>>> In <20000307235759.A3636@stat.Duke.EDU> >>>>> "Sean O'Connell" wrote: S> Do you have something odd in /usr/X11R6/lib/X11/xdm/Xservers? No. Xservers has only one line. :0 local /usr/X11R6/bin/X -once -bpp 16 -deferglyphs all S> Did you completely remove and recreate /dev ... could there be S> an old socket kicking around (/var/run)? What about under S> /tmp/.X11-unix ? I recreated /dev/* with newer MAKEDEV script (1.242). /tmp is mounted by mfs. S> Also, you may have some old pollution kicking around (like versions S> of chown and chmod in the wrong places ... see /usr/src/UPDATING) S> from 3.X days. Just removed old chown and chgrp. S> Lastly, did you copy /dev/null over /var/run/utmp and /var/log/wtmp S> ... you could be bitten by a formatting change. Are your shells S> completely rebuilt? What about ssh? or some form xterm replacement? I executed cp /dev/null /var/run/utmp cp /dev/null /var/log/wtmp and others(bash2, ssh, kterm and fvwm2) are also rebuilt. Ssh is openssh in the src tree. Then, nakaji@xa12:nakaji$ w w: /dev/:0: No such file or directory 8:31PM up 12 mins, 1 user, load averages: 1.15, 0.59, 0.24 USER TTY FROM LOGIN@ IDLE WHAT nakaji p1 :0.0 8:31PM - w nakaji@xa12:nakaji$ finger finger: /dev//:0: No such file or directory Login Name TTY Idle Login Time Office Phone nakaji NAKAJI Hiroyuki p1 Wed 20:31 nakaji NAKAJI Hiroyuki *:0 Wed 20:20 There is still 'No such file or directory'. :( S> Rapidly running out of ideas, good luck I'll recheck the steps for upgrading my system. Thanks. -- NAKAJI Hiroyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 3:55: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 8945F37B569 for ; Wed, 8 Mar 2000 03:55:05 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.3/8.9.3) id MAA00456; Wed, 8 Mar 2000 12:55:01 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) X-Authentication-Warning: jfh00.fernuni-hagen.de: jfh set sender to fritz.heinrichmeyer@fernuni-hagen.de using -f To: Walter Brameld Cc: "F. Heinrichmeyer" , freebsd-current@FreeBSD.ORG Subject: Parallel port Zip drive and other old crappy hardware References: <00030723213100.08909@Bozo_3.BozoLand.domain> <38C63957.CF484F5C@fernuni-hagen.de> <00030806394001.00611@Bozo_3.BozoLand.domain> From: Fritz Heinrichmeyer Date: 08 Mar 2000 12:55:01 +0100 In-Reply-To: Walter Brameld's message of "Wed, 8 Mar 2000 06:38:45 -0500" Message-ID: Lines: 10 User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.2 (Hestia) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD-4.0 will kick out some older/cheaper hardware. My CMI8330 on board sound chip at home needs patching of mss.c and sbc.c to work. Overall performance is now very good on the other side. -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 4:11: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from moran.grauel.com (usr1-44.mintel.net [63.81.123.59]) by hub.freebsd.org (Postfix) with ESMTP id 236E537C29E; Wed, 8 Mar 2000 04:11:03 -0800 (PST) (envelope-from rjk@moran.grauel.com) Received: (from rjk@localhost) by moran.grauel.com (8.9.3/8.9.3) id VAA06140; Tue, 7 Mar 2000 21:35:35 -0500 (EST) (envelope-from rjk) From: Richard J Kuhns MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14533.48246.835804.111800@localhost.grauel.com> Date: Tue, 7 Mar 2000 21:35:34 -0500 (EST) To: Kris Kennaway Cc: Richard J Kuhns , freebsd-current@FreeBSD.ORG Subject: Re: YA ssh question (ssh-askpass?) In-Reply-To: References: <14533.29753.499155.780744@localhost.grauel.com> X-Mailer: VM 6.75 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 4:42:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id 276DE37B537; Wed, 8 Mar 2000 04:42:17 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id HAA00317; Wed, 8 Mar 2000 07:42:04 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38C64A9C.3B8EBFE7@acm.org> Date: Wed, 08 Mar 2000 07:42:04 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Walter Brameld Cc: Kris Kennaway , R Joseph Wright , freebsd-current@FreeBSD.ORG Subject: Re: no openssh after build References: <00030706261400.00767@Bozo_3.BozoLand.domain> <00030706310702.00767@Bozo_3.BozoLand.domain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 bloom@acm.org 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 5:14:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0729637C013 for ; Wed, 8 Mar 2000 05:14:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id FAA13994 for ; Wed, 8 Mar 2000 05:13:32 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: FreeBSD 4.0 release candidate #3 now available. Date: Wed, 08 Mar 2000 05:13:31 -0800 Message-ID: <13989.952521211@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-20000307-CURRENT ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-20000307-CURRENT With ISO images available from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-20000307-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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 7:14:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7F94737C05D for ; Wed, 8 Mar 2000 07:14:10 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p07-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.136]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id AAA09156; Thu, 9 Mar 2000 00:13:56 +0900 (JST) Message-ID: <38C66DE7.43E5E4F0@newsguy.com> Date: Thu, 09 Mar 2000 00:12:39 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Ian Whalley Cc: freebsd-current@FreeBSD.ORG Subject: Re: Remote upgrade from 3.4-STABLE to 4.0 References: <38C5724E.84052394@whalley.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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) dcs@newsguy.com dcs@freebsd.org 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 7:23:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id A7B8A37C05D for ; Wed, 8 Mar 2000 07:23:56 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id KAA47665 for ; Wed, 8 Mar 2000 10:23:48 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000308102112.00bfdd80@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 08 Mar 2000 10:21:12 -0500 To: current@freebsd.org From: Mike Tancsa Subject: 4.0-20000308-CURRENT crypto Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 7:40:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id DA96C37C066 for ; Wed, 8 Mar 2000 07:40:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id HAA21747; Wed, 8 Mar 2000 07:39:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Mike Tancsa Cc: current@FreeBSD.ORG Subject: Re: 4.0-20000308-CURRENT crypto In-reply-to: Your message of "Wed, 08 Mar 2000 10:21:12 EST." <3.0.5.32.20000308102112.00bfdd80@marble.sentex.ca> Date: Wed, 08 Mar 2000 07:39:05 -0800 Message-ID: <21744.952529945@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 8:10: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 42E0B37C078 for ; Wed, 8 Mar 2000 08:09:59 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id KAA16665; Wed, 8 Mar 2000 10:09:56 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-70.max1.wa.cyberlynk.net(207.227.118.70) by peak.mountin.net via smap (V1.3) id sma016663; Wed Mar 8 10:09:43 2000 Message-Id: <3.0.3.32.20000308100755.008639c0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 08 Mar 2000 10:07:55 -0600 To: bloom@acm.org From: "Jeffrey J. Mountin" Subject: Re: no openssh after build Cc: current@FreeBSD.ORG In-Reply-To: <38C64A9C.3B8EBFE7@acm.org> References: <00030706261400.00767@Bozo_3.BozoLand.domain> <00030706310702.00767@Bozo_3.BozoLand.domain> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 >bloom@acm.org > >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 - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 8:11:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id F3C3C37B641 for ; Wed, 8 Mar 2000 08:11:33 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id LAA52030; Wed, 8 Mar 2000 11:11:23 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000308110846.01fcfcf0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 08 Mar 2000 11:08:46 -0500 To: "Jordan K. Hubbard" From: Mike Tancsa Subject: Re: 4.0-20000308-CURRENT crypto Cc: current@FreeBSD.ORG In-Reply-To: <21744.952529945@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 8:27:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from slurpee.jlms.com (jlms.com [216.141.4.160]) by hub.freebsd.org (Postfix) with ESMTP id F38C637B595 for ; Wed, 8 Mar 2000 08:27:34 -0800 (PST) (envelope-from adriel@slurpee.jlms.com) Received: (from adriel@localhost) by slurpee.jlms.com (8.9.3/8.9.3) id KAA10237; Wed, 8 Mar 2000 10:26:26 -0600 (envelope-from adriel) Message-ID: <20000308102625.M5199@adriel.net> Date: Wed, 8 Mar 2000 10:26:25 -0600 From: Adriel Ickler To: freebsd-current@freebsd.org Subject: Re: howto for 3.4-STABLE -> 4.0-CURRENT? References: <200002101835.NAA81587@server.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: ; from Eugene M. Kim on Thu, Feb 10, 2000 at 11:14:11PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 (ab@astralblue.com): > 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 > > "Is your music unpopular? Make it popular; make music > which people like, or make people who like your music." > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ---------------------------------------------------- Adriel Ickler Network Administrator - adriel@jlms.com Self Trading Securities - Voice: 512-263-2769 www.selftrading.com - Fax: 512-263-2141 ---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 8:30:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3186637B576 for ; Wed, 8 Mar 2000 08:30:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA22084; Wed, 8 Mar 2000 08:29:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Mike Tancsa Cc: current@FreeBSD.ORG Subject: Re: 4.0-20000308-CURRENT crypto In-reply-to: Your message of "Wed, 08 Mar 2000 11:08:46 EST." <3.0.5.32.20000308110846.01fcfcf0@marble.sentex.ca> Date: Wed, 08 Mar 2000 08:29:21 -0800 Message-ID: <22081.952532961@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Also, does the ISO image have the same issue ? No, it's uploading now (I caught it in time to stop it). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 8:32:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id AADDB37B61C for ; Wed, 8 Mar 2000 08:32:16 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA81537; Wed, 8 Mar 2000 08:32:05 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA99204; Wed, 8 Mar 2000 08:32:15 -0800 (PST) (envelope-from obrien) Date: Wed, 8 Mar 2000 08:32:15 -0800 From: "David O'Brien" To: Dave Boers Cc: freebsd-current@freebsd.org, dalroi@wit401310.student.utwente.nl Subject: Re: Small bug in chown and chgrp ? Message-ID: <20000308083215.C98890@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000306203608.B26973@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000306203608.B26973@relativity.student.utwente.nl>; from djb@relativity.student.utwente.nl on Mon, Mar 06, 2000 at 08:36:08PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 8:36: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from slurpee.jlms.com (jlms.com [216.141.4.160]) by hub.freebsd.org (Postfix) with ESMTP id F032B37B580 for ; Wed, 8 Mar 2000 08:36:01 -0800 (PST) (envelope-from adriel@slurpee.jlms.com) Received: (from adriel@localhost) by slurpee.jlms.com (8.9.3/8.9.3) id KAA10394; Wed, 8 Mar 2000 10:34:35 -0600 (envelope-from adriel) Message-ID: <20000308103435.N5199@adriel.net> Date: Wed, 8 Mar 2000 10:34:35 -0600 From: Adriel Ickler To: freebsd-current@FreeBSD.ORG Subject: Re: howto for 3.4-STABLE -> 4.0-CURRENT? References: <200002101835.NAA81587@server.baldwin.cx> <20000308102625.M5199@adriel.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <20000308102625.M5199@adriel.net>; from Adriel Ickler on Wed, Mar 08, 2000 at 10:26:25AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Addition: you may want to consider carefully the ramifications of remaking all the devices while logged in from remote, and outline a method, I didnt need to I found out because this box was installed after jan 2000. Quoting Adriel Ickler (adriel@adriel.net): > 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 (ab@astralblue.com): > > 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 > > > > "Is your music unpopular? Make it popular; make music > > which people like, or make people who like your music." > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > ---------------------------------------------------- > Adriel Ickler > Network Administrator - adriel@jlms.com > Self Trading Securities - Voice: 512-263-2769 > www.selftrading.com - Fax: 512-263-2141 > ---------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ---------------------------------------------------- Adriel Ickler Network Administrator - adriel@jlms.com Self Trading Securities - Voice: 512-263-2769 www.selftrading.com - Fax: 512-263-2141 ---------------------------------------------------- How long does it take a DEC field service engineer to change a lightbulb? It depends on how many bad ones he brought with him. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 8:47:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from argon.blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 9C22F37C4A3 for ; Wed, 8 Mar 2000 08:47:25 -0800 (PST) (envelope-from will@blackdawn.com) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 72D511A69; Wed, 8 Mar 2000 11:47:14 -0500 (EST) Date: Wed, 8 Mar 2000 11:47:14 -0500 From: Will Andrews To: Mike Tancsa Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: 4.0-20000308-CURRENT crypto Message-ID: <20000308114714.B424@argon.blackdawn.com> References: <21744.952529945@zippy.cdrom.com> <3.0.5.32.20000308110846.01fcfcf0@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3.0.5.32.20000308110846.01fcfcf0@marble.sentex.ca>; from mike@sentex.ca on Wed, Mar 08, 2000 at 11:08:46AM -0500 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 08, 2000 at 11:08:46AM -0500, Mike Tancsa wrote: > 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_ ? I can assure you that, as an AP Latin V (seventh year Latin for me) student, "i.e." is the correct notation. :-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9: 2:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id DFA9B37C32F for ; Wed, 8 Mar 2000 09:02:09 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA12193; Wed, 8 Mar 2000 09:02:05 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA39397; Wed, 8 Mar 2000 09:02:04 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 8 Mar 2000 09:02:04 -0800 (PST) Message-Id: <200003081702.JAA39397@vashon.polstra.com> To: dmmiller@cvzoom.net Subject: Re: More "ld-elf.so.1: assert failed" messages In-Reply-To: <38C5A975.957756C4@cvzoom.net> References: <38BA5751.2396AE87@cvzoom.net> <38BB1E9C.CF44EC93@cvzoom.net> <200003060201.SAA85727@vashon.polstra.com> <38C5A975.957756C4@cvzoom.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <38C5A975.957756C4@cvzoom.net>, Donn Miller 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9: 5:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id C26C537C2DA for ; Wed, 8 Mar 2000 09:05:15 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id MAA32482 for ; Wed, 8 Mar 2000 12:05:05 -0500 (EST) Date: Wed, 8 Mar 2000 12:05:05 -0500 (EST) From: "Matthew N. Dodd" To: current@freebsd.org Subject: world breakage with NO_OPENSSL Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9:13: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 931BC37C64F for ; Wed, 8 Mar 2000 09:12:51 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id LAA17118; Wed, 8 Mar 2000 11:12:47 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-70.max1.wa.cyberlynk.net(207.227.118.70) by peak.mountin.net via smap (V1.3) id sma017115; Wed Mar 8 11:12:28 2000 Message-Id: <3.0.3.32.20000308111040.00aea270@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 08 Mar 2000 11:10:40 -0600 To: "Jordan K. Hubbard" From: "Jeffrey J. Mountin" Subject: Re: 4.0-20000308-CURRENT crypto Cc: current@FreeBSD.ORG In-Reply-To: <21744.952529945@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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-20000307-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-YYYYMMDD-CURRENT and the src directory: ncftp>mget [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 - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9:14:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id F399537B643 for ; Wed, 8 Mar 2000 09:14:11 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for current@freebsd.org id 12Sk2E-000KNx-00; Wed, 8 Mar 2000 17:14:10 +0000 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id RAA43598 for current@freebsd.org; Wed, 8 Mar 2000 17:14:10 GMT (envelope-from jcm) Message-ID: <20000308171409.A43398@freebsd-uk.eu.org> Date: Wed, 8 Mar 2000 17:14:09 +0000 From: J McKitrick To: current@freebsd.org Subject: Parallel port Zip drive and EPP mode Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9:17:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 520A637C14E for ; Wed, 8 Mar 2000 09:17:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA22475 for ; Wed, 8 Mar 2000 09:16:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: ERRATA on the 4.0-20000307-CURRENT release candidate (#3) Date: Wed, 08 Mar 2000 09:16:31 -0800 Message-ID: <22469.952535791@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9:27:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 996F337C18B for ; Wed, 8 Mar 2000 09:27:48 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA22612; Wed, 8 Mar 2000 09:26:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Jeffrey J. Mountin" Cc: current@FreeBSD.ORG Subject: Re: 4.0-20000308-CURRENT crypto In-reply-to: Your message of "Wed, 08 Mar 2000 11:10:40 CST." <3.0.3.32.20000308111040.00aea270@207.227.119.2> Date: Wed, 08 Mar 2000 09:26:35 -0800 Message-ID: <22609.952536395@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9:35:45 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 13E5A37B5F0; Wed, 8 Mar 2000 09:35:44 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 116DA2E815C; Wed, 8 Mar 2000 09:35:44 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 8 Mar 2000 09:35:44 -0800 (PST) From: Kris Kennaway To: "Jeffrey J. Mountin" Cc: bloom@acm.org, current@FreeBSD.ORG Subject: Re: no openssh after build In-Reply-To: <3.0.3.32.20000308100755.008639c0@207.227.119.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9:36:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 37A0D37B513 for ; Wed, 8 Mar 2000 09:36:22 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 12800 invoked from network); 8 Mar 2000 17:36:16 -0000 Received: from lcm161.cvzoom.net (HELO cvzoom.net) (208.230.69.161) by ns.cvzoom.net with SMTP; 8 Mar 2000 17:36:16 -0000 Message-ID: <38C68F72.4070405@cvzoom.net> Date: Wed, 08 Mar 2000 12:35:46 -0500 From: Donn Miller User-Agent: Mozilla/5.0 (X11; N; FreeBSD 4.0-CURRENT i386; en-US; m14) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: current@freebsd.org Subject: Re: More "ld-elf.so.1: assert failed" messages References: <38BA5751.2396AE87@cvzoom.net> <38BB1E9C.CF44EC93@cvzoom.net> <200003060201.SAA85727@vashon.polstra.com> <38C5A975.957756C4@cvzoom.net> <200003081702.JAA39397@vashon.polstra.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > = > In article <38C5A975.957756C4@cvzoom.net>, > 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.=A0 Mozilla doesn't have the problem with the = "non-patch" version.=A0 So, maybe it isn't the application.=A0 Or, maybe = the = original, "non-patch" version wasn't doing something right. Just wondering, in case the problem isn't with Mozilla.=A0 I'm using = Mozilla right now, with the original ld-elf.so.1.=A0 (The fonts are hard = on my eyes.) - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9:38:49 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 3917937B580; Wed, 8 Mar 2000 09:38:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 362DD2E8106; Wed, 8 Mar 2000 09:38:47 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 8 Mar 2000 09:38:47 -0800 (PST) From: Kris Kennaway To: "Jeffrey J. Mountin" Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: FTP globbing bug (Re: 4.0-20000308-CURRENT crypto) In-Reply-To: <3.0.3.32.20000308111040.00aea270@207.227.119.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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-YYYYMMDD-CURRENT and the src directory: > > ncftp>mget [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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9:40:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id E57C337C193 for ; Wed, 8 Mar 2000 09:40:37 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id MAA59036; Wed, 8 Mar 2000 12:40:25 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000308123749.0181c550@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 08 Mar 2000 12:37:49 -0500 To: "Jordan K. Hubbard" From: Mike Tancsa Subject: Re: 4.0-20000308-CURRENT crypto Cc: current@FreeBSD.ORG In-Reply-To: <22609.952536395@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9:42:56 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 43B9E37B8DB; Wed, 8 Mar 2000 09:42:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 411B72E8108; Wed, 8 Mar 2000 09:42:54 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 8 Mar 2000 09:42:54 -0800 (PST) From: Kris Kennaway To: Adriel Ickler Cc: freebsd-current@freebsd.org Subject: Re: howto for 3.4-STABLE -> 4.0-CURRENT? In-Reply-To: <20000308102625.M5199@adriel.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9:45:14 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 0442837B8DB; Wed, 8 Mar 2000 09:45:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 019572E815C; Wed, 8 Mar 2000 09:45:11 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 8 Mar 2000 09:45:11 -0800 (PST) From: Kris Kennaway To: "Matthew N. Dodd" Cc: current@freebsd.org Subject: Re: world breakage with NO_OPENSSL In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 9:57:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 8D67F37B644; Wed, 8 Mar 2000 09:57:13 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id JAA33774; Wed, 8 Mar 2000 09:56:56 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38C69468.13064438@gorean.org> Date: Wed, 08 Mar 2000 09:56:56 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-CURRENT-0307 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: R Joseph Wright , freebsd-current@FreeBSD.ORG, Kris Kennaway Subject: Re: no openssh after build References: <90169.952420152@axl.ops.uunet.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 10:29:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 396E837B515; Wed, 8 Mar 2000 10:29:38 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id MAA14589; Wed, 8 Mar 2000 12:29:36 -0600 (CST) From: Mohit Aron Message-Id: <200003081829.MAA14589@cs.rice.edu> Subject: enabling APIC without SMP To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Date: Wed, 8 Mar 2000 12:29:35 -0600 (CST) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 10:57:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3205237C253 for ; Wed, 8 Mar 2000 10:57:08 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA82434 for ; Wed, 8 Mar 2000 10:57:07 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA89601 for current@freebsd.org; Wed, 8 Mar 2000 10:57:18 -0800 (PST) (envelope-from obrien) Date: Wed, 8 Mar 2000 10:57:17 -0800 From: "David O'Brien" To: current@freebsd.org Subject: build breakage in libpam w/NO_OPENSSH Message-ID: <20000308105717.A89582@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With USA_RESIDENT=YES NOINFO=true NOGAMES=true NODESCRYPTLINKS=true NO_OPENSSH=true, I get this on a buildworld when updating a Jan 15th box. ===> libpam/modules/pam_ssh cc -pipe -O -Wall -I/FBSD/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh -I/usr/obj/FBSD/src/i386/usr/include -c /FBSD/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/log-client.c -o log-client.o cc -pipe -O -Wall -I/FBSD/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh -I/usr/obj/FBSD/src/i386/usr/include -c /FBSD/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/pam_ssh/pam_ssh.c -o pam_ssh.o building standard pam_ssh library ranlib libpam_ssh.a cc -fpic -DPIC -pipe -O -Wall -I/FBSD/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh -I/usr/obj/FBSD/src/i386/usr/include -c /FBSD/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/log-client.c -o log-client.So cc -fpic -DPIC -pipe -O -Wall -I/FBSD/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh -I/usr/obj/FBSD/src/i386/usr/include -c /FBSD/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/pam_ssh/pam_ssh.c -o pam_ssh.So building shared library pam_ssh.so /usr/obj/FBSD/src/i386/usr/libexec/elf/ld: cannot open -lssh: No such file or directory *** Error code 1 Stop in /FBSD/src/lib/libpam/modules/pam_ssh. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 11: 3:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 92B1D37B548 for ; Wed, 8 Mar 2000 11:03:52 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id NAA17696; Wed, 8 Mar 2000 13:03:39 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-69.max1.wa.cyberlynk.net(207.227.118.69) by peak.mountin.net via smap (V1.3) id sma017693; Wed Mar 8 13:03:09 2000 Message-Id: <3.0.3.32.20000308130122.00b8a100@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 08 Mar 2000 13:01:22 -0600 To: "Jordan K. Hubbard" From: "Jeffrey J. Mountin" Subject: Re: 4.0-20000308-CURRENT crypto Cc: current@FreeBSD.ORG In-Reply-To: <22609.952536395@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 11:42:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from www.menzor.dk (themoonismadeofgreenchease.dk [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id A266E37B57E for ; Wed, 8 Mar 2000 11:42:04 -0800 (PST) (envelope-from morten@seeberg.dk) Received: from sos (userhost.cma.dk [130.228.127.200]) by www.menzor.dk (8.8.8/8.8.8) with SMTP id VAA02661 for ; Wed, 8 Mar 2000 21:01:27 +0100 (CET) (envelope-from morten@seeberg.dk) Message-ID: <000f01bf8936$e0be2420$deff58c1@sos> From: "Morten Seeberg" To: Subject: RC3: APM on IBM Thinkpad 600E (2645,5A0) Date: Wed, 8 Mar 2000 20:45:34 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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-20000307-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=0x183f9ff 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: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 pcic-pci0: mem 0x50102000-0x50102fff irq 11 at device 2.0 on pci0 pcic-pci1: mem 0x50101000-0x50101fff irq 11 at device 2.1 on pci0 csa0: mem 0x50000000-0x500fffff,0x50100000-0x50100fff irq 11 at device 6.0 on pci0 pcm0: on csa0 pcm0: ac97 codec reports dac not ready isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcf0-0xfcff at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 11 chip1: port 0xefa0-0xefaf at device 7.3 on pci0 fdc0: 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: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic: management irq 10 pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pccard0: on pcic0 pccard1: 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 [13328/15/63] at ata0-master using UDMA33 acd0: DVD-ROM 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 11:46:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 5DAF937B66A for ; Wed, 8 Mar 2000 11:46:26 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 687CF3E40; Wed, 8 Mar 2000 20:46:17 +0100 (CET) Date: Wed, 8 Mar 2000 20:46:17 +0100 From: Jesper Skriver To: Morten Seeberg Cc: current@freebsd.org Subject: Re: RC3: APM on IBM Thinkpad 600E (2645,5A0) Message-ID: <20000308204617.B21712@skriver.dk> References: <000f01bf8936$e0be2420$deff58c1@sos> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: <000f01bf8936$e0be2420$deff58c1@sos>; from morten@seeberg.dk on Wed, Mar 08, 2000 at 08:45:34PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 12:26:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from www.menzor.dk (themoonismadeofgreenchease.dk [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id DC7DC37B580 for ; Wed, 8 Mar 2000 12:26:22 -0800 (PST) (envelope-from morten@seeberg.dk) Received: from sos (userhost.cma.dk [130.228.127.200]) by www.menzor.dk (8.8.8/8.8.8) with SMTP id VAA02805 for ; Wed, 8 Mar 2000 21:45:52 +0100 (CET) (envelope-from morten@seeberg.dk) Message-ID: <001f01bf893d$139cd980$deff58c1@sos> From: "Morten Seeberg" To: Subject: RC3: No support for 3C589B/C (ep0) during install? Date: Wed, 8 Mar 2000 21:29:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 :) *Please select IRQs that can be used by PC-cards *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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 13:28: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from www.telemere.net (www.telemere.net [63.224.9.3]) by hub.freebsd.org (Postfix) with ESMTP id D1D7A37C0FB for ; Wed, 8 Mar 2000 13:28:01 -0800 (PST) (envelope-from visigoth@telemere.net) Received: by www.telemere.net (Postfix, from userid 1001) id 4E0D270601; Wed, 8 Mar 2000 15:34:58 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by www.telemere.net (Postfix) with ESMTP id 4A78F6C801 for ; Wed, 8 Mar 2000 15:34:58 -0600 (CST) Date: Wed, 8 Mar 2000 15:34:58 -0600 (CST) From: Visigoth To: freebsd-current@freebsd.org Subject: /etc/periodic/daily/200.backup-passwd and MD5 Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1574324419-952551298=:16144" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1574324419-952551298=:16144 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 visigoth@telemere.net --0-1574324419-952551298=:16144 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="200.backup-passwd.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Patch for 200.backup-passwd and MD5 Content-Disposition: attachment; filename="200.backup-passwd.patch" KioqIC92YXIvYmFja3Vwcy8yMDAuYmFja3VwLXBhc3N3ZAlNb24gRmViIDIx IDA5OjE5OjAwIDIwMDANCi0tLSAvZXRjL3BlcmlvZGljL2RhaWx5LzIwMC5i YWNrdXAtcGFzc3dkCU1vbiBGZWIgMjEgMDk6MTk6MjggMjAwMA0KKioqKioq KioqKioqKioqDQoqKiogMTYsMjIgKioqKg0KICAgICAgaWYgY21wIC1zICRi YWsvbWFzdGVyLnBhc3N3ZC5iYWsgL2V0Yy9tYXN0ZXIucGFzc3dkOyB0aGVu IDo7IGVsc2UNCiAgCWVjaG8gIiRob3N0IHBhc3N3ZCBkaWZmczoiDQogIAlk aWZmIC11ICRiYWsvbWFzdGVyLnBhc3N3ZC5iYWsgL2V0Yy9tYXN0ZXIucGFz c3dkIHxcDQohIAkJc2VkICdzL15cKFs8Pl0gW146XSpcKTpbXjpdKjovXDE6 KHBhc3N3b3JkKTovJw0KICAJbXYgJGJhay9tYXN0ZXIucGFzc3dkLmJhayAk YmFrL21hc3Rlci5wYXNzd2QuYmFrMg0KICAJY3AgLXAgL2V0Yy9tYXN0ZXIu cGFzc3dkICRiYWsvbWFzdGVyLnBhc3N3ZC5iYWsNCiAgICAgIGZpDQotLS0g MTYsMjIgLS0tLQ0KICAgICAgaWYgY21wIC1zICRiYWsvbWFzdGVyLnBhc3N3 ZC5iYWsgL2V0Yy9tYXN0ZXIucGFzc3dkOyB0aGVuIDo7IGVsc2UNCiAgCWVj aG8gIiRob3N0IHBhc3N3ZCBkaWZmczoiDQogIAlkaWZmIC11ICRiYWsvbWFz dGVyLnBhc3N3ZC5iYWsgL2V0Yy9tYXN0ZXIucGFzc3dkIHxcDQohIAkJc2Vk ICdzL15cKFteOl0qXCk6W146XSo6L1wxOihwYXNzd29yZCk6LycNCiAgCW12 ICRiYWsvbWFzdGVyLnBhc3N3ZC5iYWsgJGJhay9tYXN0ZXIucGFzc3dkLmJh azINCiAgCWNwIC1wIC9ldGMvbWFzdGVyLnBhc3N3ZCAkYmFrL21hc3Rlci5w YXNzd2QuYmFrDQogICAgICBmaQ0K --0-1574324419-952551298=:16144-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 13:30:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id C550F37B68D for ; Wed, 8 Mar 2000 13:30:07 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id QAA76574 for ; Wed, 8 Mar 2000 16:30:06 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000308162728.01fb4e20@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 08 Mar 2000 16:27:28 -0500 To: current@freebsd.org From: Mike Tancsa Subject: March 8 SNAP gateway_enable="YES" not being set ? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I could have swore I set this during the initial installation, but it did not get set in /etc/rc.conf. I am going to do another install tonight and verify if this is the case. Has anyone else noticed this ? Its very possible I made a typo, but I thought I would mention it just in case. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 13:33:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from waldorf.cs.uni-dortmund.de (waldorf.cs.uni-dortmund.de [129.217.4.42]) by hub.freebsd.org (Postfix) with ESMTP id 4F98637B67F for ; Wed, 8 Mar 2000 13:33:36 -0800 (PST) (envelope-from Kai.Grossjohann@CS.Uni-Dortmund.DE) Received: from marcy.cs.uni-dortmund.de (marcy.cs.uni-dortmund.de [129.217.20.159]) by waldorf.cs.uni-dortmund.de with ESMTP id WAA00383 for ; Wed, 8 Mar 2000 22:33:27 +0100 (MET) Received: from lucy.cs.uni-dortmund.de (lucy [129.217.20.160]) by marcy.cs.uni-dortmund.de id WAA20465; Wed, 8 Mar 2000 22:33:26 +0100 (MET) Received: (from grossjoh@localhost) by lucy.cs.uni-dortmund.de (8.9.3/8.9.3/Debian 8.9.3-6) id WAA12297; Wed, 8 Mar 2000 22:33:26 +0100 X-Authentication-Warning: lucy.cs.uni-dortmund.de: grossjoh set sender to Kai.Grossjohann@CS.Uni-Dortmund.DE using -f To: freebsd-current@FreeBSD.ORG Subject: Re: ssh strangeness in -current... References: <200003060010.BAA98138@dorifer.heim3.tu-clausthal.de> From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai=?iso-8859-1?q?_Gro=DFjohann?=) Date: 08 Mar 2000 22:33:26 +0100 In-Reply-To: Oliver Fromme's message of "Mon, 6 Mar 2000 01:10:30 +0100 (CET)" Message-ID: Lines: 21 User-Agent: Gnus/5.0804 (Gnus v5.8.4) Emacs/20.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 14: 2:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from gnu.IN-Berlin.DE (gnu.in-berlin.de [192.109.42.4]) by hub.freebsd.org (Postfix) with ESMTP id 003A437C28A for ; Wed, 8 Mar 2000 14:02:06 -0800 (PST) (envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de) Received: from hirsch.in-berlin.de (root@hirsch.in-berlin.de [192.109.42.6]) by gnu.IN-Berlin.DE (8.9.3/8.9.3) with ESMTP id XAA19871 for ; Wed, 8 Mar 2000 23:02:02 +0100 (CET) (envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de) Received: by hirsch.in-berlin.de (Smail3.2) id ; Wed, 8 Mar 2000 23:02:00 +0100 (CET) Received: by dva.in-berlin.de (Postfix, from userid 200) id 90F3610E00; Wed, 8 Mar 2000 22:49:47 +0100 (CET) Date: Wed, 8 Mar 2000 22:49:47 +0100 From: Boris Staeblow To: freebsd-current@freebsd.org Subject: bridging broken in -current AND -stable Message-ID: <20000308224947.A1755@dva.in-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible that bridging is broken in -current and -stable? Some minutes (02 - 30 min.) after bootup I get: Fatal trap 12: Page fault while in kernel mode fault code: Supervisor read, page not present Sorry, i´ve no further crashlogs/dumps. This panic occur only with bridging enabled - in -current AND -stable. My last working (stable) kernel with bridging is from 17 Jan 2000. Extract from -current dmesg: de0: port 0xe000-0xe07f \ mem 0xe5000000-0xe50003ff irq 7 at device 9.0 on pci0 de0: 21143 [10-100Mb/s] pass 4.1 de0: address 00:80:ad:78:11:4b de0: driver is using old-style compatability shims de1: port 0xd400-0xd47f \ mem 0xe4000000-0xe400007f irq 11 at device 12.0 on pci0 de1: 21041 [10Mb/s] pass 1.1 de1: address 00:80:ad:1c:af:a8 de1: driver is using old-style compatability shims BRIDGE 990810, have 13 interfaces -- index 1 type 6 phy 0 addrl 6 addr 00.80.ad.78.11.4b -- index 2 type 6 phy 0 addrl 6 addr 00.80.ad.1c.af.a8 Boris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 14: 5:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 3833737B6A6 for ; Wed, 8 Mar 2000 14:05:40 -0800 (PST) (envelope-from brameld@twave.net) Received: from [12.21.241.164] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id ga046858 for ; Wed, 8 Mar 2000 17:05:23 -0500 Received: from Bozo_3.BozoLand.domain (localhost [127.0.0.1]) by Bozo_3.BozoLand.domain (8.9.3/8.9.3) with SMTP id RAA00235; Wed, 8 Mar 2000 17:05:10 -0500 (EST) (envelope-from brameld@twave.net) From: Walter Brameld To: "F. Heinrichmeyer" Subject: Re: Parallel port Zip drive Date: Wed, 8 Mar 2000 17:03:41 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-current@FreeBSD.ORG References: <00030723213100.08909@Bozo_3.BozoLand.domain> <38C63957.CF484F5C@fernuni-hagen.de> <00030806394001.00611@Bozo_3.BozoLand.domain> In-Reply-To: <00030806394001.00611@Bozo_3.BozoLand.domain> MIME-Version: 1.0 Message-Id: <00030817051000.00230@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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:fritz.heinrichmeyer@fernuni-hagen.de > > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 14:16:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 367AF37B62A for ; Wed, 8 Mar 2000 14:16:36 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id XAA68192; Wed, 8 Mar 2000 23:15:23 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200003082215.XAA68192@info.iet.unipi.it> Subject: Re: bridging broken in -current AND -stable In-Reply-To: <20000308224947.A1755@dva.in-berlin.de> from Boris Staeblow at "Mar 8, 2000 10:49:47 pm" To: Boris Staeblow Date: Wed, 8 Mar 2000 23:15:23 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Charset iso-8859-1 unsupported, filtering to ASCII...] > > 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. can you switch to some supported card ("ed" or "fxp") ? cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 14:39:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 6EDB937B540 for ; Wed, 8 Mar 2000 14:39:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id RAA05957; Wed, 8 Mar 2000 17:39:40 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200003082239.RAA05957@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <001f01bf893d$139cd980$deff58c1@sos> Date: Wed, 08 Mar 2000 17:39:40 -0500 (EST) From: John Baldwin To: Morten Seeberg Subject: RE: RC3: No support for 3C589B/C (ep0) during install? Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 -- 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 15: 4:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (hda.bicnet.net [208.220.68.243]) by hub.freebsd.org (Postfix) with ESMTP id AD45737B62C for ; Wed, 8 Mar 2000 15:04:37 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id SAA64038; Wed, 8 Mar 2000 18:08:06 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200003082308.SAA64038@hda.hda.com> Subject: Re: current lockups In-Reply-To: <00Mar8.103928est.115210@border.alcanet.com.au> from Peter Jeremy at "Mar 7, 2000 09:45:55 am" To: Peter Jeremy Date: Wed, 8 Mar 2000 18:08:06 -0500 (EST) Cc: Dave Boers , Arun Sharma , freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 2000-Mar-07 06:29:17 +1100, Dave Boers wrote: > >It is rumoured that Arun Sharma had the courage to say: > >> Compiling Mozilla with make -j 2 got -current to lock up, twice in > >> succession. I'm running a fairly recent snapshot (a week or two old) > >> on a Dual celeron box (BP6) with UDMA66 enabled. > > > >Finally. I've been complaining about this on several occasions. I'm also > >running UDMA66 and Dual Celeron BP6. No overclocking. > > Later postings mention possible problems with UDMA66. The other > possibility that has been discussed recently is potential priority > inversions for processes using rtptio and idprio. > > Note that ntpd will use rtprio if the Posix P1003.1b extensions aren't > enabled in the kernel. (These were enabled by default in GENERIC on > i386 in mid-January). If you have the new ntpd (rather than xntpd) > and are running a kernel without options P1003_1B, > _KPOSIX_PRIORITY_SCHEDULING and _KPOSIX_VERSION=199309L, you could > potentially get a lockup due to a priority inversion. (Though I > think the probability is very small). There's no difference between rtprio and P1003.1B scheduling other than the name. rtprio is the same as P1003.1B "SCHED_RR". I'd like to remove the rtprio call from ntpd. I think we ought to do it now before 4.0 ships. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 15: 6:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from gnu.IN-Berlin.DE (gnu.in-berlin.de [192.109.42.4]) by hub.freebsd.org (Postfix) with ESMTP id BD42F37B58D for ; Wed, 8 Mar 2000 15:06:09 -0800 (PST) (envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de) Received: from hirsch.in-berlin.de (root@hirsch.in-berlin.de [192.109.42.6]) by gnu.IN-Berlin.DE (8.9.3/8.9.3) with ESMTP id AAA21897; Thu, 9 Mar 2000 00:06:04 +0100 (CET) (envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de) Received: by hirsch.in-berlin.de (Smail3.2) id ; Thu, 9 Mar 2000 00:06:02 +0100 (CET) Received: by dva.in-berlin.de (Postfix, from userid 200) id 7E7A010E00; Thu, 9 Mar 2000 00:04:54 +0100 (CET) Date: Thu, 9 Mar 2000 00:04:54 +0100 From: Boris Staeblow To: Luigi Rizzo Cc: freebsd-current@FreeBSD.ORG Subject: Re: bridging broken in -current AND -stable Message-ID: <20000309000454.A37304@dva.in-berlin.de> References: <20000308224947.A1755@dva.in-berlin.de> <200003082215.XAA68192@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: <200003082215.XAA68192@info.iet.unipi.it>; from luigi@info.iet.unipi.it on Wed, Mar 08, 2000 at 11:15:23PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Ooohhhhhhhh noooo! :-(( 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. Boris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 15:54:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by hub.freebsd.org (Postfix) with ESMTP id CF2CC37B70F for ; Wed, 8 Mar 2000 15:54:09 -0800 (PST) (envelope-from bartequi@neomedia.it) Received: from bartequi.ottodomain.org (ppp30-pa4.neomedia.it [195.103.207.222]) by aragorn.neomedia.it (8.9.3/8.9.3) with SMTP id AAA01080 for ; Thu, 9 Mar 2000 00:54:06 +0100 (CET) From: Salvo Bartolotta Date: Wed, 08 Mar 2000 23:57:24 GMT Message-ID: <20000308.23572400@bartequi.ottodomain.org> Subject: upgraded to -CURRENT (?) et al. To: freebsd-current@FreeBSD.ORG X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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=3DProgramming & development tools.' Error code 1 (six times) 7) /usr/src/usr.bin/xinstall/make clean all install NOSHARED=3DYES 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 #@[]*^=A7 [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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 16: 7:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by hub.freebsd.org (Postfix) with ESMTP id D220337B6E5 for ; Wed, 8 Mar 2000 16:07:21 -0800 (PST) (envelope-from bartequi@neomedia.it) Received: from bartequi.ottodomain.org (ppp30-pa4.neomedia.it [195.103.207.222]) by aragorn.neomedia.it (8.9.3/8.9.3) with SMTP id BAA18237 for ; Thu, 9 Mar 2000 01:07:10 +0100 (CET) From: Salvo Bartolotta Date: Thu, 09 Mar 2000 00:10:27 GMT Message-ID: <20000309.102700@bartequi.ottodomain.org> Subject: upgraded to -CURRENT (?) et al. II Aside note To: freebsd-current@FreeBSD.ORG X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear users, I forgot to specify (yawn ..) that, after recompiling another kernel=20 at the end of my upgrading procedure, I no longer saw the "wd1s2a"=20 problem. My / device was correctly identified as ad1s2a :-) Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 16:19: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 846BE37B6E5 for ; Wed, 8 Mar 2000 16:18:51 -0800 (PST) (envelope-from brameld@twave.net) Received: from [12.21.241.164] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id sa050432 for ; Wed, 8 Mar 2000 19:18:43 -0500 Received: from Bozo_3.BozoLand.domain (localhost [127.0.0.1]) by Bozo_3.BozoLand.domain (8.9.3/8.9.3) with SMTP id TAA00449; Wed, 8 Mar 2000 19:18:30 -0500 (EST) (envelope-from brameld@twave.net) From: Walter Brameld To: J McKitrick , current@freebsd.org Subject: Re: Parallel port Zip drive and EPP mode Date: Wed, 8 Mar 2000 19:09:58 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <20000308171409.A43398@freebsd-uk.eu.org> In-Reply-To: <20000308171409.A43398@freebsd-uk.eu.org> MIME-Version: 1.0 Message-Id: <00030819183007.00362@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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=0x383f9ff <- snip -> ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 vpo0: on ppbus0 imm0: EPP 1.9 mode sbc0: 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: on sbc0 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x620-0x623 on isa0 ad0: 17206MB [34960/16/63] at ata0-master using UDMA33 ad1: 8693MB [17662/16/63] at ata0-slave using UDMA33 acd0: CDROM at ata1-master using WDMA2 da0 at vpo0 bus 0 target 5 lun 0 da0: 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 16:43:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [216.99.193.36]) by hub.freebsd.org (Postfix) with ESMTP id 7568337B73E for ; Wed, 8 Mar 2000 16:43:20 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id QAA03602; Wed, 8 Mar 2000 16:43:25 -0800 Received: by shell1.aracnet.com (8.9.3) id QAA14081; Wed, 8 Mar 2000 16:45:39 -0800 Date: Wed, 8 Mar 2000 16:45:39 -0800 (PST) From: Brian Beattie To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: FreeBSD 4.0 release candidate #3 now available. In-Reply-To: <13989.952521211@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Mar 2000, Jordan K. Hubbard wrote: > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-20000307-CURRENT > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-20000307-CURRENT > > With ISO images available from: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-20000307-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, beattie@aracnet.com | standards based software. Users of Microsoft beattie@aracnet.com | 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 16:47:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 9407337B6F0 for ; Wed, 8 Mar 2000 16:47:27 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115256>; Thu, 9 Mar 2000 11:48:16 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: current lockups In-reply-to: <200003082308.SAA64038@hda.hda.com>; from dufault@hda.com on Thu, Mar 09, 2000 at 10:05:21AM +1100 To: Peter Dufault Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Mar9.114816est.115256@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <00Mar8.103928est.115210@border.alcanet.com.au> <200003082308.SAA64038@hda.hda.com> Date: Thu, 9 Mar 2000 11:48:14 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Mar-09 10:05:21 +1100, Peter Dufault wrote: >There's no difference between rtprio and P1003.1B scheduling other than >the name. rtprio is the same as P1003.1B "SCHED_RR". I wasn't aware of that. >I'd like to remove the rtprio call from ntpd. I think we ought to do >it now before 4.0 ships. Given there is a known a priority inversion bug related to realtime (or idle) scheduling, it would seem wise not to use it in any system utilities. The relevant patch would appear to be (untested): --- /usr/src/usr.sbin/ntp/config.h Tue Feb 1 13:56:05 2000 +++ /tmp/config.h Thu Mar 9 11:46:11 2000 @@ -619,10 +619,10 @@ #define HAVE_RANDOM 1 /* Define if you have the rtprio function. */ -#define HAVE_RTPRIO 1 +/* #undef HAVE_RTPRIO */ /* Define if you have the sched_setscheduler function. */ -#define HAVE_SCHED_SETSCHEDULER 1 +/* #undef HAVE_SCHED_SETSCHEDULER */ /* Define if you have the setlinebuf function. */ #define HAVE_SETLINEBUF 1 Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 16:49:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by hub.freebsd.org (Postfix) with ESMTP id A151737B672 for ; Wed, 8 Mar 2000 16:49:06 -0800 (PST) (envelope-from bartequi@neomedia.it) Received: from bartequi.ottodomain.org (ppp30-pa4.neomedia.it [195.103.207.222]) by aragorn.neomedia.it (8.9.3/8.9.3) with SMTP id BAA30758 for ; Thu, 9 Mar 2000 01:31:51 +0100 (CET) From: Salvo Bartolotta Date: Thu, 09 Mar 2000 00:35:09 GMT Message-ID: <20000309.350900@bartequi.ottodomain.org> Subject: upgraded to -CURRENT (?) et al. III To: freebsd-current@FreeBSD.ORG X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear users, I forgot to specify another point in my first letter:=20 "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=20 -STABLE and finally to -CURRENT.=20 Sorry for these omissions :-(=20 I should really go to bed *sigh* Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 17:16:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from elwood.cais.com (elwood.cais.com [199.0.216.215]) by hub.freebsd.org (Postfix) with ESMTP id 7A5FB37B672 for ; Wed, 8 Mar 2000 17:16:32 -0800 (PST) (envelope-from ron@bigslacker.com) Received: from proxy.delron-corp.com ([209.8.126.130]) by elwood.cais.com (8.9.1/Elwood) with ESMTP id UAA20727 for ; Wed, 8 Mar 2000 20:07:37 -0500 (EST) Received: from localhost (ron@localhost) by proxy.delron-corp.com (8.9.3/8.9.3) with ESMTP id UAA04917 for ; Wed, 8 Mar 2000 20:14:26 -0500 (EST) (envelope-from ron@bigslacker.com) Date: Wed, 8 Mar 2000 20:14:26 -0500 (EST) From: Ron Pritchett X-Sender: ron@proxy.delron-corp.com To: current@freebsd.org Subject: Kerberos 5 in 4.0? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 17:20: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id B6F9437B63E for ; Wed, 8 Mar 2000 17:20:00 -0800 (PST) (envelope-from bob@luke.immure.com) Received: (from bob@localhost) by luke.immure.com (8.9.3/8.9.3) id TAA11009; Wed, 8 Mar 2000 19:19:42 -0600 (CST) (envelope-from bob) Date: Wed, 8 Mar 2000 19:19:42 -0600 From: Bob Willcox To: Brian Beattie Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FreeBSD 4.0 release candidate #3 now available. Message-ID: <20000308191942.B10795@luke.immure.com> Reply-To: Bob Willcox References: <13989.952521211@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from beattie@aracnet.com on Wed, Mar 08, 2000 at 04:45:39PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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-20000307-CURRENT > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-20000307-CURRENT > > > > With ISO images available from: > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-20000307-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, bob@immure.com but the wish to find out, which is the exact Austin, TX opposite. -- Bertrand Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 17:22:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A50F537B6D1 for ; Wed, 8 Mar 2000 17:22:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA24855; Wed, 8 Mar 2000 17:21:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Brian Beattie Cc: current@FreeBSD.ORG Subject: Re: FreeBSD 4.0 release candidate #3 now available. In-reply-to: Your message of "Wed, 08 Mar 2000 16:45:39 PST." Date: Wed, 08 Mar 2000 17:21:11 -0800 Message-ID: <24852.952564871@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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-20000307-CURRENT > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-20000307-CURRENT > > > > With ISO images available from: > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-20000307-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 , > beattie@aracnet.com | standards based software. Users of Microsoft > beattie@aracnet.com | 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 17:31:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [216.99.193.36]) by hub.freebsd.org (Postfix) with ESMTP id F412C37B66F for ; Wed, 8 Mar 2000 17:31:46 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id RAA10163; Wed, 8 Mar 2000 17:31:48 -0800 Received: by shell1.aracnet.com (8.9.3) id RAA22725; Wed, 8 Mar 2000 17:34:02 -0800 Date: Wed, 8 Mar 2000 17:34:02 -0800 (PST) From: Brian Beattie To: Bob Willcox Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FreeBSD 4.0 release candidate #3 now available. In-Reply-To: <20000308191942.B10795@luke.immure.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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-20000307-CURRENT > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-20000307-CURRENT > > > > > > With ISO images available from: > > > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-20000307-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 207 641435648 Mar 8 22:18 install-alpha.iso -rw-r--r-- 1 2035 207 687331328 Mar 8 22:27 install-i386.iso 226 Transfer complete. > > -- > Bob Willcox What is wanted is not the will-to-believe, > bob@immure.com but the wish to find out, which is the exact > Austin, TX opposite. -- Bertrand Russell > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Beattie | This email was produced using professional quality, beattie@aracnet.com | standards based software. Users of Microsoft beattie@aracnet.com | 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 17:34: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id D1BA637B63E for ; Wed, 8 Mar 2000 17:34:00 -0800 (PST) (envelope-from brameld@twave.net) Received: from [12.21.241.164] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id qa052380 for ; Wed, 8 Mar 2000 20:33:38 -0500 Received: from Bozo_3.BozoLand.domain (localhost [127.0.0.1]) by Bozo_3.BozoLand.domain (8.9.3/8.9.3) with SMTP id UAA00561; Wed, 8 Mar 2000 20:33:36 -0500 (EST) (envelope-from brameld@twave.net) From: Walter Brameld To: Salvo Bartolotta , freebsd-current@FreeBSD.ORG Subject: Re: upgraded to -CURRENT (?) et al. III Date: Wed, 8 Mar 2000 20:33:05 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <20000309.350900@bartequi.ottodomain.org> In-Reply-To: <20000309.350900@bartequi.ottodomain.org> MIME-Version: 1.0 Message-Id: <0003082033360D.00362@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 17:38:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id E99B437B736 for ; Wed, 8 Mar 2000 17:38:56 -0800 (PST) (envelope-from bob@luke.immure.com) Received: (from bob@localhost) by luke.immure.com (8.9.3/8.9.3) id TAA11718; Wed, 8 Mar 2000 19:38:52 -0600 (CST) (envelope-from bob) Date: Wed, 8 Mar 2000 19:38:51 -0600 From: Bob Willcox To: Brian Beattie Cc: Bob Willcox , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FreeBSD 4.0 release candidate #3 now available. Message-ID: <20000308193851.C10795@luke.immure.com> Reply-To: Bob Willcox References: <20000308191942.B10795@luke.immure.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from beattie@aracnet.com on Wed, Mar 08, 2000 at 05:34:02PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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-20000307-CURRENT > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-20000307-CURRENT > > > > > > > > With ISO images available from: > > > > > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-20000307-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 207 641435648 Mar 8 22:18 install-alpha.iso > -rw-r--r-- 1 2035 207 687331328 Mar 8 22:27 install-i386.iso > 226 Transfer complete. > -- Bob Willcox What is wanted is not the will-to-believe, bob@immure.com but the wish to find out, which is the exact Austin, TX opposite. -- Bertrand Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 17:42:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from RedDust.BlueSky.net.au (reddust.bluesky.net.au [203.31.37.15]) by hub.freebsd.org (Postfix) with ESMTP id 7CE2237B73E for ; Wed, 8 Mar 2000 17:42:22 -0800 (PST) (envelope-from receiver@RedDust.BlueSky.net.au) Received: from localhost (receiver@localhost) by RedDust.BlueSky.net.au (8.9.3/8.9.3) with ESMTP id LAA24526 for ; Thu, 9 Mar 2000 11:43:32 +1000 (EST) (envelope-from receiver@RedDust.BlueSky.net.au) Date: Thu, 9 Mar 2000 11:43:32 +1000 (EST) From: Idea Receiver To: current@freebsd.org Subject: more question about "make release" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 18:27: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 7F0E637B71E for ; Wed, 8 Mar 2000 18:26:59 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id SAA78066 for current@freebsd.org; Wed, 8 Mar 2000 18:26:34 -0800 (PST) (envelope-from ulf) Date: Wed, 8 Mar 2000 18:26:34 -0800 From: Ulf Zimmermann To: current@freebsd.org Subject: 4.0 RC3 install problem from ftp.FreeBSD.org Message-ID: <20000308182634.G20583@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Says, it can't chdir into the 4.0-20000307-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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 18:57:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id E3CAC37B720; Wed, 8 Mar 2000 18:57:32 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id VAA30619; Wed, 8 Mar 2000 21:58:30 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Wed, 8 Mar 2000 21:58:30 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Boris Staeblow , jkh@freebsd.org Cc: Luigi Rizzo , freebsd-current@freebsd.org Subject: Re: bridging broken in -current AND -stable In-Reply-To: <20000309000454.A37304@dva.in-berlin.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Boris Staeblow wrote: > On Wed, Mar 08, 2000 at 11:15:23PM +0100, Luigi Rizzo wrote: >=20 > > >=20 > > > Is it possible that bridging is broken in -current and -stable? > >=20 > > 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. >=20 > Ooohhhhhhhh noooo! :-(( > The best nic=B4s all around are unsupported? ;) >=20 > > can you switch to some supported card ("ed" or "fxp") ? >=20 > Hmm, "ed" is lousy and "fxp" is too expensive for me now... >=20 > How great is the chance that good old dec is coming back? > I could help you testing your code... :) >=20 > 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=20 robert@fledge.watson.org 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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=092000/01/24 17:19:37=091.7 +++ if_dc.c=092000/03/08 18:15:55 @@ -122,6 +122,11 @@ =20 #include =20 +#include "opt_bdg.h" +#ifdef BRIDGE=20 +#include +#endif + #include /* for vtophys */ #include /* for vtophys */ #include /* for DELAY */ @@ -2099,14 +2104,30 @@ =09=09ifp->if_ipackets++; =09=09eh =3D mtod(m, struct ether_header *); =20 -=09=09/* -=09=09 * Handle BPF listeners. Let the BPF user see the packet, but -=09=09 * don't pass it up to the ether_input() layer unless it's +=09=09/* Handle BPF listeners. Let the BPF user see the packet */ +=09=09if (ifp->if_bpf) +=09=09=09bpf_mtap(ifp, m); + +#ifdef BRIDGE +=09=09if (do_bridge) { +=09=09=09struct ifnet *bdg_ifp ; +=09=09=09bdg_ifp =3D bridge_in(m); +=09=09=09if (bdg_ifp !=3D BDG_LOCAL && bdg_ifp !=3D BDG_DROP) +=09=09=09=09bdg_forward(&m, bdg_ifp); +=09=09=09if (((bdg_ifp !=3D BDG_LOCAL) && (bdg_ifp !=3D BDG_BCAST) &&=09= =09=09 (bdg_ifp !=3D BDG_MCAST)) || bdg_ifp =3D=3D BDG_DROP) { +=09=09=09=09m_freem(m); +=09=09=09=09continue; +=09=09=09} +=09=09} + +=09eh =3D mtod(m, struct ether_header *); +#endif + +=09=09/* Don't pass it up to the ether_input() layer unless it's =09=09 * a broadcast packet, multicast packet, matches our ethernet =09=09 * address or the interface is in promiscuous mode. =09=09 */ =09=09if (ifp->if_bpf) { -=09=09=09bpf_mtap(ifp, m); =09=09=09if (ifp->if_flags & IFF_PROMISC && =09=09=09=09(bcmp(eh->ether_dhost, sc->arpcom.ac_enaddr, =09=09=09=09 ETHER_ADDR_LEN) && To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 19:43:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from tranquility.net (ppp-port1-28.tranquility.net [206.152.118.28]) by hub.freebsd.org (Postfix) with ESMTP id 14B1937B690 for ; Wed, 8 Mar 2000 19:43:27 -0800 (PST) (envelope-from ishmael@tranquility.net) Received: from localhost (ishmael@localhost) by tranquility.net (8.9.3/8.9.3) with ESMTP id VAA00709 for ; Mon, 8 Mar 1999 21:44:28 -0600 (CST) (envelope-from ishmael@tranquility.net) Date: Mon, 8 Mar 1999 21:44:26 -0600 (CST) From: Ishmael To: current@FreeBSD.ORG Subject: building ports Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 19:55: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id 6922A37B757 for ; Wed, 8 Mar 2000 19:54:58 -0800 (PST) (envelope-from chris@aims.com.au) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au (8.9.3/8.9.3) with ESMTP id OAA15966 for ; Thu, 9 Mar 2000 14:54:55 +1100 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.0.0.R) for ; Thu, 09 Mar 2000 14:53:55 +1100 Reply-To: From: "Chris Knight" To: Subject: RE: building ports Date: Thu, 9 Mar 2000 14:53:53 +1100 Message-ID: <000901bf897b$16bc86e0$020aa8c0@aims.private> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal X-MDaemon-Deliver-To: freebsd-current@FreeBSD.ORG X-Return-Path: chris@aims.com.au X-MDRcpt-To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Ishmael > Sent: Tuesday, 9 March 1999 14:44 > To: current@FreeBSD.ORG > 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 majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 20: 0:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 07A6F37B742 for ; Wed, 8 Mar 2000 20:00:41 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id UAA14615; Wed, 8 Mar 2000 20:00:40 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id UAA39926; Wed, 8 Mar 2000 20:00:39 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 8 Mar 2000 20:00:39 -0800 (PST) Message-Id: <200003090400.UAA39926@vashon.polstra.com> To: dmmiller@cvzoom.net Subject: Re: More "ld-elf.so.1: assert failed" messages In-Reply-To: <38C68F72.4070405@cvzoom.net> References: <38BA5751.2396AE87@cvzoom.net> <38C5A975.957756C4@cvzoom.net> <200003081702.JAA39397@vashon.polstra.com> <38C68F72.4070405@cvzoom.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <38C68F72.4070405@cvzoom.net>, Donn Miller 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 a way to do it using alloca(). This takes us back to the traditional state of things, where lazy binding (the common case) is reentrant but dlopen() is not. I could make the default locking methods no-ops and we'd be back to the situation we traditionally had. That's what I think we should probably do. For multi-threaded applications this would work almost all the time. It would fail only if one thread was in dlopen() when another thread either called dlopen() itself or did something that made the lazy binding code kick in. Applications are smart enough to avoid reentering dlopen, but short of suspending all other threads they really don't have a way to prevent lazy binding from happening while a separate thread is inside dlopen. So applications could still fail, but it would be very rare and it would be nothing new -- that risk has been with us all along, even before I started messing with this stuff. Applications whose thread packages called dllockinit() wouldn't have problems under any circumstances, of course. I think this would be a decent solution. But past experience shows that the N threads packages out there can tend to surprise me. Do you think I should just leave it alone until after 4.0 is released, or is wine important enough that I should try to fix it even though it's a bit risky? The other possibility would be to fix the wine port so it calls dllockinit() to set up locking. I don't know for sure how hard that would be, but it's probably a feasible solution. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 20: 5:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id B98B137B7E7 for ; Wed, 8 Mar 2000 20:05:16 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for current@freebsd.org id 12SuCJ-0007Ve-00; Thu, 9 Mar 2000 04:05:15 +0000 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id EAA03996 for current@freebsd.org; Thu, 9 Mar 2000 04:05:15 GMT (envelope-from jcm) Message-ID: <20000309040515.B3975@freebsd-uk.eu.org> Date: Thu, 9 Mar 2000 04:05:15 +0000 From: J McKitrick To: current@freebsd.org Subject: Paralle mode ZIP support Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 21:38:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 6EE8137B6CF for ; Wed, 8 Mar 2000 21:37:11 -0800 (PST) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.2/8.9.3) with UUCP id GAA88721 for freebsd-current@FreeBSD.ORG; Thu, 9 Mar 2000 06:36:51 +0100 (CET) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id GAA30325 for ; Thu, 9 Mar 2000 06:36:41 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <007d01bf88c0$717ed8a0$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: Subject: poptop+ppp, ok in current, not stable Date: Wed, 8 Mar 2000 06:37:23 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to use MS-VPN using poptop. (pptpd) It works nicely from home to my current at home, but not to my stable = at work. I have copied /etc/ppp/ppp.conf, /etc/ppp/ppp.secret and = /usr/local/etc/pptpd.conf from the current to the stable machine. When logging on to the stable, I get this in messages: Mar 9 06:25:50 ns pptpd[88343]: GRE: = read(fd=3D5,buffer=3D804d000,len=3D81 96) from PTY failed: status =3D 0 error =3D No error Mar 9 06:25:50 ns pptpd[88343]: CTRL: PTY read or GRE write failed = (pty,gre)=3D(5 ,4) ppp.log says repeately: Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: ACFCOMP[2] Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: PROTOCOMP[2] Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: ACCMAP[6] 0x00000000 Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: MRU[4] 1500 Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: MAGICNUM[6] 0x469c1c68 Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: deflink: State change Stopped = --> Req-Sent Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: deflink: SendConfigReq(1) = state =3D Req-Sent Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: ACFCOMP[2] Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: PROTOCOMP[2] Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: ACCMAP[6] 0x00000000 Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: MRU[4] 1500 Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: MAGICNUM[6] 0x469c1c68 Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Mar 9 06:25:41 ns ppp[88344]: tun0: LCP: deflink: SendConfigReq(1) = state =3D Req-Sent The windows machine just says "Verifying username and password". I've tried chap instead of pap with no difference. The stable is make-world'ed march 1. What could I be missing? Should I just wait to 4.0 gets released and upgrade at work?=20 Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 21:44:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id F2C1737B7D7 for ; Wed, 8 Mar 2000 21:44:46 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id AAA31111 for ; Thu, 9 Mar 2000 00:46:00 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Thu, 9 Mar 2000 00:46:00 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-current@freebsd.org Subject: tcpdump IPv4 warning (gratuitous) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a quicky. Since we now support IPv6 by default, you can imagine environments where you have an interface and IPv4 is not in use. My tcpdump is from a rather elderly 4.0, so this may be fixed already, but: # tcpdump -eni bridge0 tcpdump: WARNING: bridge0: no IPv4 address assigned tcpdump: listening on bridge0 That seems a litte gratuitous. I'm quite aware that there is no IPv4 address assigned--that was intentional :-). (This is a bridge snooping interface--I don't want an IPv4 address) If this is already fixed, nevermind.. :-) Robert N M Watson robert@fledge.watson.org 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 22:28: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 5A82837B6A3 for ; Wed, 8 Mar 2000 22:28:02 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id HAA69718; Thu, 9 Mar 2000 07:26:52 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200003090626.HAA69718@info.iet.unipi.it> Subject: Re: bridging broken in -current AND -stable In-Reply-To: <20000309000454.A37304@dva.in-berlin.de> from Boris Staeblow at "Mar 9, 2000 00:04:54 am" To: Boris Staeblow Date: Thu, 9 Mar 2000 07:26:52 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > 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. > > Ooohhhhhhhh noooo! :-(( > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 8 22:49:14 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id D03F137B6D8; Wed, 8 Mar 2000 22:49:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id CE8902E8158 for ; Wed, 8 Mar 2000 22:49:12 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 8 Mar 2000 22:49:12 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: Two /var/log files not created Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Something else I forgot when I installed 4.0: there are two files referenced in /etc/syslog.conf which don't exist in a fresh install, so syslogd complains about them at boot: /var/log/cron /var/log/security These should probably be created as empty files at install-time - they were only added in the last few months of 1999. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 0:13:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from m3.cs.berkeley.edu (m3.CS.Berkeley.EDU [128.32.45.179]) by hub.freebsd.org (Postfix) with ESMTP id A8B9837B68B for ; Thu, 9 Mar 2000 00:13:24 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca1-183.ix.netcom.com [209.109.232.183]) by m3.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id AAA23892; Thu, 9 Mar 2000 00:13:22 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id AAA59971; Thu, 9 Mar 2000 00:13:18 -0800 (PST) To: Ishmael Cc: current@FreeBSD.ORG Subject: Re: building ports References: From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 09 Mar 2000 00:13:14 -0800 In-Reply-To: Ishmael's message of "Mon, 8 Mar 1999 21:44:26 -0600 (CST)" Message-ID: Lines: 14 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Ishmael * 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 You just did make world and still got this error? That's not supposed to happen. What do > ls -l /var/db/port.mkversion > cat /var/db/port.mkversion say? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 0:20:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 9B75637B68A; Thu, 9 Mar 2000 00:20:40 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12SyAs-000LCd-00; Thu, 09 Mar 2000 10:20:02 +0200 From: Sheldon Hearn To: Doug Barton Cc: R Joseph Wright , freebsd-current@FreeBSD.ORG, Kris Kennaway Subject: Re: no openssh after build In-reply-to: Your message of "Wed, 08 Mar 2000 09:56:56 PST." <38C69468.13064438@gorean.org> Date: Thu, 09 Mar 2000 10:20:01 +0200 Message-ID: <81506.952590001@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 08 Mar 2000 09:56:56 PST, Doug Barton wrote: > 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. Looks like mergemaster is much cleverer than I thought. Being called Mr Barton certainly _is_ a compliment! :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 0:28:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from 001.co.jp (ej1.001.co.jp [210.146.252.72]) by hub.freebsd.org (Postfix) with ESMTP id BD31D37B507; Thu, 9 Mar 2000 00:28:03 -0800 (PST) (envelope-from mic@001.co.jp) Received: from ej1.001.co.jp.001.co.jp ([192.168.100.33]) by 001.co.jp (8.8.8/3.6W:Mon Mar 16 22:26:19 JST 1998) with SMTP id QAA24572; Thu, 9 Mar 2000 16:13:41 +0900 (JST) Message-ID: <008401bf8999$57235c40$2164a8c0@ej1.001.co.jp.001.co.jp> From: "=?iso-2022-jp?B?GyRCJTAlbCE8JUglOCVjITwlSyE8GyhC?=" To: Subject: =?iso-2022-jp?B?GyRCJTAlbCE8JUglOCVjITwlSyE8GyhCTkVXUxskQiFKGyhCMDM=?= =?iso-2022-jp?B?MDkxMDA0GyRCIUsbKEI=?= Date: Thu, 9 Mar 2000 16:29:07 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $B!!!!(B $B!!!!!!%0%l!<%H%8%c!<%K!<(BNEWS $BFMA3$N%a!<%kAw?.$9$k;v$r$*5v$7$/$@$5$$!#(B $B9%I>$KIU$-!!Bh#2CF!*!*?7=U%-%c%s%Z!<%s$G$9!#(B $B!A%@%$%P!e$2$F$*$j$^$9!#(B $B3t<02q; Thu, 9 Mar 2000 00:48:56 -0800 (PST) (envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de) Received: from hirsch.in-berlin.de (root@hirsch.in-berlin.de [192.109.42.6]) by gnu.IN-Berlin.DE (8.9.3/8.9.3) with ESMTP id JAA05229; Thu, 9 Mar 2000 09:48:53 +0100 (CET) (envelope-from dva.in-berlin.de!balu@hirsch.in-berlin.de) Received: by hirsch.in-berlin.de (Smail3.2) id ; Thu, 9 Mar 2000 09:48:50 +0100 (CET) Received: by dva.in-berlin.de (Postfix, from userid 200) id CE9EA10E00; Thu, 9 Mar 2000 09:46:03 +0100 (CET) Date: Thu, 9 Mar 2000 09:46:03 +0100 From: Boris Staeblow To: Luigi Rizzo Cc: freebsd-current@FreeBSD.ORG Subject: Re: bridging broken in -current AND -stable Message-ID: <20000309094603.A66667@dva.in-berlin.de> References: <20000309000454.A37304@dva.in-berlin.de> <200003090626.HAA69718@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003090626.HAA69718@info.iet.unipi.it>; from luigi@info.iet.unipi.it on Thu, Mar 09, 2000 at 07:26:52AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 09, 2000 at 07:26:52AM +0100, Luigi Rizzo wrote: > 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. For future investments: which nics do you recommend? (stable driver, speed...) fxp? > 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. ok. Which nics are capable for bridging now in -current? ed, fxp, ...? To prevent the page faults in the upcomping release the bridging support should be disabled in if_de. Maybe the manpage should note the real supported nics. Boris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 1:20:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 1DFB737B74C for ; Thu, 9 Mar 2000 01:20:27 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by jfh00.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id KAA20144; Thu, 9 Mar 2000 10:20:21 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <38C76CD5.F2E86F64@fernuni-hagen.de> Date: Thu, 09 Mar 2000 10:20:21 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: de-DE, German/Germany, en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: kdm display manager working anywhere with current? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found no way to get kdm to work, it dumps core in a qt string find routine. wdm works kind of (the window manager menu is buggy but repairable). -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 1:35:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 532D637B6B2 for ; Thu, 9 Mar 2000 01:35:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA13463; Thu, 9 Mar 2000 01:33:51 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: ulf@Alameda.net Cc: current@FreeBSD.ORG Subject: Re: 4.0 RC3 install problem from ftp.FreeBSD.org In-reply-to: Your message of "Wed, 08 Mar 2000 18:26:34 PST." <20000308182634.G20583@PacHell.TelcoSucks.org> Date: Thu, 09 Mar 2000 01:33:51 -0800 Message-ID: <13460.952594431@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good point, I forgot the link. Fixed! - Jordan > Says, it can't chdir into the 4.0-20000307-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 majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 1:57:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8638E37B535 for ; Thu, 9 Mar 2000 01:57:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA13614; Thu, 9 Mar 2000 01:56:00 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Polstra Cc: dmmiller@cvzoom.net, current@FreeBSD.ORG Subject: Re: More "ld-elf.so.1: assert failed" messages In-reply-to: Your message of "Wed, 08 Mar 2000 20:00:39 PST." <200003090400.UAA39926@vashon.polstra.com> Date: Thu, 09 Mar 2000 01:55:59 -0800 Message-ID: <13611.952595759@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The other possibility would be to fix the wine port so it calls > dllockinit() to set up locking. I don't know for sure how hard that > would be, but it's probably a feasible solution. To be honest, I'd be the most comfortable with this solution but also trust John's skills with the linker (certainly far more than I trust mine :) to say that whatever he's comfortable with, I'm comfortable with. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 1:57:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id DB93637B535 for ; Thu, 9 Mar 2000 01:57:41 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id KAA70395; Thu, 9 Mar 2000 10:56:19 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200003090956.KAA70395@info.iet.unipi.it> Subject: Re: bridging broken in -current AND -stable In-Reply-To: <20000309094603.A66667@dva.in-berlin.de> from Boris Staeblow at "Mar 9, 2000 09:46:03 am" To: Boris Staeblow Date: Thu, 9 Mar 2000 10:56:19 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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. > > For future investments: which nics do you recommend? > (stable driver, speed...) fxp? probably, yes, though the whole bunch of drivers contributed by Bill Paul look interesting as well (i have no idea on how good is the hardware, e.g. the rl 8139 is not such a good card). > Which nics are capable for bridging now in -current? ed, fxp, ...? and 'rl' i think. > To prevent the page faults in the upcomping release the bridging support > should be disabled in if_de. > Maybe the manpage should note the real supported nics. wish i had more time. cheers luigi > > Boris > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 3: 6:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (hda.bicnet.net [208.220.68.243]) by hub.freebsd.org (Postfix) with ESMTP id BC66C37B6D2 for ; Thu, 9 Mar 2000 03:06:07 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id GAA65909; Thu, 9 Mar 2000 06:09:55 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200003091109.GAA65909@hda.hda.com> Subject: Re: current lockups In-Reply-To: <00Mar9.114816est.115256@border.alcanet.com.au> from Peter Jeremy at "Mar 9, 2000 11:48:14 am" To: Peter Jeremy Date: Thu, 9 Mar 2000 06:09:55 -0500 (EST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 2000-Mar-09 10:05:21 +1100, Peter Dufault wrote: > >There's no difference between rtprio and P1003.1B scheduling other than > >the name. rtprio is the same as P1003.1B "SCHED_RR". > > I wasn't aware of that. > > >I'd like to remove the rtprio call from ntpd. I think we ought to do > >it now before 4.0 ships. > > Given there is a known a priority inversion bug related to realtime > (or idle) scheduling, it would seem wise not to use it in any system > utilities. The relevant patch would appear to be (untested): > > --- /usr/src/usr.sbin/ntp/config.h Tue Feb 1 13:56:05 2000 > +++ /tmp/config.h Thu Mar 9 11:46:11 2000 You have to do something in the "./configure" stuff. Hopefully someone in the know can suggest the "--with-no-foobar" option needed on the command line so I don't have to wade into it. Autoconfiguring POSIX realtime is a bad, bad idea because: 1. You don't know if it is available in all environments; 2. You don't know who is allowed to use it; 3. You don't know what the heck it does. It decidedly does not mean "run as fast as you can". Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 3:32:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from tranquility.net (ppp-port3-56.tranquility.net [206.152.119.152]) by hub.freebsd.org (Postfix) with ESMTP id 5FFEF37B69C; Thu, 9 Mar 2000 03:32:19 -0800 (PST) (envelope-from ishmael@tranquility.net) Received: from localhost (ishmael@localhost) by tranquility.net (8.9.3/8.9.3) with ESMTP id FAA01757; Tue, 9 Mar 1999 05:33:26 -0600 (CST) (envelope-from ishmael@tranquility.net) Date: Tue, 9 Mar 1999 05:33:25 -0600 (CST) From: Ishmael To: Satoshi - Ports Wraith - Asami Cc: current@FreeBSD.ORG Subject: Re: building ports In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well, on the advice of someone, i manually edited these files changing the date in them to 20000201, before changing it it was 19990308. i dunno if its significant, but i rebuilt using make buildworld, make installworld. and i did run mergemaster afterwards. what date is supposed to be in this file btw? Jeremy > You just did make world and still got this error? That's not supposed > to happen. What do > > > ls -l /var/db/port.mkversion > > cat /var/db/port.mkversion > > say? > > Satoshi > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 3:36: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcat.heimat.gr.jp (pcat.heimat.gr.jp [211.0.53.98]) by hub.freebsd.org (Postfix) with ESMTP id 2E68537B63F for ; Thu, 9 Mar 2000 03:35:54 -0800 (PST) (envelope-from nakaji@tutrp.tut.ac.jp) Received: from xa12.heimat.gr.jp (xa12.heimat.gr.jp [211.0.53.97]) by pcat.heimat.gr.jp (8.9.3/3.7W) with ESMTP id UAA51699; Thu, 9 Mar 2000 20:35:50 +0900 (JST) To: "Sean O'Connell" Cc: current@freebsd.org Subject: Re: XDM login using sessreg and last, uptime, w and so on... References: <86g0u2vpz3.fsf@xa12.heimat.gr.jp> <86zosaxvzn.fsf@xa12.heimat.gr.jp> <20000307235759.A3636@stat.Duke.EDU> <86r9dloffo.fsf@xa12.heimat.gr.jp> <20000308123340.F2878@stat.Duke.EDU> MIME-Version: 1.0 (generated by REMI 1.14.1 - =?ISO-8859-4?Q?=22Mushigawa=F2?= =?ISO-8859-4?Q?sugi=22?=) Content-Type: text/plain; charset=US-ASCII From: NAKAJI Hiroyuki Date: 09 Mar 2000 20:35:49 +0900 In-Reply-To: <20000308123340.F2878@stat.Duke.EDU> (Sean O'Connell's message of "Wed, 8 Mar 2000 12:33:40 -0500") Message-ID: <86ln3swf3e.fsf@xa12.heimat.gr.jp> Lines: 38 User-Agent: T-gnus/6.14.1 (based on Gnus v5.8.3) (revision 12) REMI/1.14.1 (=?ISO-8859-4?Q?Mushigawa=F2sugi?=) FLIM/1.13.2 (Kasanui) APEL/10.2 Emacs/20.5 (i386--freebsd) MULE/4.0 (HANANOEN) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> In <20000308123340.F2878@stat.Duke.EDU> >>>>> "Sean O'Connell" wrote: > On FreeBSD it was successful and there seems no problem. Sean> One out of two is not bad :) I think so too. :-) Sean> Could your path be set in such a way that it is exec'ing 3.X Sean> versions of fileutils or finger or something like that in Sean> /usr/local/bin rather than updated ones in /usr hierarchy. No. These tools are all in /usr/bin. Sean> Did you run mergemaster on /etc and/or update all the various Sean> rc files? Yes. I have just run mergemaster and reboot the system. Sean> The /usr/X11R6/bin/X symlink really points to an updated Sean> XF86_xxxx like you didn't switch for using XF86_S3 to XF86_SVGA Sean> (only built this) but the symlink for X is still pointing to Sean> XF86_S3. I'm using X-TT server on both FreeBSD and FreeBSD(98). This morning, I recompiled X-TT of FreeBSD(98) and there still is 'w: /dev/:0: No such file or directory'. X is properly linked to XF98_MGA.xtt. Sean> Curious... love a good mystery. Yes, this is a mystery but not so serious... Ok, I'll ask about this problem to FreeBSD(98)'s mailing list. It may be pc98's problem... Thank you all very much for your help. -- NAKAJI Hiroyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 4:32:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from www.menzor.dk (themoonismadeofgreenchease.dk [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id C6B9037B61E for ; Thu, 9 Mar 2000 04:32:27 -0800 (PST) (envelope-from ml@seeberg.dk) Received: from sos (userhost.cma.dk [130.228.127.200]) by www.menzor.dk (8.8.8/8.8.8) with SMTP id NAA04900 for ; Thu, 9 Mar 2000 13:52:24 +0100 (CET) (envelope-from ml@seeberg.dk) Message-ID: <000901bf89c4$0948e230$deff58c1@sos> Reply-To: "Morten Seeberg" From: "Morten Seeberg" To: Subject: =?iso-8859-1?Q?RC3-ISO_doesn=B4t_recognize_Thinkpad_600E_CD-ROM_Drive?= Date: Thu, 9 Mar 2000 13:36:03 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, when booting off the RC3 ISO, I the the error: Can´t work out which disk we are booting from. Guessed BIOS device 0x8b not found by probes, defaulting to disk0: The ISO only found my floppy as disk0 and my FAT partition as disk1. Not the CD-ROM drive it booted off. It works just fine when booting off the floppies. But if the RC3-ISO CD is in the Cd-ROM while booting off the disks I still get the above error, although everything works fine, because I boot off the floppies. It´s like the bootloader cannot recognize the CD-ROM drive, but the GENERIC can. I have a IBM Thinkpad 600E, with the DVD drive. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /\/\orten $eeberg, Systems Consultant @ Merkantildata - Enterprise Solutions #echo 'System Administrators suck :)' > /dev/console To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 5:54:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from NOC.cs.uu.nl (magic.cs.uu.nl [131.211.80.22]) by hub.freebsd.org (Postfix) with ESMTP id 5063A37B6CF for ; Thu, 9 Mar 2000 05:54:53 -0800 (PST) (envelope-from edwin@cs.uu.nl) Received: by NOC.cs.uu.nl (Postfix, from userid 164) id 29F593E8C2; Thu, 9 Mar 2000 14:54:48 +0100 (MET) Date: Thu, 9 Mar 2000 14:54:48 +0100 From: Edwin Kremer To: Ishmael Cc: current@FreeBSD.ORG Subject: Re: building ports Message-ID: <20000309145448.C23820@cs.uu.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: ; from ishmael@tranquility.net on Mon, Mar 08, 1999 at 09:44:26PM -0600 X-Organization: Department of Computer Science, Utrecht University X-Phone: +31-30-2534104 (telefax: +31-30-2513791) X-PGP-DSS-Key: http://horowitz.surfnet.nl:11371/pks/lookup?op=get&search=0x33E1E549 X-PGP-RSA-Key: http://horowitz.surfnet.nl:11371/pks/lookup?op=get&search=0xAD4B1845 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 08, 1999 at 09:44:26PM -0600, Ishmael wrote: : Your system is too old to use this bsd.port.mk. According to the mail headers, your system clock is about one year behind actual time. That might have screwed up the `make'... Best regards, -- Edwin H. Kremer, senior systems- and network administrator. Dept. of Computer Science, Utrecht University, The Netherlands [WHOIS: ehk3] -------------------- http://www.cs.uu.nl/people/edwin/ ----------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 7: 6:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id ECC0B37B6BD for ; Thu, 9 Mar 2000 07:06:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id HAA01424; Thu, 9 Mar 2000 07:05:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Poul-Henning Kamp Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: Please review: fdisk -e -> -I In-reply-to: Your message of "Fri, 03 Mar 2000 00:45:46 +0100." <693.952040746@critter.freebsd.dk> Date: Thu, 09 Mar 2000 07:05:06 -0800 Message-ID: <1421.952614306@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK! > > You have my OK to change the option, but you'll need Jordans > OK to commit it. > > Poul-Henning > > In message <200003022033.NAA17898@harmony.village.org>, Warner Losh writes: > > > >Given that OpenBSD had the -e flag to fdisk first, and that it means > >edit there and that disklabel -e means edit, I'd like to apply the > >following patch to -current before it becomes 4.0. If we wait, we'll > >have compatibility problems. Right now it is too easy to shoot > >yourself in the foot with this. > > > >When this was hashed out here, the idea was met with wide spread > >support, even fiven the advanced nature of the freeze. I take that > >support to mean that this is something that would be a good idea to do > >for 4.0. > > > >Comments? > > > >Warner > > > >Index: fdisk.8 > >=================================================================== > >RCS file: /home/imp/FreeBSD/CVS/src/sbin/i386/fdisk/fdisk.8,v > >retrieving revision 1.16 > >diff -u -r1.16 fdisk.8 > >--- fdisk.8 1999/08/28 00:13:01 1.16 > >+++ fdisk.8 2000/03/02 20:29:12 > >@@ -8,7 +8,7 @@ > > .Nd PC partition table maintenance program > > .Sh SYNOPSIS > > .Nm fdisk > >-.Op Fl Baeitu > >+.Op Fl BIaitu > > .Op Fl b Ar bootcode > > .Op Fl 1234 > > .Op Ar disk > >@@ -62,7 +62,7 @@ > > if > > .Fl f > > is given. > >-.It Fl e > >+.It Fl I > > Initialize the contents of sector 0 with one FreeBSD slice covering the ent ire disk. > > .It Fl f Ar configfile > > Set partition values using the file > >Index: fdisk.c > >=================================================================== > >RCS file: /home/imp/FreeBSD/CVS/src/sbin/i386/fdisk/fdisk.c,v > >retrieving revision 1.34 > >diff -u -r1.34 fdisk.c > >--- fdisk.c 2000/02/11 11:25:23 1.34 > >+++ fdisk.c 2000/03/02 20:31:56 > >@@ -120,7 +120,7 @@ > > static int B_flag = 0; /* replace boot code */ > > static int a_flag = 0; /* set active partition */ > > static char *b_flag = NULL; /* path to boot code */ > >-static int e_flag = 0; /* use entire disk for FreeBSD */ > >+static int I_flag = 0; /* use entire disk for FreeBSD */ > > static int i_flag = 0; /* replace partition data */ > > static int u_flag = 0; /* update partition data */ > > static int t_flag = 0; /* test only, if f_flag is given */ > >@@ -216,7 +216,7 @@ > > { > > int c, i; > > > >- while ((c = getopt(argc, argv, "Bab:ef:ituv1234")) != -1) > >+ while ((c = getopt(argc, argv, "BIab:f:ituv1234")) != -1) > > switch (c) { > > case 'B': > > B_flag = 1; > >@@ -227,8 +227,8 @@ > > case 'b': > > b_flag = optarg; > > break; > >- case 'e': > >- e_flag = 1; > >+ case 'I': > >+ I_flag = 1; > > break; > > case 'f': > > f_flag = optarg; > >@@ -292,7 +292,7 @@ > > > > printf("******* Working on device %s *******\n",disk); > > > >- if (e_flag) > >+ if (I_flag) > > { > > struct dos_partition *partp; > > > >@@ -648,7 +648,7 @@ > > if ( !(st.st_mode & S_IFCHR) ) > > warnx("device %s is not character special", disk); > > if ((fd = open(disk, > >- a_flag || e_flag || B_flag || u_flag ? O_RDWR : O_RDONLY)) == -1) { > >+ a_flag || I_flag || B_flag || u_flag ? O_RDWR : O_RDONLY)) == -1) { > > if(errno == ENXIO) > > return -2; > > warnx("can't open device %s", disk); > > > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 8:31: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 91A7137B79A for ; Thu, 9 Mar 2000 08:30:59 -0800 (PST) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.2/8.9.3) with UUCP id RAA07722 for freebsd-current@FreeBSD.ORG; Thu, 9 Mar 2000 17:30:53 +0100 (CET) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id PAA34283; Thu, 9 Mar 2000 15:11:39 +0100 (CET) (envelope-from leifn@neland.dk) Date: Thu, 9 Mar 2000 15:11:39 +0100 (CET) From: Leif Neland To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: poptop+ppp, ok in current, not stable In-Reply-To: <007d01bf88c0$717ed8a0$0e00a8c0@neland.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Mar 2000, Leif Neland wrote: > I'm trying to use MS-VPN using poptop. (pptpd) > > It works nicely from home to my current at home, but not to my stable at work. > Followup: From work to current at home fails too: > ppp.log says repeately: > > Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: ACFCOMP[2] > Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: PROTOCOMP[2] > Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: ACCMAP[6] 0x00000000 > Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: MRU[4] 1500 > Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: MAGICNUM[6] 0x469c1c68 > Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: deflink: State change Stopped --> Req-Sent > Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: deflink: SendConfigReq(1) state = Req-Sent > Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: ACFCOMP[2] > Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: PROTOCOMP[2] > Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: ACCMAP[6] 0x00000000 > Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: MRU[4] 1500 > Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: MAGICNUM[6] 0x469c1c68 > Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) > Mar 9 06:25:41 ns ppp[88344]: tun0: LCP: deflink: SendConfigReq(1) state = Req-Sent > > The windows machine just says "Verifying username and password". > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 8:45:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8ACF737B6F6 for ; Thu, 9 Mar 2000 08:45:52 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id IAA17607; Thu, 9 Mar 2000 08:45:51 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id IAA40726; Thu, 9 Mar 2000 08:45:50 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 9 Mar 2000 08:45:50 -0800 (PST) Message-Id: <200003091645.IAA40726@vashon.polstra.com> To: jkh@zippy.cdrom.com Subject: Re: More "ld-elf.so.1: assert failed" messages In-Reply-To: <13611.952595759@zippy.cdrom.com> References: <13611.952595759@zippy.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <13611.952595759@zippy.cdrom.com>, Jordan K. Hubbard wrote: > > The other possibility would be to fix the wine port so it calls > > dllockinit() to set up locking. I don't know for sure how hard that > > would be, but it's probably a feasible solution. > > To be honest, I'd be the most comfortable with this solution Me too, for 4.0. Given Donn's reports of trouble with my patches, I think the timing is just wrong to try and do anything major with the dynamic linker between now and Monday. It's too hard to test it. All the troublesome ports are _huge_ (Mozilla, Wine, ...), and the failures are timing-dependent and not so easy to reproduce. Obviously I'll strive to fix the remaining problems after 4.0 has been tagged. As far as I know, Wine is the only port that has problems with the version of the dynamic linker that's in -current at present. I've looked into adding the dllockinit() stuff to Wine, but could use some help from somebody who knows its internals better. I found the threads primitives, etc., but am not so sure where to place the dllockinit() call. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 8:53:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from ws-ilmar.ints.ru (ws-ilmar.ints.ru [194.67.173.16]) by hub.freebsd.org (Postfix) with ESMTP id 41B9337B73F for ; Thu, 9 Mar 2000 08:53:24 -0800 (PST) (envelope-from ilmar@ints.ru) Received: from localhost (localhost [127.0.0.1]) by ws-ilmar.ints.ru (8.9.3/8.9.3) with ESMTP id TAA86045; Thu, 9 Mar 2000 19:53:03 +0300 (MSK) Date: Thu, 9 Mar 2000 19:53:03 +0300 (MSK) From: "Ilmar S. Habibulin" To: "F. Heinrichmeyer" Cc: "freebsd-current@FreeBSD.ORG" Subject: Re: kdm display manager working anywhere with current? In-Reply-To: <38C76CD5.F2E86F64@fernuni-hagen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, F. Heinrichmeyer wrote: > I found no way to get kdm to work, it dumps core in a qt string find > routine. wdm works kind of (the window manager menu is buggy but > repairable). three day cvsup - kdm works fine. konqueror - that is the problem. :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 8:57:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (f204.law7.hotmail.com [216.33.237.204]) by hub.freebsd.org (Postfix) with SMTP id 0486537B6A9 for ; Thu, 9 Mar 2000 08:57:08 -0800 (PST) (envelope-from jmd526@hotmail.com) Received: (qmail 82046 invoked by uid 0); 9 Mar 2000 16:57:06 -0000 Message-ID: <20000309165706.82045.qmail@hotmail.com> Received: from 209.220.228.2 by www.hotmail.com with HTTP; Thu, 09 Mar 2000 08:57:06 PST X-Originating-IP: [209.220.228.2] From: "John Daniels" To: freebsd-current@freebsd.org Subject: FBSD4.0-RC3 install Date: Thu, 09 Mar 2000 11:57:06 EST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I did an install of 4.0-RC3 last night and found the following: 1: Unable to transfer the local distribution from ftp://current.freebsd.org/pub/FreeBSD/Snapshots/i386 2: Unable to transfer the X9set distribution from ftp://current.freebsd.org/pub/FreeBSD/Snapshots/i386 3: The Ports collection took about 85 MB, not about 70 MB 4: The first option for configuring X in full screen graphic mode, which requires VGA16, did not work. So I picked option #3, which seemed like the next best option because it too mentioned a full-screen configuration. (I skipped over option #2: the shell-based configuration because the description said that that was more difficult -- the description doesn't mention the pros or cons of option #3.) Bad move. The next screen I saw was the next setup item (Ports). I thought that I had lost the opportunity to setup X but later I returned to the "Main Menu" where I could choose to setup X. 5: Something similar happened when I came to the account setup screen. Option #1 was to "Exit this menu (back to previous) but instead of going *back*, it seemed to go forward, bringing me to the screen to set password for root. 6: After Install was complete and a reboot, X would not start, when I tried 'startx', I got: /usr/libexec/ld-elf.so.1: shared object "libXThrStub.so.6" not found 7: I couldn't find PostgreSQL as a port (under 'database') during the install. It's definitely *there* in the installed Ports collection, though. Are other ports missing (it didn't seem like there were 3100+). Are the number of ports for the install purposely limited? QUESTIONS 1-Is #1 just a localization which is unnecessary for USA? 2-Are #2,#4, and #6 related? Was X9set missing in the distro? 3-Is it possible to include more documentation during install or online? I think there are several possible 'gotcha's' that may be avoided. For examples see above, but also: I had used FIPS to create a new partition before the install but had not deleted it. In the Install program, the type of this partition was "6" and the description was "FAT." The install program allowed me to change the type to ??? (the FreeBSD type) and the description now said "FreeBSD." But I hesitated to continue because the description explictly said that "unused" was to be changed to "FreeBSD." I exited the install, went back to Win95, fired up DOSCMD and used fdisk to delete the partition. Would the install have worked if I hadn't deleted the partition? or would it have damaged something? 4-How can I get 'startx' to work now? John ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 9: 1: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9959B37B895 for ; Thu, 9 Mar 2000 09:00:58 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA02612; Thu, 9 Mar 2000 09:01:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "John Daniels" Cc: freebsd-current@FreeBSD.ORG Subject: Re: FBSD4.0-RC3 install In-reply-to: Your message of "Thu, 09 Mar 2000 11:57:06 EST." <20000309165706.82045.qmail@hotmail.com> Date: Thu, 09 Mar 2000 09:01:37 -0800 Message-ID: <2609.952621297@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi: > I did an install of 4.0-RC3 last night and found the following: > > 1: Unable to transfer the local distribution from > ftp://current.freebsd.org/pub/FreeBSD/Snapshots/i386 Because it's not there. I listed the URLs I listed *very specifically* and that is the ONLY location you can get this from. Just ignore current.freebsd.org for the purposes of these release candidates please. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 9: 2: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (f198.law7.hotmail.com [216.33.237.198]) by hub.freebsd.org (Postfix) with SMTP id A954C37B74C for ; Thu, 9 Mar 2000 09:02:02 -0800 (PST) (envelope-from jmd526@hotmail.com) Received: (qmail 73844 invoked by uid 0); 9 Mar 2000 17:02:01 -0000 Message-ID: <20000309170201.73843.qmail@hotmail.com> Received: from 209.220.228.2 by www.hotmail.com with HTTP; Thu, 09 Mar 2000 09:02:01 PST X-Originating-IP: [209.220.228.2] From: "John Daniels" To: freebsd-current@freebsd.org Subject: RE: FBSD 4.0-RC3 install Date: Thu, 09 Mar 2000 12:02:01 EST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I should have added that I installed Gnome and Afterstep and later (before end of install), I also got IceWM from Ports. Is X confused about which WM to use? John ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 10:24:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (f95.law7.hotmail.com [216.33.237.95]) by hub.freebsd.org (Postfix) with SMTP id C652837B7B8 for ; Thu, 9 Mar 2000 10:24:13 -0800 (PST) (envelope-from jmd526@hotmail.com) Received: (qmail 45425 invoked by uid 0); 9 Mar 2000 18:24:10 -0000 Message-ID: <20000309182410.45424.qmail@hotmail.com> Received: from 209.220.228.2 by www.hotmail.com with HTTP; Thu, 09 Mar 2000 10:24:10 PST X-Originating-IP: [209.220.228.2] From: "John Daniels" To: jkh@zippy.cdrom.com Cc: freebsd-current@freebsd.org Subject: Re: FBSD4.0-RC3 install Date: Thu, 09 Mar 2000 13:24:10 EST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I got the install floppies from the ftp directory that you listed. When the install came to a point where it asked for the ftp site to get the distribution, it listed a "primary" site (ftp.freebsd.org, I believe) and several other mirror sites, one of which was the current snapshot site. The message on this screen said that only the primary site was guaranteed to have all releases, so I tried that. The install program returned immediately saying that it couldn't find the files. So I tried the snapshot site, and it worked. I believe that I may have even seen a March 8th date at somepoint also. In any case, I completely understand that special proceedures would be warranted for Release Candidates, resulting in a mismatch with the message on the "pick an ftp transfer site" screen -- and an erroneous assumption on my part that the snapshot site was the next best thing. My only desire right now is to get this right. So, I am now wondering: 1- What did I miss in not getting the "local distribution?" (I searched freebsd.org to no avail) and what else might I have missed? 2- Is there any easy and/or correct way to recover (/stand/sysinstall?, CVSup?), or should I just reinstall? John >From: "Jordan K. Hubbard" >To: "John Daniels" >CC: freebsd-current@FreeBSD.ORG >Subject: Re: FBSD4.0-RC3 install >Date: Thu, 09 Mar 2000 09:01:37 -0800 > > > Hi: > > I did an install of 4.0-RC3 last night and found the following: > > > > 1: Unable to transfer the local distribution from > > ftp://current.freebsd.org/pub/FreeBSD/Snapshots/i386 > >Because it's not there. I listed the URLs I listed *very >specifically* and that is the ONLY location you can get this from. >Just ignore current.freebsd.org for the purposes of these release >candidates please. > >- Jordan ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 11: 1:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 4BCC937B63D for ; Thu, 9 Mar 2000 11:01:38 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id VAA99897 for freebsd-current@FreeBSD.ORG; Thu, 9 Mar 2000 21:01:31 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200003091901.VAA99897@zibbi.mikom.csir.co.za> Subject: ata, DMA and the install floppies To: freebsd-current@FreeBSD.ORG (FreeBSD-current) Date: Thu, 9 Mar 2000 21:01:31 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have been trying to install yesterday's 4.0 snap on a no-name brand motherboard with the VIA chipset, but I'm running in some problems. I suspect there is a problem with the DMA. The error I'm getting when the disk is newfs'ed is a repeating: ad0: WRITE command timeout - resetting ata0: resetting devices .. done ad0: WRITE command timeout - resetting ata0: resetting devices .. done ... It seems that it is just going on and on. Shouldn't it back down to non DMA mode after a while? Is there a way to disable the DMA on the install floppies? Part of the probe looks like this: (written down by hand) atapci0: port 0xe000 - 0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ... ad0: 6204MB [13446/15/63] at ata0-master using UDMA33 John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 11:19:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 0BBEE37B5EB for ; Thu, 9 Mar 2000 11:19:40 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id OAA59912; Thu, 9 Mar 2000 14:19:19 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000309141635.0212d210@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 09 Mar 2000 14:16:35 -0500 To: John Hay , freebsd-current@FreeBSD.ORG (FreeBSD-current) From: Mike Tancsa Subject: Re: ata, DMA and the install floppies In-Reply-To: <200003091901.VAA99897@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:01 PM 3/9/00 +0200, John Hay wrote: >atapci0: port 0xe000 - 0xe00f at device 7.1 on pci0 >ata0: at 0x1f0 irq 14 on atapci0 >... >ad0: 6204MB [13446/15/63] at ata0-master using UDMA33 Actually, I just noticed the same thing today. Should not having #options ATA_ENABLE_ATAPI_DMA commented out negated the UDMA ? atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ad0: 4104MB [8896/15/63] at ata0-master using UDMA33 Or is the "using UDMA33" somewhat misleading ? 4.0-20000308-CURRENT FreeBSD 4.0-20000308-CURRENT #0 ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 11:23:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 009F237B64D for ; Thu, 9 Mar 2000 11:23:52 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA20462; Thu, 9 Mar 2000 20:23:34 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200003091923.UAA20462@freebsd.dk> Subject: Re: ata, DMA and the install floppies In-Reply-To: <200003091901.VAA99897@zibbi.mikom.csir.co.za> from John Hay at "Mar 9, 2000 09:01:31 pm" To: jhay@mikom.csir.co.za (John Hay) Date: Thu, 9 Mar 2000 20:23:33 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG (FreeBSD-current) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems John Hay wrote: > Hi, > > I have been trying to install yesterday's 4.0 snap on a no-name brand > motherboard with the VIA chipset, but I'm running in some problems. I > suspect there is a problem with the DMA. The error I'm getting when the > disk is newfs'ed is a repeating: > > ad0: WRITE command timeout - resetting > ata0: resetting devices .. done > ad0: WRITE command timeout - resetting > ata0: resetting devices .. done > ... > > It seems that it is just going on and on. Shouldn't it back down to non > DMA mode after a while? Is there a way to disable the DMA on the install > floppies? It should back down after 3 retries... But is is 3 retries pr request, so say it gets through on the 2 retry each time this will continue.. I dont know if there is access to the sysctl knobs from the emergency shell, but that would be a solution... > Part of the probe looks like this: (written down by hand) > > atapci0: port 0xe000 - 0xe00f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ... > ad0: 6204MB [13446/15/63] at ata0-master using UDMA33 Hmm, wierd, did this hardware run FreeBSD before ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 11:24:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 9FAF037B858 for ; Thu, 9 Mar 2000 11:24:34 -0800 (PST) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 632081905C; Thu, 9 Mar 2000 20:24:33 +0100 (CET) Received: by antinea.enst.fr (Postfix, from userid 1000) id B39A738E; Thu, 9 Mar 2000 20:24:26 +0100 (CET) Date: Thu, 9 Mar 2000 20:24:26 +0100 To: John Hay Cc: FreeBSD-current Subject: Re: ata, DMA and the install floppies References: <200003091901.VAA99897@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003091901.VAA99897@zibbi.mikom.csir.co.za>; from jhay@mikom.csir.co.za on Thu, Mar 09, 2000 at 09:01:31PM +0200 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-03-09-20-24-26+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | ad0: WRITE command timeout - resetting | ata0: resetting devices .. done | ad0: WRITE command timeout - resetting | ata0: resetting devices .. done | ... | | It seems that it is just going on and on. Shouldn't it back down to non | DMA mode after a while? Is there a way to disable the DMA on the install | floppies? How many times did it retry? It looks like everything is in place to default to PIO mode in this case, but you have allow it to try 3 times before it fallbacks to PIO. >From ata-disk.c log: revision 1.59 date: 2000/03/05 16:52:23; author: sos; state: Exp; lines: +24 -24 [...] Update the timeout code to try fallback to PIO if problems arise in DMA mode. ---------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 11:26:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 28FD837B7B1 for ; Thu, 9 Mar 2000 11:26:38 -0800 (PST) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id E69F51905C; Thu, 9 Mar 2000 20:26:33 +0100 (CET) Received: by antinea.enst.fr (Postfix, from userid 1000) id A9C5338E; Thu, 9 Mar 2000 20:26:33 +0100 (CET) Date: Thu, 9 Mar 2000 20:26:33 +0100 To: Soren Schmidt Cc: John Hay , FreeBSD-current Subject: Re: ata, DMA and the install floppies References: <200003091901.VAA99897@zibbi.mikom.csir.co.za> <200003091923.UAA20462@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200003091923.UAA20462@freebsd.dk>; from sos@freebsd.dk on Thu, Mar 09, 2000 at 08:23:33PM +0100 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-03-09-20-26-33+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9/03, Soren Schmidt wrote: | Hmm, wierd, did this hardware run FreeBSD before ?? This looks exactly like the problem I was having with my Compaq laptop, which could run 3.4 boot disks just fine but not 4.0 kernels. I was probably too lazy to wait until it reaches the 3 attempts, so I will try again :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 11:30:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 374AA37B66E for ; Thu, 9 Mar 2000 11:30:27 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id OAA64153; Thu, 9 Mar 2000 14:30:01 -0500 (EST) Date: Thu, 9 Mar 2000 14:30:01 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Samuel Tardieu Cc: Soren Schmidt , John Hay , FreeBSD-current Subject: Re: ata, DMA and the install floppies In-Reply-To: <2000-03-09-20-26-33+trackit+sam@inf.enst.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Samuel Tardieu wrote: > This looks exactly like the problem I was having with my Compaq laptop, which > could run 3.4 boot disks just fine but not 4.0 kernels. I was probably too > lazy to wait until it reaches the 3 attempts, so I will try again :) > What model laptop may I ask? I'm running 4.0-current since 1/11/2000 (last world rebuild 3/8/2000) on a Compaq Armada 7400 without incident. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 11:31:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 35F7E37B7F9 for ; Thu, 9 Mar 2000 11:31:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA03480; Thu, 9 Mar 2000 11:31:48 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "John Daniels" Cc: freebsd-current@freebsd.org Subject: Re: FBSD4.0-RC3 install In-reply-to: Your message of "Thu, 09 Mar 2000 13:24:10 EST." <20000309182410.45424.qmail@hotmail.com> Date: Thu, 09 Mar 2000 11:31:48 -0800 Message-ID: <3477.952630308@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I got the install floppies from the ftp directory that you listed. When the > install came to a point where it asked for the ftp site to get the > distribution, it listed a "primary" site (ftp.freebsd.org, I believe) and This should work now - it just needed some symlinks to be created. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 11:33: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 216DF37B64D for ; Thu, 9 Mar 2000 11:32:55 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id VAA00712; Thu, 9 Mar 2000 21:32:19 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200003091932.VAA00712@zibbi.mikom.csir.co.za> Subject: Re: ata, DMA and the install floppies In-Reply-To: <200003091923.UAA20462@freebsd.dk> from Soren Schmidt at "Mar 9, 2000 08:23:33 pm" To: sos@freebsd.dk (Soren Schmidt) Date: Thu, 9 Mar 2000 21:32:19 +0200 (SAT) Cc: jhay@mikom.csir.co.za (John Hay), freebsd-current@FreeBSD.ORG (FreeBSD-current) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I have been trying to install yesterday's 4.0 snap on a no-name brand > > motherboard with the VIA chipset, but I'm running in some problems. I > > suspect there is a problem with the DMA. The error I'm getting when the > > disk is newfs'ed is a repeating: > > > > ad0: WRITE command timeout - resetting > > ata0: resetting devices .. done > > ad0: WRITE command timeout - resetting > > ata0: resetting devices .. done > > ... > > > > It seems that it is just going on and on. Shouldn't it back down to non > > DMA mode after a while? Is there a way to disable the DMA on the install > > floppies? > > It should back down after 3 retries... But is is 3 retries pr request, > so say it gets through on the 2 retry each time this will continue.. > I dont know if there is access to the sysctl knobs from the emergency > shell, but that would be a solution... Well it is been doing fsck for more than an hour now. :-) This is before the emergency shell is opened, but if I remember correctly, sysctl is not part of tools available. > > > Part of the probe looks like this: (written down by hand) > > > > atapci0: port 0xe000 - 0xe00f at device 7.1 on pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ... > > ad0: 6204MB [13446/15/63] at ata0-master using UDMA33 > > Hmm, wierd, did this hardware run FreeBSD before ?? A similar system did run FreeBSD-3.4, but I never enabled DMA on it. I'll try to install 3.4 on this one and see. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 11:45:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id AE9F937B805 for ; Thu, 9 Mar 2000 11:45:11 -0800 (PST) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 4379C1905C; Thu, 9 Mar 2000 20:45:01 +0100 (CET) Received: by antinea.enst.fr (Postfix, from userid 1000) id D8A6D3E2; Thu, 9 Mar 2000 20:44:50 +0100 (CET) Date: Thu, 9 Mar 2000 20:44:50 +0100 To: Kelly Yancey Cc: Soren Schmidt , John Hay , FreeBSD-current Subject: Re: ata, DMA and the install floppies References: <2000-03-09-20-26-33+trackit+sam@inf.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kbyanc@posi.net on Thu, Mar 09, 2000 at 02:30:01PM -0500 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-03-09-20-44-50+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | What model laptop may I ask? I'm running 4.0-current since 1/11/2000 | (last world rebuild 3/8/2000) on a Compaq Armada 7400 without incident. Armada V300. I sent the full details here a few days ago. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 11:54:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 5267137B7FD for ; Thu, 9 Mar 2000 11:54:34 -0800 (PST) (envelope-from dervish@goku.cl.msu.edu) Received: (from dervish@localhost) by goku.cl.msu.edu (8.9.3/8.9.3) id PAA42743 for freebsd-current@freebsd.org; Thu, 9 Mar 2000 15:02:16 -0500 (EST) (envelope-from dervish) Date: Thu, 9 Mar 2000 15:02:16 -0500 From: Bush Doctor To: freebsd-current@freebsd.org Subject: buildworld failure in cvs ... Message-ID: <20000309150216.A39127@goku.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 4.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone else seeing this. cvsupped from 12:00 noon EST ... cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/cvs/../lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/lib -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i386/usr/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries.o error.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main.o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o rtag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' /usr/lib/libRSAglue.so.1: undefined reference to `R_GetRandomBytesNeeded' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPrivateDecrypt' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPublicEncrypt' /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomFinal' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPrivateEncrypt' /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomInit' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPublicDecrypt' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cvs/cvs. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cvs. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 12:16: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from adara.lcs.mit.edu (adara.lcs.mit.edu [18.111.14.1]) by hub.freebsd.org (Postfix) with ESMTP id 4C9A337B7DD for ; Thu, 9 Mar 2000 12:16:01 -0800 (PST) (envelope-from beng@adara.lcs.mit.edu) Received: from adara.lcs.mit.edu (localhost [127.0.0.1]) by adara.lcs.mit.edu (8.9.3/8.9.3) with ESMTP id PAA39085; Thu, 9 Mar 2000 15:17:01 -0500 (EST) (envelope-from beng@adara.lcs.mit.edu) Message-Id: <200003092017.PAA39085@adara.lcs.mit.edu> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bush Doctor Cc: freebsd-current@freebsd.org Subject: Re: buildworld failure in cvs ... In-Reply-To: Message from Bush Doctor of "Thu, 09 Mar 2000 15:02:16 EST." <20000309150216.A39127@goku.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Mar 2000 15:17:01 -0500 From: Benjamin Greenwald Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having the same problem. To overstate the obvious, it's related to compiling with MAKE_KERBEROS4=yes which require the des code in libcrypto. Anyone know how libRSAglue is getting pulled in? -Ben Greenwald > Is anyone else seeing this. cvsupped from 12:00 noon EST > > ... > > cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/cvs/../ lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. > /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/lib - I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA > VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i386/us r/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c > lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries.o erro r.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o > hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main.o mkmo dules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen > d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o rtag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts > .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/ ../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ > libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err > /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' > /usr/lib/libRSAglue.so.1: undefined reference to `R_GetRandomBytesNeeded' > /usr/lib/libRSAglue.so.1: undefined reference to `RSAPrivateDecrypt' > /usr/lib/libRSAglue.so.1: undefined reference to `RSAPublicEncrypt' > /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomFinal' > /usr/lib/libRSAglue.so.1: undefined reference to `RSAPrivateEncrypt' > /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomInit' > /usr/lib/libRSAglue.so.1: undefined reference to `RSAPublicDecrypt' > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/cvs/cvs. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/cvs. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin. > *** Error code 1 > > Stop in /usr/src/gnu. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > > #;^) > -- > f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. > bush doctor > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 12:19:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id B840237B7FB for ; Thu, 9 Mar 2000 12:19:41 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id PAA65492; Thu, 9 Mar 2000 15:19:28 -0500 (EST) Date: Thu, 9 Mar 2000 15:19:28 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Samuel Tardieu Cc: Soren Schmidt , John Hay , FreeBSD-current Subject: Re: ata, DMA and the install floppies In-Reply-To: <2000-03-09-20-44-50+trackit+sam@inf.enst.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Samuel Tardieu wrote: > | What model laptop may I ask? I'm running 4.0-current since 1/11/2000 > | (last world rebuild 3/8/2000) on a Compaq Armada 7400 without incident. > > Armada V300. I sent the full details here a few days ago. > Ah, I remember seeing that. As I recall the systems were fairly similar with regards to the IDE configuration. We have the IDE controllers, same size/geometry hard drives (although I think mine is identified as IBM and yours WD...but I've read elsewhere they are in fact the same drive). The only other difference I recall was that your laptop has a different CD-ROM drive. But I'm trying to work off memory here; I can verify the similarity when I get home (where the laptop is). Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 12:51:30 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 0729837B73A; Thu, 9 Mar 2000 12:51:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 04A282E8157; Thu, 9 Mar 2000 12:51:28 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 9 Mar 2000 12:51:27 -0800 (PST) From: Kris Kennaway To: Bush Doctor Cc: freebsd-current@freebsd.org Subject: Re: buildworld failure in cvs ... In-Reply-To: <20000309150216.A39127@goku.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Bush Doctor wrote: > Is anyone else seeing this. cvsupped from 12:00 noon EST > > ... > > cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/cvs/../lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. > /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/lib -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA > VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i386/usr/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c > lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries.o error.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o > hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main.o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen > d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o rtag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts > .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ > libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err > /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' Did this come up as part of make world? It looks like you have a stale library. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 12:54:54 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 918C437B839; Thu, 9 Mar 2000 12:54:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 8F6C02E8157; Thu, 9 Mar 2000 12:54:52 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 9 Mar 2000 12:54:52 -0800 (PST) From: Kris Kennaway To: Benjamin Greenwald Cc: Bush Doctor , freebsd-current@freebsd.org Subject: Re: buildworld failure in cvs ... In-Reply-To: <200003092017.PAA39085@adara.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Benjamin Greenwald wrote: > I'm having the same problem. To overstate the obvious, it's related to > compiling with MAKE_KERBEROS4=yes which require the des code in libcrypto. > Anyone know how libRSAglue is getting pulled in? It shouldn't be..libRSAglue is an empty stub thesedays containing no symbols. Unless I've missed something nothing should even be looking for it, especially during make world, and especially not outside of the obj tree. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 12:57:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from gta.com (gw.gta.com [199.120.225.5]) by hub.freebsd.org (Postfix) with ESMTP id 2B08637B835 for ; Thu, 9 Mar 2000 12:57:49 -0800 (PST) (envelope-from lab@gta.com) Received: from gta.com (GTA internal mail system) by gta.com id QAA60502; Thu, 9 Mar 2000 16:03:17 -0500 (EST) Date: Thu, 9 Mar 2000 16:03:17 -0500 (EST) Message-Id: <200003092103.QAA60502@gta.com> From: Larry Baird To: freebsd-current@freebsd.org Subject: FBSD4.0-20000307 install floppies and VAIO PCG-Z505HS User-Agent: tin/1.4.2-20000205 ("Possession") (UNIX) (FreeBSD/3.4-STABLE (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ran into an odd problem tring to install the 3/7 release of 4.0 onto my VAIO PCG-Z505HS. The install hung while probing for plug and play devices. I had the BIOS set to non plug and play OS. So just for grins I turned plug and play OS on in the bios and tried again. Installed without a hitch. Of course I had to then go back into the BIOS and turn off plug and play OS to get by USB devices working after the install. (-: Any thoughts? Larry -- ------------------------------------------------------------------------ Larry Baird | HTTP://www.gnatbox.com Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 13:41: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from adara.lcs.mit.edu (adara.lcs.mit.edu [18.111.14.1]) by hub.freebsd.org (Postfix) with ESMTP id CA6ED37B828; Thu, 9 Mar 2000 13:40:56 -0800 (PST) (envelope-from beng@adara.lcs.mit.edu) Received: from adara.lcs.mit.edu (localhost [127.0.0.1]) by adara.lcs.mit.edu (8.9.3/8.9.3) with ESMTP id QAA56158; Thu, 9 Mar 2000 16:42:00 -0500 (EST) (envelope-from beng@adara.lcs.mit.edu) Message-Id: <200003092142.QAA56158@adara.lcs.mit.edu> To: Kris Kennaway Cc: Bush Doctor , freebsd-current@freebsd.org Subject: Re: buildworld failure in cvs ... In-reply-to: Your message of "Thu, 09 Mar 2000 12:54:52 PST." From: Benjamin Greenwald X-Sender: beng@lcs.mit.edu Date: Thu, 09 Mar 2000 16:42:00 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It was during a buildworld. I'm going to do a make world with MAKE_KERBEROS4=NO, and then do a buildworld after the reboot and see if it was somehow pulling the library from outside of /obj. -Ben > On Thu, 9 Mar 2000, Benjamin Greenwald wrote: > > > I'm having the same problem. To overstate the obvious, it's related to > > compiling with MAKE_KERBEROS4=yes which require the des code in libcrypto. > > Anyone know how libRSAglue is getting pulled in? > > It shouldn't be..libRSAglue is an empty stub thesedays containing no > symbols. Unless I've missed something nothing should even be looking for > it, especially during make world, and especially not outside of the obj > tree. > > Kris > > ---- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 13:42:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from everest.overx.com (everest.overx.com [63.82.145.202]) by hub.freebsd.org (Postfix) with ESMTP id 89CCA37B837 for ; Thu, 9 Mar 2000 13:42:34 -0800 (PST) (envelope-from dayton@overx.com) Received: from polo.overx.com (polo.overx.com [63.82.145.204]) by everest.overx.com (Postfix) with ESMTP id 83588203C for ; Thu, 9 Mar 2000 15:42:29 -0600 (CST) Received: by polo.overx.com (Postfix, from userid 1001) id CAE773F29; Thu, 9 Mar 2000 15:42:36 -0600 (CST) From: Soren Dayton Reply-To: dayton+freebsd-stable@overx.com To: freebsd-current@freebsd.org Subject: samba 2.0.6 crashing -stable Date: 09 Mar 2000 15:42:36 -0600 Message-ID: <86bt4n6cs3.fsf@polo.overx.com> Lines: 19 User-Agent: Gnus/5.070099 (Pterodactyl Gnus v0.99) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been having a recurring problem with samba on my freebsd machines. It began when I was running 3.2, and it appears to still be around with -stable. (and samba 2.0.3, and now 2.0.6) Basically, when copying large files, the FreeBSD file server appears to lose all of its network connectivity. It cannot be pinged, etc. You also cannot log in as root because it hangs after you type in `root' on console. (which might be concistent with all networking failing. I think, but have not verified this, that anything that does not use NIS or some such thing will continue to work. Has anyone heard of such problems? Any ideas? Thanks. Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 13:59:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from everest.overx.com (everest.overx.com [63.82.145.202]) by hub.freebsd.org (Postfix) with ESMTP id A5BC737B8B4 for ; Thu, 9 Mar 2000 13:59:23 -0800 (PST) (envelope-from dayton@overx.com) Received: from polo.overx.com (polo.overx.com [63.82.145.204]) by everest.overx.com (Postfix) with ESMTP id 2905D2031 for ; Thu, 9 Mar 2000 15:59:20 -0600 (CST) Received: by polo.overx.com (Postfix, from userid 1001) id EBAB63F29; Thu, 9 Mar 2000 15:59:27 -0600 (CST) From: Soren Dayton Reply-To: dayton@overx.com To: freebsd-current@freebsd.org Subject: sorry. Mistyped Date: 09 Mar 2000 15:59:27 -0600 Message-ID: <864saf6c00.fsf@polo.overx.com> Lines: 5 User-Agent: Gnus/5.070099 (Pterodactyl Gnus v0.99) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was thinking about -current something and wrote current. Please disregard my message. Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 14: 2:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.iae.nl (mail.iae.nl [194.151.64.19]) by hub.freebsd.org (Postfix) with ESMTP id C30CD37B87C for ; Thu, 9 Mar 2000 14:02:51 -0800 (PST) (envelope-from hansot@iae.nl) Received: from iae.nl (pm17d025.iae.nl [212.61.3.25]) by mail.iae.nl (Postfix) with ESMTP id A0A4220F26; Thu, 9 Mar 2000 23:02:49 +0100 (CET) Message-ID: <38C81F71.6CBD66B3@iae.nl> Date: Thu, 09 Mar 2000 23:02:25 +0100 From: Hans Ottevanger X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Cc: sos@freebsd.dk Subject: RC3 install floppies: panic: resource_list_alloc: resource entry is busy Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I just tried to boot the RC3 install floppies on my Pentium 66 testbox. It gets through the config stage without trouble, but then panics immediately with: ... pcib0: on motherboard pci0: on pcib0 atapci0: port 0 x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 atapci0: Busmastering DMA not supported panic: resource_list_alloc: resource entry is busy I am also having this problem with 4.0-CURRENT kernels since February 18, both with my own custom kernel config and GENERIC. I have to revert to the ata driver of February 17 or earlier to get the system booting again, and then it runs perfectly. This machine has an Intel motherboard with a Mercury chipset, 64 Mbyte RAM, Matrox Millenium II, two Western Digital disks, and it ran all previous FreeBSD releases perfectly for almost five years. Anybody else having this problem ? And before I start digging, any idea where to look for a solution, if it makes sense at all ? Kind regards, Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 14: 4: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A273037B94C for ; Thu, 9 Mar 2000 14:03:57 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA69158; Thu, 9 Mar 2000 15:03:52 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA11524; Thu, 9 Mar 2000 15:03:33 -0700 (MST) Message-Id: <200003092203.PAA11524@harmony.village.org> To: Larry Baird Subject: Re: FBSD4.0-20000307 install floppies and VAIO PCG-Z505HS Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 09 Mar 2000 16:03:17 EST." <200003092103.QAA60502@gta.com> References: <200003092103.QAA60502@gta.com> Date: Thu, 09 Mar 2000 15:03:33 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003092103.QAA60502@gta.com> Larry Baird writes: : then go back into the BIOS and turn off plug and play OS to get : by USB devices working after the install. (-: : : Any thoughts? You should have turned off PNP OS in the BIOS to start with. That's the only setting that is supported. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 14:29:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 7CDAC37B7AF; Thu, 9 Mar 2000 14:29:49 -0800 (PST) (envelope-from dervish@goku.cl.msu.edu) Received: (from dervish@localhost) by goku.cl.msu.edu (8.9.3/8.9.3) id RAA43479; Thu, 9 Mar 2000 17:37:31 -0500 (EST) (envelope-from dervish) Date: Thu, 9 Mar 2000 17:37:31 -0500 From: Bush Doctor To: Kris Kennaway Cc: freebsd-current@freebsd.org Subject: Re: buildworld failure in cvs ... Message-ID: <20000309173731.B39127@goku.cl.msu.edu> References: <20000309150216.A39127@goku.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kris@hub.freebsd.org on Thu, Mar 09, 2000 at 12:51:27PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Kris Kennaway aka (kris@hub.freebsd.org) said: > On Thu, 9 Mar 2000, Bush Doctor wrote: > > > Is anyone else seeing this. cvsupped from 12:00 noon EST > > > > ... > > > > cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/cvs/../lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. > > /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/lib -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA > > VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i386/usr/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c > > lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries.o error.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o > > hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main.o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen > > d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o rtag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts > > .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ > > libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err > > /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' > > Did this come up as part of make world? It looks like you have a stale > library. It's occurring during a buildworld. If you're referring to libRSAglue being stale it looks like that may be it. bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so -> libRSAglue.so.1 -r--r--r-- 1 root wheel 5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a > > Kris > > ---- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 14:59:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id 77EB237B882; Thu, 9 Mar 2000 14:58:59 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id RAA92085; Thu, 9 Mar 2000 17:58:41 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38C82CA1.C9467300@acm.org> Date: Thu, 09 Mar 2000 17:58:41 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Bush Doctor Cc: Kris Kennaway , freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure in cvs ... References: <20000309150216.A39127@goku.cl.msu.edu> <20000309173731.B39127@goku.cl.msu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am not seeing the problem with a standard build, but I am not building Kerberos. Looking at the makefiles, there is no mentioned of libRSAglue anyplace. The link command doesn't even imply the use of libRSAglue. Also, a buildworld should not be using libraries outside of the build environment. Don't bother building with MAKE_KERBEROS4=NO. All of the tests look at the variable being defined and not its value. You might try removing your object directory and doing a make cleandir twice to make sure nothing is left in source tree that shouldn't be there. Jim Bloom bloom@acm.org Bush Doctor wrote: > > Out of da blue Kris Kennaway aka (kris@hub.freebsd.org) said: > > On Thu, 9 Mar 2000, Bush Doctor wrote: > > > > > Is anyone else seeing this. cvsupped from 12:00 noon EST > > > > > > ... > > > > > > cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/cvs/../lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. > > > /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/lib -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA > > > VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i386/usr/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c > > > lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries.o error.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o > > > hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main.o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen > > > d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o rtag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts > > > .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ > > > libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err > > > /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' > > > > Did this come up as part of make world? It looks like you have a stale > > library. > It's occurring during a buildworld. If you're referring to libRSAglue > being stale it looks like that may be it. > > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a > lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so -> libRSAglue.so.1 > -r--r--r-- 1 root wheel 5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 > -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 15:44:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id 1034037B89B for ; Thu, 9 Mar 2000 15:44:02 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id RAA53638; Thu, 9 Mar 2000 17:43:48 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <001201bf8a21$5178fa60$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "Jordan K. Hubbard" Cc: References: <3477.952630308@zippy.cdrom.com> Subject: Re: FBSD4.0-RC3 install Date: Thu, 9 Mar 2000 17:43:47 -0600 Organization: West Bend Internet MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Jordan K. Hubbard" > > This should work now - it just needed some symlinks to be created. > The link to the packages directory is wrong. It is pointing one to many directories back. packages -> ../../../../ports/i386/packages-4-current it should be: packages -> ../../../ports/i386/packages-4-current I also noticed one very small error on the screen for setting up the mouse. It says to choose option 4 to disable the mouse, it should be option 5. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 16:39:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id C2B3D37B7F1 for ; Thu, 9 Mar 2000 16:39:37 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12TCWR-0006aJ-00 for current@freebsd.org; Thu, 09 Mar 2000 23:39:15 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12TCWR-000Bsw-00 for current@freebsd.org; Thu, 09 Mar 2000 23:39:15 +0000 Date: Thu, 9 Mar 2000 23:39:15 +0000 From: Ben Smithurst To: current@freebsd.org Subject: mount_cd9660+atapi-cd panic Message-ID: <20000309233915.T62624@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok, this was partly caused by dodgy hardware it seems, so don't worry too much, but it would be nice if a panic could be avoided. first, 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 #12: Sun Mar 5 23:40:38 GMT 2000 ben@platinum.scientia.demon.co.uk:/usr/src/sys/compile/PLATINUM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 400909968 Hz CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 67043328 (65472K bytes) avail memory = 62517248 (61052K bytes) Preloaded elf kernel "kernel" at 0xc0273000. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 rl0: port 0xe000-0xe0ff mem 0xe8001000-0xe80010ff irq 10 at device 10.0 on pci0 rl0: Ethernet address: 00:e0:7d:74:66:7c miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: supplying EUI64: 00:e0:7d:ff:fe:74:66:7c atapci0: port 0xf000-0xf00f irq 0 at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ad0: 8063MB [16383/16/63] at ata0-master using UDMA33 acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done acd0: MODE_SENSE_BIG DONEDRQ acd0: MODE_SENSE_BIG - ABORTED COMMAND asc=4e ascq=00 error=00 acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done acd0: MODE_SENSE_BIG DONEDRQ acd0: MODE_SENSE_BIG - ABORTED COMMAND asc=4e ascq=00 error=00 acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done acd0: MODE_SENSE_BIG DONEDRQ acd0: MODE_SENSE_BIG - ABORTED COMMAND asc=4e ascq=00 error=00 acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done acd0: MODE_SENSE_BIG DONEDRQ acd0: MODE_SENSE_BIG - ABORTED COMMAND asc=4e ascq=00 error=00 ata1-master: CDROM device - NO DRIVER! Mounting root from ufs:/dev/ad0s4a rl0: starting DAD for fe80:0001::02e0:7dff:fe74:667c IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled rl0: DAD complete for fe80:0001::02e0:7dff:fe74:667c - no duplicates found rl0: starting DAD for fec0:56c0:60a7:1045:02e0:7dff:fe74:667c rl0: DAD complete for fec0:56c0:60a7:1045:02e0:7dff:fe74:667c - no duplicates found Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8:0xc01bc0ad stack pointer = 0x10:0xc6047d30 frame pointer = 0x10:0xc6047d3c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 49742 (mount_cd9660) interrupt mask = none trap number = 12 panic: page fault syncing disks... 12 done Uptime: 2m50s dumping to dev #ad/0x50001, offset 278656 dump ata0: resetting devices .. done 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 dunno what's wrong with that drive, it worked fine after rebooting. As you can see, the panic occured when trying to mount the CD-ROM. Here's the backtrace: 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 2641920 initial pcb at 21c8a0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8:0xc01bc0ad stack pointer = 0x10:0xc6047d30 frame pointer = 0x10:0xc6047d3c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 49742 (mount_cd9660) interrupt mask = none trap number = 12 panic: page fault syncing disks... 12 done Uptime: 2m50s dumping to dev #ad/0x50001, offset 278656 dump ata0: resetting devices .. done 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 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:304 304 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:304 #1 0xc012ddc8 in poweroff_wait (junk=0xc01ffccf, howto=-978243040) at ../../kern/kern_shutdown.c:554 #2 0xc01dbcd9 in trap_fatal (frame=0xc6047cf0, eva=44) at ../../i386/i386/trap.c:924 #3 0xc01db9b1 in trap_pfault (frame=0xc6047cf0, usermode=0, eva=44) at ../../i386/i386/trap.c:817 #4 0xc01db57b in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 1, tf_esi = -1065680896, tf_ebp = -972784324, tf_isp = -972784356, tf_ebx = -1064931712, tf_edx = 0, tf_ecx = 0, tf_eax = 44, tf_trapno = 12, tf_err = 0, tf_eip = -1071923027, tf_cs = 8, tf_eflags = 66050, tf_esp = -1065678848, tf_ss = -1065704960}) at ../../i386/i386/trap.c:423 #5 0xc01bc0ad in atapi_queue_cmd (atp=0xc07b0000, ccb=0xc6047d68 "\036", data=0x0, count=0, flags=0, timeout=30, callback=0, unused=0x0, bp=0x0) at ../../dev/ata/atapi-all.c:178 #6 0xc01bfdd0 in acd_prevent_allow (cdp=0xc07b0800, lock=1) at ../../dev/ata/atapi-cd.c:1747 #7 0xc01bdbae in acdopen (dev=0xc07aa200, flags=1, fmt=8192, p=0xc5b13220) at ../../dev/ata/atapi-cd.c:481 #8 0xc015eef9 in spec_open (ap=0xc6047e10) at ../../miscfs/specfs/spec_vnops.c:191 #9 0xc015edf9 in spec_vnoperate (ap=0xc6047e10) at ../../miscfs/specfs/spec_vnops.c:117 #10 0xc01a4f51 in ufs_vnoperatespec (ap=0xc6047e10) at ../../ufs/ufs/ufs_vnops.c:2301 #11 0xc015ba3f in vn_open (ndp=0xc6047edc, fmode=1, cmode=0) at vnode_if.h:189 #12 0xc0157a3d in open (p=0xc5b13220, uap=0xc6047f80) at ../../kern/vfs_syscalls.c:994 #13 0xc01dbf0a in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077936645, tf_esi = 2, tf_ebp = -1077938168, tf_isp = -972783660, tf_ebx = -1077936832, tf_edx = -1077936635, tf_ecx = -1077936635, tf_eax = 5, tf_trapno = 12, tf_err = 2, tf_eip = 134525628, tf_cs = 31, tf_eflags = 647, tf_esp = -1077939028, tf_ss = 47}) at ../../i386/i386/trap.c:1073 #14 0xc01d0e86 in Xint0x80_syscall () #15 0x80482b9 in ?? () #16 0x80480f9 in ?? () (kgdb) frame 5 #5 0xc01bc0ad in atapi_queue_cmd (atp=0xc07b0000, ccb=0xc6047d68 "\036", data=0x0, count=0, flags=0, timeout=30, callback=0, unused=0x0, bp=0x0) at ../../dev/ata/atapi-all.c:178 178 request->ccbsize = (ATP_PARAM->cmdsize) ? 16 : 12; (kgdb) p request $1 = (struct atapi_request *) 0x0 (this seems odd, a few lines before that dereferenced request without a problem.) (kgdb) p *atp $2 = {controller = 0x0, unit = 0, driver = 0x10, devname = 0x18
, cmd = 32 ' ', flags = 1024} That doesn't look very useful either... I'm guessing the fix should be fairly simple (check something != NULL and return ESOMETHING if it is), unfortunately as the drive seems to be working again I won't be able to test it. :-( kernel config file: ## $Id: PLATINUM,v 1.10 2000/02/20 20:34:28 ben Exp $ machine i386 cpu I586_CPU ident PLATINUM maxusers 16 options ATA_STATIC_ID options COMPAT_43 options FFS options FFS_ROOT options INET options INET6 options KTRACE options P1003_1B options SOFTUPDATES options SYSVSHM options UCONSOLE options _KPOSIX_PRIORITY_SCHEDULING device isa device atkbdc0 at isa? port IO_KBD device miibus device pci device ata device atadisk device atapicd device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device npx0 at nexus? port IO_NPX irq 13 device rl device sc0 at isa? device vga0 at isa? pseudo-device bpf 4 pseudo-device loop pseudo-device ether pseudo-device pty pseudo-device splash If you want more information, let me know. -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 17: 4:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226]) by hub.freebsd.org (Postfix) with ESMTP id 7A36B37B880; Thu, 9 Mar 2000 17:04:02 -0800 (PST) (envelope-from mi@video-collage.com) X-Relay-IP: ‚  Received: from dufus.video-collage.com (dufus [10.222.222.77]) by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id UAA11384; Thu, 9 Mar 2000 20:03:54 -0500 (EST) From: Mikhail Teterin Received: (from mi@localhost) by dufus.video-collage.com (8.9.3/8.9.3) id UAA21838; Thu, 9 Mar 2000 20:03:53 -0500 (EST) (envelope-from mi@xxx) Message-Id: <200003100103.UAA21838@dufus.video-collage.com> Subject: SMP on Alpha? To: current@freebsd.org, alpha@freebsd.org Date: Thu, 9 Mar 2000 20:03:53 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Will the -current version of FreeBSD run on a multi-CPU axp machine and use all of the CPUs? Would that be a reliable box (assuming the admin sometimes knows what he is doing)? Do I want to make a "production" server out of an axp box at all in the near future? Thanks! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 17: 4:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from adara.lcs.mit.edu (adara.lcs.mit.edu [18.111.14.1]) by hub.freebsd.org (Postfix) with ESMTP id AED2F37B886; Thu, 9 Mar 2000 17:04:31 -0800 (PST) (envelope-from beng@adara.lcs.mit.edu) Received: from adara.lcs.mit.edu (localhost [127.0.0.1]) by adara.lcs.mit.edu (8.9.3/8.9.3) with ESMTP id UAA62398; Thu, 9 Mar 2000 20:05:23 -0500 (EST) (envelope-from beng@adara.lcs.mit.edu) Message-Id: <200003100105.UAA62398@adara.lcs.mit.edu> X-Mailer: exmh version 2.1.1 10/15/1999 To: bloom@acm.org Cc: Bush Doctor , Kris Kennaway , freebsd-current@freebsd.org Subject: Re: buildworld failure in cvs ... In-Reply-To: Message from Jim Bloom of "Thu, 09 Mar 2000 17:58:41 EST." <38C82CA1.C9467300@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Mar 2000 20:05:23 -0500 From: Benjamin Greenwald Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I meant I was going to comment out MAKE_KERBEROS4, but thanks for the tip. Speaking of which, this is precisely what I did. I commented out MAKE_KERBEROS4, did a make world, uncommented MAKE_KERBEROS4, made the world again, and the second time everything was fine. There's probably a faster way to do this but I can attest that the above works. -Ben > I am not seeing the problem with a standard build, but I am not building > Kerberos. Looking at the makefiles, there is no mentioned of libRSAglue > anyplace. The link command doesn't even imply the use of libRSAglue. > Also, a buildworld should not be using libraries outside of the build > environment. > > Don't bother building with MAKE_KERBEROS4=NO. All of the tests look at > the variable being defined and not its value. You might try removing > your object directory and doing a make cleandir twice to make sure > nothing is left in source tree that shouldn't be there. > > Jim Bloom > bloom@acm.org > > Bush Doctor wrote: > > > > Out of da blue Kris Kennaway aka (kris@hub.freebsd.org) said: > > > On Thu, 9 Mar 2000, Bush Doctor wrote: > > > > > > > Is anyone else seeing this. cvsupped from 12:00 noon EST > > > > > > > > ... > > > > > > > > cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/c vs/../lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. > > > > /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs /lib -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA > > > > VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i 386/usr/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c > > > > lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries. o error.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o > > > > hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main. o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen > > > > d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o r tag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts > > > > .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cv s/cvs/../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ > > > > libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err > > > > /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' > > > > > > Did this come up as part of make world? It looks like you have a stale > > > library. > > It's occurring during a buildworld. If you're referring to libRSAglue > > being stale it looks like that may be it. > > > > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* > > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue. a > > lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue. so -> libRSAglue.so.1 > > -r--r--r-- 1 root wheel 5872 Jan 29 07:29 /usr/lib/libRSAglue. so.1 > > -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_ p.a > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 17: 6:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from xena.cs.waikato.ac.nz (xena.cs.waikato.ac.nz [130.217.241.20]) by hub.freebsd.org (Postfix) with ESMTP id 30DB937B886 for ; Thu, 9 Mar 2000 17:06:46 -0800 (PST) (envelope-from joerg@lucy.cs.waikato.ac.nz) Received: from lucy.cs.waikato.ac.nz (joerg@lucy.cs.waikato.ac.nz [130.217.241.12]) by xena.cs.waikato.ac.nz (8.9.3/8.9.3) with ESMTP id OAA25841; Fri, 10 Mar 2000 14:06:41 +1300 (NZDT) Received: (from joerg@localhost) by lucy.cs.waikato.ac.nz (8.9.3/8.9.0) id OAA18962; Fri, 10 Mar 2000 14:06:39 +1300 (NZDT) Date: Fri, 10 Mar 2000 14:06:39 +1300 From: Joerg Micheel To: freebsd-current@freebsd.org Cc: joerg@cs.waikato.ac.nz Subject: sysinstall sets USA_RESIDENT="YES" Message-ID: <20000310140639.A18954@cs.waikato.ac.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Organization: SCMS, The University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... drained by Solaris 7 SPARC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This happens every time I run sysinstall, potentially dangerous for me, as ports may be fetching crypto stuff from the wrong places. With a -current system of March 2nd. Joerg -- Joerg B. Micheel Email: Waikato Applied Network Dynamics Phone: +64 7 8384794 The University of Waikato, CompScience Fax: +64 7 8384155 Private Bag 3105 Pager: +64 868 38222 Hamilton, New Zealand Plan: TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 17:16:30 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id F407C37B8C9; Thu, 9 Mar 2000 17:16:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id F18812E8155; Thu, 9 Mar 2000 17:16:27 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 9 Mar 2000 17:16:27 -0800 (PST) From: Kris Kennaway To: Jim Bloom Cc: Bush Doctor , freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure in cvs ... In-Reply-To: <38C82CA1.C9467300@acm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Jim Bloom wrote: > the variable being defined and not its value. You might try removing > your object directory and doing a make cleandir twice to make sure > nothing is left in source tree that shouldn't be there. Yes, thats a likely candidate. Can you try blowing away /usr/obj and see if the problem persist? Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 17:23:40 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id E58E437B8C8; Thu, 9 Mar 2000 17:23:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E28902E8155; Thu, 9 Mar 2000 17:23:37 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 9 Mar 2000 17:23:37 -0800 (PST) From: Kris Kennaway To: Warner Losh Cc: Larry Baird , freebsd-current@FreeBSD.ORG Subject: Re: FBSD4.0-20000307 install floppies and VAIO PCG-Z505HS In-Reply-To: <200003092203.PAA11524@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Warner Losh wrote: > In message <200003092103.QAA60502@gta.com> Larry Baird writes: > : then go back into the BIOS and turn off plug and play OS to get > : by USB devices working after the install. (-: > : > : Any thoughts? > > You should have turned off PNP OS in the BIOS to start with. That's > the only setting that is supported. Yes, but he said this caused the system to panic at boot. Thats why he turned it off :) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 17:32:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id F019037B8D9; Thu, 9 Mar 2000 17:32:42 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115241>; Fri, 10 Mar 2000 12:33:32 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: SMP on Alpha? In-reply-to: <200003100103.UAA21838@dufus.video-collage.com>; from mi@video-collage.com on Fri, Mar 10, 2000 at 12:06:18PM +1100 To: Mikhail Teterin Cc: current@FreeBSD.ORG, alpha@FreeBSD.ORG Message-Id: <00Mar10.123332est.115241@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200003100103.UAA21838@dufus.video-collage.com> Date: Fri, 10 Mar 2000 12:33:31 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Mar-10 12:06:18 +1100, Mikhail Teterin wrote: >Will the -current version of FreeBSD run on a multi-CPU axp machine and >use all of the CPUs? Not yet, but Real Soon Now. > Would that be a reliable box (assuming the admin >sometimes knows what he is doing)? -current comes with all the usual `not for production use' caveats, and (without any slur on Doug Rabson, who's doing the work), you'd be very game taking FreeBSD's first cut at Alpha/SMP and putting it into production. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 17:38:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from adara.lcs.mit.edu (adara.lcs.mit.edu [18.111.14.1]) by hub.freebsd.org (Postfix) with ESMTP id 6935237B8D5; Thu, 9 Mar 2000 17:38:13 -0800 (PST) (envelope-from beng@adara.lcs.mit.edu) Received: from adara.lcs.mit.edu (localhost [127.0.0.1]) by adara.lcs.mit.edu (8.9.3/8.9.3) with ESMTP id UAA03300; Thu, 9 Mar 2000 20:39:17 -0500 (EST) (envelope-from beng@adara.lcs.mit.edu) Message-Id: <200003100139.UAA03300@adara.lcs.mit.edu> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kris Kennaway Cc: Jim Bloom , Bush Doctor , freebsd-current@freebsd.org Subject: Re: buildworld failure in cvs ... In-Reply-To: Message from Kris Kennaway of "Thu, 09 Mar 2000 17:16:27 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Mar 2000 20:39:17 -0500 From: Benjamin Greenwald Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did try blowing away /obj. Didn't help. -Ben > On Thu, 9 Mar 2000, Jim Bloom wrote: > > > the variable being defined and not its value. You might try removing > > your object directory and doing a make cleandir twice to make sure > > nothing is left in source tree that shouldn't be there. > > Yes, thats a likely candidate. Can you try blowing away /usr/obj and see > if the problem persist? > > Kris > > ---- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 17:41: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 64B8F37B8E7; Thu, 9 Mar 2000 17:41:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 628102E8155; Thu, 9 Mar 2000 17:41:02 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 9 Mar 2000 17:41:02 -0800 (PST) From: Kris Kennaway To: Benjamin Greenwald Cc: Jim Bloom , Bush Doctor , freebsd-current@freebsd.org Subject: Re: buildworld failure in cvs ... In-Reply-To: <200003100139.UAA03300@adara.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Benjamin Greenwald wrote: > I did try blowing away /obj. Didn't help. Hmm. I'll try running a buildworld at home tonight with stale libRSAglue libs in /usr/lib and see if I can reproduce this. I don't think it's anything in the source tree which is causing the breakage directly - although if it's picking up things outside /usr/obj during the course of the buildworld that needs to be fixed. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 18: 9:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 0F2F137B8FD for ; Thu, 9 Mar 2000 18:08:49 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id CAA13527; Fri, 10 Mar 2000 02:11:24 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id BAA64158; Fri, 10 Mar 2000 01:54:18 +0100 (CET) Date: Fri, 10 Mar 2000 01:54:18 +0100 (CET) From: Juergen Lock Message-Id: <200003100054.BAA64158@saturn.kn-bremen.de> To: jdp@polstra.com Subject: Re: More "ld-elf.so.1: assert failed" messages X-Newsgroups: local.list.freebsd.current In-Reply-To: <200003091645.IAA40726@vashon.polstra.com> References: <13611.952595759@zippy.cdrom.com> Organization: home Cc: jkh@zippy.cdrom.com, current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200003091645.IAA40726@vashon.polstra.com> you write: >In article <13611.952595759@zippy.cdrom.com>, >Jordan K. Hubbard wrote: >> > The other possibility would be to fix the wine port so it calls >> > dllockinit() to set up locking. I don't know for sure how hard that >> > would be, but it's probably a feasible solution. >> >> To be honest, I'd be the most comfortable with this solution >... >As far as I know, Wine is the only port that has problems with the >version of the dynamic linker that's in -current at present. I've >looked into adding the dllockinit() stuff to Wine, but could use >some help from somebody who knows its internals better. Hm you could ask over in comp.emulators.ms-windows.wine... > I found >the threads primitives, etc., but am not so sure where to place the >dllockinit() call. When does it need to be called, just when starting a new thread? (i have looked at the wine source before but never at ld-elf.so...) And would this be the same on -stable and 4.0? Currently you should be able to build a wine on a -stable box and it would still run on 4.0 (well it wouldn't run _worse_ than on -stable), at least thats the idea. Anyway if it should be called before a new thread becomes runnable for the first the i think it could go in THREAD_Create (in scheduler/thread.c), if it needs to be called from within the new thread itself it looks like it should go in THREAD_Start in the same source. HTH, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 18:12:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.originative.co.uk (mailgate.originative.co.uk [194.217.50.228]) by hub.freebsd.org (Postfix) with ESMTP id B576E37B8FC for ; Thu, 9 Mar 2000 18:12:46 -0800 (PST) (envelope-from paul@originative.co.uk) Received: from originative.co.uk (lobster.originative.co.uk [194.217.50.241]) by mail.originative.co.uk (Postfix) with ESMTP id 77FCD1D133 for ; Fri, 10 Mar 2000 02:12:45 +0000 (GMT) Message-ID: <38C85A1D.F7A21141@originative.co.uk> Date: Fri, 10 Mar 2000 02:12:45 +0000 From: Paul Richards Organization: Originative Solutions Ltd X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en-GB, en MIME-Version: 1.0 To: current@freebsd.org Subject: The pw command Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Non-root users can use the pw command to get information from the master.passwd file e.g. ps showuser paul paul:*:1000:1000::0:0:& Richards:/home/paul:/usr/local/bin/bash which shows the class, password expiry and account expiry. I'm not sure whether that's information that should be kept secure but it does seem like 'pw' is the only command that makes it available. The 'chsh' command doesn't show this information except when run as root for instance. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 18:42:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 077A937B8FD for ; Thu, 9 Mar 2000 18:42:39 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.251.241]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id VAA03232; Thu, 9 Mar 2000 21:42:22 -0500 (EST) Message-ID: <38C8610C.E17A41EF@acm.org> Date: Thu, 09 Mar 2000 21:42:20 -0500 From: Jim Bloom X-Mailer: Mozilla 4.72 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Juergen Lock Cc: jdp@polstra.com, jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: More "ld-elf.so.1: assert failed" messages References: <13611.952595759@zippy.cdrom.com> <200003100054.BAA64158@saturn.kn-bremen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NOTE: Take everything I say here as general info. I haven't used these thread packages, but have used others in the past. It should be called somewhere between the starting of the process and the creation of the second thread. There is no problem if there is only one thread. THREAD Create would be fine as long as it sets a variable accessible to all threads indicating dllockinit has been called. Another possible location would be a routine that initialize the multithreading for the process. This routine may not exist in all thread packages though. Jim Bloom bloom@acm.org Juergen Lock wrote: > > In article <200003091645.IAA40726@vashon.polstra.com> you write: > >In article <13611.952595759@zippy.cdrom.com>, > >Jordan K. Hubbard wrote: > >> > The other possibility would be to fix the wine port so it calls > >> > dllockinit() to set up locking. I don't know for sure how hard that > >> > would be, but it's probably a feasible solution. > >> > >> To be honest, I'd be the most comfortable with this solution > > >... > >As far as I know, Wine is the only port that has problems with the > >version of the dynamic linker that's in -current at present. I've > >looked into adding the dllockinit() stuff to Wine, but could use > >some help from somebody who knows its internals better. > > Hm you could ask over in comp.emulators.ms-windows.wine... > > > I found > >the threads primitives, etc., but am not so sure where to place the > >dllockinit() call. > > When does it need to be called, just when starting a new thread? > (i have looked at the wine source before but never at ld-elf.so...) > And would this be the same on -stable and 4.0? Currently you > should be able to build a wine on a -stable box and it would still > run on 4.0 (well it wouldn't run _worse_ than on -stable), at least > thats the idea. > > Anyway if it should be called before a new thread becomes > runnable for the first the i think it could go in THREAD_Create > (in scheduler/thread.c), if it needs to be called from within > the new thread itself it looks like it should go in THREAD_Start > in the same source. > > HTH, > -- > Juergen Lock > (remove dot foo from address to reply) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 18:50:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id BD12D37B8E7 for ; Thu, 9 Mar 2000 18:50:41 -0800 (PST) (envelope-from brameld@twave.net) Received: from [208.47.188.185] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id qa080304 for ; Thu, 9 Mar 2000 21:50:10 -0500 Received: from Bozo_3.BozoLand.domain (localhost [127.0.0.1]) by Bozo_3.BozoLand.domain (8.9.3/8.9.3) with SMTP id VAA01922; Thu, 9 Mar 2000 21:48:47 -0500 (EST) (envelope-from brameld@twave.net) From: Walter Brameld To: Edwin Kremer , Ishmael Subject: Re: building ports Date: Thu, 9 Mar 2000 21:48:21 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: current@FreeBSD.ORG References: <20000309145448.C23820@cs.uu.nl> In-Reply-To: <20000309145448.C23820@cs.uu.nl> MIME-Version: 1.0 Message-Id: <00030921484701.01911@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 09 Mar 2000, in a never-ending search for enlightenment, Edwin Kremer wrote: > On Mon, Mar 08, 1999 at 09:44:26PM -0600, Ishmael wrote: > > : Your system is too old to use this bsd.port.mk. > > According to the mail headers, your system clock is about one year > behind actual time. That might have screwed up the `make'... > > > Best regards, > > -- > Edwin H. Kremer, senior systems- and network administrator. > Dept. of Computer Science, Utrecht University, The Netherlands [WHOIS: ehk3] > -------------------- http://www.cs.uu.nl/people/edwin/ ----------------------- > Ya think? -- 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 19:47:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id 59CA137B88F for ; Thu, 9 Mar 2000 19:47:21 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id UAA26772 for ; Thu, 9 Mar 2000 20:09:03 -0800 (PST) Received: from wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id TAA05469 for ; Thu, 9 Mar 2000 19:38:39 -0800 (PST) (envelope-from dbutter@wireless.net) Message-ID: <38C86F70.16B7164B@wireless.net> Date: Thu, 09 Mar 2000 19:43:44 -0800 From: Devin Butterfield X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pdf MIME-Version: 1.0 To: current@freebsd.org Subject: XFree86 4.0 in FreeBSD 4.0? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Just wondering if there are plans in the works to get Xfree86 4.0 into FreeBSD 4.0. I just noticed that X 4.0 has finally been released. -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 20:18:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 2269837B8E6; Thu, 9 Mar 2000 20:18:51 -0800 (PST) (envelope-from dervish@goku.cl.msu.edu) Received: (from dervish@localhost) by goku.cl.msu.edu (8.9.3/8.9.3) id XAA50093; Thu, 9 Mar 2000 23:26:28 -0500 (EST) (envelope-from dervish) Date: Thu, 9 Mar 2000 23:26:28 -0500 From: Bush Doctor To: Kris Kennaway Cc: Benjamin Greenwald , Jim Bloom , freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure in cvs ... Message-ID: <20000309232628.A50064@goku.cl.msu.edu> References: <200003100139.UAA03300@adara.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kris@hub.freebsd.org on Thu, Mar 09, 2000 at 05:41:02PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Kris Kennaway aka (kris@hub.freebsd.org) said: > On Thu, 9 Mar 2000, Benjamin Greenwald wrote: > > > I did try blowing away /obj. Didn't help. > > Hmm. I'll try running a buildworld at home tonight with stale libRSAglue > libs in /usr/lib and see if I can reproduce this. I don't think it's > anything in the source tree which is causing the breakage directly - > although if it's picking up things outside /usr/obj during the course of > the buildworld that needs to be fixed. Not that it directly relates to the problem, I wound up doing the following to get 'make buildworld' to work: 1. rm -rf ../obj/* && make clean && make cleandepend && make cleandir && make clean && make update 2. cd secure;make obj;make depend && make all install 3. rm -rf ../obj/* && make clean && make cleandepend && make cleandir && make cleandir && make clean Again my libRSAglue libraries before the above were: bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so -> libRSAglue.so.1 -r--r--r-- 1 root wheel 5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a and after: bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* -r--r--r-- 1 root wheel 810 Mar 9 18:02 /usr/lib/libRSAglue.a lrwxr-xr-x 1 root wheel 15 Mar 9 18:02 /usr/lib/libRSAglue.so -> libRSAglue.so.1 -r--r--r-- 1 root wheel 1616 Mar 9 18:02 /usr/lib/libRSAglue.so.1 -r--r--r-- 1 root wheel 868 Mar 9 18:02 /usr/lib/libRSAglue_p.a Unfortunately I blew away the old libraries, but would like to know what happens with your test ... > > Kris > > ---- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > > #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 21:53:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from cr759667-a.nvcr1.bc.wave.home.com (cr759667-a.nvcr1.bc.wave.home.com [24.113.130.83]) by hub.freebsd.org (Postfix) with ESMTP id 904B737B8BB for ; Thu, 9 Mar 2000 21:53:36 -0800 (PST) (envelope-from fido@yaahoo.yi.org) Received: from localhost (fido@localhost) by cr759667-a.nvcr1.bc.wave.home.com (8.9.3/8.9.3) with ESMTP id VAA17364; Thu, 9 Mar 2000 21:55:58 -0800 (PST) (envelope-from fido@yaahoo.yi.org) Date: Thu, 9 Mar 2000 21:55:57 -0800 (PST) From: "Shaun (UNIX)" X-Sender: fido@cr759667-a.nvcr1.bc.wave.home.com To: fido the dog Cc: FreeBSD-current Subject: Re: ata, DMA and the install floppies In-Reply-To: <200003091901.VAA99897@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I was getting the same error, I have two HD's on a Addladin TXpro Chipset and two CD-ROM drives. I get ad1: READ command timeout -resetting ata0: resetting devices .. done ata0-slave: WARNING: WAIT_READY active=ATA_ACTIVE_ATA BUT I have no ATA hard drives. Another thing I noticed with the install, is when it is probing for devices, it was trying to find PC_card0: but I had disable PC Card support in the kernel config (the install conflict screen for the install floppies) Anyways, other then that, things are going ok with my 4.0 RC3 install. Cheers Shaun On Thu, 9 Mar 2000, John Hay wrote: > Hi, > > I have been trying to install yesterday's 4.0 snap on a no-name brand > motherboard with the VIA chipset, but I'm running in some problems. I > suspect there is a problem with the DMA. The error I'm getting when the > disk is newfs'ed is a repeating: > > ad0: WRITE command timeout - resetting > ata0: resetting devices .. done > ad0: WRITE command timeout - resetting > ata0: resetting devices .. done > ... > > It seems that it is just going on and on. Shouldn't it back down to non > DMA mode after a while? Is there a way to disable the DMA on the install > floppies? > > Part of the probe looks like this: (written down by hand) > > atapci0: port 0xe000 - 0xe00f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ... > ad0: 6204MB [13446/15/63] at ata0-master using UDMA33 > > John > -- > John Hay -- John.Hay@mikom.csir.co.za > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 22: 2:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from Millenium.kabsi.at (mx.kabelsignal.at [195.202.129.3]) by hub.freebsd.org (Postfix) with ESMTP id C687437B8BB for ; Thu, 9 Mar 2000 22:02:18 -0800 (PST) (envelope-from entropy@kabsi.at) Received: from DARKSTAR.kabsi.at ([195.202.183.28]) by Millenium.kabsi.at (8.9.3/8.9.3) with ESMTP id HAA10110; Fri, 10 Mar 2000 07:01:47 +0100 Message-Id: <4.3.2.20000310065950.01dd79e8@localhost> X-Sender: e1977a01@mail.kabsi.at X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Fri, 10 Mar 2000 07:01:54 +0100 To: as@psa.at From: Alexander Sanda Subject: Re: buildworld failure in cvs ... Cc: Bush Doctor , freebsd-current@FreeBSD.ORG In-Reply-To: References: <38C82CA1.C9467300@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 17:16 09.03.2000 -0800, Kris Kennaway wrote: > > the variable being defined and not its value. You might try removing > > your object directory and doing a make cleandir twice to make sure > > nothing is left in source tree that shouldn't be there. > >Yes, thats a likely candidate. Can you try blowing away /usr/obj and see >if the problem persist? Testa aslfdj slkdflaskdf lksflskf laksdflkas dflskf sldkfjsl lskdfj laskdjf lksdlks fskdjfls slkdfjs dlkasldk sjdlfkjs fskdjfl sdlfjslf sldjf sldfjs ldkfj To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 22:10:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 2136137B933; Thu, 9 Mar 2000 22:10:22 -0800 (PST) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id XAA60009; Thu, 9 Mar 2000 23:10:21 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id XAA00705; Thu, 9 Mar 2000 23:10:20 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14536.37324.570844.920977@whale.home-net> Date: Thu, 9 Mar 2000 23:10:20 -0700 (MST) To: qa@freebsd.org, current@freebsd.org Subject: Feedback on 4.0-RC3 (mostly good! :) X-Mailer: VM 6.73 under Emacs 20.6.1 Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, finally had a chance to frag the hard drive and install 4.0-RC3 from cdrom and see how it went. Here's my observations on the good: 1) On the same hardware as I tested 4.0-RC and 4.0-RC2 on, now I no longer get those "long ATA probes"! This is awesome! Whatever was done, is great, now the machine boots very speedily. 2) The "Standard Installation" is much better than "Novice". It was good to rename this. 3) I chose the "A" option for partition/label and good, reasonable defaults were given to me. 4) The "Standard Install" went flawlessly (despite my best attempts at pilot error :). Now observations on a few nit-picky things: 1) There is a typo (spelling error) in one of the dialogs I was presented. I was trying to force pilot error into the situation :) and got a dialog that contained the following line: "You can also chose "No" at the next prompt and go back into the installation menus to try and retry whichever operations failed." The word "chose" should be "choose." I'd supply a patch, but I only installed kernel source :( 2) Again, while trying to inject pilot error, I created a FreeBSD partition of only 10Mb and gave that as the only slice the Label editor could deal with. When I hit 'A' to have it auto-decide, it came back with a dialog box: "Unable to create root partition. Too big?" I assume by what I gave to it, that it means to say "dummy, you didn't give me a big enough slice with which to work, try again." If that is the case, perhaps a small re-write of the dialog message is in order to help explain what has gone on and a possible course of action to correct the problem--like "give me a larger slice to work with here". In all honesty, I *meant* to create a 10Gb partition and typed so fast that my brain didn't snap that "10M" != "10G" ... and thus I presented a wierd situation to the Label editor. The system is fast, GNOME+E. desktop is usable, kernel config went like a charm. Looks *real* good from where I'm sittin'. Good work to all! Let's ship this puppy. :) -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 22:16:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from MailAndNews.com (MailAndNews.com [199.29.68.160]) by hub.freebsd.org (Postfix) with ESMTP id 0309837B569 for ; Thu, 9 Mar 2000 22:16:11 -0800 (PST) (envelope-from mheffner@mailandnews.com) Received: from muriel.penguinpowered.com [208.138.199.76] (mheffner@mailandnews.com); Fri, 10 Mar 2000 01:16:05 -0500 X-WM-Posted-At: MailAndNews.com; Fri, 10 Mar 00 01:16:05 -0500 Content-Length: 1030 Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <38C85A1D.F7A21141@originative.co.uk> Date: Fri, 10 Mar 2000 01:16:39 -0500 (EST) Reply-To: Mike Heffner From: Mike Heffner To: Paul Richards Subject: RE: The pw command Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Mar-2000 Paul Richards wrote: | Non-root users can use the pw command to get information from the | master.passwd file e.g. | | ps showuser paul | paul:*:1000:1000::0:0:& Richards:/home/paul:/usr/local/bin/bash | | which shows the class, password expiry and account expiry. I'm not sure | whether that's information that should be kept secure but it does seem | like 'pw' is the only command that makes it available. The 'chsh' | command doesn't show this information except when run as root for | instance. | pw(8) uses getpwuid(3) to retrieve a password entry from the world readable /etc/pwd.db. It doesn't open master.passwd, (well at least when run as a non-superuser). IMO, that information is not something that needs to be secured. /**************************************** * Mike Heffner * * Fredericksburg, VA -- ICQ# 882073 * * Sent at: 10-Mar-2000 -- 00:58:18 EST * * http://my.ispchannel.com/~mheffner * ****************************************/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 22:18: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from cr759667-a.nvcr1.bc.wave.home.com (cr759667-a.nvcr1.bc.wave.home.com [24.113.130.83]) by hub.freebsd.org (Postfix) with ESMTP id 0DF4937B935; Thu, 9 Mar 2000 22:18:00 -0800 (PST) (envelope-from fido@yaahoo.yi.org) Received: from localhost (fido@localhost) by cr759667-a.nvcr1.bc.wave.home.com (8.9.3/8.9.3) with ESMTP id WAA17417; Thu, 9 Mar 2000 22:19:58 -0800 (PST) (envelope-from fido@yaahoo.yi.org) Date: Thu, 9 Mar 2000 22:19:58 -0800 (PST) From: "Shaun (UNIX)" X-Sender: fido@cr759667-a.nvcr1.bc.wave.home.com To: John Reynolds Cc: qa@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Feedback on 4.0-RC3 (mostly good! :) In-Reply-To: <14536.37324.570844.920977@whale.home-net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, You are using RC3 ? Hmm...I wonder why you are not getting the ATA prob problems like alot of us are. What is your system config? Yes it is FAST! and I love it....I see that the 64MB memory problem has been fix at the install level. 3.x only reads 64MB of RAM at the floppy install. 4.0 reads all of my 128MB. Cheers Shaun On Thu, 9 Mar 2000, John Reynolds wrote: > > OK, finally had a chance to frag the hard drive and install 4.0-RC3 from cdrom > and see how it went. Here's my observations on the good: > > 1) On the same hardware as I tested 4.0-RC and 4.0-RC2 on, now I no longer get > those "long ATA probes"! This is awesome! Whatever was done, is great, now > the machine boots very speedily. > > 2) The "Standard Installation" is much better than "Novice". It was good to > rename this. > > 3) I chose the "A" option for partition/label and good, reasonable defaults > were given to me. > > 4) The "Standard Install" went flawlessly (despite my best attempts at pilot > error :). > > Now observations on a few nit-picky things: > > 1) There is a typo (spelling error) in one of the dialogs I was presented. I > was trying to force pilot error into the situation :) and got a dialog that > contained the following line: > > "You can also chose "No" at the next prompt and go back into the > installation menus to try and retry whichever operations failed." > > The word "chose" should be "choose." I'd supply a patch, but I only > installed kernel source :( > > 2) Again, while trying to inject pilot error, I created a FreeBSD partition of > only 10Mb and gave that as the only slice the Label editor could deal > with. When I hit 'A' to have it auto-decide, it came back with a dialog > box: > > "Unable to create root partition. Too big?" > > I assume by what I gave to it, that it means to say "dummy, you didn't give > me a big enough slice with which to work, try again." If that is the case, > perhaps a small re-write of the dialog message is in order to help explain > what has gone on and a possible course of action to correct the > problem--like "give me a larger slice to work with here". In all honesty, I > *meant* to create a 10Gb partition and typed so fast that my brain didn't > snap that "10M" != "10G" ... and thus I presented a wierd situation to the > Label editor. > > The system is fast, GNOME+E. desktop is usable, kernel config went like a > charm. Looks *real* good from where I'm sittin'. Good work to all! Let's ship > this puppy. :) > > -Jr > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation > jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running > jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. > http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 22:25:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 9EF6937B944; Thu, 9 Mar 2000 22:25:06 -0800 (PST) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id XAA60056; Thu, 9 Mar 2000 23:25:04 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id XAA00960; Thu, 9 Mar 2000 23:25:04 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14536.38208.393729.229282@whale.home-net> Date: Thu, 9 Mar 2000 23:25:04 -0700 (MST) To: "Shaun (UNIX)" Cc: John Reynolds , qa@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Feedback on 4.0-RC3 (mostly good! :) In-Reply-To: References: <14536.37324.570844.920977@whale.home-net> X-Mailer: VM 6.73 under Emacs 20.6.1 Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Thursday, March 9, Shaun (UNIX) wrote: ] > Hello, > > You are using RC3 ? Hmm...I wonder why you are not getting the ATA prob > problems like alot of us are. What is your system config? > I'm using a P2B-DS Asus motherboard with BX chipset. Standard PIIX4 stuff. The drive is a Quantum Fireball 20.5Gb (don't have the exact model number handy). It's a UDMA66 drive but of course I'm only using UDMA33 to it ... I don't have the dmesg output handy from 4.0-RC3, but here's from 3.4-STABLE: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 Beats me, it's a pretty vanilla setup. All I know is that now when the thing boots from the cd (and after compiling a custom kernel) it doesn't sit there and "hang" for 30 seconds or so like it did before ..... ? > Yes it is FAST! and I love it....I see that the 64MB memory problem has > been fix at the install level. 3.x only reads 64MB of RAM at the floppy > install. 4.0 reads all of my 128MB. Yes, very fast ... I'm really looking forward to running it (I've been installing on a disc I can frag at will ... can't "take the plunge" until later :). -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 22:58:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from cr759667-a.nvcr1.bc.wave.home.com (cr759667-a.nvcr1.bc.wave.home.com [24.113.130.83]) by hub.freebsd.org (Postfix) with ESMTP id B755437B926 for ; Thu, 9 Mar 2000 22:58:10 -0800 (PST) (envelope-from fido@yaahoo.yi.org) Received: from localhost (fido@localhost) by cr759667-a.nvcr1.bc.wave.home.com (8.9.3/8.9.3) with ESMTP id XAA17492 for ; Thu, 9 Mar 2000 23:00:33 -0800 (PST) (envelope-from fido@yaahoo.yi.org) Date: Thu, 9 Mar 2000 23:00:33 -0800 (PST) From: "Shaun (UNIX)" X-Sender: fido@cr759667-a.nvcr1.bc.wave.home.com To: freebsd-current@freebsd.org Subject: Port apps In-Reply-To: <14536.38208.393729.229282@whale.home-net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have a question regarding ports. I noticed there was compat3x distro files, is there going to be ports that are only for FreeBSD 4.0 and will I ever run into a problem with 3.x ports not working with 4.x it was just a thought. Cheers Shaun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 23: 2:24 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id E328537B93B; Thu, 9 Mar 2000 23:02:22 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E13F22E8156; Thu, 9 Mar 2000 23:02:22 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 9 Mar 2000 23:02:22 -0800 (PST) From: Kris Kennaway To: "Shaun (UNIX)" Cc: freebsd-current@freebsd.org Subject: Re: Port apps In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Shaun (UNIX) wrote: > I noticed there was compat3x distro files, is there going to be ports that > are only for FreeBSD 4.0 Yes. > and will I ever run into a problem with 3.x ports > not working with 4.x You shouldn't do: that's what the compat3x libraries are for. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 23:13:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 0939A37B6F9 for ; Thu, 9 Mar 2000 23:13:20 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id CAA59138; Fri, 10 Mar 2000 02:12:44 -0500 (EST) Date: Fri, 10 Mar 2000 02:12:44 -0500 (EST) From: "Matthew N. Dodd" To: Devin Butterfield Cc: current@FreeBSD.ORG Subject: Re: XFree86 4.0 in FreeBSD 4.0? In-Reply-To: <38C86F70.16B7164B@wireless.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Devin Butterfield wrote: > Just wondering if there are plans in the works to get Xfree86 4.0 into > FreeBSD 4.0. I just noticed that X 4.0 has finally been released. Looks a bit green for inclusion in a release not to mention that its list of supported devices is a bit short in some areas. There are 4.0 binaries for FreeBSD 4.0 and 3.x available on ftp.xfree86.org and other mirrors so you can play around with it if you like. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 23:31:54 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id B9D5A37B6F9; Thu, 9 Mar 2000 23:31:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B7DB62E8156; Thu, 9 Mar 2000 23:31:52 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 9 Mar 2000 23:31:52 -0800 (PST) From: Kris Kennaway To: Paul Richards Cc: current@freebsd.org Subject: Re: The pw command In-Reply-To: <38C85A1D.F7A21141@originative.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Mar 2000, Paul Richards wrote: > Non-root users can use the pw command to get information from the > master.passwd file e.g. > > ps showuser paul > paul:*:1000:1000::0:0:& Richards:/home/paul:/usr/local/bin/bash % pw showuser kkenn kkenn:*:1000:0::0:0:Kris Kennaway:/home/kkenn:/usr/local/bin/tcsh % grep kkenn /etc/passwd kkenn:*:1000:0::0:0:Kris Kennaway:/home/kkenn:/usr/local/bin/tcsh % ls -l /usr/bin/pw -r-xr-xr-x 1 root wheel 53180 Mar 4 00:49 /usr/sbin/pw* In other words, pw(8) runs with no special privileges and can only read what the user can normally read. ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 9 23:40:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id ABF2B37B968 for ; Thu, 9 Mar 2000 23:40:21 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA93793; Fri, 10 Mar 2000 08:40:16 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200003100740.IAA93793@freebsd.dk> Subject: Re: mount_cd9660+atapi-cd panic In-Reply-To: <20000309233915.T62624@strontium.scientia.demon.co.uk> from Ben Smithurst at "Mar 9, 2000 11:39:15 pm" To: ben@scientia.demon.co.uk (Ben Smithurst) Date: Fri, 10 Mar 2000 08:40:16 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Ben Smithurst wrote: > ok, this was partly caused by dodgy hardware it seems, so don't worry > too much, but it would be nice if a panic could be avoided. aaiiighh! I knwo exactly what wrong, dont call make_dev early :) Thanks, that probably one of the most complete reports I've seen in a long time, makes bug hunting a breeze, thanks! Fix coming as soon as I've tested it... -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 0: 4:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id CD67337B977 for ; Fri, 10 Mar 2000 00:04:46 -0800 (PST) (envelope-from dholland@xmission.com) Received: from [204.228.142.205] (helo=xmission.com) by mail.xmission.com with esmtp (Exim 3.03 #3) id 12TKPb-0004JS-00 for freebsd-current@freebsd.org; Fri, 10 Mar 2000 01:04:43 -0700 Message-ID: <38C8ABC1.AB95F5BA@xmission.com> Date: Fri, 10 Mar 2000 01:01:05 -0700 From: David X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: 4.0-2000-03-08-SNAP and XFree86, other issues... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My Config: PIIIx2 TYAN S1836 board with dual 10k rpm Connor SCSI, 384Mb ram, and Maxtrox G200 16Meg SD ram. Ftp'd kern.flp and mfsroot.flp from current.freebsd.org (4.0-2000-03-08_Snap)... Did a clean install ... Things I noticed were: During the install, couldn't get the Crypt distribution or Local -- guess that has already been covered in the list. While the installer detected my second SCSI drive da1, for some reason when I tried to create a partition on da1 it would always show me da0 instead. X11R6 gives me an elf linker error on the XThru...so when trying to use XF86_SVGA (startx). I can see the XThru..so in the lib/aout directory but not in lib. Did the XF_SVGA get linked wrong? Misc Suggestion: I personally find the installer much more friendly than any of the competition, but one area I feel it could be improved in would be to use Accept, Close, and Cancel rather than the current Ok and Cancel. Hope this was of some help, long live BSD! (Next time I promise to learn how to use the automated bug reporting feature). David Holland dholland@xmission.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 0: 5: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5BC2D37B6F9 for ; Fri, 10 Mar 2000 00:05:01 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA99578; Fri, 10 Mar 2000 09:04:55 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200003100804.JAA99578@freebsd.dk> Subject: Re: RC3 install floppies: panic: resource_list_alloc: resource entry is busy In-Reply-To: <38C81F71.6CBD66B3@iae.nl> from Hans Ottevanger at "Mar 9, 2000 11:02:25 pm" To: hansot@iae.nl (Hans Ottevanger) Date: Fri, 10 Mar 2000 09:04:55 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Hans Ottevanger wrote: > Hi folks, > > I just tried to boot the RC3 install floppies on my Pentium 66 testbox. > It gets through the config stage without trouble, but then panics > immediately with: > > ... > pcib0: on motherboard > pci0: on pcib0 > atapci0: possible> port 0 > x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 > atapci0: Busmastering DMA not supported > panic: resource_list_alloc: resource entry is busy > > I am also having this problem with 4.0-CURRENT kernels since February > 18, both with my own custom kernel config and GENERIC. > I have to revert to the ata driver of February 17 or earlier to get the > system booting again, and then it runs perfectly. Hmm, seems to be a resource conflict problem, question is what is causing this. Could you do a verbose boot both with the old working kernel, and the new failing one ? > This machine has an Intel motherboard with a Mercury chipset, 64 Mbyte > RAM, Matrox Millenium II, two Western Digital disks, and it ran all > previous FreeBSD releases perfectly for almost five years. Yeah I notice the RZ 1000 chips in there, BE CAREFULL, I wouldn't use this for anything I cared about... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 0:56:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id E559E37B98B for ; Fri, 10 Mar 2000 00:56:45 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip234.r4.d.bel.nwlink.com (ip234.r4.d.bel.nwlink.com [207.202.172.234]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id AAA16517 for ; Fri, 10 Mar 2000 00:56:44 -0800 (PST) Date: Fri, 10 Mar 2000 00:51:06 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: freebsd-current@FreeBSD.org Subject: single user mode problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has been going on for awhile, and I've looked everywhere for a solution. When I boot single user, the / filesystem gets mounted on wd0s4a even though /dev does not even have such an entry nor does /etc/fstab, since these have all been updated. This is not really such a problem until I try to exit from single user mode. Then, it tries to remount / on ad0s4a and can't find it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 1:17: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id 5836137B99B; Fri, 10 Mar 2000 01:17:01 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 12TLXT-000PKN-0B; Fri, 10 Mar 2000 09:16:56 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA49689; Fri, 10 Mar 2000 09:23:17 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 10 Mar 2000 09:19:13 +0000 (GMT) From: Doug Rabson To: Peter Jeremy Cc: Mikhail Teterin , current@freebsd.org, alpha@freebsd.org Subject: Re: SMP on Alpha? In-Reply-To: <00Mar10.123332est.115241@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Mar 2000, Peter Jeremy wrote: > On 2000-Mar-10 12:06:18 +1100, Mikhail Teterin wrote: > >Will the -current version of FreeBSD run on a multi-CPU axp machine and > >use all of the CPUs? > > Not yet, but Real Soon Now. > > > Would that be a reliable box (assuming the admin > >sometimes knows what he is doing)? > > -current comes with all the usual `not for production use' caveats, > and (without any slur on Doug Rabson, who's doing the work), you'd > be very game taking FreeBSD's first cut at Alpha/SMP and putting it > into production. On the other hand, a uniprocessor alpha has a decent amount of horsepower and should be suitable for use in production. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 1:42:31 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 4AF2C37B98C; Fri, 10 Mar 2000 01:42:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 48E742E8157; Fri, 10 Mar 2000 01:42:30 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 10 Mar 2000 01:42:30 -0800 (PST) From: Kris Kennaway To: Bush Doctor Cc: Benjamin Greenwald , Jim Bloom , freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure in cvs ... In-Reply-To: <20000309232628.A50064@goku.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Bush Doctor wrote: > Again my libRSAglue libraries before the above were: > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a > lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so -> libRSAglue.so.1 > -r--r--r-- 1 root wheel 5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 > -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a This was very helpful - I've been able to replicate the problem by install an old libRSAglue of this vintage. It still doesn't answer why on earth make world is trying to link with it, but at least now I have something to look at. Thanks! Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 2: 3:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by hub.freebsd.org (Postfix) with ESMTP id 2893037B99C for ; Fri, 10 Mar 2000 02:03:38 -0800 (PST) (envelope-from bartequi@neomedia.it) Received: from bartequi.ottodomain.org (ppp40-pa4.neomedia.it [195.103.207.232]) by aragorn.neomedia.it (8.9.3/8.9.3) with SMTP id LAA32722; Fri, 10 Mar 2000 11:03:26 +0100 (CET) From: Salvo Bartolotta Date: Fri, 10 Mar 2000 10:06:49 GMT Message-ID: <20000310.10064900@bartequi.ottodomain.org> Subject: Re: single user mode problem To: R Joseph Wright , freebsd-current@FreeBSD.ORG References: X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 3/10/00, 9:51:06 AM, R Joseph Wright wrote regarding single user mode problem: > This has been going on for awhile, and I've looked everywhere for a > solution. When I boot single user, the / filesystem gets mounted on > wd0s4a even though /dev does not even have such an entry nor does > /etc/fstab, since these have all been updated. > This is not really such a problem until I try to exit from single user= > mode. Then, it tries to remount / on ad0s4a and can't find it. Dear Joseph, as I have recently written, I met an analogous problem while upgrading to CURRENT: the "wdNsMa syndrome" appeared when I rebooted in s.u.m. with the shining gleaming roaring freshly-made 4.0-CURRENT kernel in order to (somehow) make installworld. Well, I did NOT care about it and I went ahead ruthlessly ... By the way, I made another kernel at the end of the process ("by the book"). I suppose (?) this cleared the problem. In fact, I was able to boot with no weird messages: all my filesystems were correctly identified as adNsM (e.g. ad1s2a, ad1s2e ...) HTH, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 2:14:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from www.menzor.dk (themoonismadeofgreenchease.dk [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id 3797D37B924 for ; Fri, 10 Mar 2000 02:14:50 -0800 (PST) (envelope-from ml@seeberg.dk) Received: from sos (fw.merkantildata.dk [194.239.79.3]) by www.menzor.dk (8.8.8/8.8.8) with SMTP id LAA03773; Fri, 10 Mar 2000 11:14:45 +0100 (CET) (envelope-from ml@seeberg.dk) Message-ID: <004c01bf8a79$f8f7f9a0$3500a8c0@sos> Reply-To: "Morten Seeberg" From: "Morten Seeberg" To: "Oliver Schonefeld" , References: <200001011616.RAA23768@frizzantino.TechFak.Uni-Bielefeld.DE> Subject: Re: ida driver in -current and eisa bus attachment Date: Fri, 10 Mar 2000 11:18:22 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Work on this driver is stalled owing to the fact that nobody that can and > > wants to work on it has access to the Compaq hardware required. You > > can't use these controllers except in Compaq systems, which makes things > > very difficult. > that's true :-( Again I would like to point out, that only the newest controllers, 3200 and up is difficult getting to work in non-Compaq systems: http://seeberg.dk/freebsd/idaraid To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 2:51:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.esil.univ-mrs.fr (jiyu.esil.univ-mrs.fr [139.124.44.249]) by hub.freebsd.org (Postfix) with ESMTP id 71C7F37B99C for ; Fri, 10 Mar 2000 02:51:49 -0800 (PST) (envelope-from la.firme@esil.univ-mrs.fr) Received: from esil.univ-mrs.fr (root@dopici.esil.univ-mrs.fr [139.124.32.246]) by mailhost.esil.univ-mrs.fr (8.9.3/ESIL/jtpda-5.3.1) with ESMTP id LAA62024 for ; Fri, 10 Mar 2000 11:51:42 +0100 (CET) Message-ID: <38C8D3BE.15F17D29@esil.univ-mrs.fr> Date: Fri, 10 Mar 2000 10:51:42 +0000 From: =?iso-8859-1?Q?J=E9rome?= OUFELLA Organization: ESIL X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: 3.4 vs. 4.0 NFS Code performance Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I need to use a quite big NFS server, serving ~120GB for ~200 clients, all OS's mixed (*BSD, Linux, HP-UX, IRIX, Solaris, Xterminals). Is it worth it to use the -current branch (-release on next monday perhaps?) for this important server, or should I rather use the 3.4-STABLE NFS implementation ? Thanks for all the tips you could give me. Jerome Oufella Network administration team ESIL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 3: 2:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 9F0BF37B993 for ; Fri, 10 Mar 2000 03:02:03 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id NAA19693 for freebsd-current@FreeBSD.ORG; Fri, 10 Mar 2000 13:01:54 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200003101101.NAA19693@zibbi.mikom.csir.co.za> Subject: USA_RESIDENT and sysinstall To: freebsd-current@FreeBSD.ORG (FreeBSD-current) Date: Fri, 10 Mar 2000 13:01:54 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I installed a -current snap from internat.freebsd.org that was built with crypto source from internat. I answered yes when sysinstall asked me if I want the crypto stuff, but then found that it marked me as an USA_RESIDENT=YES in /etc/make.conf and it also asked me later if I want to install the rsaref libraries. I think the test for USA_RESIDENT should be a bit more clever or the message should be a bit more clear. At the moment it is: -------- Do you wish to install cryptographic software? If you choose No, FreeBSD will use an MD5 based password scheme which, while perhaps more secure, is not interoperable with the traditional DES-based passwords on other Unix systems. There will also be some differences in the type of RSA code you use. Please do NOT choose Yes at this point if you are outside the United States and Canada and are installing from a U.S. FTP server. Instead, install everything but the crypto bits from the U.S. site and then switch to an international FTP server to install crypto on a second pass with the Custom Installation option. -------- Maybe we can have some kind of flag in the crypto distribution to mark if it is USA or non-USA and use that to decide how to set USA_RESIDENT or maybe someone clever enough can figure out if the dowloaded crypto libraries still need rsaref and use that to set it? Also it would be nice to have an option to install the crypto ditribution (to get openssh) but still have md5 passwords, ie. the libcrypt.* links don't get extracted out of the crypto distribution or something can just link them back to libscrypt.*. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 3: 8:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id B6EA237B9CF for ; Fri, 10 Mar 2000 03:08:46 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id UAA17833; Fri, 10 Mar 2000 20:08:12 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id UAA05968; Fri, 10 Mar 2000 20:08:11 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id UAA20283; Fri, 10 Mar 2000 20:08:10 +0900 (JST) To: itojun@iijlab.net Cc: dick@tar.com, fink@es.net, ab@astralblue.com, fenner@research.att.com, jose@we.lc.ehu.es, current@FreeBSD.ORG, 6bone@ISI.EDU Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? In-Reply-To: <24051.952462663@coconut.itojun.org> References: <20000307102628S.shin@nd.net.fujitsu.co.jp> <24051.952462663@coconut.itojun.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000310200904T.shin@nd.net.fujitsu.co.jp> Date: Fri, 10 Mar 2000 20:09:04 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 208 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Very unfortunately, 6to4 is not yet supported in FreeBSD/KAME. > >So now available options will be, > > -Use freenet6 (for one hosts). > > -Get IPv6 address block and connect to 6bone using gif tunnel. > > We hope to add 6to4 support for KAME/FreeBSD very soon (next week is a > good guess). We may need some more testing before real use, > but it should work. it is in KAME/NetBSD already, I just don't have > time to make it work on othre *BSDs yet... 6to4 support seems to be very important for initial IPv6 deployment on FreeBSD4.0, so I tried small additinal patches to make it available. And It seems to work. Could some FreeBSD4.0 user with direct internet connectivity please try this patches and try to ping6 to my host's 6to4 address? The procedure is, (1)apply this patch and rebuild your kernel (2)configure 6to4 interface I suppose that your IPv4 address is 1.2.3.4 -configure stf interface's outer addr, using gifconfig gifconfig stf0 1.2.3.4 255.255.255.255 (The destination IPv4 addr can be anything.) -encode your IPv4 address to hex format per 2 byte, for later use If it is 1.2.3.4, then it will be, 0102:0304. -encode your IPv6 address on stf interface, for later configuration The format is, like below. 2002: 4byte v4 addr : 2byte SLA ID : 8byte interface ID For simplicity, I choose 0 for SLA ID, and 1 for interface ID. Then, if your IPv4 addr is 1.2.3.4, then your IPv6 addr on stf is, 2002:0102:0304::1 -configure stf interface's IPv6 addr Please use ifconfig. ifconfig stf0 inet6 2002:0102:0304::1 prefixlen 16 (3)try pinging to my host's 6to4 address My machine's 6to4 address is 2002:cbb2:8dd8::1. Please try, ping6 2002:cbb2:8dd8::1 I hope there is reply from my machine. And here is the patches. Thanks, Yoshinobu Inoue Index: net/if_gif.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_gif.c,v retrieving revision 1.3 diff -u -r1.3 if_gif.c --- net/if_gif.c 2000/02/27 18:36:30 1.3 +++ net/if_gif.c 2000/03/10 10:09:25 @@ -83,7 +83,7 @@ /* * gif global variable definitions */ -int ngif = NGIF; /* number of interfaces */ +int ngif = NGIF + 1; /* number of interfaces. +1 for stf. */ struct gif_softc *gif = 0; void @@ -95,7 +95,7 @@ gif = sc = malloc (ngif * sizeof(struct gif_softc), M_DEVBUF, M_WAIT); bzero(sc, ngif * sizeof(struct gif_softc)); - for (i = 0; i < ngif; sc++, i++) { + for (i = 0; i < ngif - 1; sc++, i++) { /* leave last one for stf */ sc->gif_if.if_name = "gif"; sc->gif_if.if_unit = i; sc->gif_if.if_mtu = GIF_MTU; @@ -107,6 +107,16 @@ if_attach(&sc->gif_if); bpfattach(&sc->gif_if, DLT_NULL, sizeof(u_int)); } + sc->gif_if.if_name = "stf"; + sc->gif_if.if_unit = 0; + sc->gif_if.if_mtu = GIF_MTU; + sc->gif_if.if_flags = IFF_MULTICAST; + sc->gif_if.if_ioctl = gif_ioctl; + sc->gif_if.if_output = gif_output; + sc->gif_if.if_type = IFT_GIF; + sc->gif_if.if_snd.ifq_maxlen = ifqmaxlen; + if_attach(&sc->gif_if); + bpfattach(&sc->gif_if, DLT_NULL, sizeof(u_int)); } PSEUDO_SET(gifattach, if_gif); @@ -322,6 +332,11 @@ /* only one gif can have dst = INADDR_ANY */ #define satosaddr(sa) (((struct sockaddr_in *)(sa))->sin_addr.s_addr) + +#ifdef INET6 + if (bcmp(ifp->if_name, "stf", 3) == 0) + satosaddr(dst) = INADDR_BROADCAST; +#endif if (satosaddr(dst) == INADDR_ANY) { int i; Index: netinet/in_gif.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/in_gif.c,v retrieving revision 1.3 diff -u -r1.3 in_gif.c --- netinet/in_gif.c 1999/12/22 19:13:18 1.3 +++ netinet/in_gif.c 2000/03/10 10:09:25 @@ -84,6 +84,9 @@ SYSCTL_INT(_net_inet_ip, IPCTL_GIF_TTL, gifttl, CTLFLAG_RW, &ip_gif_ttl, 0, ""); +#define IN6_IS_ADDR_6TO4(x) (ntohs((x)->s6_addr16[0]) == 0x2002) +#define GET_V4(x) ((struct in_addr *)(&(x)->s6_addr16[1])) + int in_gif_output(ifp, family, m, rt) struct ifnet *ifp; @@ -98,6 +101,9 @@ struct ip iphdr; /* capsule IP header, host byte ordered */ int proto, error; u_int8_t tos; +#ifdef INET6 + struct ip6_hdr *ip6 = NULL; +#endif if (sin_src == NULL || sin_dst == NULL || sin_src->sin_family != AF_INET || @@ -124,7 +130,6 @@ #ifdef INET6 case AF_INET6: { - struct ip6_hdr *ip6; proto = IPPROTO_IPV6; if (m->m_len < sizeof(*ip6)) { m = m_pullup(m, sizeof(*ip6)); @@ -147,6 +152,24 @@ bzero(&iphdr, sizeof(iphdr)); iphdr.ip_src = sin_src->sin_addr; +#ifdef INET6 + /* XXX: temporal stf support hack */ + if (bcmp(ifp->if_name, "stf", 3) == 0 && ip6 != NULL) { + if (IN6_IS_ADDR_6TO4(&ip6->ip6_dst)) + iphdr.ip_dst = *GET_V4(&ip6->ip6_dst); + else if (rt && rt->rt_gateway->sa_family == AF_INET6) { + struct in6_addr *dst6; + + dst6 = &((struct sockaddr_in6 *) + (rt->rt_gateway))->sin6_addr; + if (IN6_IS_ADDR_6TO4(dst6)) + iphdr.ip_dst = *GET_V4(dst6); + } else { + m_freem(m); + return ENETUNREACH; + } + } else +#endif if (ifp->if_flags & IFF_LINK0) { /* multi-destination mode */ if (sin_dst->sin_addr.s_addr != INADDR_ANY) @@ -232,6 +255,17 @@ if ((sc->gif_if.if_flags & IFF_UP) == 0) continue; + +#ifdef INET6 + /* XXX: temporal stf support hack */ + if (proto == IPPROTO_IPV6 && + bcmp(sc->gif_if.if_name, "stf", 3) == 0 && + satosin(sc->gif_psrc)->sin_addr.s_addr == + ip->ip_dst.s_addr) { + gifp = &sc->gif_if; + break; + } +#endif if ((sc->gif_if.if_flags & IFF_LINK0) && satosin(sc->gif_psrc)->sin_addr.s_addr == ip->ip_dst.s_addr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 3:39:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id AB14537B9EB for ; Fri, 10 Mar 2000 03:39:13 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id UAA13224; Fri, 10 Mar 2000 20:38:30 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id UAA27518; Fri, 10 Mar 2000 20:38:29 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id UAA20733; Fri, 10 Mar 2000 20:38:28 +0900 (JST) To: itojun@iijlab.net Cc: dick@tar.com, fink@es.net, ab@astralblue.com, fenner@research.att.com, jose@we.lc.ehu.es, current@FreeBSD.ORG, 6bone@ISI.EDU Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? In-Reply-To: <20000310200904T.shin@nd.net.fujitsu.co.jp> References: <20000307102628S.shin@nd.net.fujitsu.co.jp> <24051.952462663@coconut.itojun.org> <20000310200904T.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000310203922A.shin@nd.net.fujitsu.co.jp> Date: Fri, 10 Mar 2000 20:39:22 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 142 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And here is the patches. The last patches should work but I found a improvement related to coexistence with gif, so this is the updated patches. Thanks, Yoshinobu Inoue Index: net/if_gif.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_gif.c,v retrieving revision 1.3 diff -u -r1.3 if_gif.c --- net/if_gif.c 2000/02/27 18:36:30 1.3 +++ net/if_gif.c 2000/03/10 11:32:38 @@ -83,7 +83,7 @@ /* * gif global variable definitions */ -int ngif = NGIF; /* number of interfaces */ +int ngif = NGIF + 1; /* number of interfaces. +1 for stf. */ struct gif_softc *gif = 0; void @@ -95,7 +95,7 @@ gif = sc = malloc (ngif * sizeof(struct gif_softc), M_DEVBUF, M_WAIT); bzero(sc, ngif * sizeof(struct gif_softc)); - for (i = 0; i < ngif; sc++, i++) { + for (i = 0; i < ngif - 1; sc++, i++) { /* leave last one for stf */ sc->gif_if.if_name = "gif"; sc->gif_if.if_unit = i; sc->gif_if.if_mtu = GIF_MTU; @@ -107,6 +107,16 @@ if_attach(&sc->gif_if); bpfattach(&sc->gif_if, DLT_NULL, sizeof(u_int)); } + sc->gif_if.if_name = "stf"; + sc->gif_if.if_unit = 0; + sc->gif_if.if_mtu = GIF_MTU; + sc->gif_if.if_flags = IFF_MULTICAST; + sc->gif_if.if_ioctl = gif_ioctl; + sc->gif_if.if_output = gif_output; + sc->gif_if.if_type = IFT_GIF; + sc->gif_if.if_snd.ifq_maxlen = ifqmaxlen; + if_attach(&sc->gif_if); + bpfattach(&sc->gif_if, DLT_NULL, sizeof(u_int)); } PSEUDO_SET(gifattach, if_gif); @@ -322,6 +332,11 @@ /* only one gif can have dst = INADDR_ANY */ #define satosaddr(sa) (((struct sockaddr_in *)(sa))->sin_addr.s_addr) + +#ifdef INET6 + if (bcmp(ifp->if_name, "stf", 3) == 0) + satosaddr(dst) = INADDR_BROADCAST; +#endif if (satosaddr(dst) == INADDR_ANY) { int i; Index: netinet/in_gif.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/in_gif.c,v retrieving revision 1.3 diff -u -r1.3 in_gif.c --- netinet/in_gif.c 1999/12/22 19:13:18 1.3 +++ netinet/in_gif.c 2000/03/10 11:32:38 @@ -84,6 +84,9 @@ SYSCTL_INT(_net_inet_ip, IPCTL_GIF_TTL, gifttl, CTLFLAG_RW, &ip_gif_ttl, 0, ""); +#define IN6_IS_ADDR_6TO4(x) (ntohs((x)->s6_addr16[0]) == 0x2002) +#define GET_V4(x) ((struct in_addr *)(&(x)->s6_addr16[1])) + int in_gif_output(ifp, family, m, rt) struct ifnet *ifp; @@ -98,6 +101,9 @@ struct ip iphdr; /* capsule IP header, host byte ordered */ int proto, error; u_int8_t tos; +#ifdef INET6 + struct ip6_hdr *ip6 = NULL; +#endif if (sin_src == NULL || sin_dst == NULL || sin_src->sin_family != AF_INET || @@ -124,7 +130,6 @@ #ifdef INET6 case AF_INET6: { - struct ip6_hdr *ip6; proto = IPPROTO_IPV6; if (m->m_len < sizeof(*ip6)) { m = m_pullup(m, sizeof(*ip6)); @@ -147,6 +152,24 @@ bzero(&iphdr, sizeof(iphdr)); iphdr.ip_src = sin_src->sin_addr; +#ifdef INET6 + /* XXX: temporal stf support hack */ + if (bcmp(ifp->if_name, "stf", 3) == 0 && ip6 != NULL) { + if (IN6_IS_ADDR_6TO4(&ip6->ip6_dst)) + iphdr.ip_dst = *GET_V4(&ip6->ip6_dst); + else if (rt && rt->rt_gateway->sa_family == AF_INET6) { + struct in6_addr *dst6; + + dst6 = &((struct sockaddr_in6 *) + (rt->rt_gateway))->sin6_addr; + if (IN6_IS_ADDR_6TO4(dst6)) + iphdr.ip_dst = *GET_V4(dst6); + } else { + m_freem(m); + return ENETUNREACH; + } + } else +#endif if (ifp->if_flags & IFF_LINK0) { /* multi-destination mode */ if (sin_dst->sin_addr.s_addr != INADDR_ANY) @@ -232,6 +255,19 @@ if ((sc->gif_if.if_flags & IFF_UP) == 0) continue; + +#ifdef INET6 + /* XXX: temporal stf support hack */ + if (proto == IPPROTO_IPV6 && + bcmp(sc->gif_if.if_name, "stf", 3) == 0 && + satosin(sc->gif_psrc)->sin_addr.s_addr == + ip->ip_dst.s_addr && + satosin(sc->gif_pdst)->sin_addr.s_addr == + INADDR_BROADCAST) { + gifp = &sc->gif_if; + break; + } +#endif if ((sc->gif_if.if_flags & IFF_LINK0) && satosin(sc->gif_psrc)->sin_addr.s_addr == ip->ip_dst.s_addr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 5:15:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from waldorf.cs.uni-dortmund.de (waldorf.cs.uni-dortmund.de [129.217.4.42]) by hub.freebsd.org (Postfix) with ESMTP id EFD1B37BA35 for ; Fri, 10 Mar 2000 05:15:05 -0800 (PST) (envelope-from Kai.Grossjohann@CS.Uni-Dortmund.DE) Received: from marcy.cs.uni-dortmund.de (marcy.cs.uni-dortmund.de [129.217.20.159]) by waldorf.cs.uni-dortmund.de with ESMTP id OAA16660; Fri, 10 Mar 2000 14:14:26 +0100 (MET) Received: from lucy.cs.uni-dortmund.de (lucy [129.217.20.160]) by marcy.cs.uni-dortmund.de id OAA25728; Fri, 10 Mar 2000 14:14:25 +0100 (MET) Received: (from grossjoh@localhost) by lucy.cs.uni-dortmund.de (8.9.3/8.9.3/Debian 8.9.3-6) id OAA25175; Fri, 10 Mar 2000 14:14:25 +0100 X-Authentication-Warning: lucy.cs.uni-dortmund.de: grossjoh set sender to Kai.Grossjohann@CS.Uni-Dortmund.DE using -f To: freebsd@mrynet.com (FreeBSD mailing list) Cc: freebsd-current@FreeBSD.ORG Subject: Re: sshd in current....no config files in /etc/ssh References: <200003072002.MAA09569@mrynet.com> From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai=?iso-8859-1?q?_Gro=DFjohann?=) Date: 10 Mar 2000 14:14:25 +0100 In-Reply-To: freebsd@mrynet.com's message of "Tue, 7 Mar 2000 12:02:38 +0000" Message-ID: Lines: 13 User-Agent: Gnus/5.0804 (Gnus v5.8.4) Emacs/20.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG freebsd@mrynet.com (FreeBSD mailing list) writes: > You know people, it's quite sad that those with knowledge simply > refuse to answer simple questions without "RTFM" attitudes and > indirect (and more frequently direct) insults to intelligence and > sensibilities. The answer `run mergemaster' will work for the next, similar, problem. The answer you gave won't work for anything but ssh. kai -- ~/.signature: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 5:15:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id C611137BA55; Fri, 10 Mar 2000 05:15:06 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id IAA00910; Fri, 10 Mar 2000 08:15:00 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38C8F554.A1C004C6@acm.org> Date: Fri, 10 Mar 2000 08:15:00 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Reynolds Cc: qa@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Feedback on 4.0-RC3 (mostly good! :) References: <14536.37324.570844.920977@whale.home-net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Reynolds wrote: > 1) There is a typo (spelling error) in one of the dialogs I was presented. I > was trying to force pilot error into the situation :) and got a dialog that > contained the following line: > > "You can also chose "No" at the next prompt and go back into the > installation menus to try and retry whichever operations failed." > > The word "chose" should be "choose." I'd supply a patch, but I only > installed kernel source :( > Also, this sentence should either have "try and" removed or replaced with "attempt to". Either of these is much better grammatically. Jim Bloom bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 5:36: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 5772437BB4A for ; Fri, 10 Mar 2000 05:35:57 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id HAA20801; Fri, 10 Mar 2000 07:35:08 -0600 (CST) (envelope-from dick) Date: Fri, 10 Mar 2000 07:35:08 -0600 From: "Richard Seaman, Jr." To: Yoshinobu Inoue Cc: itojun@iijlab.net, fink@es.net, ab@astralblue.com, fenner@research.att.com, jose@we.lc.ehu.es, current@FreeBSD.ORG, 6bone@ISI.EDU Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? Message-ID: <20000310073508.I302@tar.com> References: <20000307102628S.shin@nd.net.fujitsu.co.jp> <24051.952462663@coconut.itojun.org> <20000310200904T.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000310200904T.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Fri, Mar 10, 2000 at 08:09:04PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 10, 2000 at 08:09:04PM +0900, Yoshinobu Inoue wrote: > 6to4 support seems to be very important for initial IPv6 > deployment on FreeBSD4.0, so I tried small additinal patches > to make it available. And It seems to work. > > Could some FreeBSD4.0 user with direct internet connectivity > please try this patches and try to ping6 to my host's 6to4 > address? > The procedure is, For the benefit of the lists, and confirming private mail I sent, ping6 works using the second of the patches sent (I didn't try the first). -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 6:26:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.originative.co.uk (mailgate.originative.co.uk [194.217.50.228]) by hub.freebsd.org (Postfix) with ESMTP id 27F4237B51E for ; Fri, 10 Mar 2000 06:26:09 -0800 (PST) (envelope-from paul@originative.co.uk) Received: from originative.co.uk (lobster.originative.co.uk [194.217.50.241]) by mail.originative.co.uk (Postfix) with ESMTP id A54C21D132; Fri, 10 Mar 2000 14:26:06 +0000 (GMT) Message-ID: <38C905FE.10C5E591@originative.co.uk> Date: Fri, 10 Mar 2000 14:26:06 +0000 From: Paul Richards Organization: Originative Solutions Ltd X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en-GB, en MIME-Version: 1.0 To: Kris Kennaway Cc: current@freebsd.org Subject: Re: The pw command References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Fri, 10 Mar 2000, Paul Richards wrote: > > > Non-root users can use the pw command to get information from the > > master.passwd file e.g. > > > > ps showuser paul > > paul:*:1000:1000::0:0:& Richards:/home/paul:/usr/local/bin/bash > > % pw showuser kkenn > > kkenn:*:1000:0::0:0:Kris Kennaway:/home/kkenn:/usr/local/bin/tcsh > > % grep kkenn /etc/passwd > > kkenn:*:1000:0::0:0:Kris Kennaway:/home/kkenn:/usr/local/bin/tcsh > > % ls -l /usr/bin/pw > -r-xr-xr-x 1 root wheel 53180 Mar 4 00:49 /usr/sbin/pw* > > In other words, pw(8) runs with no special privileges and can only read > what the user can normally read. Ok, as Mike mentioned in his email pw gets its info from pwd.db, I knew that. What I had assumed was that pwd.db was the same as the contents of /etc/passwd. I spent most of last night trying to work out how a non-root user was getting access to master.passwd based on that flawed assumption :-) My /etc/passwd does not have the class and expiry fields in it. I've deleted it and let it be recreated and it still doesn't have those fields. I've browsed through the code in pwd_mkdb and it looks to me like it deliberately creates the old style /etc/passwd file, which makes sense from a comatibility perspective. So what I'm puzzled about now is how come yours is different and do we think its correct that pwd.db and /etc/passwd have different information in them? Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 6:36:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id DF64D37B9AF for ; Fri, 10 Mar 2000 06:36:44 -0800 (PST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id PAA00524 for ; Fri, 10 Mar 2000 15:37:09 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Fri, 10 Mar 2000 15:37:09 +0100 (CET) From: "O. Hartmann" To: freebsd-current@freebsd.org Subject: RAID 5 Failure dumps all terminals Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We use A Mylex DAC960PD RAID 5 controller, attached to 7 harddrives. One of the drives have had permanent failures, so we changed it. Well, as I understand RAID 5, rebuilding the defective drive should not involve the system, but On console (it ttyv0) I get a message like "mlx0: error reading message log - invalid log entry request". On all other ttyv* a logged in user (root) gets the same message from kernel. Is this eloquence of the kernel and the mlx-driver a preliminary feature or is the code still buggy, instable or anything else? I feel a little bit confused about that, while other systems using RAID 5 are completely quiet while rebuilding the defective and changed device. On the other hand, how can I redirect console output to another console, on which nobody never can log in (it should not be ttyv0)? How to prevent users and root on some ttyv* from getting that much error messages, except on a bunch of declared ttys? Thanks in advance ... Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 6:58:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 1870037BA1E for ; Fri, 10 Mar 2000 06:58:32 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id JAA45750; Fri, 10 Mar 2000 09:01:40 -0600 (CST) (envelope-from jlemon) Date: Fri, 10 Mar 2000 09:01:40 -0600 (CST) From: Jonathan Lemon Message-Id: <200003101501.JAA45750@prism.flugsvamp.com> To: ml@seeberg.dk, current@freebsd.org Subject: Re: ida driver in -current and eisa bus attachment X-Newsgroups: local.mail.freebsd-current In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >> > Work on this driver is stalled owing to the fact that nobody that can >and >> > wants to work on it has access to the Compaq hardware required. You >> > can't use these controllers except in Compaq systems, which makes things >> > very difficult. >> that's true :-( > >Again I would like to point out, that only the newest controllers, 3200 and >up is difficult getting to work in non-Compaq systems: > >http://seeberg.dk/freebsd/idaraid Note that I just committed some more changes to the IDA driver to 4.0-RC yesterday. The changes are: - support for EISA controllers (untested) - support for newer S2400 controllers (untested) - addition of IDA to the GENERIC kernel - support for installing directly onto the RAID array. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 7:18:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.aracnet.com (mail2.aracnet.com [216.99.193.35]) by hub.freebsd.org (Postfix) with ESMTP id 1193537B9E8 for ; Fri, 10 Mar 2000 07:18:46 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (shell1.aracnet.com [216.99.193.21]) by mail2.aracnet.com (8.9.3/8.9.3) with ESMTP id HAA03735 for ; Fri, 10 Mar 2000 07:18:55 -0800 Received: by shell1.aracnet.com (8.9.3) id HAA24350; Fri, 10 Mar 2000 07:21:15 -0800 Date: Fri, 10 Mar 2000 07:21:15 -0800 (PST) From: Brian Beattie To: freebsd-current@freebsd.org Subject: RC3 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A couple of comments on the RC3 CD image. 1) I tried to install by moving things out od the way: cd /;mkdir save;mv * save;cd /usr;mkdir save;mv * save and then boot from CD. Because I did not newfs /, it assumed /dev was built and failed. 2) When I tried to install CRYPTO from the CD I got errors for a number of them, something about not being able to read a script of something (it was 2am so I do not have the exact error message), so i installed from FTP. 3) First time i declined DES because I did not want DES passwords, hoping it would install crypto (ssl, ssh) or would ask me. Over the install went well, I will finish configuring tonight and see how it goes. Brian Beattie | This email was produced using professional quality, beattie@aracnet.com | standards based software. Users of Microsoft beattie@aracnet.com | 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 7:21:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 5D3E537B9CC for ; Fri, 10 Mar 2000 07:21:22 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id KAA66327; Fri, 10 Mar 2000 10:21:15 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200003101521.KAA66327@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 10 Mar 2000 10:21:15 -0500 (EST) From: John Baldwin To: current@FreeBSD.org Subject: inetd broken w/o INET6 Cc: oogali@intranova.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It appears inetd is broken if you don't have INET6 defined. This is the case for picoBSD, for example: > make -DRELEASE_CRUNCH cc -O -pipe -Wall -DLOGIN_CAP -c /usr/source/src/usr.sbin/inetd/inetd.c /usr/source/src/usr.sbin/inetd/inetd.c: In function `getconfigent': /usr/source/src/usr.sbin/inetd/inetd.c:1594: syntax error before `else' /usr/source/src/usr.sbin/inetd/inetd.c:1435: warning: unused variable `s' /usr/source/src/usr.sbin/inetd/inetd.c:1434: warning: unused variable `argc' /usr/source/src/usr.sbin/inetd/inetd.c: At top level: /usr/source/src/usr.sbin/inetd/inetd.c:1601: syntax error before `->' /usr/source/src/usr.sbin/inetd/inetd.c:1601: warning: type defaults to `int' in declaration of `se_family' /usr/source/src/usr.sbin/inetd/inetd.c:1601: warning: data definition has no type or storage class /usr/source/src/usr.sbin/inetd/inetd.c:1602: syntax error before `}' *** Error code 1 Stop in /usr/source/src/usr.sbin/inetd. I've fixed this and another INET6-related warning with this patch: Index: builtins.c =================================================================== RCS file: /usr/cvs/src/usr.sbin/inetd/builtins.c,v retrieving revision 1.17 diff -u -r1.17 builtins.c --- builtins.c 2000/01/25 14:52:09 1.17 +++ builtins.c 2000/03/10 15:13:35 @@ -335,7 +335,9 @@ struct utsname un; struct stat sb; struct sockaddr_in sin[2]; +#ifdef INET6 struct sockaddr_in6 sin6[2]; +#endif struct sockaddr_storage ss[2]; struct ucred uc; struct timeval tv = { Index: inetd.c =================================================================== RCS file: /usr/cvs/src/usr.sbin/inetd/inetd.c,v retrieving revision 1.79 diff -u -r1.79 inetd.c --- inetd.c 2000/02/22 00:27:53 1.79 +++ inetd.c 2000/03/10 15:13:08 @@ -1590,8 +1590,8 @@ if (v4bind == 0 || no_v4bind != 0) sep->se_nomapped = 1; } -#endif else { /* default to v4 bind if not v6 bind */ +#endif if (no_v4bind != 0) { syslog(LOG_INFO, "IPv4 bind is ignored for %s", sep->se_service); @@ -1599,7 +1599,9 @@ goto more; } sep->se_family = AF_INET; +#ifdef INET6 } +#endif /* init ctladdr */ switch(sep->se_family) { case AF_INET: This patch can also be found at http://people.FreeBSD.org/~jhb/patches/inetd.patch -- John Baldwin -- http://www.cslab.vt.edu/~jobaldwi/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 7:45: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id B00F237B98F for ; Fri, 10 Mar 2000 07:45:03 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id JAA21213; Fri, 10 Mar 2000 09:44:35 -0600 (CST) (envelope-from dick) Date: Fri, 10 Mar 2000 09:44:35 -0600 From: "Richard Seaman, Jr." To: Yoshinobu Inoue Cc: itojun@iijlab.net, current@freebsd.org Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? Message-ID: <20000310094435.K302@tar.com> References: <20000307102628S.shin@nd.net.fujitsu.co.jp> <24051.952462663@coconut.itojun.org> <20000310200904T.shin@nd.net.fujitsu.co.jp> <20000310073508.I302@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000310073508.I302@tar.com>; from dick@tar.com on Fri, Mar 10, 2000 at 07:35:08AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 10, 2000 at 07:35:08AM -0600, Richard Seaman, Jr. wrote: > On Fri, Mar 10, 2000 at 08:09:04PM +0900, Yoshinobu Inoue wrote: > > > 6to4 support seems to be very important for initial IPv6 > > deployment on FreeBSD4.0, so I tried small additinal patches > > to make it available. And It seems to work. > > > > Could some FreeBSD4.0 user with direct internet connectivity > > please try this patches and try to ping6 to my host's 6to4 > > address? > > The procedure is, > > For the benefit of the lists, and confirming private mail I sent, > ping6 works using the second of the patches sent (I didn't try the > first). Ok. In addition to your instructions I also configured the box as an IPv6 router (using the rc.conf switches) and used a prefix of 2002:cc5f:bb02::0/64 on the interior ethernet interface de0 with 2002:cc5f:bb02::1/16 on stf0. I'm not sure if this is quite right. Anyway, I can ping6 to 2002:cbb2:8dd8::1 from my interior ipv6 box as well as from the router box. I also configured DNS for the two boxes, assigning ipv6 addresses to test.ipv6.tar.com and ns.ipv6.tar.com. One of my DNS secondaries does not update immediately on notification, so you might not get the ipv6 resolution until it updates on schedule if you happen to query that box. However, once all the secondaries are up, i hope you can ping6 to both ns.ipv6.tar.com (router) and test.ipv6.tar.com (interior). I also had to adjust my ipv4 firewall rules to allow protocol ipv6 through. Strange that I didn't have to do that when doing a gif tunnel to freenet6.net. Also, what do I have to do to enable ip6fw? -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 8:40:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id BAE1037BACE; Fri, 10 Mar 2000 08:40:23 -0800 (PST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id RAA10250; Fri, 10 Mar 2000 17:40:51 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Fri, 10 Mar 2000 17:40:51 +0100 (CET) From: "O. Hartmann" To: freebsd-current@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Mylex RAID 5 failure ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, Iposted prior a message here because of the failure of our Mylex DAC960PD based RAID 5. After changing the faulty drive, the Mylex controller started rebuilding the defective drive (hot-swapped the drive). On console I got (and still get!) the message mlx0: error reading message log - invalid log entry request This message is still dumped out of the console although all activities on the RAID has been stopped and it seems to be 'repaired'. But the whole system is really slow now! what is going on? RAID 5 controller is Mylex DAC960PD mlx0: DAC960P/PD, 3 channels, firmware 3.51-0-12, 4MB RAM. The system is based on the cvsupdated source of Tuesday, 07th March. Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 8:59: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 01A0C37BC0E; Fri, 10 Mar 2000 08:59:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id F2E722E8156; Fri, 10 Mar 2000 08:59:02 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 10 Mar 2000 08:59:02 -0800 (PST) From: Kris Kennaway To: Paul Richards Cc: current@freebsd.org Subject: Re: The pw command In-Reply-To: <38C905FE.10C5E591@originative.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Mar 2000, Paul Richards wrote: > So what I'm puzzled about now is how come yours is different and do we > think its correct that pwd.db and /etc/passwd have different information > in them? Oops, that was a cut-n-paste-o. I didn't notice the extra two fields the second time :-) It's for backwards-compatability, you're right. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 9:14:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id B1F2437BDD3 for ; Fri, 10 Mar 2000 09:14:45 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip147.r11.d.bel.nwlink.com (ip147.r11.d.bel.nwlink.com [207.202.174.147]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id JAA25892; Fri, 10 Mar 2000 09:13:07 -0800 (PST) Date: Fri, 10 Mar 2000 09:07:29 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: Salvo Bartolotta Cc: freebsd-current@FreeBSD.ORG Subject: Re: single user mode problem In-Reply-To: <20000310.10064900@bartequi.ottodomain.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > This has been going on for awhile, and I've looked everywhere for a > > solution. When I boot single user, the / filesystem gets mounted on > > wd0s4a even though /dev does not even have such an entry nor does > > /etc/fstab, since these have all been updated. > > This is not really such a problem until I try to exit from single user > > mode. Then, it tries to remount / on ad0s4a and can't find it. > > > Dear Joseph, > > as I have recently written, I met an analogous problem while upgrading > to CURRENT: the "wdNsMa syndrome" appeared when I rebooted in s.u.m. > with the shining gleaming roaring freshly-made 4.0-CURRENT kernel in > order to (somehow) make installworld. Well, I did NOT care about it > and I went ahead ruthlessly ... > > By the way, I made another kernel at the end of the process ("by the > book"). I suppose (?) this cleared the problem. In fact, I was able to > boot with no weird messages: all my filesystems were correctly > identified as adNsM (e.g. ad1s2a, ad1s2e ...) Hi Salvo, I did read your recent post on this. For me, however, the problem persists even with a new kernel. I've looked through all the boot and init files for some clue as to where it's getting the idea that / is on wd0s4a but I can't find anything ):-(. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 9:20:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 3A1CB37BCD9; Fri, 10 Mar 2000 09:20:04 -0800 (PST) (envelope-from dervish@goku.cl.msu.edu) Received: (from dervish@localhost) by goku.cl.msu.edu (8.9.3/8.9.3) id MAA64688; Fri, 10 Mar 2000 12:27:08 -0500 (EST) (envelope-from dervish) Date: Fri, 10 Mar 2000 12:27:08 -0500 From: Bush Doctor To: Kris Kennaway Cc: Benjamin Greenwald , Jim Bloom , freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure in cvs ... Message-ID: <20000310122708.B61730@goku.cl.msu.edu> References: <20000309232628.A50064@goku.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kris@hub.freebsd.org on Fri, Mar 10, 2000 at 01:42:30AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Kris Kennaway aka (kris@hub.freebsd.org) said: > On Thu, 9 Mar 2000, Bush Doctor wrote: > > > Again my libRSAglue libraries before the above were: > > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* > > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a > > lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so -> libRSAglue.so.1 > > -r--r--r-- 1 root wheel 5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 > > -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a > > This was very helpful - I've been able to replicate the problem by install > an old libRSAglue of this vintage. It still doesn't answer why on earth > make world is trying to link with it, but at least now I have something to > look at. Thanks! You're welcome. I'm interested in what you find out. > > Kris > > ---- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > > #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 9:21:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id EE42537BD19; Fri, 10 Mar 2000 09:20:08 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id MAA18815; Fri, 10 Mar 2000 12:19:38 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38C92EAA.896438EF@acm.org> Date: Fri, 10 Mar 2000 12:19:38 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Bush Doctor , Benjamin Greenwald , freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure in cvs ... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Thu, 9 Mar 2000, Bush Doctor wrote: > > > Again my libRSAglue libraries before the above were: > > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* > > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a > > lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so -> libRSAglue.so.1 > > -r--r--r-- 1 root wheel 5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 > > -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a > > This was very helpful - I've been able to replicate the problem by install > an old libRSAglue of this vintage. It still doesn't answer why on earth > make world is trying to link with it, but at least now I have something to > look at. Thanks! I looked into this problem a bit as well. I believe it is a build order and dependency problem that shouldn't exist. libkrb is built before libRSAglue and then the shared library is built with -LRSAglue which is only found in /usr/lib. kerberosIV/Makefile.inc has a line "LDADD+= -LRSAglue". This whole issue should not exist simply because libRSAglue is a dummy stub and there is no reson to link anything against it. The quick fix is to remove libRSAglue from the makefiles where it is used. The following makefiles need to have the references to RSAglue removed: usr.sbin/ppp/Makefile usr.sbin/pppd/Makefile secure/libexec/sshd/Makefile kerberosIV/Makefile.inc I don't know how to change ld (compile time?) so that it doesn't look in the standard locations for files during buildworld. That is what is required to guarantee this problem doesn't happen again. Kris, would you like patches or will you edit these yourself? Jim Bloom bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 9:30: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id 6601B37C029; Fri, 10 Mar 2000 09:26:44 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id MAA18835; Fri, 10 Mar 2000 12:26:11 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38C93033.B45CDE89@acm.org> Date: Fri, 10 Mar 2000 12:26:11 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway , Bush Doctor , Benjamin Greenwald , freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure in cvs ... References: <38C92EAA.896438EF@acm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Bloom wrote: > > The > following makefiles need to have the references to RSAglue removed: > > usr.sbin/ppp/Makefile > usr.sbin/pppd/Makefile > secure/libexec/sshd/Makefile > kerberosIV/Makefile.inc > Ignore secure/libexec/sshd/Makefile. That was left over from when I was trying to integrate OpenSSH into the base system before Mark's work was included. Jim Bloom bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 9:45:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from unix.megared.net.mx (dns.megared.net.mx [200.52.207.52]) by hub.freebsd.org (Postfix) with ESMTP id 8CB9437BA52 for ; Fri, 10 Mar 2000 09:45:44 -0800 (PST) (envelope-from ales@megared.net.mx) Received: from ales (ales.megared.net.mx [200.52.207.54]) by unix.megared.net.mx (8.9.3/8.9.3) with SMTP id LAA40122; Fri, 10 Mar 2000 11:45:45 -0600 (CST) (envelope-from ales@megared.net.mx) Message-ID: <027e01bf8ab8$66bf6ca0$020a0a0a@megared.net.mx> From: "Alejandro Ramirez" To: "Jonathan Lemon" , , References: <200003101501.JAA45750@prism.flugsvamp.com> Subject: RE: ida driver in -current and eisa bus attachment Date: Fri, 10 Mar 2000 11:45:19 -0600 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Jonathan, > Note that I just committed some more changes to the IDA driver to > 4.0-RC yesterday. The changes are: > > - support for EISA controllers (untested) > - support for newer S2400 controllers (untested) > - addition of IDA to the GENERIC kernel > - support for installing directly onto the RAID array. Are there any plans to add some utility to configure (or reconfigure) the array under FreeBSD??? Greetings Ales To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 9:47:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id DD54537BA40; Fri, 10 Mar 2000 09:47:11 -0800 (PST) (envelope-from dervish@goku.cl.msu.edu) Received: (from dervish@localhost) by goku.cl.msu.edu (8.9.3/8.9.3) id MAA64808; Fri, 10 Mar 2000 12:54:54 -0500 (EST) (envelope-from dervish) Date: Fri, 10 Mar 2000 12:54:54 -0500 From: Bush Doctor To: Jim Bloom Cc: Kris Kennaway , Benjamin Greenwald , freebsd-current@FreeBSD.ORG Subject: Re: buildworld failure in cvs ... Message-ID: <20000310125454.C61730@goku.cl.msu.edu> References: <38C92EAA.896438EF@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38C92EAA.896438EF@acm.org>; from bloom@acm.org on Fri, Mar 10, 2000 at 12:19:38PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Jim Bloom aka (bloom@acm.org) said: > Kris Kennaway wrote: > > > > On Thu, 9 Mar 2000, Bush Doctor wrote: > > > > > Again my libRSAglue libraries before the above were: > > > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR* > > > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a > > > lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so -> libRSAglue.so.1 > > > -r--r--r-- 1 root wheel 5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 > > > -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a > > > > This was very helpful - I've been able to replicate the problem by install > > an old libRSAglue of this vintage. It still doesn't answer why on earth > > make world is trying to link with it, but at least now I have something to > > look at. Thanks! > > I looked into this problem a bit as well. > > I believe it is a build order and dependency problem that shouldn't > exist. libkrb is built before libRSAglue and then the shared library is > built with -LRSAglue which is only found in /usr/lib. > kerberosIV/Makefile.inc has a line "LDADD+= -LRSAglue". > > This whole issue should not exist simply because libRSAglue is a dummy > stub and there is no reson to link anything against it. The quick fix > is to remove libRSAglue from the makefiles where it is used. The > following makefiles need to have the references to RSAglue removed: Hmmm ..., I just helped a co-worker upgrade from -release to -current and he ran into a problem where 'make buildworld' failed in building Kerberos IV. I seem to recall a similiar problem a few weeks back on my -current box. I wound up commenting out the kerberos IV build in make.conf, performed a 'make buildworld' and 'make installworld' without kerberos IV, and rebuilt world afterwards with kerberos IV enabled. I really must be more proactive in reporting -current hiccups I come across :( Unfortunately, my co-worker has already overwritten the buildworld log :( > > usr.sbin/ppp/Makefile > usr.sbin/pppd/Makefile > secure/libexec/sshd/Makefile > kerberosIV/Makefile.inc > > I don't know how to change ld (compile time?) so that it doesn't look in > the standard locations for files during buildworld. That is what is > required to guarantee this problem doesn't happen again. > > Kris, would you like patches or will you edit these yourself? > > Jim Bloom > bloom@acm.org #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 9:51: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 75C8B37BC15 for ; Fri, 10 Mar 2000 09:51:01 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id CAA26719; Sat, 11 Mar 2000 02:49:35 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id CAA19105; Sat, 11 Mar 2000 02:49:34 +0900 (JST) Received: from localhost ([192.168.245.162]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id CAA16792; Sat, 11 Mar 2000 02:49:32 +0900 (JST) To: dick@tar.com Cc: itojun@iijlab.net, current@freebsd.org Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? In-Reply-To: <20000310094435.K302@tar.com> References: <20000310200904T.shin@nd.net.fujitsu.co.jp> <20000310073508.I302@tar.com> <20000310094435.K302@tar.com> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000311025028W.shin@nd.net.fujitsu.co.jp> Date: Sat, 11 Mar 2000 02:50:28 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 102 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > 6to4 support seems to be very important for initial IPv6 > > > deployment on FreeBSD4.0, so I tried small additinal patches > > > to make it available. And It seems to work. > > > > > > Could some FreeBSD4.0 user with direct internet connectivity > > > please try this patches and try to ping6 to my host's 6to4 > > > address? > > > The procedure is, > > > > For the benefit of the lists, and confirming private mail I sent, > > ping6 works using the second of the patches sent (I didn't try the > > first). Thanks very much for your confirmations! > Ok. In addition to your instructions I also configured the > box as an IPv6 router (using the rc.conf switches) and > used a prefix of 2002:cc5f:bb02::0/64 on the interior > ethernet interface de0 with 2002:cc5f:bb02::1/16 on stf0. I'm > not sure if this is quite right. Maybe it is OK. > Anyway, I can ping6 to 2002:cbb2:8dd8::1 from my interior ipv6 > box as well as from the router box. I also configured DNS > for the two boxes, assigning ipv6 addresses to test.ipv6.tar.com > and ns.ipv6.tar.com. One of my DNS secondaries does not update > immediately on notification, so you might not get the ipv6 > resolution until it updates on schedule if you happen to query > that box. However, once all the secondaries are up, i hope > you can ping6 to both ns.ipv6.tar.com (router) and > test.ipv6.tar.com (interior). Yes I could successfully ping them! % ping6 test.ipv6.tar.com PING6(56=40+8+8 bytes) 2002:cbb2:8dd8::1 --> 2002:cc5f:bb02:0:2a0:c9ff:feb1:23ae 16 bytes from 2002:cc5f:bb02:0:2a0:c9ff:feb1:23ae, icmp_seq=0 hlim=63 time=715.85 ms 16 bytes from 2002:cc5f:bb02:0:2a0:c9ff:feb1:23ae, icmp_seq=1 hlim=63 time=426.515 ms ^C --- test.ipv6.tar.com ping6 statistics --- 3 packets transmitted, 2 packets received, 33% packet loss round-trip min/avg/max = 426.515/571.182/715.85 ms % ping6 ns.ipv6.tar.com PING6(56=40+8+8 bytes) 2002:cbb2:8dd8::1 --> 2002:cc5f:bb02:0:200:c0ff:fe34:41c6 16 bytes from 2002:cc5f:bb02:0:200:c0ff:fe34:41c6, icmp_seq=0 hlim=64 time=396.449 ms 16 bytes from 2002:cc5f:bb02:0:200:c0ff:fe34:41c6, icmp_seq=1 hlim=64 time=363.181 ms ^C --- ns.ipv6.tar.com ping6 statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 363.181/379.815/396.449 ms > I also had to adjust my ipv4 firewall rules to allow protocol > ipv6 through. Strange that I didn't have to do that when > doing a gif tunnel to freenet6.net. Also, what do I have to > do to enable ip6fw? Wmmm, it is strange that freenet6 was OK. About ip6fw, I think you can enable ip6fw over 6to4 by specifying "via stf" for each rules for IPv6. Here are some examples. (I belive following examples will work, but not tested yet.) If you want to allow 1:2:3::/48, add 10 allow ipv6 from 1:2:3:::/48 to any via stf* in add 15 allow ipv6 from any to 1:2:3::/48 via stf* out If you want to allow only ssh from 3:4:5::/48 outside to 6:7:8:9::/64 inside, (stf0 below can be stf*. Choosed it just for variety.) add 700 allow tcp from 3:4:5::/48 to 6:7:8:9::/64 ssh via stf0 in add 800 allow tcp from 6:7:8:9::/64 ssh to 3:4:5::/48 via stf0 out By the way, I'm now very much interested in next round of test, that non 6to4 IPv6 prefix routing via 6to4 cloud. Could you please assign some non 6to4 prefix inside your environment? If your non 6to4 prefix is 1:2:3:4::/64 for example, then I would like to configure a route for it, like below. route add -inet6 1:2:3:4:: -prefixlen 64 2002:cc5f:bb02::1 And my non 6to4 prefix is 3ffe:501:4819:2000::/64. So please assigne following route. route add -inet6 3ffe:501:4819:2000:: -prefixlen 64 2002:cbb2:8dd8::1 Then I believe I can ping to some of your non 6to4 addresses from my non 6to4 address. Also, I think you can ping to my non 6to4 addr, 3ffe:501:4819:2000:210:5aff:fe86:b65a, from your non 6to4 address. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 9:52:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id BEEFC37BB3E; Fri, 10 Mar 2000 09:52:11 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id CAA26829; Sat, 11 Mar 2000 02:52:09 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id CAA09913; Sat, 11 Mar 2000 02:52:08 +0900 (JST) Received: from localhost ([192.168.245.162]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id CAA16844; Sat, 11 Mar 2000 02:52:07 +0900 (JST) To: jhb@FreeBSD.ORG Cc: current@FreeBSD.ORG, oogali@intranova.net Subject: Re: inetd broken w/o INET6 In-Reply-To: <200003101521.KAA66327@server.baldwin.cx> References: <200003101521.KAA66327@server.baldwin.cx> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000311025303B.shin@nd.net.fujitsu.co.jp> Date: Sat, 11 Mar 2000 02:53:03 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It appears inetd is broken if you don't have INET6 defined. This is > the case for picoBSD, for example: Woops, sorry. I'll reflect it. Thanks for the patches. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 9:53:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 625BE37C00C for ; Fri, 10 Mar 2000 09:53:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA02592; Fri, 10 Mar 2000 09:54:36 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003101754.JAA02592@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: R Joseph Wright Cc: freebsd-current@FreeBSD.org Subject: Re: single user mode problem In-reply-to: Your message of "Fri, 10 Mar 2000 00:51:06 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Mar 2000 09:54:36 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This has been going on for awhile, and I've looked everywhere for a > solution. When I boot single user, the / filesystem gets mounted on > wd0s4a even though /dev does not even have such an entry nor does > /etc/fstab, since these have all been updated. > This is not really such a problem until I try to exit from single user > mode. Then, it tries to remount / on ad0s4a and can't find it. Since there's no extra mounting activity that goes on on single-user mode vs. multi-user mode, I'm suspicious that you've probably gone and done something else as well that we're not hearing about. Regardless, this is typically syptomatic of either a very old /boot/loader, non-use of the loader eg. through a /boot.config file, or an error in the entry for / in /etc/fstab. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 9:55:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 3CFAE37BCE2 for ; Fri, 10 Mar 2000 09:55:26 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id LAA50709; Fri, 10 Mar 2000 11:58:29 -0600 (CST) (envelope-from jlemon) Date: Fri, 10 Mar 2000 11:58:29 -0600 From: Jonathan Lemon To: Alejandro Ramirez Cc: Jonathan Lemon , ml@seeberg.dk, current@FreeBSD.ORG Subject: Re: ida driver in -current and eisa bus attachment Message-ID: <20000310115829.B48050@prism.flugsvamp.com> References: <200003101501.JAA45750@prism.flugsvamp.com> <027e01bf8ab8$66bf6ca0$020a0a0a@megared.net.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <027e01bf8ab8$66bf6ca0$020a0a0a@megared.net.mx> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 10, 2000 at 11:45:19AM -0600, Alejandro Ramirez wrote: > Hi Jonathan, > > > Note that I just committed some more changes to the IDA driver to > > 4.0-RC yesterday. The changes are: > > > > - support for EISA controllers (untested) > > - support for newer S2400 controllers (untested) > > - addition of IDA to the GENERIC kernel > > - support for installing directly onto the RAID array. > > Are there any plans to add some utility to configure (or reconfigure) the > array under FreeBSD??? Unfortunately, no. That would require documentation on the controller, and so far, Compaq hasn't shown any inclination to release information. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 10:21: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 6C3E437BA6A for ; Fri, 10 Mar 2000 10:20:53 -0800 (PST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id TAA85859 for ; Fri, 10 Mar 2000 19:21:21 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Fri, 10 Mar 2000 19:21:21 +0100 (CET) From: "O. Hartmann" To: freebsd-current@freebsd.org Subject: Again, RAID 5 failure ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well ... more confused! I posted some messages here before ... after I though the RAID has been rebuilt I tried to shutdown the server. On console I still got massive dumps of the same message, as I posted before. Shutdown was blocked, but I don't know by what, only thing to bring back the server alive was: power cycle. I think that's not in sensu strictu of what we understand when we say hot swap RAID 5? Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 10:29:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from mecca.servint.com (mecca.servint.com [209.50.225.14]) by hub.freebsd.org (Postfix) with ESMTP id 0263837BA88 for ; Fri, 10 Mar 2000 10:29:43 -0800 (PST) (envelope-from loschert@servint.com) Received: from delft.servint.com (207-172-79-129.s129.tnt5.rcm.va.dialup.rcn.com [207.172.79.129]) by mecca.servint.com (8.9.3/8.9.0) with ESMTP id NAA06043 for ; Fri, 10 Mar 2000 13:45:30 -0500 (EST) Received: (qmail 14792 invoked by uid 1000); 10 Mar 2000 18:29:04 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Mar 2000 18:29:04 -0000 Date: Fri, 10 Mar 2000 13:29:04 -0500 (EST) From: Matt Loschert To: Doug Barton Cc: current@FreeBSD.ORG Subject: Re: Alternative way to do -stable to -current upgrade In-Reply-To: <38C5F109.476539B0@simplenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Mar 2000, Doug Barton wrote: > I've been meaning to post this for a while. I recently upgraded two way > old 4.0 systems to post-signal changes -current. It's not quite a 3.x -> > 4.0-Current upgrade, but it's close. I had to do a few things > differently than what's in Updating, and I wanted to test the > feasability of not going single user mode since I keep remote upgrades > in the back of my mind even though I don't do a lot of them anymore. > This is assuming that you've done all the right things with upgrading > sources, double-checked /etc/make.conf, using clean /usr/src, clean > /usr/obj, etc. > > 1. make buildworld > 2. make buildkernel > I actually updated my kernel config file while world was building so I > did 'make KERNEL=MYKERNELFILE buildkernel, and below, but that's not for > the faint of heart. As someone already pointed out, GENERIC is a better > choice, and doesn't require any options. > 3. make installkernel > 4. cd /usr/src/sbin/mknod && make install > I had to do this or the next step didn't work. > 5. cp /usr/src/etc/MAKEFILE /dev ; cd /dev ; /bin/sh MAKEFILE all > 6. Update /etc/fstab and new disk devices per instructions in Updating > 7. reboot > 8. make -k installworld > 9. make installworld > 10. mergemaster > 11. rebuilt my kernel (make sure to update your kernel config file) and > rebooted > > I did one system this way feeling my way through, then did another > following these instructions and didn't have any problems. I never had > to go single user, although these were workstation machines. For servers > you'd probably want to use /var/run/nologin, or similar. (Just make sure > you open plenty of shells for yourself first. :) > > I hope this is useful, > > Doug I just wanted to let you know that I used this procedure on a very recent 3.4-STABLE to -CURRENT upgrade and it worked flawlessly. The whole procedure was performed multi-user and remotely (the two boxes are sitting right next to each other though). I had been following the upgrade threads on -current and reading UPDATING, and this procedure appeared to be the most coherent I had seen. Thanks Doug. - Matt -- Matt Loschert loschert@servint.com Software Engineer voice (703) 847-1381 ServInt Internet Services fax (703) 847-1383 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 10:47:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles549.castles.com [208.214.165.113]) by hub.freebsd.org (Postfix) with ESMTP id B670E37BA6A for ; Fri, 10 Mar 2000 10:47:23 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA02768; Fri, 10 Mar 2000 10:48:23 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003101848.KAA02768@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Alejandro Ramirez" Cc: "Jonathan Lemon" , ml@seeberg.dk, current@FreeBSD.ORG Subject: Re: ida driver in -current and eisa bus attachment In-reply-to: Your message of "Fri, 10 Mar 2000 11:45:19 CST." <027e01bf8ab8$66bf6ca0$020a0a0a@megared.net.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Mar 2000 10:48:22 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi Jonathan, > > > Note that I just committed some more changes to the IDA driver to > > 4.0-RC yesterday. The changes are: > > > > - support for EISA controllers (untested) > > - support for newer S2400 controllers (untested) > > - addition of IDA to the GENERIC kernel > > - support for installing directly onto the RAID array. > > Are there any plans to add some utility to configure (or reconfigure) the > array under FreeBSD??? Compaq claimed that the documentation necessary to do this was available, but it's not. I've tried to contact the individual that I spoke to about this, but he's not returning email or phone calls. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 10:57:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles549.castles.com [208.214.165.113]) by hub.freebsd.org (Postfix) with ESMTP id 5B80537BA57 for ; Fri, 10 Mar 2000 10:57:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA02844; Fri, 10 Mar 2000 10:57:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003101857.KAA02844@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "O. Hartmann" Cc: freebsd-current@freebsd.org Subject: Re: RAID 5 Failure dumps all terminals In-reply-to: Your message of "Fri, 10 Mar 2000 15:37:09 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Mar 2000 10:57:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We use A Mylex DAC960PD RAID 5 controller, attached to 7 > harddrives. One of the drives have had permanent failures, so > we changed it. Well, as I understand RAID 5, rebuilding the defective > drive should not involve the system, but On console (it ttyv0) I get > a message like "mlx0: error reading message log - invalid log entry request". The controller has told us that there's a message waiting for us, but when we go to get the message, it claims that it doesn't exist. The driver doesn't handle being lied to very well; you're probably getting a storm of these messages based on your followups. I'll take a look at this and see if I can reproduce it. > On all other ttyv* a logged in user (root) gets the same message > from kernel. Is this eloquence of the kernel and the mlx-driver a preliminary > feature or is the code still buggy, instable or anything else? I feel a little bit > confused about that, while other systems using RAID 5 are completely quiet > while rebuilding the defective and changed device. I have no idea what "other systems" you're talking about. I consider it prudent to log hardware failures, rather than letting them slip silently by. > On the other hand, how can I redirect console output to another console, on which > nobody never can log in (it should not be ttyv0)? How to prevent users and root > on some ttyv* from getting that much error messages, except on a bunch of > declared ttys? You would want to read the syslogd manpage, which will make this very standard part of your system's configuration somewhat clearer. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 11:18:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 570F937B78F for ; Fri, 10 Mar 2000 11:18:35 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id OAA66871; Fri, 10 Mar 2000 14:18:08 -0500 (EST) Date: Fri, 10 Mar 2000 14:18:08 -0500 (EST) From: "Matthew N. Dodd" To: Alejandro Ramirez Cc: Jonathan Lemon , ml@seeberg.dk, current@FreeBSD.ORG Subject: RE: ida driver in -current and eisa bus attachment In-Reply-To: <027e01bf8ab8$66bf6ca0$020a0a0a@megared.net.mx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Mar 2000, Alejandro Ramirez wrote: > > Note that I just committed some more changes to the IDA driver to > > 4.0-RC yesterday. The changes are: > > > > - support for EISA controllers (untested) > > - support for newer S2400 controllers (untested) > > - addition of IDA to the GENERIC kernel > > - support for installing directly onto the RAID array. > > Are there any plans to add some utility to configure (or reconfigure) the > array under FreeBSD??? The interfaces for configuring volumes aren't available from Compaq due to IP issues. Its possible that they might be reverse engineered. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 11:25:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from puku.zamnet.zm (puku.zamnet.zm [208.224.176.40]) by hub.freebsd.org (Postfix) with ESMTP id C77E337BC6C for ; Fri, 10 Mar 2000 11:25:15 -0800 (PST) (envelope-from daniel@zamnet.zm) Received: from zamnet.zm (thor.zamnet.zm [208.224.176.91]) by puku.zamnet.zm (8.9.3/8.9.3) with ESMTP id VAA50630 for ; Fri, 10 Mar 2000 21:28:58 +0200 (ZMT) Message-ID: <38C94C54.F03B163E@zamnet.zm> Date: Fri, 10 Mar 2000 21:26:12 +0200 From: Daniel Mpolokoso X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: RC3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've managed to install RC3 without a hitch. The only problem I have is that I can't get the XFree86 setup to configure X to run on my graphics hardware: pci0: at 1.0 irq 11 My Compaq desktop using the Intel 810e motherboard. Any pointers? Daniel. ------------------------------------------------------------------------ Daniel Mpolokoso - Managing Director (Act.), Email: daniel@zamnet.zm ZAMNET Communication Systems Limited, Phone: +260 - 1 - 763065 P.O. Box 38299, Lusaka, Zambia. Fax: +260 - 1 - 224775 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 11:27: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id F3B0D37BBEC; Fri, 10 Mar 2000 11:26:54 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip147.r11.d.bel.nwlink.com (ip147.r11.d.bel.nwlink.com [207.202.174.147]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id LAA27235; Fri, 10 Mar 2000 11:26:53 -0800 (PST) Date: Fri, 10 Mar 2000 11:21:15 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: Mike Smith Cc: freebsd-current@FreeBSD.org Subject: Re: single user mode problem In-Reply-To: <200003101754.JAA02592@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Regardless, this is typically syptomatic of either a very old > /boot/loader, non-use of the loader eg. through a /boot.config file, or > an error in the entry for / in /etc/fstab. > Isn't /boot/loader updated upon making a new world? If so, it ought to be current. I don't know any way of finding out since it's a binary file. /etc/fstab: /dev/ad0s4b none swap sw 0 0 /dev/ad0s4a / ufs rw 1 1 /dev/ad0s4e /usr ufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 /dev/ad0s1 /dos msdos ro,noauto 0 0 proc /proc procfs rw 0 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 11:55:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id DC24C37BA29 for ; Fri, 10 Mar 2000 11:54:57 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id NAA22566; Fri, 10 Mar 2000 13:54:30 -0600 (CST) (envelope-from dick) Date: Fri, 10 Mar 2000 13:54:30 -0600 From: "Richard Seaman, Jr." To: Yoshinobu Inoue Cc: itojun@iijlab.net, current@FreeBSD.ORG Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? Message-ID: <20000310135430.L302@tar.com> References: <20000310200904T.shin@nd.net.fujitsu.co.jp> <20000310073508.I302@tar.com> <20000310094435.K302@tar.com> <20000311025028W.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="NMuMz9nt05w80d4+" X-Mailer: Mutt 1.0.1i In-Reply-To: <20000311025028W.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Sat, Mar 11, 2000 at 02:50:28AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --NMuMz9nt05w80d4+ Content-Type: text/plain; charset=us-ascii On Sat, Mar 11, 2000 at 02:50:28AM +0900, Yoshinobu Inoue wrote: > By the way, I'm now very much interested in next round of > test, that non 6to4 IPv6 prefix routing via 6to4 cloud. > > Could you please assign some non 6to4 prefix inside your > environment? Ok. c000::/64 > route add -inet6 3ffe:501:4819:2000:: -prefixlen 64 2002:cbb2:8dd8::1 Did it on the router. > Then I believe I can ping to some of your non 6to4 addresses > from my non 6to4 address. Try: c000::2a0:c9ff:feb1:23ae (border router) c000::200:c0ff:fe34:41c6 (interior box) > Also, I think you can ping to my non > 6to4 addr, 3ffe:501:4819:2000:210:5aff:fe86:b65a, from your > non 6to4 address. I tried deleting the 6to4 address from an interface on the interior node and did a ping6, but I get no replies (I think you have to configure the route on your end first?). Is there a simpler way to force ping6 to use the non 6to4 address as the source? I can ping6 your non 6to4 address from my 6to4 address, see attached. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 --NMuMz9nt05w80d4+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ping6.out" PING6(56=40+8+8 bytes) 2002:cc5f:bb02:0:2a0:c9ff:feb1:23ae --> 3ffe:501:4819:2000:210:5aff:fe86:b65a 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=0 hlim=63 time=530.244 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=1 hlim=63 time=360.666 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=2 hlim=63 time=360.621 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=3 hlim=63 time=410.744 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=4 hlim=63 time=350.658 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=5 hlim=63 time=350.743 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=6 hlim=63 time=350.836 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=7 hlim=63 time=350.761 ms --- 3ffe:501:4819:2000:210:5aff:fe86:b65a ping6 statistics --- 9 packets transmitted, 8 packets received, 11% packet loss round-trip min/avg/max = 350.658/383.159/530.244 ms --NMuMz9nt05w80d4+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 12:22:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id EFBBF37BB57 for ; Fri, 10 Mar 2000 12:22:25 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id FAA25233; Sat, 11 Mar 2000 05:21:15 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id FAA06708; Sat, 11 Mar 2000 05:21:15 +0900 (JST) Received: from localhost ([192.168.245.162]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id FAA18893; Sat, 11 Mar 2000 05:21:13 +0900 (JST) To: dick@tar.com Cc: itojun@iijlab.net, current@FreeBSD.ORG Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? In-Reply-To: <20000310135430.L302@tar.com> References: <20000310094435.K302@tar.com> <20000311025028W.shin@nd.net.fujitsu.co.jp> <20000310135430.L302@tar.com> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000311052209D.shin@nd.net.fujitsu.co.jp> Date: Sat, 11 Mar 2000 05:22:09 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 75 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > By the way, I'm now very much interested in next round of > > test, that non 6to4 IPv6 prefix routing via 6to4 cloud. > > > > Could you please assign some non 6to4 prefix inside your > > environment? > > Ok. c000::/64 > > > route add -inet6 3ffe:501:4819:2000:: -prefixlen 64 2002:cbb2:8dd8::1 > > Did it on the router. > > > Then I believe I can ping to some of your non 6to4 addresses > > from my non 6to4 address. > > Try: > > c000::2a0:c9ff:feb1:23ae (border router) > c000::200:c0ff:fe34:41c6 (interior box) Either seems to be OK. % ping6 c000::2a0:c9ff:feb1:23ae PING6(56=40+8+8 bytes) 3ffe:501:4819:2000:200:eff:fe2e:def6 --> c000::2a0:c9ff:feb1:23ae 16 bytes from c000::2a0:c9ff:feb1:23ae, icmp_seq=0 hlim=62 time=1136.08 ms 16 bytes from c000::2a0:c9ff:feb1:23ae, icmp_seq=2 hlim=62 time=351.348 ms 16 bytes from c000::2a0:c9ff:feb1:23ae, icmp_seq=3 hlim=62 time=352.258 ms 16 bytes from c000::2a0:c9ff:feb1:23ae, icmp_seq=4 hlim=62 time=346.276 ms 16 bytes from c000::2a0:c9ff:feb1:23ae, icmp_seq=5 hlim=62 time=342.058 ms ^C --- c000::2a0:c9ff:feb1:23ae ping6 statistics --- 6 packets transmitted, 5 packets received, 16% packet loss round-trip min/avg/max = 342.058/505.603/1136.08 ms phoenix% ping6 c000::200:c0ff:fe34:41c6 PING6(56=40+8+8 bytes) 3ffe:501:4819:2000:200:eff:fe2e:def6 --> c000::200:c0ff:fe34:41c6 16 bytes from c000::200:c0ff:fe34:41c6, icmp_seq=0 hlim=63 time=385.097 ms 16 bytes from c000::200:c0ff:fe34:41c6, icmp_seq=1 hlim=63 time=372.819 ms 16 bytes from c000::200:c0ff:fe34:41c6, icmp_seq=2 hlim=63 time=361.545 ms ^C --- c000::200:c0ff:fe34:41c6 ping6 statistics --- 4 packets transmitted, 3 packets received, 25% packet loss round-trip min/avg/max = 361.545/373.153/385.097 ms > > Also, I think you can ping to my non > > 6to4 addr, 3ffe:501:4819:2000:210:5aff:fe86:b65a, from your > > non 6to4 address. > > I tried deleting the 6to4 address from an interface on the > interior node and did a ping6, but I get no replies (I think > you have to configure the route on your end first?). Yes, I have configured it, so it should work now. > Is > there a simpler way to force ping6 to use the non 6to4 > address as the source? Woops, ping6 don't have "-S" option. I also tried it from internal machine, and enabled the 6to4 machine as router. > I can ping6 your non 6to4 address from my 6to4 address, see > attached. Thanks, thus, this stf interface seems to be working very well. Also I believe, your machine can setup other gif tunnel to other IPv4 addr at the same time. It seems to be OK for my machine. The gif src addr and dst addr need to be explicitly defined, but the src addr can be same with stf interface addr. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 12:23:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E059F37BA82 for ; Fri, 10 Mar 2000 12:23:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA42534; Fri, 10 Mar 2000 12:23:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Hay Cc: freebsd-current@FreeBSD.ORG (FreeBSD-current) Subject: Re: USA_RESIDENT and sysinstall In-reply-to: Your message of "Sat, 10 Mar 2000 13:01:54 +0200." <200003101101.NAA19693@zibbi.mikom.csir.co.za> Date: Fri, 10 Mar 2000 12:23:34 -0800 Message-ID: <42531.952719814@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I installed a -current snap from internat.freebsd.org that was built > with crypto source from internat. I answered yes when sysinstall asked > me if I want the crypto stuff, but then found that it marked me as an > USA_RESIDENT=YES in /etc/make.conf and it also asked me later if I > want to install the rsaref libraries. > > I think the test for USA_RESIDENT should be a bit more clever or the > message should be a bit more clear. At the moment it is: Yes, I screwed this up - I'm fixing it now! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 12:25:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from cloudbase.sixforty.co.uk (cloudbase.sixforty.co.uk [194.207.180.10]) by hub.freebsd.org (Postfix) with ESMTP id D3FD737BCF1 for ; Fri, 10 Mar 2000 12:25:06 -0800 (PST) (envelope-from l.farr@epcdirect.co.uk) Received: from bka (jack.sixforty.co.uk [213.48.101.201]) by cloudbase.sixforty.co.uk (8.9.3/8.8.7) with SMTP id UAA01067 for ; Fri, 10 Mar 2000 20:24:51 GMT Reply-To: From: "Lawrence Farr" To: Subject: Mylex Support Date: Fri, 10 Mar 2000 20:28:12 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have 4 different Mylex DAC960 controllers that I cannot install Current onto. (Tried from Late December to 20000307). Sysinstall seems to get the geometry wrong, and even telling sysinstall the "correct" geometry, it gives a "tied to write beyond end of drive" error. Booting from a running -current and formatting does the same. They all have the latest BIOS, and they have been tried with various drive combinations. Has anyone else got this to work successfully or is it just me?. And if it is just me, anyone got any ideas? I have been pestering Mike Smith about this for ages, and have probably driven him mad! Lawrence Farr EPC Direct To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 12:26: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 2C12137BA8D for ; Fri, 10 Mar 2000 12:25:55 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id OAA22730; Fri, 10 Mar 2000 14:25:29 -0600 (CST) (envelope-from dick) Date: Fri, 10 Mar 2000 14:25:29 -0600 From: "Richard Seaman, Jr." To: Yoshinobu Inoue Cc: itojun@iijlab.net, current@FreeBSD.ORG Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? Message-ID: <20000310142528.M302@tar.com> References: <20000310094435.K302@tar.com> <20000311025028W.shin@nd.net.fujitsu.co.jp> <20000310135430.L302@tar.com> <20000311052209D.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000311052209D.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Sat, Mar 11, 2000 at 05:22:09AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 11, 2000 at 05:22:09AM +0900, Yoshinobu Inoue wrote: > > I tried deleting the 6to4 address from an interface on the > > interior node and did a ping6, but I get no replies (I think > > you have to configure the route on your end first?). > > Yes, I have configured it, so it should work now. Yes, it does. It all looks good. PING6(56=40+8+8 bytes) c000::2a0:c9ff:feb1:23ae --> 3ffe:501:4819:2000:210:5aff:fe86:b65a 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=0 hlim=63 time=452.312 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=1 hlim=63 time=361.945 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=2 hlim=63 time=421.628 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=4 hlim=63 time=341.997 ms 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=5 hlim=63 time=582.145 ms --- 3ffe:501:4819:2000:210:5aff:fe86:b65a ping6 statistics --- 7 packets transmitted, 5 packets received, 28% packet loss round-trip min/avg/max = 341.997/432.005/582.145 ms -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 12:33:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 2D37F37BC60 for ; Fri, 10 Mar 2000 12:33:13 -0800 (PST) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id E52301C4A; Fri, 10 Mar 2000 15:33:11 -0500 (EST) Date: Fri, 10 Mar 2000 15:33:11 -0500 From: Bill Fumerola To: Daniel Mpolokoso Cc: freebsd-current@freebsd.org Subject: Re: RC3 Message-ID: <20000310153311.U25438@jade.chc-chimes.com> References: <38C94C54.F03B163E@zamnet.zm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38C94C54.F03B163E@zamnet.zm>; from daniel@zamnet.zm on Fri, Mar 10, 2000 at 09:26:12PM +0200 X-Operating-System: FreeBSD 3.2-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 10, 2000 at 09:26:12PM +0200, Daniel Mpolokoso wrote: > I've managed to install RC3 without a hitch. The only problem I have is that > I can't get the XFree86 setup to configure X to run on my graphics hardware: > > pci0: at 1.0 irq 11 > > My Compaq desktop using the Intel 810e motherboard. > > Any pointers? This requires a special module that only works with Linux, AFAIK. I have no idea if an effort to port it exists. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: billf@chc-chimes.com / billf@FreeBSD.org Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 12:38:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id F123337BC37 for ; Fri, 10 Mar 2000 12:38:08 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id OAA22812; Fri, 10 Mar 2000 14:37:48 -0600 (CST) (envelope-from dick) Date: Fri, 10 Mar 2000 14:37:48 -0600 From: "Richard Seaman, Jr." To: Yoshinobu Inoue Cc: itojun@iijlab.net, current@freebsd.org Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? Message-ID: <20000310143748.N302@tar.com> References: <20000310200904T.shin@nd.net.fujitsu.co.jp> <20000310073508.I302@tar.com> <20000310094435.K302@tar.com> <20000311025028W.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000311025028W.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Sat, Mar 11, 2000 at 02:50:28AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 11, 2000 at 02:50:28AM +0900, Yoshinobu Inoue wrote: > > I also had to adjust my ipv4 firewall rules to allow protocol > > ipv6 through. Strange that I didn't have to do that when > > doing a gif tunnel to freenet6.net. Also, what do I have to > > do to enable ip6fw? > > Wmmm, it is strange that freenet6 was OK. Just to clarify, I had to configure a hole in ipfw for freenet6.net too. I had just forgotten about it. :) -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 12:45:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 0A1B137BB24 for ; Fri, 10 Mar 2000 12:45:32 -0800 (PST) (envelope-from kent@lab1.tfd.com) Received: from lab1.tfd.com (lab1.tfd.com [10.9.200.31]) by rtp.tfd.com (8.9.3/8.9.3) with SMTP id PAA03445 for ; Fri, 10 Mar 2000 15:46:00 -0500 (EST) Received: by lab1.tfd.com id AA00976 (5.67b/IDA-1.5 for freebsd-current@freebsd.org); Fri, 10 Mar 2000 15:43:44 -0500 Date: Fri, 10 Mar 2000 15:43:44 -0500 From: Kent Hauser Message-Id: <200003102043.AA00976@lab1.tfd.com> To: freebsd-current@freebsd.org Subject: PCI modems Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've tried hard to get my PCI internal modem work with current. I've tried editing /sys/isa/sio.c with the all possible byte and word swaps of the vendor/dev printouts from the kernel probe. The documentation for this USR modem says it's *not* a winmodem, but a "standalone" modem. The 3.x FAQ suggests fiddling with/enabling the PNP driver -- which seems integrated in current. Any suggestions? Thanks. Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 12:48:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 685DD37BCB0 for ; Fri, 10 Mar 2000 12:48:44 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id FAA08363; Sat, 11 Mar 2000 05:47:34 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id FAA09103; Sat, 11 Mar 2000 05:47:34 +0900 (JST) Received: from localhost ([192.168.245.162]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id FAA19228; Sat, 11 Mar 2000 05:47:32 +0900 (JST) To: dick@tar.com Cc: itojun@iijlab.net, current@FreeBSD.ORG Subject: Re: IPv6: can a link-site (or global) address be configured in rc.conf? In-Reply-To: <20000310142528.M302@tar.com> References: <20000310135430.L302@tar.com> <20000311052209D.shin@nd.net.fujitsu.co.jp> <20000310142528.M302@tar.com> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000311054828E.shin@nd.net.fujitsu.co.jp> Date: Sat, 11 Mar 2000 05:48:28 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 16 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I tried deleting the 6to4 address from an interface on the > > > interior node and did a ping6, but I get no replies (I think > > > you have to configure the route on your end first?). > > > > Yes, I have configured it, so it should work now. > > Yes, it does. It all looks good. > > PING6(56=40+8+8 bytes) c000::2a0:c9ff:feb1:23ae --> 3ffe:501:4819:2000:210:5aff:fe86:b65a > 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=0 hlim=63 time=452.312 ms > 16 bytes from 3ffe:501:4819:2000:210:5aff:fe86:b65a, icmp_seq=1 hlim=63 time=361.945 ms Much thanks for your help! :-) Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 13:12:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from gothic.abyss.net (gothic.abyss.net [216.42.78.194]) by hub.freebsd.org (Postfix) with SMTP id D2A1D37BA79 for ; Fri, 10 Mar 2000 13:12:32 -0800 (PST) (envelope-from ksb@abyss.net) Received: (qmail 17967 invoked from network); 10 Mar 2000 21:14:09 -0000 Received: from nightmare.abyss.net (ksb@216.42.78.195) by gothic.abyss.net with SMTP; 10 Mar 2000 21:14:09 -0000 Date: Fri, 10 Mar 2000 16:16:12 -0500 (EST) From: "Kevin S. Brackett" To: freebsd-current@freebsd.org Subject: dvd playback Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was looking around the internet to see how the opensource people were getting along with all the suits against them, and I found a site with a freebsd css-auth patch and nist archive tared; I was wondering how well dvd playback was at this point? all those wondering, the site is linked from http://www.opendvd.org/. - kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 13:17:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from ren.sasknow.com (h139-142-245-96.ss.fiberone.net [139.142.245.96]) by hub.freebsd.org (Postfix) with ESMTP id 4FB8437BAA7 for ; Fri, 10 Mar 2000 13:17:28 -0800 (PST) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id PAA06578 for ; Fri, 10 Mar 2000 15:17:24 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Fri, 10 Mar 2000 15:17:24 -0600 (CST) From: Ryan Thompson To: freebsd-current@freebsd.org Subject: 4.0-20000307-CURRENT kern.flp keyboard probe questions Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all... Maybe there is a valid reason for this, but when I attempt to boot the 4.0 kern.flp without a keyboard attached (I share one keyboard between four systems, here), it displays keyboard: no and the BTX loader message, and ceases to display ANY output on the attached monitor (though it does continue to access the disk, I'm assuming, until the MFS root floppy is needed)? I assume this is because, without a keyboard, the loader assumes a serial console is attached. This is not the case in my situation. Isn't there a better way to identify a serial console? And, if not, could the loader at least not display a message on the local monitor like "Switching output to serial console...", or better yet, "Switching output to serial console in 10 seconds.. press any key to abort"? IMO, something like the above might avoid some confusion in the future. -- Ryan Thompson Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 13:57:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9FC6337B82C for ; Fri, 10 Mar 2000 13:57:24 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA24366; Fri, 10 Mar 2000 13:57:21 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA43351; Fri, 10 Mar 2000 13:57:20 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 10 Mar 2000 13:57:20 -0800 (PST) Message-Id: <200003102157.NAA43351@vashon.polstra.com> To: bloom@acm.org Subject: Re: More "ld-elf.so.1: assert failed" messages In-Reply-To: <38C8610C.E17A41EF@acm.org> References: <13611.952595759@zippy.cdrom.com> <200003100054.BAA64158@saturn.kn-bremen.de> <38C8610C.E17A41EF@acm.org> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <38C8610C.E17A41EF@acm.org>, Jim Bloom wrote: [when dllockinit() should be called] > It should be called somewhere between the starting of the process > and the creation of the second thread. There is no problem if there > is only one thread. > > THREAD Create would be fine as long as it sets a variable accessible > to all threads indicating dllockinit has been called. > > Another possible location would be a routine that initialize the > multithreading for the process. This routine may not exist in all > thread packages though. That is all correct. Dllockinit has to be called once only, before any threads have been forked but late enough so that it's safe to call the thread sychronization primitives. Ideally, a reader/writer lock should be used. But it will also work to use a simple mutex. In that case, rlock_acquire and wlock_aquire will be the same (lock the mutex). I'd recommend using a simple mutex unless the threads package already implements reader/writer locks. I really hope I can render all this nonsense unnecessary after the code freeze ends. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 13:58:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-198-202.guate.net [209.198.197.202]) by hub.freebsd.org (Postfix) with ESMTP id B438437C0E2; Fri, 10 Mar 2000 13:58:35 -0800 (PST) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id PAA85233; Fri, 10 Mar 2000 15:57:49 -0600 (CST) (envelope-from obonilla) Date: Fri, 10 Mar 2000 15:57:49 -0600 From: Oscar Bonilla To: R Joseph Wright Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: single user mode problem Message-ID: <20000310155749.A85181@fisicc-ufm.edu> References: <200003101754.JAA02592@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 10, 2000 at 11:21:15AM -0800, R Joseph Wright wrote: > > > > Regardless, this is typically syptomatic of either a very old > > /boot/loader, non-use of the loader eg. through a /boot.config file, or > > an error in the entry for / in /etc/fstab. > > > > Isn't /boot/loader updated upon making a new world? If so, it ought to be > current. I don't know any way of finding out since it's a binary file. > sorry if this is a stupid reply, but you don't happen to have this line in your kerne config file do you? config kernel root on wd0 regards, -oscar -- pgp public key: finger obonilla@fisicc-ufm.edu pgp fingerprint: 6D 18 8C 90 4C DF F0 4B DF 35 1F 69 A1 33 C7 BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 14:16:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from m3.cs.berkeley.edu (m3.CS.Berkeley.EDU [128.32.45.179]) by hub.freebsd.org (Postfix) with ESMTP id 7303C37BACF for ; Fri, 10 Mar 2000 14:16:28 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca36-20.ix.netcom.com [207.92.172.20]) by m3.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id OAA08070; Fri, 10 Mar 2000 14:15:55 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id OAA74305; Fri, 10 Mar 2000 14:14:41 -0800 (PST) To: Edwin Kremer Cc: Ishmael , current@FreeBSD.ORG Subject: Re: building ports References: <20000309145448.C23820@cs.uu.nl> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 10 Mar 2000 14:13:59 -0800 In-Reply-To: Edwin Kremer's message of "Thu, 9 Mar 2000 14:54:48 +0100" Message-ID: Lines: 13 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Edwin Kremer * On Mon, Mar 08, 1999 at 09:44:26PM -0600, Ishmael wrote: * * : Your system is too old to use this bsd.port.mk. * * According to the mail headers, your system clock is about one year * behind actual time. That might have screwed up the `make'... Yes, that certainly would have. The "date" written in /var/db/pkg/port.mkversion will be one year old! Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 14:49:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 7871537BF40; Fri, 10 Mar 2000 14:49:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA00634; Fri, 10 Mar 2000 14:49:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003102249.OAA00634@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: R Joseph Wright Cc: Mike Smith , freebsd-current@FreeBSD.org Subject: Re: single user mode problem In-reply-to: Your message of "Fri, 10 Mar 2000 11:21:15 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Mar 2000 14:49:45 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Regardless, this is typically syptomatic of either a very old > > /boot/loader, non-use of the loader eg. through a /boot.config file, or > > an error in the entry for / in /etc/fstab. > > > > Isn't /boot/loader updated upon making a new world? If so, it ought to be > current. I don't know any way of finding out since it's a binary file. That's correct. If the loader is run, there is no way for 'wd' to become involved in the process unless a disk error occurs reading from the 'ad' driver. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 14:51:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [192.215.234.86]) by hub.freebsd.org (Postfix) with SMTP id 4BBBC37BB08 for ; Fri, 10 Mar 2000 14:51:47 -0800 (PST) (envelope-from gordont@bluemtn.net) Received: (qmail 23023 invoked by uid 1078); 10 Mar 2000 22:50:11 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Mar 2000 22:50:11 -0000 Date: Fri, 10 Mar 2000 14:50:11 -0800 (PST) From: Gordon Tetlow X-Sender: gordont@sdmail0.sd.bmarts.com To: Lawrence Farr Cc: freebsd-current@freebsd.org Subject: Re: Mylex Support In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Mar 2000, Lawrence Farr wrote: > I have 4 different Mylex DAC960 controllers that I cannot install Current > onto. (Tried from Late December to 20000307). Sysinstall seems to get the > geometry wrong, and even telling sysinstall the "correct" geometry, it gives > a "tied to write beyond end of drive" error. Booting from a running -current > and formatting does the same. They all have the latest BIOS, and they have > been tried with various drive combinations. Has anyone else got this to work > successfully or is it just me?. I know it sounds wierd, but if you boot with a dos floppy and fdisk a small partition onto the drives, it might work. We used to have a problem (not on Mylex controllers though) that sounds the same. After putting on the small partition, boot the install and it will (hopefully) detect the right geometry. Anyone else have any ideas? -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 14:57:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from axt.cna.ne.jp (axt.cna.ne.jp [210.231.112.10]) by hub.freebsd.org (Postfix) with ESMTP id 67CE137C3A1; Fri, 10 Mar 2000 14:57:34 -0800 (PST) (envelope-from ican21@cna.ne.jp) Received: from ogate.cna.ne.jp (ogate.cna.ne.jp [210.231.112.20]) by axt.cna.ne.jp (8.9.3/3.7W00010421) with ESMTP id HAA10515; Sat, 11 Mar 2000 07:57:20 +0900 (JST) Received: from [10.2.129.206] ([10.2.129.206]) by ogate.cna.ne.jp (8.8.8+Sun/8.8.8) with ESMTP id HAA02210; Sat, 11 Mar 2000 07:53:25 +0900 (JST) User-Agent: Microsoft Outlook Express Macintosh Edition - 5.0 (1513) Date: Sat, 11 Mar 2000 07:48:59 +0900 Subject: =?ISO-2022-JP?B?GyRCMWMycSROMWk9UCRLISIhWDR7QjgbKEo=?= =?ISO-2022-JP?B?GyRCJE4lUyE8JWskLCEiJCIkSiQ/TU0kQCQxJE4lUxsoSg==?= =?ISO-2022-JP?B?GyRCITwlayRLJW8lcyU/JUMlQSRHSlE/SCEjIVkbKEo=?= From: =?ISO-2022-JP?B?GyRCRU9KVUUvSVcbKEo=?= Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="ISO-2022-JP" Content-transfer-encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $BEbFM$J%a!<%k$*5v$72<$5$$!#(J $B4?Aw7^2q$d7k:'<0$N%7!<%:%s$G$9!#(J $B$=$3$G!"1c2q44;vMM$K$*CN$i$;$G$9!#(J $B$46=L#$N$J$$J}$K$O?4$+$i$*OM$S?=$7>e$2$^$9$H$H$b$K!"(J $B:o=|$N$*4j$$$r?=$7>e$2$^$9!#(J $B!|!|!|4{B8$N%S!<%k$,$"$J$?MM$@$1$N%S!<%k$K%o%s%?%C%A$GJQ?H!#!|!|!|(J $B!Je$K!"%7!<%k$rE=$j$^$9$,!"E=$C$F$$(J $B$k0cOB46$,A4$/$"$j$^$;$s!#(J $B%"%5%R%9!<%Q!<%I%i%$!"%5%C%]%m9u@8$KBP1~$G$9!#$^$?!"#1#0Kg(J $B!J#1#0K\J,!K$+$i\$7$/$O2<5-$N%[!<%`%Z!<%8$r$4Mw2<$5$$!#(J =====$B!!(Jhttp://www.ican21.com/o_messe/indexf.html$B!!(J======= ------------------------------------------------------------ $B4k6HL>!!!!(J $B3t<02q!!(J $BEOJUE/IW(J $B%a!<%k!!!!(J ican@bau.co.jp TEL$B!!!!!!(J 018-823-9928 FAX$B!!!!!!(J 018-865-6898 $B=;=j!!!!!!(J $B=)ED;T?720A%>lD.(J2-18 $BC4Ev; Fri, 10 Mar 2000 15:00:37 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA74040; Fri, 10 Mar 2000 16:00:34 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA18948; Fri, 10 Mar 2000 16:00:12 -0700 (MST) Message-Id: <200003102300.QAA18948@harmony.village.org> To: Kent Hauser Subject: Re: PCI modems Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 10 Mar 2000 15:43:44 EST." <200003102043.AA00976@lab1.tfd.com> References: <200003102043.AA00976@lab1.tfd.com> Date: Fri, 10 Mar 2000 16:00:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003102043.AA00976@lab1.tfd.com> Kent Hauser writes: : I've tried hard to get my PCI internal modem work with current. Well, there's no support for that yet. : I've tried editing /sys/isa/sio.c with the all possible byte : and word swaps of the vendor/dev printouts from the kernel : probe. The documentation for this USR modem says it's *not* : a winmodem, but a "standalone" modem. Yes. It works with my driver. However, I finished it during the freeze and Bruce requested that I hold off until after 4.0. I'll likely commit it after 4.0 goes golden. Although I have a "fix a pccard panic" fix for sio that's been approved, but not reviewed yet. I could sneak this into that commit :-). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 10 15: 2:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.iae.nl (mail.iae.nl [194.151.64.19]) by hub.freebsd.org (Postfix) with ESMTP id AD8AD37BBC2 for ; Fri, 10 Mar 2000 15:02:34 -0800 (PST) (envelope-from hansot@iae.nl) Received: from iae.nl (pm17d180.iae.nl [212.61.3.180]) by mail.iae.nl (Postfix) with ESMTP id AC6E420F19; Sat, 11 Mar 2000 00:02:28 +0100 (CET) Message-ID: <38C97F03.733B1AA0@iae.nl> Date: Sat, 11 Mar 2000 00:02:27 +0100 From: Hans Ottevanger X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: RC3 install floppies: panic: resource_list_alloc: resource entry is busy References: <200003100804.JAA99578@freebsd.dk> Content-Type: multipart/mixed; boundary="------------660E6D1FF97F825A67EFD117" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------660E6D1FF97F825A67EFD117 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Soren Schmidt wrote: > [...] > Hmm, seems to be a resource conflict problem, question is what is > causing this. Could you do a verbose boot both with the old > working kernel, and the new failing one ? > Attached are two files. Both kernels used are built from the same config file, which is mostly GENERIC with devices removed that I do not have. The file "new" results from booting a kernel built completely from sources cvsupped yesterday. For "old" I replaced the contents of /sys/dev/ata by the files of February 17, i.e. before the major changes. I must remark that this is one of the machines that reports its IDE IRQ as 0 when asked for it. About two months ago there were problems when the ata driver took the timer interrupt. This was fixed by a special clause in ata-all.c, at least up to February 17. Maybe the current problem is related. > > This machine has an Intel motherboard with a Mercury chipset, 64 Mbyte > > RAM, Matrox Millenium II, two Western Digital disks, and it ran all > > previous FreeBSD releases perfectly for almost five years. > > Yeah I notice the RZ 1000 chips in there, BE CAREFULL, I wouldn't > use this for anything I cared about... For serious work I now have two BP6 based machines, this became just a testmachine. I know about the possible data corruption problems with RZ1000 chips, but I have never seen them with FreeBSD, despite the fact that I did a "make world" every other week for more than two years. However, if you run Linux or Solaris on this machine, and forget to switch off the EIDE prefetch buffers, the results can be quite dramatic... Kind regards, Hans --------------660E6D1FF97F825A67EFD117 Content-Type: text/plain; charset=us-ascii; name="new" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="new" SMAP type=01 base=00000000 00000000 len=00000000 0009fc00 SMAP type=01 base=00000000 00100000 len=00000000 03f00000 SMAP type=02 base=00000000 fffc0000 len=00000000 00040000 Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Mar 10 21:43:07 CET 2000 root@myhost.my.domain:/usr/src/sys/compile/CUSTOM Calibrating clock(s) ... TSC clock: 66643091 Hz, i8254 clock: 1300543 Hz 1300543 Hz differs from default of 1193182 Hz by more than 1% Timecounter "i8254" frequency 1193182 Hz TSC clock: 48650664 Hz (Method B) Timecounter "TSC" frequency 48650664 Hz CPU: Pentium/P5 (48.65-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x517 Stepping = 7 Features=0x1bf real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002d1000 - 0x03ff7fff, 64122880 bytes (15655 pages) avail memory = 62267392 (60808K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f0120 bios32: Entry = 0xf145c (c00f145c) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x1440 pnpbios: Found PnP BIOS data at 0xc00f0130 pnpbios: Entry = f0000:1245 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc02b8000. Intel Pentium detected, installing workaround for F00F bug pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x00000000 (0x80000000) pci_open(1b): mode1res=0x00000000 (0xff000001) pci_open(2): mode 2 enable port (0x0cf8) is 0x00 pci_open(2a): mode2res=0x0e (0x0e) pci_open(2a): now trying mechanism 2 pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=04a38086) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 54761513 bytes/sec bzero() bandwidth = 27416038 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x00000000 (0x80000000) pci_open(1b): mode1res=0x00000000 (0xff000001) pci_open(2): mode 2 enable port (0x0cf8) is 0x00 pci_open(2a): mode2res=0x0e (0x0e) pci_open(2a): now trying mechanism 2 pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=04a38086) pcib0: on motherboard found-> vendor=0x8086, dev=0x04a3, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1042, dev=0x1000, revid=0x01 class=01-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 000001f0, size 3 map[14]: type 1, range 32, base 000003f4, size 2 found-> vendor=0x8086, dev=0x0484, revid=0x03 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x102b, dev=0x051b, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base a0000000, size 24 map[14]: type 1, range 32, base a1000000, size 14 map[18]: type 1, range 32, base a1800000, size 23 found-> vendor=0x10b7, dev=0x9200, revid=0x74 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 0000fc80, size 7 map[14]: type 1, range 32, base ffbffc00, size 7 pci0: on pcib0 CPU: Pentium, 66MHz, CPU->Memory posting ON, read around write Warning: Cache parity disabled! Warning: DRAM parity mask! Cache: 256KB writeback, cache clocks=3-2-2-2/4-2-2-2 Cache flags: cache-all byte-control DRAM: page mode memory clocks=X-4-4-4 (70ns) CPU->PCI: posting ON, burst mode ON, PCI clocks=2-1-1-1 PCI->Memory: posting ON Refresh: RAS#Only BurstOf4 atapci0: port 0x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 atapci0: Busmastering DMA not supported panic: resource_list_alloc: resource entry is busy Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.372 db> --------------660E6D1FF97F825A67EFD117 Content-Type: text/plain; charset=us-ascii; name="old" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="old" SMAP type=01 base=00000000 00000000 len=00000000 0009fc00 SMAP type=01 base=00000000 00100000 len=00000000 03f00000 SMAP type=02 base=00000000 fffc0000 len=00000000 00040000 Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Mar 10 22:57:58 CET 2000 root@myhost.my.domain:/home/src/sys/compile/CUSTOM Calibrating clock(s) ... TSC clock: 66643293 Hz, i8254 clock: 1193159 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 66643293 Hz CPU: Pentium/P5 (66.64-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x517 Stepping = 7 Features=0x1bf real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002cf000 - 0x03ff7fff, 64131072 bytes (15657 pages) avail memory = 62275584 (60816K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f0120 bios32: Entry = 0xf145c (c00f145c) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x1440 pnpbios: Found PnP BIOS data at 0xc00f0130 pnpbios: Entry = f0000:1245 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Intel Pentium detected, installing workaround for F00F bug pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x00000000 (0x80000000) pci_open(1b): mode1res=0x00000000 (0xff000001) pci_open(2): mode 2 enable port (0x0cf8) is 0x00 pci_open(2a): mode2res=0x0e (0x0e) pci_open(2a): now trying mechanism 2 pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=04a38086) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 75058170 bytes/sec bzero() bandwidth = 37572797 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x00000000 (0x80000000) pci_open(1b): mode1res=0x00000000 (0xff000001) pci_open(2): mode 2 enable port (0x0cf8) is 0x00 pci_open(2a): mode2res=0x0e (0x0e) pci_open(2a): now trying mechanism 2 pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=04a38086) pcib0: on motherboard found-> vendor=0x8086, dev=0x04a3, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1042, dev=0x1000, revid=0x01 class=01-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 000001f0, size 3 map[14]: type 1, range 32, base 000003f4, size 2 found-> vendor=0x8086, dev=0x0484, revid=0x03 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x102b, dev=0x051b, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base a0000000, size 24 map[14]: type 1, range 32, base a1000000, size 14 map[18]: type 1, range 32, base a1800000, size 23 found-> vendor=0x10b7, dev=0x9200, revid=0x74 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 0000fc80, size 7 map[14]: type 1, range 32, base ffbffc00, size 7 pci0: on pcib0 CPU: Pentium, 66MHz, CPU->Memory posting ON, read around write Warning: Cache parity disabled! Warning: DRAM parity mask! Cache: 256KB writeback, cache clocks=3-2-2-2/4-2-2-2 Cache flags: cache-all byte-control DRAM: page mode memory clocks=X-4-4-4 (70ns) CPU->PCI: posting ON, burst mode ON, PCI clocks=2-1-1-1 PCI->Memory: posting ON Refresh: RAS#Only BurstOf4 ata-pci0: port 0x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 ata-pci0: Busmastering DMA not supported ata0: iobase=0x01f0 altiobase=0x03f4 bmaddr=0x0000 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=50 ata0: devices = 0x3 ata0 at 0x01f0 irq 14 on ata-pci0 isab0: at device 2.0 on pci0 Bus Modes: Bus Park, Resource Lock, Coprocessor errors enabled Keyboard controller: 60h,62h,64h,66h RTC: 70h-77h Port 92: enabled isa0: on isab0 pci0: (vendor=0x102b, dev=0x051b) at 12.0 irq 11 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xfc80-0xfcff mem 0xffbffc00-0xffbffc7f irq 10 at device 14.0 on pci0 xl0: Ethernet address: 00:50:04:d8:b3:c4 xl0: media options word: a xl0: found MII/AUTO miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: xl0 attached Trying Read_Port at 203 Trying Read_Port at 243 CTL0001: start dependant CTL0001: adding irq mask 0x20 CTL0001: adding dma mask 0x2 CTL0001: adding dma mask 0x20 CTL0001: adding io range 0x220-0x22f, size=0x10, align=0x1 CTL0001: adding io range 0x330-0x331, size=0x2, align=0x1 CTL0001: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0001: start dependant CTL0001: adding irq mask 0x6a0 CTL0001: adding dma mask 0xa CTL0001: adding dma mask 0xa0 CTL0001: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0001: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0001: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0001: start dependant CTL0001: adding irq mask 0x6a0 CTL0001: adding dma mask 0xa CTL0001: adding dma mask 0xa0 CTL0001: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0001: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0001: start dependant CTL0001: adding irq mask 0x6a0 CTL0001: adding dma mask 0xa CTL0001: adding dma mask 0xa0 CTL0001: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0001: start dependant CTL0001: adding irq mask 0x6a0 CTL0001: adding dma mask 0xa CTL0001: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0001: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0001: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0001: start dependant CTL0001: adding irq mask 0x6a0 CTL0001: adding dma mask 0xa CTL0001: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0001: end dependant CTL7001: adding io range 0x200-0x207, size=0x8, align=0x1 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: 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 ata-isa0: already registered as ata0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x0000 ata1: mask=01 status0=00 status1=ff ata1: mask=01 status0=00 status1=ffffffff ata1: devices = 0x4 ata1 at port 0x170 irq 15 on isa0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 05 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x61 0x71 0x61 0x61 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1: irq maps: 0x61 0x69 0x61 0x61 sio1 at port 0x2f8-0x2ff irq 3 flags 0x30 on isa0 sio1: type 16550A, console ppc0: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc_detect_fifo: PWord not supported ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port isa_probe_children: probing PnP devices unknown0: