search for: ufs1

...onfigured as a module, then you need to recompile your kernel with that option enabled. Further information can be found in the link below: http://oz123.github.io/writings/2012-11-26-enable-ufs-write-support-debian/ Creating an UFS image: sudo dd if=/dev/zero of=<image> bs= count=; - UFS1: sudo mkfs.ufs -O 1 <image>; - UFS2: sudo mkfs.ufs <image>; Mounting an UFS image: - UFS1: sudo mount -t ufs -o rw,loop,ufstype=44bsd <image> <mountpoint>; - UFS2: sudo mount -t ufs -o rw,loop,ufstype=ufs2 <image> <mountpoint>; Insta...

...onfigured as a module, then you need to recompile your kernel with that option enabled. Further information can be found in the link below: http://oz123.github.io/writings/2012-11-26-enable-ufs-write-support-debian/ Creating an UFS image: sudo dd if=/dev/zero of=<image> bs= count=; - UFS1: sudo mkfs.ufs -O 1 <image>; - UFS2: sudo mkfs.ufs <image>; Mounting an UFS image: - UFS1: sudo mount -t ufs -o rw,loop,ufstype=44bsd <image> <mountpoint>; - UFS2: sudo mount -t ufs -o rw,loop,ufstype=ufs2 <image> <mountpoint>; Insta...

.../fs/ufs/bmap.c b/core/fs/ufs/bmap.c new file mode 100644 index 0000000..117daef --- /dev/null +++ b/core/fs/ufs/bmap.c @@ -0,0 +1,202 @@ +/* + * Copyright (C) 2013 Raphael S. Carvalho <raphael.scarv at gmail.com> + * + * Partially taken from fs/ext2/bmap.c + * This file was modified according UFS1/2 needs. + * + * Copyright (C) 2009 Liu Aleaxander -- All rights reserved. This file + * may be redistributed under the terms of the GNU Public License. + */ + +#include <stdio.h> +#include <dprintf.h> +#include <fs.h> +#include <disk.h> +#include <cache.h> +#include &...

.../fs/ufs/bmap.c b/core/fs/ufs/bmap.c new file mode 100644 index 0000000..117daef --- /dev/null +++ b/core/fs/ufs/bmap.c @@ -0,0 +1,202 @@ +/* + * Copyright (C) 2013 Raphael S. Carvalho <raphael.scarv at gmail.com> + * + * Partially taken from fs/ext2/bmap.c + * This file was modified according UFS1/2 needs. + * + * Copyright (C) 2009 Liu Aleaxander -- All rights reserved. This file + * may be redistributed under the terms of the GNU Public License. + */ + +#include <stdio.h> +#include <dprintf.h> +#include <fs.h> +#include <disk.h> +#include <cache.h> +#include &...

It's needed to enumerate both UFS1/2 since they have different magic numbers and super block offsets. Besides, UFS2 can be installed in the 0-64k range like BTRFS, whereas UFS1 can't. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- extlinux/main.c | 71 +++++++++--- extlinux/ufs.h |...

It's needed to enumerate both UFS1/2 since they have different magic numbers and super block offsets. Besides, UFS2 can be installed in the 0-64k range like BTRFS, whereas UFS1 can't. UFS2 has no cow feature unlike BTRFS. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- extlinux/main.c | 79 +++...

...get_default_subvol(char * rootdir, char * subvol) > > static int install_file(const char *path, int devfd, struct stat *rst) > { > - if (fs_type == EXT2 || fs_type == VFAT || fs_type == NTFS) > + if (fs_type == EXT2 || fs_type == VFAT || fs_type == NTFS > + || fs_type == UFS1) > return ext2_fat_install_file(path, devfd, rst); > - else if (fs_type == BTRFS) > + else if (fs_type == BTRFS || fs_type == UFS2) > return btrfs_install_file(path, devfd, rst); > else if (fs_type == XFS) > return xfs_install_file(path, devfd, rst); > @@ -983,...

In attach. Usage: > mkfs-opts ufs /dev/vda1 features:1 Creates UFS1 partition > mkfs-opts ufs /dev/vda1 features:2 Creates UFS2 partition. -- Nikita A Menkovich JID: menkovich at gmail.com Tel: +7 (921) 423-96-48 -------------- next part -------------- A non-text attachment was scrubbed... Name: do_mkfs.ufs.patch Type: text/x-patch Size: 2809 bytes Desc: not av...

...a better core/ldlinux_limit.pl > > This should be rendered obsolete and unnecessary with the recent patch for > ldlinux.sys on btrfs (but might be relevant for UFS2). > > --Gene Hi everyone, it's been a long time. Anyway, let's go to what really matters here. 1) No, neither ufs1 nor ufs2 has support to the COW feature. That being said, ldlinux.sys can be installed as a regular file unlike BTRFS (should we fall back to this approach when ldlinux.sys size is greater than 64kb or make it a default decision for ufs1/2?). I don't know enough details of the installer, so her...

...linux/main.c Mon Oct 06 16:27:44 2014 +++ syslinux-6.03_typo/extlinux/main.c Fri Nov 13 02:29:56 2015 @@ -14,7 +14,7 @@ /* * extlinux.c * - * Install the syslinux boot block on an fat, ntfs, ext2/3/4, btrfs, xfs, + * Install the syslinux boot block on a fat, ntfs, ext2/3/4, btrfs, xfs, * and ufs1/2 filesystem. */ @@ -392,11 +392,11 @@ if (sb5.sb_magicnum == *(u32 *)XFS_SB_MAGIC) { if (be32_to_cpu(sb5.sb_blocksize) != XFS_SUPPORTED_BLOCKSIZE) { fprintf(stderr, - "You need to have 4 KiB filesystem block size for " - " being able to install Syslinux in your XF...

...re Syslinux bootsector can be installed" + " regardless of the filesystem block size)\n"); return 1; } @@ -420,8 +420,8 @@ int install_bootblock(int fd, const char *device) if (!ok) { fprintf(stderr, - "no fat, ntfs, ext2/3/4, btrfs, xfs " - "or ufs1/2 superblock found on %s\n", + "no fat, ntfs, ext2/3/4, btrfs, xfs" + " or ufs1/2 superblock found on %s\n", device); return 1; } @@ -751,7 +751,7 @@ bail: * * test if path is a subvolume: * * this function return * * 0-> path exists but it is not...

On Fri, Nov 13, 2015 at 06:14:36AM +0100, Geert Stappers via Syslinux wrote: > On Fri, Nov 13, 2015 at 05:05:26AM +0200, Ady via Syslinux wrote: > > diff U3 syslinux-6.03/extlinux/main.c syslinux-6.03_typo/extlinux/main.c > > --- syslinux-6.03/extlinux/main.c Mon Oct 06 16:27:44 2014 > > +++ syslinux-6.03_typo/extlinux/main.c Fri Nov 13 02:29:56 2015 > > patch seen >

...gt; know, UFS symlinks are very similar to ext* symlinks (not surprising >> since ext2 was heavily inspired by UFS): symlinks below a specific size >> is stored in the inode overlaying the block pointers, and otherwise the >> symlink is just an ordinary file. > According to the ufs1/2 specification, a symbolic link stores the path > of the destination file in a fragment (1024 bytes), or in the 60/120 > bytes used for ufs1/2 block pointers respectively. Right... the former is the same thing as a (short) file, right? (I'm assuming a very long symlink could be longer...

I am building a tool to identify the file that has a specific LBA. The approach I am using is to search through each inode from number 2 up. This approach works well with UFS1 file systems as then preinitialize all the inodes. However, UFS2 does lazy inode initialization so there are always some that are basically garbage. I have not found any relaiable way to determine from the inode contents if it is in use or not. I suspect that information is in the inod...

On 05/29/2014 07:36 AM, Raphael S Carvalho wrote: > On Thu, May 29, 2014 at 11:30 AM, H. Peter Anvin <hpa at zytor.com> wrote: >> On 05/29/2014 07:20 AM, Raphael S.Carvalho wrote: >>> +static int ufs_readlink(struct inode *inode, char *buf) >>> +{ >>> + ufs_debug("ufs_readlink\n"); >>> + return inode->size; >>> +}

...option wasn't even configured as a module, then you need to enable it and recompile your kernel. Further information can be found here: http://oz123.github.io/writings/2012-11-26-enable-ufs-write-support-debian/ Creating an UFS image: sudo dd if=/dev/zero of=<image> bs= count=; - UFS1: sudo mkfs.ufs -O 1 <image>; - UFS2: sudo mkfs.ufs <image>; Mounting an UFS image: - UFS1: sudo mount -t ufs -o rw,loop,ufstype=44bsd <image> <mountpoint>; - UFS2: sudo mount -t ufs -o rw,loop,ufstype=ufs2 <image> <mountpoint>; Insta...

...t. As far as I > know, UFS symlinks are very similar to ext* symlinks (not surprising > since ext2 was heavily inspired by UFS): symlinks below a specific size > is stored in the inode overlaying the block pointers, and otherwise the > symlink is just an ordinary file. According to the ufs1/2 specification, a symbolic link stores the path of the destination file in a fragment (1024 bytes), or in the 60/120 bytes used for ufs1/2 block pointers respectively. > > -hpa > > -- Raphael S. Carvalho

...mlinks are very similar to ext* symlinks (not surprising >>> since ext2 was heavily inspired by UFS): symlinks below a specific size >>> is stored in the inode overlaying the block pointers, and otherwise the >>> symlink is just an ordinary file. >> According to the ufs1/2 specification, a symbolic link stores the path >> of the destination file in a fragment (1024 bytes), or in the 60/120 >> bytes used for ufs1/2 block pointers respectively. > > Right... the former is the same thing as a (short) file, right? (I'm > assuming a very long sy...

...n threads) 09/30 [PATCH v2] core: Check size of ldlinux.sys at building time (needs core shrink first) 09/06-09/17 [PATCH 2/2] com32/disk: Improve flow at disk_write_sectors and disk_read_sectors (rework needed) 09/06-09/30 [PATCH 1/2] com32/lib/: Avoid unneeded allocation. 07/22 [PATCH 1/1 v2] Add UFS1/2 support to Extlinux installer. 07/19 core/fs: Add support to Unix File system 1/2. 07/18 core/serial: Add support for serial output functions. -Pending rejection 10/8 gPXE null pointer deref (gPXE should be removed) -To Merge shortly: 09/30 diag/geodsp: README fixes 07/18 PXE legacynet DNS dotq...

...at boot time. * kbd: Getting the keyboard shift state is now a firmware method. * kbd: Fix force-prompt features. * BTRFS: Fix booting on BTRFS. * cache, btrfs: Provide a general cached read routine. * NTFS: Correct file->offset usage in ntfs_readdir (Andy Alex). * New support for UFS/FFS (UFS1/2) (Raphael S. Carvalho). * adv: Remove double definition; it should fix uses of the ADV, including "--once". * Make symbols defined in linker script HIDDEN. * memdump: Remove old obsolete COM16 binary. * com32: Fix lua's dependencies; improve parallel build.