[solved (I think)]Re: Why is my /etc/fstab being ignored.

[Joe(theWordy)Philbrook]

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

It would appear that on Apr 9, Joe(theWordy)Philbrook did say:
> It would appear that on Apr 8, Matthew Flaschen did say:
> > Joe(theWordy)Philbrook wrote:
> > >> noauto should do it.  Please attach your entire /etc/fstab file.
> > > 
> > > OK see attached...
> > Thanks.  Now which are being automounted?  I noted that you have
> > conflicting entries for several removable media entries, which I don't
> > believe is allowed.  For comparison, my fstab is attached to this
> > message.  I have only one cd entry, but I can still burn and read both
> > cds and dvds thanks to udev.  I don't really know how floppies work on
> 
> Well the multiple entries for removable media may not be "allowed" but
> they work. I've used my own NON-standard mountpoints for every
> distribution I've ever put on my pc. I don't eliminate the mountpoints
> the default fstab(s) used because I don't know if some software may
> depend on them implicitly. I suppose that I could replace mine with
> symlinks to the mountpoints the installer likes... If they stop working
> I may bother... 
> But I'd still need 2 cd entries as my dvd-rom is NOT the same physical
> device as my cd-rw...

I'm still unclear on it's allowability, But I decided that in this world
where it's assumed that it's desirable for all filesystems to be mounted
by some daemon like process. Something might choke on multiple active
listings for the same /dev/[file] Thus I commented out the /media/
entries for my cd drives.


> As far as which ones are being automounted...
> 
> ALL of them! 

Turns out that the culprit was that durned
/etc/ivman/IvmConfigActions.xml

It took me a while to wade through all the unfamiliar XML to see that the
only real difference between the /etc/ivman/IvmConfigActions.xml and the
{thank gosh it was there} IvmConfigActions.xml.dpkg-old was:

 <!-- perform these rules on devices already attached when Ivman starts -->
    <ivm:Option name="checkOnInit" value="true" />

was new...

Also the last three lines of:

    <!-- try to mount any mountable volume at all -->
    <!--ivm:Match name="ivm.mountable" value="true"-->
        <!--ivm:Option name="mount" value="true" /-->
    <!--/ivm:Match-->

had been un-commented.

So I re-commented (replacing the "<" with "<!--" and ">" with "-->" is
the way to comment out a piece of XML code right?) the three lines.
ZZ<ctl>+<alt>+<delete>
And when it rebooted, the problem went away...

> Speaking of which: Please see my other list message posted 4-2-07
> Subject: Warning: device /dev/hda1 is already handled by /etc/fstab
> Message-ID: <Pine.LNX.4.64.0704021214040.6493 at localhost.localdomain>
> It might give a clue...

it did, it did give me a clue. If it weren't for that error in the
start-up text, I'd never have known to look at ivman... 

   #############################################################
   ##_if_you'd_prefer_an_clearsigned_".asc"_text_file_of_this_##
   ##message_as_an_mime_encoded_attachment,just_ask_me_while__##
   ##it's_STILL_IN_my_outbox_folder_._._._=+=+=+=+=+=+=+=+;-)_##
   #gpg sig for: Joe (theWordy) Philbrook DSA key ID 0x6C2163DE#
   # You can find my public gpg key at http://pgpkeys.mit.edu/ #
   #############################################################
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFGH7xORZ/61mwhY94RAn1GAKCEnGtyO0yt9ZDbws/H12KUGdX1JgCgzypQ
e14BbqJXx/K+Zk45f3ECqrE=
=JPf6
-----END PGP SIGNATURE-----
-- 
|   ---   ___
|   <0>   <->	   Joe (theWordy) Philbrook
|	^		J(tWdy)P
|    ~\___/~	     <<jtwdyp at ttlc.net>>