How high will Microsoft fly? Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : How high will Microsoft fly?

MSFT 485.49

+1.8%

Nov 26 3:59 PM EST

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: SunSpot who wrote (42402)	4/17/2000 3:39:00 PM
From: Gerald Walls	Read Replies (1) of 74651

OT A new server has been put up (Pentium 100MHz, 32MB RAM, Red Hat Linux 6.2) I did an upgrade on my 486 internet gateway/firewall machine this weekend. Red Hat 6.1 to Red Hat 6.2. I'd already upgraded the kernel to 2.2.14-1.1.0. The upgrade updated the kernel to 2.2.14-5.0. Needless to say, something got screwed up when I upgraded this "easier to use and maintain than Windows" (or so some have claimed) operating system. My standard NE-compatible ethernet card quit working, and after a while I noticed that I was getting a couple of "can't find module xxx" messages during my numerous reboots. I noticed that the boot ramdisk was still initrd-2.2.14-1.1.0 and I believe (going from memory here) that the lilo.conf file mentioned this ramdisk associated with the vmlinuz-2.2.14-5.0 file. I then tried to "mkinitrd /boot/initrd-2.2.14-5.0 2.2.14-5.0" and was told "All the loopback devices are in use!". Doing an "init 1" to go into single user mode (just something to try) didn't help. I also noticed that the login prompt, which reports the kernel version, also thought the kernel was 2.2.14-1.1.0. I eventually just gave up and re-upgraded, manually marking the kernel components to force and upgrade over itself. Now my ethernet works and there are no module error messages. However, the ramdisk is still 2.2.14-1.1.0, but it doesn't seem to be mentioned in the lilo.conf file at all. If what I've read about the ramdisk being for pre-mount drivers (i.e, SCSI) is true then I don't see why it was ever created and used anyway as I have no SCSI By the time I go to bed tonight I expected to have my PPP functional again.

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next