Discuss October 2012

discuss@lists.centos.org

162 participants
170 discussions

CentOS-announce Digest, Vol 92, Issue 16
by centos-announce-request＠centos.org 24 Oct '12

24 Oct '12

Send CentOS-announce mailing list submissions to centos-announce(a)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-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)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. CEBA-2012:1399 CentOS 6 lvm2 Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 23 Oct 2012 19:37:57 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2012:1399 CentOS 6 lvm2 Update To: centos-announce(a)centos.org Message-ID: <20121023193757.GA17454(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2012:1399 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1399.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: feca04fc38b06a4ff4cca91a195e999cdd65db81b6397a9605482d01a07871ea cmirror-2.02.95-10.el6_3.2.i686.rpm 820bce104e3e485d9adb704eec80a8cc487b7ca015756ffab0fafcaec20be4a0 device-mapper-1.02.74-10.el6_3.2.i686.rpm 860ad02bc5659f31d16de91fb70234c0724577187a8086bd9f7670a3a348bc81 device-mapper-devel-1.02.74-10.el6_3.2.i686.rpm ec0596f15fee582caa9d1d3abf1023e880ba62fd0cc55a0e6459fafeca25edbe device-mapper-event-1.02.74-10.el6_3.2.i686.rpm 5b69cdd032e0cddbd6f9dafc2f3b081b7b19159418df63c3f890aa5c0dd108c3 device-mapper-event-devel-1.02.74-10.el6_3.2.i686.rpm e5378b28d50bb8961519447c69e52ebb6f32acd95e1bf770bb035edfd3ad528c device-mapper-event-libs-1.02.74-10.el6_3.2.i686.rpm 6c6bd9e1ad0fc9e9f9a19c0f8b95502991e2c02b33f287c88ab7399d7f27e3e5 device-mapper-libs-1.02.74-10.el6_3.2.i686.rpm d5d23a78e2881a05634e92963e46512fc3dd2b8f6eee1cb3d6aa146df8234146 lvm2-2.02.95-10.el6_3.2.i686.rpm a62008882234cb850a668545d56d7ed35791daf416de30b053d964b10f666771 lvm2-cluster-2.02.95-10.el6_3.2.i686.rpm 727ff681977a0b6a79fca65f76b85f3ff3fe54d3a0f251482f3708f060892f75 lvm2-devel-2.02.95-10.el6_3.2.i686.rpm c68a8460066dde323715bf614df0eae90f2005f929e442092cab9c12b6dec8b1 lvm2-libs-2.02.95-10.el6_3.2.i686.rpm x86_64: f78f2f7d726df57555825322fb913efb0cdb194deca03225320ca7c7eacc08c6 cmirror-2.02.95-10.el6_3.2.x86_64.rpm 60e4671d7ac6d87e882824cc2f5a96bb7a184fa98ceaebc14184dd5b62b31b34 device-mapper-1.02.74-10.el6_3.2.x86_64.rpm 860ad02bc5659f31d16de91fb70234c0724577187a8086bd9f7670a3a348bc81 device-mapper-devel-1.02.74-10.el6_3.2.i686.rpm 19560b0aeca3c820d0ed08ce95d676f48096566bcd4468ab2b72258f62e38d24 device-mapper-devel-1.02.74-10.el6_3.2.x86_64.rpm 286cd2db283315f420b25331286743e261e25867ad1309fe91911154e6acbc02 device-mapper-event-1.02.74-10.el6_3.2.x86_64.rpm 5b69cdd032e0cddbd6f9dafc2f3b081b7b19159418df63c3f890aa5c0dd108c3 device-mapper-event-devel-1.02.74-10.el6_3.2.i686.rpm 122af42f772bdba3d4db970cc84e2b4356dd00b3179a09810f71214da03b21cc device-mapper-event-devel-1.02.74-10.el6_3.2.x86_64.rpm e5378b28d50bb8961519447c69e52ebb6f32acd95e1bf770bb035edfd3ad528c device-mapper-event-libs-1.02.74-10.el6_3.2.i686.rpm cdd1c74cde730a9f4f9a8c064891ec7dd588e1dec502cee5bb2496705245ba01 device-mapper-event-libs-1.02.74-10.el6_3.2.x86_64.rpm 6c6bd9e1ad0fc9e9f9a19c0f8b95502991e2c02b33f287c88ab7399d7f27e3e5 device-mapper-libs-1.02.74-10.el6_3.2.i686.rpm 77c0c2a77388dbade4d2fc566f31611f9ad1aefb5fe89e5c1ece6dfcebd292c8 device-mapper-libs-1.02.74-10.el6_3.2.x86_64.rpm e004f68d8bd11df66de601a67f9009f35c8ed5fcac1741cf633353c9472c0532 lvm2-2.02.95-10.el6_3.2.x86_64.rpm cbeba58d390691e48ae1636b790ac91e51c60207f5d061a4a1b098a76159c480 lvm2-cluster-2.02.95-10.el6_3.2.x86_64.rpm 727ff681977a0b6a79fca65f76b85f3ff3fe54d3a0f251482f3708f060892f75 lvm2-devel-2.02.95-10.el6_3.2.i686.rpm 15652b236bee326de6af0a26fd81bf05a4076e2a50b571ecb4c1fc7a8ba7c601 lvm2-devel-2.02.95-10.el6_3.2.x86_64.rpm c68a8460066dde323715bf614df0eae90f2005f929e442092cab9c12b6dec8b1 lvm2-libs-2.02.95-10.el6_3.2.i686.rpm 967ac24f484626bf9ab4176e49cdf17e0b3ebe70b47d6ea7197efc3f4412561b lvm2-libs-2.02.95-10.el6_3.2.x86_64.rpm Source: f709977c75f1fb3ebe08df88e5bc308dd46d9639e37b09333d829ea9a64ec48d lvm2-2.02.95-10.el6_3.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 92, Issue 16 ***********************************************

1 0

Getting 8139cp (1.3) and 8139too (0.9.28) on Centos 5.8
by Jerry Geis 24 Oct '12

24 Oct '12

Subject says it all. How can I get the 1.3 version and 0.9.28 to compile on CentOS 5.8 ??? When I compile the two as modules I get errors. My Makefile is: obj-m += 8139cp.o 8139too.o all: make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules clean: make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean The errors I get are: Entering directory `/usr/src/kernels/2.6.18-308.4.1.el5-i686' CC [M] /home/silentm/MessageNet/realtek/8139cp.o /home/silentm/MessageNet/realtek/8139cp.c: In function ‘cp_rx_skb’: /home/silentm/MessageNet/realtek/8139cp.c:430: error: ‘struct net_device’ has no member named ‘stats’ /home/silentm/MessageNet/realtek/8139cp.c:431: error: ‘struct net_device’ has no member named ‘stats’ /home/silentm/MessageNet/realtek/8139cp.c: In function ‘cp_rx_err_acct’: /home/silentm/MessageNet/realtek/8139cp.c:444: error: ‘struct net_device’ has no member named ‘stats’ /home/silentm/MessageNet/realtek/8139cp.c:446: error: ‘struct net_device’ has no member named ‘stats’ /home/silentm/MessageNet/realtek/8139cp.c:448: error: ‘struct net_device’ has no member named ‘stats’ /home/silentm/MessageNet/realtek/8139cp.c:450: error: ‘struct net_device’ has no member named ‘stats’ /home/silentm/MessageNet/realtek/8139cp.c:452: error: ‘struct net_device’ has no member named ‘stats’ /home/silentm/MessageNet/realtek/8139cp.c:454: error: ‘struct net_device’ has no member named ‘stats’ /home/silentm/MessageNet/realtek/8139cp.c: In function ‘cp_rx_poll’: /home/silentm/MessageNet/realtek/8139cp.c:504: error: ‘struct net_device’ has no member named ‘stats’ /home/silentm/MessageNet/realtek/8139cp.c:519: error: ‘struct net_device’ has no member named ‘stats’ /home/silentm/MessageNet/realtek/8139cp.c:568: error: implicit declaration of function ‘__napi_complete’ /home/silentm/MessageNet/realtek/8139cp.c: In function ‘cp_interrupt’: /home/silentm/MessageNet/realtek/8139cp.c:605: error: implicit declaration of function ‘napi_schedule_prep’ /home/silentm/MessageNet/realtek/8139cp.c:607: error: implicit declaration of function ‘__napi_schedule’ /home/silentm/MessageNet/realtek/8139cp.c: In function ‘cp_tx’: /home/silentm/MessageNet/realtek/8139cp.c:673: error: ‘struct net_device’ has no member named ‘stats’ Thanks, Jerry

2 1

mount -o loop question.
by Jobst Schmalenbach 24 Oct '12

24 Oct '12

Hi, I know I can create a file and mount it like this: dd if=/dev/zero of=/tmp/somefile bs=1024 count=100000 mke2fs /tmp/somefile mount /tmp/somefile /mnt -o loop but that has a problem it cannot grow. Is there a way to do the same (above) but have it not restricted to a size? Or can I append blocks to the end of the file without distroying it? Jobst -- Sendmail administration is not black magic. There are legitimate technical reasons why it requires the sacrificing of a live chicken. | |0| | Jobst Schmalenbach, jobst(a)barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L & The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia

4 6

CentOS-announce Digest, Vol 92, Issue 15
by centos-announce-request＠centos.org 23 Oct '12

23 Oct '12

1 0

CentOS 6 NFS mmap I/O bug?
by Tom McDonald 22 Oct '12

22 Oct '12

I'm working with a company who is running into an issue occasionally with their app running CentOS 6 on an NFS mount. The problem is essentially that, from a single CentOS 6 client, the client sometimes gets the wrong file size back from a stat() call. The problem specifically seems to happen after mmap and ftruncate calls. The former envionrment for the application was CentOS 4 where is has run for many years with no apparent issues. Here's an strace output showing the problem: 13:10:38.270134 stat("trunk_file14", {st_mode=S_IFREG|0600, st_size=36528128, ...}) = 0 <0.000019> 13:10:38.270204 open("trunk_file14", O_RDWR|O_SYNC) = 3 <0.000440> 13:10:38.270688 mmap(NULL, 36528128, PROT_READ|PROT_WRITE, MAP_SHARED, 3, 0) = 0x7f57bade3000 <0.003543> 13:10:38.275585 msync(0x7f57bade3000, 36527128, MS_SYNC) = 0 <0.000534> 13:10:38.276176 munmap(0x7f57bade3000, 36528128) = 0 <0.000026> 13:10:38.276240 ftruncate(3, 36527128) = 0 <0.000463> 13:10:38.276744 close(3) = 0 <0.000020> 13:10:38.276794 stat("trunk_file14", {st_mode=S_IFREG|0600, st_size=36528128, ...}) = 0 <0.000020> Note that the file size returned in the last stat() following the close() returns the size of the file prior to the ftruncate (36528128, but should be 36527128). Normally, this final stat() will return the correct file size, but every now and then we get this. After waiting a few seconds another stat to the file will show the expected file size which would be 36527128 in this case. The NFS client is using mount options "tcp,nfsvers=3". The process is also single threaded, and there's no expectation for the I/O to appear to behave synchronously beyond more than a single NFS client. We're suspicious that the CentOS 6 NFS client is not caching properly. Additional testing is happening now, but it also appears that it may only happen when the memory map calls are in place ( mmap(), memmove(), and msync() ). We don't expect the files to We have reproduced this issue with both CentOS 6.0 and 6.3 on multiple NFS servers from different vendors. Any help is appreciated. I've attached a small C program I've hacked together to reproduce the problem in case anyone is interested. Thanks, Tom

2 2

SELinux AVC problem postfix <-> dspam
by Patrick Lists 22 Oct '12

22 Oct '12

Hi, I guess this is a bit OT but perhaps someone has encountered this issue before. On a CentOS 6.3 x86_64 box I have installed postfix and dspam from EPEL. Dspam is configured to listen on port 10026. After having configured dspam and postfix I start dspam and then postfix and I see the following AVC message in audit.log: type=AVC msg=audit(1350920492.936:400): avc: denied { name_bind } for pid=19971 comm="master" src=10026 scontext=unconfined_u:system_r:postfix_master_t:s0 tcontext=system_u:object_r:postfix_master_t:s0 tclass=tcp_socket type=SYSCALL msg=audit(1350920492.936:400): arch=c000003e syscall=49 success=no exit=-13 a0=5b a1=7f015fa63b30 a2=10 a3=7fff6b2bf89c items=0 ppid=1 pid=19971 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4 comm="master" exe="/usr/libexec/postfix/master" subj=unconfined_u:system_r:postfix_master_t:s0 key=(null) When I run sudo grep 1350920492 /var/log/audit/audit.log | audit2allow -M postfix-dspam I get: $ cat postfix-dspam.te module pf 1.0; require { type postfix_master_t; class tcp_socket name_bind; } #============= postfix_master_t ============== allow postfix_master_t self:tcp_socket name_bind; To fix this issue activate the postfix-dspam policy with: # semodule -i postfix-dspam.pp Can anyone confirm this is the correct way to fix this problem? Should I file a bug? Thanks and regards, Patrick

1 1

Adding an MT9234ZBA-USB modem to CentOS6.3
by James B. Byrne 22 Oct '12

22 Oct '12

How, exactly, does CentOS-6.3 with udev recognize an USB modem when it is plugged in. How is it indicated? What other configuration is required? I can find the modem in /sys/class/tty and I can get the attributes using udevadm but I do not see anything in ps that refers to the modem device. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 3

r8712u wireless driver
by David A. De Graaf 22 Oct '12

22 Oct '12

I've just installed centos 6.3 for the first time on a test machine and couldn't be happier - except that a critical wireless adapter driver is missing - the r8712u. I would love to convert my mythtv machine from Fedora 17 to centos 6.3 to put all that chaos and instability behind me. My mythtv machine connects only wirelessly to the rest of my network and uses a Rosewill RNX-N180UBE USB adapter. This adapter has a larger than normal antenna with 5db of gain and supports 802.11n protocol. This provides greater bandwidth and a more reliable connection than any previously tested wireless adapter. However, it requires the r8712u driver that is absent from centos 6.3 and all the repos that I've examined. The elrepo repo has a number of packages that are close, but unfortunately not the r8712u. This driver is available for Fedora 17 in the kmod-staging package. Is there any chance to adapt this package for centos 6.3? Or at least the r8712u driver portion thereof? Any suggestions to solve this dilemma? -- David A. De Graaf DATIX, Inc. Hendersonville, NC dad(a)datix.us www.datix.us

2 2

swapper: page allocation failure. order:1, mode:0x20
by Tim Nelson 22 Oct '12

22 Oct '12

I see this ocasionally on one of my CentOS 6.3 x64 systems: Oct 18 03:10:52 backup kernel: swapper: page allocation failure. order:1, mode:0x20 Oct 18 03:10:52 backup kernel: Pid: 0, comm: swapper Not tainted 2.6.32-279.9.1.el6.x86_64 #1 Oct 18 03:10:52 backup kernel: Call Trace: Oct 18 03:10:52 backup kernel: <IRQ> [<ffffffff8112789f>] ? __alloc_pages_nodemask+0x77f/0x940 Oct 18 03:10:52 backup kernel: [<ffffffff811620a2>] ? kmem_getpages+0x62/0x170 Oct 18 03:10:52 backup kernel: [<ffffffff81162cba>] ? fallback_alloc+0x1ba/0x270 Oct 18 03:10:52 backup kernel: [<ffffffff8116270f>] ? cache_grow+0x2cf/0x320 Oct 18 03:10:52 backup kernel: [<ffffffff81162a39>] ? ____cache_alloc_node+0x99/0x160 Oct 18 03:10:52 backup kernel: [<ffffffff8116381b>] ? kmem_cache_alloc+0x11b/0x190 Oct 18 03:10:52 backup kernel: [<ffffffff8142dfa8>] ? sk_prot_alloc+0x48/0x1c0 Oct 18 03:10:52 backup kernel: [<ffffffff8142e272>] ? sk_clone+0x22/0x2e0 Oct 18 03:10:52 backup kernel: [<ffffffff8147bfa6>] ? inet_csk_clone+0x16/0xd0 Oct 18 03:10:52 backup kernel: [<ffffffff81494f83>] ? tcp_create_openreq_child+0x23/0x450 Oct 18 03:10:52 backup kernel: [<ffffffff814927ed>] ? tcp_v4_syn_recv_sock+0x4d/0x310 Oct 18 03:10:52 backup kernel: [<ffffffff81494d26>] ? tcp_check_req+0x226/0x460 Oct 18 03:10:52 backup kernel: [<ffffffff8148a6d6>] ? tcp_rcv_state_process+0x126/0xa10 Oct 18 03:10:52 backup kernel: [<ffffffff8149220b>] ? tcp_v4_do_rcv+0x35b/0x430 Oct 18 03:10:52 backup kernel: [<ffffffff8142fd97>] ? __kfree_skb+0x47/0xa0 Oct 18 03:10:52 backup kernel: [<ffffffff81493a4e>] ? tcp_v4_rcv+0x4fe/0x8d0 Oct 18 03:10:52 backup kernel: [<ffffffff81492193>] ? tcp_v4_do_rcv+0x2e3/0x430 Oct 18 03:10:52 backup kernel: [<ffffffff814716dd>] ? ip_local_deliver_finish+0xdd/0x2d0 Oct 18 03:10:52 backup kernel: [<ffffffff81471968>] ? ip_local_deliver+0x98/0xa0 Oct 18 03:10:52 backup kernel: [<ffffffff81470e2d>] ? ip_rcv_finish+0x12d/0x440 Oct 18 03:10:52 backup kernel: [<ffffffff814713b5>] ? ip_rcv+0x275/0x350 Oct 18 03:10:52 backup kernel: [<ffffffff8104efd4>] ? scale_rt_power+0x24/0x80 Oct 18 03:10:52 backup kernel: [<ffffffff8143aafb>] ? __netif_receive_skb+0x49b/0x6f0 Oct 18 03:10:52 backup kernel: [<ffffffff81490d3a>] ? tcp4_gro_receive+0x5a/0xd0 Oct 18 03:10:52 backup kernel: [<ffffffff8143cd78>] ? netif_receive_skb+0x58/0x60 Oct 18 03:10:52 backup kernel: [<ffffffff8143ce80>] ? napi_skb_finish+0x50/0x70 Oct 18 03:10:52 backup kernel: [<ffffffff8143f3b9>] ? napi_gro_receive+0x39/0x50 Oct 18 03:10:52 backup kernel: [<ffffffffa025af2f>] ? bnx2_poll_work+0xd4f/0x1270 [bnx2] Oct 18 03:10:52 backup kernel: [<ffffffff810632bb>] ? enqueue_task_fair+0xb/0x100 Oct 18 03:10:52 backup kernel: [<ffffffffa025b579>] ? bnx2_poll+0x69/0x2d8 [bnx2] Oct 18 03:10:52 backup kernel: [<ffffffff8106010c>] ? try_to_wake_up+0x24c/0x3e0 Oct 18 03:10:52 backup kernel: [<ffffffff8143f4d3>] ? net_rx_action+0x103/0x2f0 Oct 18 03:10:52 backup kernel: [<ffffffff81073f41>] ? __do_softirq+0xc1/0x1e0 Oct 18 03:10:52 backup kernel: [<ffffffff810dbb00>] ? handle_IRQ_event+0x60/0x170 Oct 18 03:10:52 backup kernel: [<ffffffff8100c24c>] ? call_softirq+0x1c/0x30 Oct 18 03:10:52 backup kernel: [<ffffffff8100de85>] ? do_softirq+0x65/0xa0 Oct 18 03:10:52 backup kernel: [<ffffffff81073d25>] ? irq_exit+0x85/0x90 Oct 18 03:10:52 backup kernel: [<ffffffff81506095>] ? do_IRQ+0x75/0xf0 Oct 18 03:10:52 backup kernel: [<ffffffff8100ba53>] ? ret_from_intr+0x0/0x11 Oct 18 03:10:52 backup kernel: <EOI> [<ffffffff81014877>] ? mwait_idle+0x77/0xd0 Oct 18 03:10:52 backup kernel: [<ffffffff8150392a>] ? atomic_notifier_call_chain+0x1a/0x20 Oct 18 03:10:52 backup kernel: [<ffffffff81009e06>] ? cpu_idle+0xb6/0x110 Oct 18 03:10:52 backup kernel: [<ffffffff814e48da>] ? rest_init+0x7a/0x80 Oct 18 03:10:52 backup kernel: [<ffffffff81c21f7b>] ? start_kernel+0x424/0x430 Oct 18 03:10:52 backup kernel: [<ffffffff81c2133a>] ? x86_64_start_reservations+0x125/0x129 Oct 18 03:10:52 backup kernel: [<ffffffff81c21438>] ? x86_64_start_kernel+0xfa/0x109 Any thoughts on the cause? The system has 16GB of RAM, and whenever checked, there is no swap usage. Is this a memory error (bad RAM)? --Tim

4 8

ext3 partition on LVM lost all data
by HALAC Matej 22 Oct '12

22 Oct '12

Hello Gentlemen, I would like to ask a question about an issue I have with the Centos 6.3 installation. I have installed a Centos 6.3 on a server we used before with 5.4 on Friday. I have created a KS file to let me connect to the server via VNC and have all repos and packages preconfigured. I only needed to partition the hard drive using VNC. During the partition process I selected which volumes should be formatted and which should be left alone. The installation went perfectly, without a problem. I added the server to our Puppet infrastructure and started to assign modules to it. After I have installed and configured samba I wanted to mount the data volume so that people could continue their work on Monday. Unfortunately the partition was empty. Only the lost+found directory was present. Can you please tell me what went wrong? Or if this can be fixed somehow? Here is the anaconda generated KS file that is based on my own that I included in my Centos image: # Kickstart file automatically generated by anaconda. #version=DEVEL install cdrom lang en_US.UTF-8 keyboard us network --onboot yes --device eth0 --mtu=1500 --bootproto static --ip <server IP> --netmask 255.255.255.0 --gateway <our gateway> --noipv6 --nameserver 8.8.8.8 --hostname newserver rootpw --iscrypted <root password> # Reboot after installation reboot firewall --service=ssh authconfig --enableshadow --passalgo=sha512 selinux --enforcing timezone --utc Europe/Bratislava bootloader --location=mbr --driveorder=ddf1_Default --append="crashkernel=auto rhgb quiet" # 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 --none #volgroup VolGroup00 --pesize=32768 --useexisting --noformat pv.253002 #logvol None --fstype=ext3 --name=LogVol00_data --vgname=VolGroup00 --useexisting --noformat #logvol /home --fstype=ext4 --name=LogVol00_home --vgname=VolGroup00 --useexisting #logvol / --fstype=ext4 --name=LogVol00_root --vgname=VolGroup00 --useexisting #logvol swap --name=LogVol00_swap --vgname=VolGroup00 --useexisting #logvol /tmp --fstype=ext4 --name=LogVol00_tmp --vgname=VolGroup00 --useexisting #logvol /var --fstype=ext4 --name=LogVol00_var --vgname=VolGroup00 --useexisting #part /boot --fstype=ext4 --onpart=ddf1_Defaultp1 #part pv.253002 --onpart=ddf1_Defaultp2 --noformat repo --name="CentOS" --baseurl=cdrom:sr0 --cost=100 repo --name="Centos 6.3 Base - x86_64" --baseurl= --cost=1000 repo --name="Centos 6.3 Extras - x86_64" --baseurl= --cost=1000 repo --name="Centos 6.3 Updates - x86_64" --baseurl= --cost=1000 repo --name="epel" --baseurl= --cost=1000 repo --name="puppet" --baseurl=http://yum.puppetlabs.com/el/6/products/x86_64/ --cost=1000 %packages @Base @Core @base @core @hardware-monitoring @server-platform @server-policy epel-release pax puppet puppetlabs-release sgpio -hunspell -hunspell-en %end -- HALAC Matej

2 1

← Newer
1
2
3
4
5
6
7
8
9
...
17
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss October 2012