request for changes to LVM naming for FC7
by Patrick Bakker
For FC7 would it be possible to give volume groups more descriptive names?
For instance instead of VolGroup00 could the volume group anaconda creates
be called FedoraCore7?
Also, is it at all possible for smarts to be built-in so that more than 1
version of Fedora (and ideally other distributions as well) could all share
the same boot partition? Two issues I can think of:
- As long as everybody includes a distribution prefix in the vmlinuz,
initrd ... like .fc6 there should not be any overlap of kernels.
- It looks like Fedora installs grub's configuration in /etc which makes it
particular to Fedora. Is it possible to move it into /boot as well so that
the same grub
can be modified by any distribution?
My particular scenario is that I usually try to run the previous FC and the
new FC in parallel. Occassionally I add a 3rd experimental distribution in
the middle. Then I have separate paritions for data that does not change for
any distribution (ie. music, photos and maybe home if I dare at somepoint).
For example:
FC5 partitions, FC6 partitions, Ubuntu, Data
With FC7:
FC7 paritions, FC6 partitions, Whatever, Data
With FC8:
FC7 partitions, FC8 partitions, Whatever, Data
Every distribution install assumes that it is the only OS on disk in terms
of monopolizing the MBR with its variant of grub. This makes keeping track
of all of the paritions confusing.
Patrick
17 years, 5 months
xsession error
by Jovan Spasojevic
hi,
i had do an update today something goes wrong. i cannot Login anymore in
gnome (xsession-error) whatever goes wrong i don't know.
I must login in terminal (save) on gui login (chosse session) and than
start in xterm gnome-session.
whatwever goes wrong i hope it will be fixed on (fc7).
regards,
jovan
17 years, 5 months
Re: Hplip and Scanning?
by Jovan Spasojevic
Hi, i am not using fc6 . I'm using rawhide/dev/fc7 however u want to
call. I have do the steps but i cannot scan either.......i know what can
i do anymore.....
regards,
jovan
17 years, 5 months
problems with install : LVM2 corruption
by Patrick bakker
Hi,
I managed to install FC6 but ran into a few problems in the process
(good ISO, verified CD). I had some LVM2 groups from FC4 and FC5 (and
possibly before) which I was going to have FC6 overwrite. I selected
custom partioning in the install and I tried to Edit the groups and
give them new mount points for FC6. There was some kind of error which
I didn't pay too much attention to at the time. If I recall correctly
it said something like there needed to be an extended partition for
LVM to work. Since I already had /hda2 marked as an LVM2 partition I
clicked around trying to convince Anaconda that all was well. I am
quite sure the only button I ever clicked was Edit on a partition (no
Add/Delete) because I was trying re-use existing volume groups. I then
carried on to the next step of preparing the partitions. Anaconda then
crashed. I tried reinstalling it but when the custom partioning screen
came up none of the LVM groups were visible. Since I still had a few
regular 4GB partitions around from some earlier FC installation I
installed FC6 there instead and left everything else alone because I
thought I could propably fix any LVM problems easier on a running
system.
Now I am running FC6 but I cannot mount any of my LVM volume groups. I
tried try to list the groups initially using something like vgscan.
The VolGroup00 showed up but it was missing one field which seemed odd
(2nd from the top I think, I didn't write it down).
If I try a vgscan now though nothing shows up.
Is there any way I can try to recover my LVM volume groups? Here's
some more details:
> fdisk /dev/hda
> p
Device Boot Start End Blocks Id System
/dev/hda1 1 3648 29302528+ 5 Extended
/dev/hda2 3649 24792 169839180 8e Linux LVM
/dev/hda5 1 608 4883697 83 Linux
/dev/hda6 609 1216 4883728+ 83 Linux
/dev/hda7 1217 1824 4883728+ 83 Linux
/dev/hda8 1825 2432 4883728+ 83 Linux
/dev/hda9 2433 3040 4883728+ 83 Linux
/dev/hda10 * 3041 3053 104391 83 Linux
I had at least the following:
/dev/mapper/VolGroup00-home
/dev/mapper/VolGroup00-music
/dev/mapper/LogVol00
Unfortunately, I was going to backup my home folder but then I
thought, I've never had any problems before with Fedora, why bother?
Oops.
Any help would be appreciated!
Thanks,
Patrick
17 years, 5 months
Re: xsession error
by Jovan Spasojevic
Hi had followd the steps but i cannot login .......what can i do
more...if possible??
regards
jovan
17 years, 5 months
Hplip and Scanning?
by Jovan Spasojevic
Hello,
i am not sure but i can't scanning anymore and i think hplip is not
working not correctly.
[jovans@localhost ~]$ sane-find-scanner
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make
sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
# Also you need support for SCSI Generic (sg) in your operating
system.
# If using Linux, try "modprobe sg".
found USB scanner (vendor=0x03f0, product=0x4c11) at libusb:001:003
# Your USB scanner was (probably) detected. It may or may not be
supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary
ports
# can't be detected by this program.
# You may want to run this program as root to find all devices. Once
you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
[jovans@localhost ~]$ scanimage -L
[jovans@localhost ~]$
Because the sane backend is configured correctly. Before 7 Days scanning
was ok but yet not more.....
anybody ideas?
regards,
jovan
17 years, 5 months
Recent yum update
by Michael Weiner
I ran yum update this morning on my recently upgraded FC6 server and saw the
following:
/etc/selinux/strict/contexts/files/file_contexts: Multiple different
specifications for /usr/bin/apt-get (system_u:object_r:rpm_exec_t:s0 and
system_u:object_r:apt_exec_t:s0).
/etc/selinux/strict/contexts/files/file_contexts: Multiple different
specifications for /usr/bin/apt-shell (system_u:object_r:rpm_exec_t:s0 and
system_u:object_r:apt_exec_t:s0).
...
libsemanage.semanage_direct_remove: Module bootloader was not found.
semodule: Failed on bootloader!
error: %trigger(selinux-policy-strict-2.3.18-10.noarch) scriptlet failed,
exit status 1
libsemanage.semanage_direct_remove: Module bootloader was not found.
semodule: Failed on bootloader!
error: %trigger(selinux-policy-strict-2.4.1-3.fc6.noarch) scriptlet failed,
exit status 1
...
error: %preun(ORBit-devel-0.5.17-19.fc6.i386) scriptlet failed, exit status
1
Has anyone else seen this? And is this anything to worry about?
Thanks in advance
Michael Weiner
17 years, 5 months
i386 junk on x86_64 default install
by Michel Salim
I do think it makes sense for yum to install both i386 and x86_64
variants of a package, if both are available, unless specified
otherwise. What I don't think makes sense, though, is having /so/ many
i386 packages available in the x86_64 tree, and thus also in the
installation media.
Having 32-bit libraries makes sense, for the purpose of running legacy
closed-source applications. Having i386 -devel packages... does not.
What's the point, without a 32-bit compiler to go along?
And then there are the i386 applications: firefox, gaim, etc. These
get installed by default (there's no way I can see to exclude i386
packages short of using kickstart). Removing them should be
straightforward, right? Just yum --remove glibc.i686. But it's not
that simple:
1. Often times, removing a 32-bit package also removes the files
shared with the 64-bit sibling.
2. With the default FC6 install, I get a circular dependency when
trying to remove glibc.i686. It never displays the final list of
affected packages.
Would it be possible, for FC7, to limit the 32-bit packages included
in -core to only the 32-bit libraries? Anything that installs to
/usr/bin should be excluded. Maybe include a core-i386 repository that
is by default disabled, for users who need 32-bit apps.
--
Michel Salim
http://salimma.livejournal.com/
17 years, 5 months
Video corruption with FC6 on ThinkPad 600X
by Chris Schumann
On my ThinkPad 600X, I did an upgrade install using CDs from FC5 to FC6. Now
the semi-transparent areas on the top and bottom of the screen in Gnome are
garbled. The icons on top of them display fine, but the area behind them
looks like a classic video driver bug.
The menus and icons on the left of the top menu bar are fine, but the icons
on the right of the top bar, and the left part of the bottom bar, both have
the issue.
Video chip is NeoMagic 256ZX with 4MB RAM. (NM2360? driver) Any pointers?
Chris
17 years, 5 months
--as-needed and undefined non-weak symbols
by Ville Skyttä
I'm wondering if I've stumbled upon a bug in ld's --as-needed or
something I was not aware of, here's an example, foo.c:
extern void gtk_main();
int main() {
gtk_main();
}
Now, libgtk (as of FC5) contains lots of undefined gdk_* symbols, so
trying "gcc -lgtk foo.c" on the above fails as expected, and "gcc -lgdk
-lgtk foo.c" succeeds, again as expected. However, to my surprise, "gcc
-Wl,--as-needed -lgdk -lgtk foo.c" fails:
/tmp/ccImoouo.o: In function `main':
foo.c:(.text+0xa): undefined reference to `gtk_main'
collect2: ld returned 1 exit status
Is this how --as-needed should behave? Ie. the linker does not appear
to notice that linking with libgdk is actually needed in this case and
drops it -> boom.
gtk+ is just an easy-to-find example in Fedora, and in its case,
eliminating the non-weak symbols in libgtk by linking it with libgdk
would most likely be the correct way around the problem, ditto with the
majority of other undefined-non-weak-symbols-in-shared-libs cases out
there. But don't pay attention to those details, I'm curious whether
the above demonstrates a problem in --as-needed or not.
17 years, 5 months