On Wed 11 Jan 2023 00:17:44 +, Gervase wrote:
> On Sat, 2022-12-24 at 14:16 +, Gervase wrote:
> > Awhile back, I did have a look around the fix. From what I
> > remembered,
> > intrigeri's solution used a systemd shutdown 'script' to check for
> > devmaps or whatever of LVMs, ZFS
On Fri 07 Apr 2017 12:02:46 +0200, intrigeri wrote:
> /lib/systemd/system/initramfs-shutdown.service:
> ⋯
> /usr/share/initramfs-tools/initramfs-restore:
> ⋯
> /usr/bin/unmkinitramfs /initrd.img "$WORKDIR"
> ⋯
> /lib/systemd/system-shutdown/initramfs-tools:
> ⋯
>
Ben Hutchings wrote:
> On Mon, 2022-01-10 at 11:04 +1100, Trent W. Buck wrote:
> > Package: initramfs-tools
> > Version: 0.140
> > Severity: wishlist
> >
> > This is a vote for
> > https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/52
&g
PS: my previous email speculated: does zstd -T0 break SOURCE_DATE_EPOCH?
I think this test shows that zstd -T0 is safe even when SOURCE_DATE_EPOCH=1.
i.e. it does not need the equivalent of mkinitramfs's workaround for xz and
gzip.
bash5$ ls -hl
total 1.1G
-rw-r--r-- 1 twb twb 1.1G
Package: initramfs-tools
Version: 0.140
Severity: wishlist
This is a vote for
https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/52
I did this investigation 2 months ago, but AFAICT I forgot to push it to
bugs.debian.org.
Package: debian-kernel-handbook
Version: 1.0.19
Severity: normal
[Initially filed against debian-kernel-handbook because while the
problem is in src:linux, it's not strictly a problem with src:linux's
official binary packages.]
Debian Live images with custom kernels need some workarounds,
Package: initramfs-tools
Version: 0.140
Severity: wishlist
Recent Linux kernels support putting boot options
(e.g. "init=/bin/sh" or "i915.alpha_support=1")
inside the initrd file.
https://www.kernel.org/doc/html/latest/admin-guide/bootconfig.html#boot-kernel-with-a-boot-config
For me,
Trent W. Buck wrote:
> 3. A single mount(2) call also works!
>
> It is quite annoying that we need *anything* special in userland, because
> a nfsvers=4.2,sec=sys mount requires only 2049/tcp (no other ports/services),
> and
> the actual filesystem is in-kernel, so
> r
Short version:
1. nfsmount(8klibc) is still explicitly broken for NFSv4.
2. mount.nfs(8nfs-utils) works in the ramdisk.
3. A single mount(2) call also works!
Boring detailed version follows.
John Goerzen wrote:
> nfsmount is incapable of mounting NFSv4 filesystems. It seems to have
>
Package: nfs-kernel-server
Version: 1:1.3.4-2.5
Severity: minor
File: /usr/share/man/man8/rpc.nfsd.8.gz
The manpage says:
> nproc
>
> specify the number of NFS server threads.
> By default, just one thread is started.
> However, for optimum performance several threads should be used.
Debian Bug Tracking System wrote:
> + LC_ALL=C sort
> [and similar LC_ALL=C elsewhere]
I think you can dial that back from LC_ALL=C to just LC_COLLATE=C.
Informal proof:
bash4$ printf %s\\n README ReadMe readme | LC_COLLATE=en_AU.UTF-8 sort
readme
ReadMe
README
Package: initramfs-tools
Version: 0.120+deb8u2
Severity: wishlist
File: /usr/sbin/mkinitramfs
Several times a month I build Debian Live images and rsync them to
remote sites that use them on diskless kiosk farms.
I was annoyed because if there have been few security updates,
rsync will take a
I recently upgraded my NFSv3 clients from wheezy to jessie, and they just DID
NOT WORK.
The NFS sysvinit init scripts had dependency cycles & race conditions when used
under systemd.
I ended up writing my own systemd units for the parts I needed (foo.mount,
statd, & rpcbind),
and disabling the
Hi,
I wanted to say pass options to my compress program, e.g.
# cat /etc/initramfs-tools/conf.d/xz
compress="pxz -Ccrc32 -1" # dev builds should build fast
compress="pxz -Ccrc32 -9ev" # prod builds should boot fast
Unfortunately this code requires the compress (or
[Here are some background details on this feature.]
There is a dumber "good enough" command called "systemd-analyze plot".
I asked myself: is it worth rolling a custom kernel just for systemd-bootchart?
I looked for some examples to compare; I found these
Package: initramfs-tools
Version: 0.115
Severity: wishlist
File: /usr/sbin/mkinitramfs
When building a live-boot image with a custom kernel that lacks CONFIG_MODULE,
I ran into this warning output:
Setting up linux-image-3.13.7inmate (3.13.7inmate-1) ...
update-initramfs: Generating
Ben Hutchings wrote:
I'll change it to treat ENOTDIR as non-fatal (same as ENOENT).
Thanks, that sounds appropriate to me.
4875 open(/boot/extlinux/options.cfg, O_RDONLY) = -1 ENOTDIR (Not a
directory)
FTR, this was happening because /boot/extlinux existed -- it was the
installer
Package: linux-base
Version: 3.5
Severity: minor
I did the following:
- basic squeeze install, choose no bootloader,
- manually do an extlinux install in /boot (extlinux package is NOT installed)
- set link_in_boot=yes in kernel-img.conf
Those are about the only things I did. Then I
Package: linux-2.6
Severity: wishlist
Tags: experimental
User: debian-l...@live.debian.org
Usertags: kernel
xz (a.k.a. LZMA2) is a shiny new compression algorithm that yields
smaller files than gzip, and is faster than bzip2.
For Debian Live images, especially, it would be nice to have better
Package: linux-base
Version: 2.6.34-1~experimental.2
Severity: minor
I had cdebootstrap generate a squeeze chroot, and installed a kernel
into it. When I then ran dpkg-reconfigure -a -plow in the chroot,
this package borked the dpkg-reconfigure run because /etc/fstab
doesn't exist.
+ chroot
Package: initramfs-tools
Version: 0.94.4
Severity: wishlist
Following the kernel handbook, I built a mainline kernel using make
deb-pkg. This kernel is configured without modules or initrd
support. On installing it with dpkg -i, I got this:
$ sudo dpkg -i
Vagrant Cascadian wrote:
Please consider setting CONFIG_RAMZSWAP (a.k.a. compcache), which
enables a ram based compressed swap device. i think it can be
enabled as a module, but i'm not sure.
This feature is very useful to thin clients, embedded devices, or
other environments with limited
Bastian Blank wrote:
On Fri, Feb 26, 2010 at 09:57:37AM +1100, Trent W. Buck wrote:
# printf ondemand /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
It should give an error here.
# dmesg | tail -1
[38198.312686] ondemand governor failed, too long transition latency
Moritz Muehlenhoff wrote:
After upgrading from .29 to .30, I can no longer change my CPU
frequency scaling governor: [...]
The next release of Debian (6.0, code name Squeeze) will be based on
2.6.32. Please test the current 2.6.32 from unstable/testing and
tell us whether the problem
Ben Hutchings wrote:
Also, you could try using acpi-cpufreq instead of p4-clockmod. I
don't know whether it will work on this machine but it might do.
# modprobe acpi-cpufreq
FATAL: Error inserting acpi_cpufreq
On Sun, Aug 10, 2008 at 12:57:29AM +0100, David wrote:
retitle 463860 [atl2] Fails to create a wifi interface
I think atl2 is wrong. Aren't you talking about the ath5k driver?
atl2 drives the Attansic Technology Corp. L2 100 Mbit Ethernet Adapter.
--
To UNSUBSCRIBE, email to
Package: linux-image-2.6.29-1-686
Version: 2.6.29-1
Severity: normal
I'm using an Eee PC 701, which has a wired interface:
03:00.0 Ethernet controller: Attansic Technology Corp. L2 100 Mbit Ethernet
Adapter (rev a0)
This has worked fine with previous kernel versions. After upgrading
to
I encountered this bug when running VMWare Server 1.0.3 on CentOS (4
or 5, I think). The guest OS was a fresh Debian Etch AMD64 system
(using 2.6.18) which I dist-upgraded to Lenny (using 2.6.22).
The 2.6.22 kernel could not detect the SCSI drive, with the same
diagnostics as reported by OP.
28 matches
Mail list logo
