lkml.org 
[lkml]   [1999]   [Nov]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: `filetype' ext2 feature causes dump to SEGV
Date
Followup to:  <199911180422.XAA11970@tsx-prime.MIT.EDU>
By author: "Theodore Y. Ts'o" <tytso@MIT.EDU>
In newsgroup: linux.dev.kernel
>
> Actually, it was Stephen Tweedie who originally did the dump port, and
> the reason for why it was done that way was precisely because it was a
> port of the BSD dump program, which originally only supported exactly
> one filesystem -- the BSD UFS. Since the BSD UFS didn't have an ext2
> lbirary functions, it accessed the direct, indirect blocks directly;
> Stephen just simply used the ext2 library to read the inode table, but
> didn't otherwise try to make major changes to the dump program.
>
> If you want to make dump use more of the ext2 library's features, that's
> probably a good thing. I would very strongly encourage you to keep the
> on-tape format compatible with the BSD dump program, however. Being
> able to exchange dump tape between BSD and Linux can be a very handy
> feature from time to time.
>

It still seems that the right thing for this would be to go through
the filesystem layer, so a mounted filesystem can be accessed safely?

-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:55    [W:0.061 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site