On 2024-11-14 10:31:46, Michael Stone wrote:
> On Tue, Nov 12, 2024 at 11:10:54PM +0100, Iustin Pop 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
On Thu, Nov 14, 2024 at 04:39:28PM +0100, Iustin Pop wrote:
Indeed. But even the comment, by itself, I think raises a question - why
do we (still) do this?
Because there's very little incentive to change it.
On Tue, Nov 12, 2024 at 11:10:54PM +0100, Iustin Pop 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 situ
On Tue, 2024-11-12 at 23:10 +0100, Iustin Pop wrote:
> 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. Debia
On Nov 12, Iustin Pop wrote:
> 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
Agreed.
--
ciao,
Marco
signature
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
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 direc
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 symlink
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 h
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
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
Geert Stappers writes:
> Chesters fence
Chesterton's?
Bjørn
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 d
13 matches
Mail list logo
