Bug 152100

Summary:	while booting, init script for powersaved and Mount SMB/ CIFS file systems gets mixed up
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Jon Nelson <jnelson-suse>
Component:	Other	Assignee:	Holger Macht <hmacht>
Status:	VERIFIED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P5 - None	CC:	suse-beta, werner
Version:	Beta 4
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Jon Nelson 2006-02-19 16:49:17 UTC

What I see is this:

Starting powersaved: Mount SMB/ CIFS File System         unused

Not sure what's going on there but I see two problems:

1. it's not clear /which/ is 'unused' - in either case these should be on their own lines.
2. There is an extra space after 'SMB/' (It should read SMB/CIFS no space) (pretty minor issue)

Comment 1 Jon Nelson 2006-02-19 19:02:34 UTC

This is reproduceable by switching to and from runlevels (such as runlevel 1 and 3).

Comment 2 Holger Macht 2006-03-17 23:51:33 UTC

Will look at it as soon as I find some spare time.

Comment 3 Holger Macht 2006-03-17 23:52:13 UTC

Setting to REMIND

Comment 4 Forgotten User ZhJd0F0L3x 2006-03-18 12:49:21 UTC

this is probably a "parallel booting / blogd" issue IMO, and one that probably nothing can be easily done about.

Comment 5 Holger Macht 2006-03-18 13:12:58 UTC

I think the line "Starting powersaved:" is printed at the very beginning of the rcpowersaved script. Maybe we should simply shift this text to a later point were we actually print the remaining text like 'loading modules'...

Comment 6 Stefan Behlert 2006-09-13 12:15:44 UTC

Looks better in alpha4 of openSUSE10.2, at least it was not visible on the tested machines. Please reopen if it happens again with alpha5.

Comment 7 Bugzilla Account Maintenance 2008-09-02 18:08:10 UTC

Because the LATER and REMIND resolutions have been removed, the resolution of this bug has changed from REMIND to WONTFIX. If this bug needs to be reconsidered, reopen it and set a future "Target Milestone for Fix."