Remastering SolydXK [adapted: 22 July 2015]

[Arjen Balfoort]

I'm downloading the ISO right now and will look at them after the weekend.
I'll also send you an e-mail with your FTP account.

[lufilte]

I'm downloading the ISO right now and will look at them after the weekend.
I'll also send you an e-mail with your FTP account.

Tank you my friend.

I only did is Localized to Portuguêse European, but i can also do another ones including Portuguêse Brazilian too.!

[Arjen Balfoort]

I only did is Localized to Portuguêse European, but i can also do another ones including Portuguêse Brazilian too.!

That would be great! However, remember that ISOs are released twice a year and you'll then have 4 ISOs to build, test and upload. It takes time, effort and commitment

[lufilte]

I only did is Localized to Portuguêse European, but i can also do another ones including Portuguêse Brazilian too.!

That would be great! However, remember that ISOs are released twice a year and you'll then have 4 ISOs to build, test and upload. It takes time, effort and commitment

I'll remember that.
But the constructor rename the 201601 ISO to 201606, why this?
and btw the help menu doesn’t work.

[Arjen Balfoort]

For me it generates 201605 isos. So, I can only guess that it is June on your development machine.
The help button opens Firefox with the help file. Works for me and I don't know why not for you.

Please start the constructor from terminal and post back the output if you have any problems:

Code: Select all

constructor

[lufilte]

For me it generates 201605 isos. So, I can only guess that it is June on your development machine.
The help button opens Firefox with the help file. Works for me and I don't know why not for you.

Please start the constructor from terminal and post back the output if you have any problems:

Code: Select all

constructor

Even with the update of constructor i do not have the help see below

Code: Select all

ommand to execute: modprobe loop
Command to execute: ls /usr/lib/grub/ 2> /dev/null | grep efi | cut -d'-' -f1
Opening "/usr/lib/solydxk/constructor/../../../share/solydxk/constructor/help.html" with Chromium Web Browser  (text/html)
[1:1:0530/112603:FATAL:sandbox_linux.cc(178)] Check failed: sandbox::Credentials::MoveToNewUserNS(). 
#0 0x7fd16beaca9e <unknown>
#1 0x7fd16bec03ab <unknown>
#2 0x7fd16f979ecd <unknown>
#3 0x7fd16e5ad03f <unknown>
#4 0x7fd16be78ae3 <unknown>
#5 0x7fd16be79cc3 <unknown>
#6 0x7fd16be787e0 <unknown>
#7 0x7fd16ba2daea ChromeMain
#8 0x7fd163f60b45 __libc_start_main
#9 0x7fd16ba2d999 <unknown>

Received signal 6
#0 0x7fd16beac578 <unknown>
#1 0x7fd1642f98d0 <unknown>
#2 0x7fd163f74067 gsignal
#3 0x7fd163f75448 abort
#4 0x7fd16beaba72 <unknown>
#5 0x7fd16bec06b3 <unknown>
#6 0x7fd16f979ecd <unknown>
#7 0x7fd16e5ad03f <unknown>
#8 0x7fd16be78ae3 <unknown>
#9 0x7fd16be79cc3 <unknown>
#10 0x7fd16be787e0 <unknown>
#11 0x7fd16ba2daea ChromeMain
#12 0x7fd163f60b45 __libc_start_main
#13 0x7fd16ba2d999 <unknown>
  r8: ffffffd1745c2e88  r9: ffffffd1745c2e78 r10: 0000000000000008 r11: 0000000000000202
 r12: 00007ffffedf1518 r13: 00007ffffedf2801 r14: 00007ffffedf0b88 r15: 00007ffffedf0b78
  di: 0000000000000001  si: 0000000000000001  bp: 00007fd1733b2f20  bx: 0000000000000000
  dx: 0000000000000006  ax: 0000000000000000  cx: ffffffffffffffff  sp: 00007ffffedf00a8
  ip: 00007fd163f74067 efl: 0000000000000202 cgf: 0000000000000033 erf: 0000000000000000
 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]

this is when i call constructor from gui link.

From terminal i get this:

Code: Select all

Command to execute: modprobe loop
Command to execute: ls /usr/lib/grub/ 2> /dev/null | grep efi | cut -d'-' -f1
Create list store eval string: Gtk.ListStore(bool, str, str, int, int)
First item is column name (multi-column list): Selecionar
First item is column name (multi-column list): Distribuição
First item is column name (multi-column list): Diretório de trabalho
Create column names: ['Selecionar', 'Distribuição', 'Diretório de trabalho']
First item is column name: skip first item
Create column: Gtk.TreeViewColumn("Selecionar", Gtk.CellRendererToggle(), active=0)
Check box found: add toggle function
Column added: Selecionar
Create column: Gtk.TreeViewColumn("Distribuição", Gtk.CellRendererText(), text=1, weight=3, size=4)
Column added: Distribuição
Create column: Gtk.TreeViewColumn("Diretório de trabalho", Gtk.CellRendererText(), text=2, weight=3, size=4)
Column added: Diretório de trabalho
Versão: 2.7.2

cheers

[grizzler]

That may be because the constructor tries to open the browser as root. I assume chromium's sandbox forbids that. I know firefox can be started as root (which is something you just don't want, as far as I'm concerned). To prevent that from happening I create empty files called /root/.mozilla on all my systems. That makes firefox crash with a warning about not being able to find the profile whenever some root application tries to run it. And of course that's what happens when I click the constructor's Help button.

The solution here would be to open the help file as the user, not root. There are several ways to find the logged in user inside an application running as root, but depending on whether it was called with gksu, gksudo, sudo or pkexec, not all of them work under all circumstances. I usually use this (which is a bit contrived, but at least it always works - for the first logged in user only, of course):

Code: Select all

User=$(LANG=C who -u | head -n1)
User=${User%% *}

As a quick test I created a small shell script /usr/lib/solydxk/constructor/files/open containing

Code: Select all

#!/bin/bash
User=$(LANG=C who -u | head -n1)
sudo -u ${User%% *} -- xdg-open $1

and changed the function on_btnHelp_clicked() in /usr/lib/solydxk/constructor/constructor.py to

Code: Select all

    def on_btnHelp_clicked(self, widget):
        system("/usr/lib/solydxk/constructor/files/open file://%s &" % self.help)

This works as expected, neatly opening the help page in another tab in my browser or starting the browser if it isn't running already (though in the latter case, it does leave the constructor's own terminal window open when the constructor is closed, so this will require some finetuning...).

[Arjen Balfoort]

Never thought of using an external bash!
I tried all kinds of ways the python way. Even changing the uid and gid but that didn't work. Whatever I did there was either a permission denied because I couldn't change the home directory to look in or it was trying to use Thunderbird to open the html file. Using xdg-mime to change that behavior for root did not work (I was warned for that).

I'll try you're way.

[Edit]
I'll use "logname" to get the user's name.

[Arjen Balfoort]

Still the same for me:

Code: Select all

Opening "/usr/lib/solydxk/constructor/../../../share/solydxk/constructor/help.html" with Mozilla Thunderbird Mail/News  (text/html)

and it doesn't do a thing.

[lufilte]

Ok so i did go on preferences to kde and forced to open firefox as predefined web browser then the help works.

i see that only works with Firefox is ok for me.

but yes i do not know why it try to open chromium!!! that doesn't make sense.

but yes now it is working
cheers

[grizzler]

Still the same for me:

Code: Select all

Opening "/usr/lib/solydxk/constructor/../../../share/solydxk/constructor/help.html" with Mozilla Thunderbird Mail/News  (text/html)

and it doesn't do a thing.

Weird. I remember RavenLX mentioning she had issues when xdg-open needed to open a file in an editor. It seems KDE doesn't always play nice with xdg-open.
There must be something seriously wrong with the mime settings - or how they're interpreted - if text/html files are offered to Thunderbird!

P.S.
I tried logname to find the username. It failed under some circumstances (I forget what they were exactly - I think it was in a cron job).

[Arjen Balfoort]

I've created open-as-user in solydxk-system:

Code: Select all

#!/bin/bash
FLE=$1
USR=$2
if [ "$USR" == '' ]; then
  USR=$(logname)
fi
CMD=$(which kde-open)
if [ "$CMD" == "" ]; then
  CMD="xdg-open"
fi
sudo -H -u $USR bash -c "$CMD \"$FLE\""

The constructor has been updated to use this script. I think it's going to come in handy in other applications as well

Thanks Grizzler, your script gave me the hint I needed.

[ilu]

That may be because the constructor tries to open the browser as root. I assume chromium's sandbox forbids that. I know firefox can be started as root (which is something you just don't want, as far as I'm concerned). To prevent that from happening I create empty files called /root/.mozilla on all my systems. That makes firefox crash with a warning about not being able to find the profile whenever some root application tries to run it. And of course that's what happens when I click the constructor's Help button.

I can't really help with the issue but this reminds me that also calling the UM help starts firefox as root which I don't mind but which is not the safest behaviour.

[Arjen Balfoort]

Perhaps you meant DDM or USB Creator?
I've updated those as well.

[ilu]

I meant UM: There is this link to our forums on the "Informations" page - if you click that it starts a root FF.
I regularly use it to update my non-solydxk-firefox from mozilla. But for someone unaware starting an internet search from there it might be considered potentially dangerous.

[Arjen Balfoort]

Ah, those!
There was only thing I could do: remove the hyperlinks all together.
I cannot start another application as another user from a hyperlink. That brings even more security issues.

[ilu]

As I said, I like the link there but I can do without.
Besides that it's root the root firefox also has no security settings and no security addons installed. And it causes confusion. We had forum threads in the past where people got confused ("My browser does not have any configuration anymore, what happened?").
For general safety I would suggest to just put the links name there ("Open your browser and visit this site: ...") without a hyperlink behind it. People would need to copy-paste but that's what a prudent internet user should do anyways.

[Arjen Balfoort]

As I said, I like the link there but I can do without.
Besides that it's root the root firefox also has no security settings and no security addons installed. And it causes confusion. We had forum threads in the past where people got confused ("My browser does not have any configuration anymore, what happened?").

I implemented a tip from Grizzler in our nightlies: create /root/.mozilla and /root/.thunderbird files. You won't be able to open Firefox or Thunderbird as root. If you really need to, you'll need to remove those files manually.

For general safety I would suggest to just put the links name there ("Open your browser and visit this site: ...") without a hyperlink behind it. People would need to copy-paste but that's what a prudent internet user should do anyways.

That's how it works with the updated UM. It's in the repository.

[jsvenancio]

Good night.

Does this tutorial still apply with the new SolydX updates?

If you have the need to create a SolydXK iso with some extra programs or custom configuration that you can use on a USB stick, or even plan to build a CE of SolydXK, this is the thing for you.

Disclaimer
SolydXK Constructor was created for maintaining the current SolydXK ISO's, and is provided as-is: support is not provided.

Source: https://github.com/SolydXK/solydxk-constructor

Installation
Make sure you're sources.list looks like this:

Code: Select all

deb http://repository.solydxk.com/ solydxk main upstream import
deb http://ftp.debian.org/debian jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb http://ftp.debian.org/debian/ jessie-backports main contrib non-free

Upgrade your system, and install solydxk-constructor:

Code: Select all

sudo apt update
sudo apt upgrade
sudo apt install solydxk-constructor

SolydXK Constructor Help
SolydXK Constructor helps building your custom SolydXK ISO, and was solely created for maintaining the current SolydXK ISO's, but it might benefit those who want to build their custom SolydXK ISO.
You can download SolydXK's nightly builds here: http://downloads.solydxk.nl/nightly

Before you start, take a good look at the Help page.

Example build: SolydK

1. Check and adapt (as root):
   /usr/lib/solydxk/constructor/files/trackers
   /usr/lib/solydxk/constructor/files/webseeds
2. Add 201411 ISO with the constructor (see the Help file on how to do that).
3. Edit /root/etc/apt/sources.list:

   Code: Select all

   deb http://repository.solydxk.com/ solydxk main upstream import
   deb http://ftp.debian.org/debian jessie main contrib non-free
   deb http://security.debian.org/ jessie/updates main contrib non-free
   deb http://ftp.debian.org/debian/ jessie-backports main contrib non-free

4. Hit "Edit in terminal" and run these commands:

   Code: Select all

   apt install solydk-system-adjustments libjpeg62-turbo plymouth-themes solydxk-mozilla-evolvere-icon-theme
   apt dist-upgrade

   Note 1: you need to replace solydk-system-adjustments with solydx-system-adjustments if you're editing SolydX.
   Note 2: ignore the libkmod errors while uploading. You're in a chrooted environment and these messages seem harmless.
5. Hit "Upgrade"
6. Check /boot/grub directory:
   efi.img
   font.pf2
   grub.cfg
   loopback.cfg (copy of grub.cfg)
   [x86_64-efi] or [i386-efi]
7. Edit boot/isolinux/splash.png if needed
8. Edit boot/grub/grub.cfg (Replace SolydK with SolydX if you're editing SolydX):

   Code: Select all

   if loadfont $prefix/font.pf2 ; then
     set gfxmode=800x600
     insmod efi_gop
     insmod efi_uga
     insmod video_bochs
     insmod video_cirrus
     insmod gfxterm
     insmod png
     terminal_output gfxterm
   fi
   
   background_image /isolinux/splash.png
   set menu_color_normal=white/black
   set menu_color_highlight=dark-gray/white
   set timeout=5
   
   
   menuentry "Start SolydK 8 64-bit 201507" {
       set gfxpayload=keep
       linux   /live/vmlinuz boot=live config  quiet splash
       initrd  /live/initrd.img
   }
   menuentry "Start SolydK 8 64-bit 201507 (safe)" {
       set gfxpayload=keep
       linux   /live/vmlinuz boot=live config  memtest noapic noapm nodma nomce nolapic nomodeset nosmp nosplash vga=normal
       initrd  /live/initrd.img
   }
   submenu 'Advanced options ...' {
       menuentry "Check the integrity of the medium" {
   	linux   /live/vmlinuz  boot=live verify-checksums
   	initrd  /live/initrd.img
       }
       menuentry "Boot from disk" {
   	set root=(hd1)
   	chainloader +1
       }
       menuentry "System restart" {
   	reboot
       }
       menuentry "System shutdown" {
   	halt
       }
   }
   

   Copy boot/grub/grub.cfg to boot/grub/loopback.cfg if it does not exist.
   Translate both files if you make a localized ISO.
9. Check if exists: boot/efi/boot/bootx64.efi or boot/efi/boot/bootia32.efi
10. Edit boot/isolinux/isolinux.cfg (Replace SolydK with SolydX if you're editing SolydX):

    Code: Select all

    default vesamenu.c32
    timeout 100
    
    menu background splash.png
    menu title Welcome to SolydK 8 64-bit 201507
    menu color border 0 #00eeeeee #00000000
    menu color sel 7 #ffeeeeee #ff000000
    menu color title 0 #ffeeeeee #55000000
    menu color tabmsg 0 #ffeeeeee #55000000
    menu color unsel 0 #ffeeeeee #55000000
    menu color hotsel 0 #ff000000 #ffffffff
    menu color hotkey 7 #ffffffff #ff000000
    menu color timeout_msg 0 #ffffffff #00000000
    menu color timeout 0 #ffffffff #00000000
    menu color cmdline 0 #ffffffff #00000000
    menu hidden
    
    label live
      menu label Start SolydK
      kernel /live/vmlinuz
      append boot=live config  quiet splash initrd=/live/initrd.img
    menu default
    label xforcevesa
        menu label Start SolydK (safe)
        kernel /live/vmlinuz
        append boot=live config  memtest noapic noapm nodma nomce nolapic nomodeset nosmp nosplash vga=normal initrd=/live/initrd.img
    
    menu begin advanced
        menu label ^Advanced options
    	menu title Advanced options
    	label mainmenu
    	    menu label ^Back..
    	    menu exit
    	label check
    	    menu label Check the integrity of the medium
    	    kernel /live/vmlinuz
    	    append boot=live verify-checksums initrd=/live/initrd.img
    	label hdt
    	    menu label Hardware Detection Tool
    	    com32 hdt.c32
    	label memtest
    	    menu label Memory Diagnostic Tool
    	    kernel memtest86
    	label local
    	    menu label Boot from disk
    	    com32 chain.c32
    	    append hd0 0
    	label restart
    	    menu label System restart
    	    com32 reboot.c32
    	label off
    	    menu label System shutdown
    	    com32 poweroff.c32
    menu end
    

11. Check boot/offline/ directory:
    grub-efi-amd64_2.02~beta2-22_amd64.deb
    grub-efi_2.02~beta2-22_amd64.deb
    or the 32-bit versions of those packages.
12. Hit "Build"

Use Debian live as base
As said above: the SolydXK Constructor was built to maintain the SolydXK ISOs. However, theoratically it should also work with a Debian Live ISO: http://www.debian.org/CD/live
If you use Debian, you'll need the "isolinux" directory (and its contents) to replace the "isolinux" directory in the Debian unpack directory.
After that you'll need to configure the distribution from scratch.