Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Garrett Wollman writes:
> : < said:
> : > Hmmm, they look good to me. Maybe Mark's system doesn't have group
> : > operator at gid 5. That's one bad thing about the new DEVFS: it
> : > appears to enshrine things like this in the kernel...
>
> In message <[EMAIL PROTECTED]> Mark Murray writ
es:
> : > I don't know either. However, it might be because of permission
> : > problems. It will return EINVAL when it can't open the apm file for
> : > write. Maybe a devfs related issue?
> :
> : I don't have devfs on this system yet.
>
> Od
> : > I don't know either. However, it might be because of permission
> : > problems. It will return EINVAL when it can't open the apm file for
> : > write. Maybe a devfs related issue?
> :
> : Hmm, it may not be using the right perms during make_dev perhaps.
>
> Hmmm, they look good to me.
In message <[EMAIL PROTECTED]> Mark Murray writes:
: > I don't know either. However, it might be because of permission
: > problems. It will return EINVAL when it can't open the apm file for
: > write. Maybe a devfs related issue?
:
: I don't have devfs on this system yet.
Odd that. That's t
> I don't know either. However, it might be because of permission
> problems. It will return EINVAL when it can't open the apm file for
> write. Maybe a devfs related issue?
I don't have devfs on this system yet.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscr
> > : zzz/apm -z gives me "apm: ioctl(APMIO_SUSPEND): Invalid argument"
> >
> > I noticed this with the first SMPNG kernel I tried. The newer one
> > this problem disappeared. Don't know why it would matter, but I may
> > have missed a commit while in new mexico.
>
> It may be a kernel/world s
On Thu, Sep 14, 2000 at 04:53:54PM -0400, Garrett Wollman wrote:
> (Probably easier, actually, but I don't know AWK well enough to
> actually implement it.)
awk -F: '$0 ~/^(#|$)/ {next}
{print "#define\tUID_" toupper($1) "\t" $3}' ${PASSWD} > ${.TARGET}
--
Jos Backus _/ _/_
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> John Baldwin writes:
>: Warner Losh wrote:
>: > In message <[EMAIL PROTECTED]> John Baldwin writes:
>: > : It may be a kernel/world sync problem. Although I don't know why the ioctl
>: > : argument would suddenly
< It would only take a small amount of Makefile magic to fix
> this... something like:
> perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \
>$_[2], "\n");' ${PASSWD} >${.TARGET}
Oh, I forgot to point out -- this would be easy to do in AWK a
In message <[EMAIL PROTECTED]> Garrett Wollman writes:
: < said:
: > Hmmm, they look good to me. Maybe Mark's system doesn't have group
: > operator at gid 5. That's one bad thing about the new DEVFS: it
: > appears to enshrine things like this in the kernel...
:
: It would only take a small am
< said:
> Hmmm, they look good to me. Maybe Mark's system doesn't have group
> operator at gid 5. That's one bad thing about the new DEVFS: it
> appears to enshrine things like this in the kernel...
It would only take a small amount of Makefile magic to fix
this... something like:
PASSWD?=
In message <[EMAIL PROTECTED]> John Baldwin writes:
: Warner Losh wrote:
: > In message <[EMAIL PROTECTED]> John Baldwin writes:
: > : It may be a kernel/world sync problem. Although I don't know why the ioctl
: > : argument would suddenly become invalid. Maybe it passes in a struct ucred,
: > :
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> John Baldwin writes:
> : It may be a kernel/world sync problem. Although I don't know why the ioctl
> : argument would suddenly become invalid. Maybe it passes in a struct ucred,
> : which changed in size just before the SMPng commit?
>
> I do
In message <[EMAIL PROTECTED]> John Baldwin writes:
: It may be a kernel/world sync problem. Although I don't know why the ioctl
: argument would suddenly become invalid. Maybe it passes in a struct ucred,
: which changed in size just before the SMPng commit?
I don't know either. However, it m
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Mark Murray writes:
> : > In message <[EMAIL PROTECTED]> Warner Losh wri
> : tes:
> : > : 2) APM is now broken. It worked after the ACPI integration,
> : > :but after the SMPNG stuff neither apm -z nor the BIOS keys
> : > :
In message <[EMAIL PROTECTED]> Mark Murray writes:
: > In message <[EMAIL PROTECTED]> Warner Losh wri
: tes:
: > : 2) APM is now broken. It worked after the ACPI integration,
: > : but after the SMPNG stuff neither apm -z nor the BIOS keys
: > : seems to suspend.
: >
: > Turns out th
> In message <[EMAIL PROTECTED]> Warner Losh wri
tes:
> : 2) APM is now broken. It worked after the ACPI integration,
> :but after the SMPNG stuff neither apm -z nor the BIOS keys
> :seems to suspend.
>
> Turns out this isn't the case.
shutdown -p does not turn off the machi
In message <[EMAIL PROTECTED]> Sheldon Hearn writes:
: > 7) SSH to a machine on my local network is dog slow
: >sometimes. I can type about one line or two lines ahead of
: >it in email when it happens. It feels like a network pause
: >of about 1-2 seconds. Local win
In message <[EMAIL PROTECTED]> Warner Losh writes:
: 2) APM is now broken. It worked after the ACPI integration,
: but after the SMPNG stuff neither apm -z nor the BIOS keys
: seems to suspend.
Turns out this isn't the case.
: 3) Linux emuation is panics the machin
On Fri, 08 Sep 2000 00:01:54 MST, John Baldwin wrote:
> > 3) Linux emuation is panics the machine in linux_open on
> >a normal boot.
>
> Hate to ask, but are you sure it is loading the right module? With
> the kernel.ko change, modules don't live in the same place anymore,
> and I
On Fri, 08 Sep 2000 00:36:12 CST, Warner Losh wrote:
> 6) Switching virtual termintals from the X server to the
> console is busted.
This does not appear to be a problem here, with SMPng and XFree86-3.3.6.
> 7) SSH to a machine on my local network is dog slow
> s
Warner Losh wrote:
>
> I've noticed a few things wrong with the SMPNG code. These are mostly
> impressions. As I learn more about them, I'll file more formal bug
> reports. This is an FYI to fellow travelers along the path.
> 1) You can't have I386_CPU at all. This is likely bad in
>
22 matches
Mail list logo
