oot a netbsd floppy to recover data from other
partitions (which didn't have errors :)
--
Manuel Bouyer, LIP6, Universite Paris VI. manuel.bou...@lip6.fr
--
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
oot a netbsd floppy to recover data from other
partitions (which didn't have errors :)
--
Manuel Bouyer, LIP6, Universite Paris VI. [EMAIL PROTECTED]
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
p, and it's not
necesserely a good thing to let a server operate without all it's filesystems.
On my shell server, if /var gets corrupted, I'm sure I prefer to get a panic
instead of letting it run without accounting.
--
Manuel Bouyer, LIP6, Universite Paris VI. manuel.
> Presumably the console user is the one fiddling with the external
> media.
>
What I would do here is give root privileges to the user who mounted the
filesystem, for this filesystem.
As in 4.4BSD non-root users can mount media if they have access to the block
device, I think thi
, I don't think changing the panic() to
return(appropriate_error_code) is the rigth thing to do, in some case
you want to panic if a filesystem gets corrupted. This could probably
be switched on/off for root/non-root mounts.
Also I think there are some cases where it's too late to recov
p, and it's not
necesserely a good thing to let a server operate without all it's filesystems.
On my shell server, if /var gets corrupted, I'm sure I prefer to get a panic
instead of letting it run without accounting.
--
Manuel Bouyer, LIP6, Universite Paris VI. [EM
, they need to have access to the block devices.
For "loopback" mounts (null, union, umap, ...), we have to be more carefull
about restrictions. Maybe NFS is an issue too ...
--
Manuel Bouyer, LIP6, Universite Paris VI. manuel.bou...@lip6.fr
--
To Unsubscribe: send mail
> Presumably the console user is the one fiddling with the external
> media.
>
What I would do here is give root privileges to the user who mounted the
filesystem, for this filesystem.
As in 4.4BSD non-root users can mount media if they have access to the block
device, I think thi
, I don't think changing the panic() to
return(appropriate_error_code) is the rigth thing to do, in some case
you want to panic if a filesystem gets corrupted. This could probably
be switched on/off for root/non-root mounts.
Also I think there are some cases where it's too late to recov
thing, they need to have access to the block devices.
For "loopback" mounts (null, union, umap, ...), we have to be more carefull
about restrictions. Maybe NFS is an issue too ...
--
Manuel Bouyer, LIP6, Universite Paris VI. [EMAIL PROTECTED]
--
To Unsubscribe: send mail to [EMAIL
10 matches
Mail list logo
