I would like to install F13 x64
I have seen the size difference in the partitions.
Question: Do I have to reformat my F12 installation or will upgrade
resize the boot partition?
I did not select a seperate Home partition when I installed F12. I
realize now I should have.
My / partition, that contains /var, has only 800 MB available and
I will certainly need more.
I have plenty of space in another partition and would like to use
that one for downloading rpm's tu upgrade from fedora 12 to 13.
As preupgrade.cli accept -c yum-xxx.conf, I tried that option including
but it didn't work as I got "not enough space..."
(Pleaso note that the size of my /boot is already 500 MB).
What is the recommended solution to use a filesystem outside
of /var for preupgrade and then upgrade?
I goggled a lot and only found this closed bug report
I would install the intel Fortran compiler of l_cprof_p_11.1.072.tgz on my
Fedora Core 12.
I went through the following comments step by step successfully to make the
compiler compatible with the FC12:
However, I have still the following problem:
Cannot determine which operating system is running. Supported operating
for this release include:
- Asianux* 3.0
- Debian* 5.0
- Fedora* 10 (IA-32 and Intel(R) 64 only)
- Red Hat Enterprise Linux* 3, 4, 5
- SGI ProPack* 5 (IA-64 and Intel(R) 64 only)
- SuSE Linux* Enterprise Server* 9, 10, 11
- Turbo Linux* 11
- Ubuntu* 9.04
Any idea to fix the above problem?
Thank you for your co-operation.
Saeid Jalali Asadabadi,
Department of Physics, Faculty of Science,
University of Isfahan (UI), Hezar Gerib Avenue,
81744 Isfahan, Iran.
Dep. of Phys. :+98-0311-793 2435
Office :+98-0311-793 4176
Fax No. :+98-0311-793 2409
Homepage : <http://sci.ui.ac.ir/~sjalali>
www : <http://www.ui.ac.ir> http://www.ui.ac.ir
When using NM (in Gnome) to configure a VPN (Sysco, which uses vpnc as the
backend) where does it store the VPN configuration settings?
Trying to find them so I can move them to a new F13 installation rather than
re-creating all of 'em.
Thanks in advance!
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------
Do you not know? Have you not heard?
The LORD is the everlasting God, the Creator of the ends of the earth.
He will not grow tired or weary, and his understanding no one can fathom.
----------------------------- Isaiah 40:28 (niv) -----------------------------
I have a desktop machine with 3 SATA drives. I have a separate OS on
each drive and use the graphical boot manager GAG
(gag.sourceforge.net) to boot into each of the 3 OS's. I had Fedora
11 installed on the second drive (sdb). Rather than try an update, I
did a clean install of FC13 from DVD in which I re-formatted my /
directory (sdb1) and left my separate /home partition unformatted.
Due to using GAG, I specified that the boot loader should be installed
on sdb1 (rather than sdb). This is how I've done it in the past and
done with the other distros I have installed on sda and sdc. However,
once the install finishes, the media is ejected, and I'm asked to
reboot, choosing to boot from sdb1 via GAG produced a hang
(essentially a black screen with a single _ or - in the upper left
hand corner of the screen.
I thought maybe I had to specify a dedicated /boot partition of at
least 512MB, so I performed the install again, this time specifying
sdb1 as /boot and sdb2 as / and to install the boot loader to sdb1
with sdb2 defaulting to the Fedora install. Same result.
The install media is verified as good. I next grabbed the FC13 Live
CD and performed an 'Install to Hard Disk' from that again specifying
that the boot loader be installed to sdb1 (/boot). This time, when
selecting to boot Fedora 13 after the initial installation reboot, the
screen is black and then the computer start the POST and reboots to
GAG (no hang like before, just an apparent failed boot and quickly
reboots the machine). No error messages seen in either case.
Any ideas on what may be going on here?
What is "nomodeset" SUPPOSED to do? I really do want to know, because I wonder
if "nomodeset" is ineffectual on my system, and that's why I can't get the
rpmfusion nVidia driver to work (it used to work on this same system under
I want to go with the nVidia driver because:
1. nouveau (in KDE) leaves me with a hideous multicolored (grey & black) taskbar
at the bottom of my display.
2. Whatever driver is defaulted to when nouveau won't run (vesa?) will boot
perfectly on my system, BUT it only displays at a maximum resolution of
1280x1024. 1920x1080 is the resolution I was running it at with this same
system, same monitor, same video card on Fedora 12.
So, I'd really like to know if my problem is because "nomodeset" is doing
nothing on my system...
Steven P. Ulrick
I looked for a component in bugzilla for abrt, and it isn't listed so
I'd like to know where I should file this bug report.
> May 27 13:42:16 dt01 kernel: epiphany: segfault at fffffffffffff7f0 ip 000000391f474b8c sp 00007fffdf2c4d90 error 4 in libc-2.11.1.so[391f400000+16f000]
> May 27 13:42:18 dt01 abrt: saved core dump of pid 9989 (/usr/bin/epiphany) to /var/cache/abrt/ccpp-1274992936-9989.new/coredump (54530048 bytes)
Notice the "error 4" part and that abrt captures a backtrace for it.
> May 28 01:08:43 dt01 kernel: tecnoballz: segfault at 10132ddf0 ip 000000000042f5e0 sp 00007fffe99b21f0 error 6 in tecnoballz[400000+68000]
Notice the "error 6" part and that abrt does not capture a backtrace for it.
The link above says that the error codes are processor dependent.
Maybe there is something generic that can determine whether to attempt
processing a backtrace.
Is this a kernel issue, abrt issue or both? Where should I file the bug report?
Fresh install f13 - fully updated.
As per usual on laptop - i ran
gconftool-2 --direct --config-source
xml:readwrite:/etc/gconf/gconf.xml.defaults --type bool --set
So that gdm does not present user list to the world.
Rebooted - gdm screen comes up - background is there - and lower bar
The box where I would put username / password is a thin vertical line
1 pixel wide ...it is impossible to login to gdm
reset to false and restart and its fine again.
known bug or is there a new way to configure gdm now ?
in F13, Anaconda seems to allow encrypted partitions ONLY if you use LVM.
If I set up the disk as simple partitions with no lvm/VG/raid, how can
I realize encrypted partitions or even whole disk?
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us -----------------------------
I can do all things through Christ
who strengthens me.
------------------------------ Philippians 4:13 -------------------------------
I created a user by the name test, and after doing with my testing was
going to delete the user using the following command, userdel and also
added '-f' for cleaning out the home without leaving any traces of
'test'. But the command says :
[root@xbox ~]# userdel -f test
userdel: user test is currently logged in
Then i noticed that a tab in terminal was open with the user logged in.
Closed the TAB and again tried to remove the user. And to irony the user
was already gone as now the command said :.
[root@xbox ~]# userdel -f test
userdel: user 'test' does not exist
Tried listing the files and all were there intact.
[root@xbox ~]# ll /home/test/
.bash_history .bash_profile .dbus/
firefox-3.6.4.tar.bz2 .gconfd/ .gnome2_private/
.bash_logout .bashrc firefox/
.gconf/ .gnome2/ .mozilla/
I'm totally lost that how is parameter working fully against what man
says about it, pert manual
This option forces the removal of the user account, even if
the user is still logged in. It also forces userdel to remove the user´s
home directory and mail spool, even if another user uses the same home
directory or if the mail spool is not owned by the specified user. If
USERGROUPS_ENAB is defined to yes in /etc/login.defs and if a group
exists with the same name as the deleted user, then this group will be
removed, even if it is still the primary group of another user.
Seems that there is some issue with the command parameter, what do you
say ? is there some issue or Am i wrong somewhere.
Linux user number: 490644
Open your doors.......It's time to look beyond Windows