Does it make sense to have a timeout (or perhaps just timestamps) in the
driver, so that after some period of inactivity, you "know" that the
next byte from the moust is the first of a multi-byte message?
louie
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
> On Sun, Jan 28, 2001 at 10:13:49AM +0100, Steve O'Hara-Smith wrote:
> > Hi,
> >
> > Asbestos suit on, round two.
> >
> > The patch below changes getusershell to support a #include syntax
> > in /etc/shells.
>
> I guess this is what I object to. I don't particularly like having
> Perhaps /etc/shells is the least of all evils here.
I think there's way too much paranoia about software systems putting
stuff into /etc. It intended to contain host-specific configuration data
I think there's value in having this configuration data in one or very
few places so you're n
EGP hasn't been in wide use for probably 7 or 8 years now.
I think the real problem with this dynamic link issue and keeping the
connection up is that the default policy is wrong. You ought to
specify what sort of traffic is "important" and should cause a
dynamic link to be established (and ke
>
> > Btw, can I use IGMP to something useful/interesting/funny?
>
> AFAIK it's some kind of dynamic route establishment (learning
> about topology by listening to what your neighbour knows about
> the network). Home users and small LANs won't need it IMHO,
> maybe WAN links will benefit? But
I've got two mobos with VIA MVP3 chipsets on-board. As these systems
(until recently) had only SCSI peripherals, I didn't notice any problem.
However, when I added an IDE CDRW drive, I got these very strange system
lock-ups/hangs. Specifically, this was an FIC VA-503+ mobo, with a
450MHz K6-2 C
>
> I have two reports about machines with 384MB RAM panicing when
> the floppies are accessed. I don't have the message right now
> except for a report that "it said something about bouncebuffers"
I apologize for the vagueness of this response, but perhaps it might
help shed some light.
I've
> > I posted code and results a while back to freebsd-arch which sampled the
> > sound card from userland and analysed the shannon entropy of the noise
> > (for the record, all but one card I tried gave about 6 bits of entropy or
> > more per 16 bit sample with no recording device plugged in, and
> In message <[EMAIL PROTECTED]>, Alexander Langer writ
> es:
> >Thus spake Poul-Henning Kamp ([EMAIL PROTECTED]):
> >
> >> I have thought about adding a entropy server to my array of weird
> >> servers in my lab. Something like a Geiger counter and a smokedetector
> >> could do wonders.
> >
> >H
> > In message <[EMAIL PROTECTED]>, Mark Murray writes:
> >
> > >getnanotime() is already extensively used;
> >
> > I looked at that use, but as far as I can tell, it is only used as a
> > flag at this time, the bits returned by getnanotime() does not end up
> > in the entropy pool ?
>
> Not t
I almost hate to bring this up, but I think the unnamed-here proposed
replacement for our lpd allows you to set your PRINTER environment
variable to something like
[EMAIL PROTECTED]
louie
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
Yes, I started noticing this too while building some ports on a test
machine with last night's -current (I think).
louie
> After today's buildworld, I am seeing lots of warning messages from libc like:
>
> expr in free(): warning: modified (chunk-) pointer
>
> Does it happen to anyone else on
I get errors like this while 'make depend' in the Heimdel code. So far,
in libroken and libasn1.
I tried looking at fixing this, but I fear the build system is too
tricky for me to want to venture in to fix.
louie
mkdep -f .depend -a
-I/usr/src/kerberos5/lib/libasn1/../../../crypto/heimd
> Here is my proposal, adjusted a little as per suggestions. It attempts to
> follow these loose guidelines:
...
> net/ - move existing contents to net/base or something
> similar
>atalk/ - formerly sys/netatalk
>atm/
>
> On 02-Jul-00 Chris Costello wrote:
> > On Sunday, July 02, 2000, John Baldwin wrote:
> >>ip/ - IPv4, IPv6, and IPsec bits from sys/netinet{,6}
> >>tcp/ - TCP""" "
> >>udp/ - UDP"
> Mike Smith wrote:
> >
> > > VMware intercepts the inb/outb instruction to port 0x5658 when the eax
> > > register is set to a magic value, otherwise it would be handled as any
> > > other ports.
> >
> > I think, again, that adding an i386-specific word that detects the
> > presence of VMware i
> On Fri, 5 May 2000, Kris Kennaway wrote:
>
> # It's not clear that you installed the openssl.cnf file before making the
> # cert - can you confirm?
>
> Yes I did. I put it in /etc/ssl as you suggested.
Just curious, but is there any documentation installed that describes
what the contents of
> I wonder how wise it was to change MLEN without more testing. But hey,
> this is -current, that's what it's there for.
I've been running with MLEN set to 256 bytes for more than a year for
reasons unrelated to this commit, and haven't seen any problems at all.
(Of course, I don't use sppp..)
I think that if the sysctl data was reorganized, so that the per
module or instance data was at the leaves of the tree, you could avoid
the problem entirely. This is the general approach used on MIB definitions
used for SNMP; each variable is an instance (usually the 0th) at the
leaf. You don't
> current.freebsd.org is currently down due to a hardware failure. I don't
> have an ETA on when it will be back up again, due to it being offsite.
> I'll post more info as it becomes available.
Usually hardware and software craps out when the "demo detector" kicks
in. It seems that the we've go
I've been messing about with IPSEC in 4.0-current, and have observed some
unexpected behavior. Is there someone I can swap some email with off
the list to determine if what I'm seeing is a bug, or I'm just confused?
It has to do with security policy specifications and what SAID is being
selecte
> Will Andrews wrote:
>
> > On Mon, Feb 28, 2000 at 10:42:22PM +0200, Maxim Sobolev wrote:
> > > Do you have any plans to make XFree86-devel port of it? This let us to test
> > > it and refine before XF-4.0 will be released.
> >
> > I already made one. However, since XFree86 4.0's release is impe
> In message <[EMAIL PROTECTED]> "Louis A. Mamakos" writes:
> : With the 4.0-RC image, and sysinstall, I was now able to use a PCMCIA
> : ethernet to NFS mount the distribution media. It would have been nice
> : if the PCMCIA CDROM drive would have worked, but this
> According to Louis A. Mamakos:
> > a PCMCIA ethernet card, which is real important, as this puppy has
> > a USB floppy and a PCMCIA CDROM drive, neither of which seem to be
>
> You can boot the kern floppy because it is using the BIOS to read the
> disk.. My VAIO a
> Today The Hermit Hacker wrote:
>
> > Up until this afternoon, when I lost an IDE drive, I've been using CVSup'd
> > sources and ports, so haven't fllowed the threads too closely dealing with
> > 4.0RC, so this is probably already known, but ...
> >
> > I just installed two 4.0RC systems this a
> Yep, you're remembering wrong. You can raise the soft limit again,
> but not the hard limit. It's even documented in sh(1):
Maybe the default in bash changed somewhere along the line (modifing the
hard limit rather than the soft limit). Oh well, no problem. It's nice
to know there's a reas
Is it just me, or did something change?
It seems that now you can't raise resource limits after they've been
lowered. I've had a 'ulimit -c 0' in my login profile for a while;
previously when I needed to do debugging, I'd raise the limit to
something reasonable at the shell prompt, and then deb
> On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote:
> > Is it possible to bump the revision of libstdc++ (and perhaps others) so
> > that existing programs can continue to function?
>
> Nope. This is -CURRENT and this type of thing happens. And with a
>
I just put a new -current on my test machine, and watched a bunch of stuff
fall over and die due to the new C++ implementation.
Is it possible to bump the revision of libstdc++ (and perhaps others) so
that existing programs can continue to function? I fear I will be
tracking down occasional bro
> > One other lingering issue - I don't believe we install any of the USB
> > header files (in particular, /sys/dev/usb/usb.h) in /usr/include. While
> > I certainly have /usr/src populated on my box, we probably ought to not
> > require it.
> >
> > Should it be installed in /usr/include/dev/usb
> > Second, a domain name can at most a single CNAME record associated
> > with it, and other other record types. BIND will (should) barf on a
> > zone file containing the example you listed.
>
> It does not. It will round-robin over the CNAME's.
If it does, than this is a bug in BIND. The DN
> > Maybe you should make cvsup.freebsd.org as a rotary (of sorts),
> > which returns a different IP address based on the callers IP
> > address. (or is that even possible?) That way, any given
> > host will always try the same cvsup server, but you'll be
> > spreading the load out among the se
> A nice heuristic that attempts to minimize latency and maximize throughput
> would be a nice feature to have. For extra credit, reverse entropy as well.
>
> Seriously, attempting to connect to a list of servers using record route
> and minimizing the latency and/or hop count would be a great
> What's all this about loopback mounts in fstab about? What does
> that have to do with diskless startup?
I've got a loopback mount in /var/db/mounttab that looks like this:
946789037 localhost /null
which is there because I run cfs (a crypto file system; see
/usr/ports/
> As Pascal Hofstee wrote:
> > With CURRENT-sources updates within an hour ago ... buildworld fails:
>
> Revert to version 1.26 of gnu/lib/libdialog/Makefile. someone broke it when
> he decided to install all the files in TESTS/...
>
> Don't forget to revert to 1.34 of lib/libncurses/Makefile fo
> Any other SCSI CD owners here currently using tosha? I'd be
> quite interested to know if this is drive-specific.
I've used tosha with a "TOSHIBA CD-ROM XM-6201TA 1037" SCSI drive to
read audio data for subsequent mp3 conversion with no problems.
louie
To Unsubscribe: send mail to [EMA
> Louis A. Mamakos wrote:
> >
> > Will we try to include the remaining KAME IPv6 integration into 4.0 before
> > the freeze? It would be nice to have 4.0 with a functioning IPv6 stack and
> > some applications.
>
> IPv6 is a very complex area and I believe
Will we try to include the remaining KAME IPv6 integration into 4.0 before
the freeze? It would be nice to have 4.0 with a functioning IPv6 stack and
some applications.
louie
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> On Mon, 13 Dec 1999, Kris Kennaway wrote:
>
> > On Mon, 13 Dec 1999, Peter Wemm wrote:
> >
> > > I wonder if we should move fortune to usr.bin? It's hardly a game and I'm
> > > way beyond tired of it being left out of standard paths...
> > > (ie: "/bin:/usr/bin[:/usr/local/bin]")
> >
> > I h
> David Malone wrote:
> > I just had the same problem as someone else on the list where I
> > booted after a make world and new kernel, and then fsck reported
> > the filesystems clean but mount said they were dirty. I booted
> > from the old kernel, installed and ran the new MAKEDEV and the
>
I got a few calcru() warnings on a dual Pentium-III Xeon system. It had been
up for around 9 or 10 days or so; I've since rebooted it. Specific
configuration
available if you need it.
louie
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
> "Kenneth D. Merry" <[EMAIL PROTECTED]> writes:
> > Jonathan Lemon wrote...
> > > In article [EMAIL PROTECTED]> you
>write:
> > > > Before I spend a lot of time hunting this down, I figured it might be worth
> > > > asking -- is there any particular reason why TCP sockets may be getting
> > > >
And my mine... I get zero COW optimized faults.
louie@whizzo[20] $ vmstat -s
47312081 cpu context switches
89421468 device interrupts
30438305 software interrupts
16214761 traps
244593116 system calls
1546 swap pager pageins
5124 swap pager pages paged in
4185 swap pager pageo
> On Wed, 11 Aug 1999, Brian F. Feldman wrote:
>
> > What in the world would be the point of doing this? What would be so great
> > about not seeing the system boot up?
>
> One might want minimal or no boot messages, just to look nice, while
> still wanting the dmesg stuff around in case somethi
FYI, I just upgraded from a Pentium/P54C at 133MHz on a Tyan Titan-III
motherboard to an AMD K6-III CPU at 450Mhz (100MHz bus speed) on a
Tyan S1590S "Trinity 100" AT-form factor motherboard. Runs really
good!
I previously built a machine with a K6-2 at 350MHz on an FIC VA-503+
motherboard for
> There's also the the minor nit that there's no documentation. RTSL
> may be OK for developers, but it's not really appropriate for end
> users. This is aggravated by the timers being in 500ms units - phk
> tripped over this recently.
Before documenting it, how about we fix it's name to be mor
I recently tried building a new kernel after quite a bit, and I get a
panic while the system's booting in devfs_makelink, apparently being
called from fd_attach().
Is DEVFS and the new-bus code hopelessly incompatable, and should I just
unconfigure DEVFS? Or is this something that I can dig into
> On Apr 29, 7:41pm, Mike Smith wrote:
> } Subject: Re: ppbus causes hangs?
> }
> } Try setting the flags on the 'ppc' device to 0x40 and _please_ report
> } the results.
>
> I also ran into this problem with a 4/30/1999 version of 3.1-stable
> on a Dell Dimension XPS R400. The 0x40 flag fixed
> On Sun, 28 Mar 1999, Matthew Thyer wrote:
>
> > Is the Creative Labs Soundblaster Live supported under FreeBSD-CURRENT ?
> >
> > This is a PCI card with 3D surround sound (4 speakers).
> >
> > Under Windows it has a soundblaster emulation mode where it emulates
> > a Sound Blaster 16 but the P
> > ===> pccardc
> > cc -O -pipe -I/usr/src/usr.sbin/pccard/pccardc/../pccardd -Wall -g -static
> > -c /usr/src/usr.sbin/pccard/pccardc/beep.c
> > /usr/src/usr.sbin/pccard/pccardc/beep.c: In function `beep_main':
> > /usr/src/usr.sbin/pccard/pccardc/beep.c:74: `PIOCSBEEP' undeclared (first
> > use
I've been trying to play with the USB support lately, and haven't got
much success. I'm running a 4.0-current freshly CVSUPed, and less
than 24 hours old. In summary, here's excepts from what I'm seeing
when doing a verbose boot that appear to be relevent. During a boot,
there is a few second p
I had this problem too. It seems that the code included when you
define USB_DEBUG has suffered some bitrot. Drop this out of your
kernel config, and these compile time errors will go away.
louie
> Hi,
>
> Am I the only one who gets this when he tries to compile a kernel with
> the usb drivers
I've been thinking about this same thing, and I thought that relatively
static fallback list of environments plus an (persistant) index to tell
you what you've tried so far might work. I was considering stealing a
byte from the RTC CMOS to hold the state between reboots.
louie
To Unsubscribe:
53 matches
Mail list logo