Hi all of course, the subject is a joke! ;-) Yesterday, finally, I succeeded in making an on-line update of my SuSE 9.1 (it seemed a matter of /dev/null permissions - thanks to Leen anyway). Since the list of patches I had to install was very long I started installing a certain number of them (say more than one half). The result has been the following: MANY CONFLICTS: Samba, Evolution & other packages. I had to downgrade them to the previous versions. FIREFOX: I was not able to start it neither as root nor as user (X server problem). Downgraded to the previous version (0.8). Works fine. ON BOOT: This message repeated about fifteen times: "/sbin/splash: line 1: /dev/null: Read-only filesystem" then "/etc/init.d/boot.d/S01boot.proc: line 51: /dev/null: Read-only filesystem" coldplug waits for 20/25 seconds before to start scanning: "coldplug scanning input:" (20/25 seconds stop) Setting up network interfaces: waiting for mandatory devices: eth0 20 19 18 17 16 14 ^^^^^^^^^^^^^^^^^ ?? (this line is mine) "Starting RPC portmap deamonportmap: fork: Success failed" (the same message I have on the notebook as I posted some day ago) Before the update the message was: "Starting RPC portmap deamonportmap done" and, as a consequence of the above: "Failed services in runlevel 5: portmap" ON SHUTDOWN: Thede messages: /etc/init.d/boot.d/K17boot.md: line 51: /dev/null: Read-only filesystem /etc/init.d/boot.d/K19boot.rootfsck: line 51: /dev/null: Read-only filesystem /etc/init.d/boot.d/K20boot.shm: line 51: /dev/null: Read-only filesystem /etc/init.d/boot.d/K21boot.proc: line 51: /dev/null: Read-only filesystem /etc/init.d/boot.d/K21setserial: line 51: /dev/null: Read-only filesystem proc umounted /etc/init.d/rc6.d/S20reboot: line 110: /dev/null: Read-only filesystem That's all, at the moment. Is there anyone that can explain to me (or give me any link) about what happened? Ciao emilio
Hi Emilio, I'll comment only on the things I know about. I'll leave out the remaining stuff for someone else to comment on (denoted with [...]). On Saturday 12 March 2005 11:45, contiemilio@virgilio.it wrote:
Hi all of course, the subject is a joke! ;-)
Yesterday, finally, I succeeded in making an on-line update of my SuSE 9.1 (it seemed a matter of /dev/null permissions - thanks to Leen anyway).
Hmm, I must have missed your post where you describe how you solved your previous problem(s).
Since the list of patches I had to install was very long I started installing a certain number of them (say more than one half).
A hint: Many patches -> a) either you installed 9.1 very recently and had no choice; b) you installed 9.1 a while ago. In that case it probably would have been better to update on a regular base, e.g. once a month or perhaps once a week. Then the list of patches/packages to update will remain short and it would be easier to solve problems. Looking back at the messages you posted, it seems you had no choice [although you could have tried to update gradually, e.g. one (or a few) patch(es) after another ;P ]
The result has been the following:
[...]
FIREFOX: I was not able to start it neither as root nor as user (X server problem). Downgraded to the previous version (0.8). Works fine.
You already solved this problem, so the problem does not exist anymore. :)
ON BOOT:
This message repeated about fifteen times: "/sbin/splash: line 1: /dev/null: Read-only filesystem" then "/etc/init.d/boot.d/S01boot.proc: line 51: /dev/null: Read-only filesystem"
Seems root was mounted read/only??? Post your /etc/fstab. [...]
Setting up network interfaces: waiting for mandatory devices: eth0 20 19 18 17 16 14 ^^^^^^^^^^^^^^^^^ ?? (this line is mine)
This is just a count-down from 20 seconds. Seems after about 6 seconds eth0 came up, so nothing to worry about.
"Starting RPC portmap deamonportmap: fork: Success failed" (the same message I have on the notebook as I posted some day ago)
Is that notebook different from the pc you're talking about in this email?
Before the update the message was: "Starting RPC portmap deamonportmap done"
and, as a consequence of the above:
"Failed services in runlevel 5: portmap"
Could be related to the 'Read-only filesystem'-error, but let's see if portmap has something to say: Try this, as root, in a terminal window (konsole or xterm): rcportmap status if it is not running, try this: portmap -d and post any error messages. To kill portmap (if it is still running), open another terminal window, become root, and enter: ps aux|grep portmap You'll see something like nobody 25643 .... portmap -d root 25660 .... grep portmap The number right after 'nobody' is portmap's process id. Use that to kill portmap: kill 25643 You most certainly would have to use another process id
ON SHUTDOWN: Thede messages: [snip] /etc/init.d/rc6.d/S20reboot: line 110: /dev/null: Read-only filesystem
As earlier in this email: post /etc/fstab Cheers, Leen
Alle 14:15, sabato 12 marzo 2005, Leendert Meyer ha scritto:
Hi Emilio,
I'll comment only on the things I know about. I'll leave out the remaining stuff for someone else to comment on (denoted with [...]).
Your answer has been very fast! ;-) Or it's been my post too quick! ;-( To-day I installed other patches and almost all my problems seem disappeared! (please, don't ask me which (whose) patch(es) solved the problem: I shouldn't answer you). All apart from:
Setting up network interfaces: waiting for mandatory devices: eth0 20 19 18 17 16 14 ^^^^^^^^^^^^^^^^^ ?? (this line is mine)
This is just a count-down from 20 seconds. Seems after about 6 seconds eth0 came up, so nothing to worry about.
Yes, but that didn't happen before the update. and the conflicts (may be these also are going to be solved after the installation of other patches). Finally, to answer your question: yes, I installed SuSE 9.1 recently (4 months - 2 weeks on notebook)
Cheers,
Leen
Ciao emilio
On Saturday 12 March 2005 15:59, contiemilio@virgilio.it wrote:
Alle 14:15, sabato 12 marzo 2005, Leendert Meyer ha scritto:
To-day I installed other patches and almost all my problems seem disappeared!
I'm glad. :)
All apart from:
Setting up network interfaces: waiting for mandatory devices: eth0 20 19 18 17 16 14 ^^^^^^^^^^^^^^^^^ ?? (this line is mine)
This is just a count-down from 20 seconds. Seems after about 6 seconds eth0 came up, so nothing to worry about.
Yes, but that didn't happen before the update.
It's a feature, not a bug/error.
and the conflicts (may be these also are going to be solved after the installation of other patches).
Well, install those patches first. After that, come back if you still have problems. Cheers, Leen
participants (2)
-
contiemilio@virgilio.it
-
Leendert Meyer