tcpdump problem with 4.3-Release

Is there a problem with tcpdump on 4.3-Release? On a system with very low packet rates, tcpdump never displays any packets. Its as if its in buffered mode. Eventually it will show traffic, but it appears that some of the packets are not actually displayed. On a system with lots of traffic,

Re: serial console

How are you preventing unauthorized access via the PM2? I haven't found any way to prevent it. At 16:04 -0700 5/14/01, Jason DiCioccio wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >I've found the Portmaster 2E to be quite good at this too :).. > >- - Original Message - >From

Re: soft update should be default

On Fri, May 04, 2001 at 10:39:51PM -0400, Chris BeHanna wrote: > On Fri, 4 May 2001, Tadayuki OKADA wrote: [...] > > I've heard that it always keeps consistency. > > So you can skip fsck after the crash. > > #I don't know the detail, so please someone correct me if I'm wrong. > > I've had a num

Re: Heimdal breakage - char * vs. const char *

On 15 May, [EMAIL PROTECTED] wrote: > There was of course another problem too. Now I've tested my fix for > that and my RELENG_4 box has done a full build successfully. Verify > that you have: > > lib/libasn1/Makefile: 1.3.2.4 > lib/libhdb/Makefile: 1.2.2.2 > > If you do and it still fails to

Re: .login_conf can overwrite values from /etc/login.conf

Hi, Thanks for pointing out that part of the man page. I played around with it somemore, and found out that even if /etc/login.conf has filesize-max, the user can override that setting with his .login_conf. What I'm essentially discovering is that the user is not restricted to the "me" keyword

Re: serial console

On Mon, 14 May 2001, Jason DiCioccio wrote: > I've found the Portmaster 2E to be quite good at this too :).. For a single box, Telebit Netblazer LS'es work extremely well, with the added bonus that you can use DC 5V to power the thing instead of AC. I suppose someone will soon mention those ser

Re: HEADS UP - fxp now requires miibus

On 2001-05-13 01:20 -0400, Mike Tancsa <[EMAIL PROTECTED]> wrote: > > Any luck with the 815E issue ? > > fxp1: port 0xc400-0xc43f mem 0xd5101000-0xd5101fff > irq 15 at device 8.0 on pci1 > fxp1: Ethernet address 00:01:80:07:1e:f4 > inphy1: on miibus1 > inphy1: 10baseT, 10baseT-FDX, 100baseTX

Re: Heimdal breakage - char * vs. const char *

Peter Pentchev <[EMAIL PROTECTED]> writes: > > Three days later, RELENG_4 build still seems to break in exactly > > the same place. Your fix does not appear to have been a fix. > > Hmm? I just rebuilt my -stable machine, and everything compiled fine. There was of course another problem too. N

Re: serial console

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've found the Portmaster 2E to be quite good at this too :).. - - Original Message - From: "Nick Barnes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 14, 2001 12:40 PM Subject: serial console > I have received several ind

Re: Running Stable on remote production server

Juha Saarinen([EMAIL PROTECTED])@2001.05.14 08:12:07 +: > On Sun, 13 May 2001, Stephen Hilton wrote: > > > How can you accomplish the single user installworld steps on a remote system ? > > Especially the mergemaster program that involves interactive routines ? > > I would be using SSH to con

Re: Running Stable on remote production server

Stephen Hilton([EMAIL PROTECTED])@2001.05.13 10:57:03 +: > Subject: Re: Running Stable on remote production server > > How can you accomplish the single user installworld steps on a remote system ? > Especially the mergemaster program that involves interactive routines ? > I would be using SS

serial console

I have received several individual replies to this message, asking for more details of setting up a serial console. I haven't actually done this myself since 2.2.5 (or maybe 2.2.8), and the procedure has changed a little since then. I refer people to the relevant section of the handbook: http:/

Re: make world still broken around krb4_version bug--when will the patch reach stable?

Nat Lanza wrote: > > John Merryweather Cooper <[EMAIL PROTECTED]> writes: > > > I'm open to other suggestions, and I'll do the rm -rfd /usr/src if I > > absolutely have to, but I'd rather avoid it. > > I just tried deleting /usr/src, re-cvsupping, and rebuilding, and it > still dies at the same

vlans broken on fxp0 ?

Has anyone been able to get VLANs working with the latest commits from this morning ? This is using fxp0: port 0xc000-0xc03f mem 0xd500-0xd50f,0xd510-0xd5100fff irq 11 at device 4.0 on pci1 fxp0: Ethernet address 00:03:47:0c:86:20 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX