Re: [CentOS-es] Red wifi en Centos 6.3
El 21/03/13, Rodrigo Pichiñual Norin rodrigo.pichin...@gmail.com escribió: Antes de instalar Centos tenia fedora 18 en mi laptop y me reconocía amabas redes cableada e inalambrica (p1p2 wlan0), pero con centos no me reconoce ni una, la red cableada tuve que meterle mano yo. Si ocupo ifconfig -a solo me muestra la local lo Si muestra esa salida posiblemente no tienes interfaces, estan dañadas o no estan haciendo contacto, ES MUY raro que no reconozca que yo sepa ahora CentOS en la versión 6.x debe reconocer mucho hardware ya no es como CentOS 5, posiblemente también tu hardware es muy reciente y poco comun. después de configurar la red cableada y al hacer un ifconfig -a ,uestra Cómo haz configurado? no llego a entender si no lo veías antes cómo has hecho y TODAVIA PARA VERLO con ese nombre, no se si estoy mal (LO DUDO) pero hasta donde vi en CentOS 6.0 las interfaces se nombran todavía con eth0, eth1, ..., wlan0 (wifi) y NO P1P2 eso es de fedora que en nueva release introduce nueva forma de nombrar a las interfaces, yo soy el único que esta hablando de esto? hay varios en la lista que usan CentOS y no dicen si p1p2 es válido en CentOS, que yo sepa NO lo p1p2 Muy extraño, deamasiado diría CentOS no nombra de esa manera a las interfaces, por ahora, fedora si nombra de esa manera. me captas? Causa confusión lo que muestras, mira que dice la docuentación redhat el 6 https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html No existe p1p2, eso es de fedora, en Centos debería de ser eth..., asi debería de verse si es que reconoce, aunque podría cambiarse, pero mejor sería dejar con ese nombre. Gracias. El 21 de marzo de 2013 02:23, Tranc3 Music edgarr...@gmail.com escribió: El 20/03/13, Rodrigo Pichiñual Norin rodrigo.pichin...@gmail.com escribió: Hola a todos, Resulta que instala CentOS en su versión *minimal Desktop*, una vez terminada la instalación pude ver que no tenia red, en un principio * NetworkManager* intentaba configurar mi red, pero aun así no tenia net, me puse a configurar la red cableada (Ethernet) el dispositivo por defecto era *p1p2* y ahora tengo internet cableada el Drama es con el dispositivo ¿p1p2? que yo sepa esa es la forma que fedora (las últimas releases) le da nombre a las interfaces, pero CentOS todavía no da esos nombres, que yo sepa sigue con eth0,eth1,..., estas seguro que estas usando CentOS? :o, o estoy equivocado? :o wifi, no tengo un WLAN0 en /etc/sysconfig/netwok-scripts/, me interesa configurar esto ya instale centos en mi portatil tanto de forma manual o con Network Manager ?¿? no entender pro completo: ya instale centos en mi portatil tanto de forma manual o con Network Manager Pero bueno segun lo que entiendo..., primero por qué no usas ifconfig -a, para ver tus interfaces, si tienes interfaz wifi seguro que se verá usando ifconfig -a, no estan congiguradas aún, también por defecto en CentOS no se inicializa las interfaces, a menos que en la isntalación le hayas dicho que si. Si tienes NetworkManager por qué no usas y configuras? debes hacerlo también, lee las opciones que ves por ahí hay una que te permite configurar tanto la cableada y la inalambrica (si es que la detecta, creo que si, CentOS 6.3 es un fedora 12 ó 13 debería de detectar hardware en su mayoría), saludos y suerte. *Gracias* ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es -- UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity. -- Dennis M. Ritchie Mis bits: http://bitsenlared.wordpress.com Live free or die! ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es -- *Rodrigo Pichiñual * *Ingeniero en Computación* *87272971 * rodrigo.pichin...@gmail.com / rodr...@latitud33.cl rodrigo.pichin...@gmail.com ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es -- UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity. -- Dennis M. Ritchie Mis bits: http://bitsenlared.wordpress.com Live free or die! ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es
[CentOS] CentOS-announce Digest, Vol 97, Issue 13
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org
You can reach the person managing the list at
centos-announce-ow...@centos.org
When replying, please edit your Subject line so it is more specific
than Re: Contents of CentOS-announce digest...
Today's Topics:
1. CEEA-2013:0674 CentOS 5 tzdata Update (Johnny Hughes)
2. CEEA-2013:0674 CentOS 6 tzdata Update (Johnny Hughes)
--
Message: 1
Date: Fri, 22 Mar 2013 10:15:32 +
From: Johnny Hughes joh...@centos.org
Subject: [CentOS-announce] CEEA-2013:0674 CentOS 5 tzdata Update
To: centos-annou...@centos.org
Message-ID: 20130322101532.ga17...@chakra.karan.org
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Enhancement Advisory 2013:0674
Upstream details at : https://rhn.redhat.com/errata/RHEA-2013-0674.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
435ae45a48d892eacda1abf3ed117156f354d41a1c896ce3632ea4e2557300d0
tzdata-2013b-1.el5.i386.rpm
980dab577b3a69c609412a349b7d690388d26d353f3bd0ff1cdb239e006d3854
tzdata-java-2013b-1.el5.i386.rpm
x86_64:
e0e942a9f3778363eca8d0bf06a7f088ab68984a24db49f5af9f4a44c6ca845a
tzdata-2013b-1.el5.x86_64.rpm
5b5b46b53b597cfad585423065b292cc315d03c65aaa4ca73d1bf273b6c291e3
tzdata-java-2013b-1.el5.x86_64.rpm
Source:
dcfe8ea539ab8266fcdaff08d233c49d0c7ece5257beddf3af5c3ab422a6f362
tzdata-2013b-1.el5.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
--
Message: 2
Date: Fri, 22 Mar 2013 12:05:17 +
From: Johnny Hughes joh...@centos.org
Subject: [CentOS-announce] CEEA-2013:0674 CentOS 6 tzdata Update
To: centos-annou...@centos.org
Message-ID: 20130322120517.ga23...@chakra.karan.org
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Enhancement Advisory 2013:0674
Upstream details at : https://rhn.redhat.com/errata/RHEA-2013-0674.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
5d9ee77be4c1ee9778c819a082458869aaad6d4613092127b76f65f8878d76c3
tzdata-2013b-1.el6.noarch.rpm
ae49a41c6f95a9ae76a97027bd1a04264881bbbd5e8d782323e5add4eef9fa3f
tzdata-java-2013b-1.el6.noarch.rpm
x86_64:
5d9ee77be4c1ee9778c819a082458869aaad6d4613092127b76f65f8878d76c3
tzdata-2013b-1.el6.noarch.rpm
ae49a41c6f95a9ae76a97027bd1a04264881bbbd5e8d782323e5add4eef9fa3f
tzdata-java-2013b-1.el6.noarch.rpm
Source:
289dcd9845ad9aff7f693f7d216ffc40f3b788b8c358157250a277e9a75eca02
tzdata-2013b-1.el6.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
--
___
CentOS-announce mailing list
centos-annou...@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce
End of CentOS-announce Digest, Vol 97, Issue 13
***
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] Touchpad doesn't work with C6, kernel-related...
Hi folks! :-) I have a Fujitsu Lifebook U series laptop running updated CentOS 6.4 (64bit), and the touchpad doesn't work. It's a new laptop, the touchpad works correctly in Fedora 18 Live (given the kernel parameters below), no hardware problems. I searched the web all around, and it's a known issue for several laptop models. The only solution, quoted everywhere, it is to append the i8042.notimeout i8042.nomux to the kernel parameters. The problem is that the latest CentOS6 kernel (2.6.32-358.2.1.el6.x86_64) doesn't appear to recognize these. Or it otherwise ignores them. I did append the parameters, but (unlike in Fedora) the touchpad is still dead. This laptop is to be used by a noob user who needs a LTS distro and is already accustomed to CentOS, so a more modern distro like Fedora or Ubuntu is not an option. What can be done about this? Would a CentOSplus kernel work? It is somehow too lousy to tell the client The touchpad of your brand-new laptop doesn't work because CentOS is too old, use an USB mouse instead. Any advice appreciated. TIA, :-) Marko ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Touchpad doesn't work with C6, kernel-related...
On Sat, Mar 23, 2013 at 7:04 AM, Marko Vojinovic vvma...@gmail.com wrote: Hi folks! :-) I have a Fujitsu Lifebook U series laptop running updated CentOS 6.4 (64bit), and the touchpad doesn't work. It's a new laptop, the touchpad works correctly in Fedora 18 Live (given the kernel parameters below), no hardware problems. I searched the web all around, and it's a known issue for several laptop models. The only solution, quoted everywhere, it is to append the i8042.notimeout i8042.nomux to the kernel parameters. The problem is that the latest CentOS6 kernel (2.6.32-358.2.1.el6.x86_64) doesn't appear to recognize these. Or it otherwise ignores them. I did append the parameters, but (unlike in Fedora) the touchpad is still dead. This laptop is to be used by a noob user who needs a LTS distro and is already accustomed to CentOS, so a more modern distro like Fedora or Ubuntu is not an option. What can be done about this? Would a CentOSplus kernel work? It is somehow too lousy to tell the client The touchpad of your brand-new laptop doesn't work because CentOS is too old, use an USB mouse instead. Any advice appreciated. TIA, :-) Marko Just did a quick check. The current CentOS kernel (centosplus kernel as well) seems to have code for i8042.nomux but not i8042.notimeout in linux/drivers/input/serio/i8042.c . You might want to give ELRepo's kernel-ml a try: http://elrepo.org/tiki/kernel-ml It is the latest mainline kernel that runs on CentOS. Akemi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Virtual Hosts and users
On Fri, Mar 22, 2013 at 8:09 PM, Bruce Whealton br...@futurewaveonline.com wrote: Hello, I do have virtual hosts setup. I registered one domain and used a second service that allowed me to use a subdomain on their domains and have it point to my IP for my server (the external IP). This might let me give permissions to someone to help me if I get stuck. This might be off-topic on a Centos list, although some issues do seem to relate to setting permissions, ownership, virtual hosts and etc. For example, I have the registered domain setup as the first virtual host and this is done inside the httpd.conf file. So, it's basically inside ./html/public_html/ Then my second domain is setup in a vhosts.d config file. But I didn't associate a user with that. Therefore both domains seem to require that the owner is apache:apache, which is set in the httpd.conf file. How do I setup domain2.com as a second (or third) virtual host *and* setup a username/pw for accessing that domain and others. Apache is infinitely configurable. And web login users normally don't have anything to do with the permissions on the underlying files and directories. See http://httpd.apache.org/docs/2.2/howto/auth.html. You'll have to decide how you want to store the passwords and set up the restrictions on the top-level directory for each site. http://httpd.apache.org/docs/2.2/howto/auth.html -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can't find root device with lvm root after moving drive on CentOS 6.3
Grub (in the menu) has the following commands: root (hd0,1) kernel /vmlinuz-2.6.32-279.el6.x86_64 ro root=/dev/mapper/vg_resolve02-lv_root rd_NO_LUKS LANG=en.US.UTF-8 rd_NO_MD crashkernel=128M rd_LVM_LV=vg_resolve02/lv_root SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet pcie_aspm=off When I successfully booted manually, I removed rhgb quiet and added rdshell to that line. To the best of my memory, that line is stock, I don't recall ever changing it permanently. The names of the volume group and logical volume in that line correspond to my actual root device. -- Joakim Ziegler - Supervisor de postproducción - Terminal joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864 On 22/03/13 21:33, Barry Brimer wrote: When I booted the box after this, I got a kernel panic, the typical Can't find root device. Reading https://fedoraproject.org/wiki/How_to_debug_Dracut_problems , I did the following: # lvm vgscan # lvm vgchange -ay And then # ln -s /dev/mapper/volumegroup-root_volume /dev/root # exit After this, the box boots up normally, and everything works as it should. However, when I reboot, it again fails to find the root device. So, after all this, my question is, how do I make Dracut (I'm assuming) understand that this LVM volume is my root device and pick it up automatically? What does your kernel line in grub look like? Barry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can't find root device with lvm root after moving drive on CentOS 6.3
Oh, and the exact Dracut error I get is: dracut Warning: No root device block:/dev/mapper/vg_resolve02-lv_root found dracut Warning: LVM vg_resolve02/lv_root not found But then: # lvm vgscan Found volume group vg_resolve02 using metadata type lvm2 # lvm vgchange -ay 1 logical volume(s) in volume group vg_resolve02 now active # ls /dev/mapper control vg_resolve02-lv_root # ln -s /dev/mapper/vg_resolve02-lv_root /dev/root ln: creating symbolic link /dev/root: File exists # ls -l /dev/root /dev/root - dm-0 # rm /dev/root # ln -s /dev/mapper/vg_resolve02-lv_root /dev/root # exit And everything boots normally. Apologies if there are minor mistakes or omissions in this text. Since I can't copy/paste, I've transcribed it, excluding some parts, like the permissions of the symlink in the ls output. I have, however, double checked the important parts, like the names of devices and files. -- Joakim Ziegler - Supervisor de postproducción - Terminal joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864 On 23/03/13 18:55, Joakim Ziegler wrote: Grub (in the menu) has the following commands: root (hd0,1) kernel /vmlinuz-2.6.32-279.el6.x86_64 ro root=/dev/mapper/vg_resolve02-lv_root rd_NO_LUKS LANG=en.US.UTF-8 rd_NO_MD crashkernel=128M rd_LVM_LV=vg_resolve02/lv_root SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet pcie_aspm=off When I successfully booted manually, I removed rhgb quiet and added rdshell to that line. To the best of my memory, that line is stock, I don't recall ever changing it permanently. The names of the volume group and logical volume in that line correspond to my actual root device. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] How to make a network interface come up automatically on link up?
I have a recently installed Mellanox VPI interface in my server. This is an InfiniBand interface, which, through the use of adapters, can also do 10GbE over fiber. I have one of the adapter's two ports configured for 10GbE in this way, with a point to point link to a Mac workstation with a Myricom 10GbE card. I've configured this interface on the Linux box (eth2) using /etc/sysconfig/network-scripts/ifcfg-eth2 , setting its IP address, MTU, subnet, etc. Everything seems to work fine, with a single exception. If I reboot the Mac on the other end, causing the link state of the fiber interface to bounce, the network interface on the Linux box doesn't come back up when the link comes back up. That is, ifconfig shows it as having the link up, but it doesn't do the equivalent of ifup eth2 when the link comes back, so it doesn't get an IP, the routing table doesn't get updated, etc. So, my question is, how can I make CentOS automatically configure this interface when the link comes back up? It's a bit annoying having to log in and do ifup eth2 every time... -- Joakim Ziegler - Supervisor de postproducción - Terminal joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to make a network interface come up automatically on link up?
what do you find in dmesg and /var/log/messages? The system should bring it up automatically. If not, you should get an error for the prompts. Banyan He Blog: http://www.rootong.com Email: ban...@rootong.com On 3/24/2013 10:27 AM, Joakim Ziegler wrote: I have a recently installed Mellanox VPI interface in my server. This is an InfiniBand interface, which, through the use of adapters, can also do 10GbE over fiber. I have one of the adapter's two ports configured for 10GbE in this way, with a point to point link to a Mac workstation with a Myricom 10GbE card. I've configured this interface on the Linux box (eth2) using /etc/sysconfig/network-scripts/ifcfg-eth2 , setting its IP address, MTU, subnet, etc. Everything seems to work fine, with a single exception. If I reboot the Mac on the other end, causing the link state of the fiber interface to bounce, the network interface on the Linux box doesn't come back up when the link comes back up. That is, ifconfig shows it as having the link up, but it doesn't do the equivalent of ifup eth2 when the link comes back, so it doesn't get an IP, the routing table doesn't get updated, etc. So, my question is, how can I make CentOS automatically configure this interface when the link comes back up? It's a bit annoying having to log in and do ifup eth2 every time... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to make a network interface come up automatically on link up?
On Sat, 2013-03-23 at 20:27 -0600, Joakim Ziegler wrote: I have a recently installed Mellanox VPI interface in my server. This is an InfiniBand interface, which, through the use of adapters, can also do 10GbE over fiber. I have one of the adapter's two ports configured for 10GbE in this way, with a point to point link to a Mac workstation with a Myricom 10GbE card. I've configured this interface on the Linux box (eth2) using /etc/sysconfig/network-scripts/ifcfg-eth2 , setting its IP address, MTU, subnet, etc. Everything seems to work fine, with a single exception. If I reboot the Mac on the other end, causing the link state of the fiber interface to bounce, the network interface on the Linux box doesn't come back up when the link comes back up. That is, ifconfig shows it as having the link up, but it doesn't do the equivalent of ifup eth2 when the link comes back, so it doesn't get an IP, the routing table doesn't get updated, etc. So, my question is, how can I make CentOS automatically configure this interface when the link comes back up? It's a bit annoying having to log in and do ifup eth2 every time... Joakim, Do you have ONBOOT=yes in the /etc/sysconfig/network-scripts/ifcfg-eth2? -- Kind Regards Earl Ramirez GPG Key: http://trinipino.com/PublicKey.asc signature.asc Description: This is a digitally signed message part ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to make a network interface come up automatically on link up?
I do have ONBOOT=yes, yes. It comes up on boot (if there's a link), it just doesn't come up after the link goes down and comes back up. -- Joakim Ziegler - Supervisor de postproducción - Terminal joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864 On 23/03/13 21:13, Earl Ramirez wrote: On Sat, 2013-03-23 at 20:27 -0600, Joakim Ziegler wrote: I have a recently installed Mellanox VPI interface in my server. This is an InfiniBand interface, which, through the use of adapters, can also do 10GbE over fiber. I have one of the adapter's two ports configured for 10GbE in this way, with a point to point link to a Mac workstation with a Myricom 10GbE card. I've configured this interface on the Linux box (eth2) using /etc/sysconfig/network-scripts/ifcfg-eth2 , setting its IP address, MTU, subnet, etc. Everything seems to work fine, with a single exception. If I reboot the Mac on the other end, causing the link state of the fiber interface to bounce, the network interface on the Linux box doesn't come back up when the link comes back up. That is, ifconfig shows it as having the link up, but it doesn't do the equivalent of ifup eth2 when the link comes back, so it doesn't get an IP, the routing table doesn't get updated, etc. So, my question is, how can I make CentOS automatically configure this interface when the link comes back up? It's a bit annoying having to log in and do ifup eth2 every time... Joakim, Do you have ONBOOT=yes in the /etc/sysconfig/network-scripts/ifcfg-eth2? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
