Partitioning in anaconda
by Frode Petersen
Hi. I've searched release notes, bugzilla and news archives for an
answer to this, but haven't found one. I have found one other query on
fedoraforum, but no solution. (
http://forums.fedoraforum.org/archive/index.php/t-259666.html )
I started installing f14 on a machine (P4, 2GB ram, 30GB free on 75GB
HD, 1st partition is WinXP). I use manual setup of partitions, as I have
always done, planning to use the following approximate scheme:
sda1 - primary - ntfs - 45 GB - winXP
sda2 - primary - ext2 - 200 MB - /boot
sda5 - extended - ext4 - 7 GB - /home
sda6 - extended - swap - 2 GB - [swap]
sda7 - extended - ext4 - 20 GB - /
It seems that anaconda overrides my choice of not ticking the 'create
primary partition' box in the 'add partition' dialog, making all three
first partitions created primary. This means that both /boot and either
/home or / would be primary partitions.
Questions:
- 'Olde' knowledge says that only one primary partition can be visible
to the system at one time. Is this not longer true?
- If still true, the system wouldn't be able to see the home or root
partition, would it?
- If the behaviour is by design, what is the reasoning behind it? Is
it better than letting the admin decide?
I haven't yet tried partitioning with fdisk first, but will try to do
that tomorrow. Hopefully it will be a usable workaround.
Have a nice weekend,
Frode Petersen
12 years, 9 months
About Fedora bugs
by Bill Davidsen
We were talking the other day, people were mentioning the bugs they got
back from bugzilla recently marked as:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
People were saying that the same problem got the same message a year
ago, but it said "Fedora 11" that time. So I have a suggestion, if no
one in the support group looks at a bug in 180 days, close it with a
DONTCARE status and tell the submitter that no one could be bothered to
even look at the bug in half a year. And do the same thing if a bug sits
in NEEDINFO for six months, if no one responds in that length of time
they probably no longer care.
Users have this unrealistic view that there is a queue of bugs and they
get fixed in the order submitted. The truth is that if you don't hear in
a month you probably won't ever hear unless someone else reports it and
triage catches that they are dups. That doesn't always happen, one of
the bugs I had with FC10 was reported as WONTFIX at EOL, and when I
tried to reproduce it found that it had been fixed months before and no
one bothered to update the bug.
Finally, if someone reports a bug in an app, and the tester finds that
it's supposed to work that way, if the documentation says it works some
other way don't change it to NOTABUG, change it to a documentation bug.
If the conflicting documentation is mentioned in the bug report, take a
minute and get it resolved. Please?
My occasional rant when I look at all the time I wasted reporting bugs...
--
Bill Davidsen<davidsen(a)tmr.com>
We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination. -me, 2010
12 years, 9 months
howto download i686 kernel on x86_64 box
by Mike Wright
Hi all,
I'm running f14-x86_64 but have a need for a f14.i686 kernel package
(kernel-2.6.35.6-45.fc14.i686). I'd also like to unpack it but not into
its default locations.
That leaves me with two questions:
How do I download it without installing it?
How do I unpack it into a safe location (such as /test)?
Been fiddling with yum and had no luck.
TIA,
Mike Wright
12 years, 9 months
updating initrd.img file of the pxe installation files
by Eric Doutreleau
Hi
i m trying to install f13 on a computer with cobbler and pxe but when i
boot the network card is not detected.
i would like to update the initrd image file with updated modules
Does anybody have a pointer on how to do that?
Thanks in advance for any help
--
Eric Doutreleau
12 years, 9 months
grub on raid1 cannot mount filesystem
by Pavel Lisy
Hello
I've found strange problem in new Fedora 15. I suppose it should work.
It's maybe fdisk or grub problem.
Normaly I have this (working) multiboot solution on my home PC:
On first small (100MB) partition are grub1 files only with this config
(grub is installed to MBR):
--- cut ---
title Fedora 15
root (hd0,2)
chainloader +1
title Fedora 14
root (hd0,4)
chainloader +1
title Ubuntu
root (hd0,5)
chainloader +1
--- cut ---
Grub of linux distributions is installed into their partitions
I want make the same on mirrored environment
2 HD in mirror (raid1):
size id OS/SW FS
1. part 200MB fd grub ext4
2. part 8GB 82 SWAP swap
3. part 10 GB fd fedora 15 ext4
4. part extended
5. part 10 GB fd fedora 14 ext4
6. part 10 GB fd ubuntu ext4
...
last part rest. of disk - LVM
I've installed Fedora 15 on
/dev/md0 (/dev/sda1,/dev/sdb1) /boot
/dev/md1 (/dev/sda3,/dev/sdb3) /
grub was in MBR and everything worked.
THIS WORKS:
grub> root (hd0,0)
grub> setup (hd0)
When I want put grub of Fedora 15 to start of /dev/sda3 grub is
complaining:
THIS DOESN'T WORK:
grub> root (hd0,2)
grub> setup (hd0,2)
Error 17: cannot mount selected partition
Without mirror (raid1) it works. With raid1 it works only on first
partition. Can you explain me why?
Thanks in advance
Pavel
12 years, 9 months
Wine fonts makes html rendering on firefox and chrome much worse
by Fernando Lozano
Hi there,
Please someone help me find out how to solve this problem: for some weeks I
have been experiencing problems with fonts on Firefox and Chrome when
acessing two different webmail systems. At first I though the problem was
caused by remi RPMs I used to install Firefox 4 on Fedora 14. I installed
Fedora 15 and everything was fine for a while, and then fonts became
strange again. When firefox started having font problems, Google Chrome
started also.
The problem was: Bold fonts and regular fonts look almost the same. Bold
fonts had a wider average character width, but were not thicker.
So I got another computer, installed Fedora 15 from scratch, and compared
the results. Everything fine. Updated all packages, including rpmfusion
ones. Also fine.
Then I noticed the new system was missing some packages I use, I guess they
come from rpmfusion: gnome-mplayer and wine. After installing those, the
font problem in Firefox and Chrome was back again.
But this time I saved the output of rpm -qa at each step, then I compared
the latest working state with the one that wasn't. I noticed there are a
number of wine-*-fonts packages, and removed then (I also had to remove
wine itself). Problem solved!
Can anyone explain why either wine itself (or wine fonts) interfere with
web browser page rendering?
And how can I re-install wine without messing up with web page fonts?
[]s, Fernando Lozano
12 years, 9 months
chown ??
by Mickey
On a backup drive /mnt/home/tom , I want to change all directories and
files in tom to owner:tom .
The drive is mounted but from /home the command chown -R tom tom is not
changing the directories and files to owner, tom .
Command chown -R tom:tom tom won't change the ownership in the
directories and files in
directory tom .
12 years, 9 months
named shows different results
by fedora
Hi listers
I have a very curious problem here:
I changed some CNAME entries in the named for a specific domain this
morning.
when i now (from an internal workstation) do a
dig @nameserver cname
i get a different answer, depending on whether @nameserver points to the
local address 192.168.... or on the public ip address 212.90..... of the
nameserver
in the first case, named returns the old (incorrect) address of cname.
in the second case, named returns the new (correct) address of cname.
when i let @nameserver point to the secondary nameserver, the above
difference does not show up, it always returns the correct address.
from the outside world, the new (correct) value is always returned.
what could the problem be and how to avoid it?
thanks in advance
suomi
12 years, 9 months
Upgrade of F13 to F14 via yum
by Paolo Galtieri
Yesterday I upgraded a F13 system to F14 using yum upgrade. It took all
day (and part of the night) but when I checked this morning the system
had rebooted and everything looked fine. Until I logged in. Then I
noticed that named now consumes >100% cpu (the system is a dual
processor Intel(R) Pentium(R) 4 CPU 2.80GHz). There is nothing obvious
in the logs that I could find that would explain this. This system is
my DNS server and was working fine under F13. When I run strace named
is spewing the following messages:
[pid 5329] futex(0xb784b04c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb784b048,
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} <unfinished ...>
[pid 5330] <... futex resumed> ) = 0
[pid 5330] futex(0xb784b018, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid 5329] <... futex resumed> ) = 1
[pid 5329] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid 5330] <... futex resumed> ) = 0
[pid 5330] gettimeofday({1309450987, 273490}, NULL) = 0
[pid 5330] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 5330] clock_gettime(CLOCK_REALTIME, {1309450987, 273721365}) = 0
[pid 5330] futex(0xb784b04c, FUTEX_WAIT_PRIVATE, 1490757, {1142,
153144635} <unfinished ...>
[pid 5329] <... futex resumed> ) = 1
[pid 5329] gettimeofday({1309450987, 273973}, NULL) = 0
[pid 5329] gettimeofday({1309450987, 274119}, NULL) = 0
[pid 5329] futex(0xb784b04c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb784b048,
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} <unfinished ...>
[pid 5330] <... futex resumed> ) = 0
[pid 5330] futex(0xb784b018, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid 5329] <... futex resumed> ) = 1
[pid 5329] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid 5330] <... futex resumed> ) = 0
[pid 5330] gettimeofday({1309450987, 274655}, NULL) = 0
[pid 5330] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 5330] clock_gettime(CLOCK_REALTIME, {1309450987, 274883103}) = 0
[pid 5330] futex(0xb784b04c, FUTEX_WAIT_PRIVATE, 1490759, {1142,
151982897} <unfinished ...>
[pid 5329] <... futex resumed> ) = 1
[pid 5329] gettimeofday({1309450987, 275135}, NULL) = 0
[pid 5329] gettimeofday({1309450987, 275250}, NULL) = 0
[pid 5329] gettimeofday({1309450987, 275367}, NULL) = 0
[pid 5329] futex(0xb784b04c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb784b048,
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} <unfinished ...>
[pid 5330] <... futex resumed> ) = 0
[pid 5330] futex(0xb784b018, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid 5329] <... futex resumed> ) = 1
[pid 5329] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid 5330] <... futex resumed> ) = 0
[pid 5330] gettimeofday({1309450987, 275914}, NULL) = 0
[pid 5330] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 5330] clock_gettime(CLOCK_REALTIME, {1309450987, 276147526}) = 0
[pid 5330] futex(0xb784b04c, FUTEX_WAIT_PRIVATE, 1490761, {1142,
150718474} <unfinished ...>
[pid 5329] <... futex resumed> ) = 1
[pid 5329] gettimeofday({1309450987, 276417}, NULL) = 0
[pid 5329] gettimeofday({1309450987, 276536}, NULL) = 0
[pid 5329] futex(0xb784b04c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb784b048,
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} <unfinished ...>
[pid 5330] <... futex resumed> ) = 0
[pid 5330] futex(0xb784b018, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid 5329] <... futex resumed> ) = 1
[pid 5329] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid 5330] <... futex resumed> ) = 0
[pid 5330] gettimeofday({1309450987, 277056}, NULL) = 0
[pid 5330] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 5330] clock_gettime(CLOCK_REALTIME, {1309450987, 277286204}) = 0
[pid 5330] futex(0xb784b04c, FUTEX_WAIT_PRIVATE, 1490763, {1142,
149579796} <unfinished ...>
[pid 5329] <... futex resumed> ) = 1
[pid 5329] gettimeofday({1309450987, 277553}, NULL) = 0
[pid 5329] gettimeofday({1309450987, 277669}, NULL) = 0
[pid 5329] gettimeofday({1309450987, 277785}, NULL) = 0
[pid 5329] futex(0xb784b04c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb784b048,
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} <unfinished ...>
[pid 5330] <... futex resumed> ) = 0
[pid 5330] futex(0xb784b018, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid 5329] <... futex resumed> ) = 1
[pid 5329] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid 5330] <... futex resumed> ) = 0
[pid 5330] gettimeofday({1309450987, 278305}, NULL) = 0
[pid 5330] futex(0xb784b018, FUTEX_WAKE_PRIVATE, 1) = 0
Has anyone else had issues with named after an upgrade?
Another issue I encountered has to do with Selinux alerts. Here's one
of the alerts:
SELinux is preventing /usr/bin/updatedb from getattr access on the
directory /etc/udev/rules.d
The permissions on the directory on the upgraded system is:
drwxr-xr-x. root root system_u:object_r:udev_var_run_t:s0 /etc/udev/rules.d/
On one of my other F14 system it's:
drwxr-xr-x. root root system_u:object_r:udev_rules_t:s0 /etc/udev/rules.d/
Note that they are not the same. I also get the following alerts:
SELinux is preventing /bin/mount from write access on the directory
/var/named
drwxr-x---. root named system_u:object_r:named_zone_t:s0 /var/named
SELinux is preventing /bin/mount from write access on the directory
/usr/lib/bind
Another issue I'm having on all my Linux systems connected to my KVM
switch. The problem is I get constant USB disconnects/reconnects. They
occur about every 30 seconds on average. I don't know if this indicates
the hardware is going bad or something else.
Any thoughts are appreciated.
Thanks,
Paolo
12 years, 9 months