Received: from mail-lj1-f174.google.com (mail-lj1-f174.google.com [209.85.208.174]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id EA09E782D55 for ; Fri, 24 Jan 2020 15:16:16 +0000 (UTC) Received: by mail-lj1-f174.google.com with SMTP id x14so501339ljd.13 for ; Fri, 24 Jan 2020 07:16:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=e5BoVS28Ksu1ZS9k580gcG5bAB75dRNvAVtmp0xS9hU=; b=ZZzc4v0Tm5kStUGMCoE6jb6uc7Jb+N6eckZv1dYX/VGybUnIgboR5K69Dydmbe9wph 8Gyt8lkopfXRVgyryaQg5Pu9WcM1s3pMP9prikOgYauG1PUhj0jqcH8axFmbWeA1lieS +fG5W//I4XAXUVaEwyNZiLDBUp7jlWV+EuIqnoYGuxjfo2Ug34VKURgu0IHNGk1aZ0vB NGoCpaaUrRHi9APKFnQtvgn37GKp+2dJvovqd/xCG28i9BNAxGs3Fz6/S4y2e8QZUNdd Cgf2nqX4kHy8+2aeuZOg9T/pak1R0ZAergV9sIjfl+ZdP06mYB1mIIJdu7OcgKmuJBlB fWPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=e5BoVS28Ksu1ZS9k580gcG5bAB75dRNvAVtmp0xS9hU=; b=Ns14PZKixtBh/ZBiC5UA49e0kq62JBX6BPZfk5+Elh01SBBtKS8jvhgcr/y5tAmY9c 2lpOj1onc2qoraXdMKEqkwDIJ7j3fArpw1mfLUHcaAs5Xwinu+RrlWpe2OVqQ2RayQlP TGQwHYTcjZ6ePDWxFOn2THtGsT88tP/M1tpDh3ndN7IzyNADIq1yxdZmNXWRQDaA58Kz NActOP0y93vFW8tnt86ltvPnncuh6igChyUtIdH16womOYdhQ/MFyk5phn06JNRFd2J8 ehYFd9c14V45AP819jSbZ8wsoZzW+SX+73lxygAzopLzkvc5rrLnsbhJVFOYPahbiUxD vgAg== X-Gm-Message-State: APjAAAWNSzVTnOBykxBa1qZiPNOwyKeZANrhHJ8FRc814p3Eq/Qk0RTh 0ttICGnIb/I5gTs/FeriyPqqdHSnsqblXXestuA= X-Google-Smtp-Source: APXvYqyR0TqwlfS1D+q1buLiPz0BisStW4QZJRNowAcnHk7TrFH67wzsUv855dtDbZr6sJKTPe2Og2YM6pgCExjns6A= X-Received: by 2002:a2e:884c:: with SMTP id z12mr2590469ljj.55.1579878976391; Fri, 24 Jan 2020 07:16:16 -0800 (PST) MIME-Version: 1.0 References: <20200124132726.1e33842f@ncopa-desktop.copa.dup.pw> <20200124160211.782fe2ec@ncopa-desktop.copa.dup.pw> In-Reply-To: <20200124160211.782fe2ec@ncopa-desktop.copa.dup.pw> From: PICCORO McKAY Lenz Date: Fri, 24 Jan 2020 11:16:05 -0400 Message-ID: Subject: Re: manual install boot process of setup-disk does not work To: Natanael Copa , Wolf Cc: alpine-user Content-Type: multipart/alternative; boundary="0000000000002d0c5e059ce43dda" --0000000000002d0c5e059ce43dda Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I agree with you in all, thanks Natanael i'll update wiki pages about partition only installation now! Wolf give me tips about the grub process: well, arch linux today are a pain in the fuck*g ass.. he give me a arch wiki page.. BUT here are a problem.. grub are not in default image! so if we do not have networking we don't able to make it install able if i have different arch (x86 vs x64) already installed! procedure to make alpine main os if previous linux are installed will be very complicated to gain new users.. if grub are not in the media image! wifi modules are a pain remember that! modem are not in hotpost mode at install ! as example: fi grub are installed and can added new entry to the installed linux, the new user can boot their older linux and copy paste to alpine partition the proper files.. making the alpine grub install the main grub boot, due older linux was in bios mode and grub will perfom a UEFI boot.. another case .. install both alpine and another linux or freebsd or osx in same disk only alone partitions.. and want make alpine main os to manage the boot process.. of course i not need networking in alpine, just boot and that's all.. this cannot be possible due there's no grub in the media.. only for x86 and x64... arm ones does not have that option.. there's more cases, the only problem: grub need packages are not in default images! El vie., 24 de ene. de 2020 a la(s) 11:02, Natanael Copa ( ncopa@alpinelinux.org) escribi=C3=B3: > On Fri, 24 Jan 2020 10:52:13 -0400 > PICCORO McKAY Lenz wrote: > > > El vie., 24 de ene. de 2020 a la(s) 08:27, Natanael Copa ( > > ncopa@alpinelinux.org) escribi=C3=B3: > > > > > On Thu, 23 Jan 2020 09:32:48 -0500 > > > > > > seems manually make boot able the installed system does not work with > > > > setup-disk?, > > > > > > Thanks natanael, that works for x86 and x64 BIOS only computers now: > > > > > I think you need to install the bootloader yourself to MBR. > > > With syslinux its something like `dd if=3D/usr/share/syslinux/mbr.bin > > > of=3D/dev/sda`. With grub I don't know. > > > > > BUT why setup-disk does not make it if we specified the install disk > > by "DEFAULT_DISK=3Dsda > > setup-disk -q -m sys /mnt"??? > > > > The reasoning was that if users use `setup-disk /mnt` the user will > also know how to install the bootloader. There are just too many things > that can go wrong is setup-disk tries to do it, so I never bothered to > do anything about it. > > DEFAULT_DISK !=3D boot disk. > > -nc > > > i need that clarifications, to property make wiki documentation (very > weak > > in that) > > Seems that are very important to users to able to install if there's > > already a prevously linux instalation in their disk! > > exactly, and we dont want setup-disk to remove the other OSes in case > of dualbooting. And we dont want the script to start try figuring out > whatever bootloader is used from before or how to also boot windows etc. > > Better let user install boot loader. > > > please seems you need to assist me to make available to make it work > > with grub ! that methos does not work with UEFI computers! > > currently the setup-disk uses syslinux for BIOS boot and grub for UEFI. > I'm not sure the code is there for install grub in BIOS mode. > > > taking in consideration that users commonly does not install alpine > > linux alone in a disk for x86 and x64 machines right? > > I thiknk setup script also works for ppc64le, but to be honest, I don't > know. > > > > > > > > -nc > > > > > --0000000000002d0c5e059ce43dda Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I agree with you in all, thanks Nata= nael i'll update wiki pages about partition only installation now!

Wolf give me tips about the grub process: well, arch l= inux today are a pain in the fuck*g ass.. he give me a arch wiki page..

BUT here are a problem.. grub are not in default= image! so if we do not have networking we don't able to make it instal= l able if i have different arch (x86 vs x64) already installed!

procedure to make alpine main os if previous linux are in= stalled will be very complicated to gain new users.. if grub are not in the= media image! wifi modules are a pain remember that! modem are not in hotpo= st mode at install !

as example: fi grub are insta= lled and can added new entry to the installed linux, the new user can boot = their older linux and copy paste to alpine partition the proper files..=C2= =A0 making the alpine grub install the main grub boot, due older linux was = in bios mode and grub will perfom a UEFI boot..

another case .. install both alpine and another linux or freebsd or osx = in same disk only alone partitions.. and want make alpine main os to manage= the boot process.. of course i not need networking in alpine, just boot an= d that's all.. this cannot be possible due there's no grub in the m= edia.. only for x86 and x64... arm ones does not have that option..

there's more cases, the only problem: grub need = packages are not in default images!

El vie., 24 de ene.= de 2020 a la(s) 11:02, Natanael Copa (ncopa@alpinelinux.org) escribi=C3=B3:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 24 Jan 2020 10:52:= 13 -0400
PICCORO McKAY Lenz <mckaygerhard@gmail.com> wrote:

> El vie., 24 de ene. de 2020 a la(s) 08:27, Natanael Copa (
> ncopa@alpin= elinux.org) escribi=C3=B3:
>
> > On Thu, 23 Jan 2020 09:32:48 -0500
> >
> > seems manually make boot able the installed system does not work = with=C2=A0
> > > setup-disk?,=C2=A0
> >
> > Thanks natanael, that works for x86 and x64 BIOS only computers n= ow:=C2=A0
>
> > I think you need to install the bootloader yourself to MBR.
> > With syslinux its something like `dd if=3D/usr/share/syslinux/mbr= .bin
> > of=3D/dev/sda`. With grub I don't know.
> >=C2=A0
> BUT why setup-disk does not make it if we specified the install disk > by "DEFAULT_DISK=3Dsda
> setup-disk -q -m sys /mnt"???
>

The reasoning was that if users use `setup-disk /mnt` the user will
also know how to install the bootloader. There are just too many things
that can go wrong is setup-disk tries to do it, so I never bothered to
do anything about it.

DEFAULT_DISK !=3D boot disk.

-nc

> i need that clarifications, to property make wiki documentation (very = weak
> in that)
> Seems that are very important to users to able to install if there'= ;s
> already a prevously linux instalation in their disk!

exactly, and we dont want setup-disk to remove the other OSes in case
of dualbooting. And we dont want the script to start try figuring out
whatever bootloader is used from before or how to also boot windows etc.
Better let user install boot loader.

> please seems you need to assist me to make available to make it work > with grub ! that methos does not work with UEFI computers!

currently the setup-disk uses syslinux for BIOS boot and grub for UEFI. I&#= 39;m not sure the code is there for install grub in BIOS mode.

> taking in consideration that users commonly does not install alpine > linux alone in a disk for x86 and x64 machines right?

I thiknk setup script also works for ppc64le, but to be honest, I don't=
know.

>
>
> > -nc
> >=C2=A0

--0000000000002d0c5e059ce43dda--