Bug 29670

Summary:	updating baselayout with automounted /home leaves system unbootable
Product:	Gentoo Linux	Reporter:	Ernst Bachmann <e.bachmann>
Component:	[OLD] Core system	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Ernst Bachmann 2003-09-26 06:14:17 UTC

I'm using automount/autofs to mount /home/ from a nfs server. 
when updating baselayout (probably other packages as well), the emerge 
finishes ok, but when copying the new files to their final destination it 
breaks when trying to create /home/.keep (impossible on automounted /home) 
The remaining files are not copied over, leaving the system in an inconsistent 
state (It was quite difficult to get it to boot again) 
 
I think an automounted /home is quite common in larger environments, so the 
ebuilds should be aware of this. (the apache ebuilds are an other example for 
this, they try to create /home/apache if not modified) 

Reproducible: Didn't try
Steps to Reproduce:
1. fail to update your system for a long time (uptime was about 200 days) 
2. emerge -u baselayout 
3. init 6 
Actual Results:  
System didn't boot cause the init scripts didn't work 

Expected Results:  
ignore/warn about /home/.keep, continue copying remaining files.

Comment 1 SpanKY gentoo-dev

2003-09-26 18:09:09 UTC


*** This bug has been marked as a duplicate of 9849 ***