using sudo
by David Berg
I'm in the process of switching from ubuntu to Fedora and am so far
impressed. The first thing I want to change is how administration is
handled. I like ubuntu's decision to remove the root password and only
allow root access through sudo.
So I gave myself full sudo access, disabled root logins, and eliminated
the root password. Works great on the command line.
The problem is this: How can I get the gui's to switch from wanting to
use an su interface (and asking for a non-existant root password) to
using sudo?
Is there setting or link I can change to have everything switch over?
--Dave
17 years, 5 months
Upgrade warnings FC6 x86_64 (with xen)
by Bill Davidsen
I just did an install of FC6+xen, and I'm not sure if xen is involved in
the problem or not. After I did the initial install and rebooted, I
checked the list of updates
yum check-update | tee update.list
and found updates for the kernel, yum, and virt-manager. Doing the
updates cautiously (I have been seeing upgrade problems), I got:
Is this ok [y/N]: y
Downloading Packages:
(1/1): virt-manager-0.2.6 100% |=========================| 452 kB
00:02
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Failed to load file "/etc/gconf/gconf.xml.defaults/%gconf-tree-nl.xml":
Error on line 7519 char 29: Invalid UTF-8 encoded text
Failed to load file "/etc/gconf/gconf.xml.defaults/%gconf-tree-hu.xml":
Line 1557 character 50: No text is allowed inside element <dir>
Failed to load file "/etc/gconf/gconf.xml.defaults/%gconf-tree-ja.xml":
Error on line 6767 char 77: Invalid UTF-8 encoded text
Failed to load file "/etc/gconf/gconf.xml.defaults/%gconf-tree-gu.xml":
Error on line 4460 char 80: Invalid UTF-8 encoded text
Failed to load file "/etc/gconf/gconf.xml.defaults/%gconf-tree-ru.xml":
Error on line 4134 char 51: Invalid UTF-8 encoded text
Failed to load file "/etc/gconf/gconf.xml.defaults/%gconf-tree-es.xml":
Error on line 8160 char 5: Invalid UTF-8 encoded text
Updating : virt-manager ######################### [1/2]
Cleanup : virt-manager ######################### [2/2]
Updated: virt-manager.x86_64 0:0.2.6-1.fc6
Complete!
Is this meaningless, or a hint that something else is wrong?
--
bill davidsen <davidsen(a)tmr.com>
CTO TMR Associates, Inc
Unsigned numbers may not be negative. However, unsigned numbers may be
less than zero for sufficiently large values of zero.
17 years, 5 months
Re: dual boot 1 drive
by Oldman
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Timothy Payne wrote:
> I've tried (hd0,0) no luck
>
>
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this
> file
> # NOTICE: You have a /boot partition. This means that
> # all kernel and initrd paths are relative to /boot/, eg.
> # root (hd0,0)
> # kernel /vmlinuz-version ro root=/dev/hda2
> # initrd /initrd-version.img
> #boot=/dev/hda
> default=0
> timeout=60
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title Fedora Core (2.6.18-1.2849.fc6)
> root (hd0,0)
> kernel /vmlinuz-2.6.18-1.2849.fc6 ro root=LABEL=/
> initrd /initrd-2.6.18-1.2849.fc6.img
> title Fedora Core (2.6.18-1.2798.fc6)
> root (hd0,0)
> kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=LABEL=/
> initrd /initrd-2.6.18-1.2798.fc6.img
> title Win 98
> rootnoverify (hd1,0)
> chainloader +1
>
>
> [root@localhost ~]# fdisk -l
>
> Disk /dev/hda: 41.1 GB, 41174138880 bytes
> 255 heads, 63 sectors/track, 5005 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/hda1 1 13 104391 83 Linux
> /dev/hda2 14 3200 25599577+ 83 Linux
> /dev/hda3 * 3201 5005 14498662+ c W95 FAT32 (LBA)
> [root@localhost ~]#
>
> On Fri, 2006-12-01 at 06:31 -0800, oldman wrote:
> Timothy Payne wrote:
>>>> I've done it with 2 drives no problem. FC 6 is first, Win98 second and
>>>> both work. Grub won't boot the Win98, and I must have tried 10
>>>> suggestions from the web. This is my last hope.
>>>>
>>>> Tim...
>>>>
> Well I think I'll need more information please!
>
> What is the output of /sbin/fdisk -l (that is a lower case "L" and run
> as root)
> Please post your /boot/grub/grub.conf
> Just to be sure, post your /boot/grub/device.map file too
> What exactly do you see when you try to boot Windows?
>
> Maybe someone else knows for sure, but I recall that various earlier
> versions of windows needed to be the first partition on the first drive
> of a system. Did you ever have your system with Win98 as the second
> partition with no other OS on the drive?
>
> Scott
>>
rootnoverify (hd0,2)
Grub starts counting partitions and drives with 0 so hd0,2 is the first
drive of the first hdd controller and the third partition partition on
that drive which is equal to fdisk's hda3
Good luck
Scott
P.S. You should keep responses on the mailing list so that others can
see answers too. I'll forward this to the list
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFFcX395mBKdb7VQEcRArVkAJ9X1UWy/+EupPKWDXwUkwC6xnSxYACePL+3
uw2cUrCpuOgcey4SNGFME4E=
=W21D
-----END PGP SIGNATURE-----
17 years, 5 months
Mom! K3b and yum are not sharing their toys again!!
by Ric Moore
OK, figuring something had to be missing I rpm -e k3b as there was no
k3b-devl installed and yum kept bitchin about it..
--> Populating transaction set with selected packages. Please wait.
---> Package k3b.i386 0:0.12.17-1 set to be updated
---> Package k3b-extras.i386 0:0.12.17-1.fc6 set to be updated
---> Package k3b-devel.i386 0:0.12.17-0.1.fc6 set to be updated
---> Package k3b-i18n.noarch 0:0.12.16-1 set to be updated
--> Running transaction check
--> Processing Dependency: k3b = 0.12.17-0.1.fc6 for package: k3b-devel
--> Finished Dependency Resolution
/usr/lib/yum-plugins/kmdl.py:42: DeprecationWarning: getHdrList() will
go away in a future version of Yum.
for hdr in conduit.getRpmDB().getHdrList():
Error: Missing Dependency: k3b = 0.12.17-0.1.fc6 is needed by package
k3b-devel
Ur.. ahhh... is it because there is a zero missing on the package
schema? k3b.i386 has 0:0.12 which may be a typo??? k3b devel wants 0.12
so I'm boggled. Anyone have a clue?? Should I just GRAB the darn
k3b-devel package manually and put the --force to it?? Goldang computers
anyway. <Sigh> Ric
17 years, 5 months
Can't get GRUB installed.
by Ted Gervais
I am having trouble booting up core6. I installed it earlier today and
after trying to find a way to get Grub to work I formatted the drive and
started over.
Now I am back at the same prompt with no core6 running. Grub does not
appear and the result is - Windows comes up rather than linux.
I am totally lost now. There is no sign at all that there is even Linux
installed on this computer, and yet I just took off centos which was
working fine and it used grub as its windows manager.
I have two harddrives (hda and hdb).
HDA is for Windows and HDB for Linux.
That is how it was with centos and previous versions of linux such as
core5. It always worked fine.
Now I get nothing when I reboot the machine other than windows..
What am I overlooking? And is there a way that I can bring up this
installed version of Fedora (core6) using the rescue disk? If this is
possible what would be the boot line to get things running?
---
Ted Gervais,
Coldbrook, Nova Scotia, Canada
17 years, 5 months
An rpm of TeXmacs for fedora Core 6 X64 bit
by Jan Brosius
Hello,
I upgraded from fedora Core 5 x64bit to fedora Core 6 x64bit. However I
found that TeXmacs was not included in the extras package list anymore.
This rpm package is included in the extras of Fedora Core 5 (x64bit). I
am not capable to do thid myself. Would anyone try to package TeXmacs
for Fedora Core 6 (x64bit).
Thanks
Jan
17 years, 5 months
/var/lib/dbus?
by Tom Horsley
I just updated my x86_64 partition and my i386 partition (both FC6).
When I rebooted x86_64 after updating i386, I got a message that
it couldn't create the /var/lib/dbus/machine-id file.
Sure enough, there was no /var/lib/dbus directory. I created it by
hand and dbus was happier.
I looked over in the i386 root partition, and it did have a /var/lib/dbus
directory.
Did the x86_64 dbus rpm leave that bit out or something?
17 years, 5 months