Hi Jeremy,
Jeremy Katz wrote:
(dropping lkml again)
On Thu, 2008-12-18 at 08:36 +0100, Hannes Reinecke wrote:
We definitely should get together to hammer our one implementation.
Having different scripts for every distributions is a PITA.
Indeed -- but as davej noticed, going with one
Hi all,
Bernhard Walle wrote:
* Seewer Philippe [2008-12-19 08:41]:
Hannes Reinecke wrote:
[snip]
If anyone is interested I can give a short overview of it.
Please do so, would be appreciated.
A good start is the manual page in section 5:
http://git.opensuse.org/?p=projects/mkinitrd.git;a
ndividual packages / vendors.
And then we would have a small common initramfs which well could be included
with the kernel sources.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
h...@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfe
Hi Jeremy,
Jeremy Katz wrote:
On Dec 19, 2008, at 3:21 AM, Hannes Reinecke wrote:
Jeremy Katz wrote:
(dropping lkml again)
On Thu, 2008-12-18 at 08:36 +0100, Hannes Reinecke wrote:
By instead moving to where we're basing everything off of uevents we can
hopefully move away from the ma
not. So you basically have to write
some device-specific udev rules for enabling multipath on some
devices.
The hard part here is to remove the component device from the list
of eligible devices so that eg LVM doesn't erroneously tries to
scan from a multipath or dmraid component device.
Ch
m there. However, you're still facing the problem that you'd
might want to run 'fsck' on the root device. And you might want to
know when 'mount' has actually finished, as only then you can execute
'init'. Sadly the 'mount' events
error condition).
The only safe way here is to send a ping to the host port we're
trying to connect to, and limit this with a timeout.
And start up the command once the ping succeeds.
Otherwise timeout and start error recovery.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries
appear. Even the udev queue check is pointless here; either
we have a device node, in which case we can continue regardless
of how many events are still in the udev queue;
or we don't have one, in which case it quite irrelevant if
udev has still events to process or not.
Think of multipath taking
tput - which means that on machines not running Xen it would still jump
> in the
> "then" clause.
>
> I think I am going to modify the xen-detect to accept another flag that would
> just print a string if it is running in a PV context and nothing else- that
> should make
On 02/13/2012 10:59 AM, Harald Hoyer wrote:
> Am 10.02.2012 16:01, schrieb Mimi Zohar:
>> Hi Harald,
>>
[ .. ]
Ohh, can you _order_ dracut modules now?
Harald, that'll be four modules for me, please :-)
Sorry, I just _had_ to go for that cheap pun.
Cheers,
Hannes
--
Move kernel module selection to 95dasd_mod and make 95dasd depend
on that module.
Signed-off-by: Hannes Reinecke
---
modules.d/95dasd/module-setup.sh | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/modules.d/95dasd/module-setup.sh b/modules.d/95dasd/module-setup.sh
normalize_dasd_arg is a RedHat specific script, so no point
installing this module if the script isn't present.
Signed-off-by: Hannes Reinecke
---
modules.d/95dasd/module-setup.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/modules.d/95dasd/module-setup.sh b/modules.d/95dasd/m
apply.
Hannes Reinecke (10):
95dasd: Install kernel modules only once
95dasd: Only install module if normalize_dasd_arg is present
95dasd_mod: make dasd_cio_free optional
95zfcp: Make installation optional
95znet: Make installation optional
Install /bin/mount
Fixup keymap setting for ope
On SuSE the DASD configuration is kept in udev rules, one rule
file per device. So add a new module for copying and creating
these rules during boot.
Signed-off-by: Hannes Reinecke
---
dracut-functions.sh| 28 +
modules.d/95dasd_rules/module-setup.sh | 27
SUSE installs plymount files in /usr/lib, not /usr/libexec.
So check for both when including plymouth support.
Signed-off-by: Hannes Reinecke
---
modules.d/50plymouth/module-setup.sh | 17 -
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/modules.d/50plymouth
systemd relies on /bin/mount to be present, so install it.
Signed-off-by: Hannes Reinecke
---
modules.d/99fs-lib/module-setup.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/modules.d/99fs-lib/module-setup.sh
b/modules.d/99fs-lib/module-setup.sh
index 7979bab..b24207d 100755
--- a
znet_cio_free is a RedHat-specific tool, so do not install this
module on systems where the program is missing.
Signed-off-by: Hannes Reinecke
---
modules.d/95znet/module-setup.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/modules.d/95znet/module-setup.sh b/modules.d/95znet/module
SuSE is storing the zfcp configuration in udev files, so we should
be including these.
Signed-off-by: Hannes Reinecke
---
modules.d/95zfcp_rules/module-setup.sh | 25
modules.d/95zfcp_rules/parse-zfcp.sh | 54 ++
2 files changed, 79 insertions
openSUSE is using compressed keymaps.
Signed-off-by: Hannes Reinecke
---
modules.d/10i18n/module-setup.sh | 3 +++
1 file changed, 3 insertions(+)
diff --git a/modules.d/10i18n/module-setup.sh b/modules.d/10i18n/module-setup.sh
index 0741c64..f07b148 100755
--- a/modules.d/10i18n/module
zfcp_cio_free is a RedHat-specific tool, so do not install this
module if the program isn't present.
Signed-off-by: Hannes Reinecke
---
modules.d/95zfcp/module-setup.sh | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/modules.d/95zfcp/module-setup.sh b/modules.d/9
dasd_cio_free is a RedHat-specific tool, so make it optional.
Signed-off-by: Hannes Reinecke
---
dracut-functions.sh| 9 +
modules.d/95dasd_mod/module-setup.sh | 3 ++-
modules.d/95dasd_mod/parse-dasd-mod.sh | 4 +++-
3 files changed, 14 insertions(+), 2 deletions
On 11/28/2013 01:51 PM, Harald Hoyer wrote:
> On 11/27/2013 04:44 PM, Hannes Reinecke wrote:
>> dasd_cio_free is a RedHat-specific tool, so make it optional.
>>
>> Signed-off-by: Hannes Reinecke
>> ---
>> dracut-functions.sh| 9
On 11/27/2013 04:44 PM, Hannes Reinecke wrote:
> systemd relies on /bin/mount to be present, so install it.
>
> Signed-off-by: Hannes Reinecke
> ---
> modules.d/99fs-lib/module-setup.sh | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/modules.d/99fs-lib/module
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
--
Dr. Hannes Reinecke zSeries & Storage
h...@suse.de
Move kernel module selection to 95dasd_mod and make 95dasd depend
on that module.
Signed-off-by: Hannes Reinecke
---
modules.d/95dasd/module-setup.sh | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/modules.d/95dasd/module-setup.sh b/modules.d/95dasd/module-setup.sh
dded a new SUSE-specific mkinitrd compability script,
as the SUSE mkinitrd is quite different.
And some minor fixes which came up during package build.
Please apply.
Hannes Reinecke (13):
95dasd: Install kernel modules only once
95dasd: Only install module if normalize_dasd_arg is present
dasd_cio_free is a RedHat-specific tool, so make it optional.
Signed-off-by: Hannes Reinecke
---
modules.d/95dasd_mod/module-setup.sh | 3 ++-
modules.d/95dasd_mod/parse-dasd-mod.sh | 4 +++-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/modules.d/95dasd_mod/module-setup.sh
normalize_dasd_arg is a RedHat specific script, so no point
installing this module if the script isn't present.
Signed-off-by: Hannes Reinecke
---
modules.d/95dasd/module-setup.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/modules.d/95dasd/module-setup.sh b/modules.d/95dasd/m
zfcp_cio_free is a RedHat-specific tool, so do not install this
module if the program isn't present.
Signed-off-by: Hannes Reinecke
---
modules.d/95zfcp/module-setup.sh | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/modules.d/95zfcp/module-setup.sh b/modules.d/9
Add '--logfile' option to make the log file configurable during
runtime.
Signed-off-by: Hannes Reinecke
---
dracut.8.asc | 6 ++
dracut.sh| 4
2 files changed, 10 insertions(+)
diff --git a/dracut.8.asc b/dracut.8.asc
index 2ea6744..d381dcf 100644
--- a/dracut.8.asc
+++
On SuSE the DASD configuration is kept in udev rules, one rule
file per device. So add a new module for copying and creating
these rules during boot.
Signed-off-by: Hannes Reinecke
---
dracut-functions.sh| 28 +
modules.d/95dasd_rules/module-setup.sh | 27
Signed-off-by: Hannes Reinecke
---
Makefile| 1 +
mkinitrd-suse.8.asc | 106
2 files changed, 107 insertions(+)
create mode 100644 mkinitrd-suse.8.asc
diff --git a/Makefile b/Makefile
index e7da948..ba551cf 100644
--- a
Scripts with a shebang should be marked as executable.
Signed-off-by: Hannes Reinecke
---
modules.d/03modsign/load-modsign-keys.sh | 0
modules.d/03modsign/module-setup.sh | 0
modules.d/40network/net-lib.sh | 0
modules.d/40network/parse-vlan.sh| 0
modules.d/50drm
SUSE has its own mkinitrd system. As the arguments clash
with the dracut-provided mkinitrd script I've added a new
mkinitrd-suse.sh wrapper.
Signed-off-by: Hannes Reinecke
---
mkinitrd-suse.sh | 354 +++
1 file changed, 354 inser
znet_cio_free is a RedHat-specific tool, so do not install this
module on systems where the program is missing.
Signed-off-by: Hannes Reinecke
---
modules.d/95znet/module-setup.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/modules.d/95znet/module-setup.sh b/modules.d/95znet/module
Shell-completion files are meant to be sourced, not executed.
So they shouldn't have a shebang at the start.
Signed-off-by: Hannes Reinecke
---
dracut-bash-completion.sh | 2 +-
lsinitrd-bash-completion.sh | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/dracut
openSUSE is using compressed keymaps.
Signed-off-by: Hannes Reinecke
---
modules.d/10i18n/module-setup.sh | 3 +++
1 file changed, 3 insertions(+)
diff --git a/modules.d/10i18n/module-setup.sh b/modules.d/10i18n/module-setup.sh
index 0741c64..f07b148 100755
--- a/modules.d/10i18n/module
SuSE is storing the zfcp configuration in udev files, so we should
be including these.
Signed-off-by: Hannes Reinecke
---
modules.d/95zfcp_rules/module-setup.sh | 25 +
modules.d/95zfcp_rules/parse-zfcp.sh | 65 ++
2 files changed, 90 insertions
ed' will return '0', causing the main initqueue to
short-circuit and the actual initqueue jobs will never be executed.
Is this the intended outcome?
IE are all jobs for the initqueue are _required_ to supply a
'finished' job?
I would have thought it
On 05/13/2014 11:48 AM, Harald Hoyer wrote:
On 13.05.2014 11:44, Hannes Reinecke wrote:
Hi all,
I'm trying to figure out why my initqueue scripts are never called.
Eg 95fcoe is just installing an initqueue job, which should call
'fcoe-up' on the interface.
However, this script
On 05/13/2014 12:22 PM, Harald Hoyer wrote:
On 13.05.2014 11:55, Hannes Reinecke wrote:
[ .. ]
Ah. So fcoe never worked?
(As it doesn't supply an 'finished' script)
Cheers,
Hannes
What do you mean? Normally there are "finished" scripts installed, which wait
for
On 05/13/2014 12:39 PM, Harald Hoyer wrote:
On 13.05.2014 12:30, Hannes Reinecke wrote:
On 05/13/2014 12:22 PM, Harald Hoyer wrote:
On 13.05.2014 11:55, Hannes Reinecke wrote:
[ .. ]
Ah. So fcoe never worked?
(As it doesn't supply an 'finished' script)
Cheers,
Hannes
W
On 05/13/2014 02:10 PM, Harald Hoyer wrote:
On 13.05.2014 12:42, Hannes Reinecke wrote:
On 05/13/2014 12:39 PM, Harald Hoyer wrote:
On 13.05.2014 12:30, Hannes Reinecke wrote:
On 05/13/2014 12:22 PM, Harald Hoyer wrote:
On 13.05.2014 11:55, Hannes Reinecke wrote:
[ .. ]
Ah. So fcoe never
On 05/13/2014 04:32 PM, Harald Hoyer wrote:
On 13.05.2014 16:21, Hannes Reinecke wrote:
On 05/13/2014 02:10 PM, Harald Hoyer wrote:
On 13.05.2014 12:42, Hannes Reinecke wrote:
On 05/13/2014 12:39 PM, Harald Hoyer wrote:
for systemd:
modules.d/98systemd/rootfs-generator.sh:
[ "$
On 05/20/2014 10:46 AM, Hannes Reinecke wrote:
On 05/13/2014 04:32 PM, Harald Hoyer wrote:
On 13.05.2014 16:21, Hannes Reinecke wrote:
On 05/13/2014 02:10 PM, Harald Hoyer wrote:
On 13.05.2014 12:42, Hannes Reinecke wrote:
On 05/13/2014 12:39 PM, Harald Hoyer wrote:
for systemd
The rootfs-generator was installed in the wrong path
in the initrd, cause it never to be run.
References: bnc#878714
Signed-off-by: Hannes Reinecke
---
modules.d/98systemd/module-setup.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/modules.d/98systemd/module-setup.sh
b
e 'ip=ibft' setting does look a bit odd.
And confuses the logic ...
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
h...@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörf
On 06/04/2014 01:50 PM, Harald Hoyer wrote:
On 04.06.2014 09:52, Hannes Reinecke wrote:
Hi all,
I'm trying to setup a machine with root on iSCSI via iBFT
(on SR-IOV, yay!).
But anyhow, I'll be setting 'ip=ibft' on the commandline as per documentation
and the iBFT sett
of those calls will generate a SIGABRT.
Nasty.
Best would be to pull libgcc_s in always when libpthread is
required. But that would be some library detection magic.
Can you fix this up?
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
h...@suse.de
them posted.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
h...@suse.de +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)
--
To unsubscribe from this list:
On 08/19/2014 04:00 PM, Harald Hoyer wrote:
On 22.07.2014 15:45, Hannes Reinecke wrote:
On 07/22/2014 03:41 PM, Harald Hoyer wrote:
Anything missing? Wishes? Bugs?
Well, apart from roughly 150 patches queued for SLES ...
(cf github.com:/hreinecke/dracut.git branch sles12)
Sadly I haven&#
On 11/21/2014 06:43 AM, WANG Chao wrote:
> Hi,
>
> On 11/20/14 at 03:56pm, Thomas Renninger wrote:
>> From: Hannes Reinecke
>>
>> Some iSCSI initiator present firmware information in
>> /sys/firmware/ibft or /sys/firmware/iscsi_bootX
>>
>> Whenever
On 12/12/2014 04:02 AM, Baoquan He wrote:
> On 12/11/14 at 03:46pm, Thomas Renninger wrote:
>> From: Hannes Reinecke
>>
>> When running with --hostonly-cmdline we should be storing
>> the current configuration in /etc/cmdline.d so that dracut
>> will be c
*
> Stored kernel commandline:
> root=UUID=d5e53483-30bc-4119-8c0c-841d47a2f76brootflags=rw,noatime,compress=lzo,ssd,discard,space_cache,autodefrag,inode_cacherootfstype=btrfs
> …
>
Any specific reason for this?
Errors, failures?
Cheers,
Hannes
--
Dr. Hannes Rei
On 07/07/2015 01:41 PM, Harald Hoyer wrote:
> On 29.06.2015 19:36, Thomas Renninger wrote:
>> From: Hannes Reinecke
>>
>> https://bugzilla.opensuse.org/show_bug.cgi?id=905746
>>
>> Version 2: Remove 64-md-raid.rules
>>
>> Signed-off-by: Thomas Renni
On 11/13/2015 12:00 PM, Harald Hoyer wrote:
> On 07.07.2015 13:54, Hannes Reinecke wrote:
>> On 07/07/2015 01:41 PM, Harald Hoyer wrote:
>>> On 29.06.2015 19:36, Thomas Renninger wrote:
>>>> From: Hannes Reinecke
>>>>
>>>> https://bugzilla.o
56 matches
Mail list logo
