Is it just me??
I've noticed, on several machines (PC, laptop, netbook) that if
the machine has no connection, or thinks it has none, the gpk function
claims there are no updates; but if I doubt that and run yum update, it
may immediately get over a hundred -- or at least report a failure to
Couldn't gpk do the same??
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.
-----BEGIN PGP SIGNED MESSAGE-----
Hi LTSP/Fedora Community.
(1st let me say "Sorry for the X-Posting to multiple Lists")
I would like to take this opportunity to say that Myself and a friend
have stepped up and I will now take over trying to keep LTSP in Fedora
Current with the upstream.
@ the end of last week I was given access to the LTSP Package on Fedora.
I have the src of ltsp-5.2.4 and am in the process of getting this into
and .rpm for Fedora 13 & Fedora 14 (x86 & x86_64).
This is going to take a little bit of time to get this release into an
.rpm, but we hope to have this done within the next week or so...
I first need to get my head around how the current version is packaged
and then we should be able to get the new version packaged the same way
to try and make this all as seamless as possible.
Red Hat GLS Instructor EMEA
Red Hat UK Ltd
64 Baker Street
4th Floor, London, W1U 7DF
Mob: +44 7841 231160
Desk: +44 0207 009 4429 (Direct)
Tel: +44 1252 362709
Fax: +44 1252 548116
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Brendan Lane (Ireland), Matt Parson
(USA), Charlie Peters (USA)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
I there a way to test new GIMP 2.7/2.8 in Fedora? I looked in Rawhide
repos and I still see only 2.6x versions there. Any plans to put 2.7 in
Rawhide repost for testing purposes?
pratite me na twitteru - www.twitter.com/valentthttp://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic
I was wondering how one does it: I have been looking at the Preferences
-> Desktop but I can not find a way to have it take nothing as the
background. Previously, in F10,11,12, I recall that there was a button
somewhere which said no background. I can not find it here.
Thanks to Chris Smart, Peter Danenberg and others, I have been able to
install Fedora 12 as the sole O/S on my Macbook Air (first
However the wirless networking is not enabled.
I am following the instructions in
There was no wireless device shown in the network Configuration, so I
clicked New and added a device for hardware Apple Airport.
I also tried adding wireless device on the Hardware tab (eth0), but although
it allows me to do this, after I save and then reopen the Network
Configuration, the hardware only shows a device pan0 of Type Ethernet
(which was there from the start). It does appear on the Devices tab
(it didn't originally until I added it), but has staus of inactive,
and no means to activate it.
However, even after restarting the computer, the wireless icon on the
panel says there are no network devices available.
So I tried removing the device from control by NetworkManager, and
activated it manually. But then I get:
Device eth0 does seem to be present, delaying initalization.
What do I need to do?
On 25 April 2010 19:47, Alan Pevec <apevec gmail.com> wrote:
> On Sat, Apr 24, 2010 at 4:38 PM, Valent Turkovic
> <valent.turkovic gmail.com> wrote:
>> how to make Fedora 12 and Fedora 13 LiveCD/DVD that is btrfs formated
>> and not ext4?
>> What options need to be enables in kicstart file so that
>> livecd-creator makes btrfs iso images?
> Didn't try it, but should be enough to change fstype in fedora-live-base.ks
>> part / --size 3072 --fstype ext4
A quick scan reveals adjusting fstype will not be enuff, btrfs uses
different userspace tools from ext "btrfs-progs", so livecd-tools
will need a patch.
Kernel 2.6.35 now supports
The device will be wlan0 instead of ra0
I just downloaded
and built it and booted it.
It found my Ralink 2860 based mini-pci and
all is super-well.
You will need to modify your /etc/sysconfig/wpa_supplicant
and replace ra0 with wlan0
Once you do that, you will need to System->Administration->Network
and activate wlan0, and save it.
That should create the ifcfg-wlan0 file in /etc/sysconfig/network-scripts
and should also create hard links to it in /etc/sysconfig/networking/devices
and in /etc/sysconfig/networking/profiles/default
(unless of course these links are no longer needed).
If you had set up your wifi with a fixed ip address, you will need to
set that up too.
Once done, then
sudo ifup wlan0
and you are up and running.
I have so far discovered that these rtx00 drivers are driving
the card much much better than ralinktech's own driver.
For example, the signal to noise ratio is increased by a factor of 10!!!
No kidding!!! Factor of 10!
i.e. signal strength went from around 5 or 6 to 60!!!
Google recently announced the availability of GMail Video Chat for
linux!, Unfortunately the sad part is that the released only for
Ubuntu and Debian based systems!
So the thing is we have a .deb. Is there a way we could get the .rpm
for installation? anyone have this convert to rpm?
This is in regard to the issue that, when Linux is hibernated, upon
reboot the thaw starts immediately and the grub menu is not presented.
I am now absolutely convinced this is not a BIOS issue, it is a kernel
or boot loader issue.
I worked around it by adding a level of indirection to the boot process.
To do this requires that you have at least one Linux partition that is
not / or /boot.
The basic idea is that Linux is booted with a chainloader, same as
Windows. So the main grub menu gives you a choice of Linux or Windows,
and both are implemented with "chainloader +1" stanzas. It works, but I
don't recommend trying this unless you are fairly familiar with how the
boot loader works, and are comfortable reinstalling the boot loader from
a rescue CD/DVD if something goes wrong.
The high-level instructions go like this:
1) In your extra Linux partition, create "boot" and "boot/grub"
2) Copy the contents of /boot/grub to this new grub directory.
3) Edit the boot/grub/grub.conf file in this new directory so that
Windows and Linux are presented as "chainloader +1" stanzas.
4) Install grub in the master boot record, pointing to this partition
5) Install grub in the first sector of your root partition, with the
usual kernel choices.
When this is done, at boot time you get a choice of Linux or Windows. If
you select Linux, the second boot loader comes up with the usual choice
of kernels. If Linux is hibernated, you can then boot and run Windows
just fine (my Windows install doesn't have a hibernate option so I
wasn't able to test hibernating Windows in this scenario). If you boot
again and select Linux, instead of getting the choice of kernels, it
immediately resumes the hibernated image. This is how I *want* it to
work, so I have left it this way.
Suppose you have this:
/dev/sda2 Linux root
/dev/sda3 Linux /local
Then /boot/grub gets copied to /local/boot/grub, then
edit /local/boot/grub/grub.conf so that you have something like this:
grub> root (hd0,2)
grub> setup (hd0)
This loads the master boot record that points to /dev/sda2, the
Now edit /boot/grub/grub.conf and remove the Windows stanza (you don't
need it here any more). Then run:
grub> root (hd0,1)
grub> setup (hd0,1)
This loads grub into the first sector of the Linux root partition,
pointing at that partition and presenting the usual choice of kernels.
This has worked great for me. I can now hibernate Linux, boot into
Windows, and later resume from the hibernated Linux image.