Thanks again to krishna.murphy for a thourgh and speedy reply.
From what I understand, talking to several of the Debian creaters and others, it has been a general concensus to lock up "root" as an "X" window type format because we're all too clumsy and don't take care enough to watch what we do. So they have to baby sit us and make sure we don't do anything to our system. Of course, they forget I can do a terminal window, type sudo, then "cd /;rm -fr *" and the whole system is gone. They're protection is in the wrong place, needs to be in education, not slapping nuckles with a ruler. But that is their problem. I'll keep trying various suggestions including yours on getting root privelage X programs to run. First thing I think I'll try something other than KDE.

The BIOS problem seems to be wide spread, but most people either have small systems or do not use SCSI. The general problem is, I have SCSI BIOS start, (during boot), and get /dev/sda, /dev/sdb, etc. When the OS starts, that still holds through boot (in some cases). If not, what it is doing is the OS is running a search for all devices that match SCSI drivers (ATA), IDE (new), USB storage, SCSI drives or tape drives and the first one gets assigned /dev/sda, second /dev/sdb, etc. Problem arises, if I happen to have my first item it finds in the sting turned off or on another computer (it's a portable USB drive), this shifts the /dev's back one and now what might have been my boot drive (/dev/sdk2) is now /dev/sdj2 and the system gives me a boot error. I have to correct all devices back to what they were and reboot. If I permanently, remove or re-arrange something, I have to manually change the boot sequence in the OS to the new drive designators. Generally, as I have seen for years, HD's are always handled first and retain their address, peripherals are added as placed or found.