[FC8] useradd anomaly - GUI or command line???
by Deepak
Hi,
I am trying to add new users in my FC8 machine.
As root I issued command
# groupadd zion
# useradd -c "Some User" -m -g zion -p secret666 someuser
now If try to login from console is unsuccessful
===================
login: someuser
Password: secret666
gives me
login Incorrect
==================
I open the GUI user manager and remove the currently created user and
added the user the same name and password and added him to the zion
group.
Now i can login with that name and password noramally.
My Question
=========
Is there something broken in command line tool "useradd"?
Thanks
16 years, 6 months
Preferred Architecture for Centrino Core Duo
by Jeremy Nix
I was reading the Fedora 8 documentation and came across section 3.2
that recommends that the x86_64 architecture to be used for the Centrino
Core Duo processors. In prior versions, I have been running the i686
architecture, so I am curious as to what the benefits would be in
switching to a 64 bit architecture when my processor is a 32bit
dual-core. Can somebody explain this to me, as the documentation does
not really outline the benefits or reasons to switch to the 64 bit
architecture.
Thanks in advance.
--
__________________________________
Jeremy Nix
Senior Application Developer
Southwest Financial Services, Ltd.
(513) 621-6699
16 years, 6 months
FC8 Sound not working after kernel update
by Dean Maluski
Just did the yum update of xen kernel on IBM Thinkpad T22.
Afterward system sounds are not playing.
XMMS wasn't working either until I went in and reconfigured from default
PCM to Soundfusion (hw:0,0) In think it was set to default PCM device.
I can go in as root and detect sound card, works.
Also as X user do test sounds OK but when I try to play system sounds
nothbing heard and no complaints in /var/log/messages.
16 years, 6 months
problems with window focus and resize/move operations
by Nataraj
Hi,
In the gnome-window-properties (i.e. system->preferences->look and
feel-> windows), I have the box checked "Select windows when the mouse
moves over them". I have used this setting for years, even in other
window managers. Most recently, I find that focus is very often not in
the window over which the cursor is positioned. Certain applications
seem to be more troublesome than others.
Emacs, seems to quite often grab window focus on its own when the cursor
is over another window. Firefox, on the other hand seems to always lose
focus. Sometimes I have to repeated click to bring the focus back where
I want it. At first I suspected a bug in emacs, but I'm not entirely
sure now. I've since seen the behavior while running accessgrid.
I experience these problems with window focus on a Fedora 7 system as
well as on a Fedora 8 system running under vmware (and in full screen
mode, under the F7 system). The problem is much worse under F8. Both
systems have all of the current updates installed.
I also notice with firefox, a problem where sometimes, I cannot move or
resize the window in the vertical plane, only horizontally. I restart
firefox and then this works again. So far I have noticed this problem
only under F7.
Has anyone else seen either of these two behaviors?
Nataraj
16 years, 6 months
Re: fedora-list Digest, Vol 46, Issue 30
by Rambod Kamaei
Dear Fedora
What about Tacacs and Radius.
I need config file.
Best Regards,
Rambod Kamaei (PhD)
CCIE, CCNP, Linux Expert.
Tel: +98 21 22643500 to 9
Cell: +98 912 2185672
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
16 years, 6 months
Gtk / Nodoka errors x86_64.
by byrdca
I have noticed a few strange errors that seem related to Gtk and
Nodoka (examples below). These usually show up when I am starting an
application.
[EXAMPLE 1]
Gtk-WARNING **: Unable to locate theme engine in module_path: "nodoka"
[EXAMPLE 2]
/usr/share/themes/Nodoka/gtk-2.0/gtkrc:35: error: lexical error or
unexpected token, expected valid token
The line referenced above reads as follows:
GtkTreeView::odd_row_color = shade (0.929458256, @base_color)
Anyone have any idea what may be wrong?
Thanks in advance.
16 years, 6 months
RE: Grub clarification
by Dan Thurman
>Craig White wrote:
>just for S&G's
>
>try booting DVD or cd and going to rescue mode...
>
>once you get command line,
>
>chroot /mnt/sysimage
>grub-install /dev/sda
>exit
>exit
>
>and see if it boots
>
>Craig
>
Can I do this with F8-Live CD?
I tried in F1:
> grub-install /dev/sda
Probing devices to guess BIOS drives. This may take a long time.
Could not find device for /dev/mapper/livecd-rw
Could not find device for /dev/mapper/livecd-rw
Could not find device for /dev/mapper/livecd-rw
/dev/mapper/livecd-rw: Not found or not a block device.
Otherwise, I'll have to download and burn a rescue CD.
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.16.13/1165 - Release Date: 12/2/2007 8:34 PM
16 years, 6 months
libdvdnav
by J M
The libdvdnav just released in Fedora Updates
(libdvdnav-4.1.1-2.fc8.i386.rpm
)
causes the livna totem-xine and vlc packages to crash; is there a way to
tell yum to only look at livna for the package or do I have to exclude
it and look for updates manually from time to time?
Respectfully,
Jason
16 years, 6 months
RE: Grub clarification
by Dan Thurman
>From: fedora-list-bounces(a)redhat.com
>[mailto:fedora-list-bounces@redhat.com]On Behalf Of Tod Merley
>Sent: Monday, December 03, 2007 1:52 PM
>To: For users of Fedora
>Subject: Re: Grub clarification
>
>
>On Dec 3, 2007 10:53 AM, Daniel B. Thurman <dant(a)cdkkt.com> wrote:
>>
>> I am trying to install F8 onto my old system and having
>> trouble getting grub to find the drive. Here is the story.
>> [snip!]
>
>Hi Daniel B. Thurman!
>
>Two things come to mind:
>
>1. HW! Some drives and CMOS combinations just do not work. Check the
>CMOS client, that it sees the drive and that the drive is high on the
>boot list. Check to see that it is Master on the first IDE bus.
>Since it is an old system you might do well to load the defaults and
>edit the boot list (a "until you shut the power off" fix for a bad
>CMOS battery).
>
>2. Mis-placed or malformed Master Boot Record (MBR). The MBR needs to
>be the very first 512 bytes of the disk - loading GRUB on the second
>partition sounds strange although the MBR can be built to find GRUB
>anywhere. To help sort that one out I refer you to a Google search on
>"grub thestarman" and the GRUB manual.
>
>Good Hunting!
>
>Tod
>
Yeah, that is part of my original problem. I have several other disks
and they are attached to SCSI drives as well. The BIOS is a bit screwy
in try to determine the order of how disks are being read and which comes
first? The SCSI drives or the IDE drives? I still couldn't figure this
out. The system is: VA Linux Systems: 501. Pretty old.
When I first started with F8-Live, the screen showing custom partitions
displayed in order:
/dev/sda SCSI disk 1
/dev/sdb SCSI disk 2
/dev/sdc IDE-0 Primary disk 3
/dev/sdd IDE-0 Secondary disk 4
So in THAT case, I tried to install GRUB in /dev/sdc1 and choosed
the Advanced Options to set MBR @ /dev/sdc1. This did not work.
So - then I decided to remove ALL SCSI drives and in doing so, I
was left with:
/dev/sda IDE-0 Primary disk 1
/dev/sdb IDE-0 Secondary disk 2
So, I am focusing on this right now trying to get things going
but then again, I am still not able to get GRUB to get started
and all I see on a boot is a black screen with the word: GRUB
at the top-left corner of my monitor.
>fedora-list mailing list
>fedora-list(a)redhat.com
>To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.5.503 / Virus Database: 269.16.13/1165 - Release
>Date: 12/2/2007 8:34 PM
>
>
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.16.13/1165 - Release Date: 12/2/2007 8:34 PM
16 years, 6 months
