From: jacksprat <picamanic@gmail.com>
To: voidlinux <voidlinux@googlegroups.com>
Subject: Re: Trying to Install on USB drive using GRUB
Date: Tue, 25 Jun 2019 09:59:54 -0700 (PDT) [thread overview]
Message-ID: <778c2f0c-ab30-426d-b057-203e79e2213d@googlegroups.com> (raw)
In-Reply-To: <CAHpAuDGcu2ZEToeJPN6Z+cQmmf466-d3nt-pA=vyNPGHnKMr3g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1733 bytes --]
Lilo? Ii haven't given up trying to get grub.cfg right. here is a fragment
#
menuentry 'Void GNU/Linux 4.18.17 [sda1]' {
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
echo 'Loading Linux 4.18.17_1 ...'
linux /boot/vmlinuz-4.18.17_1 root=/dev/sda1 ro
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-4.18.17_1.img
}
It is the "set root" line that I suspect is wrong, but if "msdos1"=1st
partition, why do both "hd0" and "hd1" fail? Close..
On Tuesday, June 25, 2019 at 4:40:28 PM UTC+1, space pudim wrote:
>
> El mar., 25 de jun. de 2019 16:34, jacksprat <pica...@gmail.com
> <javascript:>> escribió:
>
>> Well, I tried install to the identical pen drive that booted Void Linux
>> Live, and repeated what I did to grub-install, and the resultant USB drive
>> booted! However, the boot sequence died running the initramfs, just after
>> running dracut on the first partition of my HD [/dev/sda1]. I have aleady
>> seen my error in the grub.cfg file [scream]. This is going too be hard
>> work, but worth it in the end [?]. Just got to remember how grub.cfg is
>> coded..
>>
>
> Maybe LILO is still an option?
>
>>
--
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To post to this group, send email to voidlinux@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/778c2f0c-ab30-426d-b057-203e79e2213d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 3239 bytes --]
next prev parent reply other threads:[~2019-06-25 16:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 9:25 jacksprat
2019-06-25 9:33 ` Igor Fontana
2019-06-25 10:33 ` jacksprat
2019-06-25 10:40 ` Igor Fontana
2019-06-25 11:07 ` jacksprat
2019-06-25 12:56 ` Igor Fontana
2019-06-25 13:38 ` Jeff Pohlmeyer
2019-06-25 13:53 ` jacksprat
2019-06-25 13:58 ` Igor Fontana
2019-06-25 14:07 ` jacksprat
2019-06-25 14:11 ` Igor Fontana
2019-06-25 14:25 ` Jeff Pohlmeyer
2019-06-25 14:37 ` jacksprat
2019-06-25 13:46 ` jacksprat
2019-06-25 15:34 ` jacksprat
2019-06-25 15:40 ` Igor Fontana
2019-06-25 16:59 ` jacksprat [this message]
2019-06-25 17:23 ` jacksprat
2019-06-25 18:32 ` Jeffrey Sheinberg
2019-06-26 5:46 ` jacksprat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=778c2f0c-ab30-426d-b057-203e79e2213d@googlegroups.com \
--to=picamanic@gmail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).