On Thu, 20 May 1999, Nick Hibma wrote:
>
> You set a 'low' priority for the ide match as -100. I suggest we use a
> much lower value for that: -1. With USB we have 15 levels already,
> spaced ten apart (welcome back BASIC :) makes 150.
>
> Has anyone come up with a decent set of levels yet,
> > #define PRIORITY_FAIL -1
> >
> > It sounds like we can loads of haggling about the names there... The
> > last one is to take out the dependency on errno being greater than
> > zero.
>
> I would actually quite like to keep the possibility of returning an errno.
> It gives
On Fri, 21 May 1999, Nick Hibma wrote:
> > > #define PRIORITY_FAIL-1
> > >
> > > It sounds like we can loads of haggling about the names there... The
> > > last one is to take out the dependency on errno being greater than
> > > zero.
> >
> > I would actually quite like to kee
>> How do you guarantuee that the errno is positive? Add an assert
>> somewhere, like checking whether ENXIO >= PRIORITY_FAIL?
>
>They just are positive and have always been positive :-)
>
>Changing that (making errnos negative) would break so much code I don't
>even want to think about it.
On Fri, 21 May 1999, Bruce Evans wrote:
> >> How do you guarantuee that the errno is positive? Add an assert
> >> somewhere, like checking whether ENXIO >= PRIORITY_FAIL?
> >
> >They just are positive and have always been positive :-)
> >
> >Changing that (making errnos negative) would break so mu
>> >They just are positive and have always been positive :-)
>> >
>> >Changing that (making errnos negative) would break so much code I don't
>> >even want to think about it.
>>
>> >From errno.h:
>>
>> #ifdef KERNEL
>> /* pseudo-errors returned inside kernel to modify return to process */
>> #def
On Fri, 21 May 1999, Bruce Evans wrote:
> >> >They just are positive and have always been positive :-)
> >> >
> >> >Changing that (making errnos negative) would break so much code I don't
> >> >even want to think about it.
> >>
> >> >From errno.h:
> >>
> >> #ifdef KERNEL
> >> /* pseudo-errors re
On Fri, 21 May 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:
> > >
> > > Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I
> > > want
> > > to allow mtrr support for my Voodoo Banshee)
> >
> > It's being worked on. The K6 is a problematic device, as it
In article <199905210435.oaa11...@godzilla.zeta.org.au> you wrote:
>>> I'm not sure why it happens like this; try putting a DELAY() just
>>> before we actually set the root device and see if you can put it off.
>>
>>Why not just spl() protect that printf call so that its output is
>>dumped contigu
<
said:
> How do you guarantuee that the errno is positive? Add an assert
> somewhere, like checking whether ENXIO >= PRIORITY_FAIL?
No, we simply define it to be so.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
woll...@lcs.mit.edu | O Siem / T
>
> > The loader won't help you because you are booting from under DOS, but
> > the loader will boot the kernel just fine off a DOS filesystem.
>
> I'd like to understand this aspect of the loader better. This mode
> might be useful for booting from (for example) a DOS flash filesystem?
Typica
Hi,
I build a 4.0-current SNAP each evenning, and thought I'd give a new
install a try since the dev_t issue appears to have been resolved..
Unfortunately, booting from either a CD or boot floppies, after
probing the ppi0(or maybe plip0) device, the system spontaniously
reboots (and I can't
Hi all,
Is there any commercial products for computer telephony development on *BSD
and/or Linux exists today? Basically we are looking for quite standard
features like interactive voice response, voice messaging, text to speech,
fax, notification systems, etc.
I am in fact trying one product
:
:Matt, I told you about this before, but completely forgot about it. After
:doing considerable testing on my test servers, i thought -current was safe
:enough to try on our production shell servers. I installed -current on one
:of my servers, and to my dismay, it hung. :)
:
:Within 5 minutes of r
>Perhaps I should use the log facility instead of printf in the announce
>code?
This would just duplicate boot-time output, since log() echoes everything
using printf() if the log device is not open.
Bruce
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in
Hi,
Following up on my own mail... I applied the patch below from
John Birrell, and the boot process got farther, but still fails.
Chasing the problem alittle farther I found the following
in ufs/mfs/mfs_vfsops.c:
rootdev = makedev(255, mfs_minor++);
printf(
Hi,
The following patch and John Birrell's patch posted earlier appear
to fix the problem when booting a 4.0-current install floppy(kern.flp).
The DEVT_FASCIST macro is incorrect and does the wrong thing
when the device id 'x' passed into makedev is 255.
Thanks,
John
Index: kern_conf.c
=
17 matches
Mail list logo
