devel November 2008

devel@lists.centos.org

45 participants
42 discussions

Isolinux.cfg + multiple ks.cfg problem
by Richard J 04 Nov '08

04 Nov '08

Hi, I am working on to add two installation options in the isolinux.cfg file. The options are: 1) To automatically install centos (including partitioning the HDD) 2) Manual installation and disk partition For that I used different ks.cfg files: 1) auto.ks.cfg - For automatic installation 2) ks.cfg - for manual installation To select the installation option I edited the isolinux.cfg file as follows: ################################################################ default linux prompt 1 timeout 600 display boot.msg F1 boot.msg F2 options.msg F3 general.msg F4 param.msg F5 rescue.msg F7 snake.msg label linux kernel vmlinuz append initrd=initrd.img text ramdisk_size=8192 ks=cdrom:/auto.ks.cfg nousb nopcmcia label text kernel vmlinuz append initrd=initrd.img text ramdisk_size=8192 ks=cdrom:/ks.cfg nousb nopcmcia ################################################################ But the problem is when I write "linux text" it starts the 'Automatic' installation. When I done write anything and pressed Enter then also automatic installation starts. Although when i typed 'text' and pressed Enter then 'Manual' installation started. My question is: in the default linux distro when 'linux text' is entered then the installation starts in the text mode else in the graphical mode. I also need to make a similar setup for 'automatic' and 'manual' installation. Can anyone help me out in this matter. Help is much appreciated. :-) Thanks, Richard

1 0

Re: [packagers] Re: [svn] r6530 - in trunk/tools: . centos-rescue centos-rescue/fset centos-rescue/skelroot centos-rescue/skelroot/etc
by Dag Wieers 03 Nov '08

03 Nov '08

On Mon, 3 Nov 2008, Dag Wieers wrote: > We have a big issue where it works for simple initramfs archives (the minimal > one), but it consistently fails for big ones (40MB). While it does work for > the RIPLinux initramfs which is 45MB. We have to make the ramdisk_size extremely big (now using 128000) for my image. The original uncompressed RIPLinux initramfs is 90M. Ours is 105M :-/ (And missing the kernel modules, we might want to make an all-in CentOS kernel) I guess we have to discuss some of the details, what we want to accomplish and how we want to do that. I am interested in: - a tool to generate custom initramfs for specific applications to boot directly into, eg ncurses frontends for wiping or ghosting disks, troubleshooting hardware and network problems (this is what I need right now) and other things - a ready-to-go rescue image that people can install in their boot-loader (or maybe we can provide by default ?) so that in case of a real problem (something important for booting trashed) they can find the problem and fix it - a full RIPLinux alike recovery CD including documentation and tools to recover systems (ISO, USB, PXE) using the default CentOS kernel - same full recovery CD with a very recent kernel with more features, the same initramfs could be used for this and the above if all modules are compiled in the kernel (like with RIPLinux) RIPLinux currently also has an X version with a lot more stuff like firefox, flash, minimal window manager, gparted, ... but for me that is not a priority. A full-fledged live cd seems more appropriate for a graphical environment. -- -- dag wieers, dag(a)wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors]

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel November 2008