torios-dev team mailing list archive

[Nio Wiklund <nio.wiklund@xxxxxxxxx>]

Den 2015-05-07 03:54, Israel skrev:
> Hi Nio,
> (inlines)
> On 05/06/2015 10:54 AM, Nio Wiklund wrote:
>> Den 2015-05-06 15:39, Israel skrev:
>>> On 05/06/2015 08:04 AM, Nio Wiklund wrote:
>>> ... 
>> Hi Israel,
>>
>> A. I don't think I understand. I intended to try to help getting nano to
>> work, so I need the environment for doing that. Is that what you call
>> the iso maker scripts?
> Nano works fine in the installed system (I use it often).
> Nano does NOT work in the liveCD (as you well know).
> So, in order to test it, you need to build the liveCD.
> The ISO maker scripts make the ISO (think NioWill scripts for 9w...
> except automated)
>> 1. Get the current ToriOS iso file. Mount it. OK
>>
>> 2. What should I extract from the iso file? The iso maker scripts? What
>> names? Where should I put them? Do I need to extract and or install
>> something else?
> extract the tarball
> /image/live/tarballs/ToriOS-i386.tar.xz
> 
> IF you want to build the ISO from the ISOmaker scripts
> 
> https://github.com/Israel-/ISOmaker
> 
> you can branch the entire thing if you like
> mostly you need to
> chmod +x ISOmaker chroot.bash chroot2.bash isolinux-chroot.bash
> 
> then run
> ./ISOmaker
> the first time it will run for a very long time.... it will need to
> download everything to make the deboostrap, then tar it up.  THEN it
> will also need to download everything to make the liveCD environment
> (torios-live, jwm, jwm-settings-manager, obi-installer, mkusb, etc.. etc..)
> Then it will build....  and soon enough... you will have a live CD.
> 
> testing would be tweaking the chroot.bash OR chroot2.bash scripts used
> by ISOmaker
> to try to make nano not segfault...
> 
> The other option would be to try to figure out what nano needs that we
> are not giving it....
> 
>>
>> B. There is no check that the tarball is an OS. It is possible to do it
>> - at least check for some files, that should be there - I do something
>> similar in mkusb in order to see if it is 'iso-testing', installing the
>> same system (but the next daily build). Then the USB pendrive is
>> selected automatically.
>>
>> Yes, the OBI will fail, if certain files are missing. For example, we
>> have already found the /etc/fstab should be there (do you remember)?
> haha, oh yeah of course :)  that was a huge issue... how could I forget
> that!  Wow, we have come remarkably far since those early days of trying
> to figure out how in the world to build an OS :D
> You are completely right!  So those checks should be sufficient to stop
> something bad from happening if a user clicks on their:
>  funny-cat-videos.tar.xz file
> instead of:
> my-supercool-os.tar.xz file
> that was my only real concern.  I know in theory it should be hard to
> accidentally do that, but either way... it would fail, thanks for
> reminding me!!
>>
>> Best regards
>> Nio
> 

Hi Israel,

I'll try to use your ISOmaker scripts. I think and hope that there will
be time for nano this weekend.

By the way, have you tried to use another Ubuntu mirror as source, for
the packages, in order to build the iso file? If you are using the US
mirror, maybe it contains a faulty nano package for some reason. Or
contained a faulty nano package, when you built your system. In that
case maybe wiping your system and building a new cache of packages (at
least get a new version of nano) would solve the problem?

Best regards
Nio