Re: [CentOS-docs] Installing CentOS - user feedback

[Manuel Wolfshant]

On 8/18/20 2:34 AM, Manuel Wolfshant wrote:

On 8/17/20 11:04 PM, Rich Bowen wrote:
A few days ago I got email from a user who was attempting to install 
CentOS. I've included their full message below, but, to summarize, 
when one clicks on the "CentOS Linux" link on the front page of 
centos.org one is given a matrix of choices, and no guidance. On 
choosing one option - say, x84_64 ISO, one is then given another list 
of options and no guidance. Pick one of *those* options and you are 
yet again given a list of options and no guidance.


Now, it could be argued that someone who doesn't know what to choose 
is not our target audience, and I suppose that would be an ok 
position to hold. But wouldn't it be great to lower the bar just a 
little, and offer some guidance as to which links one should click?


I'd like to see several things:

1) On the front page, where it says "We offer two Linux distros:", 
there would be at least some hint of what this choice entails


2) On the download page - https://www.centos.org/centos-linux/ - a 
little explanation of what the various options there are.


So far, this is all just edits to centos.org. The next two steps 
involve pushing changes to the mirror network, and I honestly have no 
idea what is involved there.


3) Adding phrasing to 
http://isoredirect.centos.org/centos/8/isos/x86_64/ that indicates 
what that inscrutable list of links means.


and finally, possibly not even possible:

4) Add words to http://centos4.zswap.net/8.2.2004/isos/x86_64/ (as a 
random example) that say what the various options mean. This is 
probably not possible, since these are just autoindex generated 
pages. We could, however, offer Apache httpd and nginx configuration 
recommendations which will provide that additional information for 
sites that chose to follow the instructions.



Oh, sweet. I just noticed that below the /8/isos tree there is no 
description similar to 
http://centos4.zswap.net/7/isos/x86_64/0_README.txt. Wonderful choice, 
dropping each and every hint that [barely] existed.





And, really, #1 and #2 are the most important here.

Rich, I fully agree with that user and frankly, I command him for 
reaching out and telling you ( and us ) his concerns. I for one would 
have quit and not looked back. Been there, done that.


Leaving that aside, AFAIK the main web site is not under community 
control. It was taken over by RedHat eons ago ( not that it was 
accessible for us, the members of the CentOS teams, before that anyway 
) and I bet that there are most 5 people who can modify it. If memory 
serves I am part of the wiki translation team for 12 years or so and 
AFAIK none of those who can edit the wiki had ever had any sort of 
influence on the pages published on www.c.o. We actually had to _beg_ 
to have links in the main website point to the wiki ( which _was_ 
under our control ) so that we could publish information we thought 
that could/would be useful for the users.



In an ideal world, we would have some sort of AJAX that would 
dynamically describe each and every iso link on the main pages of the 
web site. But that's a job for web designers and content publishers. I 
fully recommend to whoever will be tasked with this project to look at 
the wiki maintained by the arch community. THAT is how things should 
be done, from my point of view. And, with all due respect, I mean that 
as opposed to access.r.c and www.r.c which are awful to navigate 
unless you know exactly what you want.. and sometimes not even then.


wolfy


PS: I created the very very first 0_README.txt file that is now 
included in the isos/$ARCH folder. A file which usually is ignored for 
the simple reason that end users almost never reach it but whose 
content should be published BEFORE the users attempt to download an iso.





The full message follows:

>>
I stumbled on your address on a Centos Faq page. I hope you can give me
some sort of answer.
I have been searching for a way to ask a question, but have not located
a forum. As I am fairly new to Linux generally, I am exploring
varieties, and Centos surfaced as an interesting option. But, again, I
have a problem no one else considers worthy of asking or answering: how
do I choose? Apparently the user in the download directory is supposed
to know what they are looking for.
When I followed the link to "download CentOs", I chose a link with
".iso" on it. This opened another page, so I picked another likely
candidate. I went four or five branches deep before I gave up. I have no
idea why I would want one branch or the other. Should I just leave
CentOs to the experts?
I really wish that on the home page there was a specification for "user
level". Do developers assume that the user is expert, and that someone
who is not qualified will get exhausted and go away? It seems very
unkind to make that assumption and not say so. If I am not the intended
user, please tell me! Otherwise, 

Re: [CentOS-docs] Installing CentOS - user feedback

[Manuel Wolfshant]

On 8/17/20 11:04 PM, Rich Bowen wrote:
A few days ago I got email from a user who was attempting to install 
CentOS. I've included their full message below, but, to summarize, 
when one clicks on the "CentOS Linux" link on the front page of 
centos.org one is given a matrix of choices, and no guidance. On 
choosing one option - say, x84_64 ISO, one is then given another list 
of options and no guidance. Pick one of *those* options and you are 
yet again given a list of options and no guidance.


Now, it could be argued that someone who doesn't know what to choose 
is not our target audience, and I suppose that would be an ok position 
to hold. But wouldn't it be great to lower the bar just a little, and 
offer some guidance as to which links one should click?


I'd like to see several things:

1) On the front page, where it says "We offer two Linux distros:", 
there would be at least some hint of what this choice entails


2) On the download page - https://www.centos.org/centos-linux/ - a 
little explanation of what the various options there are.


So far, this is all just edits to centos.org. The next two steps 
involve pushing changes to the mirror network, and I honestly have no 
idea what is involved there.


3) Adding phrasing to 
http://isoredirect.centos.org/centos/8/isos/x86_64/ that indicates 
what that inscrutable list of links means.


and finally, possibly not even possible:

4) Add words to http://centos4.zswap.net/8.2.2004/isos/x86_64/ (as a 
random example) that say what the various options mean. This is 
probably not possible, since these are just autoindex generated pages. 
We could, however, offer Apache httpd and nginx configuration 
recommendations which will provide that additional information for 
sites that chose to follow the instructions.


And, really, #1 and #2 are the most important here.

Rich, I fully agree with that user and frankly, I command him for 
reaching out and telling you ( and us ) his concerns. I for one would 
have quit and not looked back. Been there, done that.


Leaving that aside, AFAIK the main web site is not under community 
control. It was taken over by RedHat eons ago ( not that it was 
accessible for us, the members of the CentOS teams, before that anyway ) 
and I bet that there are most 5 people who can modify it. If memory 
serves I am part of the wiki translation team for 12 years or so and 
AFAIK none of those who can edit the wiki had ever had any sort of 
influence on the pages published on www.c.o. We actually had to _beg_ to 
have links in the main website point to the wiki ( which _was_ under our 
control ) so that we could publish information we thought that 
could/would be useful for the users.



In an ideal world, we would have some sort of AJAX that would 
dynamically describe each and every iso link on the main pages of the 
web site. But that's a job for web designers and content publishers. I 
fully recommend to whoever will be tasked with this project to look at 
the wiki maintained by the arch community. THAT is how things should be 
done, from my point of view. And, with all due respect, I mean that as 
opposed to access.r.c and www.r.c which are awful to navigate unless you 
know exactly what you want.. and sometimes not even then.


wolfy


PS: I created the very very first 0_README.txt file that is now included 
in the isos/$ARCH folder. A file which usually is ignored for the simple 
reason that end users almost never reach it but whose content should be 
published BEFORE the users attempt to download an iso.





The full message follows:

>>
I stumbled on your address on a Centos Faq page. I hope you can give me
some sort of answer.
I have been searching for a way to ask a question, but have not located
a forum. As I am fairly new to Linux generally, I am exploring
varieties, and Centos surfaced as an interesting option. But, again, I
have a problem no one else considers worthy of asking or answering: how
do I choose? Apparently the user in the download directory is supposed
to know what they are looking for.
When I followed the link to "download CentOs", I chose a link with
".iso" on it. This opened another page, so I picked another likely
candidate. I went four or five branches deep before I gave up. I have no
idea why I would want one branch or the other. Should I just leave
CentOs to the experts?
I really wish that on the home page there was a specification for "user
level". Do developers assume that the user is expert, and that someone
who is not qualified will get exhausted and go away? It seems very
unkind to make that assumption and not say so. If I am not the intended
user, please tell me! Otherwise, could someone please explain how to
choose which version of CentOs to use?
If you could forward this letter to someone who can take the time to
answer my question, I will be grateful.
<<

___
CentOS-docs mailing list
CentOS-docs@centos.org

Re: [CentOS-docs] Documentation SIG: Participation wanted

[Manuel Wolfshant]

Count me in.

wolfy


On June 30, 2020 9:20:55 PM GMT+03:00, Rich Bowen  wrote:
>Hi, folks,
>
>I've been working through the CentOS wiki for more than a year now, 
>trying to identify and fix outdated/wrong/obsolete content. It's a 
>daunting task, and I'm losing.
>
>I would very much like to gather a group of people who are:
>
>* Knowledgeable about CentOS
>* Good with words
>* Have a little time
>
>who would be willing and able to review the content of the wiki, and
>fix 
>the bits that are incorrect.
>
>The CentOS Documentation SIG (which doesn't actually exist in any 
>meaningful way) is, according to the wiki:
>
>responsible for the content of the Wiki, and other public sources of 
>documentation. This includes, but is not limited to:
>
>* Determining, and imposing, a hierarchy/architecture of content in the
>wiki
>* Editing/pruning existing content when it is
>incorrect/outdated/obsolete
>* Recruiting subject matter experts to do some of that editing
>* Recruiting translators to keep our various translations in sync
>
>[Ref: https://wiki.centos.org/SpecialInterestGroup/Documentation ]
>
>If any of the above appeals to you, I would ask you to let me know. I 
>would like to create a SIG around the wiki. Please let me know if
>you're 
>interested. I know that there are a number of you who are consistently 
>active on this list. I would like to find a way to give us a little
>more 
>power/authority over the wiki to make higher-level editorial decisions 
>about information architecture. Also, having a formal SIG might be a
>way 
>to engage more people to join the effort and dedicate some time to it.
>
>___
>CentOS-docs mailing list
>CentOS-docs@centos.org
>https://lists.centos.org/mailman/listinfo/centos-docs

___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] very low performance of Xen guests

[Manuel Wolfshant]

On 6/15/20 5:40 PM, Stephen John Smoogen wrote:



On Mon, 15 Jun 2020 at 09:42, Manuel Wolfshant 
mailto:wo...@nobugconsulting.ro>> wrote:


On 6/15/20 2:46 PM, Stephen John Smoogen wrote:

I got inspired by Adi's earlier suggestion and after reading
https://access.redhat.com/articles/3311301 I've tried today all
variants of disabling the spectre mitigations. Whatever I do,
immediately after a reboot, yum reinstall kernel does not take
less than 5 minutes :( It goes down to 2 min if I repeat the
operation afterwards so I guess some caching kicks in. I will try
later today the kernels from elrepo and maybe even xen.crc.id.au
<http://xen.crc.id.au> ( I kind of hate the "disable selinux"
recommendation from the install page so I postponed it in the hope
of other solution ).



If you can do a full reinstall, could you see if a KVM host/guest 
combo has the same problem? That would at least point the finger more 
firmly at VT, spectre or something else.





I finally managed to install a fresh KVM host / guest pair on an 
identical blade ( HS21XM, 64 GB ram, 2*E5450@ 3.00GHz ). Here are the 
results I see:



1. KVM host, stock instalation and fully updated, kernel 3.10.0-1127.10.1
#cd /sys/kernel/debug/x86/
#cat ibrs_enabled pti_enabled retp_enabled
0
1
1

#time yum -y reinstall kernel-3.10.0-1127.el7.x86_64
real    0m50.026s
user    0m32.872s
sys 0m23.312s


2. KVM guest on the same machine (virt-install --name guest1-rhel7 
--memory 2048 --vcpus 2  --disk size=20 --network=bridge:br0 --pxe 
--os-variant rhel7 <=== copy/paste from 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-guest_virtual_machine_installation_overview-creating_guests_with_virt_install 
), stock installation and fully updated with absolutely no change 
towards the defaults including same ibrs_enabled pti_enabled 
retp_enabled as the host, , kernel 3.10.0-1127.10.1



#time yum -y reinstall kernel-3.10.0-1127.el7.x86_64
real    2m39.644s
user    1m54.662s
sys 1m32.496s


3. Xen Domu,  3.10.0-1127.8.2.el7.x86_6 ( but results are consistent 
across all kernels )


# cat ibrs_enabled pti_enabled retp_enabled
0
0
0

# time yum -y reinstall kernel-3.10.0-1127.el7.x86_64
real    5m44.030s
user    2m9.931s
sys 4m7.771s


4. Dom0, 4.9.215-36.el7.x86_64, , xen 4.12 from centos' repo

# time  yum -y reinstall kernel-3.10.0-1127.el7.x86_64
real    1m52.417s
user    0m45.704s
sys 1m32.167s

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] very low performance of Xen guests

[Manuel Wolfshant]

On 6/15/20 2:46 PM, Stephen John Smoogen wrote:



On Sun, 14 Jun 2020 at 14:49, Manuel Wolfshant 
mailto:wo...@nobugconsulting.ro>> wrote:


Hello


    For the past months I've been testing upgrading my Xen hosts
to CentOS 7 and I face an issue for which I need your help to solve.

    The testing machines are IBM blades, model H21 and H21XM.
Initial tests were performed on the H21 with 16 GB RAM; during the
last 6=7 weeks I've been using the H21XM with 64 GB. In all cases
the guests were fully updated CentOS 7 -- initially 7.6 ( most
recent at the time of the initial tests ), and respectively 7.8
for the tests performed during the last 2 months.  As host I used
initially CentOS 6 with latest kernel available in the centos virt
repo at the time of the tests and CentOS 7 with the latest kernel
as well. As xen versions I tested 4.8 and 4.12 ( xl info included
below ). The storage for the last tests is a Crucial MX500 but
results were similar when using traditional HDD.

    My problem, in short, is that the guests are extremely slow.
For instance , in the most recent tests, a yum install kernel
takes cca 1 min on the host and 12-15 (!!!) minutes in the guest,
all time being spent in dracut regenerating the initramfs images.
I've done rough tests with the storage  ( via dd if=/dev/zero
of=a_test_file size bs=10M count=1000 ) and the speed was
comparable between the hosts and the guests. The version of the
kernel in use inside the guest also did not seem to make any
difference . OTOH, sysbench (
https://github.com/akopytov/sysbench/ ) as well as p7zip benchmark
report for the guests a speed which is between 10% and 50% of the
host. Quite obviously, changing the elevator had no influence either.

    Here is the info which I think that should be relevant for the
software versions in use. Feel free to ask for any additional info.


Is there a way to boot up a PV guest versus an HVM?


If I understood the docs correctly, newer xen does only PVHVM ( 
xen_platform_pci=1 activates that ) and HVM. But they say it's better 
than PV. And I did verify, PVHVM is indeed enabled and active





I could not find a H21XM but found an HS21XM on the iBM


My bad. The blades are indeed HS21 (Type 8853) and HS21 XM (Type 7995). 
The XM blades have 2*Xeon E5450@3GHz / 12GB L1 cache processors. The 
options I can fiddle with are https://imgur.com/a/DonXe5P


AFAICS the setttings are reasonable but please do let me know if there 
is anything there that should not be as it is



site and that seemed to be a 4 core 8 thread cpu which looks 'old' 
enough that the Spectre/etc fixes to improve performance after the 
initial hit were not done. (Basically I was told that if the CPU was 
older than 2012, just turn off hyperthreading altogether to try and 
get back some performance.. but don't expect much).


I can live with that. My problem is that DomU are much much slower that 
Dom0 so it seems xen virtualization affects ( heavily ) the performance.



As such I would also try turning off HT on the CPU to see if that 
improves anything.


I got inspired by Adi's earlier suggestion and after reading 
https://access.redhat.com/articles/3311301 I've tried today all variants 
of disabling the spectre mitigations. Whatever I do, immediately after a 
reboot, yum reinstall kernel does not take less than 5 minutes :( It 
goes down to 2 min if I repeat the operation afterwards so I guess some 
caching kicks in. I will try later today the kernels from elrepo and 
maybe even xen.crc.id.au ( I kind of hate the "disable selinux" 
recommendation from the install page so I postponed it in the hope of 
other solution ).


___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] very low performance of Xen guests

[Manuel Wolfshant]

Hello


    For the past months I've been testing upgrading my Xen hosts to 
CentOS 7 and I face an issue for which I need your help to solve.


    The testing machines are IBM blades, model H21 and H21XM. Initial 
tests were performed on the H21 with 16 GB RAM; during the last 6=7 
weeks I've been using the H21XM with 64 GB. In all cases the guests were 
fully updated CentOS 7 -- initially 7.6 ( most recent at the time of the 
initial tests ), and respectively 7.8 for the tests performed during the 
last 2 months.  As host I used initially CentOS 6 with latest kernel 
available in the centos virt repo at the time of the tests and CentOS 7 
with the latest kernel as well. As xen versions I tested 4.8 and 4.12 ( 
xl info included below ). The storage for the last tests is a Crucial 
MX500 but results were similar when using traditional HDD.


    My problem, in short, is that the guests are extremely slow. For 
instance , in the most recent tests, a yum install kernel takes cca 1 
min on the host and 12-15 (!!!) minutes in the guest, all time being 
spent in dracut regenerating the initramfs images. I've done rough tests 
with the storage  ( via dd if=/dev/zero of=a_test_file size bs=10M 
count=1000 ) and the speed was comparable between the hosts and the 
guests. The version of the kernel in use inside the guest also did not 
seem to make any difference . OTOH, sysbench ( 
https://github.com/akopytov/sysbench/ ) as well as p7zip benchmark 
report for the guests a speed which is between 10% and 50% of the host. 
Quite obviously, changing the elevator had no influence either.


    Here is the info which I think that should be relevant for the 
software versions in use. Feel free to ask for any additional info.



 [root@t7 ~]# xl info
host   : t7
release    : 4.9.215-36.el7.x86_64
version    : #1 SMP Mon Mar 2 11:42:52 UTC 2020
machine    : x86_64
nr_cpus    : 8
max_cpu_id : 7
nr_nodes   : 1
cores_per_socket   : 4
threads_per_core   : 1
cpu_mhz    : 3000.122
hw_caps    : 
bfebfbff:000ce3bd:20100800:0001::::

virt_caps  : pv hvm
total_memory   : 57343
free_memory    : 53620
sharing_freed_memory   : 0
sharing_used_memory    : 0
outstanding_claims : 0
free_cpus  : 0
xen_major  : 4
xen_minor  : 12
xen_extra  : .2.39.g3536f8dc
xen_version    : 4.12.2.39.g3536f8dc
xen_caps   : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
hvm-3.0-x86_32p hvm-3.0-x86_64

xen_scheduler  : credit2
xen_pagesize   : 4096
platform_params    : virt_start=0x8000
xen_changeset  :
xen_commandline    : placeholder dom0_mem=1024M,max:1024M cpuinfo 
com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all ucode=-1

cc_compiler    : gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
cc_compile_by  : mockbuild
cc_compile_domain  : centos.org
cc_compile_date    : Tue Apr 14 14:22:04 UTC 2020
build_id   : 24148a191438467f26a9e16089205544a428f661
xend_config_format : 4


[root@t5 ~]# xl info
host   : t5
release    : 4.9.215-36.el6.x86_64
version    : #1 SMP Mon Mar 2 10:30:40 UTC 2020
machine    : x86_64
nr_cpus    : 8
max_cpu_id : 7
nr_nodes   : 1
cores_per_socket   : 4
threads_per_core   : 1
cpu_mhz    : 2000
hw_caps    : 
b7ebfbff:0004e33d:20100800:0001::::

virt_caps  : hvm
total_memory   : 12287
free_memory    : 6955
sharing_freed_memory   : 0
sharing_used_memory    : 0
outstanding_claims : 0
free_cpus  : 0
xen_major  : 4
xen_minor  : 8
xen_extra  : .5.86.g8db85532
xen_version    : 4.8.5.86.g8db85532
xen_caps   : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
hvm-3.0-x86_32p hvm-3.0-x86_64

xen_scheduler  : credit
xen_pagesize   : 4096
platform_params    : virt_start=0x8000
xen_changeset  :
xen_commandline    : dom0_mem=1024M,max:1024M cpuinfo 
com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all

cc_compiler    : gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-23)
cc_compile_by  : mockbuild
cc_compile_domain  : centos.org
cc_compile_date    : Thu Dec 12 14:34:48 UTC 2019
build_id   : da34ae5b90c82137dcbc466cd66322381bc6fd21
xend_config_format : 4

/Note:/ with all other kernels and xen versions that were published for 
C6 during the last year,  the performance was the same, i.e. slow



The test VM is exactly the same, copied among servers:

[root@t7 ~]# cat  /etc/xen/test7_1
builder = "hvm"
xen_platform_pci=1
name = "Test7"
memory = 2048
maxmem = 4096
vcpus = 2
vif = [ 

Re: [CentOS-docs] Incorrect link in /Contribute wiki page

[Manuel Wolfshant]

On 3/29/20 4:02 PM, Lucio Seki wrote:

Hi Yagi-san,

Thank you for guiding me.
Does this wiki have a wysiwyg editor? Or the workflow is to download 
the whole page, edit it, and then upload it back again?
In my Menu it shows just 'Load' and 'Save' options in the menu, even 
in the WikiSandBox page.


Regards,
Lucio Seki


Once you login with your account, an "Edit" button appears on the top 
line, immediately to the left of the Search field.


___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-docs] Initial draft for the release notes for C7.7

[Manuel Wolfshant]

Hello


    I

I've created a draft for the Release Notes for CentOS 7.7 at 
https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7.1908



    Manuel


___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] [QEMU-KVM] Centos guest VM freezing

[Manuel Wolfshant]

On 1/9/19 11:50 AM, Akshar Kanak wrote:

Hi
Thanks for the reply

We have seen the same guest VM freezing on vmware ESXi machine also ,


No wonder given that the guest remains 5 years out of date even when 
using a different hypervisor. Leaving aside that also the long-term 
kernel installed from ElRepo that you are using is also more then 4 
years out of date.


Please update the OS(es) to the current supported OS versions ( that is, 
7.6 / 6.10 ) and verify if the problems persist. But you've already been 
told that by several persons...



so we were interested in know in the internal condition of the guest 
vm when the freeze happened

How can we analyse the core file generated by "virsh dump "


http://bfy.tw/LhMS might help with that


Regards,

    manuel





Thanks and regards
Akshar

On Wed, Jan 9, 2019 at 1:58 PM Manuel Wolfshant 
mailto:wo...@nobugconsulting.ro>> wrote:


On 1/9/19 10:24 AM, Akshar Kanak wrote:

Dear team
    I am running a centos guest VM  which freezes for every few
days . The qemu-kvm on  shows 100% cpu utilization.
    Ping to the guest might work or may not work .Please can you
tell me what approach can i take to debug it .
    using "virsh dump" I can dump the core of the  guest vm but I
am not sure how to analyse it .
    Guest Centos VM : "Linux GUESTCentOS70
3.10.0-123.4.4.el7.x86_64 #1 SMP Fri Jul 25 05:07:12 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux"
"CentOS Linux release 7.0.1406 (Core)"
1 vcpu and 2 GB ram
Host machine : "Linux HOST 3.10.51-1.el6.elrepo.x86_64 #1 SMP Fri
Aug 1 13:14:11 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux"
"CentOS release 6.5 (Final)"
qemu-kvm package used : qemu-kvm-0.12.1.2-2.415.el6_5.10.x86_64
Thanks and regards
Akshar


I'd say that you should start by updating the OS on both host and
guest. Both OSes are heavily outdated, you lack YEARS of updates.



___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] [QEMU-KVM] Centos guest VM freezing

[Manuel Wolfshant]

On 1/9/19 10:24 AM, Akshar Kanak wrote:

Dear team
    I am running a centos guest VM  which freezes for every few days . 
The qemu-kvm on  shows 100% cpu utilization.
    Ping to the guest might work or may not work .Please can you tell 
me what approach can i take to debug it .
    using "virsh dump" I can dump the core of the  guest vm but I am 
not sure how to analyse it .
    Guest Centos VM : "Linux GUESTCentOS70 3.10.0-123.4.4.el7.x86_64 
#1 SMP Fri Jul 25 05:07:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux"

  "CentOS Linux release 7.0.1406 (Core)"
  1 vcpu and 2 GB ram
Host machine : "Linux HOST 3.10.51-1.el6.elrepo.x86_64 #1 SMP Fri Aug 
1 13:14:11 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux"

"CentOS release 6.5 (Final)"
qemu-kvm package used : qemu-kvm-0.12.1.2-2.415.el6_5.10.x86_64
Thanks and regards
Akshar


I'd say that you should start by updating the OS on both host and guest. 
Both OSes are heavily outdated, you lack YEARS of updates.



    Regards


    Manuel

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] CentOS wiki - QA related data/activities

[Manuel Wolfshant]

On 05/14/2018 02:19 AM, Manuel Wolfshant wrote:




* QaWiki section linked below is very out of date. Is it and the team 
active?


https://wiki.centos.org/QaWiki
You are right on this one. Sooner or later "someone" should fix this 
page, too :) 


 which I just did, using a sledge hammer. Thanks for reminding us 
about the old cruft.
Oh, and I forgot to answer: yes the QA / dev team IS active. Those new 
releases - especially for new archs - do not test themselves by magic :)


Manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-docs] CentOS wiki - QA related data/activities

[Manuel Wolfshant]

Hi all,


Hello Phil




Trying to lookup QA related team, data and general info.

Issues:

* Not allowed to view below page, even if logged in.

https://wiki.centos.org/QaTeam
The page contains pieces of information which is preferable to not be 
available for reading to the general public,




* Page below mentions QA mailing list.

https://wiki.centos.org/FAQ/General/RebuildReleaseProcess

No QA list though on page below.

https://lists.centos.org/mailman/listinfo/
That wiki page is heavily outdated. Things have changed a lot in the 
last couple of years and the wiki pages were not updated accordingly. In 
particular the QA mailing list is no longer used.






* QaWiki section linked below is very out of date. Is it and the team active?

https://wiki.centos.org/QaWiki
You are right on this one. Sooner or later "someone" should fix this 
page, too :)



Regards,

        Manuel

___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] discussions around upstream documentation

[Manuel Wolfshant]

On 04/12/2016 08:11 AM, Fabian Arrotin wrote:

On 11/04/16 21:11, Akemi Yagi wrote:

>On Mon, Apr 11, 2016 at 10:37 AM, Karsten Wade  wrote:

>>-BEGIN PGP SIGNED MESSAGE-
>>Hash: SHA1
>>
>>On 04/11/2016 09:18 AM, Jim Perrin wrote:

>>>What are the thoughts or concerns about this sort of workflow
>>>change?

>>
>>Any chance Moin Moin can store wiki source in git and sync
>>automatically with a central git repository?
>>
>>It would provide another pathway to suggest edits to the wiki without
>>requiring wiki edit permissions.
>>
>>For new documentation, e.g. layered project content from SIGs or
>>upstream documentation sources, I would think we'd want to skip a
>>conversion to/from Moin Moin and instead work directly in the sources
>>from upstream. Eases merging upstream, etc. Last Summer's GSoC
>>students implemented such a workflow.

>
>I agree with providing another pathway. More specifically, I am
>against moving entirely away from the current way of editing the wiki.
>
>Going for the git environment has its own merits as already mentioned,
>but at the same time it would deter some people. Not everyone is
>particularly fond of (or familiar with) git. I would not be surprised
>if some of the existing wiki authors stop contributing if the direct
>edit is no longer an option.
>
>Akemi

That's what I fear too. A wiki is something that has to be edited live,
and be quick/fast.
+1 here. A wiki has an "edit button" , a "preview button" and a "save 
button". It's not a "commit to git, pull from git, format for wiki, 
whatever" dance. It's already hard enough that people need to create a 
wiki account, subscribe to a mailing list ( with a different account BTW 
), announce their intention and request real access, wait for access.





Git-based doc is probably something more formalized and for tech writers
having to maintain an "official" doc.
I (in the past) had a look athttp://www.mkdocs.org/  for this (and so
all the .md can be in a public git repo that people can submit PR to)
While personally I don't mind switching to something using git in the
workflow, I'm wondering if such tool shouldn't be used instead to target
"official" docs under centos.org/docs and not the wiki. (both can be
complementary)

just my 0.02$

Another +1 here as well. Let's focus on $SUBJECT.
The issue at hand is not the wiki ( and its workflow ) but the content 
from https://www.centos.org/docs/ which is

a) deprecated for years
b) unmaintainable by the community.
There is no public info on who has access to update the above link or 
even what should ( and what should NOT ) get published there. It's 
assumed that the content should replicate ( adjusted as needed i.e. 
respecting trademarks , branding and so on plus removing/replacing 
references to the parts of RHEL not relevant for CentOS ) the content 
from upstream. However since CentOS 6 was launched, short of rumors 
around "we cannot do that because of legal stuff" nothing was ever done. 
All we have now is documentation for long long long dead releases ( 2, 
3, 4 ) and some copies of the RHEL 5 docs, 3 or more years old. We do 
not even have a pointer along "take with a grain a salt the information 
from the upstream docs hosted at access.redhat.com" which still would be 
more than nothing and would alleviate a bit ( or at least complement ) 
the need for the @docs trigger in #centos.


Before discussing tooling , IMNSHO we should focus on the actual content 
that we want/need to publish and the method to create and deliver it. 
Using publican, mkdocs or whatever method to generate web pages from 
"something" should be the result of this discussion, not the preamble.


___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] status of https://wiki.centos.org/Documentation

[Manuel Wolfshant]

On 03/22/2016 09:30 AM, Fabian Arrotin wrote:

Hi,

I was having a look at that page, and was wondering what we can do for
point #3 (Manuals and other documentation)
As we have no real content for CentOS 6 and 7 , my idea was just to
explain in one line that (while technically not the CentOS
documentation) , almost all the points coming from uptream documentation
( - except for subscription manager - ) can be applied to CentOS and so
having link from that section to https://access.redhat.com/documentation/en/

Ideas, thoughts, comments ?


+1 for that. it's long overdue.
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Wiki Update - Aide Link

[Manuel Wolfshant]

On 02/02/2016 04:27 PM, Mike Thompson wrote:

Hello All,

My username is MikeThompson

The link to configure Aide at the bottom of this page:
https://wiki.centos.org/HowTos/OS_Protection

Is dead, and says its dead, however, the old link to
http://www.bofh-hunter.com/2008/04/10/centos-5-and-aide/ now redirects
to a malicious website.

One of my less than savvy users got his windows machine infected there
last night.  I'm wondering if it makes sense to change the link to point
to one of the following guides which are very decent:

http://www.server-world.info/en/note?os=CentOS_6=aide
http://www.server-world.info/en/note?os=CentOS_7=aide
https://highon.coffee/blog/security-harden-centos-7/

Would be happy to make the change, but hopefully the malicious URL can
be taken down.


I've updated the page,

Manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

[Manuel Wolfshant]

On 01/14/2016 06:57 PM, George Dunlap wrote:

As mentioned yesterday, Xen 4.6 packages are now available for
testing.  These also include an update to libvirt 1.3.0, in line with
what's available for CentOS 7.  Please test, particularly the upgrade
if you can, and report any problems here.

To upgrade:

yum update --enablerepo=centos-virt-xen-testing

To install from scratch:

* Install centos-release-xen from centos-extras

yum install centos-release-xen

* Update to get the new kernel:

yum update

* Install the Xen packages from the centos-virt-xen-testing repo:

yum install --enablerepo=centos-virt-xen-testing xen

Keep in mind that there is still a bug in the upstream CentOS
new-kernel script which for some people consistently fails to add an
"initird" line to the Xen boot stanza.  Check /boot/grub/grub.conf;
the Xen stanza should look something like this:

title CentOS (3.18.21-17.el6.x86_64)
 root (hd0,0)
 kernel /xen.gz dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1
console=com1,tty loglvl=all guest_loglvl=all
 module /vmlinuz-3.18.21-17.el6.x86_64 ro
root=/dev/mapper/VolGroup-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD
rd_LVM_LV=VolGroup/lv_swap SYSFONT=latarcyrheb-sun16 crashkernel=auto
rd_LVM_LV=VolGroup/lv_root  KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb
quiet
 module /initramfs-3.18.21-17.el6.x86_64.img


  -George
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Hello

I've attempted to upgrade today to xen 4.6 ( because of something 
which seems to be a reincarnation of 
http://lists.xen.org/archives/html/xen-devel/2014-01/msg02259.html ) and 
I noticed that the new xen-runtime package tries to bring in a whole 
bunch of other packages:



Installing for dependencies:
 atk x86_64 1.30.0-1.el6 base 195 k
 avahi-libs x86_64 0.6.25-15.el6 base 55 k
 cairo x86_64 1.8.8-6.el6_6 base 309 k
 cups-libs x86_64 1:1.4.2-72.el6 base 321 k
 fontconfig x86_64 2.8.0-5.el6 base 186 k
 freetype x86_64 2.3.11-15.el6_6.1 base 361 k
 gdk-pixbuf2 x86_64 2.24.1-6.el6_7 updates 501 k
 gtk2 x86_64 2.24.23-6.el6 base 3.2 M
 hicolor-icon-theme noarch 0.11-1.1.el6 base 40 k
 jasper-libs x86_64 1.900.1-16.el6_6.3 base 137 k
 libXcomposite x86_64 0.4.3-4.el6 base 20 k
 libXcursor x86_64 1.1.14-2.1.el6 base 28 k
 libXft x86_64 2.3.1-2.el6 base 55 k
 libXi x86_64 1.7.2-2.2.el6 base 37 k
 libXinerama x86_64 1.1.3-2.1.el6 base 13 k
 libXrandr x86_64 1.4.1-2.1.el6 base 23 k
 libXrender x86_64 0.9.8-2.1.el6 base 24 k
 libthai x86_64 0.1.12-3.el6 base 183 k
 libtiff x86_64 3.9.4-10.el6_5 base 343 k
 pango x86_64 1.28.1-10.el6 base 351 k


Is this really needed ?

wolfy
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen package update (including XSA-156)

[Manuel Wolfshant]

On 11/18/2015 02:08 PM, Pasi Kärkkäinen wrote:

Hello,

On Sun, Nov 15, 2015 at 06:42:18PM +0200, Pasi Kärkkäinen wrote:

On Sun, Nov 15, 2015 at 02:04:58PM +0200, Pasi Kärkkäinen wrote:

On Thu, Nov 12, 2015 at 02:00:27PM +, George Dunlap wrote:

So going forward, we're moving the CentOS 6 Xen packages from the
custom "xen4" repos that were introduced several years ago, to repos
based on its position as a sub-project of the Virt Sig.  That will
make things consistent between all the sigs, as well as between CentOS
6 and 7 Xen packages.

Unfortunately, XSA-156 came up rather suddenly and is a bit blocked by
this transition.

So please help us test the new repository structure, so that we can
with conscience push the updates to xen4 users in general.


Seems to work for me!



Except now on another system I see this problem:


Anyone else seeing this libvirt-python problem with virt-manager and/or 
virt-viewer ?

(happens on a freshly installed system, so no earlier libvirt rpms installed)

It tries to install half of the OS, but it works for me.  It seems that 
your yum does not like that you already have 
libvirt-client-1.2.15-3.el6.x86_64. Mine is happy to bring in 
libvirt-{python,client}-0.10.2-54.el6_7.2.x86_64 from updates


wolfy



# yum install virt-manager
..
..
..

--> Finished Dependency Resolution
Error: Package: libvirt-python-0.10.2-54.el6_7.2.x86_64 (updates)
Requires: libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
Available: libvirt-client-0.10.2-54.el6.x86_64 (base)
libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
Available: libvirt-client-0.10.2-54.el6_7.2.x86_64 (updates)
libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
Installed: libvirt-client-1.2.15-3.el6.x86_64 (@centos-virt-xen)
Not found
  You could try using --skip-broken to work around the problem
  You could try running: rpm -Va --nofiles --nodigest


Are we missing a build of libvirt-python 1.2.15 package?



___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen package update (including XSA-156)

[Manuel Wolfshant]

On 11/12/2015 04:44 PM, George Dunlap wrote:
Do you have the centos-extras repo enabled? The key in question is in 
the centos-release-virt-common package, which is in the centos-extras repo


I've just updated, so far so good.
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen package update (including XSA-156)

[Manuel Wolfshant]

On 11/12/2015 04:00 PM, George Dunlap wrote:

To update to the new repository structure, install the
centos-release-xen package directly from the new repo:

  yum 
updatehttp://mirror.centos.org/centos/6/virt/x86_64/xen/centos-release-xen-7-11.el6.x86_64.rpm

This should replace the xen4 repositories with the new virt sig


[root@xenh4bis ~]# yum update -y 
http://mirror.centos.org/centos/6/virt/x86_64/xen/centos-release-xen-7-11.el6.x86_64.rpm

Loaded plugins: fastestmirror, presto
Setting up Update Process
centos-release-xen-7-11.el6.x86_64.rpm | 6.0 kB 00:00
Examining 
/var/tmp/yum-root-DzSL_q/centos-release-xen-7-11.el6.x86_64.rpm: 
10:centos-release-xen-7-11.el6.x86_64
Marking /var/tmp/yum-root-DzSL_q/centos-release-xen-7-11.el6.x86_64.rpm 
as an update to 10:centos-release-xen-6-4.el6.centos.x86_64

Loading mirror speeds from cached hostfile
 * epel: fedora.mirrors.telekom.ro
base |  951 B 00:00
updates |  951 B 00:00
Resolving Dependencies
--> Running transaction check
---> Package centos-release-xen.x86_64 10:6-4.el6.centos will be updated
---> Package centos-release-xen.x86_64 10:7-11.el6 will be an update
--> Processing Dependency: 
/etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization for package: 
10:centos-release-xen-7-11.el6.x86_64
--> Processing Dependency: 
/etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization for package: 
10:centos-release-xen-7-11.el6.x86_64

--> Finished Dependency Resolution
Error: Package: 10:centos-release-xen-7-11.el6.x86_64 
(/centos-release-xen-7-11.el6.x86_64)

   Requires: /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen package update (including XSA-156)

[Manuel Wolfshant]

On 12 noiembrie 2015 16:44:55 EET, George Dunlap  wrote:

>Do you have the centos-extras repo enabled?  The key in question is in
>the centos-release-virt-common package, which is in the centos-extras
>repo.
>
> -George
no, i normally keep everything but base,updates (and xen4centos on xen 
machines) disabled. I will retry later today.
Thanks

  wolfy

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] Update for FAQ - q.15 q.31 update merge

[Manuel Wolfshant]

On 06/09/2015 01:27 AM, Karsten Wade wrote:

[...]
http://wiki.centos.org/KarstenWade/GeneralFAQUpdateq31q15

Thanks - Karsten

I'd say that at least the following paragraphs from q15 are worth
preserving: - Any point release is just a snapshot with previous
updates, plus the latest batch of new upstream updates, rolled into
a new [base] repo with an initially empty [updates] repo. - There
is a CentOS Vault containing older CentOS trees. This vault is a
picture of the older tree when it was removed from the main tree,
and does not receive updates. It should only be used for
reference.

After  If you are using an older minor version than the latest in
a given branch, then you are missing security and bugfix updates.
I'd also emphasize that we offer no support for these
configurations, something along: For this reason old minor releases
are never supported. If you want/need to freeze at an old point
release you are entirely on your own.


wolfy, tired of people who fail to understand what minor releases
are and keep pushing in IRC for support of old[er] stuff

I think those look pretty good especially if you think they can answer
confusion about community support for older minor versions. Included
here with some highlighting:

The size of this answer article is just a bit larger (looking) than
each of the previous two answers, which is good -- too many words
won't help. :)

I trimmed a bit more stuff -- repetitive phrasing and unrelated terms
- -- I think it's ready publish to the FAQ.

Call me picky but I'd rephrase
 The CentOS Project *ONLY* provides updates or other changes for 
the latest version of each major branch.

to
 The CentOS Project provides updates or other changes*ONLY* for the 
latest version of each major branch.


I am not a native English speaker so I might be wrong but I feel like 
the emphasis is better placed in the variant I suggested because it 
marks one of the major differences towards RH and the EUS/AUS mechanism 
that exists for RHEL. Heck, we might even add a reference to those a la 
if you need active support for an older minor release please consider 
using  



And yes, this FAQ item becomes a bit longish...
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Update for FAQ - q.15 q.31 update merge

[Manuel Wolfshant]

On 06/05/2015 08:30 PM, Karsten Wade wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Folks:

A few of us (KB, Johnny, myself) have begun work on updating the main
FAQs on the CentOS wiki. Mainly that means looking over and updating
for any changes that have been going on in the last 18 months as the
project has expanded to include SIG releases, monthly updates of many
new types, new hardware architectures, and so forth.

For this first update we've got this from the FAQ:

q.15:
http://wiki.centos.org/FAQ/General#head-6e2c3746ec45ac3142917466760321e8
68f43c0e
q.31
http://wiki.centos.org/FAQ/General#head-dcca41e9a3d5ac4c6d900a991990fd11
930867d6

The first item is that these questions are repetitive, so I'd like to
combine them in to a single answer. Second is that version numbering
has expanded, so we need to cover monthly updates and so forth.

Circling around on this, we ended up with the following complete
rewrite that would replace q.31 and retire q.15 (thereby making q.31
in to q.30.) How does this update sound?

If we're close enough, I'll push it to live at the start of next week,
and we can always continue iterating on it.

The text below is in Moin Moin format; I was going to do a diff
between the versions but then we differed so wildly in combining and
rewriting that I think a mental diff will work better. A formatted
draft is here:

http://wiki.centos.org/KarstenWade/GeneralFAQUpdateq31q15

Thanks - Karsten


I'd say that at least the following paragraphs from q15 are worth 
preserving:
- Any point release is just a snapshot with previous updates, plus the 
latest batch of new upstream updates, rolled into a new [base] repo with 
an initially empty [updates] repo.
- There is a CentOS Vault containing older CentOS trees. This vault is a 
picture of the older tree when it was removed from the main tree, and 
does not receive updates. It should only be used for reference.


After  If you are using an older minor version than the latest in a 
given branch, then you are missing security and bugfix updates. I'd 
also emphasize that we offer no support for these configurations, 
something along:
For this reason old minor releases are never supported. If 
you want/need to freeze at an old point release you are entirely on 
your own.



wolfy, tired of people who fail to understand what minor releases are 
and keep pushing in IRC for support of old[er] stuff

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] CentOS 6 VM image for paravirtualizaton on CentOS Xen server

[Manuel Wolfshant]

On 03/16/2015 08:58 AM, Pasi Kärkkäinen wrote:

On Sun, Mar 15, 2015 at 07:52:42PM -0700, Sarah Newman wrote:

I'd really prefer to work from 'virsh' than from hand-writing xl
configuration files.When I last did this sort of thing, I worked from
a PXE environment that I controlled and could reserve DHCP settings
based on MAC addresses, and tune PXE to boot from disk by default but
allow users to select a clean re-install of the operating system they
wanted.

virt-install with --location maybe? Never tried it but it looks like what you 
want.

http://linux.die.net/man/1/virt-install


Yeah you can use virt-install on CentOS 5 Xen host to install CentOS 6 PV domUs,
I do that often, an example for GUI installation:

virt-install -d -n vmname -r 1024 --vcpus=2 -f /dev/vg01/vmname_disk0 -b virbr0 --vnc -p 
-l http://ftp.funet.fi/pub/mirrors/centos.org/6.5/os/x86_64;

(you need to have virt-viewer installed, that'll be used to display the VNC GUI 
console).

-- Pasi


Quote from an actual installation:

[root@xenh4 ~]# history| grep virt
virt-install  -n dhcpdns -p -r 1024 --os-type=linux --vnc -f 
/var/lib/xen/images/dhcpdns -s 2 -l 
http://192.168.50.40/mrepo/centos6-i386/disc1 -x 
ks=ftp://192.168.50.40/linux/ks-minimalC6-xen.cfg;


[root@xenh4 ~]# uname -a
Linux xenh4 2.6.18-400.1.1.el5xen #1 SMP Thu Dec 18 02:18:37 EST 2014 
i686 i686 i386 GNU/Linux


https://github.com/CentOS/Community-Kickstarts/blob/master/ks-minimalC6.cfg 
is quite close to the above mentioned ks-minimalC6-xen.cfg ( actually 
both are descendants of the same template of mine )


___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] Pull Request wiki.c.o/AdditionalResources/Repositories

[Manuel Wolfshant]

On 01/15/2015 01:09 AM, PatrickD Garvey wrote:

On Tue, Jan 13, 2015 at 10:04 AM, Karanbir Singh mail-li...@karan.org wrote:

On 01/09/2015 11:49 PM, Tom Sorensen wrote:

KB -- I made those changes several months ago (Sep/Oct I believe), with
discussion in IRC. This was after a spate of people in the main channel
having issues with Atomic (there's a name that's going to end up causing
problems...) and the continued use of RPMForge/RepoForge, with no
indication that they're really really bad. As well as the recognition of
the reality that there are a very few repos that are frequently
recommended (and, in the case of EPEL, now easily enabled in CentOS).

I think we should do a bit of work and find a tangiable set of standards
that a repo needs to meet in order to be 'endorsed' or rated at a
certain level. Because at the moment it does seem to add value to a repo
or two over others, based on personal opinion.

I am willing to write code to do this validation, but were going to need
a set of good rules to implement.

regards and thanks

- KB


Maybe it isn't code that needs to be generated.

I obviously wasn't around for any IRC discussion of this page and its
implications.
I don't imagine there is any sort of log of that discussion I could review.

Rhetorical questions and comments:
Is it true some of these repos exist because CentOS wasn't adequate for some
particular purpose, but someone thought they could provide a parallel resource
to easily install additional software?
Yes, it is. Some people need newer versions for applications  than what 
the distro can provide. Other need complementary stuff which the distro 
or better said RHEL is not willing or not able to provide.



[...]


 From Tom's comment I infer there was a need to warn people away from using some
repos that were consuming significant resources to help folks who had
trusted them.

Right. Some repos lead to problems similar to:
/
Aug 28 14:27:15 TheAlien  hey there, im having trouble updating 
packages on my server. yum update gives a long list of needed updates 
and sumarises 'Install   3 Package(s)//
// / Upgrade 132 Package(s) / Remove1 Package(s)' but then 
says 'package mysql-5.5.25-1.el5.remi.x86_64 (which is newer than 
mysql-5.0.95-5.el5_9.i386) is already installe//d' --//
//Aug 28 14:27:24 TheAlien  plus several messages like 'file 
/usr/bin/mysqlaccess from install of mysql-5.0.95-5.el5_9.i386 conflicts 
with file from package mysql-5.5.25-1.el5.r//

/
Others simply are no longer properly maintained, for instance still 
shipping older versions of applications which have known vulnerabilities.

//

[...]


It also appears that somehow Fedora's efforts have been mutually beneficial.


Yes, they have but this has nothing to do with the wiki page we speak 
about. Incidentally EPEL aims to a high standard so as to make it 
suitable for an enterprise-grade distro which CentOS aims to be and that 
is why we recommend to all others packagers to follow similar rules ( 
when possible  and if they make sense, of course ). However this is by 
no means a requirement that must be met in order to have a 3rd party 
repository listed in the CentOS wiki.




With these thoughts as background for my thinking, my brainstorm is that the
Special Interest Groups and spins may be the path to solving the need to have
additional non-CentOS resources and know they are sufficiently cooperative.

Proposal:
The Third Party Repositories section should not list any other repositories,
but should only note there are difficulties in making several independent
repositories safely usable and give a thorough explaination of what has happened
in the past without naming names.
I can only concur with what John has said. You are looking for problems 
to fix where there are none. 3 months ago Tom has made a great job in 
cleaning the page up ( and several of us assisted him when he asked for 
opinions ) and - AFAIK -  its current shape expresses the views of most 
of the regulars who provide help via the various CentOS support 
channels. If and when needed we modify the page but as it is now it is 
completely satisfactory for its purpose. Even if the feelings of some 
people get hurt by our opinions about the quality of their work ( i.e. 
of the packages they provide ).


___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] removing/redirecting the Projects page

[Manuel Wolfshant]

On 01/06/2015 05:24 PM, Fabian Arrotin wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

We've decided to decomission the (old and unused) trac instance on
projects.centos.org. We'll just redirect to git.centos.org instead
(where all the fun happens).

So, what to do with the http://wiki.centos.org/Projects page ?
deleting it ? redireting to
http://wiki.centos.org/SpecialInterestGroup (as now most of the things
outside of Core happens through SIGs)

redirect to SIG, please.
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] A request for help managing wiki permissions

[Manuel Wolfshant]

On 24 octombrie 2014 19:46:35 EEST, Jim Perrin jper...@centos.org wrote:
Long story short, the core team doesn't need to be in the business of
micro-managing wiki permissions. We've not been that good at it during
the best of times, and as the 6.6 build process is showing we've
clearly
let some stuff slip without following up on it appropriately here.


What I'd propose is that 3-4 people who have been around the
distribution a while (perhaps John Dennison and some others) volunteer
to take over handling access to the wiki. This will be implemented as
soon as we have enough trusted people to make it happen.

If you're willing to participate and you're known to us, please
volunteer in this thread.


-- 
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Count me in as well.___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Securing SSH -- Change ports

[Manuel Wolfshant]

On 10/03/2014 04:17 AM, Theodor Sigurjon Andresson wrote:

Yes, when securing your services you*layer*  defenses that could include using 
STO. But when STO is set up in a wrong way it can lead to a security issue. It 
isn't good to protect your services to slow down or prevent an attack by 
opening up a security risk. As in this case changing the port of SSH to  
isn't a good way to include STO. It doesn't matter how big the risk is, you 
just don't want this issue to be there. If you want to include STO in your 
security measures then you have to do it without opening up a security risk 
because you might be opening up a security risk that could be dangerous. In my 
opinion that is the case with SSH to port . Changing the port to an 
privileged unassigned or unused port is a better way to include STO in your 
security measures for SSH. That way you don't have the risk of another user 
listening on your SSH.

I agree with you on two things
- changing the default port is not a security measure, it just lowers 
the noise in the logs and takes you a bit out of the path of automated 
scripts looking for easy targets.
- changing the default port to anything above 1024 creates a greater 
risk than using one below 1024


On the other hand, even if it's easier to start a rouge daemon 
impersonating sshd to listen on a higher port, if you have a malevolent 
user already sniffing on a port - any port - from my point of view you 
already have bigger issues than the potential risk you mentioned.



Incidentally I am a fan of using iptables (recent match) to limit the 
number of admissible attempts from any given IP to connect to sshd ( 
yes, I know, it has nothing to do with the initial concern you raised )
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Testing Wiki migration - asking for testers

[Manuel Wolfshant]

On 09/03/2014 12:10 PM, Fabian Arrotin wrote:

Hi nice people interested in CentOS Docs and wiki !

There were already threads about migrating the wiki to something else
(mediawiki, $other), or staying with moinmoin (what we now have in place).
This mail isn't about that thread (but feel free to start a new one
about that possible migration or not), but about just migrating the
current moinmoin instance from the current machine to a new one.

I've installed a test machine (CentOS 6, with selinux in enforcing mode,
our standard now everywhere)

kudos for using enforcing !




  on which I've installed moinmoin (but same
version as the one running now on wiki.centos.org (so
moin-1.5.8-3.el6.noarch vs moin-1.5.8-2.acls.el4.centos.noarch )

Can I ask all of you to do some intensive tests around that test
instance please ?
So far it seems to work (editing page, login, reset password with email
, etc) but we'd like to be sure before migrating wiki.centos.org

Can I so ask for you collaboration/feedback please ? and surely if it's
a yeah, works for me [TM]:-)
Works for me (login,  edited 
http://wikitesting.centos.org/AdditionalResources/Repositories to bring 
it in sync with the changes I've made last night regarding a repo ). 
However it's still sluggish. Maybe not as much as the old instance but 
still.


Manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] CentOS-docs Digest, Vol 93, Issue 1

[Manuel Wolfshant]

On 08/01/2014 03:09 PM, Sahil Aggarwal wrote:
 Thanks For support.
 One more doubt is that , As Centos 7 major release is launched , now 
 support for centos 6.x where x is latest mirror point release is 
 supported or not ? ? and further 6.y where yx will be released or not .
 You are requested to calrify .

All versions of CentOS are supported for 10 years. Support for CentOS 5 
will end in 2014, for 6 in 2020 and for 7 in 2024.

 M.

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] w.r.t. satan

[Manuel Wolfshant]

On 07/28/2014 08:39 PM, 666threesixes666 wrote:
 This nick is semi anonymous, facebook has a trail leading back to me 
 in this photo.

 https://scontent-a-ord.xx.fbcdn.net/hphotos-xaf1/t1.0-9/394474_209302609153020_1364163998_n.jpg

For all we know, any of these cards 
(https://lh5.googleusercontent.com/_MYks-zls9Jc/SjW7727YrDI/A6Q/tP_mRhSV6zw/s1600/NY%2BMarriage-Hakim%2BNelson.jpg
 
http://img.naij.com/n/07/9/national-id-card_09776.jpg) might be yours as 
well ( or mine ). OK, not mine, some of the subscribers of this list met 
me in real life.


PS: No pun intended but given a sample and an installed gimp I need 30 
min to provide any document you want
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] Are xen and centos incompatible?

[Manuel Wolfshant]

On 06/10/2014 05:44 AM, lee wrote:
[...] and xen just don't go along with each other. The server is all 
on debian now. 

The problem with incompetence is its inability to recognize itself.
-- Orrin Woodward 
https://www.goodreads.com/author/show/249881.Orrin_Woodward, /L.I.F.E. 
Living Intentionally For Excellence 
https://www.goodreads.com/work/quotes/16132299 /


___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] xen setup documentation for centos?

[Manuel Wolfshant]

On 06/06/2014 06:23 AM, lee wrote:
 George Dunlap dunl...@umich.edu writes:

 *I* care about the documentation that didn't work, so that other
 people don't trip over the same thing.  :-)  If you've walked this
 path and become frustrated, there are probably a dozen other people
 who have also walked it and just not said anything.
 To give an example:

 https://www.centos.org/docs/5/html/5.1/Deployment_Guide/s1-networkscripts-static-routes.html


 [root@charon ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
 DEVICE=eth0
 BOOTPROTO=none
 DNS1=192.168.178.20
 IPADDR=192.168.1.1
 NETMASK=255.255.255.255
 NM_CONTROLLED=no
 ONBOOT=yes
 TYPE=Ethernet
 UUID=1b645d25-9f66-4335-ba0b-939cdd9f553f

 [root@charon ~]# cat /etc/sysconfig/network-scripts/route-eth0
 192.168.178.0/24 via 192.168.1.1 eth0

syntax error.  you need a dev before eth0. which actually is useless 
to append anyway because the interface is already specified in the file name


 default 192.168.178.200 dev eth0
syntax error. you miss a via before the IP of the gateway


 [root@charon ~]# service network restart
 Shutting down interface eth0:  [  OK  ]
 Shutting down loopback interface:  [  OK  ]
 Bringing up loopback interface:  [  OK  ]
 Bringing up interface eth0:  Determining if ip address 192.168.1.1 is already 
 in use for device eth0...
 Error: either to is duplicate, or eth0 is a garbage.
explained by the syntax error from the first line in route-eth0


 Error: either to is duplicate, or 192.168.178.200 is a garbage.
explained by the syntax error from the second line in route-eth0

 [  OK  ]
 [root@charon ~]# route -n
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse Iface
 [root@charon ~]#
explained by the fact that your route-eth0 file doesn't contain any 
correct line

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] xen setup documentation for centos?

[Manuel Wolfshant]

On 06/07/2014 03:03 AM, lee wrote:
 Manuel Wolfshant wo...@nobugconsulting.ro writes:
 [..]
 You're right, I overlooked the 'dev'.

 Why doesn't the error message simply say syntax error and perhaps even
 points out that dev might be missing?
Because the program ip is pretty cryptic, despite being way more 
powerful than most people know


 There is no 'to' in the
 configuration file anywhere, and saying that eth0 might be a garbage
 isn't helpful in any way.  This isn't any better than failing silently
 or just printing error.
Each line of the route-eth* file(s) is passed ad-literam to ip route 
commands so all error messages that you see come from ip. Examine 
/etc/sysconfig/network-scripts/ifup-routes for details. In your case, 
you should test the content of route-eth* by using: ip route add 
$EachLineOneByOne



 I would like to make a bug report about this so that the useless error
 message may be changed.  But what package should the report refer to?
You could file a RFE either against iproute which actually triggers the 
messages you've seen or against initscripts (ifup-routes is provided by 
it - you could ask for a better parser ).
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen and Centos 6.5

[Manuel Wolfshant]

On 05/23/2014 12:09 AM, NightLightHosts Admin wrote:
 I used it and it works great.  From what I remember I have to check
 sometimes that the xen kernel is still default.
make sure /etc/sysconfig/kernel suits your needs
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] Installing Java on Centos

[Manuel Wolfshant]

On 07/04/2013 02:37 PM, Olga Maciaszek-Sharma wrote:
 Hello,

 I have recently tried installing Java on Centos 6.4 and have found 
 that the wiki tutorial for this subject is quite outdated (the 
 proposed method doesn't work on the new version as the spec file is 
 outdated and there is no need to rebuild the rpm with nosrc file 
 anymore). I would like to post a tutorial on installing Java on Centos 
 that would be more up-to-date and referring to the newer available 
 versions of both Centos and Java.
Hello


 Please use http://wiki.centos.org/HowTos/JavaRuntimeEnvironment. As 
far as I know it is correct and applies to all current CentOS and Oracle 
Java versions.

 manuel


___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] Xen on CentOS 6.4

[Manuel Wolfshant]

On 05/27/2013 12:10 AM, Robert Dinse wrote:
   What are the advantages / disadvantes of Xen / KVM?

I for one have several machines where I cannot use KVM because the 
processors do not have support for hardware virtualization. Hence using 
xen there.

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] Fwd: Headless VNC Install Disk

[Manuel Wolfshant]

On 05/05/2013 10:36 AM, Manuel Wolfshant wrote:
 On 05/05/2013 05:27 AM, Timothy Lee wrote:

 Anyone who can answer this question regarding the wiki page's content?


 First of all, the questions are in no way related to the content of 
 that wiki page but are general CentOS installation questions.
 Second, both his problems seem to be related to am image which is not 
 complete or correctly downloaded. At the very least Irwan should check 
 the checksum of the downloaded image.

 As a side note: I always install CentOS on my HS20 blades exclusively 
 by using headless VNC ( triggered via PXE ). There are no issues that 
 I know of.


extract from my PXE config:


label centos6.4-i386minimal
 kernel vmlinuz-6.4-i386
 append vnc vncconnect=192.168.130.2 load_ramdisk=1 
initrd=initrd-6.4-i386.img network 
ks=ftp://192.168.120.40/linux/ks-minimalC6.cfg ksdevice=eth1
 MENU LABEL centos ^6.4/i386-minimal



___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] documentation on installing dvd2 in 6.3 x64 release?

[Manuel Wolfshant]

On 11/27/2012 02:04 AM, Edward Brabant wrote:


Hello -
 I've searched the CentOS 6.3 wiki docs (Help, Tips and Tricks, 
HowTo, FAQ, and website search) on how to install the dvd2.iso image 
on an x86-64 machine and can't find any info and the documentation is 
not yet posted for CentOS 6.x.  When the dvd1.iso for 6.3 x86_64 
installs, it does not prompt to install dvd2.iso.
 Please provide a URL which describes how to install the dvd2.iso 
image on an x86-64 machine.


The split between the first and second DVD was made in such a way as to 
minimize the need for the second disk. During a normal installation,  
the second DVD is asked for only if you selected for installation 
packages which are on this disk.


If there is anything on the second disk that you want to install after 
the normal installation completes ( and you do not want or you cannot 
access a CentOS mirror via network)  , you can use yum --disablerepo=\* 
--enablerepo=c6-media to access the content of the disk ( you need to 
mount it first )
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] Package lists for Cloud images

[Manuel Wolfshant]

On 10/15/2012 01:00 PM, Karanbir Singh wrote:
 Hi Guys,

 Hoping to publish some testing images today late evening ( UTC ) - the
 targets I hope to hit are :


[...]

 Also, whats the best way to publish these images in a way that they can
 go away once the test-phase is done ( and ideally we really need them to
 go away )
dev.centos.org ?
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] Wiki improvement

[Manuel Wolfshant]

On 07/21/2012 11:11 PM, Ron Arts wrote:
 Hello list,

 I found an error on the page http://wiki.centos.org/HowTos/InstallFromUSBkey,
 and I wanted to fix it, but appararently I need to follow this procedure.
 The error is you need 20mb on the USB VFAT partition in stead of 10mb
 for the latest CentOS 5.x releases.
I've edited the page and replaced 10 MB with 20 MB.
Thanks for reporting that.

 manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] HowTos/InstallFromUSBkey was: Wiki improvement

[Manuel Wolfshant]

On 07/22/2012 09:37 AM, R P Herrold wrote:
 On Sat, 21 Jul 2012, Ron Arts wrote:

 I found an error on the page http://wiki.centos.org/HowTos/InstallFromUSBkey,
 and I wanted to fix it, but appararently I need to follow this procedure.
 The error is you need 20mb on the USB VFAT partition in stead of 10mb
 for the latest CentOS 5.x releases.

 My wikiname is RonArts.
 edit applied,
you missed  the fstab commands :)


 manuel aka wolfy
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] http://wiki.centos.org/HowTos/postfix

[Manuel Wolfshant]

On 07/20/2012 11:07 PM, Phil Schaffner wrote:
 Ned Slider wrote on 07/20/2012 03:12 PM:
 One issue I see here is that the original howto was written for CentOS-5
 with dovecot 1.x.

 The OP here is clearly using CentOS-6, which uses dovecot 2.x and no
 surprises for guessing that there are a few incompatibilities between
 the config files for dovecot 1 and 2.

 Personally, I'd suggest forking the original article and maintaining
 separate versions for CentOS-5 and CentOS-6, or have separate sections
 within the article for CentOS-5 and CentOS-6 where they differ.

 To the best of my knowledge this list never did agree a mechanism for
 handling documentation differences between product versions. The danger
 is that if we keep editing changes for CentOS-6 into docs for CentOS-5
 we will end up with broken useless docs.

 How do others feel this type of situation should best be handled?
 I'd say it should be decided on a case-by-case basis, but perhaps some
 general guidelines would be helpful.  If differences can be easily
 handled by a note here and there then a separate page is probably not
 justified.  If differences are substantial between major releases, then
 a fork of a new page for the later release may be the best approach.

 Phil
+1 for Phil's approach

 Manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-docs] release notes for 6.3

[Manuel Wolfshant]

Hi people

 I have created the RN6.3 page in the wiki, so as to be sure that we 
do not forget which packages from 6.2/updates are newer than 6.3/media.
 Unfortunately the wiki engine did not allow me to copy/paste the 
acl line from the RN/6.2 page so if you have issues because of that 
we'll need an admin to fix the problem.


 Regards
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Skype's no-redistribution policy

[Manuel Wolfshant]

On 06/23/2012 02:47 PM, Karanbir Singh wrote:
 Hi,

 On 06/23/2012 02:36 AM, Yves Bellefeuille wrote:
 However, Microsoft claims to prohibit redistribution of Skype
 (http://www.skype.com/intl/en-us/legal/terms/tou/ , subsection 4.2).
 Is this different from their previous policy ?


I've read all the page in full once and subsection 4.2 three times and I 
still do not see anything prohibiting us to send people to the rpm. By 
mere saying You can download from... we are NOT redistributing.


___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] Should I switch and if so what is the procedure

[Manuel Wolfshant]

On 10/05/2011 06:06 PM, Rich wrote:
 How hard is it to switch from Xen to KVM?
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Virtualization_Getting_Started_Guide/


___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] Italian translation proposal

[Manuel Wolfshant]

On 09/29/2011 11:55 AM, Gianluca Cecchi wrote:
 On Tue, Sep 27, 2011 at 11:10 PM, Ralph Angenendt wrote:
 [snip]
 I don't understand the issue - just use the edit button on top of that
 page to continue?
 [snip]
 I get an error page with:
 You are not allowed to edit this page.
 Try now.

 Cheers,

 Ralph
 ___

 Ok, I succeeded in creating my home page...
 When I saved it, I still continue to see the edit buttons to edit
 again if I like

 Instead if I go to the work in progress italian release notes page
 http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.0/Italian

 I can't see the edit buttons at all so I don't
 know how to further edit it...
 The first time when the page was created from the TranslationTemplate
 I saw the edit buttons at top, but after the first save operation I wasn't
 able to see them any more


 One question.
 Inside the current release notes page the hyper link for localizations
 (eg German) points to:
 http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.0/German

 while if I understood correctly the general rules for localization, it should 
 be
 http://wiki.centos.org/de/Manuals/ReleaseNotes/CentOS6.0/

 So what is the correct approach? Is it the release notes an exception..?
Include this line, below Traduzioni di queste Note di Rilascio sono 
disponibili in diverse lingue :
[[Include(Manuals/ReleaseNotes/CentOS6.0,,from=##begin-translations, 
to=##end-translations)]]

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Italian translation proposal

[Manuel Wolfshant]

On 09/29/2011 12:06 PM, Manuel Wolfshant wrote:
 [[Include(Manuals/ReleaseNotes/CentOS6.0,,from=##begin-translations, 
 to=##end-translations)]] 
I noticed that you were not making use of any of the booksmarks existing 
in the English version of the RN, so I modified your translation in 
order to use them
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Italian translation proposal

[Manuel Wolfshant]

On 09/29/2011 04:13 PM, Gianluca Cecchi wrote:
 On Thu, Sep 29, 2011 at 12:30 PM, Gianluca Cecchi  wrote:
 [snip]
 When I log in with my GianlucaCecchi login and I go to
 http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.0/Italian
 I see the page but as a normal user, I don't see the control button
 at top, that I instead see when I point to:
 http://wiki.centos.org/GianlucaCecchi
 (edit, edit(GUI).)
 I don't know if it is a matter of ACL definition or what...
 Until this is fixed I can't put any additional change into the page..

 strangely I have the power to edit your translation page (Romanian)
 and the German page, but no way for the Italian one...
 perhaps because it is a new page and not an already existent one?
 or is it just the italian phrase that defaults to generate intrinsic
 inefficiency  (see our government ;-)

 BTW: I see now that the Italian link appears,
I've added it


   but due to its
 brokenness in contents, it would be preferable not to have it until I
 can modify the italian page...
I've commented the link to your page.

(I cannot fix ACLs, we have to wait for Ralph )
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] I would like to contribute to the Wiki

[Manuel Wolfshant]

On 09/29/2011 04:49 PM, Madalin Grigore-Enescu wrote:
 I would be glad to work with Manuel Wolfshant on this.

 Manuel, please let me know if you use any instant messenger client. 
 Maybe that way we can communicate faster and better on this subject 
 using our native language...
https://fedoraproject.org/wiki/ManuelWolfshant



 Also, after reading your answer, I want to add a note to your opinion 
 about Romanian CentOS users not reading romanian translations: Most of 
 the time, I use google to search for specific answers. I bet, more 
 romanian wiki pages will add more results on google.ro searches, 
 naturally driving up more readers in our native language. Of course I 
 may be wrong.
I am involved in the RLUG community since it was created ( '98) and most 
of the people I know would rather read the original. But if you have the 
time to invest in translations, maybe this will change.


 By the other way, for me, translating the wiki will certainly improve 
 my CentOS knowledge. I see this as a way both to learn for myself and 
 doing something positive for the comunity in the same time.

 
 I also have a proposal about the way we should write from now on:
 

 I think we must use romanian diacritics like șțâăî in our 
 translations. This is the correct way to write romanian. I see all the 
 wiki pages are using UTF-8 character set so there will be no technical 
 problems with that. Other from writing faster, i see no reason not to 
 use our language specific diacritics.
There is a long debate around that. As long as a whole page is written 
in one style only ( either with diacritics everywhere or with none ) you 
have my support. Personally I usually avoid diacritics because in many 
cases I had bad experience when reading pages which included them, due 
to missing fonts on the rendering side. Not to mention the large use of 
wrong characters ( ş instead of the correct one, ș)



 Also if you agree with that Manuel my next step will be to translate 
 the following page:

 http://wiki.centos.org/Documentation

 into

 http://wiki.centos.org/ro/Documentation

Sure, by all means.


___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] I would like to contribute to the Wiki

[Manuel Wolfshant]

On 09/29/2011 12:57 AM, Ralph Angenendt wrote:
 On 09/28/2011 03:20 PM, www.alopia.com wrote:
 Hello!

 My username is: MadalinGrigoreEnescu
 The proposed subject of my Wiki contribution is: I want to contribute on 
 translating CentOS Wiki pages in Romanian language (ro)
 Can you talk to Manuel (he reads here and probably sees that, too), to
 develop some strategy for that?
 I guess that reviewing each other's edits would be the best way to 
go. Another hand for the ro translations would be awesome. But of course 
it depends on Madalin's interests and plans.
 FWIW, a long time ago i started http://wiki.centos.org/ro , but I 
found out that no one really cared about the content, everybody reads 
the English version anyway.
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-docs] release notes for CentOS 5.7

[Manuel Wolfshant]

Hello

 With CentOS 5.7 around the corner, I've created the initial page 
for its Release Notes.As usual, please fix / adjust / correct as needed.


 manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] http://wiki.centos.org/HowTos/JavaRuntimeEnvironment

[Manuel Wolfshant]

On 08/18/2011 03:21 PM, Phil Schaffner wrote:
 Manuel Wolfshant wrote on 08/15/2011 12:53 PM:
 On 08/15/2011 06:42 PM, Phil Schaffner wrote:
 ...
 I'd go for a separate page for
 HowTos/JavaDevelopmentKit but could be persuaded otherwise.

 Then maybe a single Howto/Java page, with separate links to JRE and JDK ?
 Makes sense, and I would propose that would replace the current content
 on http://wiki.centos.org/HowTos/JavaOnCentOS
My thoughts exactly !


   - which begs the questions:

 1. What else besides links goes on the higher-level page?
Explanation on the intent of the page


 2. What should be preserved, if anything, from the current page?
maybe the how to create your own packages by using the old .nosrc.rpm 
from jpackage part. the rest would be obsoleted.

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] http://wiki.centos.org/HowTos/JavaRuntimeEnvironment

[Manuel Wolfshant]

On 08/18/2011 05:52 PM, R P Herrold wrote:
 On Thu, 18 Aug 2011, Manuel Wolfshant wrote:

 Makes sense, and I would propose that would replace the current content
 on http://wiki.centos.org/HowTos/JavaOnCentOS
 My thoughts exactly !
 I am missing something ... a review of google inlinks
 indicates this page is widely referenced by third party sites.
 Casually blowing this away without preserving at least parts
 seems ill considered change for its own sake
We are not blowing it away. It will remain the land point which will 
further reference JRE and JDK. Although, now that I started to fill in 
the JDK page, I am tempted to join them. But we should discuss that once 
we have more info to play with in the wiki . For now I am trying to 
bring the new JDK page to life ( and refine the JRE one)
 The top part by me remains a general and valid description of
 a method for getting Oracle's / Sun Java running ... not
 perhaps the easiest in light of some later changes, and
 perhaps not the 'ight' solution in light of the growth in
 maturity of openjdk ... but that
The top part written by you is exactly what we'll refine.
The last round of packages from Oracle are quite sane. You download a 
$STUFF.bin, run it and
- it will ask to agree to the license
- expand into a bunch of rpm packages:
jdk-6u27-linux-i586.rpm
sun-javadb-client-10.6.2-1.1.i386.rpm
sun-javadb-common-10.6.2-1.1.i386.rpm
sun-javadb-core-10.6.2-1.1.i386.rpm
sun-javadb-demo-10.6.2-1.1.i386.rpm
sun-javadb-docs-10.6.2-1.1.i386.rpm
sun-javadb-javadoc-10.6.2-1.1.i386.rpm
- install all the packages ( if you have the needed rights)

What is still needed is a clean solution to add that to the alternatives 
system
 The bottom remains a rotting trainwreck needing maintenance
 every time Oracle issues an update ... shocking.  Who could
 have predicted that?

The old method to create several rpms from the tar bundle ( using 
jpackage's nosrc ) is completely obsolete.


rant mode on Did I mention that moinmoin's syntax is awful and I 
cannot believe I even thought about using it inside the company I work 
for ? /rant mode off
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] http://wiki.centos.org/HowTos/JavaRuntimeEnvironment

[Manuel Wolfshant]

On 08/15/2011 06:42 PM, Phil Schaffner wrote:
 Manuel Wolfshant wrote on 08/11/2011 08:29 PM:
 Hi all

According to a report made in #centos, the procedure described at
 http://www.if-not-true-then-false.com/2010/install-sun-oracle-java-jdk-jre-7-on-fedora-centos-red-hat-rhel/
 works OK for jdk 1.7
It looks pretty similar to
 http://wiki.centos.org/HowTos/JavaRuntimeEnvironment so I updated our
 page to reflect the fact the jre-1.7 can be installed using the
 procedure already described in the wiki.
 Looks good.

 Any objections on including jdk
 ( and maybe replacing the links to the binary packages with
 http://www.oracle.com/technetwork/java/javase/downloads/index.html. so
 that the user can choose between 1.6/1.7 jre/jdk )?
 That would no longer fit the current name of the page, and might lead to
 some confusion.  I'd go for a separate page for
 HowTos/JavaDevelopmentKit but could be persuaded otherwise.

Then maybe a single Howto/Java page, with separate links to JRE and JDK ?

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-docs] http://wiki.centos.org/HowTos/JavaRuntimeEnvironment

[Manuel Wolfshant]

Hi all

 According to a report made in #centos, the procedure described at 
http://www.if-not-true-then-false.com/2010/install-sun-oracle-java-jdk-jre-7-on-fedora-centos-red-hat-rhel/
 
works OK for jdk 1.7
 It looks pretty similar to 
http://wiki.centos.org/HowTos/JavaRuntimeEnvironment so I updated our 
page to reflect the fact the jre-1.7 can be installed using the 
procedure already described in the wiki. Any objections on including jdk 
( and maybe replacing the links to the binary packages with 
http://www.oracle.com/technetwork/java/javase/downloads/index.html. so 
that the user can choose between 1.6/1.7 jre/jdk )?
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] Suggestions to improve this minimal kickstart config for CentOS 6?

[Manuel Wolfshant]

On 07/22/2011 07:01 PM, Kartik Subbarao wrote:
 On 07/21/2011 09:51 AM, Manuel Wolfshant wrote:
 http://wiki.centos.org/TipsAndTricks/KickStart
   
 Does anyone on this list have write access to that Wiki page? Since it's
 the #1 google search result for centos kickstart, it'd be ideal to
 have it linked from there.
 Enjoy.

 Thanks Manuel, I'm sure this will be of help to many folks!!

 One suggestion -- when I deployed the ks-minimalC6.cfg, there were still
 some -firmware packages that got installed and were not removed by the
 kickstart process. I noticed that you explicitly remove various firmware
 packages by name with the '-' notation. Another approach would be to
 remove them all programmatically in a %post section, like this:

 %post
 rpm -e $(rpm -qa | grep -i \\-firmware | grep -v kernel-firmware)

And by the way, the above can rewritten in a shorter form:
  rpm -e $( rpm -qa \*firmware | grep -v kernel)

rpm -qa will enumerate all packages but in fact you want only the 
firmware ones. So you run an useless grep to filter them when in fact 
rpm can do that for you in the first place.



___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Suggestions to improve this minimal kickstart config for CentOS 6?

[Manuel Wolfshant]

As of ks file size: who cares ? You create it once and use it as
 many times as needed. An extra dozen or hundreds of bytes / couple of
 lines are not significant in this context
 That wasn't my point :-) I guess I could have said simpler rather than
 smaller to make my point clearer. The less stuff that has to be
 manually specified in the file, the less work needed from a maintenance
 point of view. Also, it's simpler from a conceptual standpoint to see
 what's happening.


Ah, I am sorry, I misunderstood you. Yes, you are absolutely correct:  
the smaller the number of directives in the file, the simpler to maintain.
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] C6 needs a FAQ entry for GUI setup ( tweaking xorg.conf )

[Manuel Wolfshant]

On 07/22/2011 01:07 AM, R P Herrold wrote:
 On Fri, 22 Jul 2011, Manuel Wolfshant wrote:

  As some of you probably already know, since RHEL 6 xorg.conf does
 not exist any more by default.
 it is not created by default any more, but is honored if
 present is my understanding, as for multi-head, and for
 solving tricky scan problems

Correct. Which is why I think that the entry should contain basics: 
create a new xorg.conf , adjust THIS section to modify the resolution


 Based on the questions asked on IRC, I
 think it would be a good idea to add a FAQ entry on how to create one (
 and how to modify the resolution on systems where the defaults are not OK).
 a pretty wide topic -- as I recall there is an option to emit
 the config file.  but addressing general X setup is robably
 not something we want to do locally, so much as simply point
 to the proper upstream archives?
Absolutely. I do not see the X manual replicated here. Just a 5 liner, 
use $THISCOMMAND to create the file, edit $THISOTHER section to adjust 
the resolution. For anything else, read $THAT.



  Is anyone with prior experience in this domain willing to do it ?
 Otherwise I'll have to compile one myself...
 I have some notes -- I'll discuss in IRC w you tomorrow
excellent. thank you

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] Suggestions to improve this minimal kickstart config for CentOS 6?

[Manuel Wolfshant]

On 07/21/2011 01:43 PM, Dennis Jacobfeuerborn wrote:
 On 07/20/2011 01:50 PM, Manuel Wolfshant wrote:
 On 07/20/2011 02:37 PM, Dennis Jacobfeuerborn wrote:
 Oh, I believe you I'm just puzzled why I need the package and you 
 don't.
 Can you post an rpm -qa|sort of the final Package list you have in 
 the
 installed System?

 Regards,
 Dennis

 Already done that in my first mail.
 http://lists.centos.org/pipermail/centos-virt/attachments/20110720/c78c2c2d/attachment.txt
  



 Sorry, I only saw the kickstart file but didn't notice that there was 
 a package list attached as well.
 Anyway it seems I need the system-config-firewall-base package because 
 I create a live image that I boot directly. After doing a regular 
 install with the same kickstart I can login normally even without that 
 package. Still no clue though why that would make a difference or what 
 that particular package has to do with logins.

 Regards,
   Dennis
You are 100% correct. Today I added back the package to the list. I 
noticed that logins continue to work after the package is removed but 
not after reboot. Go figure. Especially as I see nothing obvious in a 
rpm -ql

I'll leave it in for now and revisit, time permitting.

 Manuel


___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Suggestions to improve this minimal kickstart config for CentOS 6?

[Manuel Wolfshant]

On 07/20/2011 04:48 PM, Kartik Subbarao wrote:
 On 07/19/2011 05:36 PM, Manuel Wolfshant wrote:
 Try the attached ks. It installs around 180 packages. libselinux-utils
 is in because I find it mandatory to be able to modify the selinux
 configuration of an existing system.

 Thanks for the info. I created a VM with this config and it took up 
 about 512MB of disk space, which is higher than the kickstart file 
 that I posted (about 460MB).
you removed selinux and also used rpm -e --nodeps which I would never 
promote (even if I also use on occasions).
ditch from my list the packages which install firmware and you'll end up 
at roughly the same size as yours. anyway my target was never minimal 
space on disk (today even CFs and SSD are several times larger than what 
the ks installs ) but minimal number of packages while still maintaining 
out of the box all the proper functionality ( or at least my vision on 
it), including for servers with real storage behind them ( brocade, etc 
). and I emphasize again: including selinux tools.


 I'm running x86_64 so I'll probably see different sizes than your 
 system which appears to be i686.
my ks works on both, just adjust the repository used for install



 In any event, thanks for taking the time to post your kickstart file. 
 It helps me validate that what I have is reasonably minimal, that I'm 
 probably not missing any major sources of size reductions. 
welcome

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Suggestions to improve this minimal kickstart config for CentOS 6?

[Manuel Wolfshant]

On 07/21/2011 02:36 AM, JDF. Franklin wrote:
 For what it's worth here are a few more tools that I include due to
 fairly minimal impact, but are assumed by many 3rd party scripts for
 example:

 rsync
 unzip
 wget

 And personally I like these for local setup though they add a big more space:
 ntp
 elinks
 lsof
 nmap
 denyhosts
 yum-utils
 autofs
 nfs-utils
 nss_db
 nss-pam-ldapd
 nss-tools
 openldap-clients
 pam_ldap
Thank you for your suggestions. I want to keep the minimal image really 
minimal so I am not going to add to it anything but hardware drivers. On 
the other hand, I will keep your list handy and adjust accordingly (if 
space allows ) the content of the Light Weight Server CD ( which is 
still under work)

For what is worth, my minimal kickstart is now available as ks-minimalC6 
at https://nazar.karan.org/cgit/bluecain/tree/

 manuel
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Suggestions to improve this minimal kickstart config for CentOS 6?

[Manuel Wolfshant]

On 07/20/2011 12:15 AM, Kartik Subbarao wrote:

On 07/19/2011 12:36 PM, Kartik Subbarao wrote:

rpm -e $(rpm -qa |grep -i firmware)

This should be changed to:
rpm -e $(rpm -qa | grep -i firmware | grep -v kernel-firmware)

Since apparently kernel depends on kernel-firmware.
Try the attached ks.  It installs around 180 packages. libselinux-utils 
is in because I find it mandatory to be able to modify the selinux 
configuration of an existing system.


There are a few packages left which can be removed if you insist:
- the firmware packages if you do not use that specific hardware ( 
atmel, brocade, qlogic ).
- yum-presto if you prefer to always download full rpm packages instead 
of deltas

- which, acl, attr


install
text
reboot
#cdrom
url --url http://wolfy/centos/os/x86_64/
lang en_US.UTF-8
keyboard us
skipx
network --device eth0 --bootproto dhcp
rootpw --iscrypted  $PUTYOURENCRYPTEDPASSWORDHERE
firewall --enabled
selinux --enforcing
authconfig --enableshadow --enablemd5
timezone Europe/Amsterdam
bootloader --location=mbr
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
clearpart --all --initlabel
part /boot --fstype ext3 --size=250
part pv.2 --size=5000 --grow 
volgroup VolGroup00 --pesize=32768 pv.2
logvol / --fstype ext4 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=256 --grow 
--maxsize=512
repo --name=updates --baseurl=http://PATHTOAVALIDREPO

%packages --nobase --excludedocs
coreutils
yum
rpm
e2fsprogs
lvm2
grub
openssh-server
openssh-clients
dhclient
yum-presto
-atmel-firmware-1.3-7.el6.noarch
-b43-openfwwf-5.2-4.el6.noarch
-cronie-1.4.4-2.el6.i686
-cronie-anacron-1.4.4-2.el6.i686
-crontabs-1.10-32.1.el6.noarch
-ipw2100-firmware-1.3-11.el6.noarch
-ipw2200-firmware-3.1-4.el6.noarch
-ivtv-firmware-20080701-20.2.noarch
-iwl1000-firmware-128.50.3.1-1.1.el6.noarch
-iwl3945-firmware-15.32.2.9-4.el6.noarch
-iwl4965-firmware-228.61.2.24-2.1.el6.noarch
-iwl5000-firmware-8.24.2.12-3.el6.noarch
-iwl5150-firmware-8.24.2.2-1.el6.noarch
-iwl6000-firmware-9.176.4.1-2.el6.noarch
-iwl6050-firmware-9.201.4.1-2.el6.noarch
-libertas-usb8388-firmware-5.110.22.p23-3.1.el6.noarch
-xorg-x11-drv-ati-firmware
-mysql-libs-5.1.47-4.el6.i686
-postfix-2.6.6-2.el6.i686
-rt61pci-firmware-1.2-7.el6.noarch
-rt73usb-firmware-1.8-7.el6.noarch
-sudo-1.7.2p2-9.el6.i686
-sysstat-9.0.4-11.el6.i686
-yum-utils-1.1.26-11.el6.noarch
-zd1211-firmware-1.4-4.el6.noarch
-info
-system-config-firewall-base
%end
%post
%end
acl-2.2.49-4.el6.i686
aic94xx-firmware-30-2.el6.noarch
atmel-firmware-1.3-7.el6.noarch
attr-2.4.44-4.el6.i686
audit-2.0.4-1.el6.i686
audit-libs-2.0.4-1.el6.i686
authconfig-6.1.4-6.el6.i686
basesystem-10.0-4.el6.noarch
bash-4.1.2-3.el6.i686
bfa-firmware-2.1.2.1-2.el6.noarch
binutils-2.20.51.0.2-5.11.el6.i686
bzip2-1.0.5-6.1.el6.i686
bzip2-libs-1.0.5-6.1.el6.i686
ca-certificates-2010.63-3.el6.noarch
centos-release-6-0.el6.centos.2.i686
checkpolicy-2.0.22-1.el6.i686
chkconfig-1.3.47-1.el6.i686
coreutils-8.4-9.el6.i686
coreutils-libs-8.4-9.el6.i686
cpio-2.10-9.el6.i686
cracklib-2.8.16-2.el6.i686
cracklib-dicts-2.8.16-2.el6.i686
curl-7.19.7-16.el6.i686
cyrus-sasl-lib-2.1.23-8.el6.i686
dash-0.5.5.1-3.1.el6.i686
db4-4.7.25-16.el6.i686
db4-utils-4.7.25-16.el6.i686
dbus-glib-0.86-5.el6.i686
dbus-libs-1.2.24-3.el6.i686
device-mapper-1.02.53-8.el6.i686
device-mapper-event-1.02.53-8.el6.i686
device-mapper-event-libs-1.02.53-8.el6.i686
device-mapper-libs-1.02.53-8.el6.i686
dhclient-4.1.1-12.P1.el6.i686
diffutils-2.8.1-28.el6.i686
dracut-004-32.el6.noarch
dracut-kernel-004-32.el6.noarch
e2fsprogs-1.41.12-3.el6.i686
e2fsprogs-libs-1.41.12-3.el6.i686
efibootmgr-0.5.4-8.el6.i686
elfutils-libelf-0.148-1.el6.i686
ethtool-2.6.33-0.3.el6.i686
expat-2.0.1-9.1.el6.i686
file-libs-5.04-5.el6.i686
filesystem-2.4.30-2.1.el6.i686
findutils-4.4.2-6.el6.i686
fipscheck-1.2.0-4.1.el6.i686
fipscheck-lib-1.2.0-4.1.el6.i686
gamin-0.1.10-9.el6.i686
gawk-3.1.7-6.el6.i686
gdbm-1.8.0-36.el6.i686
glib2-2.22.5-5.el6.i686
glibc-2.12-1.7.el6.i686
glibc-common-2.12-1.7.el6.i686
gmp-4.3.1-7.el6.i686
gnupg2-2.0.14-4.el6.i686
gpgme-1.1.8-3.el6.i686
grep-2.6.3-2.el6.i686
grub-0.97-68.el6.i686
grubby-7.0.15-2.el6.i686
gzip-1.3.12-18.el6.i686
hwdata-0.233-1.el6.noarch
info-4.13a-8.el6.i686
initscripts-9.03.17-1.el6.centos.i686
iproute-2.6.32-10.el6.i686
iptables-1.4.7-3.el6.i686
iptables-ipv6-1.4.7-3.el6.i686
iputils-20071127-13.el6.i686
kbd-1.15-11.el6.i686
kbd-misc-1.15-11.el6.noarch
kernel-2.6.32-71.el6.i686
kernel-firmware-2.6.32-71.el6.noarch
keyutils-libs-1.4-1.el6.i686
krb5-libs-1.8.2-3.el6.i686
less-436-4.el6.i686
libacl-2.2.49-4.el6.i686
libattr-2.4.44-4.el6.i686
libblkid-2.17.2-6.el6.i686
libcap-2.16-5.2.el6.i686
libcap-ng-0.6.4-3.el6.i686
libcgroup-0.36.1-6.el6.i686
libcom_err-1.41.12-3.el6.i686
libcurl-7.19.7-16.el6.i686

Re: [CentOS-docs] CentOS 6 (and 5.6) doc on http://www.centos.org/docs

[Manuel Wolfshant]

On 07/12/2011 12:57 AM, Ralph Angenendt wrote:
 Am 11.07.11 20:29, schrieb Ed Heron:

This could create more traffic on the wiki.  Is bandwidth or machine
 time a concern?
 Document type. The wiki is not really meant to serve, version, edit and
 - well - import foreign formats. You can do so if a page needs an
 attachement, but I don't really want to use it as storage for foreign
 formats.

 I don't really know what you all want to do with the documents. We can
 use them as is - and as we don't change them contentwise, I'm not sure
 why we should change artwork on those.

I am more into creating some form of redirect from docs.c.o to 
upstream's relevant docs.

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-docs] initial page for Centos 6 FAQ

[Manuel Wolfshant]

Hello

 In preparation of the soon-to-arrive Centos 6, I have created the 
http://wiki.centos.org/FAQ/CentOS6 page and added to it the explanation 
for the disappearance of boot.iso.
 As usual, please help in keeping the documentation updated / 
corrected / etc .


 Manuel

PS: I did not add the reference to new page in the main FAQ page, I am 
waiting for the official release of the distro.
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Very first contact with docs may confuse

[Manuel Wolfshant]

On 06/29/2011 02:50 PM, BlessJah wrote:
 Hi,

 This is my very first time using CentOS and I find documentation a little bit 
 confusing.

 For example, I don't know which iso image suits my needs, isn't adding big, 
 shining red link READ THIS IF YOU DON'T KNOW WHICH ISO SHOULD YOU CHOOSE a 
 good idea?
Hello

If you go to wiki.centos.org = Download ( the top link in the middle of 
the page ) you will notice in the lower part of the page a paragraph 
named Variety of ISO images.


 'README' file on mirrors with instructions would also be nice. If there 
 already is one, I wasn't able to find it, shouldn't it be bigger?

 I would also expect something like begginer guide or start here on the 
 main page of wiki (and on main page of centos).
Well, thing is that due to the very nature of the goal of existence of 
CentOS,  all the documentation for RedHat applies almost unmodified to 
CentOS. Hence the large number of references to their documentation that 
you have undoubtedly found  in our wiki. And the reason that the 
documentation is mainly at 
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/

   I think ArchLinux wiki, and it's Begginer Guide and Official 
 Installation Guide are good examples, how it can be done. Both leads user 
 through process of getting, installing and configuring system.
Thank you for your suggestions. I'll take a look and discuss with the 
other members of the doc team what can be done to improve our users' 
experience.

 Manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] New to virtualization - can't use more than one CD when installing a new VM

[Manuel Wolfshant]

On 06/28/2011 02:07 AM, Steve Campbell wrote:

Why not use a DVD image in /var/lib/xen/images?


 Our company blocks bittorents due to abuse. I believe the DVD ISOs are now
 taking up two DVDs, so I'm not sure how I'd do this either. I'll research 
 this a
 little more as I'm aware I can download the ISOs from the Japanese mirrors.

the second ISO is not needed at install time. it contains only 
additional language support for OpenOffice

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] initial page for 6.0 RN

[Manuel Wolfshant]

On 06/23/2011 02:54 PM, Lucas do Amaral - Linux Sys. Admin (IFCE) wrote:

Exept I cant create a new page ;/

You are not allowed to edit this page.


I've tried to follow the pattern and user this url:
http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.0/BrazilianPortuguese?action=edit


You have to create an account in the wiki and after that ask for editing 
permissions via this list. The rules that we try to follow for account 
names are at 
http://wiki.centos.org/Contribute#head-42b3d8e26400a106851a61aebe5c2cca54dd79e5



___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] initial page for 6.0 RN

[Manuel Wolfshant]

On 06/23/2011 07:28 PM, Markus Falb wrote:
 On 18.6.2011 20:19, Manuel Wolfshant wrote:
 Hello

   I've created the first version of the ReleaseNotes page for CentOS
 6.0 in the wiki. As usual, corrections / additions / translations are
 welcome.
 I found one minor issue

 In section 2. Introduction

 Welcome to the CentOS 6.0 release. CentOS is an Enterprise-class Linux
 Distribution derived from sources freely provided to the public by our
 Upstream OS Provider (UOP)[1].

 The footnote [1] is missing.
Hello

 thank you for notifying us. I fixed it

 Manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] Recommendations, please

[Manuel Wolfshant]

On 06/23/2011 06:28 PM, Alain Péan wrote:
 Le 23/06/2011 17:16, R P Herrold a écrit :
 I did not say the CentOS project was ** going to ship **
 xen; I said:
  The sources that will become CentOS 6 ** will run **
  xen.org virtualization as a dom0, and KVM ** may be **
  excluded

 CentOS proper at the 6 level will ship KVM as that tracks the
 upstream, warts and all

 I must say that the meaning of your message is not clear for me. What is
 the difference for you between The sources that will become CentOS 6,
 and CentOS proper ? What do you have in mind ? Why KVM may be excluded ?
Without implying that I can read his mind, I guess he meant People with 
enough skills will be able to tweak C6 to use xen as Dom0

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Recommendations, please

[Manuel Wolfshant]

On 06/23/2011 06:54 PM, Tom Bishop wrote:
 Russ if you have time can you elaborate more about why you are 
 continuing to go down the Xen path, I for one would love to hear the 
 why's and what for.  I can understand the hardware requirements, and I 
 know xen is generally going to be faster but my small requirements 
 have decided to start moving things to KVM since that is the direction 
 of the upstream...would welcome your opinions if you have time 
 available...Thanks in advance :)

I'll give you my reasons :
- existing infra, setup and knowledge
- RH gave up promoting xen because it was acquired by a competitor, not 
because it was not good ( or worse ) than kvm


___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] initial page for 6.0 RN

[Manuel Wolfshant]

On 06/22/2011 06:40 PM, Lucas do Amaral - Linux Sys. Admin (IFCE) wrote:
 Can I translate to PT-BR ? :D
Why not? We welcome translators.



 On Wed, Jun 22, 2011 at 12:37 PM, Ricardo David Carrillo Sanchez 
 dominus@gmail.com mailto:dominus@gmail.com wrote:

 Thank's

 Saludos
 -- 

 Ricardo David Carrillo Sánchez
 Administrador de Sistemas
 Analista de Seguridad Informática
 PGP/GPG key fingerprint: 7AD4 6D7B A09B C010 8445  31F4 92C2 DDFA
 2DA0 E376
 PGP/GPG public key: https://insecure-it.com.mx/keys/dominus.ceo.asc



 On Wed, Jun 22, 2011 at 10:36 AM, Akemi Yagi amy...@gmail.com
 mailto:amy...@gmail.com wrote:

 On Wed, Jun 22, 2011 at 8:33 AM, Ricardo David Carrillo Sanchez
 dominus@gmail.com mailto:dominus@gmail.com wrote:
 
  Hi,
  Could you send the link to see the Release Notes ..? or wiki
 section

 Here:

 http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.0



___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-docs] initial page for 6.0 RN

[Manuel Wolfshant]

Hello

 I've created the first version of the ReleaseNotes page for CentOS 
6.0 in the wiki. As usual, corrections / additions / translations are 
welcome.


 Manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] initial page for 6.0 RN

[Manuel Wolfshant]

On 06/18/2011 10:47 PM, Cody Jackson wrote:
 On 6/18/11, Manuel Wolfshantwo...@nobugconsulting.ro  wrote:
 Hello

   I've created the first version of the ReleaseNotes page for CentOS
 6.0 in the wiki. As usual, corrections / additions / translations are
 welcome.

 Hi;

 I just glanced at this after breakfast,
thanks !


 and I spotted a few
 grammatical errors you might wish to change:

 Section 2:
 upstream vendors redistribution policy should probably be upstream
 vendor's redistribution policy. (In fact, I notice this is on the 5.6
 release notes page as well.)
fixed in both places


 Section 6.3:
 Even as an inexperienced CentOS user we can use your help sounds a
 bit like the release team is comprised of inexperienced CentOS users.
 It is, of course, not! Perhaps something like Even as an
 inexperienced CentOS user, you can help the CentOS project! would
 work better?
uhm. I'll leave that to people with more English knowledge than me. It 
looks fine from where I stand.

 This line made me pause as well:
 Because we like to know what problems you encountered, if you had
 problems finding specific information, how you would improve
 documentation so it becomes more accessible.

 At the least, it should have a question mark at the end,
uhmm.. no. It's a enumeration of things we'd like to be informed of, not 
a question. it's not Would we like to know ... ? but we like to know 
a b and c. there is a difference between: We like to know. What 
problems ..? How would you? and we like to know [...] how would you


   although it
 is an awkward question. How does one improve documentation? The
 average user probably will not know. It might be better to include
 some specific advice here: get in touch with the dev team, contribute
 your own documentation, etc.
it's described exactly one paragraph below :)

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Wiki error

[Manuel Wolfshant]

On 06/03/2011 06:12 AM, Emmanuel Noobadmin wrote:
 I was following instructions in the wiki here
 http://wiki.centos.org/HowTos/CreateLocalMirror
 to create a local mirror for testing VMs instead of hitting the public 
 mirrors.

 However, I could not mount the NFS share in the guest. Error logged on
 the host was:
 request to export an unmounted filesystem: /share

 After some googling, I found this discussion
 http://www.ibm.com/developerworks/forums/thread.jspa?threadID=311075
 which indicates that the problem is with this part in the wiki:

 cat  /etc/exports
 /share  192.168.1.0/24(rw,mountpoint)

 The option mountpoint should not be specified for a directory.

 I was able to mount the NFS share after removing it. Could somebody
 else verify and update the wiki if confirmed?

Would you have respected the recipe ad litteram ( i.e. use /share as 
mount point instead of /mnt ) it would have worked without issues.
But I give you that, in the given context the monutpount restriction is 
probably not needed.

 Manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] New page: HowTos/JavaRuntimeEnvironment

[Manuel Wolfshant]

On 06/03/2011 10:18 PM, Phil Schaffner wrote:

http://wiki.centos.org/HowTos/JavaRuntimeEnvironment

Did not make it DRAFT as it has evolved from old pages, has been well
tested, and is near perfect. :-)

Constructive criticism is, as usual, solicited and welcomed.

Excellent article !
I've made the following modifications to it:
- replaced references to jre-u24 with u25 ( which was used in some 
places but not everywhere )

- took advantage of the fact that jre creates a symlink named latest:

   [wolfy@wolfy ~]$ ll /usr/java/
   total 4
   lrwxrwxrwx. 1 root root   16 Mar  2 12:17 default - /usr/java/latest
   drwxr-xr-x. 7 root root 4096 Mar  2 12:18 jre1.6.0_23
   lrwxrwxrwx. 1 root root   21 Mar  2 12:17 latest -
   /usr/java/jre1.6.0_23

which can make upgrading much easier, as future versions of jre will 
update the symlink but this will not require tweaking the alternatives 
links.


manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] New page: HowTos/JavaRuntimeEnvironment

[Manuel Wolfshant]

On 06/03/2011 10:56 PM, Phil Schaffner wrote:
 Alan Bartlett wrote on 06/03/2011 03:32 PM:
 One comment. I thought linkage of the libjavaplugin_jni.so file is redundant?
 May be superstitious behavior on my part.  I saw it recommended
 somewhere to use both and have followed that, but it seems to work fine
 without the libjavaplugin_jni.so link, but the link does not seem to
 cause problems.  That can be deleted if not needed.
I am 100% sure that on x86_64 libnpjp2.so is enough (that's what I use). 
On the other arch however, if I am not mistaken (I have no i386 system 
handy for testing until Monday) I am accustomed to using  
libjavaplugin_jni .
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] New page: HowTos/JavaRuntimeEnvironment

[Manuel Wolfshant]

On 06/04/2011 01:42 AM, Alan Bartlett wrote:
 On 3 June 2011 23:34, Manuel Wolfshantwo...@nobugconsulting.ro  wrote:
 On 06/03/2011 10:56 PM, Phil Schaffner wrote:
 Alan Bartlett wrote on 06/03/2011 03:32 PM:
 One comment. I thought linkage of the libjavaplugin_jni.so file is 
 redundant?
 May be superstitious behavior on my part.  I saw it recommended
 somewhere to use both and have followed that, but it seems to work fine
 without the libjavaplugin_jni.so link, but the link does not seem to
 cause problems.  That can be deleted if not needed.
 I am 100% sure that on x86_64 libnpjp2.so is enough (that's what I use).
 On the other arch however, if I am not mistaken (I have no i386 system
 handy for testing until Monday) I am accustomed to using
 libjavaplugin_jni .
 Just for you, Wolfy, freshly harvested from a working 32-bit system --

 [quote]
 [ajb@GX1 plugins]$ pwd
 /usr/lib/mozilla/plugins
 [ajb@GX1 plugins]$ ls -1
 libflashplayer.so
 libnpjp2.so
 mplayerplug-in-dvx.so
 mplayerplug-in-dvx.xpt
 mplayerplug-in-qt.so
 mplayerplug-in-qt.xpt
 mplayerplug-in-rm.so
 mplayerplug-in-rm.xpt
 mplayerplug-in.so
 mplayerplug-in-wmp.so
 mplayerplug-in-wmp.xpt
 mplayerplug-in.xpt
 nsdejavu.so
 [ajb@GX1 plugins]$
 [/quote]

 Alan.
great, thanks. I've updated the wiki page and left only libnpjp2.

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Request to Edit Wiki

[Manuel Wolfshant]

On 05/19/2011 01:02 AM, Mike Karasoff wrote:


Hello,

I would like to contribute to the Wiki.  [...] would also like to add 
information and tips on setting up CentOS machines for FPGA 
(Quartus/ISE/Modelsim) development.


Would you mind sharing what you have in mind, as I am a bit confused on 
one hand and extremely interested on the other hand ? We make heavy use 
of  Modelsim | Questa / Specman / VCS and all the centos setup is more 
or less similar to


MGC_HOME=/apps/questasim/linux/mgls;export MGC_HOME
export PATH=${PATH}:/apps/questasim/linux
export MGLS_LICENSE_FILE=1704@ls4
export LICENSE_QUEUEING=yes

In other words, nothing Centos specific, everything works by default.

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Proposal for a new page - NFS port locking

[Manuel Wolfshant]

On 05/03/2011 02:31 PM, Steve Barnes wrote:
 G'day

 Further to a little discussion on #centos-social IRC, I'd like to put 
 together a wiki page that describes the steps required to lock-down the ports 
 used by NFS. I expect it'll be quite short, with
 details on which NFS related config files to edit and a short iptables 
 excerpt that covers the relevant ports to allow. I'm thinking this could go 
 under HowTos -  Security?

 Unless there's a more suitable area, I can work on the initial scratch 
 version in my home page area (which I don't presently have permission to 
 edit).
I suggest to add the info to the already existing 
http://wiki.centos.org/HowTos/OS_Protection page ( which should be 
renamed to something with security in name, I always need a couple of 
minutes to find this page if I do not have my bookmarks handy :)  )
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] Where is my qemu command?

[Manuel Wolfshant]

On 04/27/2011 02:31 PM, Kai Schaetzl wrote:
 I'm so glad we are still on Xen :-) Especially with para-virt CentOS
 running in all the VMs, anyway, it seems hardly to be beaten.
except that we lack a lot of the new goodies. starting with 
deduplication and proper balooning
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Extract ip address from a kvm guest

[Manuel Wolfshant]

On 04/23/2011 09:27 PM, carlopmart wrote:

 Arpwatch is a correct solution when host and guests are in the same
 network, but in my environment, they are in different nets with a
 firewall in the middle...
I run arpwatch on the core router which sits between all VLANs

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] Some questions: Release Notes CentOS 5.6

[Manuel Wolfshant]

On 04/14/2011 12:24 PM, Timothy Lee wrote:
 Dear all,
 Actually, I would also like to have translations section included.
 There's no need to have languages localised. I could happily live with:

* [:Manuals/ReleaseNotes/CentOS5.6/BrazilianPortuguese:Português do 
 Brasil] - [:CleberSouza:Cleber Paiva de Souza]
* [:Manuals/ReleaseNotes/CentOS5.6/Chinese:简体中文] - [:TimothyLee:Timothy 
 Lee]
* [:Manuals/ReleaseNotes/CentOS5.6/ChineseTW:繁體中文] - [:TimothyLee:Timothy 
 Lee]
* [:Manuals/ReleaseNotes/CentOS5.6/Czech:Česky] - [:DavidHrbac:David 
 Hrbáč]
 ### * [:Manuals/ReleaseNotes/CentOS5.6/German:Deutsch] - 
 [:MarcusMoeller:Marcus Moeller]
* [:Manuals/ReleaseNotes/CentOS5.6/Japanese:日本語] - 
 [:TadashiJokagi:Tadashi Jokagi], [:AkemiYagi:Akemi Yagi]
* [:Manuals/ReleaseNotes/CentOS5.6/French:Français] - 
 [:FabianArrotin:Fabian Arrotin]
* [:Manuals/ReleaseNotes/CentOS5.6/Romanian:Romana] - 
 [:ManuelWolfshant:Manuel Wolfshant]
 ### * [:Manuals/ReleaseNotes/CentOS5.6/Russian:Русский] - 
 [:NikolayUlyanitsky:Nikolay Ulyanitsky]
* [:Manuals/ReleaseNotes/CentOS5.6/Spanish:Español] - 
 [:HardyBeltran:Hardy Beltran]
 ### * [:Manuals/ReleaseNotes/CentOS5.6/Turkish:Türkçe] - Osman Aksit

 It would help a lot to maintain the translations homogeneous. Native
 speaker looking for RN in his/her native language can read and find the
 proper localised language link.
 DH
 I agree with using #include directives to keep the list of translations
 synchronized on all pages.  As the Chinese translation maintainer, I
 find it tedious having to update the Chinese page every time a new
 translation becomes available.
then let's do it.  any objections on the approach suggested by David ?

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Some questions: Release Notes CentOS 5.6

[Manuel Wolfshant]

On 04/14/2011 03:10 AM, Hardy Beltran Monasterios wrote:


Hello

A couple of days ago, I did the Spanish translation for ReleaseNotes 
CentOS 5.6

and I have some questions

Right now, in the Spanish version we are using nice icons for Notes.
Would you like the same in the English and other translated versions ?
(I know that is not important, just looks nice ;-) )

As long as we are consistent in the wiki and we do not make it look as 
colored as a parrot, I like this idea.




On many places we mention packages names or file names. I suggest
use {{{typewriter}} style for this, to better reading/understand.

My wiki-foo is weak. Can you provide more details please, so that I do 
not go hunting for documentation ?





Some time ago, we talk about some common parts in all the translated 
versions.
And we started to use marks #begin- #end- Right now, we 
don't have
this marks for the Translations subtitle in the original version. We 
should use

I think.

You cannot do that because the translations section must include [*]  
the language names expressed in the language of the translation. For 
instance in the Romanian release notes I would use
 * [:Manuals/ReleaseNotes/CentOS5.6/Spanish:Spaniola] (Español) - 
[:HardyBeltran:Hardy Beltran]

while in the Spanish version you should use
 * [:Manuals/ReleaseNotes/CentOS5.6/Romanian:Rumano] (Romana) - 
[:HardyBeltran:Hardy Beltran]



[*] Unless we decide to not do that





By the way, I need help to use 'Include macro', all my tries were 
unsuccessful



Get inspiration from the Romanian and French translations. I am lazy so 
in step 1 I bookmarked the lists of packages for the English version and 
in step 2 I included the lists as such ( using bookmarks ) in those two 
translations. You can simply copy/paste the relevant lines.




___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Contributing to Wiki

[Manuel Wolfshant]

On 04/04/2011 08:48 PM, Akemi Yagi wrote:
 On Mon, Apr 4, 2011 at 10:40 AM, R P Herroldherr...@centos.org  wrote:
 On Mon, 4 Apr 2011, Alan Bartlett wrote:

 I think he did too, but I can't access or edit it.
 You are not allowed to view this page.
 I've just checked and see that there is a typo on the acl line.
 Unfortunately I can't correct it . . .
 umm -- E_NEED_CONTEXT  ;)

 What page URL and perhaps a diff as to what is desired,
 please? -- I've deleted the prior thread tail out of my
 mailspool already
 Here:

 http://wiki.centos.org/JimWoods

 #acl JimWoods:reead,write,revert,delete Default

 Akemi
I used my supercow powers and fixed it .

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Contributing to Wiki

[Manuel Wolfshant]

On 04/04/2011 09:00 PM, Manuel Wolfshant wrote:
 On 04/04/2011 08:48 PM, Akemi Yagi wrote:
 On Mon, Apr 4, 2011 at 10:40 AM, R P Herroldherr...@centos.org   wrote:
 On Mon, 4 Apr 2011, Alan Bartlett wrote:

 I think he did too, but I can't access or edit it.
 You are not allowed to view this page.
 I've just checked and see that there is a typo on the acl line.
 Unfortunately I can't correct it . . .
 umm -- E_NEED_CONTEXT  ;)

 What page URL and perhaps a diff as to what is desired,
 please? -- I've deleted the prior thread tail out of my
 mailspool already
 Here:

 http://wiki.centos.org/JimWoods

 #acl JimWoods:reead,write,revert,delete Default

 Akemi
 I used my supercow powers and fixed it .


Actually I wanted to by I am not allowed to. I am just an ordinary cow, 
sorry for the noise.


___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] CentOS Wiki Contribution

[Manuel Wolfshant]

On 03/27/2011 01:58 PM, Alex/AT wrote:
 Manuel Wolfshantwo...@nobugconsulting.ro  писал(а) в своём письме Sun,
 27 Mar 2011 14:57:27 +0400:

 I modified it a bit.

 However, I fail to understand why is all this complicate procedure
 needed, given that starting the installer with linux ext4 (linux
 ext4dev for the centos releases prior to 5.5, if I am not mistaken)
 achieves the same goal without any need for workarounds ? The ext4 type
 of filesystem will be present in the disk druid interface and can be
 used exactly as any other one.
 Oops. Did not know that. If that is the case, the the article is really
 not needed.

I've changed the http://wiki.centos.org/TipsAndTricks/InstallOnExt4 page 
to reflect the recommended option

 Manuel

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] CentOS Wiki Contribution

[Manuel Wolfshant]

On 03/27/2011 03:39 PM, Alan Bartlett wrote:

 My wetware failure is to blame here - was thinking that only came in
 with RHEL6 and failed to check; however, a brief article on ext4 the
 right way would still be worthwhile.
 Perhaps one of the QA team would test / confirm an ext4 installation,
 whilst QA'ing C-5.6 ?

 Looks east . . . Wolfy ?  Looks west . . . Phil ?

It works fine since C5.4, only that at the time, due to the fact that 
ext4 was still a technology preview,  the required boot option had a 
slightly different name instead of ext4.
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] CentOS Wiki Contribution

[Manuel Wolfshant]

On 03/27/2011 12:20 PM, Alex/AT wrote:
 Ralph Angenendtralph.angene...@gmail.com  писал(а) в своём письме Sat,
 26 Mar 2011 23:16:58 +0300:

 Great, go ahead:http://wiki.centos.org/TipsAndTricks/InstallOnExt4

 Can you put a bit more text around what you are doing there (especially
 why you drop to a shell to do the formatting and partitioning)?
 Thanks. Yes, I will elaborate it a bit.
 It is done and ready to be edited.
 Any comments on this are appreciated.
 I've also probably did some really bad spelling errors 'cause I'm not
 native English speaker/writer.
I modified it a bit.

However, I fail to understand why is all this complicate procedure 
needed, given that starting the installer with linux ext4 (linux 
ext4dev for the centos releases prior to 5.5, if I am not mistaken) 
achieves the same goal without any need for workarounds ? The ext4 type 
of filesystem will be present in the disk druid interface and can be 
used exactly as any other one.

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Wiki: Howtos/Virtualization/HyperV

[Manuel Wolfshant]

On 03/20/2011 10:50 PM, Ozy the barbarian guitarist wrote:
 Hello,

 My wiki contribution about HyperV is ready for evaluation.
 http://wiki.centos.org/OzydeJong/HyperV

 Cheers,
 Ozy.

The article seems fine to me.
However I'd rephrase the legacy card part to something like [...]please 
create a temporary ethernet interface named eth0 by using a 'Legacy 
Network Adapter' in your VM and respectively you can remove the 
temporary interface  ( instead of legacy interface ) in the last 
paragraph,


 Manuel
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Wiki: Howtos/Virtualization/HyperV

[Manuel Wolfshant]

On 03/17/2011 12:46 AM, Ozy the barbarian guitarist wrote:
 Hello,

 I've written a couple of articles about CentOS on my personal blog 
 that i'd like to share.
 As mentionned py pschaff on the CentOS 5 forum ( 
 https://www.centos.org/modules/newbb/viewtopic.php?topic_id=30474forum=37 
 https://www.centos.org/modules/newbb/viewtopic.php?topic_id=30474forum=37 
 ), there could be a need of an article explaining how to virtualize 
 CentOS 5 in HyperV.

 As i wrote my articles in french, i'm willing to translate them so 
 they could fit your wiki.
 Here's my inital article about Hyper-V  CentOS: 
 http://www.badministrateur.com/en/node/66

 I'm not the best admin out there as my blog's domain name suggests 
 (Bad Administrator :-), but all articles i wrote are tested and should 
 work.
 I'm willing to help if needed.

 Best regards,
 Ozy.

 centos-docs account: OzydeJong
 proposed subject: Virtualization of CentOS 5 in Hyper-V
 proposed location: Howtos/Virtualization/HyperV

 I do not use Hyper-V myself ( I tried to avoid any Microsoft 
product as much as I can, and I see no reason to use their hypervisor 
since other free solutions exist) and therefore I cannot test, but I've 
read the article and it seems sane enough. And quite similar to what one 
must do to get better performance when using other popular solutions 
such as VMWare.


___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] Network frozen in Centos 5 with Xen

[Manuel Wolfshant]

On 02/17/2011 10:31 AM, onlineque onlineque wrote:
 Hello,

 I have this problem - I have installation of Xen and Centos 5 (all RPMs are 
 from Centos repositories).
 I have several DomU virtual machines running on this machine.
 When I try to copy some bigger amount of data from another physical computer 
 to Dom0/DomU on this machine, the network freezes. The link is still up, I 
 can see that the connection really links on the switch, but nothing is 
 received or sent to the network. I tried to stop all the DomUs, stop the 
 network, unload the network drivers from memory and loading them again and 
 starting the network, but the problem persists. Only reboot solves the 
 problem.
 Sometimes the amount of data have to be around gigabytes (last time it was 
 10GB), sometimes 500MB is enough to stop the network...
 I also tried to change the NIC, but the behavior is the same.
 Btw. logs don't say anything :-/

 Any idea ? Thank you very much !

Replace the Realtek network card (preferably with an Intel ! ) if you 
are using it.
Try 
http://www.broadcom.com/support/ethernet_nic/driver-sla.php?driver=570x-Linux 
if using the BCM5705 interface. If this solves your problem, file a RFE 
in bugzlla.redhat.com because the current driver both in RHEL6 and in 
RHEL 5.6 is still based on version 1.108

 Manuel

 Vladimir


 PS: this is the output of my lspci:

 00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
 00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
 00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
 00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
 00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
 00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 
 South]
 00:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
 RTL-8139/8139C/8139C+ (rev 10)
 00:0b.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705 Gigabit 
 Ethernet (rev 03)
 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID 
 Controller (rev 80)
 00:0f.1 IDE interface: VIA Technologies, Inc. 
 VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
 Controller (rev 81)
 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
 Controller (rev 81)
 00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
 Controller (rev 81)
 00:10.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
 Controller (rev 81)
 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge 
 [KT600/K8T800/K8T890 South]
 00:11.5 Multimedia audio controller: VIA Technologies, Inc. 
 VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
 HyperTransport Technology Configuration
 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
 Address Map
 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM 
 Controller
 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
 Miscellaneous Control
 00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
 HyperTransport Technology Configuration
 00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
 Address Map
 00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM 
 Controller
 00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
 Miscellaneous Control
 01:00.0 VGA compatible controller: nVidia Corporation NV15 [GeForce2 GTS/Pro] 
 (rev a4)

 output of uname -a:

 Linux hydra 2.6.18-194.11.4.el5xen #1 SMP Tue Sep 21 05:40:24 EDT 2010 x86_64 
 x86_64 x86_64 GNU/Linux


 ___
 CentOS-virt mailing list
 CentOS-virt@centos.org
 http://lists.centos.org/mailman/listinfo/centos-virt


-- 
  Manuel Wolfshant   linux registered user #131416
 IT managerNoBug Consulting SRL
   A: Yes.
   Q: Are you sure?
   A: Because it reverses the logical flow of conversation.
   Q: Why is top posting frowned upon?

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] iTunes?

[Manuel Wolfshant]

On 02/12/2011 11:56 PM, Lucas Timm LH wrote:
 Ealier was possible run iTunes in Linux using Wine. Actually I really 
 don't know if it still works, because a lot things have changed since 
 2007 (was the last time I'd installed iTunes in Linux). BTW you can 
 install VMware Workstation or Player to run Windows XP/Seven/Whattever 
 and do what you want. I guess VirtualBox OSE have no USB support, so 
 you will need to buy a licence to VirtualBox or VMware.
USB works OK in VirtualBox-4.0-4.0.2_69518_rhel6-1.x86_64



 I don't know if KVM supports USB too.

 2011/2/12 MargoAndTodd margoandt...@gmail.com 
 mailto:margoandt...@gmail.com

 Hi All,

 If you would please suffer a Fedora Code 13 question on a CentOS
 mailing
 list, I
 have a Linux customer with Fedora Code 13 who loves it but is
 about to dump
 it because he really, really wants iTunes. (He owns an iPod and an
 iPhone.)
 None of the Linux utilities quite work right and he wants to buy
 music from
 the iTunes store as well. Plus he wants to synchronize his
 contacts list.

 So, I was thinking of installing an XP VM on his computer. Would
 iTunes work
 properly?  Would you use KVM or Virtual Box? Any words of wisdom
 shared
 would be appreciated.

 Many thanks,
 -T
 ___
 CentOS-virt mailing list
 CentOS-virt@centos.org mailto:CentOS-virt@centos.org
 http://lists.centos.org/mailman/listinfo/centos-virt




 -- 
 Lucas Timm, Goiânia/GO.
 http://timmerman.wordpress.com

 (62) 8198-0867


 ___
 CentOS-virt mailing list
 CentOS-virt@centos.org
 http://lists.centos.org/mailman/listinfo/centos-virt


___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] HowTo Document - Installing Nagios on CentOS 4x/5x

[Manuel Wolfshant]

On 02/03/2011 08:49 PM, Jonathan Q. wrote:
Hi. There's a note on this document 
(http://wiki.centos.org/HowTos/Nagios) that it appears to be abandoned 
and unmaintained. Since I'm working through the document to install 
Nagios, and taking fairly extensive notes on the process, I would like 
to bring it up to date. But, since I've not worked on an open source 
documentation project before, I'm not sure how to proceed. Basically, 
I'm clueless right now. :-)  If someone could give me a little 
guidance, I would greatly appreciate it!


A couple of initial questions:

Do I need to attempt to contact the original author for permission to 
update and maintain the document?



Generally speaking, it is polite to do so, yes. But technically speaking
- the whole content of the wiki is licensed under a Creative Commons 
Attribution-Share Alike 3.0 Unported License so anyone ( more or less 
...) may edit it
- the page under discussion starts with Note added 28 July 2010: This 
piece seems to be abandoned, is unmaintained so I am sure that a new 
owner will be welcomed.




I've saved a copy to my local machine and I'm working on it there. Is 
that the best way? How do I then submit the updated document for 
publication?


Anything else that would be good to know? :-)



Actually it's pretty simple since it is a wiki and we encourage users to 
expand / fix it.

Since you are a newcomer I suggest the following approach:
- create an account in the wiki
- submit here your suggested changes ( for instance by posting a link to 
a page hosting your modified version of the page or simply listing the 
changes as list in the mail; any reasonable method would be)
- once the changes are reviewed, ask for permission to include them in 
the wiki

- an administrator will give you the appropriate rights
- fix it
- let everyone rejoice
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] HowTos/JavaOnCentOS Wiki page revision?

[Manuel Wolfshant]

On 01/16/2011 06:26 PM, Ralph Angenendt wrote:
 Am 16.01.11 15:15, schrieb Manuel Wolfshant:
 On 01/16/2011 04:03 PM, Phil Schaffner wrote:
 If this approach is accepted I would be glad to help draft the cover
 page, and to help with polishing sub-pages; having over the years dealt
 with JDK via Sun(Oracle) RPMs, building JDK via the Jpackage approach,
 and simple JRE/plugin installations.
 Your idea looks fine to me. The existing page is so obsolete that I
 never pointed anyone to it during the last year... I always suggested
 download Sun's rpm, install, go live your life
 I'm fine with that. Java is completely over my horizon, regarding usage.
 If it doesn't run with openjdk, I normally don't run it, neither on
 servers nor on desktops.

 So that probably leaves two instructions (well, three) for that page:

 a) Use openjdk (if on 5, 6)
 b) Use SUN JDK/JRE if the above does not work for you, here's how to do
 it.
 c) Use jpackage nosrc.rpms if you insist on compliance to FHS

 For b) and c) stress that people *must* care about updates for themselves.

 Bonus points: Here's how to use Java in your browser. Especially stress
 the update issue here.

 Do I see that correctly?
Absolutely right.
Bonus points for emphasizing that the rpms derived from the .nosrc.rpm 
MUST be recreated at each update. Which is what finally made me give up 
using this approach. IIRC I wanted to automate the process , but with 
each [minor] release there were small diffs which invited to manual 
intervention, hence making the automated build impossible.

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] HowTos/JavaOnCentOS Wiki page revision?

[Manuel Wolfshant]

On 01/16/2011 04:03 PM, Phil Schaffner wrote:
 Ralph Angenendt wrote on 01/15/2011 03:39 PM:
 ...
 To me the article looks good, if you can incorporate it into the current
 wiki article (and not just replace that).
 I beg to differ.  The current Wiki article contains a lot of confusing
 and obsolete information, and in trying to cover a multitude of Java
 versions and different approaches for CentOS 4 and 5, fails to do any of
 it well.  Modifying it to merge in still more approaches such as the two
 currently under discussion in this thread, and soon CentOS 6, will add
 additional confusion.

 I would propose instead that a new cover page replace the current
 page.  It should comprise an introduction to Java on CentOS; briefly
 discuss JRE, JDK, alternatives, and browser plugins; and provide links
 to sub-pages; one of which may be the current page and/or multiple
 sub-pages derived from it.  Each subpage of JavaOnCentOS should be a
 concise method to install a particular Java flavor on a specific CentOS
 version, and should include its own detailed procedure on alternatives
 and plugins if appropriate.
right


   Obsolete pages and information could either
 be pruned or preserved in a Historical section.
neah. the old page should be either updated or deleted/replaced. it's 
close to useless as it is now.


   The two new
 submissions should each get their own sub-page.  A section at the end,
 perhaps Other Voices, could point to recommended external pages, such
 as parts of the Jpackage site, or other HowTos.

 If this approach is accepted I would be glad to help draft the cover
 page, and to help with polishing sub-pages; having over the years dealt
 with JDK via Sun(Oracle) RPMs, building JDK via the Jpackage approach,
 and simple JRE/plugin installations.
Your idea looks fine to me. The existing page is so obsolete that I 
never pointed anyone to it during the last year... I always suggested 
download Sun's rpm, install, go live your life
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] How to create a new initrd

[Manuel Wolfshant]

On 01/15/2011 06:00 PM, Phil Schaffner wrote:
 http://wiki.centos.org/TipsAndTricks/CreateNewInitrd

 Comments and constructive criticism are solicited.

 Phil
I took advantage of you invitation to complete/correct the page and 
fixed a minor typo + added a reference to the xenblk module

 Wolfy
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Automated listing of translations on each wiki page

[Manuel Wolfshant]

On 11/23/2010 12:00 AM, Ralph Angenendt wrote:
 Am 22.11.10 22:25, schrieb Marcus Moeller:
   
 Dear Ralph,
 
 http://wiki.dev.centos.org/ to your liking? I like it :)
   
 Looks fine so far. Only the CSS of the top menu is a bit broken.
 

 Where exactly? I ripped out an ad which crept into there, but that is
 the same solution we have on the original, too.
   
the first link in Chinese in the top list is a couple of pixels below 
the rest.
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Suggestion for how to section: easy way to install the JDK?

[Manuel Wolfshant]

On 10/09/2010 04:33 AM, Milos Blazevic wrote:
 Bob Stine wrote:
   
 Milos Blazivec wrote:

 /... I am, in fact, interested in making adjustments to the Wiki /
 /page - but sadly not the ones you proposed Bob, since the just
 won't do /
 /the trick./


 Hmm.  I ran the executed the bin file, edited /etc/profile so that 
 PATH included the bin directory of the sun jdk directory, added 
 environment variable JDK_HOME,  deleted the /usr/bin/java symlink from 
 java - /etc/alternative/java, and everything works, or at least well 
 enough for me to run the Eclipse C++ IDE, which was my goal.  

 Maybe adding the jdk was unnecessary for Eclipse to work?

 Could you unpack just won't do, or point to a discussion of the issue?

 
 What I meant is that the instructions you suggested in your first e-mail 
 are taken from: 
 http://www.oracle.com/technetwork/java/javase/install-linux-64-rpm-138254.html
 and are all but comprehenssive, let alone appropriate for beginners. 
 These installation instructions have been accompanying Sun Java as long 
 as I can remember, and strangely, no one cared to mention 'em in the 
 Wiki page... don't you think that's kinda odd? I don't - 'cause they 
 don't work!

 This second part (editing /etc/profiles, deleting symlinks and editing 
 PATH...) is NOT what you mentioned in your first e-mail. However, in my 
 honest oppinion, this is still not the correct way to do this.

 What you did, is that you probably got it to work for Your particular 
 purpose by resorting to an unconventional method (i.e. circumvent the 
 mechanism intended for this purpose, rather than a by-the-book 
 approach). By solving the problem this way, sooner or later you'll end 
 up breaking something. Maintainance may prove difficult later

 For me, by-the-book is using alternatives utility for this purpose - 
 intended by the makers way to handle this kind of issues. (switching 
 between different mail servers, etc.)
   

  Using alternatives in the context of Java is 100% useless for ordinary 
users who do not want to use the stock gcj or openjdk packages ( and 
therefore replace them with Sun's packages). As far as I have seen on 
the few hundreds workstations that I maintain + the requests in the IRC 
channel, users only need to run
- browser java plugin  ( solved by installing Sun's jre + a convenient 
ln -s already mentioned before in this thread
- java ( the binary, as in  java -Xmx400m -DuseDesktop=true 
-Dsun.java2d.pmoffscreen=false -jar /usr/share/jalbum/JAlbum.jar  ) in 
order to run .jar applications
- the libs needed by Eclipse, also mentioned before in the thread
 Better idea is to adjust symlink to point to the desired binary, rather 
 than editing PATH variable, deleting the symlink,...
   

At least the jre package (and I am almost sure jdk too) from Sun comes 
with the following structure:
lrwxrwxrwx 1 root root   16 Apr 10 01:25 default - /usr/java/latest
drwxr-xr-x 7 root root 4096 Jun 28 23:34 jre1.6.0_20
lrwxrwxrwx 1 root root   21 Jun 28 23:35 latest - /usr/java/jre1.6.0_20

Using /usr/java/latest and / or /usr/java/default in your scripts makes 
them immune to upgrades, as long as you stick with Sun's packages ( 
which - sad but true - make the java-openjdk / gcj packages useless and 
offer ( for the moment ) better compatibility with the real world. At 
least from I where I stand.

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Suggestion for how to section: easy way to install the JDK?

[Manuel Wolfshant]

On 10/09/2010 12:47 PM, Ned Slider wrote:
 On 09/10/10 08:32, Manuel Wolfshant wrote:

 snip

   
 At least the jre package (and I am almost sure jdk too) from Sun comes
 with the following structure:
 lrwxrwxrwx 1 root root   16 Apr 10 01:25 default -  /usr/java/latest
 drwxr-xr-x 7 root root 4096 Jun 28 23:34 jre1.6.0_20
 lrwxrwxrwx 1 root root   21 Jun 28 23:35 latest -  /usr/java/jre1.6.0_20

 Using /usr/java/latest and / or /usr/java/default in your scripts makes
 them immune to upgrades, as long as you stick with Sun's packages (
 which - sad but true - make the java-openjdk / gcj packages useless and
 offer ( for the moment ) better compatibility with the real world. At
 least from I where I stand.

 

 Are these redistributable? I'm sure they are as Red Hat has Sun's Java 
 packages on it's
 RHEL Supplementary disk for RHEL5 which it (re)distributes to customers.

   
As Russ has said, they are not.
 In which case why doesn't someone just repackage these and stick them in 
 CentOS Extras/rpmforge or somewhere and the problem largely goes away. 
 Or am I missing something?
   
Yup, you miss the fact that RH [ probably ] has agreements which allow 
them to redistribute some binary-only packages (even flash player) via a 
special channel to their  customers.
 If we had decent packages that Just Worked, we wouldn't need convoluted 
 documentation on how to install Java.
   
Indeed. Unfortunately we are not there. Not yet.
However a 3 steps procedure ( 1) download from Sun; 2) install rpm 3) 
create a symlink for your browser ) is not that bad, given the previous 
options that we had.
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-virt] working config for xen which would transfer a serial interface

[Manuel Wolfshant]

  Hello

 Can anyone share a known working config for xen which would 
transfer a serial interface ( add-on card preferably, mine uses   
e880-e887 : :03:05.0 /   ec00-ec07 : :03:05.0 ) to a DomU ?
 I've been trying with the stock packages from Centos 5.5 ( fully 
updated) and also with gitco's 3.4.3 but after 2 days of googling and 
testing we still fail to access the serial interface from DomU.
 No matter what we've tried,
- in DomU there is no reference to any kind of serial ports in 
/proc/{interrupts,ioports}
- the test program which accesses ttyS0 fails ( it works just fine in 
dom0) even after manually loading parport_serial in DomU

 /dev/ttyS{0..3} do get created by default, if that matters.



 Here is the content of the config file, after the last attempt 
(which uses gitco's xen, but we failed similarly with the stock packages):

name = testr
uuid = 57baf51a-e293-fa35-9f2e-056a1c0e322a
maxmem = 512
memory = 512
vcpus = 1
bootloader = /usr/bin/pygrub
on_poweroff = destroy
on_reboot = restart
on_crash = restart
vfb = [ type=vnc,vncunused=1,keymap=en-us ]
disk = [ tap:aio:/var/lib/xen/images/testr,xvda,w ]
vif = [ mac=00:16:36:0c:aa:1a,bridge=xenbr0,script=vif-bridge ]
irq = [11 ]
ioports = [ ec00-ec07,e080-e08f ] // we also tried to pass all the 
IO ports referenced in lspci -vvv

[r...@dom0]#lspci -vvv
03:05.0 Communication controller: NetMos Technology PCI 9835 Multi-I/O 
Controller (rev 01)
 Subsystem: LSI Logic / Symbios Logic 1P2S
 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR+ FastB2B-
 Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 TAbort- TAbort- MAbort- SERR- PERR-
 Interrupt: pin A routed to IRQ 11
 Region 0: I/O ports at ec00 [size=8]
 Region 1: I/O ports at e880 [size=8]
 Region 2: I/O ports at e800 [size=8]
 Region 3: I/O ports at e480 [size=8]
 Region 4: I/O ports at e400 [size=8]
 Region 5: I/O ports at e080 [size=16]

[r...@dom0 ~]# dmesg | grep ttyS

[r...@dom0 ~]# cat /etc/modprobe.d/blacklist
#[...]
blacklist 8250
blacklist 8250_pnp
blacklist serial_core
blacklist parport_serial
blacklist 8250_pci



[r...@dom0 ~]# grep xen /etc/grub.conf
title CentOS (2.6.18-194.el5xen)
 kernel /xen.gz-3.4.3
 module /vmlinuz-2.6.18-194.el5xen ro root=/dev/VolGroup00/LogVol00
 module /initrd-2.6.18-194.el5xen.img
title CentOS (2.6.18-194.8.1.el5xen)
 kernel /xen.gz-3.4.3
 module /vmlinuz-2.6.18-194.8.1.el5xen ro 
root=/dev/VolGroup00/LogVol00 xencons=off
 module /initrd-2.6.18-194.8.1.el5xen.img

[r...@dom0 ~]# uname -a
Linux Dom0 3 2.6.18-194.8.1.el5xen #1 SMP Thu Jul 1 19:41:05 EDT 2010 
x86_64 x86_64 x86_64 GNU/Linux

sniff from the boot messages in tge DomU:

XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/ioports/0
XENBUS: Device with no driver: device/ioports/1
XENBUS: Device with no driver: device/ioports/2
XENBUS: Device with no driver: device/ioports/3
XENBUS: Device with no driver: device/ioports/4
XENBUS: Device with no driver: device/ioports/5
XENBUS: Device with no driver: device/irq/0
XENBUS: Device with no driver: device/console/0




[r...@domu ~]# cat /proc/interrupts
CPU0
256:   7433 Dynamic-irq  timer0
257:  0 Dynamic-irq  resched0
258:  0 Dynamic-irq  callfunc0
259:554 Dynamic-irq  xenbus
260:705 Dynamic-irq  xencons
261:802 Dynamic-irq  xenfb
262:  0 Dynamic-irq  xenkbd
263:   6607 Dynamic-irq  blkif
264:   8959 Dynamic-irq  eth0
NMI:  0
LOC:  0
ERR:  0
MIS:  0

[r...@domu ~]# cat /proc/ioports
-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-0060 : keyboard
0064-0064 : keyboard
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu

[r...@domu ~]# lsmod
Module  Size  Used by
8250_pnp   43969  0
parport_serial 41153  0
8250_pci   56257  1 parport_serial
8250   86057  2 8250_pnp,8250_pci
serial_core56385  1 8250
[...]

[r...@domu ~]# uname -a
Linux DomU 2.6.18-194.8.1.el5xen #1 SMP Thu Jul 1 19:41:05 EDT 2010 
x86_64 x86_64 x86_64 GNU/Linux




 TIA

 manuel

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt