Bug 140334 - FC3 installation overwrites .bashrc in user home
Summary: FC3 installation overwrites .bashrc in user home
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: 3
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-22 13:22 UTC by Håvard Bjåstad
Modified: 2007-11-30 22:10 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2004-11-22 17:14:36 UTC


Attachments (Terms of Use)

Description Håvard Bjåstad 2004-11-22 13:22:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5)
Gecko/20041110 Firefox/1.0

Description of problem:
I had a system with FC2, with /home on a separate partition. Instead
of upgrading FC2 to FC3, I wanted to keep FC2 as a fallback option, so
I installed FC3 on a new partition, keeping /home and the old FC2
partition.

After installation, I realized that FC3 had overwritten the customized
.bashrc file in my user's home directory.

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


How reproducible:
Didn't try


Additional info:

Comment 1 Bill Nottingham 2004-11-22 16:10:13 UTC
Nothing owns /home/*, so I don't see how this could happen. Is this
reproducible?

What did it overwrite it with?

Comment 2 Håvard Bjåstad 2004-11-22 16:15:46 UTC
Not sure if it's reproducible (I haven't had time to go through a full
new install...).

My custom .bashrc had been overwritten with the default .bashrc that
you get when creating new users. Unfortunately, I didn't realize this
until I booted up after everything had been installed, so I don't know
at what point during the installation it happened.

I did ask FC3 to create myself as a user, maybe that's when it happened?

Comment 3 Bill Nottingham 2004-11-22 17:14:26 UTC
Yeah, I think that's expected. If you select to add a user, it runs
useradd, which copies the skeleton files.


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