Re: /dev/null panic still alive
From: Poul-Henning Kamp (phk_at_phk.freebsd.dk)
Date: 05/24/03
- Previous message: Georg-W. Koltermann: "RE: [acpi-jp 2255] ACPI dump for Compaq Evo N800w [LONG]"
- In reply to: Daniel C. Sobral: "Re: /dev/null panic still alive"
- Next in thread: Robert Watson: "Re: /dev/null panic still alive"
- Reply: Robert Watson: "Re: /dev/null panic still alive"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: "Daniel C. Sobral" <dcs@tcoip.com.br> Date: Sat, 24 May 2003 00:27:48 +0200
In message <3ECE8894.2000508@tcoip.com.br>, "Daniel C. Sobral" writes:
>Poul-Henning Kamp wrote:
>>
>> Somewhere, probably under /compat/linux/dev you have some device nodes
>> on a UFS filesystem. You shouldn't need those (I think ?) and they
>> are likely the cause of this.
>
>True enough. As for needing it, tell that to linux_base. I'm an innocent
>bystander.
>
>> Kirk's on vacation and I havn't heard back from rwatson what he think
>> we should do.
>
>He did mention he thought trustedbsd had a patch for this.
Yes, unfortunately, that patch which is also in -current does not work.
It works for VFIFO's but not for VCHR
-- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Georg-W. Koltermann: "RE: [acpi-jp 2255] ACPI dump for Compaq Evo N800w [LONG]"
- In reply to: Daniel C. Sobral: "Re: /dev/null panic still alive"
- Next in thread: Robert Watson: "Re: /dev/null panic still alive"
- Reply: Robert Watson: "Re: /dev/null panic still alive"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|