On Saturday 22 April 2006 09:17, S Glasoe wrote:

Are you sure that the last login session you used wasn't calling /dev/hdc1 to be mounted?

Thanks for responding, Stan. No, I can't say I'm "sure". I didn't knowingly have hdc1 mounted when I logged out and rebooted. Are you suggesting that a running application, saved in that session, could have mounted it? Or are you saying that a saved session, itself (i.e. which preserves the 'environment',) can behave like this? Carl

On Saturday 22 April 2006 9:17 am, Carl Hartung wrote:

On Saturday 22 April 2006 09:17, S Glasoe wrote:

...

Are you sure that the last login session you used wasn't calling /dev/hdc1 to be mounted?

Thanks for responding, Stan.

No, I can't say I'm "sure". I didn't knowingly have hdc1 mounted when I logged out and rebooted. Are you suggesting that a running application, saved in that session, could have mounted it? Or are you saying that a saved session, itself (i.e. which preserves the 'environment',) can behave like this?

Carl

Yes to both. An application could have mounted hdc1, you quit that app and that mount point is preserved when you log out; it is part of the environment in its current state - mounted. KDE Control Center's Save Session settings; I use "manual save" versus "save the session as is every time you log out". I had the same issue once with noauto and the partition was being auto-mounted by the session as it had been saved. It is another variation on the Auto-Start idea. I get gkrellm and gaim set the way I want them to appear every time I login. I make sure nothing else is going on that I don't want and then I do a manual KDE save session. Every time I login, gaim and gkrellm appear where I left/want them on my desktop. Stan

On Saturday 22 April 2006 11:54, Carl Hartung wrote:

Thanks Carlos & Stan, for the background and ideas. I'm off to investigate now. I'll report back...

OK, I've narrowed the problem down to Gnome mounting the filesystem when I log in. :-/ Here's what I did: a) Ctl+Alt+F1 to console b) logged in as root c) umount /dev/hdc1 d) exit (returned to login prompt) e) Ctl+Alt+F7 (returned to desktop) f) Desktop>Logout>checked 'Save current setup' g) checked 'Restart the computer' After rebooting: h) at the gdm greeter, Ctl+Alt+F1 to console i) logged in as root j) 'mount' shows /dev/hdc1 is *not* mounted k) exit and Ctl+Alt+F7 (return to greeter) l) logged into desktop as user m) Ctl+Alt+F1 to console n) logged in as root o) 'mount' shows /dev/hdc1 *is* mounted. I didn't have any user-level applications open, that I know of anyway... just the usual taskbar/panel(?) stuff: volume control, mixer, KOrganizer Reminder Daemon, SUSEWatcher, KGpg, KSensors, Ethernet connection, Display information, clock/date Any ideas, folks? Thanks! Carl

On Saturday 22 April 2006 13:01, S Glasoe wrote:

You've narrowed it down to the user login mounting hdc1. hdc1 is a partition used for backups?

Yes

What do you use for backups?

It's a simple home-brew script that I run manually at the end of the day and/or before shutting the system down. I logout of my desktop, switch to a console, log in as root, drop to run level 3 and run the script. It mounts hdb8 and hdc1, creates/updates my backups (methods are filesystem dependent) and umounts the filesystems when done. I've verified that it actually does umount them correctly upon completion of the script.

Is it auto-started at user login?

I wish ;-) When I have a bit more time later this weekend I'll 'hit the books' and do some Google research on it. regards, Carl

On Saturday 22 April 2006 13:23, Leendert Meyer wrote:

I am a Gnome agnost, but perhaps the gnome-volume-manager is the place to look? Where ever that might be... ;P

LOL! Thanks Leendert... I'll investigate. Carl

On Saturday 22 April 2006 14:01, Carl Hartung wrote:

Addendum:

I think it's worth pointing out again that hdb8 (Reiserfs) behaves correctly and that the errant filesystem on hdc1 is FAT32.

I ran gnome-volume-properties and discovered that's the correct dialogue for configuring gnome-volume-manager, i.e. configuring defaults for removable media... but I saw nothing there regarding hard drives.

Addendum 2: Running gnome-volume-properties again and unchecking all the automount and autorun options there stopped the unwanted behavior. When I have time to experiment, I'll try to narrow it down further. In the interim, hdc1 is no longer mounting when I log into GNOME. Carl

On Monday 24 April 2006 20:26, Joseph Loo wrote:

...

Following are the relevant entries in /etc/fstab:

/dev/hdb12 /mnt/hdb-bak reiserfs noauto,acl,user_xattr 1 2

/dev/hdc1 /mnt/hdc-bak vfat noauto,users,gid=users,umask=0002,utf8=true 0 0

(Note the 'noauto' declaration in each entry.)

Upon booting, hdb12 has not been mounted automatically, which is the desired behavior. However, hdc1 *is* mounting automatically.

Try changing your 1 2 at the end of the fstab file to 0 0.

Hi Joseph, The last line actually does end in 0 0 It turns out gnome-volume-manager was automounting hdc1 each time I logged into GNOME. Someone pointed me to the program 'gnome-volume-properties' (it normally resides under Desktop>Preferences in GNOME) and unchecked all the automounting functions listed there. That solved my problem, but when I have time I'm going to try narrowing it down to the specific function. Thank you very much for your response! regards, Carl

On Mon, 24 Apr 2006 17:26:36 -0700 Joseph Loo wrote:

Try changing your 1 2 at the end of the fstab file to 0 0.

These two numbers have nothing to do with mounting. The first number is used by the dump utility when doing backups- a zero means ignore. The second number is the order for checking file systems by fsck- a zero means don't check. Charles -- die_if_kernel("Penguin instruction from Penguin mode??!?!", regs); linux-2.2.16/arch/sparc/kernel/traps.c