I noticed the sun-jdk ebuilds are leaving behind a directory in /opt
after each update. I presume these are safe to delete?
Thanks,
Ian
# cd /opt
# ls -aR sun-jdk-1.4.2.0[4-8]
sun-jdk-1.4.2.04:
. .. .systemPrefs
sun-jdk-1.4.2.04/.systemPrefs:
. .. .system.lock .systemRootModFile
in the first place, but oh
well.)
With that change 2.6 came up as well.
Thanks Again!
Ian
Ian Brandt wrote:
Mike Williams wrote:
OK great, I'd change my fstab, and reboot to 2.4.X/devfs now, but I'm known
for being a little gungho :)
Well, guess there's not much more I can do
Mike Williams wrote:
Kinda, yes.
Add /dev/sdXY entries, but under someother directory, /mnt/gentoo for example.
i.e.
/dev/sda3 /mnt/gentoo auto noatime 0 1
/dev/sda1 /mnt/gentoo/boot auto ro,noatime 0 0
etc, etc
The mount -a, and see what happens.
Great suggestion. Trying it I got a
John Jolet wrote:
what does cat /proc/mounts say?
# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / reiserfs rw,noatime 0 0
none /dev devfs rw 0 0
proc /proc proc rw 0 0
none /dev/shm tmpfs rw 0 0
/dev/scsi/host0/bus0/target0/lun0/part1 /boot ext3 rw,noatime 0 0
--
gentoo-user@gentoo.org
John Jolet wrote:
okay, and does that agree with /etc/mtab?
Not exactly:
# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / reiserfs rw,noatime 0 0
none /dev devfs rw 0 0
proc /proc proc rw 0 0
none /dev/shm tmpfs rw 0 0
/dev/scsi/host0/bus0/target0/lun0/part1 /boot ext3 rw,noatime 0 0
#
Mike Williams wrote:
Interesting...
A 'cat /proc/mounts' like John suggest would be helpful, before and after
attempting to mount stuff, also try the mount manually.
mount /dev/sda3 /mnt/somethingthatexistsbutisntbeingused.
The manual mount worked:
# cat /proc/mounts
rootfs / rootfs rw 0 0
Mike Williams wrote:
OK great, I'd change my fstab, and reboot to 2.4.X/devfs now, but I'm known
for being a little gungho :)
Well, guess there's not much more I can do.
Supposing it doesn't come up, would a rescue CD be required to fix it?
I left a copy of the old /etc/fstab as
Upon trying to boot a gentoo-sources-2.4.28-r9 kernel the NOC tells me
I get an error to the effect of the Gentoo init system can't get devfs
or udev up and running (sorry for not having the exact text of the
error, it was summarized to me over the phone). I built the kernel
via make oldconfig
Hi,
I'm trying to remotely upgrade my server from
gentoo-sources-2.4.25_pre7-r2 to gentoo-sources-2.6.13-r9, i.e. from
devfs to udev. My root partition is on a RAID 1 mirror on an Adaptec
2100S. My existing fstab is below. It was summarized to me by the
NOC over the phone, so I don't have the
Mike Williams wrote:
I'd imagine /dev/sdXY will exist under both udev and devfs, and be the same,
they certainly always have done for me.
For whatever reason I couldn't get /dev/sda3 in fstab to work when I
originally installed Gentoo on this box many moons ago, I had to use
Richard Fish wrote:
Jerry McBride wrote:
FYI, the bootmisc init script already does this for you, or at least it
does with the ~x86 baselayout. Just rc-update -a bootmisc boot if it
isn't already turned on.
Also, syslog-ng will dump the kernel log to /var/log/messages when it
starts up.
Hi,
Is it possible to get the dmesg for the boot prior to the current one?
I'm trying to remotely upgrade from the 2.4 to 2.6 kernel. I followed
the migration guide, but I got something wrong because my server
didn't come back up after reboot. Fortunately I used lilo -R to boot
to the 2.6
12 matches
Mail list logo
