torios-dev team mailing list archive

[Cinque Port Computers <jackdtrice@xxxxxxxxx>]

Hi Nio,
I'm getting around that 1m30s waiting problem by commenting out the swap and cdrom entries in /etc/fstab temporarily.
Hi Israel,
I did try to install Opera via firstrun.  I'll try a different browser and report back.
Cheers,JackT.


> To: israeldahl@xxxxxxxxx; torios-dev@xxxxxxxxxxxxxxxxxxx; jackdtrice@xxxxxxxxx; ruzekle@xxxxxxxxx
> From: nio.wiklund@xxxxxxxxx
> Date: Sun, 24 Jan 2016 07:45:16 +0100
> Subject: Re: [Torios-dev] Debian ISO
> 
> Hi again Israel,
> [inline]
> Best regards
> Nio
> 
> Den 2016-01-24 kl. 02:32, skrev Israel:
> > Hi Nio
> > (inlines)
> > On 01/23/2016 02:37 PM, Nio Wiklund wrote:
> >> Den 2016-01-22 kl. 01:59, skrev Israel:
> >>> ...
> >> Hi Israel and the other developers :-)
> >>
> >> I have some time now for testing, first in my Toshiba with an Intel i5
> >> processor and 4 GB RAM.
> >>
> >> Live:
> >>
> >> 1. You forgot to treat the iso file with isohybrid, so I had to do that
> >> in order to make it work when flashed with mkusb into a pendrive.
> 
> 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.
> 
> 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).
> 
> >> 2. The information about the version according to
> >>
> >> uname -a
> >>
> >> is a little confusing (i586 or i686?). It does not handle more than 2 GB
> >> RAM well, which indicates a non-pae kernel. I will check it in my IBM
> >> Thinkpad with an Intel Pentium M later.
> > i586 is non PAE i686 is PAE
> 
> Yes but uname -a tells me both (on the same line). It is i586, confirmed
> by running with the Pentium M processor.
> 
> >> Installing:
> >>
> >> 1. At the basic OBI level: The window 'Select device - and continue' is
> >> too small (should be wider to accomodate all the text)
> > I e-mailed you about this already, but here is the general info:
> > 
> > I am working to dynamically calculate the size of text and size the
> > window accordingly.
> > I have tested this and after a few edits I now have a working version
> > (at least on my VM)
> 
> :-)
> 
> >> 2. For some reason the SSD drive connected via eSATA is shown twice in
> >> this menu (minor bug but confusing).
> > not sure where to look for this.... that is definitely part of your
> > original OBI code somewhere... I might be able to track it down....
> >> 3. There is no box to check in the 'Final warning' window. But you can
> >> click on the text 'Check this box ...' - maybe it should be changed to
> >> 'Click on this line to get it checked, if you are ready to go'. I think
> >> this is a zenity bug (or bad cooperation between zenity and jwm).
> > I think this is either a Zenity bug OR a bug in the Numix gtk theme, OR
> > it is another 'feature' Gnome has built into GTK :P
> 
> 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'
> 
> 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.
> 
> >> Installed system:
> >>
> >> 1. Apparmor init failed for me too.
> > It fails at first, but then gets things right.  I think apparmor is an
> > upstart based thing... not sure what it is for but it is in the standard
> > Ubuntu minimal or standard packages.
> 
> Apparmor is for security. See
> 
> https://wiki.ubuntu.com/AppArmor
> 
> >> 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.
> 
> >> 3. The tick boxes in ztweaks is missing, you have to click on the white
> >> space where it is supposed to be in order to activate it. The same
> >> zenity bug as before. In this case it does not work to click on the
> >> text, so it is really confusing.
> > I did change some of the text in other dialogs... but I am not sure with
> > this.  We will have to test multiple themes to check this out.  Maybe
> > file a bug with zenity/gtk/numix or whatever is causing the problem.
> 
> Maybe we simply skip ztweaks (because I don't think we will get this bug
> fixed. I have not enough time for it).
> 
> >> 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 :-)
> 
> >> 5. The panel icon for audio is bad, or should I say, the app behind it
> >> does not work correctly. I cannot open the mixer. I have to select
> >> preferences and show slider, otherwise it is mute. 'Open mixer' just
> >> flashes by - does not leave anything open.
> > as I told Jack, alsa-utils was not installed... but will be in the new
> > ISO which will be ready when OBI is ready.
> 
> :-)
> 
> >> 6. The wired network works. I can use ssh. But I have to 'sudo ping'
> >> (maybe this is a feature of debian, different from ubuntu).
> > hmm... not sure if that is a feature or a bug.  They are very similar
> > and VERY different.  But I like this ToriOS version it is the best of
> > both worlds, IMO
> >> Installing:
> >>
> >> 1. At the advanced OBI level: The checkbox is missing (the same zenity
> >> bug as before).
> >> 
> >> 2. I tried to install the PAE kernel this time. But
> >> uname -a
> >> and
> >> free -m
> >> seem to display the same as before. Are you sure that there is a
> >> difference - that different kernels are installed?
> > This IS a bug.  Thank you.  I think this will be fixed in the next version.
> > The PAE kernel installer should also leave a log file in
> > ~/pae-kernel-install.log
> > For us to check more.
> 
> :-)
> 
> >> 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.
> 
> >> sudo update-grub
> >>
> >> to get them.
> >>
> >> Still the same result from uname -a and free -m, so I think it is the
> >> same kernel all the time.
> >>
> >> Pentium M:
> >>
> >> *. The live system and the installed system work in the IBM Thinkpad
> >> with an Intel Pentium M, and the the kernel is a non-pae kernel.
> >>
> >> It seems that we get a non-pae kernel also when we select to install a
> >> PAE kernel (in computers allowing it). So [I am almost 100% sure] this
> >> is a bug.
> >>
> >> -o-
> >>
> >> There are some bugs, but considering the short time you have been
> >> converting ToriOS to debian, I think you have done a very good job. Most
> >> things work :-)
> > Thanks Nio.
> >> Best regards
> >> Nio
> > 
> > 
> 
> 
> -- 
> Mailing list: https://launchpad.net/~torios-dev
> Post to     : torios-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~torios-dev
> More help   : https://help.launchpad.net/ListHelp