Displaying 3 results from an estimated 3 matches for "fs_image".
Did you mean:
fb_image
2013 Jan 08
10
kernel BUG at fs/btrfs/volumes.c:3707 still not fixed in 3.7.1 (btrfs-zero-log required) but shown as "RIP btrfs_num_copies"
Unfortunately my laptop deadlocks from time to time, and too often
it triggers this bug in btrfs which is quite hard to recover from.
The bigger problem is that all the user sees (if anything) is seemingly
unrelated info, namely, "RIP: btrfs_num_copies+0x42/0x0b" or somesuch
http://marc.merlins.org/tmp/btrfs_num_copies.jpg
It''s only if you have serial console, or netconsole,
2013 Apr 25
1
[syslinux:rockridge] iso9660.c did not copy terminating 0 of Rock Ridge name
On 04/25/2013 07:03 AM, syslinux-bot for Thomas Schmitt wrote:
> Commit-ID: 5de463f724da515fd6c5ea49ded6dde178362181
> Gitweb: http://www.syslinux.org/commit/5de463f724da515fd6c5ea49ded6dde178362181
> Author: Thomas Schmitt <scdbackup at gmx.net>
> AuthorDate: Thu, 4 Apr 2013 20:02:37 +0200
> Committer: Matt Fleming <matt.fleming at intel.com>
> CommitDate:
2013 Mar 28
9
Rock Ridge. Was: Allowed code pages and encodings to write f0.txt through f1.txt?
Hi,
i began to implement a common lookup function for SUSP and Rock Ridge
entries:
/* Obtain the payload bytes of all SUSP entries with a given signature.
@param fs The data source from which to read CE blocks.
@param dir_rec Memory containing the whole ISO 9660 directory record.
@param sig Two characters of SUSP signature. E.g. "NM", "ER", ...