Re: /var/log/messages question
by R. G. Newbury
> On Mon, 2011-05-30 at 18:36 -0400, Tom Horsley wrote:
>> > Just for curiosity, why has no one ever arranged to
>> > log something like "Hey! I'm booting the system again!"
>> > as the very first line in that goes to /var/log/messages
>> > when the system is booting?
> I used to do something like that back when I was still using another OS.
> I modified the bootup script to add my own entry at the beginning. You
> could do the same, I don't think the script gets changed by updates that
> often.
It is far easier to add: echo "Completed boot at `date`"
to the bottom of /etc/rc.d/rc.local
Then it does not matter whether the system is using the old method or
systemd and whether it is writing to 'messages' or boot.log.
R. Geoffrey Newbury
12 years, 10 months
F15: Follow-mouse focus and hacks for GNOME shell?
by Marco Guazzone
Didn't find a way to set this type of focus under GNOME shell.
Searching in the Web I've found these 2 hacks:
gconftool-2 -s /apps/metacity/general/focus_mode -t string sloppy
or
gconftool-2 -s /apps/metacity/general/focus_mode -t string mouse
Are they safe?
Further, is there a guide to "hack" my GNOME shell. It's really nice
but there's something I'd like to change, like focus mode and enable
workspace cycle (if possible)
Thanks!!
Best,
-- Marco
12 years, 10 months
ddclient in systemd
by Patrick O'Callaghan
Anyone have a recipe for running ddclient (updates dynamic DNS info)
from systemd? The current version is written for the classic init
system. Can I just install it that way?
poc
12 years, 10 months
Cannot Connect to Network since update NetworkManager
by 严晶涛
Hello,
I use yum update -y today, and it update NetworkManager,when I reboot
my Fedora 15,I can't connect to Network.
I open gnome-terminal, press these:
> su
> /etc/init.d/NetworkManager start
>
it shows cannot start it.
When I insert my install CD,and reinstall the old NetworkManager,I can
start NetworkManager,and can connect to Network,so what can I do,waiting for
next update?
12 years, 10 months
Was inn tested for F15
by Sam Varshavchik
Has anyone tested inn in F15. Bug 708627 suggests that it never was.
In addition to that bug, I think something keeps rm -rf-ing /var/run/news
every time I reboot, which will keep inn broken even after this bug gets
fixed. At least /var/run/news was missing after my first boot into F15, I
fixed all off the above, but after the next reboot it was gone again.
12 years, 10 months
F15: bluetooth not working
by Fernando Cassia
Hi there,
I'm using a Chinese Malata PC-91007 netbook (Atom N450, the works)
http://bit.ly/lzsaKD with F15.
Bluetooth doesn't work. There's a BT led that is ON (the system
provides keystrokes Fn-F1 to enable/disable webcam, Fn-F2 to
enable-disable Wifi, but no keystroke to enable-disable BT, so on
Windows that BT led remains ON all the time as well).
The BT is connected on the mobo via USB, if I remember correctly.
13d3:3250 is the vid/pid of the device, if I'm not mistaken...
lsusb gives:
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0402:5621 ALi Corp. M5621 High-Speed IDE Controller
Bus 001 Device 003: ID 148f:3070 Ralink Technology, Corp.
RT2870/RT3070 Wireless Adapter
Bus 005 Device 002: ID 13d3:3250 IMC Networks
Bus 001 Device 009: ID 0ac8:3450 Z-Star Microelectronics Corp.
However, on F15 the Gnome 3.0 BT icon shows "Bluetooth ON, visibily
OFF". Theres no way to bring it to "Visibility on", and first I need
to pair it with a Palm Centro smartphone.
If I click on "Bluetooth Settings" I get "Bluetooth OFF" "Visibility
OFF" and al options grayed out.
Thoughts? Comments?
FC
12 years, 10 months
Yum stopped working after F14 -> F15 upgrade
by Manish Kathuria
Hello,
I have upgraded from F14 to F15 using preupgrade and everything seems
to be okay except yum. Whenever I run yum, it terminates giving the
error:
Error: Cannot retrieve metalink for repository: updates. Please verify
its path and try again
The error message appeared for other repositories also. In order to
sort out the problem I have tried out the following:
1. Disabled livna, rpmfusion and other repositories.
2. Disabled ipv6
3. Created entries in /etc/hosts for mirror.fedoraproject.org
4. Reinstalled yum, fedora-release-15-1
However, none of this has solved the problem. DNS is working fine and
all other internet applications are able to resolve sites. Any
suggestions?
Thanks,
--
Manish Kathuria
12 years, 10 months
how to enable SPICE?
by Matias Kreder
Hi,
For me it looks like SPICE was coming with Fedora 15:
http://fedoraproject.org/wiki/Features/SpiceInVirtManager
but after upgrading and switching one of my VM's to Spice instead of VNC I get:
Error starting domain: internal error Process exited while reading
console log output: qemu: -spice
port=5900,addr=127.0.0.1,disable-ticketing: there is no option group
"spice"
spice is not supported by this qemu build.
I have tried both hypervisors "qemu" and "qemu-kvm".
virt-manager has support for SPICE, but our qemu/kvm didn't come with
spice? I upgraded from F14, probably something was not installed...
Regards
Matias
12 years, 10 months
R: Re: F15- IMPORTANT Network Manager
by antonio montagnani
>----Messaggio originale----
>Da: tkevans(a)tkevans.com
>Data: 31-mag-2011
14.53
>A: "Community support for Fedora users"<users(a)lists.fedoraproject.org>
>Ogg: Re: F15- IMPORTANT Network Manager
>
>On 05/31/2011 06:17 AM, Michael
Schwendt wrote:
>> On Sat, 28 May 2011 14:31:44 +0200, AM wrote:
>>
>>> This
morning updates of Network-Manager1.0899.3.git20110526 killed all
>>> networks,
no way to connect any more, I had to downgrade to previous
>>> versions
>>
>>
Apparently, there are major issues for users. Just look up the update
>> ticket
in bodhi and the bugzilla ticket(s).
>
>I had to remove /etc/sysconfig/network-
scripts/ifcfg-Auto* then re-start
>NetWorkManager. This solved the problem I
saw after pre-upgrade F14->F15.
>
>--
>Tim Evans, TKEvans.com, Inc. | 5
Chestnut Court
>UNIX System Admin Consulting | Owings Mills, MD 21117
>http://www.tkevans.com/ | 443-394-3864
>http://www.come-here.com/News/| tkevans(a)tkevans.com
>--
>users mailing
list
>users(a)lists.fedoraproject.org
>To unsubscribe or change subscription
options:
>https://admin.fedoraproject.org/mailman/listinfo/users>Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>
surprising that nobody removed package from repo, causing problems to
everybody updating!!!! and for a newbie can be a very big problem, unless
Fedora is for geek
12 years, 10 months