Bug 631590

Summary:	I have a different prompt in single mode
Product:	[Fedora] Fedora	Reporter:	Couret Charles-Antoine <renault>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	awilliam, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	initscripts-9.20-1.fc14	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-09-14 23:24:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Couret Charles-Antoine 2010-09-07 23:39:58 UTC

Description of problem:
With Fedora 13 and Upstart, if I boot in runlevel 1, I access in root account.
But with Fedora 14, I have a « bash4-1# » prompt.

How reproducible:
Boot in runlevel 1

Additional info:
I use Fedora 14 64 bits.

Comment 1 Michal Schmidt 2010-09-08 08:35:37 UTC

The difference is that with upstart the shell run from sushell processes /root/.bashrc. With systemd it does not.
The reason is that with systemd we have "HOME=/" in the environment. Not sure why.

Comment 2 Lennart Poettering 2010-09-08 23:11:22 UTC

The kernel actually sets that HOME=/ for some weird reasons IIRC and we don't change that.

I have now changed the units invoking sushell to set $HOME=/root. This should fix this issue.

Comment 3 Fedora Update System 2010-09-09 21:53:29 UTC

systemd-9-3.fc14,initscripts-9.20-1.fc14,sysvinit-2.87-5.dsf.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/systemd-9-3.fc14,initscripts-9.20-1.fc14,sysvinit-2.87-5.dsf.fc14

Comment 4 Fedora Update System 2010-09-10 15:14:45 UTC

initscripts-9.20-1.fc14, sysvinit-2.87-5.dsf.fc14, systemd-9-3.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update initscripts sysvinit systemd'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/systemd-9-3.fc14,initscripts-9.20-1.fc14,sysvinit-2.87-5.dsf.fc14

Comment 5 Couret Charles-Antoine 2010-09-11 09:06:13 UTC

With the update, I don't have the problem. This bug is fixed. :)

Comment 6 Adam Williamson 2010-09-11 22:13:35 UTC

Please don't close the bug until the update has been accepted into the stable F14 repository. It is not fixed with the update only in updates-testing.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 7 Adam Williamson 2010-09-11 22:13:48 UTC


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 8 Fedora Update System 2010-09-14 04:29:12 UTC

systemd-10-1.fc14, initscripts-9.20-1.fc14, sysvinit-2.87-5.dsf.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update systemd initscripts sysvinit'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/systemd-10-1.fc14,initscripts-9.20-1.fc14,sysvinit-2.87-5.dsf.fc14

Comment 9 Fedora Update System 2010-09-15 07:12:47 UTC

initscripts-9.20-1.fc14, sysvinit-2.87-5.dsf.fc14, systemd-10-2.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.