← Back to team overview

torios-dev team mailing list archive

Re: (Was Re: OBI update) New Testing ISO!

 

Hi Nio,
Thanks for the detailed notes!!
(inlines below)

On 01/20/2018 02:45 PM, Nio Wiklund wrote:
> Den 2018-01-20 kl. 18:43, skrev Israel:
>> ..
>
> Hi Israel,
>
> I tested the new iso file with my Toshiba laptop from 2013, that I
> have been using for development and testing for several years.
>
> 0. The size is far above CD size but still within 1 GB (so it can be
> installed in a 1 GB USB pendrive or memory card.
>
Yes, I know it is.  This is because I simply built things, I did not try
to optimize for now.
> 1. Still based on Debian Jessie and the linux kernel 3.16.
Yes.  It has the latest updates, so Meltdown/Specter should not be an
issue (though the fixes may cause some issues as you may already be aware).
>
> 2. mkusb is back in the live system. Are also other tools back (that
> were stripped to make it fit within CD size)? What about suggesting
> the Synaptic Package Manager?
>
I am not sure what other tools were stripped.
> 3. Installing
>
> a. I first started the default way, but when I found that it would
> install to the whole drive, I said 'no' and then tried to select
> advanced mode. It failed (nothing happened). This is a bug.
>
Weird.  This is a big bug.  I will look into this.  It should be a
simple fix (I hope)
> Then I quit the installer and restarted it. Now I could select
> advanced mode.
>
> b. Installing the bootloader I presume: The window for selecting
> target device does not tell what is to be installed (I think it used
> to tell that it was about the bootloader, now only 'select device -
> and continue'). After selecting it tells what it is all about, but
> that is too late :-P
>
Hmmm... ok this should also be an easy fix.  The text of the dialog
should give advice on which device to install to.  But I may have made
things less clear.
> 4. Installed system
>
> a. Rebooting brought me to the grub menu but after some output during
> the boot sequence the system came to a black screen with a flashing
> cursor.
>
This is odd.  not sure what this issue is... it may be related to the
sudo issue below/
> SysRQ REISUB did not solve the problem. I tried with the older kernel,
> still no luck. But I could start a screen session via ctrl+alt+F1.
>
> I stayed with the non-pae kernel.
>
> b. sudo does not work in text screen: 'sudo: /usr/bin/sudo must be
> owned by uid 0 and have setuid bit set.'
>
This problem may have happened because this time I ran ISOmaker via sudo
(IIRC) and so sudo may have been owned by my VM sudo... so... that is a
problem, but one I think I can remedy fairly easily.
> c. I could boot into recovery mode, but from there I could not start
> the graphics. I think the problem is that there is no graphics driver
> for my Toshiba :-(
>
can you give me the dmseg for that, as well as the install log!  Debian
is different than Ubuntu and does not automatically include all the
extra firmware... I could (perhaps) just install it all and avoid
this... but I have a script that *should* take care of this... perhaps
it did not, though..
> d. Continuing testing I found that some but not all programs that
> normally need superuser permissions (sudo) work, when logged in as the
> standard user (and without sudo). (I don't think ToriOS was like this
> before.)
No... this is likely related to building from sudo... sorry I will
correct this.
>
> Second test
>
> I tried again, this time installing at the basic OBI level (to the
> whole drive selecting all default actions (for example to get the PAE
> kernel and check for updates), but selecting Stockholm time zone and
> Swedish language and trying to understand a working keyboard, not easy
> :-P
>
What can make this easier than it is now?  How was the old way less
difficult?  What do you suggest to make this much easier?
> Installing the PAE kernel is very slow.
>
Yes... as usual.
> This was more successful :-)
>
whew :D
> I arrived at the desktop and the menus are working. But sudo is borked
> like during the first attempt. Synaptic is in the menus, but does not
> work (maybe because of problems with sudo).
>
This is a big issue, and I will rebuild the ISO to fix things.
>
> I changed many things, so I cannot tell exactly what caused the failed
> in the first case. Maybe the non-pae kernel, maybe something else, for
> example check for updates or the default method (installing to the
> whole drive). Or maybe there was some temporary glitch during my first
> attempt.
>
This may be... OBI is pretty complicated, and while I understand most of
it, there are still parts of your code that are mysterious to me :)
> I might be able to find out better later on, but I am sending this
> feedback now.
>
Thanks for the quick response... it give me some major areas to work on
and test.
> Best regards
> Nio


-- 
Regards



Follow ups

References