Installing GCC-4.3.0 in Fedora 16
by R Logeshwaran
Hi I'm a research scholar doing my research in networking for that i use
NS-2 package (ns-allinone-2.29). it will work good in Fedora-9 which uses
GCC-4.3.
My system is a new one it is not possible for me to install Fedora-9. So i
have installed Fedora 16, but now NS.2.29 is not working in fedora 16 since
the GCC compiler is 4.6.
so i need a solution to downgrade gcc to 4.3.0 version. else solution to
run NS2.29 in fedora16
please help me...
thanking you
--
Be Awesome like
Logesh
12 years, 1 month
hex tools in coreutils
by Ian Malone
Hi,
I'm wondering if anyone can suggest ways of handling hex/binary data
with coreutils? I've just written a script which uses xxd to patch a
file (here be monsters and all that), and wondering if there are any
tools which can be used to do something similar: neither hexdump nor
xxd are part of coreutils. od is, but can't do the reverse hex to
binary conversion that xxd can do.
Thanks for your time,
--
imalone
12 years, 1 month
Debugging drm modesetting issues
by David Rees
I've run Fedora for a long time. I stuck with Fedora 14 for a long
time as I much preferred Gnome 2 over Gnome 3 and everything just
worked. Rock solid.
Since F14 went EOL, I've recently upgraded to F16, but I've been
dogged by a couple of stability issues. The rest I've figured out.
Main one is that the system won't always boot. Boot process will
continue until it's time for drm/modesetting to take place at which
point instead of getting the resized text, I get a blank screen.
Adding radeon.agpmode=-1 seems to make this more reliable, but still
occasionally hangs.
The system is still responsive - a Ctrl-Alt-Del will reboot the system.
Looking at the logs after the reboot shows nothing - so it's obviously
gotten stuck pretty early in the boot process.
How can I debug this issue so that I might gather information to file
a bug report?
Second issue is that the system is now completely unstable with AMD
Cool'n'Quiet enabled. Already filed a bug for that one.
https://bugzilla.redhat.com/show_bug.cgi?id=795334 Sucks to waste
electricity when not needed!
-Dave
12 years, 1 month
Fedora 16 preupgrade with grub2 failure.
by Michael D. Setzer II
I've don't a number of upgrades from Fedora 14 to 16 with no
problems, but just had a very bad issue with grub2 not working.
Preupgrade process seemed to go fine, then rebooted.
Screen came up, but was in a very dark gray with slightly lighter
gray letters that were not very readable, but it appeared to be
processing fine, and let it run.
After a while, it had a popup window that said something about a
bootloader with only an OK button, which I was a guessing was
that it was going to install the new bootloader, so pressed enter.
Machine rebooted but showed the old grub 0.97 options, which
only listed the upgrade kernel option and the link to run my g4l
kernels. The preupgrade option didn't find files, but booting from
the g4l kernel gave me access, and I could see a grub2 directory
was there and so was the new kernels. I was eventually able to
get the 0.97 grub.conf to load the fedora 16 kernel and initramfs
by manually creating entry, but don't know why the grub2 upgrade
would have failed, or what the best way to get the grub2 correctly
installed?
I have the previous 500GB disk with the Fedora 14 before the
upgrade, so can go back to it if necessary. Had to duplicate the
disk to a 1TB drive and increase the /boot since the system only
had a 200MB /boot.
Hoping there is a simple solution?
+----------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor
Guam Community College Computer Center
mailto:mikes@kuentos.guam.net
mailto:msetzerii@gmail.com
http://www.guam.net/home/mikes
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+----------------------------------------------------------+
http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned: 19,471
Processing time: 32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)
BOINC@HOME CREDITS
SETI 11878212.985960 | EINSTEIN 7347240.179852
ROSETTA 4278297.373025 | ABC 11278989.077652
12 years, 1 month
kernel build question - CONFIG_XEN
by Piscium
I tried to build a kernel. In this section of code I had an issue:
# now run oldconfig over all the config files
for i in *.config
do
mv $i .config
Arch=`head -1 .config | cut -b 3-`
make ARCH=$Arch listnewconfig | grep -E '^CONFIG_' >.newoptions || true
if [ -s .newoptions ]; then
cat .newoptions
exit 1
fi
rm -f .newoptions
make ARCH=$Arch oldnoconfig
echo "# $Arch" > configs/$i
cat .config >> configs/$i
done
This is from the log:
+ mv kernel-2.6.42.7-i686-PAE.config .config
++ head -1 .config
++ cut -b 3-
+ Arch=i386
+ grep -E '^CONFIG_'
+ make ARCH=i386 listnewconfig
+ '[' -s .newoptions ']'
+ cat .newoptions
CONFIG_XEN
+ exit 1
What happens is that running "make ARCH=i386 listnewconfig", reports
CONFIG_XEN as new.
If I manually add "CONFIG_XEN=n" to .config, and run "make oldconfig",
then CONFIG_XEN is removed. This - I think - means that CONFIG_XEN is
an old option. But then I am baffled why is it output by "make
ARCH=i386 listnewconfig" or even " "make listnewconfig". I can make no
sense of it. Does anybody have an explanation?
Anyway, the way I solved this build issue was by putting
"CONFIG_XEN=n" in config-local, and this way I can build, still I am
curious.
12 years, 1 month
How to keep a particular kernel version?
by enclair
Hi,
I have these three kernels: 3.1.9, 3.2.5 and 3.2.6
There is a new kernel in -updates (3.2.7).
If I update to the new kernel, yum will want to remove 3.1.9.
Is there a possibility to set up yum to keep the older kernel (3.1.9) and
to remove 3.2.5 instead (the middle one)?
(There is the possibility to remove the middle kernel before each updates,
but it's not really convenient).
12 years, 1 month
tr equivalent to sed command
by 夜神 岩男
I'm trying to move a script from invoking lots of sed and awk to bash
builtins and I'm stumped on something I'm sure is simple.
Is there a tr equivalent to the following?
sed 's/[^[:alnum:]]//g'
I just can't seem to get tr -d to accept a negative matching set, but
perhaps that's not possible?
Thanks in advance
-IY
12 years, 1 month
Re: unusable encrypted volume on a live USB (because of passphrase)
by Joel Rees
(I wish I would quit forgetting important details.)
On Sun, Feb 26, 2012 at 5:47 PM, Joel Rees <joel.rees(a)gmail.com> wrote:
> This was my second try at a live USB, and I decided to experiment with
> an encrypted volume for /home. Used a bunch of leetsp3@k substitutions
... I mean, for the passphrase ...
> without thinking about the keyboard, so I can't mount the partition on
> boot. So, I'm wondering how hard it would be to reclaim the part of
> the flash disk being used for the encrypted volume, or whether it
> might just be easier to wipe the live image and start over.
>
> Can someone point me to the stuff the live images use to put encrypted
> volumes on these FAT disks? I tend to get lost in all the interesting
> side paths when I dig into the wiki without guidance.
>
> --
> Joel Rees
--
--
Joel Rees
12 years, 1 month
unusable encrypted volume on a live USB
by Joel Rees
This was my second try at a live USB, and I decided to experiment with
an encrypted volume for /home. Used a bunch of leetsp3@k substitutions
without thinking about the keyboard, so I can't mount the partition on
boot. So, I'm wondering how hard it would be to reclaim the part of
the flash disk being used for the encrypted volume, or whether it
might just be easier to wipe the live image and start over.
Can someone point me to the stuff the live images use to put encrypted
volumes on these FAT disks? I tend to get lost in all the interesting
side paths when I dig into the wiki without guidance.
--
Joel Rees
12 years, 1 month
how to send Bcc: using Evolution
by Mike Wright
Hi all,
Subject says it all.
I'm new to Evolution and am having trouble with some of its features,
such as how does one Bcc a recipient?
Hope this isn't an FAQ. I spent a fair amount of time on this without
success.
TIA,
Mike Wright
12 years, 1 month