Re: SSH problem

2023-01-11 Thread Veli-Pekka Kestilä

On 10.1.2023 20.25, Joe Wulf via users wrote:
Additional troubleshooting should include including '-' for the ssh 
command invocation.


This is the error, when trying to run XTerm after second ssh connection:

debug2: X11 auth data does not match fake data.
X11 connection rejected because of wrong authentication.
debug2: X11 rejected 1 i0/o0
debug2: channel 1: read failed

Link to the logs from invocations:

https://www.dropbox.com/s/mj1ppfmzdmn8vn2/ssh-errors.txt?dl=0

-vpk
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: SSH problem

2023-01-10 Thread Veli-Pekka Kestilä

On 10.1.2023 14.28, Frank Elsner via users wrote:

Hello,

today I faced the following problem:

Some of my panel entries do not work. Investigation on the command line level
shows that every second ssh call doesn't work. But why?

[frank@siffux ~]$ ssh christo "mate-terminal&" &
[1] 15817

This command brings up a window running mate terminal

[frank@siffux ~]$ ssh christo "mate-terminal&" &
[2] 15827
[frank@siffux ~]$ X11 connection rejected because of wrong authentication.
Failed to parse arguments: Cannot open display:

This is the error behaviour.

What's going on? How to solve the problem?


I don't know how to solve the problem but can confirm that I have the 
same one. From what I have deducted so far is that sshd in F36 and F37 
generates new xauth token and replaces the old one every time new 
connection is opened. I can fix the problem by running xauth list after 
the first connection and then xauth add with the data from xauth list to 
restore the original authentication token every time new connection is 
created.


One might make a hack with /etc/ssh/sshrc or .ssh/rc to muck with the 
tokens, but I am not sure it's a good fix on the long run. Would be nice 
to know what changed from F35, but I don't unfortunately have any 
installed anymore.


-vpk
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: current docker instructions for installing on fedora up to date?

2018-03-19 Thread Veli-Pekka Kestilä

On 19.3.2018 21:12, Robert P. J. Day wrote:


   i realize there's been some refactoring of docker packages for
fedora, so before i get buried in this, are the docker instructions
for fedora here:

   https://docs.docker.com/install/linux/docker-ce/fedora/

up to date? they look reasonable, just want to verify before i dive
into this. thank you kindly.



I installed it with those instructions maybe a week ago and it has been 
working fine. Even found my old images from previous version. One note 
to take is that I only use the machine to build images and not running 
them otherwise so can't say about long running stuff or custom 
configurations which I don't have either.


-vpk
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: gsl

2015-06-06 Thread Veli-Pekka Kestilä

On 4.6.2015 16:23, Patrick Dupre wrote:


===
  Patrick DUPRÉ | | email: pdu...@gmx.com
  Laboratoire de Physico-Chimie de l'Atmosphère | |
  Université du Littoral-Côte d'Opale   | |
  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
  189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===



Sent: Thursday, June 04, 2015 at 3:01 PM
From: Jonathan Underwood jonathan.underw...@gmail.com
To: Community support for Fedora users users@lists.fedoraproject.org
Subject: Re: gsl

On 3 June 2015 at 22:23, Patrick Dupre pdu...@gmx.com wrote:

Hello,

Can somebody help me?

This short piece of code fails.
It seems to be due to the gsl library!

Thank for your help.

#include gsl/gsl_multifit_nlin.h

int main () {
   const gsl_multifit_fsolver_type *T_ ;
   gsl_multifit_fsolver *s_ = gsl_multifit_fsolver_alloc (T_, 10, 1);
   }



You haven't initialized T_, so when you call
gsl_multifit_fsolver_alloc, it fails because it doesn't know what
solver type to allocate for.

So, try initializing it, eg.

const gsl_multifit_fsolver_type *T_ = gsl_multifit_fdfsolver_lmsder;

  warning: initialization from incompatible pointer type [enabled by default]
const gsl_multifit_fsolver_type *T_ = gsl_multifit_fdfsolver_lmsder ;

fsolver and fdfsolver are not compatible!
I did not find a way to initiate this pointer.



Try this code:
#include gsl/gsl_multifit_nlin.h

int main () {
const gsl_multifit_fdfsolver_type * T = gsl_multifit_fdfsolver_lmder;
gsl_multifit_fdfsolver * s = gsl_multifit_fdfsolver_alloc (T, 100, 3);
}

from: http://manpagez.com/info/gsl-ref/gsl-ref-1.12/gsl-ref_507.php

Atleast I got it to compile and run without segfaults.

-vpk

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: No mouse in Fedora 21 -

2015-05-20 Thread Veli-Pekka Kestilä



On 20/05/15 03:20, Bob Goodwin - Zuni, Virginia, USA wrote:



On 19/05/15 19:08, g wrote:

The rpi2b+ or whatever they call it, I can't find the box it came in
right now, but it has a different processor than the earlier ones and
Pidora does not run on it.

.
keyboard works in terminal, ok.

.
Yes, the keyboard works, but not in an x-terminal.

Dunno 'cause I can't open a terminal. Again when X starts the 
keyboard stops working.


Have you looked what X log file says about the keyboard etc. And have 
you tried to log in trough ssh after starting X and killing it if 
keyboard still works in terminal?


-vpk

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: is it the future?

2014-09-14 Thread Veli-Pekka Kestilä

On 14.9.2014 14:01, Timothy Murphy wrote:

Joonas Sarajärvi wrote:


It is not slow if you have little journal content, as you would in
cases where you prefer plain-text logs and set journald to not keep a
persistent log.

How?
I don't see anything relevant in man journalctl under Fedora-20.
(There is no entry for man journald.)


$ apropos journald
journald.conf (5)- Journal service configuration file
systemd-journald (8) - Journal service
systemd-journald.service (8) - Journal service
systemd-journald.socket (8) - Journal service

-vpk
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: file system compatibility...

2014-08-01 Thread Veli-Pekka Kestilä

On 1.8.2014 23:58, Ed Greshko wrote:

On 08/01/14 23:37, Angelo Moreschini wrote:
I need to use an USB Hard Disk as repository; that is a subversion 
repository that is used in a local network.


This means (for me) that the data wrote inside the HD can be used, in 
case of emergency, bot on OS Linux both on OS Windows 


Actually in this Hard Disk (that have ntfs file system) are stored data
writed from OS Windows XP; and I am not able to read (easily) this 
data in OS Fedora.




I apologize for not answer the question you're asking.

However, a friend of my had a similar request not too long ago.  I 
told him not to bother with his idea and to simply go out and get a 
NAS.  He was a bit tight on money but he still went out and got a low 
end Synology NAS with 2x3TB drives.  Final cost was less than US$400.


The data is available to all of his devices.  Including his mobile 
devices.  And, of course, he has RAID to minimize loss of data.


With the NAS devices you can get other set of problems. I have for 
example been rescuing data from NAS which had sparc processor and it had 
formatted ext3 in a way that you couldn't read it in Intel processor 
machines without doing extra things and using drivers in alpha state 
(and which development had stopped and you needed to compile yourself)


So if going to nas route should check that you can actually get 
something out of the drives in case of box going bad. Or actually take 
backups instead of always planning to do them.
If you don't mind others (Like your more or less friendly spy agencies) 
to read the code in git repository one way to share the stuff with 
multiple machine is actually keeping the repo in Dropbox or something 
similar which actually copies the data to multiple places.


-vpk

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: why do we use systemd?

2014-07-10 Thread Veli-Pekka Kestilä

On 10.7.2014 13:30, Balint Szigeti wrote:

On Wed, 2014-07-09 at 13:35 +0200, lee wrote:

David Benfell benf...@parts-unknown.org  mailto:benf...@parts-unknown.org 
writes:

 I guess the two questions I'm reaching for are:

 1) Is systemd conceptually broken, just a really bad idea from the
 start? Some people say yes, and some of them argue well.

So far, I've seen only arguments that would support that systemd is a
really bad idea because it's broken by design --- or should reasonably
be designed differently.

 2) Or, is it just that systemd is buried underneath an avalanche of
 horrendous documentation and poorly chosen terminology?

You could look at the source to find an answer.  Perhaps it's great ---
but I doubt it.
Seriously? Looking the source? Except developers who will dig in the 
source code?
None user will dig the source code, they just will leave the 
distribution or worse the all Linux area if
they can't solve their problem. I think, if the user can't find 
solution, (s)he will accept it, but if there

will be too many, they just escape.


Escape where, OSX has similar thing which seems to be even less 
documented (only my impression might be wrong).
Solaris has moved something similar.  AIX has never been truly SYSV and 
needs special hardware. BSD's will work but
have their own set of fun and are geared in my experience more to people 
who like to mess with the code. And some
of them are planning to move to the thing used in OSX (or in it's 
opensource upstream). Windows also has extensive

ways to manage how processes will start in startup etc.


Maybe the thing is that world has moved forward and there is needs which 
traditional sysv init doesn't answer
anymore. And any way you feel about systemd something similar would have 
come anyway and it actually did and
people weren't happy so in came systemd instead. If there is real 
problems with systemd I am sure someone will sooner
or later fork it and do different version. That's the choice in 
free/open software it's freedom of making your own if the
current solution doesn't work for you. Nothing of this freedom is taken 
away.


It's just that those people who actually do work for getting the 
distributions out have seen that systemd is only
maintained solution at the moment. I think it's somehow telling that no 
one else is even trying to make better
solution to the problems. It doesn't mean there isn't ways to improve 
systemd (or make a replacement), it just means no one is willing to

do it.

-vpk

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: Good tutorial on setting up a grid/cluster using fedora

2014-04-04 Thread Veli-Pekka Kestilä

On 3.4.2014 23:41, Adrian Sevcenco wrote:

On 04/02/2014 09:54 PM, Bill Oliver wrote:

Just to see if I can do it, I thought I'd set up a small grid/cluster
using fedora.  Does anybody know of a good step-by-step guide for this
(preferably free and online :-) )?

As for the answer to your initial inquiry i would highly recommend ROCKS
Clusters that is based on CENTOS. it will automatically install and
manage your nodes from a single point (the FrontEnd server)(with NFS
shared home).

I have tried ROCKS before (granted it was maybe 6 years ago) and it 
seems good if you have very lage number of nodes. If not then I would 
recommend setting the things yourself. Most programs run in scientific 
clusters use MPI for shared communication so you will just need MPI 
setup I would not waste time job management and such as long as there is 
only one person running on the cluster.


Setting up maybe 10 to 20 machines with kickstart using fedora with 
openmpi, ssh-keys for easy access to nodes and nfs sharing form frontend 
shouldn't be that big job. You will take same amount time learning ROCKS 
and it will have lots of features you don't need.


Also if you don't use the machines all the time and don't have the 
hardware yet it might be beneficial to use AWS nodes to do the 
calculations. In big HPC setups the real cost of the cluster usually 
comes from electricity consumption and cooling so you should factor 
these costs in when deciding what to do.


-vpk

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: Games on Linux

2012-10-24 Thread Veli-Pekka Kestilä

On 24.10.2012 22:04, Joe Zeff wrote:

On 10/24/2012 11:51 AM, Alan Cox wrote:

Small gamer market share, historically buggy and underperforming 3D
graphics drivers, no common way to sell/support.


...and a culture based on free software.  How many Linux gamers, do 
you think, would be willing to pay for games when so much of their 
software is FOSS?  That's not to say that nobody would pay (Please 
note that not only did a fair number of Linux people buy the Humble 
Bundle, on the average, our payment was higher than anybody else's.) 
but as long as game developers think we won't, they're not going to 
spend (or waste, as they see it) any time on us.


I also seems that many funded Kickstater projects have promised Linux 
support so there will be quality games coming from there.


-vpk
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: remake /dev

2012-07-28 Thread Veli-Pekka Kestilä

On 28.7.2012 15:07, Patrick Dupre wrote:

My idea what to repair the installation from another installation.
So, I mounted the defectuous installation, and I did a chroot to it.
It works except that I have an error message:
so such file or directory : /dev/urandom

Same thing when I make a yum --version
There is no files in /dev, I though that I should rebuild it


If you really need some device nodes in chroot environment you can run 
after chroot,  MAKEDEV /dev/urandom it should just create the device 
(presuming the defective installation does still have MAKEDEV command in 
sbin)


-vpk


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: remake /dev

2012-07-28 Thread Veli-Pekka Kestilä

On 28.7.2012 18:39, Aaron Konstam wrote:

On Sat, 2012-07-28 at 15:50 +0300, Veli-Pekka Kestilä wrote:

On 28.7.2012 15:07, Patrick Dupre wrote:

So, I mounted the defectuous installation, and I did a chroot to it.
It works except that I have an error message:
so such file or directory : /dev/urandom


If you really need some device nodes in chroot environment you can run
after chroot,  MAKEDEV /dev/urandom it should just create the device
(presuming the defective installation does still have MAKEDEV command in
sbin)

-vpk



I thought of MAKEDEV but does not seem to exist anymore on the system.

[root@localhost ~]# rpm -qf /sbin/MAKEDEV
MAKEDEV-3.24-10.fc17.x86_64

Atleast it seems to in the f17 system I have set up for doing some 
virtualisation testing. Granted it wasn't in the default installation 
and I had to install it manually. But you could have found this yourself 
by just doing yum search makedev.


-vpk
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: Make external hard drive accessible to all users

2012-07-13 Thread Veli-Pekka Kestilä

On 13.7.2012 23:39, Rick Stevens wrote:

On 07/13/2012 01:25 PM, Pasha R issued this missive::

F17 introduced a change to how external drives are mounted. They are
mounted now exclusively to a logged on user. This is somewhat
inconvenient, because iso images stored on external drive is now
inaccessible to virtual machines. Is it possible to make drives
accessible to everyone?


Add the mount to /etc/fstab and make sure the auto option is included.
Something like:

/path/to/device/mountpointext4  defaults,auto 0 0

I would use UUID as the device identifier so that if device name changes 
it will still mount it correctly.


blkid /dev/sda1 will get you the uuid and then add:

UUID=YOUR-UID /mountpointext4  defaults,auto 0 0

-vpk


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: NFS mount fails CentOS5 on FC16 host

2012-05-10 Thread Veli-Pekka Kestilä

On 10.5.2012 0.40, Bill Davidsen wrote:

Ed Greshko wrote:

On 05/09/2012 10:26 PM, Bill Davidsen wrote:
I get a message rpc.idmapd appears not to be running when it is 
running, and I'm


mount is rw,soft,intr -t nfs4 and the idmap process is running on 
host and

client, remounts from other clients work, etc, etc.
It isn't clear to me from the above what system is the Client and 
what system is the

Server and on which system you're getting the error message.

Sorry, I intended the subject to make that clear, the client is 
CentOS-5 the server FC16. The message appears on the CentOS5 client. 
The same server and data works on clients running FC9, FC10, FC13, 
RHEL-6, and I believe (ie. I'm told but haven't personally tested) 
OpenBSD works as well.


This is the only machine which stopped working when the NFS server was 
updated, and of course it's the internal web server. :-(


I had lot of problems with NFSv4 and CentOS 5.8, you should check that 
you have latest kernel on 5.8 as that solved some mounting problems. As 
for the error messages telling rpc.idmapd not running you can safely 
ignore. The error comes from the mount.nfs4 trying to read file in var 
which is not in there.


If you run strace mount.nfs4 server:/ /dir you will see that the command 
tries to access /var/lock/subsys/rpcidmapd
access(/var/lock/subsys/rpcidmapd, F_OK) = -1 ENOENT (No such file or 
directory)

This doesn't work as the file is actually named /var/lock/subsys/rpc.idmapd
As how you get rid of the error before RedHat fixes the actual source 
(just make the soft link between rpcidmapd and rpc.idmapd)


Now to the real error, I had the mounting problems from CentOS 5.8 to 
CentOS 5.8 with CLIENT running with kernel 2.6.18-308.1.1.el5 mounting 
didn't work. As I had the older kernel around as this was upgrade from 
older 5.x release I tried with it and the things worked without a 
problem. RedHat fixed the problem for me atleast in kernel 
2.6.18-308.4.1.el5.


Hope this helps,
-vpk



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: NFS mount fails CentOS5 on FC16 host

2012-05-10 Thread Veli-Pekka Kestilä

On 10.5.2012 20:44, Bill Davidsen wrote:

Veli-Pekka Kestilä wrote:

On 10.5.2012 0.40, Bill Davidsen wrote:

Ed Greshko wrote:

On 05/09/2012 10:26 PM, Bill Davidsen wrote:
I get a message rpc.idmapd appears not to be running when it is 
running,

and I'm



This is the only machine which stopped working when the NFS server was
updated, and of course it's the internal web server. :-(

I had lot of problems with NFSv4 and CentOS 5.8, you should check 
that you have
latest kernel on 5.8 as that solved some mounting problems. As for 
the error
messages telling rpc.idmapd not running you can safely ignore. The 
error comes

from the mount.nfs4 trying to read file in var which is not in there.

As how you get rid of the error before RedHat fixes the actual source 
(just make

the soft link between rpcidmapd and rpc.idmapd)


Adding the link solved the problem, although it's a kludge for sure!

Yeah.
Now to the real error, I had the mounting problems from CentOS 5.8 to 
CentOS 5.8
with CLIENT running with kernel 2.6.18-308.1.1.el5 mounting didn't 
work. As I
had the older kernel around as this was upgrade from older 5.x 
release I tried
with it and the things worked without a problem. RedHat fixed the 
problem for me

atleast in kernel 2.6.18-308.4.1.el5.

And there, too, the most recent kernel upgrade made it work (although 
the warning is still there without the link).



Hope this helps,
-vpk


Looks right, the spurious warning issue is avoided for the moment, and 
the failure of the mount is fixed (and hopefully added to regression 
testing and will stay that way). Thanks for the work-around on the 
warning, I had updated the kernel by the time I saw your message, 
since I was watching closely for updates.


Good to hear. I didn't bother to fix the error. Only thing which I hated 
was that I thought first (like you did) that this error was caused by 
the failure of nfs-mount. But after little bit of searching around I 
found out it was unrelated. Then I actually managed to find the root 
cause. I actually thought of upgrading to CentOS6 for a while because of 
that.


One thing I learned from this is that one can't trust even RH to 
actually test the core features of the releases in automated way. And 
that I am really happy to have a test server as it really (even as a 
virtual machine) saves you from sleepless nights. :)


-vpk


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: mount -t nfs4 fails, but mount -t nfs succeeds

2012-04-26 Thread Veli-Pekka Kestilä

On 26.4.2012 22:45, Jonathan Ryshpan wrote:

Can anyone explain this?  How can it be fixed?  Do some services need to
be started on the server?

The server is weather.  This log is from the client:
 # mount -t nfs weather:/home/jonrysh /mnt/weather
 # ls /mnt/weather
 Desktop  Documents  Downloads  Music  Pictures  Public  Templates  
Videos  grub2
 # umount /mnt/weather
 # mount -t nfs4 weather:/home/jonrysh /mnt/weather
 mount.nfs4: mounting weather:/home/jonrysh failed, reason given by 
server:
   No such file or directory
 #
Thanks in advance - jon
Could you post your /etc/exports from weather as the exports syntax is 
different for nfs3 and nfs4.


-vpk

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


Re: CentOS-6 by PXEboot?

2011-09-22 Thread Veli-Pekka Kestilä
On 23/09/2011 04:29, Craig White wrote:
 CentOS only recently got out the 6.0 release and RHEL 6.1 has actually
 been out for quite a while. The question is, why would anyone actually
 install CentOS 6 because they are running 9+ months behind and haven't
 actually packaged a single security update yet.

 Craig

Maybe some of us don't have luxury of choosing what to use. I would love 
to use fedora, but the 1-year reinstall cycle is too short (Especially 
as it's not sure there will be someone to help users to reinstall) and 
getting the old binaries ported from vms with lost sources to work with 
software insisting to use latest bells and whistles not found in CentOS 
5. Only choice left for us is the CentOS 6.

Veli-Pekka
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines