In message <87so9r3x44@muon.xs4all.nl> Peter Mutsaers writes:
: Is this a bug that I should report through send-pr, is it already
: known as a bug or is this an intentional change in behaviour?
This is a known bug. I thought I kludged around it in apm.c in the
timeframe that you mentioned. D
%Hmm, I missed that. I took -lc out, but now I get this:
%
[...]
%/usr/local/lib/liblthread.so.0: undefined reference to `_sigsuspend'
%/usr/local/lib/liblthread.so.0: undefined reference to `_nanosleep'
%/usr/local/lib/liblthread.so.0: undefined reference to `_fork'
%/usr/local/lib/liblthread.s
On Saturday, 24 April 1999 at 0:10:17 +0900, Daniel C. Sobral wrote:
> Greg Lehey wrote:
>>
>> This has worked quite nicely for some time. Since yesterday, after
>> building a kernel with newbus support, I get strange messages if I
>> read in the Vinum symbols before reading in the kernel symbols
Hmm, I missed that. I took -lc out, but now I get this:
g++ -o makemake makemake.o ../../include/jcore/JBroadcaster.o
../../include/jcore/JCollectio
n.o ../../include/jcore/JContainer.o ../../include/jcore/JProbDistr.o
../../include/jcore/JOr
deredSetT.o ../../include/jcore/JOrderedSetUtil.o .
> >mp3s aren't playing quite right with x11amp though, little
> >skips here and there, they work fine with the old kernel.
> >mpg123 seems fine, as does the sound in FXTV.
> >I'll try making the world again.
>
> Was there ever any resolution/further inspection of this?
Not as far I know; its stil
On Fri, 23 Apr 1999, Mike Smith wrote:
> >Is there any way I can help in getting the atapi-fd driver to work with
> > LS-120's?
>
> Unless it was just recently broken, it works fine (I have one).
ATA has never worked with my LS-120. It's a Digital Research/Mitsubishi, and
I just can't get it
>> Hmm, you might like to try this patch and see what happens, there is
>> a missing old driver wrapper for the pcm stuff. As a result, it's not
>> getting run from the isa probe. Regarding the other driver, I'm not
>> sure what's going on there as the hooks appear to be present.
>
>Right on, th
>Is there any way I can help in getting the atapi-fd driver to work with
> LS-120's?
Unless it was just recently broken, it works fine (I have one).
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \
> The problem was not really a bios problem not sure what the guys
> did to fix the boot loader probably switch to using a dos int function
> to access the keyboard from the boot loader.
I haven't seen anything (being disconnected), but I thought I should
just slap you for being so stupid as to t
> > > P.S.: USBDI as in, our version of it. The people from the consortium
> > > kicked us out.
>
> > Can you elaborate on the reason that USBDI does not FreeBSD
> > to be involved with the consortium?
>
> Money. We cannot pay the fee (>1000 US $) to join the kindergarten aka
> consortium. N
I rebuilt my kernel just after the new config stuff (nexus). Since
then (but I'm not 100% sure it is related to this) my desktop computer
doesn't suspend anymore.
Before that, I could suspend it either by:
- pressing the suspend button
- zzz command (apm -z)
- wait until BIOS-set time for suspend
Sean Eric Fagan wrote:
> >> Here's a thing I've missed a couple of times: I'd like to be
> >> able to see the limits for a process in /proc.
>
> At some point, I want to add an ioctl to get various process information
> (well, multiple ioctl's, I think); SysVr4 has a bunch, and that's what I'd
>
Anthony Kimball wrote:
>
> : Against that there is a general Linuxism/Kitchen-Sink feeling.
>
> Think of this case as a plan9-ism.
I think nothing of it... My opinions wouldn't matter a tiny little
bit. :-)
Still, after reading the Samba reply to the Microsoft, err,
Mindcraft NTvsLinus benchmar
:
: Against that there is a general Linuxism/Kitchen-Sink feeling.
:
Think of this case as a plan9-ism.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Trying to see what the success rate is with everyone who's
able to get Code Crusader 2.0.x to compile on FreeBSD either on -stable or
-current. I have had no luck with getting it to compile on -stable (nor
-current right now).
ACE compiles successfully with config-freebsd-pthread.h
and platform_f
>> Here's a thing I've missed a couple of times: I'd like to be
>> able to see the limits for a process in /proc.
At some point, I want to add an ioctl to get various process information
(well, multiple ioctl's, I think); SysVr4 has a bunch, and that's what I'd
model it on.
>I'd like to be able
On Fri, 23 Apr 1999, steven wrote:
>At first i went to 4.x-Current, during buildworld colldef fails
>giving dont know how to make de_DE.ISO_8859-15 (i think.. doing from
>memory)
>
>so i tried the latest 3.x-Current and now i get syntax error's and error
>69 when in build world. Someone posted mak
Currently running 3.0-Current on my dual ppro machine. I cvsup'd this
version back in mid Jan and thought it was time to try again.
At first i went to 4.x-Current, during buildworld colldef fails
giving dont know how to make de_DE.ISO_8859-15 (i think.. doing from
memory)
so i tried the latest 3
It seems Rick Whitesel wrote:
> Hi:
> I believe the problems I started having with the new IDE drivers may
> be related to the bugs in the SMP IRQ handler described by Roger Hardiman. I
> am going to wait until Roger fixes the bug to see if my IDE problem
> disappears. I tried the latest dr
Dom Mitchell wrote:
>
> As for making ps totally proc aware, I'm not totally sure that's the way
> to go. I shall have to have a look through the archives though; I've a
> feeling that this has been discussed before...
DCS, The Archive Man, comes to your help.
If you make ps procfs dependent, y
Greg Lehey wrote:
>
> This has worked quite nicely for some time. Since yesterday, after
> building a kernel with newbus support, I get strange messages if I
> read in the Vinum symbols before reading in the kernel symbols:
...
> I debugged gdb and found that it was finding these references
> (
Dom Mitchell writes:
>On 23 April 1999, adr...@freebsd.org proclaimed:
>> Dom Mitchell writes:
>> >What we really need are some tools similiar to solaris' /usr/proc/bin
>> >stuff. http://www.sunworld.com/swol-04-1999/swol-04-supersys.html
>> >Sadly, the ability to do this lies well outside my meag
On 23 April 1999, adr...@freebsd.org proclaimed:
> Dom Mitchell writes:
> >What we really need are some tools similiar to solaris' /usr/proc/bin
> >stuff. http://www.sunworld.com/swol-04-1999/swol-04-supersys.html
> >Sadly, the ability to do this lies well outside my meagre coding
> >knowledge.
>
Dom Mitchell writes:
>On 23 April 1999, Poul-Henning Kamp proclaimed:
>> No, I just want a way to figure out what login.conf have done to
>> various processes...
>
>What we really need are some tools similiar to solaris' /usr/proc/bin
>stuff. http://www.sunworld.com/swol-04-1999/swol-04-supersys.h
Hi,
i was wondering if the limitations that are supposed to be enforced via
the login.conf mechanism do really work...
In particular, i have tried (on 3.1 something, but don't think that
current is much different in this respect) to enforce the daily etc.
login times but the system seems to ignor
On 23 April 1999, Poul-Henning Kamp proclaimed:
> No, I just want a way to figure out what login.conf have done to
> various processes...
What we really need are some tools similiar to solaris' /usr/proc/bin
stuff. http://www.sunworld.com/swol-04-1999/swol-04-supersys.html
Sadly, the ability to d
In message <19990423123108.14692.qm...@ewok.creative.net.au>, adr...@freebsd.or
G writes:
>I've finished the patch. I'll test it a little more when I get back
>home tonight, and then send the URL to -current for people to poke
>around with.
>
Cool!
>phk - I hope you didn't also want the process
Zach Heilig writes:
>On Fri, Apr 23, 1999 at 05:16:33PM +0800, adr...@freebsd.org wrote:
>> I don't know about that one, but the first one sounds easish.
>> Since I've been messing around with procfs quite a bit lately,
>> I'll spend some time later today poking around and produce a patch
>> agains
On Fri, Apr 23, 1999 at 05:16:33PM +0800, adr...@freebsd.org wrote:
> I don't know about that one, but the first one sounds easish.
> Since I've been messing around with procfs quite a bit lately,
> I'll spend some time later today poking around and produce a patch
> against -current .
I don't kno
Hi:
I believe the problems I started having with the new IDE drivers may
be related to the bugs in the SMP IRQ handler described by Roger Hardiman. I
am going to wait until Roger fixes the bug to see if my IDE problem
disappears. I tried the latest drivers on a non SMP motherboard and they
Mikhail Teterin writes:
>adr...@freebsd.org once stated:
>
>=I just went to config a kernel on a -current system supped yesterday,
>=with the source sitting in my home directory,and suddenly ..
>=
>=adr...@java:/usr/home/adrian/work/procfs/sys/compile/JAVA$ make depend
>=make: don't know how to mak
I just went to config a kernel on a -current system supped yesterday,
with the source sitting in my home directory,and suddenly ..
adr...@java:/usr/home/adrian/work/procfs/sys/compile/JAVA$ make depend
make: don't know how to make ../../../include/stddef.h. Stop
adr...@java:/usr/home/adrian/work/
David Malone writes:
>> Here's a thing I've missed a couple of times: I'd like to be
>> able to see the limits for a process in /proc.
>
>I'd like to be able to open processes file discriptors too (so
>you can still get files back if all the filsystem references to
>it have gone, but a process st
> And does this all mean that if I want my kernel source tree to be
> consistent more often than not (and any errors be fixed as soon as
> possible), I'd be better off switching from -stable to -current?
Yes and no. Stable will give you a broken tree less often. But people in
Current have a ha
p...@originative.co.uk writes:
> > From: Richard Tobin [mailto:rich...@cogsci.ed.ac.uk]
> > Is this fix going into stable? (I'm a little surprised that such a
> > change was considered appropriate for the stable branch in the first
> > place.)
>
> I didn't think the memory allocation change was
35 matches
Mail list logo
