Bug 119764 - updated kernel now missing ~/ for users
Summary: updated kernel now missing ~/ for users
Keywords:
Status: CLOSED DUPLICATE of bug 119597
Alias: None
Product: Fedora
Classification: Fedora
Component: pump
Version: rawhide
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Eido Inoue
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-02 01:07 UTC by Scott Sloan
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:02:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Here is the output from the logs (181.64 KB, text/plain)
2004-04-02 01:41 UTC, Scott Sloan 		no flags Details
View All

Description Scott Sloan 2004-04-02 01:07:13 UTC 
Description of problem:

Upgraded to latest kernel in the development tree, everything went
great no problems. rebooted, and went to sign in, only to recieve a
message say that /home/scott was not present. open vitural terminal,
logged in as root, ls /home/scott -all   and everything was still in
tack. 

rebooted to kernel-2.6.3 and was abled to log in as scott with no
error messages

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

[scott@localhost scott]$ rpm -q kernel

kernel-2.6.4-1.300
Comment 1 Scott Sloan 2004-04-02 01:09:35 UTC 
thinking this to could be related to 

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119517

and

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119763
Comment 2 Scott Sloan 2004-04-02 01:41:00 UTC 
Created attachment 99056 [details]
Here is the output from the logs
Comment 3 Scott Sloan 2004-04-02 08:03:32 UTC 
If my research is right, pump is a dhclient. Can someone point me to
what I'm missing as to how this is a pump bug? Thanks.
Comment 4 Scott Sloan 2004-04-02 14:04:10 UTC 

*** This bug has been marked as a duplicate of 119597 ***
Comment 5 Red Hat Bugzilla 2006-02-21 19:02:20 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.