Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Upgrade woes related to Java and other things
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
tagger
n00b
n00b


Joined: 31 Mar 2005
Posts: 37

PostPosted: Fri Oct 27, 2006 7:41 pm    Post subject: Upgrade woes related to Java and other things Reply with quote

I installed Gentoo a little over a year ago on my G5 (PPC64), and only recently decided to do a
Code:
emerge --update --deep --ask world

--ask told me that there were essentially two Blocks: x and java. the x block was pretty easy to fix with an unmerge - i found that several people had this problem, in forums, and followed the advice for fixing. The java problem was a bit more difficult.

First, I apologize for not having some of the details of the process... I didn't realize that they might be pretty important. Hopefully I can provide enough to get a little help.

Also, before doing anything, of course, I followed the instructions and emerged portage. That very first step was uneventful.

So, the first Java block indicated the need to download ibm-java2-ppc64-sdk-5.0-3.0.ppc64.rpm from IBM. I did this, and then, according to the instructions, ran
Code:
emerge =ibm-jdk-bin-1.5*

This seemed to work as advertised. (By the way, along the way, occasionally, an etc-update was required - I never skipped such a step.) I tried
Code:
emerge --update --deep world

again, which progressed awhile, and then gave me an error saying that now Java 1.4.2 was needed ("Java_14", I think the message said, but other things made it clear that 1.4.* was what was meant). This message went into a long explanation about why both old and new Javas are needed, and so forth. It asked me to run /usr/bin/java-check-environment, which told me basically the same thing. So, I went to get IBMJava2-142-ppc64-SDK-1.4.2-6.0.ppc64.rpm, to put in /usr/portage/distfiles/, just like the SDK 5.0 I mentioned getting above. The instructions at this stage actually said to do:
Code:
emerge -autv1 '=dev-java/ibm-jdk-bin-1.4.2.5*'

slightly different than the 1.5 installation above. This apparently "worked", too. I actually tried it before grabbing the RPM, which failed (as expected) -- once the RPM was in place, it worked. I'm sure there's a little magic in there I don't know much about, nor do I really care much about it all. I'm not fond of Java myself and don't really use it in my own development, but realize that I use it indirectly frequently, as lots of apps these days depend on Java.

Anyway, back to the point. At this point, emerge --update --deep world told me that something was wrong with the configuration, so the older Java was essentially useless (sorry I can't remember the details, but...) it told me to run
Code:
emerge =virtual/jdk-1.4*

This did something apparently successful, but not successful enough. I still had a problem continuing. The next suggestion was to emerge java_config. I don't even recall if this worked or what it did. I recall noticing /etc/env.d/java and 20java were important, and trying to establishing a link (ln -s). Ultimately, my java-check-environment told me:
Quote:

* Generation-1 configuration files were found in /etc/env.d/java
* Please run the following to remove them:
# rm /etc/env.d/java/20java
* You must then update your VMs to Generation-2 by running:
# emerge -autv1 ''
* If you've done this already....

And so-on. It refers to the Java upgrade guide and so forth.

Now for the climax. So much time had passed, doing all of this, that I was done for the day. erroneously, it seems, I thought I could shut down and boot back up the next day and continue where I left off. Unfortunately, the next day, when I booted, I got:
Quote:

* The Gentoo Linux system initialization scripts have detected that
* your system does not support UDEV.....

Going on by hitting enter or waiting 15 seconds, it continues:
Quote:

* Checking root filesystem...
fsck.ext3: No such file or directory while trying to open /dev/sda4 ...
The superblock could not be read or does not describe a correct ext2 filesystem....
* Filesystem couldn't be fixed :(
Give root password for maintenance
(or type Control-D to continue):

Some suggestions follow. Basically, I'm hosed. My root filesystem does seem to have mounted, apparently -- I can look at things like my fstab to confirm that sda4 is (supposed to be) my / (I'd forgotten, since it had been so long). But it's true, there is no sda4 in /dev/, whatever that might mean about my hosed state.

I really didn't expect all this difficulty updating, so I'm a little discouraged. I'm considering drastic measures like getting out an install CD and trying to boot from that to see if I can get stuff worked out, but I'm a bit worried about the tack I should take. Since the hard-drive boot fails so early, I have nothing (no connection to the network, etc.), so I'm forced to think drastically.

Any thoughts or helpful suggestions? [/code]
Back to top
View user's profile Send private message
nixnut
Bodhisattva
Bodhisattva


Joined: 09 Apr 2004
Posts: 10974
Location: the dutch mountains

PostPosted: Fri Oct 27, 2006 8:27 pm    Post subject: Reply with quote

Moved from Installing Gentoo to Gentoo on PPC.
Postinstallation problems. PPC stuff so better off here.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered

talk is cheap. supply exceeds demand
Back to top
View user's profile Send private message
tagger
n00b
n00b


Joined: 31 Mar 2005
Posts: 37

PostPosted: Fri Oct 27, 2006 8:47 pm    Post subject: Reply with quote

Ok, thanks. I wasn't sure if this was PPC specific or not.
Back to top
View user's profile Send private message
ivertex
n00b
n00b


Joined: 29 Sep 2003
Posts: 12
Location: Phoenix, AZ

PostPosted: Thu Nov 09, 2006 6:59 am    Post subject: May not be PPC specific Reply with quote

I believe this happens when you have kernel prior to 2.6.14 (if memory serves) and have updated other packages to more recent versions.

Another case where I know it happened to me is having upgraded to kernel 2.6.14+ (which only supports UDEV) and having an /etc/fstab that still has the 'old' names like /dev/sda3. The 'new' name under udev would be /dev/discs/disc0/part3 and fstab needs changed to reflect that or the initial mounting at boot time will fail. Once booted there are ways with udev to make /dev/sda3 come back, but I don't believe /etc/fstab can ever use the 'old' names.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum