SUSE mkinitrd wrapper

DISCUSSION Hannes Reinecke 2 participants 2 messages Nov 28, 2013 1 message not in the archive

Share & tools

Hannes Reinecke

author

2013-11-28 13:36 UTC #0 lore raw

Hi Harald,

I've updated the current 'mkinitrd-dracut.sh' script to function as a wrapper to the old SUSE mkinitrd script.
However, as some arguments clash between SUSE mkinitrd and mkinitrd-dracut.sh I've put them into a separate script, mkinitrd-suse.sh.

What do you prefer? Having two separate scripts?
As I'm not sure if anybody is actually using the 'mkinitrd-dracut.sh' script I could as well merge the changes into that one.

Just tell me what you prefer.

Cheers,

Hannes

Signature · 4 lines

Dr. Hannes Reinecke		      zSeries & Storage
[email protected]			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

Harald Hoyer

2013-11-28 14:05 UTC #2 lore raw

In reply to a message not in the archive

Quoted 13 lines · Hannes Reinecke

Hi Harald,
I've updated the current 'mkinitrd-dracut.sh' script to function as a wrapper to the old SUSE mkinitrd script.
However, as some arguments clash between SUSE mkinitrd and mkinitrd-dracut.sh I've put them into a separate script, mkinitrd-suse.sh.
What do you prefer? Having two separate scripts?
As I'm not sure if anybody is actually using the 'mkinitrd-dracut.sh' script I could as well merge the changes into that one.

Quoted 6 lines

Just tell me what you prefer.
Cheers,
Hannes

Hmm, I think "mkinitrd" is still used by some scripts. Not sure. Can it be merged and switch behavior depending on the $ID in /etc/os-release ?