Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id 39567225F64 for <~alpine/users@lists.alpinelinux.org>; Thu, 25 Jan 2024 19:29:59 +0000 (UTC) Received: by mail-ej1-x629.google.com with SMTP id a640c23a62f3a-a2f79e79f0cso739923866b.2 for <~alpine/users@lists.alpinelinux.org>; Thu, 25 Jan 2024 11:29:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=poughkeepsieschools.org; s=google; t=1706210996; x=1706815796; darn=lists.alpinelinux.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=WcHXRUGVn5a1pQ1odLf27m8G/IxFOZZd1W9dNncFyaQ=; b=E5/MNnEZhH0Cyg7x312XUMGoN1ONN8ZUSEdl4tlXrnEagyXnNmAjaN/cfFjaGBaDF8 VFI036whBdv47O2koBCgRLWWH/xIEkHoxbtYZZ4yIHVv6HEGYJ6sVUSUhmI9d+Z8MNom 9BgqT/HLb6XrFJaUwouApVftUhSBu1y8L3LywmddKv8F43CDwgen5Fw4LRw30Gx8hYp5 WUi057Rah+wkGoMw0OTB5cEt9T+AK0+mqbcxJm01R1qK0W93qMIyQZuL7N3POJtNsQKo whnx/kzbM2EvTq/U8vSwmnIuKETgbpNazNaBwiP1nV5Z8s5Atq0KHxosIDdV0T8g+hYL vQIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706210996; x=1706815796; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=WcHXRUGVn5a1pQ1odLf27m8G/IxFOZZd1W9dNncFyaQ=; b=d+vIIYCyzRU0oDXuUxj2inMIGkNvvOxUBJU5IlAznPYZ4IpsPQeGTWzja0UP7VYJ9W GFuvCDCvEFbiT3FQyTd0tL9C1BckzUFowuJll37BfcAwSXndvXRu8SsSoPhME06W2JnG 8TNSjGp9SDNGCJoxjqeCRS5tfby+UtPyFVNjYQN1VoYrJdPppH0Sacibbd5XMLU3Pxn0 VpXL5bAiavycS6RUlGheCz1N9f3ce5JPI65YBMQM3NKs1qPvBioNmPa1oTDa23s4ECic +5sK8RbwxkIhjoY3RGfzxmT5gnsoDyZPKQSq2ttTFnGPcngP9X6ZfX3vtLf/bQILTTk0 fnWA== X-Gm-Message-State: AOJu0YxoRyELDSOHldfKsUcdJP6FUBK29lZ0cxDvthp7sjLZMkkp4eDf irFx/Eux1Q5GXdlQy/sAZ8JyCWHb+0r9zt7pvRVCkmqKVux9x7qKnAYyZh43W7Wq++iBvnb743t DrpnruUBa1uPHBeEdbTsBagoDqJXPb6dVR4g6HODD66EeO46s X-Google-Smtp-Source: AGHT+IGvA5nNb9Kjd8mjjylVDJ7wehnyXGQ7Td2s5fNQUNgnWk3aznLFeO1yqoaGZOkerrCyH6BiPWQVotNmmjerTwA= X-Received: by 2002:a17:906:758:b0:a30:dfa9:87ba with SMTP id z24-20020a170906075800b00a30dfa987bamr45479ejb.53.1706210995816; Thu, 25 Jan 2024 11:29:55 -0800 (PST) MIME-Version: 1.0 References: <9f76a9108e2ac6d8cda76035c695a6acdb6aba01.camel@riseup.net> In-Reply-To: <9f76a9108e2ac6d8cda76035c695a6acdb6aba01.camel@riseup.net> From: Brian Cook Date: Thu, 25 Jan 2024 14:29:43 -0500 Message-ID: Subject: Re: vultr alpine linux-lts-dev cannot boot.. To: ~alpine/users@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="000000000000515eb3060fca34d3" --000000000000515eb3060fca34d3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable vultr does not allow ROOTFS or BOOTFS to be xfs.. I was able to boot from the 3.19 iso see my vda1 and vda3.. also alpine with ext4 uses extlinux not grub.. I had no vmlinuz-lts-dev or vmlinuz-lts kernel and no initramfs-lts-dev or initramfs-lts.. I could get network working but coping the files back into vda3.. wouldn't ever boot I could edit the extlinux.conf and got the menu and items to appear, but nothing would boot or work.. I rsync'd out of the 3.19 iso all the data and had to reinstall :( usually I export ROOTFS=3Dxfs export BOOTFS=3Dxfs setup-alpine (with or without answer file.. ) but vultr gives the ldlinux.c32 error and wouldn't boot.. not formatting at xfs got the install to work correctly and linux-lts (not dev) seems to work.. now just putting things back.. On Thu, Jan 25, 2024 at 1:56=E2=80=AFPM Ralf Mardorf wrote: > On Thu, 2024-01-25 at 12:08 -0500, Brian Cook wrote: > > I had a usb utility that would boot a linux system from the usb using > > the kernel on the usb.. but cannot find the name of it.. > > Hi, > > for this bad practice you need a bootloader on the USB device and a > kernel. You can boot into a kernel, that does not belong to a Linux > install's root directory. For example, if you have got a Linux dual boot > machine, you can boot into the kernel from one and the root directory of > the other install. This usually works without issues, but it's not > really safe to do so. > > When using a systemd based Linux distro you can use systemd-nspawn from > another systemd Linux. This is safe, but doesn't allow to fix > everything. > > If a distro isn't based on systemd or you need to fix something that can > not be done when using systemd-nspawn, then chroot is the way to go. > > In short, even if there are several possibilities that can work, > basically a chroot is often what it will come down to in the end. > > OTOH sometimes you only need to mount your Alpine Linux and edit > something. You can even run apk from another Linux and use the "--root" > option. > > apk fix --root /mnt/point/of/alpine/ package_name > > Regards, > Ralf > --=20 Network Administrator Poughkeepsie City School District SMS & Mobile: (202) 810-5827 twitter.com/bcookatpcsd "If you cannot explain it simply, you do not understand it well enough ." --000000000000515eb3060fca34d3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
vultr does not allow ROOTFS or BOOTFS to be xfs.= . I was able to boot from the 3.19 iso see my vda1 and vda3..

also alpine with ext4 uses extlinux not grub..=C2=A0

I had no vmlinuz-lts-dev or vmlinuz-lts kernel and no initramfs= -lts-dev or initramfs-lts.. I could get network working but coping the file= s back into vda3.. wouldn't ever boot

I could edit the extlinux.conf and got the menu and items to appear,= but nothing would boot or work..

I rsync'd out= of the 3.19 iso all the data and had to reinstall

:(

usually I

export ROOTFS=3Dxfs
<= div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-siz= e:small">export BOOTFS=3Dxfs

setup-alpine

(with or without answer file.. )

but vultr gives the ldlinux.c32 error and wouldn't boot.. n= ot formatting at xfs got the install to work correctly and linux-lts (not d= ev) seems to work..

now just putting things back..<= br>



On Thu, Jan 25, 2024 at 1:56=E2=80=AFPM Ra= lf Mardorf <ralf-mardorf@rise= up.net> wrote:
On Thu, 2024-01-25 at 12:08 -0500, Brian Cook wrote:
> I had a usb utility that would boot a linux system from the usb using<= br> > the kernel on the usb.. but cannot find the name of it..

Hi,

for this bad practice you need a bootloader on the USB device and a
kernel. You can boot into a kernel, that does not belong to a Linux
install's root directory. For example, if you have got a Linux dual boo= t
machine, you can boot into the kernel from one and the root directory of the other install. This usually works without issues, but it's not
really safe to do so.

When using a systemd based Linux distro you can use systemd-nspawn from
another systemd Linux. This is safe, but doesn't allow to fix
everything.

If a distro isn't based on systemd or you need to fix something that ca= n
not be done when using systemd-nspawn, then chroot is the way to go.

In short, even if there are several possibilities that can work,
basically a chroot is often what it will come down to in the end.

OTOH sometimes you only need to mount your Alpine Linux and edit
something. You can even run apk from another Linux and use the "--root= "
option.

apk fix --root /mnt/point/of/alpine/ package_name

Regards,
Ralf


--
Network Administrator
Poughkeepsie City School District
SMS &= Mobile: (202) 810-5827
twitter.com/bcookatpcsd

"If you cannot explai= n it simply, you do not understand it well enough."
--000000000000515eb3060fca34d3--