[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: grub.conf



It might be easier to do this in %post rather than modify anaconda. 
This is how we enable output to both serial port and physical console:

%post
# enable serial console in grub
sed -e '12i\
serial --unit=0 --speed=9600 -word=8 --parity=no --stop=1\
terminal --timeout=7 serial console' /boot/grub/grub.conf >/tmp/grub &&
mv /tmp/grub /boot/grub/grub.conf
# enable serial console in linux
sed -e '/kernel \/vmlinuz-2/s/$/ console=ttyS0,9600n8 console=tty0 /g'
/boot/grub/grub.conf >/tmp/grub && mv /tmp/grub /boot/grub/grub.conf

I think that you would want to eliminate "console" and "console=tty0"
from the above two lines respectively, to only enable the serial output.

-Ed 



On Tue, 2003-11-18 at 11:24, Jason Montleon wrote:
> Where/how does anaconda generate grub.conf?  I am trying to modify the first
> Fedora CD to handle an install for a headless system, such that I should
> basically never have to put a monitor/mouse/keyboard on it.  Technically it
> is possible now, but I'd like to go just one step fruther...
> 
> What I have done is this:
> Modify the isolinux.cfg to spit output to a serial console; just append
> console=ttyS0,9600
> Modify the initscripts package such that /etc/inittab contains the line
> 0:12345:respawn:/sbin/agetty ttyS0 9600
> Modify the setup package so that /etc/securetty contains ttyS0 as a secure
> tty
> 
> I think all that I'm missing now is a method in which I can alter the
> anaconda generated grub.conf to output to a serial interface; which I know
> how to do if I can alter how anaconda generates it...
> 
> 
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list redhat com
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]