In message <[EMAIL PROTECTED]> Vincent Poy
writes:
: Somehow I always thought there were more than 50 people who are
: "really running" current. We do stress test it though and it had
: performed flawlessly over the past 8 years. Question though, does anyone
: happen to know what the larg
In message <[EMAIL PROTECTED]> Daniel Eischen
writes:
: Were we going to do anything to get rid of:
:
: #define stdin (&__sF[0])
: #define stdout (&__sF[1])
: #define stderr (&__sF[2])
:
: for 5.0-release, or is the current fix the one we want to
: go with. I don't know i
On 20 Jul, Mike Smith wrote:
>> attached is a diff for rc.i386, rc.conf.5 and defaults/rc.conf which
>> allows to enable the ACPI power management in rc.conf similar to
>> apm_enable.
>
> This is not a good idea; ACPI isn't "on" or "off", and by the time
What does "acpiconf -e" do then?
Bye,
A
> On 20 Jul, Mike Smith wrote:
> >> attached is a diff for rc.i386, rc.conf.5 and defaults/rc.conf which
> >> allows to enable the ACPI power management in rc.conf similar to
> >> apm_enable.
> >
> > This is not a good idea; ACPI isn't "on" or "off", and by the time
>
> What does "acpiconf -e"
Looks as if there was an oversight associated with some of this, which
breaks the buildworld:
>>> stage 4: building everything..
...
===> usr.sbin/acpi
===> usr.sbin/acpi/acpiconf
cc -O -pipe -I/usr/src/usr.sbin/acpi/acpiconf/../../../sys
-I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.s
On 21-Jul-01 Mike Smith wrote:
>> On 20 Jul, Mike Smith wrote:
>> >> attached is a diff for rc.i386, rc.conf.5 and defaults/rc.conf which
>> >> allows to enable the ACPI power management in rc.conf similar to
>> >> apm_enable.
>> >
>> > This is not a good idea; ACPI isn't "on" or "off", and by t
OK; the buildworld & build/install of the kernel went OK, but the
installworld said:
install -C -c -o root -g wheel -m 644 isdn/i4brunppp/Makefile
/usr/share/examples/isdn/i4brunppp/Makefile
install: /usr/share/examples/isdn/i4brunppp/Makefile: No such file or directory
*** Error code 71
Stop i
