Re: [Torios-dev] ToriOS ISO considerations
On 02/04/2018 09:45 AM, Nio Wiklund wrote:
> Den 2018-02-03 kl. 00:48, skrev Israel:
>> On 01/30/2018 12:23 PM, Nio Wiklund wrote:
>>> Den 2018-01-30 kl. 19:15, skrev Israel:
On 01/30/2018 02:55 AM, psutton wrote:
>
> On 27/01/18 13:07, Nio Wiklund wrote:
>> Den 2018-01-26 kl. 23:21, skrev Israel: ...
>>>
>>> Hi Israel,
>>>
>>> You should be able to let it boot into a text screen, where you can
>>> use a dialog text menu for the alternatives. One alternative can be to
>>> run startx (providing the necessary program packages are installed.
>>>
>>> See for example this link (scroll down and you will find some dialog
>>> menus),
>>>
>>> https://help.ubuntu.com/community/Installation/UEFI-and-BIOS/stable-alternative
>>>
>>>
>>>
>>> Best regards
>>> Nio
>>
>> Hi all,
>>
>> My testing of this text-mode-menu has not gone extremely well. But I
>> have been using the time to consolidate OBI code further into more
>> common functions which provide more error checking, and logging. I have
>> used some of the code from ISOmaker (which is well tested and I have
>> used countless times, and improved over time) to re-implement things
>> that I had done in OBI in an earlier time when my understanding of the
>> chroot and shell scripting was much less than it is now.
>>
>> So currently I am refining OBI further. Nio, if you want to send me a
>> simple way you boot into a terminal logged in, and then launch x on the
>> appropriate tty I would appreciate your added input here. I have done
>> these things in a few ways, but do not have a completely adequate
>> solution in place (so I have reverted to starting X by default)
>>
>> Once I have tweaked the last bits (I have been testing and tweaking the
>> code a lot recently) to fully adapt things, and make sure everything is
>> using the new functions properly I will upload the ISO.
>>
>> Sorry this has taken so long, but I've needed to do this for a while, to
>> make OBI more stable. I have found various areas where there were bugs
>> hidden by a lack of error checking.
>>
>> I am explicitly sending more variables to functions to avoid strange
>> bleed over stuff...
>>
>> I will keep you all posted
>>
>
> Hi Israel,
>
> I think the crucial step is autologin. You can try according to the
> following links,
>
> the method I think I used
>
> https://blog.shvetsov.com/2010/09/auto-login-ubuntu-user-from-cli.html
> ---
> To auto login user "bob" on first console terminal (tty1) edit file
> /etc/init/tty1.conf and replace last line:
>
> exec /sbin/getty -8 38400 tty1
>
> with this:
>
> exec /bin/login -f bob < /dev/tty1 > /dev/tty1 2>&1
> ---
>
> I found second alternative (the accepted answer at)
>
> https://askubuntu.com/questions/175248/how-to-autologin-without-entering-username-and-passwordin-text-mode
>
>
> But there might be a problem, because I used this method when booting
> with 'init', and it might not work with systemd.
>
> I found this link, claimed to work with Ubuntu Server 16.04 LTS, which
> uses systemd (but I have not tested it),
>
> https://askubuntu.com/questions/819117/autologin-at-startup-to-ubuntu-server-16-04-1-lts
>
>
> See the accepted answer.
> ---
> Try this:
>
> Create the folder: /etc/systemd/system/getty@tty1.service.d
>
> Create the file: /etc/systemd/system/getty@tty1.service.d/override.conf
>
> Open the file with your favorite editor and add this:
>
> [Service]
> ExecStart=
> ExecStart=-/sbin/agetty --noissue --autologin myusername %I $TERM
> Type=idle
>
> Replace myusername by your user name.
> ---
>
> -o-
>
> I think starting X with startx is straight-forward even with systemd.
>
> It should be enough with the program packages
>
> xinit fluxbox xterm
>
> (you would replace fluxbox with some JWM package(s) ...).
>
> Best regards
> Nio
Hi Nio,
I have already done most of that, including the getty configuration for
systemd.
The only thing I do not do is use xinit in text-mode-menu... I use
starttorios. Perhaps I should run that instead, though startorios runs
a bunch of stuff to initialize everything else but perhaps X is not
being initialize, and lightdm does this automatically? I will test some
more things, and get back to you on it.
The getty line I was using is:
ExecStart=-/sbin/agetty -a root --noclear tty7 $TERM
I tried using %I initially, but that was not working, I will look into
the option you suggest passing (--noissue) and that may cause %I to work
better
Then I can mess with the text-mode-menu and see if 'starttorios' works
fine, or if I need to use xinit before that.
I also add text-mode-menu to the .bashrc via
[ "${TERM}" == 'linux' ] && text-mode-menu
I will test this out some more, thanks as always for your insights!
--
Regards
--
Mailing list: https://launchpad.net/~torios-dev
Post to : torios-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~torios-dev
More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] ToriOS ISO considerations
Den 2018-02-03 kl. 00:48, skrev Israel: On 01/30/2018 12:23 PM, Nio Wiklund wrote: Den 2018-01-30 kl. 19:15, skrev Israel: On 01/30/2018 02:55 AM, psutton wrote: On 27/01/18 13:07, Nio Wiklund wrote: Den 2018-01-26 kl. 23:21, skrev Israel: ... Hi Israel, You should be able to let it boot into a text screen, where you can use a dialog text menu for the alternatives. One alternative can be to run startx (providing the necessary program packages are installed. See for example this link (scroll down and you will find some dialog menus), https://help.ubuntu.com/community/Installation/UEFI-and-BIOS/stable-alternative Best regards Nio Hi all, My testing of this text-mode-menu has not gone extremely well. But I have been using the time to consolidate OBI code further into more common functions which provide more error checking, and logging. I have used some of the code from ISOmaker (which is well tested and I have used countless times, and improved over time) to re-implement things that I had done in OBI in an earlier time when my understanding of the chroot and shell scripting was much less than it is now. So currently I am refining OBI further. Nio, if you want to send me a simple way you boot into a terminal logged in, and then launch x on the appropriate tty I would appreciate your added input here. I have done these things in a few ways, but do not have a completely adequate solution in place (so I have reverted to starting X by default) Once I have tweaked the last bits (I have been testing and tweaking the code a lot recently) to fully adapt things, and make sure everything is using the new functions properly I will upload the ISO. Sorry this has taken so long, but I've needed to do this for a while, to make OBI more stable. I have found various areas where there were bugs hidden by a lack of error checking. I am explicitly sending more variables to functions to avoid strange bleed over stuff... I will keep you all posted Hi Israel, I think the crucial step is autologin. You can try according to the following links, the method I think I used https://blog.shvetsov.com/2010/09/auto-login-ubuntu-user-from-cli.html --- To auto login user "bob" on first console terminal (tty1) edit file /etc/init/tty1.conf and replace last line: exec /sbin/getty -8 38400 tty1 with this: exec /bin/login -f bob < /dev/tty1 > /dev/tty1 2>&1 --- I found second alternative (the accepted answer at) https://askubuntu.com/questions/175248/how-to-autologin-without-entering-username-and-passwordin-text-mode But there might be a problem, because I used this method when booting with 'init', and it might not work with systemd. I found this link, claimed to work with Ubuntu Server 16.04 LTS, which uses systemd (but I have not tested it), https://askubuntu.com/questions/819117/autologin-at-startup-to-ubuntu-server-16-04-1-lts See the accepted answer. --- Try this: Create the folder: /etc/systemd/system/getty@tty1.service.d Create the file: /etc/systemd/system/getty@tty1.service.d/override.conf Open the file with your favorite editor and add this: [Service] ExecStart= ExecStart=-/sbin/agetty --noissue --autologin myusername %I $TERM Type=idle Replace myusername by your user name. --- -o- I think starting X with startx is straight-forward even with systemd. It should be enough with the program packages xinit fluxbox xterm (you would replace fluxbox with some JWM package(s) ...). Best regards Nio -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] ToriOS ISO considerations
On 01/30/2018 12:23 PM, Nio Wiklund wrote: > Den 2018-01-30 kl. 19:15, skrev Israel: >> On 01/30/2018 02:55 AM, psutton wrote: >>> >>> On 27/01/18 13:07, Nio Wiklund wrote: Den 2018-01-26 kl. 23:21, skrev Israel: ... > > Hi Israel, > > You should be able to let it boot into a text screen, where you can > use a dialog text menu for the alternatives. One alternative can be to > run startx (providing the necessary program packages are installed. > > See for example this link (scroll down and you will find some dialog > menus), > > https://help.ubuntu.com/community/Installation/UEFI-and-BIOS/stable-alternative > > > Best regards > Nio Hi all, My testing of this text-mode-menu has not gone extremely well. But I have been using the time to consolidate OBI code further into more common functions which provide more error checking, and logging. I have used some of the code from ISOmaker (which is well tested and I have used countless times, and improved over time) to re-implement things that I had done in OBI in an earlier time when my understanding of the chroot and shell scripting was much less than it is now. So currently I am refining OBI further. Nio, if you want to send me a simple way you boot into a terminal logged in, and then launch x on the appropriate tty I would appreciate your added input here. I have done these things in a few ways, but do not have a completely adequate solution in place (so I have reverted to starting X by default) Once I have tweaked the last bits (I have been testing and tweaking the code a lot recently) to fully adapt things, and make sure everything is using the new functions properly I will upload the ISO. Sorry this has taken so long, but I've needed to do this for a while, to make OBI more stable. I have found various areas where there were bugs hidden by a lack of error checking. I am explicitly sending more variables to functions to avoid strange bleed over stuff... I will keep you all posted -- Regards -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] ToriOS ISO considerations
On 01/30/2018 12:23 PM, Nio Wiklund wrote: > Den 2018-01-30 kl. 19:15, skrev Israel: >> On 01/30/2018 02:55 AM, psutton wrote: >>> >>> On 27/01/18 13:07, Nio Wiklund wrote: Den 2018-01-26 kl. 23:21, skrev Israel: > Hi all, > > I recently have been putting some work into OBI, as you all know. > > There have been a few issues related to how I built the base tarball > that should be completely resolved. > > One thing I have recently decided to try is to test out the old > '9W' ;) > startup screen > > a.k.a text-mode-menu > > Basically it shows a menu allowing old computers to use the dialog > interface for OBI without needing the entire ToriOS environment to > load. Of course ToriOS can still be run from that menu by > choosing the > graphical interface option. > > This is a pretty big change (visually) so I am going to put it in the > next ISO to get everyone's feedback. > > The majority of my current work in OBI has been adding tabs to the > code, > as well as comments. I did, however, change a major thing to install > grub, rather than the old manual configuration method using sed. We > already install grub but I just moved it before other things that > went > in front of it previously. > > I hope to have this out soon, however Launchpad is slow to build > things. > It is likely bionic is taking a lot of resources right now, as > well as > all the kernel mess (Meltdown/Spectre). > > So, specifically Nio (9w) what do you think about my use of the > text-mode-menu again (it has been many years since we've used it). > Hi Israel, Sure we can use the text-mode-menu again. It might be particularly useful for 1. Very old computers and computer with very small RAM 2. Computers with a graphics chip/card, that does not work out of the box with the built-in linux drivers. Please let us know, when there is something to test! Best regards Nio >>> Text mode is a good idea, debian still uses this as an option, i know >>> the Raspbian intaller for Raspberry Pi, desktop / pixel release so it >>> should not be a problem for people to install >>> >>> I am giessing there willbe >>> >>> boot - > bootmenu -- choice of text or gui mode then from the gui live >>> you can install and from the text mode you can install or basically >>> move >>> directly in to a OBI installer. >>> >>> Or something along those lines. >>> >>> Paul >>> >> Hey Paul, >> >> The original OBI ran the text-mode-menu at the startup. >> >> I think my issue is that it is trying to start X, but I am not fully >> starting everything. >> >> What should happen is that instead of starting X it boots into this >> dialog menu which allows you to choose what you want to do (here is the >> abbreviated menu) >> >> Graphics mode (what we have been using) >> >> Text mode (low ram) >> >> quit to the shell >> >> reboot >> >> poweroff >> >> >> I need to (probably) remove nodm (or disable it) to see if I can work >> things to use the text mode menu. >> >> > > Hi Israel, > > You should be able to let it boot into a text screen, where you can > use a dialog text menu for the alternatives. One alternative can be to > run startx (providing the necessary program packages are installed. > > See for example this link (scroll down and you will find some dialog > menus), > > https://help.ubuntu.com/community/Installation/UEFI-and-BIOS/stable-alternative > > > Best regards > Nio Hi Nio, This is exactly what I was getting at!! currently we are using nodm to get past the text login screen and into the X environment (kind of like how lightdm bypasses the text login screen for the GUI login screen) But I am testing a build (actually I am building it right now) where I simply disable nodm (which is automatically installed by torios-live and then enabled). So I will see if I can use the text-mode-menu from there. I have also converted that script to do a few things at the startup. First it asks for some general configurations (language, keyboard) then presents the menu, and the menu, like the rest of OBI can be fully translated into other locales using gettext (as we have done). I am not entirely sure how well this will all work, but I will be working on it. I also am testing some changes I made to OBI. I went ahead and refactored the logging functions, and the "echo out" functions (they use zenity/dialog to display some information) to be sourced from the main 'functions' file. I renamed it to obi-functions (keeping the old one in case I missed something somewhere) and caused the sub scripts to source it and implement those functions calling them with their own function name as an argument (so logging will be easier to trace to a specific function/file) My next goal is to refactor the mklub (in the separate mkp* scripts) and test out using a
Re: [Torios-dev] ToriOS ISO considerations
Den 2018-01-30 kl. 19:15, skrev Israel: On 01/30/2018 02:55 AM, psutton wrote: On 27/01/18 13:07, Nio Wiklund wrote: Den 2018-01-26 kl. 23:21, skrev Israel: Hi all, I recently have been putting some work into OBI, as you all know. There have been a few issues related to how I built the base tarball that should be completely resolved. One thing I have recently decided to try is to test out the old '9W' ;) startup screen a.k.a text-mode-menu Basically it shows a menu allowing old computers to use the dialog interface for OBI without needing the entire ToriOS environment to load. Of course ToriOS can still be run from that menu by choosing the graphical interface option. This is a pretty big change (visually) so I am going to put it in the next ISO to get everyone's feedback. The majority of my current work in OBI has been adding tabs to the code, as well as comments. I did, however, change a major thing to install grub, rather than the old manual configuration method using sed. We already install grub but I just moved it before other things that went in front of it previously. I hope to have this out soon, however Launchpad is slow to build things. It is likely bionic is taking a lot of resources right now, as well as all the kernel mess (Meltdown/Spectre). So, specifically Nio (9w) what do you think about my use of the text-mode-menu again (it has been many years since we've used it). Hi Israel, Sure we can use the text-mode-menu again. It might be particularly useful for 1. Very old computers and computer with very small RAM 2. Computers with a graphics chip/card, that does not work out of the box with the built-in linux drivers. Please let us know, when there is something to test! Best regards Nio Text mode is a good idea, debian still uses this as an option, i know the Raspbian intaller for Raspberry Pi, desktop / pixel release so it should not be a problem for people to install I am giessing there willbe boot - > bootmenu -- choice of text or gui mode then from the gui live you can install and from the text mode you can install or basically move directly in to a OBI installer. Or something along those lines. Paul Hey Paul, The original OBI ran the text-mode-menu at the startup. I think my issue is that it is trying to start X, but I am not fully starting everything. What should happen is that instead of starting X it boots into this dialog menu which allows you to choose what you want to do (here is the abbreviated menu) Graphics mode (what we have been using) Text mode (low ram) quit to the shell reboot poweroff I need to (probably) remove nodm (or disable it) to see if I can work things to use the text mode menu. Hi Israel, You should be able to let it boot into a text screen, where you can use a dialog text menu for the alternatives. One alternative can be to run startx (providing the necessary program packages are installed. See for example this link (scroll down and you will find some dialog menus), https://help.ubuntu.com/community/Installation/UEFI-and-BIOS/stable-alternative Best regards Nio -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] ToriOS ISO considerations
On 01/30/2018 02:55 AM, psutton wrote: > > On 27/01/18 13:07, Nio Wiklund wrote: >> Den 2018-01-26 kl. 23:21, skrev Israel: >>> Hi all, >>> >>> I recently have been putting some work into OBI, as you all know. >>> >>> There have been a few issues related to how I built the base tarball >>> that should be completely resolved. >>> >>> One thing I have recently decided to try is to test out the old '9W' ;) >>> startup screen >>> >>> a.k.a text-mode-menu >>> >>> Basically it shows a menu allowing old computers to use the dialog >>> interface for OBI without needing the entire ToriOS environment to >>> load. Of course ToriOS can still be run from that menu by choosing the >>> graphical interface option. >>> >>> This is a pretty big change (visually) so I am going to put it in the >>> next ISO to get everyone's feedback. >>> >>> The majority of my current work in OBI has been adding tabs to the code, >>> as well as comments. I did, however, change a major thing to install >>> grub, rather than the old manual configuration method using sed. We >>> already install grub but I just moved it before other things that went >>> in front of it previously. >>> >>> I hope to have this out soon, however Launchpad is slow to build things. >>> It is likely bionic is taking a lot of resources right now, as well as >>> all the kernel mess (Meltdown/Spectre). >>> >>> So, specifically Nio (9w) what do you think about my use of the >>> text-mode-menu again (it has been many years since we've used it). >>> >> Hi Israel, >> >> Sure we can use the text-mode-menu again. It might be particularly >> useful for >> >> 1. Very old computers and computer with very small RAM >> >> 2. Computers with a graphics chip/card, that does not work out of the >> box with the built-in linux drivers. >> >> Please let us know, when there is something to test! >> >> Best regards >> Nio >> > Text mode is a good idea, debian still uses this as an option, i know > the Raspbian intaller for Raspberry Pi, desktop / pixel release so it > should not be a problem for people to install > > I am giessing there willbe > > boot - > bootmenu -- choice of text or gui mode then from the gui live > you can install and from the text mode you can install or basically move > directly in to a OBI installer. > > Or something along those lines. > > Paul > Hey Paul, The original OBI ran the text-mode-menu at the startup. I think my issue is that it is trying to start X, but I am not fully starting everything. What should happen is that instead of starting X it boots into this dialog menu which allows you to choose what you want to do (here is the abbreviated menu) Graphics mode (what we have been using) Text mode (low ram) quit to the shell reboot poweroff I need to (probably) remove nodm (or disable it) to see if I can work things to use the text mode menu. -- Regards -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] ToriOS ISO considerations
On 27/01/18 13:07, Nio Wiklund wrote: > Den 2018-01-26 kl. 23:21, skrev Israel: >> Hi all, >> >> I recently have been putting some work into OBI, as you all know. >> >> There have been a few issues related to how I built the base tarball >> that should be completely resolved. >> >> One thing I have recently decided to try is to test out the old '9W' ;) >> startup screen >> >> a.k.a text-mode-menu >> >> Basically it shows a menu allowing old computers to use the dialog >> interface for OBI without needing the entire ToriOS environment to >> load. Of course ToriOS can still be run from that menu by choosing the >> graphical interface option. >> >> This is a pretty big change (visually) so I am going to put it in the >> next ISO to get everyone's feedback. >> >> The majority of my current work in OBI has been adding tabs to the code, >> as well as comments. I did, however, change a major thing to install >> grub, rather than the old manual configuration method using sed. We >> already install grub but I just moved it before other things that went >> in front of it previously. >> >> I hope to have this out soon, however Launchpad is slow to build things. >> It is likely bionic is taking a lot of resources right now, as well as >> all the kernel mess (Meltdown/Spectre). >> >> So, specifically Nio (9w) what do you think about my use of the >> text-mode-menu again (it has been many years since we've used it). >> > > Hi Israel, > > Sure we can use the text-mode-menu again. It might be particularly > useful for > > 1. Very old computers and computer with very small RAM > > 2. Computers with a graphics chip/card, that does not work out of the > box with the built-in linux drivers. > > Please let us know, when there is something to test! > > Best regards > Nio > Text mode is a good idea, debian still uses this as an option, i know the Raspbian intaller for Raspberry Pi, desktop / pixel release so it should not be a problem for people to install I am giessing there willbe boot - > bootmenu -- choice of text or gui mode then from the gui live you can install and from the text mode you can install or basically move directly in to a OBI installer. Or something along those lines. Paul -- Paul Sutton http://www.zleap.net Torbay Tech Jam - 2nd Saturday of the Month at Paignton Library -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] ToriOS ISO considerations
Den 2018-01-30 kl. 01:33, skrev Israel: On 01/27/2018 07:07 AM, Nio Wiklund wrote: Den 2018-01-26 kl. 23:21, skrev Israel: Hi Israel, Sure we can use the text-mode-menu again. It might be particularly useful for 1. Very old computers and computer with very small RAM 2. Computers with a graphics chip/card, that does not work out of the box with the built-in linux drivers. Please let us know, when there is something to test! Best regards Nio Hi Nio, After some testing there is some sort of issue running the setup with nodm (the thing that logs us in automatically) and text-mode-menu. It may take me some serious experimentation to figure out how to work those things out. That said I am trying out a version without the text-mode-menu It is considerably smaller, but still not the right size (775 MiB) for a CD. It is close, but still a bit to big, I will do some tests to check things and if all goes well I will upload a new ISO soon. I have reworked a lot of the ISOmaker scripts recently to streamline the process considerably (use common functions for *everything*) and make the codebase much easier to maintain in the future. Over the years I have been refactoring OBI to do some similar stuff (mkp for the common things in mkp*) and I recently have switched to using sfdisk rather than fdisk for this same reason, to eventually make a unified single script for doing all the current mkp1,mkp2p1,mkpxpy, as well as other custom setups (like a separate /home /boot, etc) though this is still a way off. Thanks for your patience! Thanks for this update, Israel :-) Best regards Nio -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] ToriOS ISO considerations
On 01/27/2018 07:07 AM, Nio Wiklund wrote: > Den 2018-01-26 kl. 23:21, skrev Israel: > > Hi Israel, > > Sure we can use the text-mode-menu again. It might be particularly > useful for > > 1. Very old computers and computer with very small RAM > > 2. Computers with a graphics chip/card, that does not work out of the > box with the built-in linux drivers. > > Please let us know, when there is something to test! > > Best regards > Nio Hi Nio, After some testing there is some sort of issue running the setup with nodm (the thing that logs us in automatically) and text-mode-menu. It may take me some serious experimentation to figure out how to work those things out. That said I am trying out a version without the text-mode-menu It is considerably smaller, but still not the right size (775 MiB) for a CD. It is close, but still a bit to big, I will do some tests to check things and if all goes well I will upload a new ISO soon. I have reworked a lot of the ISOmaker scripts recently to streamline the process considerably (use common functions for *everything*) and make the codebase much easier to maintain in the future. Over the years I have been refactoring OBI to do some similar stuff (mkp for the common things in mkp*) and I recently have switched to using sfdisk rather than fdisk for this same reason, to eventually make a unified single script for doing all the current mkp1,mkp2p1,mkpxpy, as well as other custom setups (like a separate /home /boot, etc) though this is still a way off. Thanks for your patience! -- Regards -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] ToriOS ISO considerations
On 01/27/2018 07:07 AM, Nio Wiklund wrote: > Den 2018-01-26 kl. 23:21, skrev Israel: >> Hi all, >> >> I recently have been putting some work into OBI, as you all know. >> >> There have been a few issues related to how I built the base tarball >> that should be completely resolved. >> >> One thing I have recently decided to try is to test out the old '9W' ;) >> startup screen >> >> a.k.a text-mode-menu >> >> Basically it shows a menu allowing old computers to use the dialog >> interface for OBI without needing the entire ToriOS environment to >> load. Of course ToriOS can still be run from that menu by choosing the >> graphical interface option. >> >> This is a pretty big change (visually) so I am going to put it in the >> next ISO to get everyone's feedback. >> >> The majority of my current work in OBI has been adding tabs to the code, >> as well as comments. I did, however, change a major thing to install >> grub, rather than the old manual configuration method using sed. We >> already install grub but I just moved it before other things that went >> in front of it previously. >> >> I hope to have this out soon, however Launchpad is slow to build things. >> It is likely bionic is taking a lot of resources right now, as well as >> all the kernel mess (Meltdown/Spectre). >> >> So, specifically Nio (9w) what do you think about my use of the >> text-mode-menu again (it has been many years since we've used it). >> > > Hi Israel, > > Sure we can use the text-mode-menu again. It might be particularly > useful for > > 1. Very old computers and computer with very small RAM > > 2. Computers with a graphics chip/card, that does not work out of the > box with the built-in linux drivers. > > Please let us know, when there is something to test! > > Best regards > Nio Hi I will Nio!! The packages finally built on launchpad (it has been really slow lately) so I will being making builds today, and I will test until I have something good to give you -- Regards -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] ToriOS ISO considerations
Den 2018-01-26 kl. 23:21, skrev Israel: Hi all, I recently have been putting some work into OBI, as you all know. There have been a few issues related to how I built the base tarball that should be completely resolved. One thing I have recently decided to try is to test out the old '9W' ;) startup screen a.k.a text-mode-menu Basically it shows a menu allowing old computers to use the dialog interface for OBI without needing the entire ToriOS environment to load. Of course ToriOS can still be run from that menu by choosing the graphical interface option. This is a pretty big change (visually) so I am going to put it in the next ISO to get everyone's feedback. The majority of my current work in OBI has been adding tabs to the code, as well as comments. I did, however, change a major thing to install grub, rather than the old manual configuration method using sed. We already install grub but I just moved it before other things that went in front of it previously. I hope to have this out soon, however Launchpad is slow to build things. It is likely bionic is taking a lot of resources right now, as well as all the kernel mess (Meltdown/Spectre). So, specifically Nio (9w) what do you think about my use of the text-mode-menu again (it has been many years since we've used it). Hi Israel, Sure we can use the text-mode-menu again. It might be particularly useful for 1. Very old computers and computer with very small RAM 2. Computers with a graphics chip/card, that does not work out of the box with the built-in linux drivers. Please let us know, when there is something to test! Best regards Nio -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
