Re: BigDisk project: du(1) 64bit clean.
From: Julian Elischer (julian_at_elischer.org)
Date: 01/06/05
- Previous message: Brooks Davis: "Re: BigDisk project: du(1) 64bit clean."
- In reply to: M. Warner Losh: "Re: BigDisk project: du(1) 64bit clean."
- Next in thread: Peter Jeremy: "Re: BigDisk project: du(1) 64bit clean."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 05 Jan 2005 15:12:47 -0800 To: "M. Warner Losh" <imp@bsdimp.com>
M. Warner Losh wrote:
>In message: <41DB8FD3.3030101@elischer.org>
> Julian Elischer <julian@elischer.org> writes:
>: > I think that a big amount of this could be reduced by using simple
>: > arrays rather than lists which are more memory efficient...
>:
>: but that just puts the problem a bit further away.
>
>We have to do it. If you don't have a file system to store a file,
>then you cna't do this at all. When you are fscking /, you don't have
>a file system. And if you have finished, nothing is yet mounted r/w.
>
I'm suggesting two version..
one tha tuses RAM and oen that uses files..
the filesystem that the files are written to would be done first with
the RAM version..
We already do that here, though for different reasons.
>
>Warner
>
>
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Brooks Davis: "Re: BigDisk project: du(1) 64bit clean."
- In reply to: M. Warner Losh: "Re: BigDisk project: du(1) 64bit clean."
- Next in thread: Peter Jeremy: "Re: BigDisk project: du(1) 64bit clean."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]