torios-dev team mailing list archive

[Nio Wiklund <nio.wiklund@xxxxxxxxx>]

Hi Israel,

Making persistent live drives:

I can modify mkusb according to your suggestion and make it more general
- but ToriOS built on Ubuntu boots slightly differently from standard
Ubuntu and the Ubuntu flavours (Lubuntu ... Xubuntu), so there must
still be some special checks and actions. This might be the case also
with ToriOS built on Debian.

Anyway, I think it can be fixed without too much problems, but I should
wait until it is decided which way ToriOS will be built - based on
Ubuntu or based on Debian. I mention it now, so that we can help each
other to remember this issue.

Best regards
Nio

Den 2016-01-24 kl. 15:10, skrev Israel:
> Hi Nio,
> (inlines)
> On 01/24/2016 12:45 AM, Nio Wiklund wrote:
>> ...
>> Please start to treat the ISO file with isohybrid again!
>>
>> You forgot it with the latest Ubuntu based daily ISO and you forgot it
>> with this Debian ISO.
> I didn't forget... however that binary moved into a different package in
> xenial :(
> The script was running the command the whole time, but isohybrid didn't
> exist.
> So.... Now I fixed the script to install the xenial package name, and
> the next ISO will have it.
> Sorry about that.
>> Extra comment:
>>
>> Otherwise mkusb won't create working live-only pendrives.
>>
>> @Ali, see this point:
>>
>> If you will decide to base the released version of ToriOS on Debian, I
>> will modify mkusb in order to make persistent live drives. Persistence
>> works for Debian in a different way from Ubuntu and Ubuntu based
>> distros, and ToriOS is identified as based on Ubuntu (in mkusb).
> I use
> something like
> VAR=$(uname -v)
> if [ "${VAR/Ubuntu}" != "${VAR}" ]
> then
>   echo "Ubuntu based"
> elif [ "${VAR/Debian}" != "${VAR}" ]
> then
>   echo "Debian based"
> else
>   echo "Not Ubuntu OR Debian"
> fi
>>
>>>
>> Yes but uname -a tells me both (on the same line). It is i586, confirmed
>> by running with the Pentium M processor.
> Oh... odd.... not sure about that.
> 
>> ....
>> *checkbox bug discussion*
>> I do not expect that we will get this bug fixed. So I recommend that you
>> change the text to
>>
>> 'Click on this line to get it checked, if you are ready to go'
> I already did.  I think I fixed it in zmktbl too, and all places in OBI.
> I could be mistaken, but I did try to find them all.
>> There is probably a *similar issue with zmktbl*, that can be solved in a
>> similar way. I have not tested it, but I remember that there is a zenity
>> window with a checkbox there too.
>>
>>
>>>> 2. A start job is running ... (waiting for 90 s: systemd problem?)
>>> This is a systemd issue.  Basically the /etc/fstab had the cdrom (sr0)
>>> in it from the Debian Installer.  Then, when OBI recreates the fstab we
>>> get a funky thing where the installed OS is looking for a non-existent
>>> device for like 90 seconds.
>> I hope you will fix this issue, because it will annoy end users. But I
>> know almost nothing about systemd, so I can't help much.
> 
>> 4. The colours of the prompt in the terminal window are not green and red.
>>> :(
>>> I am not sure if I create the bashrc correctly in Debian, or possibly it
>>> doesn't get fully copied?  Not sure about that one.
>> This is a minor issue :-)
> Yes, one that can be dealt with later... or it might actually end up
> just working at some point :)
> 
>> 3. I tried again and installed a third time, (to a third ext4
>> partition), making sure I installed the 'PAE kernel'. This time the
>> installed systems grub did not display the previous versions as lines in
>> the grub menu. But it worked to run
>>> I think this is a problem with the bug.
>> It is strange that it appeared the third time but not the second time.
>> We can say that it is has low priority compared to other bugs,
>> particularly if other people won't complain about it.
> Well, an issue that seems to have happened, is in the install pae script
> it updates GRUB, which hasn't yet been installed, so there might be some
> issues from that.  But I have since fixed it.
> 
>