Hi
I'm looking at this; I'll have something by the end of the weekend
for 5-CURRENT; 4-STABLE will take a bit longer. I don't think I'll
dop anything for 3-* as it is at its end-of-life.
Domo Arrigato!
M
>
> Setting status flags using F_SETFL command of fcntl(2) on the file
> descriptor, whic
> I'm looking at this; I'll have something by the end of the weekend
> for 5-CURRENT; 4-STABLE will take a bit longer. I don't think I'll
Wow, great.
> dop anything for 3-* as it is at its end-of-life.
I agree. We can ignore 3-* as long as they don't show any big
problem.
Cheers,
h.hanai
To
On Sat, 29 Jul 2000, Hiroyuki Hanai wrote:
>
> Setting status flags using F_SETFL command of fcntl(2) on the file
> descriptor, which is returned by open(2)ing /dev/random, seems not to
> be supported. For example, when I run following code;
>
> [...]
>
> 3.4-RELEASE(and possibly 3.5 and 3.5.1)
Hi,
while trying to read (dd if=/dev/cd0c) from a damaged cd (the surface is
a little bit damaged), I've got a panic:
---snip---
#0 boot (howto=260) at ../../kern/kern_shutdown.c:303
#1 0xc01a0f19 in panic (fmt=0xc029aa60 "lockmgr: pid %d, not %s %d unlocking")
at ../../kern/kern_shutdown.c
Ok, I give up. It seems that the world change from exit to sys_exit
broke the world build, but I can't figure out where. I've fixed every
occurence of SYS_exit in the source tree (this one seems to be
src/lib/csu/i386/crt0.c, but there were some in gdb as well), and
removed /usr/obj - and I still
Mike Meyer wrote:
>
> Ok, I give up. It seems that the world change from exit to sys_exit
> broke the world build, but I can't figure out where. I've fixed every
> occurence of SYS_exit in the source tree (this one seems to be
> src/lib/csu/i386/crt0.c, but there were some in gdb as well), and
>
Argh! I knew today was going to stay a bad day.
I am pretty sure I know how to fix this and will commit a fix shortly. If you
want to try now, edit sys/kern/syscalls.master:
< 1 STD NOHIDE { void sys_exit(int rval); } sys_exit sys_exit_args void
---
> 1 STD NOHIDE { void sys_e
Peter Wemm writes:
> Argh! I knew today was going to stay a bad day.
I had similar thoughts about mine, both before I started the build,
and afterwards.
> I am pretty sure I know how to fix this and will commit a fix shortly. If you
> want to try now, edit sys/kern/syscalls.master:
> < 1 S
Mike Meyer wrote:
> Peter Wemm writes:
> > Argh! I knew today was going to stay a bad day.
>
> I had similar thoughts about mine, both before I started the build,
> and afterwards.
>
> > I am pretty sure I know how to fix this and will commit a fix shortly. If
you
> > want to try now, edi
On Fri, Jul 28, 2000 at 02:17:31PM -0700, Andrey A. Chernov wrote:
> I too. The only way I can avoid this panic is
>
> 1) Remove /erc/rc.shutdown (which write files)
> 2) Do several syns manually before reboot.
>
> In all other situations I got this panic.
Just another way (suggested
n Sat, 29 Jul 2000, Hiroyuki Hanai wrote:
> Setting status flags using F_SETFL command of fcntl(2) on the file
> descriptor, which is returned by open(2)ing /dev/random, seems not to
> be supported. For example, when I run following code;
File flags should be handled at the file level, and mostl
What hardware?
On Sat, 29 Jul 2000, Alexander Leidinger wrote:
> Hi,
>
> while trying to read (dd if=/dev/cd0c) from a damaged cd (the surface is
> a little bit damaged), I've got a panic:
> ---snip---
> #0 boot (howto=260) at ../../kern/kern_shutdown.c:303
> #1 0xc01a0f19 in panic (fmt=0xc0
On 29 Jul, Matthew Jacob wrote:
>
> What hardware?
ahc0: port 0xb000-0xb0ff mem
0xd980-0xd9800fff irq 9 at device 6.0 on pci0
ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
cd0 at ahc0 bus 0 target 1 lun 0
cd0: Removable CD-ROM SCSI-2 device
cd0: 10.000MB/s transfers (10.000MHz, of
Ben Smithurst wrote:
> dhclient seems to be broken, it's giving me the all zeroes broadcast
> address instead of all ones:
>
> inet 192.168.91.35 netmask 0xfff0 broadcast 192.168.91.32
>
> (should be broadcast 192.168.91.47)
ok, ignore this, it seems to be working after another bui
On Wed, Jul 26, 2000 at 11:12:34PM -0400, Alexander N. Kabaev wrote:
> There was a patch floating around which fixed these mouse problems for me.
>
The patch solves the problem here too. Perhaps it could be added to the other
FreeBSD patches in the XFree86-4 port.
Benedikt Schmidt
To Unsubscri
Freshly cvsupped current.
Sendmail 8.11.0
When invoking sendmail or newaliases I get this message:
/etc/pwd.db: Invalid argument
Sendmail can't read /etc/pwd.db, and therefore cannot deliver any local
mail.
Howtofixitplease?
Leif
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
I am having problems with "tail -f" hanging the machine. I don't know if this
change is related, but I suspect that it might be.
I commonly do a "tail -f" of my log file while doing a buildworld. As soon as I
interrupted the tail, the machine hung. I then tried to figure out what was
causing t
On Mon, 24 Jul 2000, Jeroen C. van Gelderen wrote:
> > > What I meant with that point is that the user may get, say an extra few
> > > hundred bits out of it with no new entropy before the scheduled reseed
> > > task kicks in.
> >
> > How does he know which bits are which? His analysis task just
Hi All
Has anyone had any difficulty loading release 4.1 ?
I have a Tyan Thunder Main board with 128 MB ram
When I try and install it bypasses the kernel configuration and takes me
straight to the /stand/sysinstall menu. There is also no keyboard support,
therefore I am unable to complete an
Brian Fundakowski Feldman wrote:
>
> On Mon, 24 Jul 2000, Jeroen C. van Gelderen wrote:
>
> > > > What I meant with that point is that the user may get, say an extra few
> > > > hundred bits out of it with no new entropy before the scheduled reseed
> > > > task kicks in.
> > >
> > > How does he
On Sunday, July 30, 2000, Leif Neland wrote:
> Freshly cvsupped current.
>
> Sendmail 8.11.0
>
> When invoking sendmail or newaliases I get this message:
> /etc/pwd.db: Invalid argument
>
> Sendmail can't read /etc/pwd.db, and therefore cannot deliver any local
> mail.
>
> Howtofixitplease?
I've sent before that current.jp.FreeBSD.org provides 4.0-RELEASE
distribution with international CVS repository (at that time).
Now we are in the post 4.1-RELEASE age. It should be changed.
***
If you are NOT an US resident, and try to use FreeBSD 4.1-RELEASE
which was built with 'RSA_RESIDEN
22 matches
Mail list logo
