hi!

in fstab there are 2 numbers at the end of every line:
i have seen
00
11
12
what do they mean? something with checking the partitions?

cheers,
christine

On Thu, 8 Jun 2006 20:18:38 +0300, christine wrote:
> hi!
>
> in fstab there are 2 numbers at the end of every line:

Have you tried the command

man fstab

On Thu, 08 Jun 2006 21:09:11 -0400, christine wrote:
> christine wrote:
> hmmm...
>
> man fstab is NOT very easy to undestand.

Dictionaries are hard to understand. Seems you have to keep looking up
more and more words to understand the first word. :-)

> the fifth field tells us to dump or not to dump.
> now, i have no idea what that "dump" means...

Go back an look at that paragraph. The hint was
   The fifth field, (fs_freq),  is  used  for  these  filesystems  by  the
       dump(8)  command

now you have to do a 
    man 8 dump

> thanks for answering my question!

Since you seem to be looking around trying to understand what is what,
this might help.

http://rute.2038bug.com/index.html.gz

If you have not done it yet, do a 
man man

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bit Twister wrote:
> On Thu, 08 Jun 2006 21:09:11 -0400, christine wrote:
>> christine wrote:
>> hmmm...
>>
>> man fstab is NOT very easy to undestand.
> 
> Dictionaries are hard to understand. Seems you have to keep looking up
> more and more words to understand the first word. :-)
> 
>> the fifth field tells us to dump or not to dump.
>> now, i have no idea what that "dump" means...
> 
> Go back an look at that paragraph. The hint was
>    The fifth field, (fs_freq),  is  used  for  these  filesystems  by  the
>        dump(8)  command
> 
> now you have to do a 
>     man 8 dump

It might be worth noting that, as Linus Torvalds doesn't think that
dump(8) is a good idea in Linux, there /might not be/ a "man  8 dump"
manpage for it.

LT> From:	 Linus Torvalds
LT> To:	 Neil Conway
LT> Subject: Re: [PATCH] SMP race in ext2 - metadata corruption.
LT> Date:	 Fri, 27 Apr 2001 09:59:46 -0700 (PDT)
LT> ...
LT> So anybody who depends on "dump" getting backups right is already
playing
LT> Russian roulette with their backups.  It's not at all guaranteed to
get the
LT> right results - you may end up having stale data in the buffer cache
that
LT> ends up being "backed up".
LT>
LT> Dump was a stupid program in the first place. Leave it behind.



- --

Lew Pitcher, IT Specialist, Corporate Technology Solutions,
Enterprise Technology Solutions, TD Bank Financial Group

(Opinions expressed here are my own, not my employer's)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEiHURagVFX4UWr64RAofdAKDA2mVb0ligQ7sXqAit8NoYEy/WUACfYzfO
jEOrdEu8Pjp53hTUzfKKO3k=
=ldwF
-----END PGP SIGNATURE-----

On Thu, 08 Jun 2006 15:05:53 -0400, Lew Pitcher wrote:
>
> It might be worth noting that, as Linus Torvalds doesn't think that
> dump(8) is a good idea in Linux, there /might not be/ a "man  8 dump"
> manpage for it.

True, can be distribution specific. MandrivaLinux has it.


>
> LT> From:	 Linus Torvalds
> LT> To:	 Neil Conway
> LT> Subject: Re: [PATCH] SMP race in ext2 - metadata corruption.
> LT> Date:	 Fri, 27 Apr 2001 09:59:46 -0700 (PDT)
> LT> ...
> LT> So anybody who depends on "dump" getting backups right is already
> playing
> LT> Russian roulette with their backups.  It's not at all guaranteed to
> get the
> LT> right results - you may end up having stale data in the buffer cache
> that
> LT> ends up being "backed up".
> LT>
> LT> Dump was a stupid program in the first place. Leave it behind.

I can relate to obsolete. I posted a script to dump network info to help
troubleshoot a poster's problem. Someone posted that mii-tool was obsolete,
proof is in man page, and to use eth-tool. eth-tool would not work on my
Linksys nics. 

On Thu, 08 Jun 2006 23:19:57 -0400, christine <christine@hotmail.com> wrote:

>so, i changed my fstab last sections to
>
>/      11
>/home  12

Put a space character between the digits, they're two whitespace 
delimited values.  
....
>maybe i can delete these???

Not until you know what put them there, you might break something.

Grant.
-- 
Memory fault -- brain fried

christine <christine@hotmail.com> writes:

>Bit Twister wrote:

>> On Thu, 08 Jun 2006 15:05:53 -0400, Lew Pitcher wrote:
>>>
>>> It might be worth noting that, as Linus Torvalds doesn't think that
>>> dump(8) is a good idea in Linux, there /might not be/ a "man  8 dump"
>>> manpage for it.
>> 
>> True, can be distribution specific. MandrivaLinux has it.
>> 
>> 
>>>
>>> LT> From:     Linus Torvalds
>>> LT> To:       Neil Conway
>>> LT> Subject: Re: [PATCH] SMP race in ext2 - metadata corruption.
>>> LT> Date:     Fri, 27 Apr 2001 09:59:46 -0700 (PDT)
>>> LT> ...
>>> LT> So anybody who depends on "dump" getting backups right is already
>>> playing
>>> LT> Russian roulette with their backups.  It's not at all guaranteed to
>>> get the
>>> LT> right results - you may end up having stale data in the buffer cache
>>> that
>>> LT> ends up being "backed up".
>>> LT>
>>> LT> Dump was a stupid program in the first place. Leave it behind.
>> 
>> I can relate to obsolete. I posted a script to dump network info to help
>> troubleshoot a poster's problem. Someone posted that mii-tool was
>> obsolete, proof is in man page, and to use eth-tool. eth-tool would not
>> work on my Linksys nics.
>hi again!

>no, here is no "man 8 dump" 
>i am running kanotix from my HD and i am very positive about its working and
>capability!

>so, i changed my fstab last sections to

>/      11
>/home  12

These make no sense. What are they supposed to do?


>seems to work fine during booting.

>there are a few lines in the fstab which i don't understand

>like these:

>/tmp/app/1/image /tmp/app/1 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
>/tmp/app/2/image /tmp/app/2 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
>/tmp/app/3/image /tmp/app/3 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
>/tmp/app/4/image /tmp/app/4 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
>/tmp/app/5/image /tmp/app/5 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
>/tmp/app/6/image /tmp/app/6 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
>/tmp/app/7/image /tmp/app/7 cramfs,iso9660 user,noauto,ro,loop,exec 0 0


>the other lines are normal /dev/ 
>and such...

>maybe i can delete these???

I have no idea at all what they are supposed to do. They mount an entry in
a directory onto the directory itself. It looks weird. Where did they come
from?


>cheers,
>christine

christine wrote:
> hi!
>
> in fstab there are 2 numbers at the end of every line:
> i have seen
> 00
> 11
> 12
> what do they mean? something with checking the partitions?
>
> cheers,
> christine

http://www.tuxfiles.org/linuxhelp/fstab.html
http://www.humbug.org.au/talks/fstab/fstab_structure.html
http://linuxhelp.blogspot.com/2006/02/etcfstab-demystified.html

Sometimes its easier to find an answer from google if `man command`
does not help.

On Thursday 08 June 2006 23:42, Unruh stood up and spoke the following
words to the masses in /comp.os.linux.misc...:/

> christine <christine@hotmail.com> writes:
> 
>> there are a few lines in the fstab which i don't understand
> 
>> like these:
> 
>> /tmp/app/1/image /tmp/app/1 cramfs,iso9660 user,noauto,ro,loop,exec 0
>> 0 
>> /tmp/app/2/image /tmp/app/2 cramfs,iso9660 user,noauto,ro,loop,exec 
>> 0 0 
>> /tmp/app/3/image /tmp/app/3 cramfs,iso9660 user,noauto,ro,loop,exec 0
>> 0  
>> /tmp/app/4/image /tmp/app/4 cramfs,iso9660 user,noauto,ro,loop,exec 0
>> 0 /tmp/app/5/image /tmp/app/5 cramfs,iso9660 user,noauto,ro,loop,exec
>> 0 0 
>>/tmp/app/6/image /tmp/app/6 cramfs,iso9660 user,noauto,ro,loop,exec 0
>> 0
>> /tmp/app/7/image /tmp/app/7 cramfs,iso9660 user,noauto,ro,loop,exec 
>> 0 0

The /cramfs/ is a compressed read-only filesystem, mainly used in
embedded systems.  Here's the /Wikipedia/ explanation on it...:

        http://en.wikipedia.org/wiki/Cramfs

<blockquote>
        "The compressed ROM filesystem (or cramfs) is a Free (GPL'ed) read-only
        Linux file system designed for simplicity and space-efficiency. It is
        mainly used in embedded systems and small-footprint systems.

        Unlike a compressed image of a conventional filesystem, a cramfs image
        does not have to be uncompressed first and can be used as-is,
        compressed. For this reason, some Linux distributions also appear to
        use cramfs as a file system for initial ramdisks (initrd) (recent
        versions of Debian in particular) and installation images (SuSE in
        particular), where there are onerous constraints on memory and image
        size."
</blockquote>

From what it appears, those lines are leftovers from an install. 
Presumably */tmp/app/$NUMBER/image* is such a filesystem and gets
mounted on */tmp/app/$NUMBER.*

Normally, according to the Filesystem Hierarchy Standard, nothing in
*/tmp* should remain there after a reboot.  

My advice here would be to run /fuser/ on these mounted filesystems -
the entries in */etc/fstab* define them as user-mountable and not
automatically mounted on boot - and if it turns out they are not
needed, remove them by doing the following...

        # Open up a commandline terminal and become root...
        su

        # Drop to single-user mode...
        shutdown now

        # Remove all that's in */tmp* ...
        cd /tmp
        rm -rf *

        # Return to normal operation - substitute 3 by 5 if the system
        # must boot to a GUI login screen...
        init 3

Hope this helps... ;-)

-- 
With kind regards,

*Aragorn*
(Registered GNU/Linux user #223157)

christine wrote:

	[---CUT---]
> there are a few lines in the fstab which i don't understand
> like these:
> 
> /tmp/app/1/image /tmp/app/1 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
> /tmp/app/2/image /tmp/app/2 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
> /tmp/app/3/image /tmp/app/3 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
	[---CUT---]

If you don't use Klik (KDE userspace installer), you can erase these 
lines safely. It's Klik which added them to your fstab.

-- 
==================
Remi Villatel
maxilys_@_tele2.fr
==================

Bit Twister wrote:

> On Thu, 8 Jun 2006 20:18:38 +0300, christine wrote:
>> hi!
>>
>> in fstab there are 2 numbers at the end of every line:
> 
> Have you tried the command
> 
> man fstab

hi!

no, i haven't
will try :-)

cheers,
christine

christine wrote:

> Bit Twister wrote:
> 
>> On Thu, 8 Jun 2006 20:18:38 +0300, christine wrote:
>>> hi!
>>>
>>> in fstab there are 2 numbers at the end of every line:
>> 
>> Have you tried the command
>> 
>> man fstab
> 
> hi!
> 
> no, i haven't
> will try :-)
> 
> cheers,
> christine


hmmm...

man fstab is NOT very easy to undestand.

the fifth field tells us to dump or not to dump.
now, i have no idea what that "dump" means...

the sixth field is about checking partitions, to check or not to check, and
in what order. that's understandable :-)


thanks for answering my question!

cheers,
christine

Bit Twister wrote:

> On Thu, 08 Jun 2006 15:05:53 -0400, Lew Pitcher wrote:
>>
>> It might be worth noting that, as Linus Torvalds doesn't think that
>> dump(8) is a good idea in Linux, there /might not be/ a "man  8 dump"
>> manpage for it.
> 
> True, can be distribution specific. MandrivaLinux has it.
> 
> 
>>
>> LT> From:     Linus Torvalds
>> LT> To:       Neil Conway
>> LT> Subject: Re: [PATCH] SMP race in ext2 - metadata corruption.
>> LT> Date:     Fri, 27 Apr 2001 09:59:46 -0700 (PDT)
>> LT> ...
>> LT> So anybody who depends on "dump" getting backups right is already
>> playing
>> LT> Russian roulette with their backups.  It's not at all guaranteed to
>> get the
>> LT> right results - you may end up having stale data in the buffer cache
>> that
>> LT> ends up being "backed up".
>> LT>
>> LT> Dump was a stupid program in the first place. Leave it behind.
> 
> I can relate to obsolete. I posted a script to dump network info to help
> troubleshoot a poster's problem. Someone posted that mii-tool was
> obsolete, proof is in man page, and to use eth-tool. eth-tool would not
> work on my Linksys nics.
hi again!

no, here is no "man 8 dump" 
i am running kanotix from my HD and i am very positive about its working and
capability!

so, i changed my fstab last sections to

/      11
/home  12

seems to work fine during booting.

there are a few lines in the fstab which i don't understand

like these:

/tmp/app/1/image /tmp/app/1 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
/tmp/app/2/image /tmp/app/2 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
/tmp/app/3/image /tmp/app/3 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
/tmp/app/4/image /tmp/app/4 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
/tmp/app/5/image /tmp/app/5 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
/tmp/app/6/image /tmp/app/6 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
/tmp/app/7/image /tmp/app/7 cramfs,iso9660 user,noauto,ro,loop,exec 0 0


the other lines are normal /dev/ 
and such...

maybe i can delete these???

cheers,
christine

"Remi Villatel"
>> there are a few lines in the fstab which i don't understand
>> like these:
>>
>> /tmp/app/1/image /tmp/app/1 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
>> /tmp/app/2/image /tmp/app/2 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
>> /tmp/app/3/image /tmp/app/3 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
> [---CUT---]
>
> If you don't use Klik (KDE userspace installer), you can erase these lines 
> safely. It's Klik which added them to your fstab.
>
yes, i have used klik, so that explains it!

thanks for the explanation!

cheers,
christine

"Grant"
> On Thu, 08 Jun 2006 23:19:57 -0400, christine <christine@hotmail.com> 
> wrote:
>
>>so, i changed my fstab last sections to
>>
>>/      11
>>/home  12
>
> Put a space character between the digits, they're two whitespace
> delimited values.

oh......yes of course!
(blushing)

thanks

cheers,
christine