similar to: [BUG][PATCH] fstype: wrong size returned for jfs

[please note that I'm not subscribed to the list] Hi again, this patch adds support for the NILFS2 (http://www.nilfs.org/) filesystem to fstype (on top of 1.5.7 from the debian package). Please let me know what you think. (please note that I'm not affiliated to nilfs in any way). diff -Nur klibc-1.5.7.orig/usr/kinit/fstype/fstype.c klibc-1.5.7/usr/kinit/fstype/fstype.c ---

hello hpa, rebased my branch, please pull latest git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks for the following shortlog maximilian attems (6): fstype: add squashfs v3 support reiser4_fs.h: add attribute packed to reiser4_master_sb fstype: add ext4 support .gitignore: add subdir specific entries usr/klibc/Kbuild: beautify klibc build fstype:

hello hpa, nothing particular stands out, just syncing with latest Debian upload and subsequent patch emails. please review merge or nack. thanks :) maks git pull git://git.debian.org/~maks/klibc.git maks for the changes: Aaron Griffin (1): [klibc] kinit: skip md assembly if mdX exists Colin Watson (1): [klibc] mount/umount FUSE support Harald Jenny (1): [klibc] fstype:

Enhance fstype so it properly takes into account whether or not the ext4 and/or ext4dev filesystems are present, and properly handles the test_fs flag. The old code also has some really buggy checks --- for example, where it compared the set of supported ro_compat features against the incompat feature bitmask: (sb->s_feature_incompat & __cpu_to_le32(EXT3_FEATURE_RO_COMPAT_SUPP) I

Various coding style fixes checkpatch warns about. The goal is not to be 100% checkpatch compliant, but to have more consistent coding style. As this is a trivial patch serie, will land in 24 hours in klibc git, unless of course ml review hits a bugger. Checked with size(3) that the generated kinit, fstype, ipconfig and nfsmount are the same. maximilian attems (4): [klibc] ipconfig: reduce

The attached patch adds support for detecting LUKS partitions (Linux Unified Key Setup - http://luks.endorphin.org/) to fstype. This makes it easier to automatically detect and activate encrypted (root) partitions from an initramfs image. The patch is now against klibc's git tree instead of klibc-1.2. Signed-off-by: David H?rdeman <david@2gen.com> -- fstype.c | 17

The attached patch adds the ability to fstype to detect lvm2 physical volumes (PV's). Signed-off-by: David H?rdeman <david@2gen.com> -------------- next part -------------- diff -Nur klibc-orig/usr/kinit/fstype/fstype.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

The attached patch adds iso9660 detection support to fstype. Signed-off-by: David H?rdeman <david at hardeman.nu> -- fstype.c | 17 +++++++++++++++++ iso9660_sb.h | 24 ++++++++++++++++++++++++ 2 files changed, 41 insertions(+) -------------- next part -------------- diff -Nru klibc/usr/kinit/fstype/fstype.c klibc-hack/usr/kinit/fstype/fstype.c ---

This patch adds support for the F2FS filesystem to fstype. Signed-off-by: Marc Dietrich <marvin24 at gmx.de> --- usr/kinit/fstype/f2fs_fs.h | 44 ++++++++++++++++++++++++++++++++++++++++++++ usr/kinit/fstype/fstype.c | 14 ++++++++++++++ 2 files changed, 58 insertions(+) create mode 100644 usr/kinit/fstype/f2fs_fs.h diff --git a/usr/kinit/fstype/f2fs_fs.h b/usr/kinit/fstype/f2fs_fs.h

Hi, As I use btrfs as root FS, I wanted fstype to be able to recognize it. The following patch add support for this FS. Regards, benjamin Signed-off-by: Benjamin Cama <benoar at free.fr> --- diff --git a/usr/kinit/fstype/btrfs_fs.h b/usr/kinit/fstype/btrfs_fs.h new file mode 100644 index 0000000..e1f933e --- /dev/null +++ b/usr/kinit/fstype/btrfs_fs.h @@ -0,0 +1,51 @@ +#ifndef

hello hpa, please pull git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks for those changes: Kyle McMartin (1): klibc-utils: add dmesg maximilian attems (2): klibc comment fix fstype: add ocfs2 support with the following diffstat README | 2 usr/Kbuild | 2 usr/kinit/fstype/fstype.c | 15 +++++++

Here's a patch to support JFS in fstype. Given that this runs as root, would you consider a patch to take the device as an argument rather than stdin? I get really nervous that one of these days I'm going to > rather than <. But otherwise... =) Tested against 1.0.14, but there's nothing in there that should keep it from applying against current git that I can see. Tks, Jeff

hello hpa, current patch queue for review, please pull: git pull git://git.debian.org/users/maks/klibc.git maks Aurelien Jarno (1): [klibc] sh4: syscalls fixes Benjamin Cama (1): [klibc] fstype: btrfs size endianness fix Thorsten Glaser (1): [klibc] add getrusage() maximilian attems (3): [klibc] resume: silence warning on resume try [klibc] bootp_packet.h minor

hello hpa, nothing too exciting, again syncing latest Debian upload and subsequent patch emails. plus wanting to get the ext4dev in line for the Lenny release. :) please review. thanks -- maks please pull git pull git://git.debian.org/~maks/klibc.git maks for the changes: Arthur Loiret (1): Makefile (ARCH): Support sh4 as sh. David H?rdeman (1): [klibc] mount: allow multiple fs

Commit-ID: 52251e210c7a21068063fe16a3874903d3f1aa14 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=52251e210c7a21068063fe16a3874903d3f1aa14 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 7 Oct 2019 20:39:46 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 8 Oct 2019 00:13:20 +0100 [klibc] fstype: Drop obsolete

ext4 no longer requires a journal. Compare: http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=commitdiff;h=a90f5391dda78f7bc4a8196a78355584ace0adf5 Signed-off-by: Colin Watson <cjwatson at ubuntu.com> --- usr/kinit/fstype/fstype.c | 8 -------- 1 files changed, 0 insertions(+), 8 deletions(-) diff --git a/usr/kinit/fstype/fstype.c b/usr/kinit/fstype/fstype.c index 69e0e30..bf63b1b

This is part of some patches to support sectors > 512. Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason. This patch add a rdwr_bytes functions which remove the assumption in some places that sector is 512. This function is quite helpful if you are going to read/write a range of bytes to/from the stack without creating stack overflows for free.

hello hpa, here my birthday submission :) please pull: git pull git://git.debian.org/users/maks/klibc.git maks Sam fixed a longstanding x86_32 build bug, thus it seems a good time to flush the queue of the piled up patches, the shortlog tells it: Aurelien Jarno (1): [klibc] sh4: syscalls fixes Benjamin Cama (1): [klibc] fstype: btrfs size endianness fix Mike Waychison (2):

"IT3 Stuart Blake Tener, USNR-R" wrote: > In terms of enterprise reliability, I understand, however, having an > "office recommended journaling filesystem", Some journaling filesystems can be _worse_ than non-journaled. If the recovery mechanism of the JFS is to "aggressively" go to the journal, journal mis-reads can _toast_ a filesystem. I'll take a full

CentOS Errata and Security Advisory 2013:0509 Low Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0509.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: fa98c0004fddc0eb5accd47bbc64b020470f83d707b0a498abb58e59c562111d ibutils-1.5.7-7.el6.i686.rpm