I installed a default GNOME workstation. Samba-client gets installed, but there is no nmblookup included. The script smbfind returns a fatal error.
Fixed in samba-2.0.5a-14, which will be in the next Raw Hide release.
*** Bug 5608 has been marked as a duplicate of this bug. *** Extremely annoying, happen in update mode from RH-6.0 It doesn't preserve it in lilo.conf.rpmorig
*** Bug 5951 has been marked as a duplicate of this bug. *** I had a 6.0 install on my system. I was using System Commander (a commercial product) to handle loading the multiple OS's I run (Linux, 98, NT). I recently tried upgrading to 6.1. First time thru the install, I figured I'd try doing an "upgrade" (I normally do complete re-installs). I followed the graphical installer instructions, and 6.1 was installed/upgraded. When the system rebooted I found that LILO was setup on my MBR, not on my Linux Partition (as I had been using). Not exactly what I was expecting. During an upgrade, why setup LILO on a partition where it does _not_ exist? I can see on a new install (and the installer explicitly asks in that case), but during an upgrade, presumably one does not change the location of the existing boot loader. The installer should _not_ _assume_ the location of the boot loader. It should make a best effort to determine where to install, and then ask if that is what I want. Anyway, some more data points... LILO had a 'dos' entry available, so I tried it out. That got me into Win98 (not System Commander, and co-incidentally the OS I booted before my upgrade attempt). Curious thing though, when I rebooted after that System Commander came up (and has since). I presume System Commander "reinstalled" itself in the MBR somehow. BTW, I things are really great otherwise, it even detected my SB!Live card. Although I don't think it works under SMP kernels yet, perhaps I try just to see, I'd be pleasantly surprised if it did work.
*** Bug 6238 has been marked as a duplicate of this bug. *** upgrading from 6.0->6.1 overwrites lilo.conf without giving the victim an opportunity to specify needed options, like linear.
*** Bug 6626 has been marked as a duplicate of this bug. *** You *REALLY* to prompt the user before installing LILO information over an existing LILO configuration. Why not look at the MBR to see whether LILO information is already in place, then prompt the user? By the way, I REALLY like the new GUI install! Keep up the good work.