RE: [qmailtoaster] QMTISO, Kickstart, drivers and updates

2007-10-24 Thread Aaron Spurlock
Well, I got the kickstart installation to prompt for network information by following a post found here: http://osdir.com/ml/linux.redhat.kickstart.general/2004-03/msg00079.html Since the Dell floppy I was using already had packages.py on it, I just took and modified kickstart.py and put it on

Re: [qmailtoaster] QMTISO, Kickstart, drivers and updates

2007-10-24 Thread Jake Vickers
Aaron Spurlock wrote: Well, I got the kickstart installation to prompt for network information by following a post found here: http://osdir.com/ml/linux.redhat.kickstart.general/2004-03/msg00079.html Since the Dell floppy I was using already had packages.py on it, I just took and modified

RE: [qmailtoaster] QMTISO, Kickstart, drivers and updates

2007-10-24 Thread Aaron Spurlock
[mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 10:20 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] QMTISO, Kickstart, drivers and updates Aaron Spurlock wrote: Well, I got the kickstart installation to prompt for network information by following a post found

RE: RE: [qmailtoaster] QMTISO, Kickstart, drivers and updates

2007-10-24 Thread Aaron Spurlock
:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 11:24 AM To: qmailtoaster-list@qmailtoaster.com Subject: RE: [qmailtoaster] QMTISO, Kickstart, drivers and updates Actually the NIC problem is just a symptom of the problem. Cent does have NIC drivers for my system, but not drivers for the Dell

Re: [qmailtoaster] QMTISO, Kickstart, drivers and updates

2007-10-24 Thread Jake Vickers
Aaron Spurlock wrote: Okay, now this doesn't make sense to me...I took a generic CentOS4.4 ServerCD and put a ks.cfg on it. Granted, it was a pretty generic ks.cfg. I then booted and issued the command: linux text ks=cdrom:/ks.cfg dd updates noapic acpi=off skipddc to try to be compatible

Re: [qmailtoaster] QMTISO, Kickstart, drivers and updates

2007-10-24 Thread Jake Vickers
Aaron Spurlock wrote: Okay, I wanted to verify that is wasn't the kickstart process, so I launched the QMTISO install with: linux dd updates noapic acpi=off skipddc So no kickstart file at all. It read in the Dell driver disk, installed a minimal system--with the network configured--and

Re: [qmailtoaster] QMTISO, Kickstart, drivers and updates

2007-10-24 Thread Erik A. Espinoza
[mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 1:02 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] QMTISO, Kickstart, drivers and updates Aaron Spurlock wrote: Okay, now this doesn't make sense to me...I took a generic CentOS4.4 ServerCD and put a ks.cfg

Re: [qmailtoaster] QMTISO, Kickstart, drivers and updates

2007-10-24 Thread Erik A. Espinoza
[mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 1:02 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] QMTISO, Kickstart, drivers and updates Aaron Spurlock wrote: Okay, now this doesn't make sense to me...I took a generic CentOS4.4 ServerCD and put

RE: [qmailtoaster] QMTISO, Kickstart, drivers and updates

2007-10-24 Thread Aaron Spurlock
-list@qmailtoaster.com Subject: Re: [qmailtoaster] QMTISO, Kickstart, drivers and updates This: Usually this manifests itself in eth0 during install becoming eth1 and vice versa. Should read: Usually this manifests itself in eth0 during install becoming eth1 after the first boot and vice versa

Re: [qmailtoaster] QMTISO, Kickstart, drivers and updates

2007-10-24 Thread Jake Vickers
2:30 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] QMTISO, Kickstart, drivers and updates This: Usually this manifests itself in eth0 during install becoming eth1 and vice versa. Should read: Usually this manifests itself in eth0 during install becoming eth1 after the first