Hey,

yeah, I’m totally there with you. I’m for sure one of the most old school ;-)

But nobody ever wants to use the T2 site donate button. Each day I spend
developing T2 I have no income. So now I try at least covering some T2
development costs via funny / fancy YouTube ;-)

As you prefer text and if the grub manual is not full enough with examples,
here is the copy of my vmware install:

set debug=video
insmod efi_gop
insmod efi_uga
insmod font
if loadfont ${prefix}/unicode.pf2
then
    insmod gfxterm
    set gfxmode=auto
    set gfxpayload=keep
    terminal_output gfxterm
fi

# Boot automatically after 30 secs.
set timeout=30
# By default, boot the GNU/Linux
set default=linux

# For booting GNU/Linux
menuentry "T2 Linux install" --id linux {
        set root=(hd0,gpt2)
        linux /boot/vmlinuz_4.10.1-dist root=/dev/disk/by-uuid/123-456-789 # 
/dev/sda2
        initrd /boot/initrd-4.10.1-dist.img
}

the by-uuid only work in T2 since a week or two, as I adapted the inited to 
include more u/dev stuff for this device links to be created early enough.

In the time I replied to all the email, I could however, indeed already written 
the iso argument generation shell code, .. :-/

Good night,

        René

On May 2, 2017, at 23:49, Chris <[email protected]> wrote:

> grub2 via shaky youtube videos... welcome to the new age...
> i really do miss the good'ol text only grub-legacy tutorials ;)
> 
> will take a look at it anyway and of course send patches as soon as
> i'm able to ;)
> 
> regards, chris
> 
> 
> 
> On Tue, 2 May 2017 23:29:54 +0200
> René Rebe <[email protected]> schrieb:
> 
>> Hi,
>> 
>> I did not write the “glue” code for grub2 isos just yet, I only used
>> it after installing the system.
>> 
>> The encrypted root config can be seen in the video link I posted:
>> 
>>      https://youtu.be/457zniNGVfU?t=33s
>> 
>> The powerpc grub2 iso glue is in trunk, architecture/powerpc/boot,
>> but it is entirely different from x86 based systems.
>> 
>> I will try to find time to code the x86 FAT glue sometime soon.
>> 
>> IIRC I also committed the start of a grub2 stone module, but that is
>> right now also only for the powerpc used case (the system I happened
>> to test-install that day).
>> 
>> In the meantime, patches are of course welcome ;-)
>> 
>>      René
>> 
>> On May 2, 2017, at 23:16, Chris <[email protected]> wrote:
>> 
>>> sounds fair
>>> 
>>> care to share your grub2 setup?
>>> seems to not make sense to work with grub-legacy if it will be
>>> replaced by grub2 soon anyway...
>>> 
>>> 
>>> On Tue, 2 May 2017 23:02:56 +0200
>>> René Rebe <[email protected]> schrieb:
>>> 
>>>> Hi,
>>>> 
>>>> because others wanted it. And I’m quite sure it worked at least a
>>>> decade ago.
>>>> 
>>>> It defaults to grub though, and that is what I build the last ISOs
>>>> with that worked for me in vmware, and actual hardware the other
>>>> week.
>>>> 
>>>> The next step will be to make grub2 the default option, I already
>>>> did this for powerpc.
>>>> 
>>>>    René
>>>> 
>>>> On May 2, 2017, at 22:59, Chris <[email protected]> wrote:
>>>> 
>>>>> so why include it in ./scripts/Config at all?
>>>>> 
>>>>> btw, i'm fine with grub ;)
>>>>> 
>>>>> 
>>>>> 
>>>>> On Tue, 2 May 2017 22:56:47 +0200
>>>>> René Rebe <[email protected]> schrieb:
>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> i’m for many reasons not interested in syslinux at all.
>>>>>> 
>>>>>> I will happily accept patches for whatever, but otherwise just
>>>>>> use grub, and on latest machines that means grub2.
>>>>>> 
>>>>>>  René
>>>>>> 
>>>>>> On May 2, 2017, at 22:51, Chris <[email protected]> wrote:
>>>>>> 
>>>>>>> from thomas' link:
>>>>>>> http://www.syslinux.org/wiki/index.php?title=Library_modules#Syslinux_Modules_by_Firmware_and_Architecture
>>>>>>> 
>>>>>>> For other Syslinux variants (PXELINUX, ISOLINUX) booting BIOS
>>>>>>> firmware, the second file, ldlinux.c32, needs to be manually
>>>>>>> added, just as the boot loader. Both files shall match the same
>>>>>>> version. For example, before building a new ISOLINUX image, two
>>>>>>> files are now needed: the isolinux.bin boot loader file, and the
>>>>>>> same auxiliary ldlinux.c32 file.
>>>>>>> 
>>>>>>> did not research it any further, but sounds like it could be the
>>>>>>> culprit... or not?
>>>>>>> 
>>>>>>> 
>>>>>>> On Tue, 2 May 2017 21:24:18 +0200
>>>>>>> René Rebe <[email protected]> schrieb:
>>>>>>> 
>>>>>>>> Hey,
>>>>>>>> 
>>>>>>>> I did not really build that recently. But ldlinux.c32 sounds
>>>>>>>> strange (is that syslinux?), if then I ever only used grub in
>>>>>>>> the last 10 years or so?
>>>>>>>> 
>>>>>>>>        René
>>>>>>>> 
>>>>>>>> On May 1, 2017, at 18:27, Chris <[email protected]> wrote:
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> forgot to mention, that i compiled the generic/minimal (no X)
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On Mon, 1 May 2017 18:22:35 +0200
>>>>>>>>> Chris <[email protected]> schrieb:
>>>>>>>>> 
>>>>>>>>>> hi list,
>>>>>>>>>> 
>>>>>>>>>> is the livecd feature supposed to work on 9.0?
>>>>>>>>>> 
>>>>>>>>>> 'cause i cant get it to run, compiled from the latest x64.iso
>>>>>>>>>> 
>>>>>>>>>> grub only shows the option to boot from hd and syslinux
>>>>>>>>>> freaks out about a missing ldlinux.c32 (ran inside a kvm
>>>>>>>>>> libvirt with ide drivers)
>>>>>>>>>> 
>>>>>>>>>> regards, chris
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> ----------------------------------------------------------- 
>>>>>>>>>> If you wish to unsubscribe from this mailing, send mail to
>>>>>>>>>> [email protected] with a subject of: unsubscribe
>>>>>>>>>> t2        
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> ----------------------------------------------------------- 
>>>>>>>>> If you wish to unsubscribe from this mailing, send mail to
>>>>>>>>> [email protected] with a subject of: unsubscribe t2        
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>> 
> 
> 

-- 
 ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
 http://exactcode.com | http://exactscan.com | http://ocrkit.com | 
http://t2-project.org | http://rene.rebe.de

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to