Posts Tagged ‘OS’

RedHat Repositories

Monday, February 1st, 2010

Situation: You are not the administrator of your server Redhat repository and the administrator takes a couple weeks to get back to you. You have to quickly rebuild your server in case of failure or for a test environment.

Solution: Backup the /etc/sysconfig/rhn/systemid to another location. Restore the file to the same exact server after rebuilding, verify permissions are correct (chmod 644), and you’re back in business.

Native Install of Redhat v5.3 Linux on a MacPro

Saturday, February 28th, 2009

The simplest way to install RedHat Linux v5.3 natively on a MacPro is to do the following:

Download RedHat EL v5.3 for Server or Desktop…or buy it.  I used the 64bit version for some kick butt performance.

Have a dedicated drive for Linux

Power off the system and unplug it

Unplug powered devices such as Ethernet

Pull out the other drives such as MacOS or Windows

Note: If you leave the drives in, Grub may recognize them and overwrite partition sectors or MBR.  I usually pull the drives out a couple inches, leaving the case lid off.  Grub is smart, perhaps too smart!

Boot up the system with the first Redhat CD or DVD in the drive.

Important Note: All non-MacOS drives and CD’s are recognized as Windows in the Boot Menu!  Weird huh?

Note: If you forget to pop in the CD/DVD, just hold down the ALT key then press the eject button (or F12 if you have a PC keyboard) or just type in eject /dev/sr0 or /dev/sr1 at the command prompt if you’re in redhat.

Install Linux as you normally and partition it as you normally would and remove all partitions.

Check the Review and modify partitioning layout

Check Configure advanced boot loader options

Selection /dev/sda1 First sector of boot partition

Note: Since the BIOS is EFI, it will not recognize MBR’s without a third party program

Carry on and install as you normally would.

After installation, you will get some error messages.  Don’t panic, unless the kernel panics!

The error message “PCI:BIOS Bug:MCFG area at e0000000 is not E820-reserved
 PCI:NOT Using MMCONFIG” according to Redhat article ID 2199 is informational only.  Redhat will fix this in future releases so users won’t freak out.
If you receive the error message “i8042.c : no controller found”, then you likely have an Nvidia video card.  Nvidia has some driver issues and you can download a driver from Nvidia after you update the kernel.
 

If you receive the error Kernel panic, you been screwing around haven’t you?
 

Error is : Kernel panic –  not syncing: Attempted to kill init!

To fix the kernel panic:
Boot off of the Linux installer CD/DVD:
Type “linux rescue” without the quotes
Click Ok to English
Click Ok to us
Click No to network interfaces
Click Continue to /mnt/sysimage
Click OK
At the command line type the following:
grub
device (hd0) /dev/sda
Note: Don’t worry if you’re hard drive is not the first one, hd0 is the only drive the system will see since you pulled the others out.
find /grub/stage1
Note: the output should be find /grub/stage1 (hd0,0)
root (hd0,0)
Note: The output should be root (hd0,0) Filesystem type is ext2fs, partition type 0x83
setup (hd0)
Note: there’s a lot of output here.
Quit
reboot
Next hold down the alt key
Remove the Linux CD/DVD.
Everything should work, if not…..Well, that sucks doesn’t it??
Ok, if that doesn’t work done then it’s probably picking up the last configuration (Linux is too smart..or maybe too stupid?).  Download a utility called Gparted and wipe out the partition table.
Note: Gparted will work but when you boot off the CD, load it into RAM.  Otherwise you will be able to erase, but not create partitions on the MacPro.  Yeah, it’s a bug.  I like to create an NTFS partition just to make sure I wiped out the old one.
Unplug everything and put the drives back in.
 

In order to go to the Linux partition, just hold down the ALT key and select the RedHat drive.  

MacOS 10.4.10-11 Lockup Problems

Friday, December 7th, 2007

Since upgrading to MacOS 10.4.11, I’ve had users complain about systems locking up and freezing.  The system wasn’t locked up, but waiting for a timeout.  At first I thought, this issue was confined to the Intel based Macs…..Wrong.  After looking at the logs I noticed some NetInfo events had occurred:

DirectoryService: NetInfo connection failed for server 127.0.0.1/local

After doing some research, I found a odd bug/solution.  The program listed below periodically polls lookupd to detect if it’s not responding and if so, forces it to terminate.  This solution may not be for everyone, but thus far works for me.  So do your homework on it.

Unlockupd

OU Admin Training–Thoughts

Thursday, April 27th, 2006

I went to some OU training and found a few gems of information I thought I would share.

To see a GUI version of Group Policies being downloaded:

Start\Help and Support\Use Tools to view your computer information and diagnose problems\Advanced System Information\View Group Policy settings applied\ 

Using the netdom utility:

netdom.exe move computer_name /Domain:asurite.ad.asu.edu /OU:OU=m.myou.mysubou,OU=m.myou,dc=asurite,dc=ad,dc=asu,dc=edu /UserD:myusername /PasswordD:*

Adding the asterisk at the end of the command will prevent your password from being echoed on the screen…..Oooohh, ahhhhh…..Isn’t that cool?

Force a user to choose between OS’s:

In the boot.ini file change the timeout to “-1” without the quotes.  The default timeout is 30. 

ASU is complaining that departments are using global groups too much and should be using Universal Groups instead.  Apparently using the former causes more network traffic.  Shouldn’t IT, err UTO be more concerned about the compromised PC’s on campus doing warez file shares and hack attempts?  Oh wait I almost forgot what they told me, “We build our applications and systems with security from the beginning, it’s not an afterthought.”  Silly me.
Well anyway, that’s what I learned from my 16 hours of training.

Windows / Apple updates

Wednesday, April 12th, 2006

In the last few weeks, there have been a lot of updates for both Windows and Mac OS’s. 

The Mac OS 10.4.6 client update breaks quite a few AFS features. (Ex. Breaking shares on 10.3.9 server and Apple shares located on the client)