HowTo reinstall grub after a Windows install wipes the MBR

Note that the exact partition spec will vary depending upon drive and partition order.


) Boot with a Live install,
) Use the disk drive GUI tool to locate
the MBR partition
the / (linux root)
the /boot (linux boot) [this is where /grub/stage(x) is]


grub
grub> root (hd0,1) # Assumes your /boot partition is sda2
grub> install (hd0,1)/grub/stage1 d (hd0) (hd0,1)/grub/stage2 p (hd0,1)/grub/grub.conf

exit and boot

HowTo selinux winbind

Who knows if this is a bug in Fedora policies, but to stop F11 from complaining:

sudo semanage port -a -t winbind_t -p tcp 1029
sudo semanage port -a -t winbind_t -p udp 1029

Key to DNS on Fedora with Windows

I finally (years overdue) got bind 9.6 to work with Windows clients.
All the documentation for any version BEFORE 9.6 is out-of-date, ignore it.

For the zone "wolfish.rouges.org" not (192.168.0.0)
1) make the zone db file owned by the named user
chown -R named:named /var/named/chroot/var/named
2) add the allow-updates attribute to the zone
3) add the check-names ignore; attribute to the zone.

WATCH THE SYNTAX!

The named.conf file is indented perversely, so it is difficult to put the attribute in the correct context.


zone "wolfish.rouges.org." IN {
allow-update {
localnets;
};
check-names ignore;
type master;
file "wolfish.rouges.org.db";
};


Epic Win.

VMWare would not work. I did an uninstall and a hard clean and reinstalled, but It was just one problem after another.
So I downloaded VirtualBox, and the rpm installed flawlessly.
I started the console, and configured it with a copy of my OLD virtual drives. I Tried to power it up, but that failed, as expected.
However, I then booted from a Windows 2000 install iso, and selected full repair.

Presto! it booted right up.

I could have saved a day if I had tried that first.

Beware ownership and permissions with kerberos

I think the issue I was having with kadmin was due to a hidden dot file being not readable by anyone but root.
I know it was A problem, but not if it was THE problem. Same permissions issue with the /var/log/kadmin.log file.
I hate to say it, but on Fedora, you (basically) have to do everything for Kerberos as root.

Procedure for installing 389.

Follow the procedure below. If anything bad happens, start over from 1.
0) Create unix user, make passwords, choose server and admin ports, etc.

1) IGNORE most of the wiki.

2) Stop running 389
service dirsrv-admin stop
service dirsrv stop

3) Use yum to uninstall old 389 packages.

4) Delete the old dirs:
rm -rf /usr/lib/dirsrv /usr/share/dirsrv /var/lib/dirsrv /var/lock/dirsrv

5) Use yum to install the new 389 packages

6) Run initial setup script:
/usr/sbin/setup-ds-admin.pl

7) To setup ssl, ensure that both servers are running, and execute:
/home/installerlocal/garage/setupssl2.sh /etc/dirsrv/slapd-trixter 11562

8) Restart servers with
service dirsrv-admin restart
service dirsrv restart

9) Start console with:
/usr/bin/389-console -u admin -w not3xch4n53 -a http://127.0.0.1:3407

They fixed the 389 install bug!

Well, that's amazing wondrous.
In the two days since I posted my comment on the install bug, the fix is available from yum.
HOORAY for open source projects! Microsoft takes years to release bug fixes.