search for: moddeps

--- helper/init.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/helper/init.c b/helper/init.c index 0ca3135..2b5dacf 100644 --- a/helper/init.c +++ b/helper/init.c @@ -163,8 +163,10 @@ main () chdir ("/"); - /* Run /init from ext2 filesystem. */ + mount_proc (); print_uptime (); + + /* Run /init from ext2 filesystem. */ execl

I don't understand what this means, I found it in root's email this morning: To log into the recovery system via ssh set up /root/.ssh/authorized_keys or specify SSH_ROOT_PASSWORD WARNING: /usr/lib/grub/x86_64-efi/moddep.lst not found, grub2-mkimage will likely fail. Please install the grub2-efi-x64-modules package to fix this. ERROR: Error occurred during grub2-mkimage of BOOTX64.efi

Hi all, Recently, after doing some maintenance on one of my servers (Centos 5), I rebooted. On reboot, it didn't find the SAN disks at all, and after some poking around in maintenance mode, I discovered that it couldn't find the Qlogic module. It turns out that /lib/modules/<kernel-version>/modules.alias, modules.dep and such were all empty or just had their header comment lines.

...*.ko*"; +] + +let rec build_initrd debug tmpdir modpath initrd = + if debug >= 1 then + printf "supermin: ext2: creating minimal initrd '%s'\n%!" initrd; + + let initdir = tmpdir // "init.d" in + mkdir initdir 0o755; + + (* Read modules.dep file. *) + let moddeps = read_module_deps modpath in + + (* Create a set of top-level modules, that is any module which + * matches a pattern in kmods. + *) + let topset = + let mods = keys moddeps in + List.fold_left ( + fun topset modl -> + let m = Filename.basename modl in + let match...

On 2016.03.06 23:25, Shao Miller via Syslinux wrote: > Having typed that, perhaps we could discuss your (or Rufus') specific > needs, in parallel? I think that is probably worthwhile, as I wouldn't mind having a second opinion from Syslinux developers on whether my current ISO -> USB conversion process could be improved. > Do I understand correctly that the primary >

On 3/3/2016 07:43, Pete Batard via Syslinux wrote: > [...] as far as I am concerned, 'A "version" such as "6.03" [is not] > enough'. [...] I'd like to help to improve Syslinux with regards to version-related concerns. Having typed that, perhaps we could discuss your (or Rufus') specific needs, in parallel? Do I understand correctly that the primary