Takahashi Yoshihiro wrote:
>
> > BTW: Is there a special reason to have boot2 in aout?
>
> Because nobody transplant from the i386 boot2 :-).
> FreeBSD(98) porting team is always suffering from a shortage of
> workers.
>
> In article <[EMAIL PROTECTED]>
> Mike Smith <[EMAIL PROTECTED]> writes:
> "JH" == Jon Hamilton <[EMAIL PROTECTED]> writes:
JH> Running -current from this afternoon, I am having a strange
JH> symptom with ppp over a pty; ppp does not detect that the pty
JH> does not support carrier, and will cycle once per second
JH> waiting for CD to appear. Put
In message <[EMAIL PROTECTED]>, Jul
ian Elischer writes:
[sysctlfs]
>Linux have basically done this in their procfs.
And have recently started to wonder if that wasn't a mistake I've heard.
I would regard sysctlfs as a grave mistake.
--
Poul-Henning Kamp FreeBSD coreteam member
[E
In <[EMAIL PROTECTED]> Kenneth Wayne Culver
<[EMAIL PROTECTED]> wrote:
> Just a question which I'm not sure is soundcard related. My xmms no longer
> starts up anymore, it just hangs in Poll before it actually puts anything
> on the display, is that because /dev/dsp isn't working?
On Fri, Dec 10, 1999 at 07:01:49PM +0100, Poul-Henning Kamp wrote:
> The ata driver has been available for you and other to test for a long
> time.
That may be the case, but the vast majority of our users don't run
-current, for good reason, and so are in no position to test it. 4.0
will be t
In message <[EMAIL PROTECTED]>, Wilko Bulte writes:
>On Sat, Dec 11, 1999 at 09:00:52AM -0800, Bob Vaughan wrote:
>> > Subject: Re: HEADSUP: wd driver will be retired!
>> > Date: Fri, 10 Dec 1999 19:19:43 +0100
>> > From: Poul-Henning Kamp <[EMAIL PROTECTED]>
>> >
>> >
>> > Maybe we should put a
"Jordan K. Hubbard" wrote:
>
> > In other words, it's not a problem specific to KLD's .. but
> > it's still a problem :-)
>
> Which raises an important issue - other than walking the sysctl tree
> regularly looking for changes, how does such an application become
> aware that the sysctl space h
On Sat, Dec 11, 1999 at 12:57:04PM -0800, Doug White <[EMAIL PROTECTED]> wrote:
> > I'm getting the "lost disk contact" messages every now and then, but
> > only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's
> > an PPro machine with Intel mobo. Can it be related to newer IBM
In message <[EMAIL PROTECTED]>, Nik Clayton writ
es:
>On Fri, Dec 10, 1999 at 07:01:49PM +0100, Poul-Henning Kamp wrote:
>> The ata driver has been available for you and other to test for a long
>> time.
>
>That may be the case, but the vast majority of our users don't run
>-current, for good re
On Sat, 11 Dec 1999, Marcel Moolenaar wrote:
> "Jordan K. Hubbard" wrote:
>
> > Actually, I'm sad to say that our shiny new sound system does *not*
> > work for some of the most popular audio chipsets on the market today
> > (where the older "luigi" sound system did support them) and this is a
>
On Sun, Dec 12, 1999 at 11:59:38AM +0100, Poul-Henning Kamp wrote:
> >Poul, I'd like to know what's wrong with
> >
> > (1) Putting ata in GENERIC
> >
> > (2) Keeping wd in LINT, commented out
>
> This will not force CURRENT users to change their configs, a config
> with wd in it will still wo
Doug Rabson wrote:
>
> > The recent commits made existing support even worse. Yes, I'm talking
> > about the ESS1888. It's more dead than before. I'll have to make the
> > noise myself these days, and I can tell you it's no opera :-)
> >
> > In short: Gimme patches! I'll be happy to test and, in
In article <[EMAIL PROTECTED]>
Marcel Moolenaar <[EMAIL PROTECTED]> writes:
> Since pc98 only has a specialized boot2 and thus shares boot0 and boot1
> with other architectures, it can be assumed that an ELF boot2 doesn't
> need any special hacking in boot0 and/or boot1, right?
No, if HDD is for
On Sun, 12 Dec 1999, Nik Clayton wrote:
> (3) A big notice in UPDATING, saying that ata is the replacement for
>wd. Make wd require "options I_WANT_WD" or something similar,
>so that people can't simply re-config their existing configuration
>file.
>
To be nasty: Ch
On Sun, 12 Dec 1999, Marcel Moolenaar wrote:
> Doug Rabson wrote:
> >
> > > The recent commits made existing support even worse. Yes, I'm talking
> > > about the ESS1888. It's more dead than before. I'll have to make the
> > > noise myself these days, and I can tell you it's no opera :-)
> > >
>
(Forwarded to -current, due to lack of audience in -smp. Sorry for
bothering you).
-- Forwarded message --
From: Remy Nonnenmacher <[EMAIL PROTECTED]>
Subject: Idle loop in SMP.
Date: Wed, 1 Dec 1999 18:43:40 +0100 (CET)
To: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Wh
Hi,
I have (long time ago) written some extensions to syscons, and
finally decided to clean them up, document and submit them.
(Being tired of updating and merging them every time a new
FreeBSD release comes out...)
The patches can be found in kern/15436, and it would be really
great if they cou
On Sat, Dec 11, 1999 at 11:31:39AM +0200, Maxim Sobolev wrote:
> Some time ago my soundcard (Vibra 16C), which worked just fine
> previously, stopped being recognised/attached. Following is relevant
> pieces of dmesg and pnpinfo:
>
> [...]
> isa_probe_children: probing PnP devices
> unknown0: a
Leif Neland wrote:
>
>
> On Sun, 12 Dec 1999, Nik Clayton wrote:
>
> > (3) A big notice in UPDATING, saying that ata is the replacement for
> >wd. Make wd require "options I_WANT_WD" or something similar,
> >so that people can't simply re-config their existing configuration
"Jordan K. Hubbard" <[EMAIL PROTECTED]> writes:
> > Since the recent block device vanishment, MAKEDEV all and my vinum
> > volumes have failed to start.
>
> Please read /usr/src/UPDATING if you're going to track -current
> these days. The reason for this is clearly documented at the
> top of th
In message <[EMAIL PROTECTED]>, Kevin Street writes:
>Jordan, I don't understand your answer. Using the new MAKEDEV is what
>causes vinum to fail. Won't -release be using the new MAKEDEV?
>
>Greg, is there a mechanism to transition an existing vinum
>installation to the new device nodes?
I th
After rebuilding World and kernel last night, I find that the behavior of
'netstat -a' has changed... Only UNIX domain sockets are shown in the
output, no inet stuff at all, e.g.:
# netstat -a
Active UNIX domain sockets
Address Type Recv-Q Send-QInode Conn Refs Nextref Addr
cbf67
Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Kevin Street writes:
>
> >Jordan, I don't understand your answer. Using the new MAKEDEV is what
> >causes vinum to fail. Won't -release be using the new MAKEDEV?
> >
> >Greg, is there a mechanism to transition an existing vinum
> >insta
I'm on the road now, and writing mail is like pulling teeth. phk
supplied the correct patch. phk, could you commit it, please?
Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
In message <[EMAIL PROTECTED]>, Greg Lehey writes:
>I'm on the road now, and writing mail is like pulling teeth. phk
>supplied the correct patch. phk, could you commit it, please?
Done.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run
At Sun, 12 Dec 1999 16:37:29 +0100,
Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
> I think that between the two of us, Greg and I have lost a oneline
> patch on the floor, try this:
>
> Index: vinumio.c
This patch solved my problem, and I found it has already been
committed to the tree. :)
tha
According to Garrett Wollman:
> It's listening on a kernel notification socket. (Implementation is an
> exercise left for the reader, but there are already a few examples.)
Like the routing socket I guess ?
Or we could implement POLLSYSCTL ? :-)
/me hides and runs
--
Ollivier ROBERT -=- Free
> Jordan, I don't understand your answer. Using the new MAKEDEV is what
> causes vinum to fail. Won't -release be using the new MAKEDEV?
Sorry, I evidently didn't read the message the same way. If the
problem is indeed as you say then vinum has been broken; I thought
he was talking about using
I'm still running a -CURRENT from just before the signal changes and
for the past 4 days, my nightly buildworld has been dying at follows:
===> games/fortune/datfiles
PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile st
rfile -Crs /3.0/cvs/src/games/fortune/datfiles/fo
Against my better judgment, I've been running -current on, among other
machines, a Dell Latitude XP 475C... The wd driver manages to deal with
the inevitable cruft quite nicely, but the ata driver refuses to mount
the root partition.
To the best of my knowledge the chipset is the Western Digital
> Against my better judgment, I've been running -current on, among other
> machines, a Dell Latitude XP 475C... The wd driver manages to deal with
> the inevitable cruft quite nicely, but the ata driver refuses to mount
> the root partition.
>
> To the best of my knowledge the chipset is the Wes
In a kernel built from sources current as of 21:00 EST, I no longer
have sound.
dmesg from yesterday:
pcm0: at port 0x220-0x22f irq 5 drq 1,0 on isa0
unknown0: at port 0x388-0x38f on isa0
joy0: at port 0x200-0x207 on isa0
unknown1: at port 0x330-0x331 irq 9 on isa0
The above worked without
On 1999-Dec-13 11:06:19 +1100, I wrote:
>I'm still running a -CURRENT from just before the signal changes and
>for the past 4 days, my nightly buildworld has been dying at follows:
>
>===> games/fortune/datfiles
>PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile strfile
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help of perlbug 1.26 running under perl 5.00503.
-
[Please enter your report here]
The following segfaults on the "setpos" line. It only
does this with the "
> > boot -v output using the wd driver follows:
>
> That's not very helpful; we know it works. How about some information on
> the problem?
Well... I'd sure like to send a boot -v for a kernel using ata... I don't
have the right hardware here to use a serial console, however.
Here are the rel
Attention, all FreeBSD, OpenBSD and NetBSD developers..
This is a chance we cannot ignore.. Please form up a development team
with a central tram leader and get signed up for this offer. The
Documentation personnel should sign up for the Contributors link to
add BSD's voice in setting the guide
>On 1999-Dec-13 11:06:19 +1100, I wrote:
>I'm still running a -CURRENT from just before the signal changes and
>for the past 4 days, my nightly buildworld has been dying at follows:
>
>===> games/fortune/datfiles
>PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile strfile
On Sun, Dec 12, 1999 at 10:37:01AM -0500, Donald J . Maddox wrote:
> After rebuilding World and kernel last night, I find that the behavior of
> 'netstat -a' has changed... Only UNIX domain sockets are shown in the
Errr... may I complain ?
I got the same problem :(
current last night.
--
CirX
> > > boot -v output using the wd driver follows:
> >
> > That's not very helpful; we know it works. How about some information on
> > the problem?
>
> Well... I'd sure like to send a boot -v for a kernel using ata... I don't
> have the right hardware here to use a serial console, however.
Th
It seems Adam Wight wrote:
> Against my better judgment, I've been running -current on, among other
> machines, a Dell Latitude XP 475C... The wd driver manages to deal with
> the inevitable cruft quite nicely, but the ata driver refuses to mount
> the root partition.
>
> To the best of my knowl
It seems Munehiro Matsuda wrote:
> Hi all,
>
> I am using -current as of December 9 (CTM:src-cur.4130.gz), and
> got following weird ATA related messages while 'make -j4 buildworld'.
> I never had this kind of message when using wd drivers.
>
> ata0-master: ad_timeout: lost disk contact -
It seems Vallo Kallaste wrote:
> On Sat, Dec 11, 1999 at 12:57:04PM -0800, Doug White <[EMAIL PROTECTED]>
>wrote:
>
> > > I'm getting the "lost disk contact" messages every now and then, but
> > > only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's
> > > an PPro machine with
> It seems Munehiro Matsuda wrote:
> > Hi all,
> >
> > I am using -current as of December 9 (CTM:src-cur.4130.gz), and
> > got following weird ATA related messages while 'make -j4 buildworld'.
> > I never had this kind of message when using wd drivers.
> >
> > ata0-master: ad_timeout: lost d
43 matches
Mail list logo
