Discuss

discuss@lists.centos.org

34758 discussions

RE: [CentOS] Getting CentOS Server CD w/kickstart config
by Plant, Dean 17 May '07

17 May '07

Devin Atencio wrote: > I would like to how how I can take the CentOS 4.4 Server Cd for > example and modify the > ISO to put on my anaconda-ks.cfg file and then modify the kernel > parameters to automatically > load the anaconda-ks.cfg file so that I can create a CD that I just > stick into my machine it will > format the drive, install the basic configuration I like without > asking any questions. I need to > install like 20 machines and I wanted to basically just stick a CD in > the drive and let it do it's thing. > > Any help on how to accomplish this would be appreciated. > Here's how I did it for RHEL CD's -------------------------------------------------- Construct a single DVD from the four RHEL CDRom's Insert & mount CD1 # mkdir /DVD # mount /dev/cdrom /media/cdrecorder Copy cd1 to /DVD # cd /media/cdrecorder # tar cf - . | (cd /DVD ; tar xvf - .) # cd / # eject cdrom Carry out the above action for CD 2-4 After all CD's have been copied. Correct the .discinfo file to reference all four disks. # cd /DVD # vi .discinfo Ensure line 4 has 1,2,3,4 A working .discinfo should be as follows. # cat .discinfo 1141417589.425945 Red Hat Enterprise Linux 4 i386 1,2,3,4 RedHat/base RedHat/RPMS RedHat/pixmaps Create the bootable ISO file. (all on one line) # mkisofs -A "RHEL/4.3 i386 3AS" -o DVD.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -R -J -v -T /DVD Burn the DVD.iso as an image not a file. References http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/x8664-multi- install-guide/s1-steps-install-cdrom.html Modify the DVD to include custom kickstart scripts. Create the /DVD tree as per the previous steps. The default files read on boot up of an RH install CDRom are located in /isolinux/ To run custom kickstart scripts we need to modify the /isolinux/isolinux.cfg and add the kickstart file to the boot process. See here for kickstart script generation. For each kickstart install we need to add 3 lines to the isolinux.cfg file. A label line - This is the identifier you type at the linux boot prompt A kernel line - This does not change A append line - This is where we tell the boot process to use a kickstart file. Firstly backup the original file. # cp /DVD/isolinux/isolinux.cfg /DVD/isolinux/isolinux.cfg.orig Now edit and add our custom kickstart file. # vi /DVD/isolinux/isolinux.cfg Add label myboot1 kernel vmlinuz append initrd=initrd.img ramdisk_size=8192 ks=cdrom:/ks.cfg This will enable you to type myboot1 at the boot prompt which will call the ks.cfg located in the / of the DVD disk. Multiple kickstart files can be added by using different label and append lines. For Example: label myboot1 kernel vmlinuz append initrd=initrd.img ramdisk_size=8192 ks=cdrom:/ks1.cfg label myboot2 kernel vmlinuz append initrd=initrd.img ramdisk_size=8192 ks=cdrom:/ks2.cfg -------------------------------------------------- Have fun. Dean

1 0

Re: [CentOS] Make Raid1 2nd disk bootable?
by David G. Miller 17 May '07

17 May '07

Les Mikesell <lesmikesell(a)gmail.com> wrote: > David G. Miller wrote: >> > >> >>> >> Grub isn't so much the issue here as the difference in the rescue mode >>> >> boot. I'm used to being able to boot the CD, chroot into the existing >>> >> system and have pretty much normal access regardless of what was >>> >> broken. Now that the system /dev directory is basically empty, things >>> >> don't work when you have to mount the partitions manually. Is there >>> >> a step to set up devices so the chroot will work? >>> >> > >> > I haven't tried this but were you looking at /dev *after* you did the >> > chroot? It sort of makes sense to me that the running kernel would only >> > populate it's /dev, not the chrooted /dev. Rescue mounts at least the >> > root partition under /mnt/sys (or something like that). Before you >> > chroot, you should probably also mount any other partitions you want >> > under /mnt/sys and then chroot. >> > > It makes sense for the boot code, but not for me afterwards... The real > problem is that the rescue mode startup doesn't mount RAID1 partitions > at all (this seems like a bug). The startup code might populate the > chroot'ed /dev if it had done the mount - I just haven't found how to do > it myself after doing the mount by hand. Thus there's no /dev/sda or > /dev/sdb as you'd expect when you want to install grub. Let me try explaining this a different way. After you let the rescue software mount the partition, *don't* chroot. It's been a long time since I had to mess with booting in rescue mode but lets assume your old root partition gets mounted under /mnt/sysimage and you told the rescue software to go ahead and mount it. If your /boot is a separate partition, you'll need to mount it manually. Assuming you keep everything where it belongs, mount it under /mnt/sysimage/boot. Then run grub by doing: /mnt/sysimage/sbin/grub --config-file=/mnt/sysimage/boot/grub/grub.conf This way grub "sees" /dev for the running system but uses your real grub config file. You may want to confirm that grub.conf has what you want in it. Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce

2 1

Getting CentOS Server CD w/kickstart config
by Devin Atencio 17 May '07

17 May '07

I would like to how how I can take the CentOS 4.4 Server Cd for example and modify the ISO to put on my anaconda-ks.cfg file and then modify the kernel parameters to automatically load the anaconda-ks.cfg file so that I can create a CD that I just stick into my machine it will format the drive, install the basic configuration I like without asking any questions. I need to install like 20 machines and I wanted to basically just stick a CD in the drive and let it do it's thing. Any help on how to accomplish this would be appreciated. Devin Atencio

2 1

Cuba and tzdata-2007d-1.el5
by Jesús García González 17 May '07

17 May '07

Hello all, It seems, tzdata-2007d-1.el5.noarch.rpm contains information about Cuba/Havana time zone that activates DST at a time other than the one that is going on in the country... Is there an updated tzdata somewhere correcting this info? or how can I correct this on my own? Thanks, J.

1 0

centos rsync paths: cobbler
by Karl R. Balsmeier 17 May '07

17 May '07

am using cobbler to import via rsync -and having trouble munging paths properly to download the 64-bit dvd or others, -what's a known good rsync path to use, or a command line that would allow me to determine this myself? When I use the web browsers of course and go to centos.org, you'll get the usual "not a suppoorted protocol" when clicking around trying to isolate a good path/server. i'm doing: cobbler import --mirror=rsync://need.servername.domain/path/to/centos86_64 --name=centos64 -any suggestions? (sorry, new to this, but definitely interested in rolling out cobbler). -krb

2 1

CentOS-announce Digest, Vol 27, Issue 9
by centos-announce-request＠centos.org 17 May '07

17 May '07

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. CESA-2007:0354 Critical CentOS 3 ia64 samba - security update (Pasi Pirhonen) 2. CESA-2007:0354 Critical CentOS 4 ia64 samba - security update (Pasi Pirhonen) 3. CESA-2007:0065 Moderate CentOS 4 ia64 bluez-utils - security update (Pasi Pirhonen) 4. CESA-2007:0354 Critical CentOS 3 s390(x) samba - security update (Pasi Pirhonen) 5. CESA-2007:0354 Critical CentOS 4 s390(x) samba - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Wed, 16 May 2007 20:19:22 +0300 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2007:0354 Critical CentOS 3 ia64 samba - security update To: centos-announce(a)centos.org Message-ID: <20070516171921.GP26635(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2007:0354 https://rhn.redhat.com/errata/RHSA-2007-0354.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/samba-3.0.9-1.3E.13.2.ia64.rpm updates/ia64/RPMS/samba-client-3.0.9-1.3E.13.2.ia64.rpm updates/ia64/RPMS/samba-common-3.0.9-1.3E.13.2.ia64.rpm updates/ia64/RPMS/samba-swat-3.0.9-1.3E.13.2.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

problem with Clam AV
by Rajeev R Veedu 17 May '07

17 May '07

I had updated clam antivirus recently (with YUM) and since then the following error is appear when my cron job runs The cron job and the output is list below: /usr/bin/freshclam --quiet -l /var/log/clam-update.log ERROR: Parse error at line 44: Option AllowSupplementaryGroups requires boolean argument. ERROR: Parse error at line 76: Option FixStaleSocket requires boolean argument. ERROR: Can't parse the config file /etc/clamd.conf Can you please help me to remove this error? Thanks Rajeev

5 6

Re: [CentOS] Re: Anaconda doesn't support raid10
by Lanny Marcus 17 May '07

17 May '07

>Message: 31 >Date: Tue, 15 May 2007 11:25:42 +0800 >From: Feizhou <feizhou(a)graffiti.net> >Subject: Re: [CentOS] Re: Anaconda doesn't support raid10 >Message-ID: <46492836.3010808(a)graffiti.net> <snip> <the reliability factor has been proven to be the same across the board. <You must have missed the thread on the Google report on various drives <that they use Feizhou: Yes, I did not see that. If the MTBF's are the same, then the Performance specs you provided are what one needs to go with, when choosing components. If Google has posted Failure rates, for the drives they use, that would be more meaningful than MTBF by the drive manufacturer, for that particular drive model. Questions: Is it your belief that all PATA/SATA/SCSI drives made by one manufacturer have the same MTBF? (I find that hard to believe. However, that might be the case.....) Also, is it your belief that these drives, made by different manufacturers, all have the same MTBF? >Who says? You? I like to have an online offsite RAID backup server. Is >there an ONE TRUE WAY OF BACKUP? No. Obviously, there is no one true way of backup. Everyone's needs are different. Your online off site RAID backup server is one way. Backups *must* be off site, in the event of a catastrophic problem. Thank you, for sharing your time and knowledge with the list! Lanny

3 3

Hotplug on CentOS 5
by Rodrigo Barbosa 17 May '07

17 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As some of you might have noticed, CentOS 5 doesn't ship with hotplug (linux-hotplug.sourceforge.net) Things get handled directly by HAL, as far as I can tell. This is ok as long as you are using gnome/kde. However, on a TUI box, or when you are running another WM (I use IceWM here), you can't count o HAL. Actually, HAL (as shipped on CentOS 5) doesn't even have fstab-sync anymore. Anyway, the interface for /proc/sys/kernel/hotplug is pretty simple and straighforward. Coding something to handle just the devices I use is very easy. However, I'm actually considering building and using hotplug on CentOS 5. Anyone has tried it yet ? Any word of advice, or other mathods of handling this situation ? Best Regards, - -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFGS7aYpdyWzQ5b5ckRAkvMAJ45H/6VSEiJApoX2w/R3ks1UjxqSQCeP3Pj 7pwV4yRE5wECpGyh5mjCRxE= =yS5U -----END PGP SIGNATURE-----

1 0

postfix
by CentOS List 17 May '07

17 May '07

Hi, Can someone point me to a step by step tutorial to install a postfix toaster? Thanks

6 6

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss