 |
|
 |
|
01-23-04 09:45 PM
ppaatt@aol.com (Pat LaVarre) wrote in message news:<2695edf1.0311280955.6824e608@posting.google.co
m>...quote:
> Can anyone say how I should have divined that e2fsck runs when I type
> fsck?
Probably better asked in comp.unix.admin (added to posting, but alas,
Google won't let me set Followup-To or relevant LINUX newsgroup(s)
(though ext2 and ext3 filesystems are also available on non-LINUX
platforms).
Anyway, many UNIX (and LINUX, etc.) implementations implement fsck as a
front end which just automagically calls the appropriate filesystem type
specific lower level fsck program (e.g. e2fsck, fsck.e3fs, fsck.ufs,
fsck.vxfs, ... whatever).
The best way to "divine" that information is examine the filesystem
type, and examine the fsck executable and/or source, to determine what
filesystem types it may automatically recognize, and how it does so and
deals with them. The fsck man page(s) may also have relevant
information and/or pointers.
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
01-23-04 09:45 PM
ppaatt@aol.com (Pat LaVarre) wrote in message news:<2695edf1.0311280955.6824e608@posting.google.co
m>...quote:
> Can anyone say how I should have divined that e2fsck runs when I type
> fsck?
Probably better asked in comp.unix.admin (added to posting, but alas,
Google won't let me set Followup-To or relevant LINUX newsgroup(s)
(though ext2 and ext3 filesystems are also available on non-LINUX
platforms).
Anyway, many UNIX (and LINUX, etc.) implementations implement fsck as a
front end which just automagically calls the appropriate filesystem type
specific lower level fsck program (e.g. e2fsck, fsck.e3fs, fsck.ufs,
fsck.vxfs, ... whatever).
The best way to "divine" that information is examine the filesystem
type, and examine the fsck executable and/or source, to determine what
filesystem types it may automatically recognize, and how it does so and
deals with them. The fsck man page(s) may also have relevant
information and/or pointers.
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
01-23-04 09:45 PM
Michael Paoli wrote:quote:
> Anyway, many UNIX (and LINUX, etc.) implementations implement fsck as a
> front end which just automagically calls the appropriate filesystem type
> specific lower level fsck program (e.g. e2fsck, fsck.e3fs, fsck.ufs,
> fsck.vxfs, ... whatever).
>
From man fsck:
In actuality, fsck is simply a front-end for the various file
system
checkers (fsck.fstype) available under Linux. The file
system-specific
checker is searched for in /sbin first, then in /etc/fs and
/etc, and
finally in the directories listed in the PATH environment
variable.
Please see the file system-specific checker manual pages for
further
details.
quote:
> The best way to "divine" that information is examine the filesystem
> type, and examine the fsck executable and/or source, to determine what
> filesystem types it may automatically recognize, and how it does so and
> deals with them. The fsck man page(s) may also have relevant
> information and/or pointers.
--
+ Regards, +
+ Nick +
+ +
+ My email address is real +
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
01-23-04 09:45 PM
Michael Paoli wrote:quote:
> Anyway, many UNIX (and LINUX, etc.) implementations implement fsck as a
> front end which just automagically calls the appropriate filesystem type
> specific lower level fsck program (e.g. e2fsck, fsck.e3fs, fsck.ufs,
> fsck.vxfs, ... whatever).
>
From man fsck:
In actuality, fsck is simply a front-end for the various file
system
checkers (fsck.fstype) available under Linux. The file
system-specific
checker is searched for in /sbin first, then in /etc/fs and
/etc, and
finally in the directories listed in the PATH environment
variable.
Please see the file system-specific checker manual pages for
further
details.
quote:
> The best way to "divine" that information is examine the filesystem
> type, and examine the fsck executable and/or source, to determine what
> filesystem types it may automatically recognize, and how it does so and
> deals with them. The fsck man page(s) may also have relevant
> information and/or pointers.
--
+ Regards, +
+ Nick +
+ +
+ My email address is real +
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
01-23-04 09:55 PM
ppaatt@aol.com (Pat LaVarre) wrote in message news:<2695edf1.0311280955.6824e608@posting.google.co
m>...quote:
> Can anyone say how I should have divined that e2fsck runs when I type
> fsck?
Probably better asked in comp.unix.admin (added to posting, but alas,
Google won't let me set Followup-To or relevant LINUX newsgroup(s)
(though ext2 and ext3 filesystems are also available on non-LINUX
platforms).
Anyway, many UNIX (and LINUX, etc.) implementations implement fsck as a
front end which just automagically calls the appropriate filesystem type
specific lower level fsck program (e.g. e2fsck, fsck.e3fs, fsck.ufs,
fsck.vxfs, ... whatever).
The best way to "divine" that information is examine the filesystem
type, and examine the fsck executable and/or source, to determine what
filesystem types it may automatically recognize, and how it does so and
deals with them. The fsck man page(s) may also have relevant
information and/or pointers.
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
01-23-04 09:55 PM
Michael Paoli wrote:quote:
> Anyway, many UNIX (and LINUX, etc.) implementations implement fsck as a
> front end which just automagically calls the appropriate filesystem type
> specific lower level fsck program (e.g. e2fsck, fsck.e3fs, fsck.ufs,
> fsck.vxfs, ... whatever).
>
From man fsck:
In actuality, fsck is simply a front-end for the various file
system
checkers (fsck.fstype) available under Linux. The file
system-specific
checker is searched for in /sbin first, then in /etc/fs and
/etc, and
finally in the directories listed in the PATH environment
variable.
Please see the file system-specific checker manual pages for
further
details.
quote:
> The best way to "divine" that information is examine the filesystem
> type, and examine the fsck executable and/or source, to determine what
> filesystem types it may automatically recognize, and how it does so and
> deals with them. The fsck man page(s) may also have relevant
> information and/or pointers.
--
+ Regards, +
+ Nick +
+ +
+ My email address is real +
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
01-23-04 10:10 PM
ppaatt@aol.com (Pat LaVarre) wrote in message news:<2695edf1.0311280955.6824e608@posting.google.co
m>...quote:
> Can anyone say how I should have divined that e2fsck runs when I type
> fsck?
Probably better asked in comp.unix.admin (added to posting, but alas,
Google won't let me set Followup-To or relevant LINUX newsgroup(s)
(though ext2 and ext3 filesystems are also available on non-LINUX
platforms).
Anyway, many UNIX (and LINUX, etc.) implementations implement fsck as a
front end which just automagically calls the appropriate filesystem type
specific lower level fsck program (e.g. e2fsck, fsck.e3fs, fsck.ufs,
fsck.vxfs, ... whatever).
The best way to "divine" that information is examine the filesystem
type, and examine the fsck executable and/or source, to determine what
filesystem types it may automatically recognize, and how it does so and
deals with them. The fsck man page(s) may also have relevant
information and/or pointers.
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
01-23-04 10:10 PM
Michael Paoli wrote:quote:
> Anyway, many UNIX (and LINUX, etc.) implementations implement fsck as a
> front end which just automagically calls the appropriate filesystem type
> specific lower level fsck program (e.g. e2fsck, fsck.e3fs, fsck.ufs,
> fsck.vxfs, ... whatever).
>
From man fsck:
In actuality, fsck is simply a front-end for the various file
system
checkers (fsck.fstype) available under Linux. The file
system-specific
checker is searched for in /sbin first, then in /etc/fs and
/etc, and
finally in the directories listed in the PATH environment
variable.
Please see the file system-specific checker manual pages for
further
details.
quote:
> The best way to "divine" that information is examine the filesystem
> type, and examine the fsck executable and/or source, to determine what
> filesystem types it may automatically recognize, and how it does so and
> deals with them. The fsck man page(s) may also have relevant
> information and/or pointers.
--
+ Regards, +
+ Nick +
+ +
+ My email address is real +
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
|
|
Sponsored Links |
 |
 |
|
|
 |
All times are GMT. The time now is 01:21 PM. |
 |
|
|
 |
|
 |
|
|
 |
|
Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
|
|
|
|
Medical and Health forum | Computer Games Reviews | Graphics design forum
|
 |
|
 |
|
