I have a boatload of patches I'd like to have reviewed. They are
fixes for most of the current batch of compiler warnings in make
buildworld. Any takers? I did fine one bug, I think.
Warner
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of t
Replying to both Scott Michel and Russell L. Carter:
Scott.
According to man pthread, libc_r is pulled in automatically by the -pthread
switch.
On Fri, 23 Apr 1999, Luigi Rizzo wrote:
> 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 t
The type of the member id_port in isa_device structure is signed short
and a value is converted int unsigned long to allocate I/O port
resource via bus_alloc_resources. If an I/O port >= 0x8000,
conversion from signed short to unsigned long causes unexpected result
and nexus_alloc_resouce cannot
Andrzej Bialecki writes:
> On Fri, 23 Apr 1999, Luigi Rizzo wrote:
>
> > 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
> > cur
Hello,
Is there anyone know how to fix the problem. I cannot make world with source
src-cur.3843 and the error is as followings. Thanks.
Clarence
=== Error ===
cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc
-I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/
On Sat, 24 Apr 1999, KATO Takenori wrote:
> The type of the member id_port in isa_device structure is signed short
> and a value is converted int unsigned long to allocate I/O port
> resource via bus_alloc_resources. If an I/O port >= 0x8000,
> conversion from signed short to unsigned long cause
On Sat, 24 Apr 1999, Stephane Legrand wrote:
> > That's also my impression. I glipmsed the whole source tree and I couldn't
> > find any place where the limits are enforced. BTW. what entity should
> > enforce login time limits? Kernel? Some user-space daemon?
> >
>
> To report a login.conf
Hi,
I'd love to play with the new IDE drivers, especially that I got an LS-120
drive, but... I can't mount my filesystems with it. I'm using today's
sources (kernel config file attached), and it fsck's them just ok, and
then just hangs. Keyboard works, though. If I boot with -v, it reports:
ad0:
On Sat, 24 Apr 1999, Stephane Legrand wrote:
> Andrzej Bialecki writes:
> > On Fri, 23 Apr 1999, Luigi Rizzo wrote:
> >
> > > Hi,
> > >
> > > i was wondering if the limitations that are supposed to be enforced via
> > > the login.conf mechanism do really work...
> > >
> > > In particula
On Sat, 24 Apr 1999, Andrzej Bialecki wrote:
> Hi,
>
> I'd love to play with the new IDE drivers, especially that I got an LS-120
Note that wfd is here for those drives.. I'm currently in a sticky situation:
wd: works with all drives, does no manner of DMA on my 6.4G Medalist
ATA
On Sat, 24 Apr 1999, Brian Feldman wrote:
> On Sat, 24 Apr 1999, Stephane Legrand wrote:
>
> > Andrzej Bialecki writes:
> > > On Fri, 23 Apr 1999, Luigi Rizzo wrote:
> > >
> > > > Hi,
> > > >
> > > > i was wondering if the limitations that are supposed to be enforced via
> > > > the log
Doug Rabson wrote:
> It needs to be signed since the value -1 is used to indicate no port
> resources. Perhaps it would be better to change it to 'int' instead of
> 'u_short'.
Oops, I didn't realize this case.
The assumption that an I/O port address is lower than 0x8000 is OK for
IBM-PC's ISA-b
> > "cputime" ressource limit. I set it to zero and that worked very
> > well. So may be only some limits are implemented ?
>
> You're right, this part works. However, I was talking about login time
> (which is how long can user be logged on to the system), which isn't
> checked anywhere.
too bad
Singed shorts are often the result of sitting on a stove during the
summer.
We also recently saw a "hanging root device to..." in a boot on one of our
machines.
:-)
Robert N Watson
rob...@fledge.watson.org http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A
Andrzej Bialecki wrote:
>
> On Sat, 24 Apr 1999, Stephane Legrand wrote:
>
> > > That's also my impression. I glipmsed the whole source tree and I
> > couldn't
> > > find any place where the limits are enforced. BTW. what entity should
> > > enforce login time limits? Kernel? Some user-space
On Sun, 25 Apr 1999, KATO Takenori wrote:
> Doug Rabson wrote:
>
> > It needs to be signed since the value -1 is used to indicate no port
> > resources. Perhaps it would be better to change it to 'int' instead of
> > 'u_short'.
>
> Oops, I didn't realize this case.
>
> The assumption that an I
>
> Singed shorts are often the result of sitting on a stove during the
> summer.
>
> We also recently saw a "hanging root device to..." in a boot on one of our
> machines.
You'll see the 'c' up above all of the SCSI device probe messages. Not
sure how we go about making that one tidy.
--
This shouldn't cause much in the way of trouble, but it will complain
about old lint in your config files. That includes 'net/tty/bio/cam'
mask indicators, and 'vector xxxintr' as well as some of the wierder
workarounds for the poor 'options' parsing.
So: things like:
device sio1 at isa? tty port
On Sat, Apr 24, 1999, Peter Wemm wrote:
> This shouldn't cause much in the way of trouble, but it will complain
> about old lint in your config files. That includes 'net/tty/bio/cam'
> mask indicators, and 'vector xxxintr' as well as some of the wierder
> workarounds for the poor 'options' parsing
Chris Costello wrote:
> On Sat, Apr 24, 1999, Peter Wemm wrote:
> > This shouldn't cause much in the way of trouble, but it will complain
> > about old lint in your config files. That includes 'net/tty/bio/cam'
> > mask indicators, and 'vector xxxintr' as well as some of the wierder
> > workaround
In article ,
Andrzej Bialecki wrote:
> On Fri, 23 Apr 1999, Luigi Rizzo wrote:
>
> That's also my impression. I glipmsed the whole source tree and I couldn't
> find any place where the limits are enforced. BTW. what entity should
> enforce login time limits? Kernel? Some user-space daemon?
Pre-
>> >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;
Luigi Rizzo once stated:
=> > "cputime" ressource limit. I set it to zero and that worked very
=> > well. So may be only some limits are implemented ?
=>
=> You're right, this part works. However, I was talking about login time
=> (which is how long can user be logged on to the system), which isn
Doug Rabson once stated:
=> If this should not be in sys/i386/isa, I will copy this file into
=> sys/pc98/pc98. Comment please.
=
=It needs to be signed since the value -1 is used to indicate no port
=resources. Perhaps it would be better to change it to 'int' instead of
='u_short'.
Uff, waistin
I was just wondering when and if sound was going to be fixed anytime soon,
I'm still getting the same error as the last time I mailed.
I just cvsupped about an hour ago, so I'm pretty up to date.
Kenneth Culver
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-curren
:> The assumption that an I/O port address is lower than 0x8000 is OK for
:> IBM-PC's ISA-bus, but PC98 can use hiher addresses for ISA-bus like
:> bus.
:
:I understand. I think the best thing is to store the port address as an
:int. I don't think there is a need to fork the file into a pc98 versio
27 matches
Mail list logo
