Displaying 6 results from an estimated 6 matches for "moddep".
Did you mean:
modded
2011 Jun 04
3
[PATCH 1/3] febootstrap/helper/init: make sure /proc is mounted into chroot.
---
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
2020 Oct 07
1
strange email from cron regarding "rear"
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
Aborting due to an error, check /var/log/rear/rear-fcshome.log for details
/bin/sh: line 1: 30339 Terminated /usr/sbin/...
2008 Apr 21
0
Odd behaviour with modules; looking for some theories
...t, 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. moddep -a fixed
things up quickly enough once I figured out what was going on.
However, I'm kinda stumped as to how these files got nuked in the first
place. It wasn't files being deleted completely, it's like they were
regenerated incorrectly. Checking backups showed these files were last...
2014 Feb 25
2
[PATCH supermin v4] Supermin 5 rewrite.
...o*",
- "ata_piix.ko*",
- "sr_mod.ko*",
- "mbcache.ko*",
- "crc*.ko*",
- "libcrc*.ko*",
- "ibmvscsic.ko*",
- "megaraid*.ko*",
- NULL
-};
-
-/* Module dependencies. */
-struct module {
- struct module *next;
- struct moddep *deps;
- char *name;
- int visited;
-};
-struct module *modules = NULL;
-
-struct moddep {
- struct moddep *next;
- struct module *dep;
-};
-
-void
-ext2_make_initrd (const char *modpath, const char *initrd)
-{
- char dir[] = "/tmp/ext2initrdXXXXXX";
- if (mkdtemp (dir) == NULL)
-...
2016 Mar 07
0
Module Versioning
...efi\minix2_be.mod (3.8 KB)
Extracting: F:\EFI\BOOT\grub\i386-efi\minix3.mod (3.6 KB)
Extracting: F:\EFI\BOOT\grub\i386-efi\minix3_be.mod (3.7 KB)
Extracting: F:\EFI\BOOT\grub\i386-efi\minix_be.mod (3.6 KB)
Extracting: F:\EFI\BOOT\grub\i386-efi\mmap.mod (6.7 KB)
Extracting: F:\EFI\BOOT\grub\i386-efi\moddep.lst (4.7 KB)
Extracting: F:\EFI\BOOT\grub\i386-efi\morse.mod (2.4 KB)
Extracting: F:\EFI\BOOT\grub\i386-efi\mpi.mod (28.6 KB)
Extracting: F:\EFI\BOOT\grub\i386-efi\msdospart.mod (2.5 KB)
Extracting: F:\EFI\BOOT\grub\i386-efi\multiboot.mod (12 KB)
Extracting: F:\EFI\BOOT\grub\i386-efi\multiboot2.mod...
2016 Mar 06
5
Module Versioning
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