A good many of our systems work only via serial console. I would like ot have the buildiso to have the option of booting serial, but not sure if there is enough need to add that to the code or just hack the iso myself after its built.
Stephen John Smoogen wrote:
A good many of our systems work only via serial console. I would like ot have the buildiso to have the option of booting serial, but not sure if there is enough need to add that to the code or just hack the iso myself after its built.
Adding a flag to append kernel options to every profile/system on the ISO seems fine to me, is that what you were thinking?
--Michael
On Tue, Nov 25, 2008 at 10:37 AM, Michael DeHaan mdehaan@redhat.com wrote:
Stephen John Smoogen wrote:
A good many of our systems work only via serial console. I would like ot have the buildiso to have the option of booting serial, but not sure if there is enough need to add that to the code or just hack the iso myself after its built.
Adding a flag to append kernel options to every profile/system on the ISO seems fine to me, is that what you were thinking?
I was thinking about that... but having serial for certain systems makes them break. So I am wondering what the correct workflow would be.
Import RHEL-3, RHEL-4, RHEL-5 [x86_32, x86_64] Create profile for serial for RHEL-3,RHEL-4,RHEL-5 Link serial systems to that profile Build bootiso to that profile?
Sorry if this is obvious...
-ENOCAFFEINE
Stephen John Smoogen wrote:
On Tue, Nov 25, 2008 at 10:37 AM, Michael DeHaan mdehaan@redhat.com wrote:
Stephen John Smoogen wrote:
A good many of our systems work only via serial console. I would like ot have the buildiso to have the option of booting serial, but not sure if there is enough need to add that to the code or just hack the iso myself after its built.
Adding a flag to append kernel options to every profile/system on the ISO seems fine to me, is that what you were thinking?
I was thinking about that... but having serial for certain systems makes them break. So I am wondering what the correct workflow would be.
Import RHEL-3, RHEL-4, RHEL-5 [x86_32, x86_64] Create profile for serial for RHEL-3,RHEL-4,RHEL-5 Link serial systems to that profile Build bootiso to that profile?
Sorry if this is obvious...
-ENOCAFFEINE
You're saying each system needs it's own parameters, right?
It seems to imply having a "--extra-kopts-for-buildiso" at some level, which feels a bit kludgy.
Anyone else have thoughts?
--Michael
On Tue, Nov 25, 2008 at 11:56 AM, Michael DeHaan mdehaan@redhat.com wrote:
Stephen John Smoogen wrote:
On Tue, Nov 25, 2008 at 10:37 AM, Michael DeHaan mdehaan@redhat.com wrote:
Stephen John Smoogen wrote:
A good many of our systems work only via serial console. I would like ot have the buildiso to have the option of booting serial, but not sure if there is enough need to add that to the code or just hack the iso myself after its built.
Adding a flag to append kernel options to every profile/system on the ISO seems fine to me, is that what you were thinking?
I was thinking about that... but having serial for certain systems makes them break. So I am wondering what the correct workflow would be.
Import RHEL-3, RHEL-4, RHEL-5 [x86_32, x86_64] Create profile for serial for RHEL-3,RHEL-4,RHEL-5 Link serial systems to that profile Build bootiso to that profile?
Sorry if this is obvious...
-ENOCAFFEINE
You're saying each system needs it's own parameters, right?
Not really. We have ~10 machines with serial only, ~40 serial and console, and 70 systems that have no serial. I figure I would need 2-3 buildiso's each aimed at a different environment
It seems to imply having a "--extra-kopts-for-buildiso" at some level, which feels a bit kludgy.
Anyone else have thoughts?
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Stephen John Smoogen wrote:
On Tue, Nov 25, 2008 at 11:56 AM, Michael DeHaan mdehaan@redhat.com wrote:
Stephen John Smoogen wrote:
On Tue, Nov 25, 2008 at 10:37 AM, Michael DeHaan mdehaan@redhat.com wrote:
Stephen John Smoogen wrote:
A good many of our systems work only via serial console. I would like ot have the buildiso to have the option of booting serial, but not sure if there is enough need to add that to the code or just hack the iso myself after its built.
Adding a flag to append kernel options to every profile/system on the ISO seems fine to me, is that what you were thinking?
I was thinking about that... but having serial for certain systems makes them break. So I am wondering what the correct workflow would be.
Import RHEL-3, RHEL-4, RHEL-5 [x86_32, x86_64] Create profile for serial for RHEL-3,RHEL-4,RHEL-5 Link serial systems to that profile Build bootiso to that profile?
Sorry if this is obvious...
-ENOCAFFEINE
You're saying each system needs it's own parameters, right?
Not really. We have ~10 machines with serial only, ~40 serial and console, and 70 systems that have no serial. I figure I would need 2-3 buildiso's each aimed at a different environment
It seems to imply having a "--extra-kopts-for-buildiso" at some level, which feels a bit kludgy.
Anyone else have thoughts?
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Ok, maybe this would help me understand better.
Can you give me an example of what changes you would have to make (specifically) to the config file buildiso uses (or the --kopts) to make your configuration work?
Maybe then some idea will jump out at me. I'm not sure if you just need a kernel argument applied to certain systems or the kernel argument changes in different ways between profiles/systems/etc for your serial console setup.
--Michael
On Tue, Nov 25, 2008 at 12:03 PM, Michael DeHaan mdehaan@redhat.com wrote:
Stephen John Smoogen wrote:
On Tue, Nov 25, 2008 at 11:56 AM, Michael DeHaan mdehaan@redhat.com wrote:
Stephen John Smoogen wrote:
On Tue, Nov 25, 2008 at 10:37 AM, Michael DeHaan mdehaan@redhat.com wrote:
Stephen John Smoogen wrote:
A good many of our systems work only via serial console. I would like ot have the buildiso to have the option of booting serial, but not sure if there is enough need to add that to the code or just hack the iso myself after its built.
Adding a flag to append kernel options to every profile/system on the ISO seems fine to me, is that what you were thinking?
I was thinking about that... but having serial for certain systems makes them break. So I am wondering what the correct workflow would be.
Import RHEL-3, RHEL-4, RHEL-5 [x86_32, x86_64] Create profile for serial for RHEL-3,RHEL-4,RHEL-5 Link serial systems to that profile Build bootiso to that profile?
Sorry if this is obvious...
-ENOCAFFEINE
You're saying each system needs it's own parameters, right?
Not really. We have ~10 machines with serial only, ~40 serial and console, and 70 systems that have no serial. I figure I would need 2-3 buildiso's each aimed at a different environment
It seems to imply having a "--extra-kopts-for-buildiso" at some level, which feels a bit kludgy.
Anyone else have thoughts?
--Michael
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Ok, maybe this would help me understand better.
Can you give me an example of what changes you would have to make (specifically) to the config file buildiso uses (or the --kopts) to make your configuration work?
Basically the only change is the following to the kernel line for boxes with serial consoles:
console=tty0 console=ttyS0,115200 text serial
for boxes without serial consoles.. don't add it as it uhm.. makes booting/installation hard :).
cobbler@lists.fedorahosted.org