Re: Cleanest way to upgrade F7 to F9 (when the time comes)
by McGuffey, David C.
>
> On Mon, 28 Apr 2008 17:11:53 -0400
> "McGuffey, David C." <DAVID.C.MCGUFFEY(a)saic.com> wrote:
>
> > What is the cleanest way to upgrade from version to version (e.g.,
F7 to
> > F9 (when it arrives)?
>
> Make a backup and do a CD or DVD upgrade. You shouldn't need to use
the
> backup but its always handy for "worst case" situations.
>
> You can do live upgrading but that is a much less tested path and best
> done with a bit of experience.
>
> > Will I run into any conflicts if I do a fresh install of F9, create
the
> > user accounts and groups (keeping the same uid and gid), untar the
home
> > folders, and pull back the key config files?
>
> Probably not.
>
> > When I tar the home folders, should I preserve the selinux context?
>
> If you've not set any specific ones then forcing a relabel should be
> quite sufficient.
>
> Alan
>
Thanks for the response.
Other than adding selinux attributes to the mounted partition that is
shared out by samba, I haven't made any selinux changes.
I'll tidy up all the Windoze files onto the drive shared by samba,
dismount it, save any other data to the USB disk, and do a DVD upgrade.
If something goes wrong, I'll have the data to restore.
There is actually plenty of space on the samba share (an ex3 partition),
that I may just tar the user and config data I want to save there, and
not worry about the USB disk.
Dave McGuffey
Principal Information System Security Engineer // NSA-IEM, NSA-IAM
SAIC, IISBU, Columbia, MD
16 years
re-enabling hyperthreading
by Michael Hennebry
Way back when I was running FC3, I used the BIOS
to disable hyperthreading in my Pentium 4.
It stopped system crashes that,
IIRC, I was told had something to do with my LCD monitor.
I never understood the problem or the solution.
I recently installed FC8.
At the time, hyperthreading was turned off.
Assuming that the previous problems are fixed,
is it safe to re-enable hyperthreading on a
system that was installed with it turned off?
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"Those parts of the system that you can hit with a hammer (not advised)
are called Hardware; those program instructions that you can only
curse at are called Software."
16 years
Re: backup
by Bradley
Tom Holroyd wrote:
> Show of hands: compress backups? Or 1:1 copy.
>
I always do a 1:1 backup. I tried doing compressed and found that
sometimes the compressed file got corrupted and plus there wasn't that
big of a space savings for me. The other problem is that if I needed a
backed up file, I could just access it directly to get what I needed.
Bradley
16 years
Problem loading Fedora
by Darrick Fitzgerald Ward
I am trying to load fedor 6 on my Dell Dimension 4300 and it keeps getting stuck at Formating/File System. I am trying to understand how to get pass this or if there is something I need to do.
I know that fedora 6 is old but I could only find fedora 8 on dvd and my pc will not boot from a dvd. I used to have windows xp on this pc but it crashed and I no longer have any of my pc disc or windows disc after a move I made a year ago.
I am a novice but I am smart and hopefully can start using linux and learn quickly.
Thank you,
16 years
Lost fc7 boot loader:
by Vincent
Hi,
Is there any way to restore the boot loader? I made dome error, reinstalled the windows XP without first back up all the data in fedora.
I have an HP Pavilion zv6000 with AMD athlon 64, 80 GB and 1GB of memory dual boot with windows and Fedora 7 (fc8 will not install in this computer, I also posted this problem but I did not get any answer) the HD is partition at 40GB each. I try to restore using fc7 original disk used for installation but it does not restore the boot loader.
I will greately appresciate some help if there is a way.
Thank you in advance
16 years
NetworkManager-0.7.0-0.6.7: Something really improved. Do you see it too?
by Paul Johnson
When yum installed this yesterday,
NetworkManager-0.7.0-0.6.7.svn3370.fc8
I didn't really expect much change.
But there is a significant improvement in 2 areas. I wasn't looking
for this, but the change was so substantial it was hard to miss.
First, in locations where it used to take a long time for the system
to get an IP address from a router--some coffee shops have been
trouble for unknown reasons--now i get an IP address right away.
Second, on my home network, where I did not have trouble getting an IP
number, the wireless seems much faster. I'd say that running X11
applications on my home server and displaying to the laptop via ssh
is about 40% faster.
This system is a Dell Latitude D820 with the Intel IPW3945. I'm using
the kernel's iwl3945 driver, as I have been for about 6 weeks. The
kernel has not been updated for a week and a half or so, the version
is kernel-2.6.24.4-64.fc8.
In case you work on NetworkManager, I say "good job." In case you
say, "what the hell is he talking about," here is an example from
messages from last week. I'm trying to join an open nonencrypted
network "sbhsd Yello Sub", which is the world's greatest sandwich
restaurant. The NetworkManager sees it, but it gives up trying to get
an IP, and then it trys to attach me to other routers, one that calls
itself "linksys" and one from a local pay-for-service network
"Freenet". The Freenet gives IP numbers, but you can't do any work
until you log in with a browser and give a password.
Apr 20 16:38:30 pols126 NetworkManager: <info> Activating device wlan0
Apr 20 16:38:30 pols126 NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) scheduled...
Apr 20 16:38:30 pols126 NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) started...
Apr 20 16:38:30 pols126 NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) scheduled...
Apr 20 16:38:30 pols126 NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) complete.
Apr 20 16:38:30 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 2 -> 0
Apr 20 16:38:30 pols126 NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) starting...
Apr 20 16:38:30 pols126 NetworkManager: <info> Activation
(wlan0/wireless): connection 'Auto sbhsd Yello Sub' requires no
security. No secrets needed.
Apr 20 16:38:30 pols126 NetworkManager: <info> Config: added 'ssid'
value 'sbhsd Yello Sub'
Apr 20 16:38:30 pols126 NetworkManager: <info> Config: added
'key_mgmt' value 'NONE'
Apr 20 16:38:30 pols126 NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) complete.
Apr 20 16:38:30 pols126 NetworkManager: <info> Config: set interface
ap_scan to 1
Apr 20 16:38:30 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 0 -> 2
Apr 20 16:38:33 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 2 -> 3
Apr 20 16:38:48 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 3 -> 0
Apr 20 16:38:48 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 0 -> 2
Apr 20 16:38:49 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 2 -> 3
Apr 20 16:38:55 pols126 NetworkManager: <info> Activation
(wlan0/wireless): association took too long, failing activation.
Apr 20 16:38:55 pols126 NetworkManager: <info> Activation (wlan0)
failed for access point (sbhsd Yello Sub)
Apr 20 16:38:55 pols126 NetworkManager: <info> Marking connection
'Auto sbhsd Yello Sub' invalid.
Apr 20 16:38:55 pols126 NetworkManager: <info> Activation (wlan0) failed.
Apr 20 16:38:55 pols126 NetworkManager: <info> Deactivating device wlan0.
Apr 20 16:38:55 pols126 NetworkManager: <WARN> remove_network_cb():
Couldn't remove network from supplicant interface: The requested
network does not exist..
Apr 20 16:38:55 pols126 NetworkManager: <info> SWITCH: no current
connection, found better connection 'Auto linksys (wlan0)'.
Apr 20 16:38:55 pols126 NetworkManager: <info> Activating device wlan0
Apr 20 16:38:55 pols126 NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) scheduled...
Apr 20 16:38:55 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 3 -> 0
Apr 20 16:38:55 pols126 NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) started...
Apr 20 16:38:55 pols126 NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) scheduled...
Apr 20 16:38:55 pols126 NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) complete.
Apr 20 16:38:55 pols126 NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) starting...
Apr 20 16:38:55 pols126 NetworkManager: <info> Activation
(wlan0/wireless): connection 'Auto linksys' requires no security. No
secrets needed.
Apr 20 16:38:55 pols126 NetworkManager: <info> Config: added 'ssid'
value 'linksys'
Apr 20 16:38:55 pols126 NetworkManager: <info> Config: added
'key_mgmt' value 'NONE'
Apr 20 16:38:55 pols126 NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) complete.
Apr 20 16:38:55 pols126 NetworkManager: <info> Config: set interface
ap_scan to 1
Apr 20 16:38:55 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 0 -> 2
Apr 20 16:39:04 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 2 -> 0
Apr 20 16:39:04 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 0 -> 2
Apr 20 16:39:20 pols126 NetworkManager: <info> Activation
(wlan0/wireless): association took too long, failing activation.
Apr 20 16:39:20 pols126 NetworkManager: <info> Activation (wlan0)
failed for access point (linksys)
Apr 20 16:39:20 pols126 NetworkManager: <info> Marking connection
'Auto linksys' invalid.
Apr 20 16:39:20 pols126 NetworkManager: <info> Activation (wlan0) failed.
Apr 20 16:39:20 pols126 NetworkManager: <info> Deactivating device wlan0.
Apr 20 16:39:20 pols126 NetworkManager: <WARN> remove_network_cb():
Couldn't remove network from supplicant interface: The requested
network does not exist..
Apr 20 16:39:20 pols126 NetworkManager: <info> SWITCH: no current
connection, found better connection 'Auto sbhsd Yello Sub (wlan0)'.
Apr 20 16:39:20 pols126 NetworkManager: <info> Activating device wlan0
Apr 20 16:39:20 pols126 NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) scheduled...
Apr 20 16:39:20 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 2 -> 0
Apr 20 16:39:20 pols126 NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) started...
Apr 20 16:39:20 pols126 NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) schedule
Apr 20 16:39:20 pols126 NetworkManager: <info> Activation
(wlan0/wireless): connection 'Auto sbhsd Yello Sub' requires no
security. No secrets needed.
Apr 20 16:39:20 pols126 NetworkManager: <info> Config: added 'ssid'
value 'sbhsd Yello Sub'
Apr 20 16:39:20 pols126 NetworkManager: <info> Config: added
'key_mgmt' value 'NONE'
Apr 20 16:39:20 pols126 NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) complete.
Apr 20 16:39:20 pols126 NetworkManager: <info> Config: set interface
ap_scan to 1
Apr 20 16:39:20 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 0 -> 2
Apr 20 16:39:23 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 2 -> 3
Apr 20 16:39:38 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 3 -> 0
Apr 20 16:39:38 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 0 -> 2
Apr 20 16:39:39 pols126 NetworkManager: <info> (wlan0) Supplicant
interface state change: 2 -> 3
Apr 20 16:39:45 pols126 NetworkManager: <info> Activation
(wlan0/wireless): association took too long, failing activation.
Apr 20 16:39:45 pols126 NetworkManager: <info> Activation (wlan0)
failed for access point (sbhsd Yello Sub)
Apr 20 16:39:45 pols126 NetworkManager: <info> Marking connection
'Auto sbhsd Yello Sub' invalid.
Apr 20 16:39:45 pols126 NetworkManager: <info> Activation (wlan0) failed.
Apr 20 16:39:45 pols126 NetworkManager: <info> Deactivating device wlan0.
Apr 20 16:39:45 pols126 NetworkManager: <WARN> remove_network_cb():
Couldn't remove network from supplicant interface: The requested
network does not exist..
Apr 20 16:39:45 pols126 NetworkManager: <info> SWITCH: no current
connection, found better connection 'Auto Freenet (wlan0)'.
Apr 20 16:39:45 pols126 NetworkManager: <info> Activating device wlan0
--
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas
16 years
Re: Re: where can i find the default keyrings???
by Richard England
>From: Bradley Pursley <pursley001(a)comcast.net>
>Date: 2008/04/29 Tue PM 12:14:36 CDT
>To: For users of Fedora <fedora-list(a)redhat.com>
>Subject: Re: where can i find the default keyrings???
>max bianco wrote:
>> On Tue, Apr 29, 2008 at 12:24 PM, Bradley Pursley
>> <pursley001(a)comcast.net> wrote:
>>
>>>
>>>>> You still didn't answer the original question: "Where are the keyring
>>>>> files?"
>>>>>
>>>>>
>>>>>
>>>>>
>>>> Your not paying attention. The original post asked where changes could
>>>> be made and I answered that question. Keyring manager is where a
>>>> legitimate user makes his/her changes. If your foolish enough to
>>>> forget all your passwords and depend on the keyring manager to
>>>> remember them all for you, well that's another issue all together. In
>>>> either case if evolution asks for the email password and you provide
>>>> it then it will work without needing to consult the keyring manager.
>>>> It sounds to me like someone is phishing.....
>>>>
>>>> Max
>>>>
>>>>
>>>>
>>> Your response was rude and very presuming and I take offense to it.
>>> Here is why I need to know where the files are:
>>>
>>> 1) I am the sole administrator for both machines that I have.
>>> 2) I am the sole person who set them up and configured them but never set
>>> up any "keyring" passwords.
>>> 3) The system started prompting me for the default keyring password, which
>>> was never set up, to save the network key for a wireless connection.
>>> 4) No password ever used on the system works for the so-called "default
>>> keyring password".
>>> 5) As such, I believe that the keyring file is corrupted and needs to be
>>> deleted and recreated, which means I need to know where they are.
>>>
>>>
>>>
>> You can take offense if you like, if you have the keyring manager
>> installed, it is a simple matter to delete the keyrings, if you have
>> even bothered to try, but it doesn't sound like it. Editing corrupted
>> files by hand, assuming they will even open is not likely to work,
>> IMHO. However google may enlighten you like it did me as to their
>> location if you take the time to use it that is. In addition you are
>> not the author of the original post as near as I can tell.
>>
>> Max
>(I'm going to ignore any further personal attacks)
>
>Okay, I'll lay it out for you just so you'll stop making those false
>assumptions and yes, I was not the original author but was hoping for an
>answer to my problem.
>
>The keyring manager will not work, nor any other program that uses the
>keyrings, because it requires a password, which I don't have, for a
>"default" keyring. This all started when I started using Network
>Manager to connect via a wireless network and it started asking for a
>password so that it could save the network key required to connect.
>Since I don't have they keyring password it won't save the network key
>and now prompts for it, along with the keyring password, every time you
>log into the system. Mind you, this is not a critical problem but is a
>major nuisance since the network key is a secured 25 digit hexidecimal
>number.
>
>Now, my options appear to be to change a setting unknown to me, delete
>the files and recreate them or find some utility to "fix" the files.
>Granted, I am not against having to use some kind of option to
>re-install the software and overwrite the configuration files since
>nothing has been permanently saved.
>
>Bradley
>
Okay, children. Tame it down or you both get a time out!
Delete /home/YOUR NAME/.gnome2/keyrings/default.keyring
Gnome/network manager will recreate the default.keyring with correct permisssions next time you connect. Enter the same password as you login password and I believe it will not prompt you in the future.
~~R
16 years
USB error #62
by Ric Moore
During boot, I keep getting this error message: "USB 1-2: device not
accepting address 2, error -62"
Since I'm having problems getting my LG phone to connect via USB cable,
and it occupies a zone 2 address, is this part of the problem?? Thanks,
Ric
--
================================================
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256 Sign up at: http://counter.li.org/
http://www.sourceforge.net/projects/oar
http://www.wayward4now.net <---down4now too
================================================
16 years
Eth0 not active at startup
by Bob Latham
Hi,
I am almost a complete newbie to Linux and I apologise for asking about
something very dumb right away.
I want to use Fedora to run a couple of network sockets on two networks
with Samba shares and a simple FTP server - that's all.
I'm having problems trying to set a static IP address on eth0. I can get
it to work but it has to be "activated" by hand each time I start the
machine. There is an option "Activate device when computer starts" but
although ticked, it appears to do nothing.
What am I doing wrong?
Cheers,
Bob.
16 years
Transmission Q, That is if I can change the subject here folks
by Gene Heskett
Greetings;
I just fired up 'transmission' because someone has managed to royally screw up
ktorrents screen handling. Its working, but even though I checked the 'ask
where to put it" box, it ignored it, and it is still putting it in my home
directory instead of the directory I normally download this stuff to. I can
fix that after its done, but why should I have to?
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Rules for Academic Deans:
(1) HIDE!!!!
(2) If they find you, LIE!!!!
-- Father Damian C. Fandal
16 years