Date: Fri, 7 Feb 2003 17:48:00 -0600 From: Juli Mallett <jmallett@FreeBSD.org> To: "Andrey A. Chernov" <ache@nagual.pp.ru> Cc: phk@phk.freebsd.dk, Bruce Evans <bde@zeta.org.au>, current@freebsd.org Subject: Re: Wrong date for DEVFS entries Message-ID: <20030207174800.A21568@FreeBSD.org> In-Reply-To: <20030207232556.GA36704@nagual.pp.ru>; from ache@nagual.pp.ru on Sat, Feb 08, 2003 at 02:25:56AM %2B0300 References: <20030207231315.GA29117@nagual.pp.ru> <13494.1044659784@critter.freebsd.dk> <20030207232556.GA36704@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
* De: "Andrey A. Chernov" <ache@nagual.pp.ru> [ Data: 2003-02-07 ] [ Subjecte: Re: Wrong date for DEVFS entries ] > On Sat, Feb 08, 2003 at 00:16:24 +0100, phk@phk.freebsd.dk wrote: > > > > Can we stop considering workarounds, and instead work on solving > > the problem please ? > > I see no solving way until kernel will understand fully and can handle > timezone database format. It means timezone code should be integrated > into kernel. And for which reason? Only to heal DEVFS timestamps? Mount > workaround looks more light-weighted. The contents of /dev/ really don't need audited, in a devfs world, like they might be in a non-devfs one. For example hiding rootkits in /dev/wd0./foo or /dev/somedev0/ or whatever isn't really quite the issue it may have ever been. People who read too much into the contents of a devfs /dev should not be too surprised if the results are dodgy. What with cloning and all. -- Juli Mallett <jmallett@FreeBSD.org> AIM: BSDFlata -- IRC: juli on EFnet OpenDarwin, Mono, FreeBSD Developer ircd-hybrid Developer, EFnet addict FreeBSD on MIPS-Anything on FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030207174800.A21568>