search for: romf

...================================== --- klibc.orig/usr/kinit/fstype/fstype.c 2006-02-05 11:09:31.000000000 +0100 +++ klibc/usr/kinit/fstype/fstype.c 2006-02-05 11:11:15.000000000 +0100 @@ -7,7 +7,7 @@ * FSSIZE - filesystem size (if known) * * We currently detect (in order): - * gzip, cramfs, romfs, xfs, luks, minix, ext3, ext2, reiserfs, jfs + * gzip, cramfs, romfs, xfs, luks, minix, ext3, ext2, reiserfs, jfs, swap * * MINIX, ext3 and Reiserfs bits are currently untested. */ @@ -20,6 +20,7 @@ #include <endian.h> #include <netinet/in.h> #include <sys/vfs.h> +#incl...

...================================== --- klibc.orig/usr/kinit/fstype/fstype.c 2006-02-05 10:53:51.000000000 +0100 +++ klibc/usr/kinit/fstype/fstype.c 2006-02-05 11:09:31.000000000 +0100 @@ -7,7 +7,7 @@ * FSSIZE - filesystem size (if known) * * We currently detect (in order): - * gzip, cramfs, romfs, xfs, minix, ext3, ext2, reiserfs, jfs + * gzip, cramfs, romfs, xfs, luks, minix, ext3, ext2, reiserfs, jfs * * MINIX, ext3 and Reiserfs bits are currently untested. */ @@ -29,6 +29,7 @@ #include "ext2_fs.h" #include "ext3_fs.h" #include "xfs_sb.h" +#include...

....c klibc/usr/kinit/fstype/fstype.c --- klibc-orig/usr/kinit/fstype/fstype.c 2006-03-22 21:28:31.000000000 +0100 +++ klibc/usr/kinit/fstype/fstype.c 2006-03-23 00:54:57.000000000 +0100 @@ -7,7 +7,7 @@ * FSSIZE - filesystem size (if known) * * We currently detect (in order): - * gzip, cramfs, romfs, xfs, luks, minix, ext3, ext2, reiserfs, jfs, swap + * gzip, cramfs, romfs, xfs, luks, lvm2, minix, ext3, ext2, reiserfs, jfs, swap * * MINIX, ext3 and Reiserfs bits are currently untested. */ @@ -30,6 +30,7 @@ #include "ext3_fs.h" #include "xfs_sb.h" #include "l...

...ot=/dev/ram0 6) excuted "cat mbr.bin > /dev/sda" 7) copied initrd.img and vmlinuz to /mnt/flash 8) umounted /mnt/flash I know it sounds strange but I wanted to do the same with isolinux, but get the following error: . . . . 16384 ram181(driver?) No filesystem could mount root, tried: romfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) Any ideas how might get this to work?

...git a/usr/kinit/fstype/fstype.c b/usr/kinit/fstype/fstype.c index c892c6b..17a89ce 100644 --- a/usr/kinit/fstype/fstype.c +++ b/usr/kinit/fstype/fstype.c @@ -6,8 +6,8 @@ * FSTYPE - filesystem type * FSSIZE - filesystem size (if known) * - * We currently detect (in order): - * gzip, cramfs, romfs, xfs, luks, lvm2, minix, ext3, ext2, reiserfs, jfs, swap + * We currently detect the filesystems listed below in the struct + * "imagetype images" (in the order they are listed). * * MINIX, ext3 and Reiserfs bits are currently untested. */ @@ -231,8 +231,13 @@ struct imagetype {...

...istered protocol family 1 NET: Registered protocol family 17 IP-Config: Guessing netmask 255.0.0.0 IP-Config: Complete: device=eth0, addr=1.2.3.4, mask=255.0.0.0, gw=255.255.255.255, host=1.2.3.4, domain=, nis-domain=(none), bootserver=1.2.3.4, rootserver=1.2.3.4, rootpath= RAMDISK: romfs filesystem found at block 0 RAMDISK: Loading 2214KiB [1 disk] into ram disk... done. VFS: Mounted root (romfs filesystem) readonly. + insmod /lib/modules/2.6.12.3-0.2/kernel/drivers/scsi/scsi_mod.ko Using /lib/modules/2.6.12.3-0.2/kernel/drivers/scsi/scsi_mod.ko SCSI subsystem initialized + insmod...

...ude <stdio.h> +#include <ctype.h> #include <string.h> #include <unistd.h> #include <fcntl.h> #include <endian.h> #include <netinet/in.h> +#include <sys/utsname.h> #include <sys/vfs.h> #define cpu_to_be32(x) __cpu_to_be32(x) /* Needed by romfs_fs.h */ @@ -110,29 +112,142 @@ static int minix_image(const void *buf, unsigned long long *bytes) return 0; } -static int ext4_image(const void *buf, unsigned long long *bytes) +/* + * Check to see if a filesystem is in /proc/filesystems. + * Returns 1 if found, 0 if not + */ +static int fs_p...

...t API vfs: Convert qib_fs/ipathfs to use the new mount API vfs: Convert ibmasmfs to use the new mount API vfs: Convert oprofilefs to use the new mount API vfs: Convert gadgetfs to use the new mount API vfs: Convert xenfs to use the new mount API vfs: Convert openpromfs to use the new mount API vfs: Convert apparmorfs to use the new mount API vfs: Convert securityfs to use the new mount API vfs: Convert selinuxfs to use the new mount API vfs: Convert smackfs to use the new mount API vfs: Convert ramfs, shmem, tmpfs, devtmpfs, rootfs...

...ssed at some point: 1. how do we get kernel command line parameters into initramfs? my favoured option is to remove the ones we care about from the kernel, they will then appear in the environment for the init script 2. load_ramdisk currently does not perform any detection of gzip vs romfs vs ext2 vs minix. If this feature is required, we may have to look at file(1). I've already looked at file(1) around klibc 0.17 time, and it wasn't anywhere clean enough for klibc. 3. do we need to worry about initrd support? initrd has this nasty habbit of wanting to change t...

With the recent kernel patch viro@www.linux.org.uk[torvalds]|include/linux/ romfs_fs.h|20041006145144|23705 aka "romfs endianness annotations" utils/fstype.c no longer links because cpu_to_be32 is undefined. Options: 1) Change the header to be ok for userspace diff -ur ../linux-2.5/include/linux/romfs_fs.h linux/include/linux/romfs_fs.h --- ../linux-2.5/include...

...it's possible * that an old lvm signature is left on the disk if pvremove * is not used before creating the new fs. + * + * The same goes for LUKS as for LVM. */ static struct imagetype images[] = { {0, "gzip", gzip_image}, {0, "cramfs", cramfs_image}, {0, "romfs", romfs_image}, {0, "xfs", xfs_image}, - {0, "luks", luks_image}, {1, "ext3", ext3_image}, {1, "ext2", ext2_image}, {1, "minix", minix_image}, {8, "reiserfs", reiserfs_image}, {64, "reiserfs", reiserfs_image},...

...ods="fs/9p fs/affs fs/autofs fs/autofs4 fs/befs fs/bfs fs/cifs \ fs/coda fs/cramfs fs/dlm fs/ecryptfs fs/efs fs/exportfs fs/ext4 \ fs/freevxfs fs/fuse fs/gfs2 fs/hfs fs/hfsplus fs/jbd2 fs/jffs \ fs/jffs2 fs/jfs fs/minix fs/ncpfs fs/ocfs2 fs/qnx4 fs/reiserfs \ fs/romfs fs/sysv fs/udf fs/ufs fs/xfs" +nls_mods="fs/nls/nls_cp* fs/nls/nls_iso* fs/nls/nls_ko* fs/nls/nls_euc*" + net_mods="net/9p net/appletalk net/atm net/ax25 \ net/bluetooth net/dccp net/decnet net/ieee80211 net/ipx net/irda \ net/mac80211 net/netrom net/rfkill n...

...or_modules("ext4")); - if ((!test_fs || !ext4dev_present) && ext4_present) - return 0; - return 1; -} - static int ext3_image(const void *buf, unsigned long long *bytes) { const struct ext3_super_block *sb = @@ -496,7 +383,6 @@ static struct imagetype images[] = { {0, "romfs", romfs_image}, {0, "xfs", xfs_image}, {0, "squashfs", squashfs_image}, - {1, "ext4dev", ext4dev_image}, {1, "ext4", ext4_image}, {1, "ext3", ext3_image}, {1, "ext2", ext2_image},

...pu(sb->s_blocks_count) + << (10 + __le32_to_cpu(sb->s_log_block_size)); + return 1; + } + return 0; +} + static int ext3_image(const void *buf, unsigned long long *bytes) { const struct ext3_super_block *sb = @@ -302,6 +321,7 @@ static struct imagetype images[] = { {0, "romfs", romfs_image}, {0, "xfs", xfs_image}, {0, "squashfs", squashfs_image}, + {1, "ext4dev", ext4_image}, {1, "ext3", ext3_image}, {1, "ext2", ext2_image}, {1, "minix", minix_image}, commit bdd1ca2344edd06c873980c7023b8be006ab...

...to new ctime accessors nfs: switch to new ctime accessors nfsd: switch to new ctime accessors nilfs2: switch to new ctime accessors ntfs: switch to new ctime accessors ntfs3: switch to new ctime accessors ocfs2: switch to new ctime accessors omfs: switch to new ctime accessors openpromfs: switch to new ctime accessors orangefs: switch to new ctime accessors overlayfs: switch to new ctime accessors proc: switch to new ctime accessors pstore: switch to new ctime accessors qnx4: switch to new ctime accessors qnx6: switch to new ctime accessors ramfs: switch to new ctime...

Hi, I am a new ext3 user and I am having problems similar to what many people are facing on this list. I have done everything as the emails suggest. I am using SuSE 7.3 with the the 2.4.10 kernel and ext3 compiled as a module. Because it is 2.4.10 kernel, I created all my journals from a rescue disk and everything seems to be working right for the non-root filesystems. My fstab has all my

...the file system type. The file system types which are currently supported are: adfs, affs, autofs, coda, coherent, cramfs, devpts, efs, ext, ext2, ext3, hfs, hpfs, iso9660, minix, msdos, ncpfs, nfs, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, udf, ufs, umsdos, vfat, xenix, xfs, xiafs. Note /dev/hda2 swap swap defaults 0 0 /dev/hda3 / ext2 defaults 1 1 /dev/lv00/publv /pub reiserfs defaults 1 2 /dev/lv00/homelv /home reiserfs defaults 1 2 /dev/hda1...

...-efi\read.mod (1.5 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\reboot.mod (1.8 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\regexp.mod (52.0 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\reiserfs.mod (8.8 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\relocator.mod (17.7 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\romfs.mod (4.3 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\scsi.mod (4.7 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\serial.mod (9 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\setjmp.mod (708 bytes) Extracting: F:\EFI\BOOT\grub\i386-efi\setjmp_test.mod (1.7 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\setpci.mod...

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Removed ks files, now in ovirt-node-recipe, which is subpackage of ovirt-node. Removed tools, these are now in ovirt-node-recipe which is subpackage of ovirt-node.

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