Re: It makes no sense to link vmlinuz and initramfs to the root directory
Am Dienstag, 12. November 2024, 07:14:34 CET schrieb kindusmith: In very early linux, as far as I remember in SuSE-Linux, the kernel was installed in a small partition /boot (about 3 or 4 sizes of the kernel) and a link ponting to the kernel on the root-partitiion (the one, mounted to "/") This got some advantages. If you have a very big root poartition and the kernel was installed there, then it was possible, the system could not boot, because the kernel was not found. The reason for this was, the BIOS could not handle the size of this big partition. To fix this and get not in trouble, the idea was to make a small partition which got the kernel and can be booted, then after the kernel has started, BIOS is no more used, because the kernel is handling the paretitiions. Andthe kernel can handle very, very big partitions. The sesond advantage of putting the kernel so, is , you can mount the kernel partition read-only, so it can not be harmed by any malware. For the uprading procedure it is possible (with a little script), to make this partition writable, and automatically read-only after upgrade is done. (If someone is interested in this, I will paste the script here, these are only 4 lines). I might remember, the seperated /boot partition was also default in RedHat, Mandriva and SLAX, but I am not quite sure. It is now a long time ago! However, maybe a link is alo no more needed, even with a seperated /boot partition. Best Hans > In early Unix, boot and vmunix were both stored in the root directory as > programs, and boot was used to start vmunix. Debian inherited this for > compatibility, but the situation has changed a lot. Today, boot is > stored in the root directory as a directory, which already contains the > kernel files vmlinuz and initramfs. Therefore, it makes no sense to link > vmlinuz and initamfs to the root directory, so the best way is to remove > them from the root directory.
Bug#1087394: ITP: reproc -- reproc (Redirected Process) is a cross-platform C/C++ library
Package: wnpp Severity: wishlist Owner: Valentin Vidic X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: reproc Version : 14.2.5 Upstream Contact: Daan De Meyer * URL : https://github.com/DaanDeMeyer/reproc * License : MIT Programming Lang: C, C++ Description : library for executing command line applications reproc (Redirected Process) is a cross-platform C/C++ library that simplifies starting, stopping and communicating with external programs. The main use case is executing command line applications directly from C or C++ code and retrieving their output. . reproc consists out of two libraries: reproc and reproc++. reproc is a C99 library that contains the actual code for working with external programs. reproc++ depends on reproc and adapts its API to an idiomatic C++11 API. It also adds a few extras that simplify working with external programs from C++. This package is required as a dependency for new version of sonic-pi package. Packaging repo will be created on salsa.debian.org.
Bug#1087395: ITP: golang-github-tc-hib-winres -- Embedding Windows icons/manifest/versioninfo/etc into Go executables
Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-tc-hib-winres Version : 0.3.1-1 Upstream Author : Thomas Combeléran, et al * URL : https://github.com/tc-hib/winres * License : 0BSD Programming Lang: Go Description : Embedding Windows icons/manifest/versioninfo/etc into Go executables Package winres provides functions for embedding resources in a Windows executable built with Go. . Most often, you'll want to embed an application icon, a manifest, and "version information", which is what you can see in the Details tab of file properties. I hope to maintain this package as part of Debian Go Packaging Team: https://salsa.debian.org/go-team/packages/golang-github-tc-hib-winres /Simon signature.asc Description: PGP signature
Re: It makes no sense to link vmlinuz and initramfs to the root directory
On Tue, Nov 12, 2024 at 02:14:34PM +0800, kindusmith wrote: In early Unix, boot and vmunix were both stored in the root directory as programs, and boot was used to start vmunix. Debian inherited this for compatibility, but the situation has changed a lot. Today, boot is stored in the root directory as a directory, which already contains the kernel files vmlinuz and initramfs. Therefore, it makes no sense to link vmlinuz and initamfs to the root directory, so the best way is to remove them from the root directory. You may alter /etc/kernel-img.conf however you wish.
Bug#1087396: ITP: golang-github-tc-hib-go-winres -- Command line tool for adding Windows resources to executable files
Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-tc-hib-go-winres Version : 0.3.3-1 Upstream Author : Thomas Combeléran, et al * URL : https://github.com/tc-hib/go-winres * License : 0BSD Programming Lang: Go Description : add Windows resources to executable files A simple command line tool for embedding usual resources in Windows executables built with Go: . * A manifest * An application icon * Version information (the Details tab in file properties) * Other icons and cursors I hope to maintain this package as part of Debian Go Packaging Team: https://salsa.debian.org/go-team/packages/golang-github-tc-hib-go-winres /Simon signature.asc Description: PGP signature
Re: It makes no sense to link vmlinuz and initramfs to the root directory
On 2024-11-12 12:45:47, Michael Stone wrote: > On Tue, Nov 12, 2024 at 02:14:34PM +0800, kindusmith wrote: > > In early Unix, boot and vmunix were both stored in the root directory as > > programs, and boot was used to start vmunix. Debian inherited this for > > compatibility, but the situation has changed a lot. Today, boot is > > stored in the root directory as a directory, which already contains the > > kernel files vmlinuz and initramfs. Therefore, it makes no sense to link > > vmlinuz and initamfs to the root directory, so the best way is to remove > > them from the root directory. > > You may alter /etc/kernel-img.conf however you wish. The question is why on a default install with grub, which doesn't need nor use the symlinks, are they still created. For most systems, they're superfluous. iustin, who also dislikes these and always needs to disable them
Re: Re: It makes no sense to link vmlinuz and initramfs to the root directory
Hi! On Tue, 2024-11-12 at 11:02:53 +0100, Johannes Schauer Marin Rodrigues wrote: > Quoting Hans (2024-11-12 09:35:08) > > However, maybe a link is alo no more needed, even with a seperated /boot > > partition. > > It's just a symlink. What's the harm? For me, the default location of the symlinks (which was the initial complaint) pollutes the root directory with files that to me do not belong there. > Having the symlink is very practical for bootloaders that are not grub. > Pointing an extlinux.conf or a boot.scr to /vmlinuz instead of having to infer > the version is nice. While related, I don't think this was the complaint at hand. I've got no systems I personally manage with symlinks on /, but for the systems where those symlinks are present (most of them, one with etckeeper history going back to 2009, when I installed etckeeper there), those get placed under /boot, which gives the advantages you point out. This would be the distinction between: do_symlinks = yes and image_dest = /boot or link_in_boot = yes > The tool debvm-run also relies on that symlink to infer the kernel image > location. > > And so does the tool mmdebstrap-autopkgtest-build-qemu. > > This is why this is a good example of Chesterton's Fence as Geert already > pointed out. Before trying to tear it down, maybe you missed some of its uses. I've had in mind starting this discussion some time ago, when I found again a system with this default (thanks for starting it now!), but postponed it because it would require checking whether there is any current code that might break (although that would seem surprising given the kernel-img.conf options available). I think the first step, before considering a default change would probably be a visit over codesearch.debian.net, and then see what needs fixing or adapting to support both locations, then file some bugs (ideally with patches), and once those are handled then file a bug against whatever generates the default kernel-img.conf, and against what holds the default value to change it? Thanks, Guillem
Bug#1087371: ITP: golang-github-ccoveille-go-safecast -- Safe number conversion in Go
Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-ccoveille-go-safecast Version : 1.1.0-1 Upstream Author : ccoVeille * URL : https://github.com/ccoveille/go-safecast * License : Expat Programming Lang: Go Description : Safe number conversion in Go go-safecast solves the type conversion issues in Go . Address gosec G115 and cwe-190 Integer Overflow or Wraparound . In Go, integer type conversion can lead to a silent and unexpected behavior and errors if not handled carefully. . This package helps to convert any number to another, and report an error when if there would be a loss or overflow in the conversion I hope to maintain this package as part of Debian Go Packaging Team: https://salsa.debian.org/go-team/packages/golang-github-gen2brain-beeep /Simon signature.asc Description: PGP signature
Re: Re: It makes no sense to link vmlinuz and initramfs to the root directory
Quoting Hans (2024-11-12 09:35:08) > However, maybe a link is alo no more needed, even with a seperated /boot > partition. It's just a symlink. What's the harm? Having the symlink is very practical for bootloaders that are not grub. Pointing an extlinux.conf or a boot.scr to /vmlinuz instead of having to infer the version is nice. The tool debvm-run also relies on that symlink to infer the kernel image location. And so does the tool mmdebstrap-autopkgtest-build-qemu. This is why this is a good example of Chesterton's Fence as Geert already pointed out. Before trying to tear it down, maybe you missed some of its uses. Thanks! cheers, josch signature.asc Description: signature
Bug#1087376: ITP: lomiri-tfamanager-app -- 2-Factor-Authentication Manager App for Lomiri Operating Environment
Package: wnpp Severity: wishlist Owner: Mike Gabriel X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: lomiri-tfamanager-app Version : 1.7.0 Upstream Contact: Joan CiberSheep * URL : https://gitlab.com/cibersheep/tfamanager/ * License : GPL-3 Programming Lang: QML Description : 2-Factor-Authentication Manager App for Lomiri Operating Environment This app is a core app for Ubuntu Touch's shell Lomiri. Ubuntu Touch is a mobile OS developed by the UBports Foundation. Lomiri is its operating environment optimized for touch based human-machine interaction, but also supports convergence (i.e. switching between tablet/phone and desktop mode). . This package provides a 2FA Manager App for Lomiri. . This package will be maintained under the umbrella of the Debian UBports Packaging Team.
Bug#1087369: ITP: golang-github-gen2brain-beeep -- Go cross-platform library for sending desktop notifications, alerts and beeps
Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-gen2brain-beeep Version : 0.0~git20240516.9c00667-1 Upstream Author : Milan Nikolic * URL : https://github.com/gen2brain/beeep * License : BSD-2-clause Programming Lang: Go Description : Go cross-platform library for sending desktop notifications, alerts and beeps beeep provides a cross-platform library for sending desktop notifications, alerts and beeps. I hope to maintain this package as part of Debian Go Packaging Team: https://salsa.debian.org/go-team/packages/golang-github-gen2brain-beeep /Simon signature.asc Description: PGP signature
Re: It makes no sense to link vmlinuz and initramfs to the root directory
On Tue, Nov 12, 2024 at 09:35:08AM +0100, Hans wrote: > Am Dienstag, 12. November 2024, 07:14:34 CET schrieb kindusmith: > In very early linux, as far as I remember in SuSE-Linux, the kernel was > installed in a small partition /boot (about 3 or 4 sizes of the kernel) and a > link ponting to the kernel on the root-partitiion (the one, mounted to "/") > > This got some advantages. If you have a very big root poartition and the > kernel was installed there, then it was possible, the system could not boot, > because the kernel was not found. The reason for this was, the BIOS could not > handle the size of this big partition. > > To fix this and get not in trouble, the idea was to make a small partition > which got the kernel and can be booted, then after the kernel has started, > BIOS is no more used, because the kernel is handling the paretitiions. Andthe > kernel can handle very, very big partitions. > > The sesond advantage of putting the kernel so, is , you can mount the kernel > partition read-only, so it can not be harmed by any malware. > > For the uprading procedure it is possible (with a little script), to make > this > partition writable, and automatically read-only after upgrade is done. > (If someone is interested in this, I will paste the script here, these are > only 4 lines). > > I might remember, the seperated /boot partition was also default in RedHat, > Mandriva and SLAX, but I am not quite sure. It is now a long time ago! > > However, maybe a link is alo no more needed, even with a seperated /boot > partition. I'm afraid none of this is relevant to the question which was about garbage symlinks in /. We know how is /boot used. -- WBR, wRAR signature.asc Description: PGP signature
Bug#1087377: ITP: golang-github-bugst-go-serial -- A cross-platform serial library for go-lang.
Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-bugst-go-serial Version : 1.6.2-1 Upstream Author : bug.st * URL : https://github.com/bugst/go-serial * License : BSD-3-clause Programming Lang: Go Description : cross-platform serial library (Go library) go.bug.st/serial - A cross-platform serial port library for Go. I hope to maintain this package as part of Debian Go Packaging Team: https://salsa.debian.org/go-team/packages/golang-github-bugst-go-serial /Simon signature.asc Description: PGP signature
