Bug 138629 - On update the symlink /home is replaced with an empty directory
On update the symlink /home is replaced with an empty directory
Product: Fedora
Classification: Fedora
Component: filesystem (Show other bugs)
athlon Linux
medium Severity low
: ---
: ---
Assigned To: Bill Nottingham
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-11-10 07:20 EST by Michael Ritzert
Modified: 2014-03-16 22:50 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-10 12:31:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Ritzert 2004-11-10 07:20:11 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)

Description of problem:
We have /home mounted via the automounter to /net/home. /home is a symlink there for convenience.
During the updates FC1=>FC2 and FC2=>FC3 this symlink was removed and replaced with an empty directory.
I had to rmdir /home; ln -s /net/home /home afterwards to get back to the old state.

I'd suggest to leave /home alone as a symlink in case it exists.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install FC2
2. Move your /home directory somewhere else and make /home a symlink there.
3. Update to FC3 using the CD ISOs.


Actual Results:  /home was no longer a symlink to /net/home, but an empty directory.

Expected Results:  I'd expect /home to still point to /net/home after the update.

Additional info:
Comment 1 Jeremy Katz 2004-11-10 09:40:47 EST
/home is included in the filesystem package, so when that gets
upgraded, /home gets restored.
Comment 2 Bill Nottingham 2004-11-10 12:31:58 EST
This can't really be done as a special case for /home.

You might want to add "%_netsharedpath /home" to /etc/rpm/macros. 

Note You need to log in before you can comment on or make changes to this bug.