Re: Fedora - time to blink
by Hugh Caley
> RHEL/CentOS/SL are good for "install-and-forget" operation; they are not good
> for "stay-current-and-reasonably-stable" operation mainly due to too old
> kernel, but also for some users due to too old apps.
I think you have this bass-ackwards. Install and forget would seem to
include reasonably stable, as bug fixes will be created for the version
for some time.
"stay-current" will be difficult in any case, as no distribution that I
know of keeps all the apps current, they generally use the more-or-less
current versions at time of release and patch them, rather than
upgrading. If that's what you want, you will probably need to build and
install your own packages. Constant upgrading seems to be the norm for
those who want the latest and greatest.
Hugh
--
*/Hugh Caley/
Linux System Administrator
Aldon Business Area
Rocket Software*
6001 Shellmound St. Ste. 600 · Emeryville, CA 94608 · USA
Tel:+1.510.285.8542
Email:hcaley@aldon.com
Web:aldon.com
12 years, 5 months
Create an rsyncd.service fedora 16
by David Highley
We are trying to create an rsyncd.service with fedora 16. We can get the
process to start but it acts like it never opens the socket and exits a
short time later. The two files we have are below.
rsyncd.socket:
[Unit]
Description=rsyncd Service Sockets
[Socket]
ListenStream=873
[Install]
WantedBy=sockets.target
rsyncd.service:
[Unit]
Description=rsyncd Rsync Daemon
After=syslog.target network.target
DefaultDependencies=no
[Service]
EnvironmentFile=/etc/rsyncd/rsyncd.conf
ExecStart=/usr/bin/rsync --config=/etc/rsyncd/rsyncd.conf --daemon
[Install]
Also=rsyncd.socket
WantedBy=multi-user.target
12 years, 5 months
F14 yum or root went ape
by Beartooth
Following on from a yum update, I got :
Cleanup : policycoreutils-2.0.85-28.fc14.x86_6 32/33
Cleanup : liveusb-creator-3.11.4-1.fc14.noarch 33/33
Dependency Installed:
libqzeitgeist.x86_64 0:0.7.0-1.fc14
Updated:
gdb.x86_64 0:7.2-52.fc14
libass.x86_64 0:0.10.0-1.fc14
liveusb-creator.noarch 0:3.11.6-1.fc14
nss.i686 0:3.12.10-7.fc14
nss.x86_64 0:3.12.10-7.fc14
nss-sysinit.x86_64 0:3.12.10-7.fc14
nss-tools.x86_64 0:3.12.10-7.fc14
phonon.x86_64 0:4.5.1-1.fc14
policycoreutils.x86_64 0:2.0.85-30.3.fc14
policycoreutils-gui.x86_64 0:2.0.85-30.3.fc14
policycoreutils-python.x86_64 0:2.0.85-30.3.fc14
qt.x86_64 1:4.7.4-7.fc14
qt-mysql.x86_64 1:4.7.4-7.fc14
qt-webkit.x86_64 1:4.7.4-7.fc14
qt-x11.x86_64 1:4.7.4-7.fc14
virtuoso-opensource.x86_64 1:6.1.4-2.fc14
Complete!
*** glibc detected *** /usr/bin/python: free(): invalid pointer:
0x00000000039e9fb0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x30d4876d63]
/usr/lib64/libpython2.7.so.1.0[0x30f149e2a1]
/usr/lib64/libpython2.7.so.1.0[0x30f14783ba]
/usr/lib64/libpython2.7.so.1.0[0x30f1483ddb]
/usr/lib64/libpython2.7.so.1.0[0x30f145a1f4]
/usr/lib64/libpython2.7.so.1.0[0x30f1482187]
/usr/lib64/libpython2.7.so.1.0(PyDict_SetItem+0x70)[0x30f1484bf0]
/usr/lib64/libpython2.7.so.1.0(PyObject_GenericSetAttr+0x125)
[0x30f148a5f5]
/usr/lib64/libpython2.7.so.1.0(PyObject_SetAttr+0x9f)[0x30f1489edf]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x1d59)[0x30f14e5da9]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x66cd)[0x30f14ea71d]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x88d)[0x30f14eb04d]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x55ea)[0x30f14e963a]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x88d)[0x30f14eb04d]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x55ea)[0x30f14e963a]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x88d)[0x30f14eb04d]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x55ea)[0x30f14e963a]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x88d)[0x30f14eb04d]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCode+0x32)[0x30f14eb162]
/usr/lib64/libpython2.7.so.1.0[0x30f150639c]
/usr/lib64/libpython2.7.so.1.0(PyRun_FileExFlags+0x90)[0x30f15071d0]
/usr/lib64/libpython2.7.so.1.0(PyRun_SimpleFileExFlags+0x1ff)
[0x30f1507daf]
/usr/lib64/libpython2.7.so.1.0(Py_Main+0xb1e)[0x30f15198ce]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x30d481ee5d]
/usr/bin/python[0x400649]
======= Memory map: ========
00400000-00401000 r-xp 00000000 fd:00 2366513 /
usr/bin/python
00600000-00602000 rw-p 00000000 fd:00 2366513 /
usr/bin/python
01c1f000-0965a000 rw-p 00000000 00:00 0
[heap]
3073c00000-3073c2a000 r-xp 00000000 fd:00 2367894 /
usr/lib64/librpmio.so.1.0.0
3073c2a000-3073e29000 ---p 0002a000 fd:00 2367894 /
usr/lib64/librpmio.so.1.0.0
3073e29000-3073e2c000 rw-p 00029000 fd:00 2367894 /
usr/lib64/librpmio.so.1.0.0
3073e2c000-3073e2e000 rw-p 00000000 00:00 0
3074000000-3074063000 r-xp 00000000 fd:00 2363648 /
usr/lib64/librpm.so.1.0.0
3074063000-3074262000 ---p 00063000 fd:00 2363648 /
usr/lib64/librpm.so.1.0.0
3074262000-307426a000 rw-p 00062000 fd:00 2363648 /
usr/lib64/librpm.so.1.0.0
3074400000-3074423000 r-xp 00000000 fd:00 2363644 /
usr/lib64/librpmbuild.so.1.0.0
3074423000-3074623000 ---p 00023000 fd:00 2363644 /
usr/lib64/librpmbuild.so.1.0.0
3074623000-3074626000 rw-p 00023000 fd:00 2363644 /
usr/lib64/librpmbuild.so.1.0.0
3074626000-307462c000 rw-p 00000000 00:00 0
30d4400000-30d441f000 r-xp 00000000 fd:00 138174 /
lib64/ld-2.13.so
30d461e000-30d461f000 r--p 0001e000 fd:00 138174 /
lib64/ld-2.13.so
30d461f000-30d4620000 rw-p 0001f000 fd:00 138174 /
lib64/ld-2.13.so
30d4620000-30d4621000 rw-p 00000000 00:00 0
30d4800000-30d4991000 r-xp 00000000 fd:00 138175 /
lib64/libc-2.13.so
30d4991000-30d4b91000 ---p 00191000 fd:00 138175 /
lib64/libc-2.13.so
30d4b91000-30d4b95000 r--p 00191000 fd:00 138175 /
lib64/libc-2.13.so
30d4b95000-30d4b96000 rw-p 00195000 fd:00 138175 /
lib64/libc-2.13.so
30d4b96000-30d4b9c000 rw-p 00000000 00:00 0
30d4c00000-30d4c84000 r-xp 00000000 fd:00 140284 /
lib64/libm-2.13.so
30d4c84000-30d4e83000 ---p 00084000 fd:00 140284 /
lib64/libm-2.13.so
30d4e83000-30d4e84000 r--p 00083000 fd:00 140284 /
lib64/libm-2.13.so
30d4e84000-30d4e85000 rw-p 00084000 fd:00 140284 /
lib64/libm-2.13.so
30d5000000-30d5017000 r-xp 00000000 fd:00 140280 /
lib64/libpthread-2.13.so
30d5017000-30d5216000 ---p 00017000 fd:00 140280 /
lib64/libpthread-2.13.so
30d5216000-30d5217000 r--p 00016000 fd:00 140280 /
lib64/libpthread-2.13.so
30d5217000-30d5218000 rw-p 00017000 fd:00 140280 /
lib64/libpthread-2.13.so
30d5218000-30d521c000 rw-p 00000000 00:00 0
30d5400000-30d5402000 r-xp 00000000 fd:00 140285 /
lib64/libdl-2.13.so
30d5402000-30d5602000 ---p 00002000 fd:00 140285 /
lib64/libdl-2.13.so
30d5602000-30d5603000 r--p 00002000 fd:00 140285 /
lib64/libdl-2.13.so
30d5603000-30d5604000 rw-p 00003000 fd:00 140285 /
lib64/libdl-2.13.so
30d5800000-30d5815000 r-xp 00000000 fd:00 140286 /
lib64/libgcc_s-4.5.1-20100924.so.1
30d5815000-30d5a14000 ---p 00015000 fd:00 140286 /
lib64/libgcc_s-4.5.1-20100924.so.1
30d5a14000-30d5a15000 rw-p 00014000 fd:00 140286 /
lib64/libgcc_s-4.5.1-20100924.so.1
30d5c00000-30d5c07000 r-xp 00000000 fd:00 144937 /
lib64/librt-2.13.so
30d5c07000-30d5e06000 ---p 00007000 fd:00 144937 /
lib64/librt-2.13.so
30d5e06000-30d5e07000 r--p 00006000 fd:00 144937 /
lib64/librt-2.13.so
30d5e07000-30d5e08000 rw-p 00007000 fd:00 144937 /
lib64/librt-2.13.so
30d6000000-30d6016000 r-xp 00000000 fd:00 140283 /
lib64/libz.so.1.2.5
30d6016000-30d6216000 ---p 00016000 fd:00 140283 /
lib64/libz.so.1.2.5
30d6216000-30d6217000 rw-p 00016000 fd:00 140283 /
lib64/libz.so.1.2.5
30d6400000-30d641c000 r-xp 00000000 fd:00 144929 /
lib64/libselinux.so.1
30d641c000-30d661c000 ---p 0001c000 fd:00 144929 /
lib64/libselinux.so.1
30d661c000-30d661d000 r--p 0001c000 fd:00 144929 /
lib64/libselinux.so.1
30d661d000-30d661e000 rw-p 0001d000 fd:00 144929 /
lib64/libselinux.so.1
30d661e000-30d661f000 rw-p 00000000 00:00 0
30d6800000-30d6817000 r-xp 00000000 fd:00 140541 /
lib64/libresolv-2.13.so
30d6817000-30d6a16000 ---p 00017000 fd:00 140541 /
lib64/libresolv-2.13.so
30d6a16000-30d6a17000 r--p 00016000 fd:00 140541 /
lib64/libresolv-2.13.so
30d6a17000-30d6a18000 rw-p 00017000 fd:00 140541 /
lib64/libresolv-2.13.so
30d6a18000-30d6a1a000 rw-p 00000000 00:00 0
30d6c00000-30d6c2f000 r-xp 00000000 fd:00 144962 /
lib64/libncursesw.so.5.7
30d6c2f000-30d6e2f000 ---p 0002f000 fd:00 144962 /
lib64/libncursesw.so.5.7
30d6e2f000-30d6e30000 rw-p 0002f000 fd:00 144962 /
lib64/libncursesw.so.5.7
30d7800000-30d7906000 r-xp 00000000 fd:00 144941 /
lib64/libglib-2.0.so.0.2600.0
30d7906000-30d7b05000 ---p 00106000 fd:00 144941 /
lib64/libglib-2.0.so.0.2600.0
30d7b05000-30d7b06000 rw-p 00105000 fd:00 144941 /
lib64/libglib-2.0.so.0.2600.0
30d7b06000-30d7b07000 rw-p 00000000 00:00 0
30d8400000-30d8414000 r-xp 00000000 fd:00 2366820 /
usr/lib64/libelf-0.152.so
30d8414000-30d8613000 ---p 00014000 fd:00 2366820 /
usr/lib64/libelf-0.152.so
30d8613000-30d8614000 r--p 00013000 fd:00 2366820 /
usr/lib64/libelf-0.152.so
30d8614000-30d8615000 rw-p 00014000 fd:00 2366820 /
usr/lib64/libelf-0.152.so
30d8800000-30d8826000 r-xp 00000000 fd:00 140287 /
lib64/libexpat.so.1.5.2
30d8826000-30d8a25000 ---p 00026000 fd:00 140287 /
lib64/libexpat.so.1.5.2
30d8a25000-30d8a28000 rw-p 00025000 fd:00 140287 /
lib64/libexpat.so.1.5.2
30d9800000-30d982b000 r-xp 00000000 fd:00 2362247 /
usr/lib64/liblua-5.1.soAborted (core dumped)
You have new mail in /var/spool/mail/root
[root@HBsk3 ~]#
I'm OK as far as "Complete!", but what encountered the
ventilation after that??
--
Beartooth Staffwright, Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.
12 years, 5 months
gnome: cd notification on logging in
by Ian Malone
Hi,
On Gnome 3.2 in Fedora 16 I get a notification when logging in for any
CDs that are in the CD/DVD drives (there are two on this machine). Is
this normal or expected behaviour?
--
imalone
12 years, 5 months
.vcf files -
by Bob Goodwin
Is there a Linux application that will display a .vcf file?
Bob
12 years, 5 months
How is screen size handled in kvm/qemu
by Alexander Volovics
I decided to try out virtualization in Fed 16 + Gnome 3.2 on my laptop.
To begin I chose a small distro 'Crunchbang-10 64bits, based on Debian
Live with the Openbox WM.
No problems with the install.
But the result is not comfortable because the laptop screen is 1600x900
and the virt manager screen for Crunchbang is 1024x768, the wrong (4:3)
proportionality.
This means that even if I use full-screen I still have a 'small'
Crunchbang screen.
I this a restriction of virtual graphics or are there (hidden)
configuration options.
Alexander
12 years, 5 months
Re: Fedora - time to blink
by Philip Rhoades
On 2011-11-28 11:10, users-request(a)lists.fedoraproject.org wrote:
> Date: Mon, 28 Nov 2011 01:09:49 +0100
> From: suvayu ali <fatkasuvayu+linux(a)gmail.com>
> Subject: Re: Fedora - time to blink
> To: Community support for Fedora users
> <users(a)lists.fedoraproject.org>
> Message-ID:
> <CAMXnza1Ejf-sKV7YE1+j1sOwWUMO7ZrAC-cvXVJrJvKYmQY_Rg(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Mon, Nov 28, 2011 at 00:57, Marko Vojinovic <vvmarko(a)gmail.com>
> wrote:
>> Or the default DE
>> choice could "rotate" for each release --- XFCE for F17, LXDE for
>> F18, KDE for
>> F19, Gnome3 for F20, and over again, in turns. That way each DE
>> would have
>> equal amount of "visibility" among users, more bugs would get fixed,
>> etc.
>
> This is actually a very nice idea. And I believe it fits in with the
> goals of Fedora, forwarding the progress of FOSS. After all Gnome is
> not the only FOSS desktop, by far. Maybe you can suggest this on the
> desktop list? (is that the appropriate list?)
Yes, it is a good idea! I have been using XFCE for some number of
releases now because I wanted a lite desktop for my netbook and so I
changed to XFCE for all my other desktops and servers for consistency -
and I have been quite happy about the change ever since!
Regards,
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: phil(a)pricom.com.au
12 years, 5 months
speed of yum
by Genes MailLists
I happened upon pacman on Arch linux - and it appeared to be
substantially faster than yum. Now this was casual "visual impact only"
- no formal tests using similar packages and same computer etc - but it
was very much noticeably faster.
Installs of even large packages seemed to fly compared to what I was
used to from yum.
Of course it could be difference in systems, or xz compression versus
presto or who knows what else ... but it leads me to ask ...
Are there any good performance benchmarks comparing yum with pacman
and apt etc?
gene/
12 years, 5 months
penta-booting hard-disk: who would administer the hard-disk office?
by Linux Tyro
Hi,
As I have liked Linux (yes, I am windows convert), so with 2 GB RAM
and 250 GB hard-disk, I am now going to make hard-disk penta boot as
follows:-
Fedora - 20 GB - installing it, - /root (20 GB)
openSUSE - 10 GB installing with /root (10 GB)
Ubuntu - 10 GB installing with /root (10 GB)
Debian - 10 GB installing with /root (10 GB)
Mint - 10 GB installing with /root (10 GB)
/home - 190 GB (remaining space)
In this scenario, I have just few doubts:
While suppose I first install Fedora, I have to use /root for 20 GB,
/home for 190 GB (which automatically becomes Logical partition...?)
or should I make both primary and logical other distros...?
Similarly proceeding with all distros, and allocating space from the
unallocated ones, okay but installed other distros would come in
Extended...(obviously...?)
After final installation, which distros would govern the booting menu?
Since some may have GRUB2 and others may have GRUB Legacy, so changing
one file might disturb the other or vice-versa? Or is it like that if
I have installed /root (Fedora) at first, so only /boot/grub/menu.lst
of Fedora would govern the hard-disk and the changes made in this file
would be done automatically with other installed distros too...Trying
this new geeky way of installation but I have no prior experience
since earlier I had installed only two distros - Fedora dual booted
with Windows, but now I am trying to remove Windows completely and
installed these distros.... Any suggestions....welcome....Thanks.
--
THX
12 years, 5 months