Public bug reported:
Speaking about this line in unmkinitramfs:
113: dd < "$initramfs" skip=$start count=$((end - start))
iflag=skip_bytes 2> /dev/null |
dd's block size is 512 by default. iflag=skip_bytes does not change that. Both
$end and $start are byte-offsets. Hence the count is
Just found out, aside for skip_bytes iflag, there is also count_bytes
one. So another fix count be:
113: dd < "$initramfs" skip=$start count=$((end - start))
iflag=skip_bytes,count_bytes 2> /dev/null |
** Description changed:
Speaking about this line in unmkinitramfs:
- 113: dd <
> The count_bytes solution looks better to me
The updated patch is attached.
I've just checked: all the *_bytes flags were introduced to dd in the
same commit
https://github.com/coreutils/coreutils/commit/140eca15c4a3d3213629a048cc307fde0d094738,
so it is safe to throw in count_bytes in the mix.
https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/92
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055055
Title:
unmkinitramfs: wrong and unneeded count= in a dd call
To
Previously I created a script to make ubuntu iso images bootable from
f2fs partitions. After discovering this bug, I converted it into a
generic "make casper aware of fs X, add kernel modules Y to the initrd"
one.
You can get it here https://github.com/slowpeek/ubuntu-remaster-bbb and
make 20.04+
The script from the post is deprecated now, I converted it into a
generic "make casper aware of fs X, add kernel modules Y to the initrd"
one.
You can get it here https://github.com/slowpeek/ubuntu-remaster-bbb and
make 14.04+ images bootable from f2fs like this:
ubuntu-remaster-f2fs input.iso
Public bug reported:
Since 23.10 the initrd consists of 4 embedded cpio:
- amd microcode
- intel microcode
- firmware + kernel modules
- rest (compressed)
Previously it was:
- amd microcode
- intel microcode
- rest (compressed)
There is no archive size header for cpio, so unmkinitramfs has to
Public bug reported:
I guess this is the correct source package to send a feature request for
debian/build-efi-images script.
Here is what I ask for:
--- build-efi-images
+++ build-efi-images.new
@@ -101,7 +101,9 @@
echo
efifwsetup
efinet
+ exfat
ext2
+
> any practical utility
Recent ubuntu desktop iso images are way over 4Gb in size, which is the
max file size for fat32. Fat32 for long time was the obvious choice to
keep iso images on.
Exfat is of interest for those who still need compatibility with
w/ndows, like it was with fat32.
F2fs is of
> isn't really an intended use-case
But there is /boot/grub/loopback.cfg since at least 14.04!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060168
Title:
Prebuilt signed grub images should
Public bug reported:
Ubuntu iso images bundle the f2fs driver in initrd since 20.04, but
casper does not recognize f2fs as a supported fs even in 24.04. Hence,
the images cant loop-boot from f2fs partitions.
A 2-lines change is all that's required since 20.04 (casper-helpers
since 22.04,
** Description changed:
Ubuntu iso images bundle the f2fs driver in initrd since 20.04, but
casper does not recognize f2fs as a supported fs even in 24.04. Hence,
the images cant loop-boot from f2fs partitions.
A 2-lines change is all that's required since 20.04 (casper-helpers
since
@Adrian Feliks (mexit)
I've just filed a similar bug about f2fs. The module is in initrd since
20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038694
Title:
Now that exfat filesystem is in
@Adrian Feliks (mexit)
How is it supposed to work with just that? Looking into initrd of 24.04
daily unpacked with unmkinitramfs. According to
main/lib/modules/6.8.0-11-generic/modules.builtin, exfat is not a
builtin module. And there is no exfat in
> I have implemented the listing of uncompressed cpio archives (roughly
120 lines of code). Now I have to add the decompression support
Finding offsets of the embedded archives is the only time consuming part
of the whole script. Mby it is better to create a separate tool, say
"scaninitramfs", to
Commenting on #2:
When building busybox, there is a number of config switches. For your binary to
support "ps -w" you need this in the config:
- CONFIG_DESKTOP is not set
- CONFIG_FEATURE_PS_WIDE=y
On my 22.04 systems I've got 2 busybox binaries: /usr/bin/busybox (2.1M)
from busybox-static
After looking deeper into the repo history, I see the questionable
implementation of pgrep_exe() was introduced by this patch
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/comments/11
in attempt to adopt the debian code to the ubuntu environment. Aside for
other things, it ignores
17 matches
Mail list logo
