VSIDO Community

VSIDO Controls => VSIDO Discussions => Topic started by: VastOne on January 17, 2017, 02:53:32 AM

Title: VSIDO Build 2017
Post by: VastOne on January 17, 2017, 02:53:32 AM
In a discussion that started here (http://vsido.org/index.php?topic=1258.msg14292#msg14292) this space is reserved to discuss the build process

I will be keeping a journal of the process here

Phase III of this endeavor is completed with the above toolset added except for Firefox or any browser at all

These are the files needed to get to the goal of Phase III which was to have a build to the point of a fsarchive and add specific tools.. think of these as Silos now as development goes forward.. this is the repeatable process I never had to do what I have really wanted in testing different setups and builds. 

Code: [Select]
xorg fluxbox lightdm spacefm lxappearance udevil medit xfce4-appfinder dbus-x11 bleachbit psmisc tint2 conky-all xfce4-terminal consolekit policykit-1 yad ncdu rsync squashfs-tools xorriso live-boot live-config live-boot-initramfs-tools live-config-systemd syslinux-common syslinux isolinux liblzo2-2 mtools libburn4 libisoburn1 libisofs6 libjte1 xdotool wmctrl gksu gparted live-tools user-setup xterm nitrogen mirage fsarchiver libcurses-perl libterm-readkey-perl libcurses-ui-perl libio-stty-perl libio-pty-perl libexpect-perl libnl-3-200 libpcsclite1 wpasupplicant scrot curl libgtk2-perl ntfs-3g p7zip-full xfsdump xfsprogs btrfs-progs btrfs-tools curlftpfs xfce4-screenshooter hardinfo bum grsync ssh-askpass lvm2 xarchiver fonts-liberation htop
and these refracta tools

Code: [Select]
refractainstaller-base_9.1.9-1_all.deb
refractainstaller-gui_9.1.9_all.deb
refractasnapshot-base_9.3.4_all.deb
refractasnapshot-gui_9.3.4_all.deb

also included is the default VSIDO /etc/skel which is the default desktop ... and all /usr/local/bin tools (hakerdefo goodies included!)

There is also an attachment of current installed apps on the released VSIDO to use as a checklist for apps

First bit of news:

New builds using mini.iso .. built using advanced install options and only the base software (no DM) just to the point of a tty login

The initial sizes are

x32 = 212.6 MiB fsarchive
x64 = 204.3 MiB fsarchive

which is close to ISO sizing

Title: Re: VSIDO Build 2017
Post by: VastOne on January 17, 2017, 03:21:09 AM
Next up: fluxbox and lxdm to get to a login
Title: Re: VSIDO Build 2017
Post by: VastOne on January 18, 2017, 04:40:06 AM
Ended up sticking with LightDM and here is an update...

I have built an x32 system to the level of lightdm, fluxbox, all of Xorg, spacefm, xfce4-terminal and xfce4-appfinder (f2 Run app) and the default /etc/skel and I would say 60% of the apps needed so far and refracta build suite. The remaining stuff though is the fat junk (Firefox and all of the media needed files)

First ISO build is a svelte 320 MiB ...  this is a good beginning but it did take all damned day and a LOT of brain bruising to remember shit I did 5 years ago to get things back as they are.. some are the same and others I shoehorned different ways

For me the hard part is done.. now it is just adding the basic tools to fill the menus ... I still have my doubts about whether this will be any smaller but it has been a fun challenge to get here
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 18, 2017, 05:58:19 AM
Once the build process is done and you have cleaned the house by,
Code: [Select]
apt-get clean
apt-get autoclean
apt-get autoremove
dpkg --list | grep '^rcb' | awk '{ print $2 }' | xargs dpkg -P
The following will list the installed packages by size,
Code: [Select]
dpkg-query -Wf '${Installed-Size}\t${Package}\n' | sort -nOr if you use aptitude,
Code: [Select]
aptitude -O installsize -F'%p %I' search '~i'Cheers!!!
Title: Re: VSIDO Build 2017
Post by: VastOne on January 18, 2017, 06:00:51 AM
Will do.. thanks mate!

What would be cool is if I could fsarchive this x32 bit and restore it.. (I can) and covert that to x64

That would save a shit ton of time... wishful thinking
Title: Re: VSIDO Build 2017
Post by: VastOne on January 20, 2017, 12:30:53 AM
Installed VSIDO 320 MiB and installed.. not a complete build but a enough to get an install ...

That's a small footprint... PackRat.. Now is when I need you to talk about what you would want as your base recovery CD and we build from there...

I could have the footprint stay right here and alter the login first run script to install the rest.. lot of possibilities..

I WANT INPUT!

(http://en.zimagez.com/miniature/shot-190117-235655.png) (http://en.zimagez.com/zimage/shot-190117-235655.php)
Title: Re: VSIDO Build 2017
Post by: jedi on January 20, 2017, 12:54:03 AM
I want VSIDO...   :'(
Title: Re: VSIDO Build 2017
Post by: PackRat on January 20, 2017, 01:09:42 AM
For the the recovery CD, I just need the basic apps to edit text files and partition/format hard drives.

terminal (xterm is fine)
spacefm, udevil -> not sure about fuse
medit, nano
partitioning tools -> fdisk, cfdisk (I like the ncurses interface), the newer ones for gpt
gparted -> but with the file support for btrfs and xfs
ntfs-3g -> I have Windows machines  :'(
wget
curl
archive tool -> fsarchiver, p7zip-full
wicd -> or just ceni
firefox-esr -> not as buggy, doesn't get whacked by gtk

That's really all I can think of past the base system, coreutils stuff.

Do you use any specialty networking and forensics tools? Those are always handy to have. Hakerdefo probably has few favorites.

Just the basic gtk and icons, don't need any of the multimedia apps.
Title: Re: VSIDO Build 2017
Post by: PackRat on January 20, 2017, 01:44:20 AM
I want VSIDO...   :'(

+100  8)

VSIDO as is makes for a pretty good rescue/recovery/live session.
Title: Re: VSIDO Build 2017
Post by: PackRat on January 20, 2017, 01:46:51 AM
Have you ever tried to make a live session that boots inot RAM?

That's a handy feature sometimes.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 20, 2017, 01:46:57 AM
I am slightly confused by this take on what I am doing

I am only strengthening what is already there..

As far as I know VSIDO is not changing at all

There may be some different build for specific reasons/users but I plan on going on with what is there for as long as it is supported
Title: Re: VSIDO Build 2017
Post by: PackRat on January 20, 2017, 01:53:42 AM
I thought you were making a mini iso with minimal X. The  the user can build from there.

Quote
As far as I know VSIDO is not changing at all

One change I think you should consider is replacing mirage with geeqie. Is mirage even developed anymore? Geeqie was the image viewer that supported raw photo format wasn't it?
Title: Re: VSIDO Build 2017
Post by: VastOne on January 20, 2017, 01:57:32 AM
^ that is certainly one release I could put out..

Another is centered on your need for a specific recovery tool.. VSIDO now minus multimedia

This is also an exercise for me to have a better repeatable process and refine it .. at the same time I am building images with debian's live-build thanks to this epic DYI Distro How To from Ozitraveller (http://crunchbang.org/forums/viewtopic.php?id=39907)

Title: Re: VSIDO Build 2017
Post by: PackRat on January 20, 2017, 02:22:47 AM
^ that is certainly one release I could put out..

That's what I [overly/] inferred. You were thinking of releasing the mini iso - like Siduction and Salix do; minimal X then users build what they need.

A network forensics and penetration testing install entry in the menu would be interesting. Although a unstable distro based forensics build seems to be a bit too bleeding edge.
Title: Re: VSIDO Build 2017
Post by: riV on January 20, 2017, 07:15:33 AM
hello VastOne
Fond of the word bare.  Bare strenghth is not mini,minimal, basic, or minus anything.

I also find it odd to find "ESR" on experimental[SID] builds. not consistent, except your mention of stability as the sole browser- removing one risk variable, but not cutting edge testing.  we are the risk takers and testers.
Title: Re: VSIDO Build 2017
Post by: PackRat on January 20, 2017, 01:09:47 PM
^ that is certainly one release I could put out..

Another is centered on your need for a specific recovery tool.. VSIDO now minus multimedia

This is also an exercise for me to have a better repeatable process and refine it .. at the same time I am building images with debian's live-build thanks to this epic DYI Distro How To from Ozitraveller (http://crunchbang.org/forums/viewtopic.php?id=39907)

Wouldn't need a the bells & whistles either - like conky  :D

You going to be using the same installer as ozi?
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 20, 2017, 04:52:28 PM
My take on this discussion. Keep the regular VSIDO build as it has always been and create a light version with Fluxbox, tint2, Terminal emulator, and NetworkManager. Nothing more, nothing less.
Why NetworkManager? Because there will be a plenty of space available ;)
Because there are plenty of users who connect to internet using smart phones and USB datacards (dongles) and wicd fails there. Users can connect to internet and via apt-get turn this VSIDO-LITE into recovery environment, pen-testing distro, Media server, anything they want :)

Cheers!!!
Title: Re: VSIDO Build 2017
Post by: VastOne on January 21, 2017, 11:59:32 PM
For the the recovery CD, I just need the basic apps to edit text files and partition/format hard drives.

terminal (xterm is fine)
spacefm, udevil -> not sure about fuse
medit, nano
partitioning tools -> fdisk, cfdisk (I like the ncurses interface), the newer ones for gpt
gparted -> but with the file support for btrfs and xfs
ntfs-3g -> I have Windows machines  :'(
wget
curl
archive tool -> fsarchiver, p7zip-full
wicd -> or just ceni
firefox-esr -> not as buggy, doesn't get whacked by gtk

That's really all I can think of past the base system, coreutils stuff.

Do you use any specialty networking and forensics tools? Those are always handy to have. Hakerdefo probably has few favorites.

Just the basic gtk and icons, don't need any of the multimedia apps.

Phase III of this endeavor is completed with the above toolset added except for Firefox or any browser at all

These are the files needed to get to the goal of Phase III which was to have a build to the point of a fsarchive and add specific tools.. think of these as Silos now as development goes forward.. this is the repeatable process I never had to do what I have really wanted in testing different setups and builds. 

Code: [Select]
xorg fluxbox lightdm spacefm lxappearance udevil medit xfce4-appfinder dbus-x11 bleachbit psmisc tint2 conky-all xfce4-terminal consolekit policykit-1 yad ncdu rsync squashfs-tools xorriso live-boot live-config live-boot-initramfs-tools live-config-systemd syslinux-common syslinux isolinux liblzo2-2 mtools libburn4 libisoburn1 libisofs6 libjte1 xdotool wmctrl gksu gparted live-tools user-setup xterm nitrogen mirage fsarchiver libcurses-perl libterm-readkey-perl libcurses-ui-perl libio-stty-perl libio-pty-perl libexpect-perl libnl-3-200 libpcsclite1 wpasupplicant scrot curl libgtk2-perl ntfs-3g p7zip-full xfsdump xfsprogs btrfs-progs btrfs-tools curlftpfs xfce4-screenshooter hardinfo bum grsync ssh-askpass
and these refracta tools

Code: [Select]
refractainstaller-base_9.1.9-1_all.deb
refractainstaller-gui_9.1.9_all.deb
refractasnapshot-base_9.3.4_all.deb
refractasnapshot-gui_9.3.4_all.deb

also included is the default VSIDO /etc/skel which is the default desktop ... and all /usr/local/bin tools (hakerdefo goodies included!)

The x64 is 329 MiB and the x32 is 332 MiB

I will put them both in the test areas once I am done testing them one more time

What I would like to see now is additional thoughts on what should be included and how.. I can script anything with wget and the vsido-welcome script

Think about VSIDO this small and first time logging in does an install of all multimedia and browser of your choice.. think out of the box.. because we can now
Title: Re: VSIDO Build 2017
Post by: VastOne on January 22, 2017, 12:20:51 AM
I am aware that there are several menu items missing.. I have not changed the menu's ... this is by design right now

@ PackRat... please confirm that fdisk and cfdisk are at what levels you need them to be

The only installer on these is the the Alternative Installer Method (refracta)
Title: Re: VSIDO Build 2017
Post by: PackRat on January 22, 2017, 12:51:44 AM
They are both current.

You have curl and scrot listed twice in your package list if that's a line for a script.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 22, 2017, 12:57:46 AM
Nitpicking fucking users...

HA!  I did say that! Out loud!

 ???  :-*  ???  ???   ???
Title: Re: VSIDO Build 2017
Post by: VastOne on January 22, 2017, 12:58:22 AM
They are both current.

You have curl and scrot listed twice in your package list if that's a line for a script.

I mean on the new ISO's did you dload and check already?

Title: Re: VSIDO Build 2017
Post by: VastOne on January 22, 2017, 01:00:24 AM

You have curl and scrot listed twice in your package list if that's a line for a script.

Fixed 

mumble grumble old man get OFF MY LAWN
Title: Re: VSIDO Build 2017
Post by: VastOne on January 22, 2017, 01:08:16 AM
My take on this discussion. Keep the regular VSIDO build as it has always been and create a light version with Fluxbox, tint2, Terminal emulator, and NetworkManager. Nothing more, nothing less.
Why NetworkManager? Because there will be a plenty of space available ;)
Because there are plenty of users who connect to internet using smart phones and USB datacards (dongles) and wicd fails there. Users can connect to internet and via apt-get turn this VSIDO-LITE into recovery environment, pen-testing distro, Media server, anything they want :)

Cheers!!!

Now that I have the base set, this is the next type of testing that I can start on.. a throwaway test if NM is to much.. :D

I'll begin with it

Also hakerdefo, think about the scripting options from here.. the user with this base and we could build scripts to get anything... think of that and let's have a discussion

I am thinking out of the gate that a choice would be between FF and Chrome (or anything else) as a browser, multimedia installs of what we now use on VSIDO and all those tools as another choice and security features as another (tor, etc)... I think this might be the future of distros or could be
Title: Re: VSIDO Build 2017
Post by: PackRat on January 22, 2017, 01:34:24 AM
mumble grumble old man get OFF MY LAWN

(http://en.zimagez.com/miniature/vqh18.jpg) (http://en.zimagez.com/zimage/vqh18.php)

getting the iso now.

Edit - looks good, pretty smooth boot and found my network:

(http://en.zimagez.com/miniature/shot-220117-015449.png) (http://en.zimagez.com/zimage/shot-220117-015449.php)

no issues with the partioning apps.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 22, 2017, 02:55:04 AM
^ Good one and thanks... Found I missed installing fsarchiver... looks like I wrote it down but did not install it.. will fix obviously but install it if you use this disk

Thank you
Title: Re: VSIDO Build 2017
Post by: VastOne on January 22, 2017, 03:00:49 AM
^ That was on the x32 build only
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 22, 2017, 05:55:01 AM
...
I am thinking out of the gate that a choice would be between FF and Chrome (or anything else) as a browser, multimedia installs of what we now use on VSIDO and all those tools as another choice and security features as another (tor, etc)... I think this might be the future of distros or could be...
VSIDO-LITE should replace wicd with NM. And give me list of applications with category, i.e. File-Managers (Thunar, SpaceFM, PCmanFM), Browsers (FF, Chrome, Opera, Vivaldi) etc. etc. And I'll build you a YAD welcome script to install them.
Cheers!!!
Title: Re: VSIDO Build 2017
Post by: VastOne on January 22, 2017, 06:02:35 AM
^ Tomorrows project... I am wiped tonight and need sleep

 ;D
Title: Re: VSIDO Build 2017
Post by: PackRat on January 22, 2017, 01:43:46 PM
Quote
VSIDO-LITE should replace wicd with NM

NetworkManager would br preferrable, but have the Debian-based distros been having the same breakage issues (seems to just quit working) some of the rolling release distros have? I would suspect not, since Debian probably has the manpower to keep up with the devlopment of NM and it's dependencies.

Edit - I removed wicd and re-installed NetworkManager and nm-applet to see if they fail.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 22, 2017, 10:54:24 PM
Added network-manager and firefox-esr to the next levels.. increased each ISO 50 MiB which is not that bad.. both will come in at 375 mark now...

Building them and will upload them as soon as they are done
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 01:16:45 AM


Edit - I removed wicd and re-installed NetworkManager and nm-applet to see if they fail.

What is the exact name or repo location of nm-applet?

Was just about to upload and saw this now I need to redo them..
Title: Re: VSIDO Build 2017
Post by: PackRat on January 23, 2017, 01:34:09 AM
network-manager-gnome (https://packages.debian.org/sid/network-manager-gnome)

lot of packages there - most come in with NetworkManager anyway.

I'll have to do a comparrison with Void. I read a while back that the devs wanted to divorce NetworkManager from gnome and make it stand alone so there would not be as many dependencies as gnome3 progressed with Wayland. Don't know how far they got.

The install in Void did not add that much - Void's package manager/packaging only uses hard dependencies to remain minimal. They over do it a bit sometimes - case in point, Xorg is not a hard dependency for fluxbox  ???. They and some other minimal rolling releases may have trimmed too much which is causing the breakage.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 02:15:37 AM
I like ceni.. :D

Will see what hakerdefo has to say about the applet side of it.. It will not add too much more to the ISO but I do not want to put anything on that is gnome specific and / or obsolete
Title: Re: VSIDO Build 2017
Post by: PackRat on January 23, 2017, 02:36:51 AM
It's not obsolete (maybe just the name).

It is like wicd-gtk; if you do a lot of roaming it's handy to have it sitting in the tray. Better than wicd in some critical ways - hackerdefo pointed those out when he requested it replace wicd. Bit higher in resource usage, but not really a deal breaker.

I
Quote
I like ceni..

so do I; if you're on a desktop, or do very little roaming it's the way to go. Never understood why it's not in Debian's official repos.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 02:43:05 AM
I'll add the manager .. it is really tiny in what it adds ...
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 03:05:44 AM
It's not obsolete (maybe just the name).

It is like wicd-gtk; if you do a lot of roaming it's handy to have it sitting in the tray. Better than wicd in some critical ways - hackerdefo pointed those out when he requested it replace wicd. Bit higher in resource usage, but not really a deal breaker.

You know or have the specific Fluxbox startup command needed to get this going?  I have not used this in years and do not know
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 03:19:38 AM

You know or have the specific Fluxbox startup command needed to get this going?  I have not used this in years and do not know

Found it

Code: [Select]
nm-applet &
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 04:27:18 AM
Latest test ISO's are uploading

(http://www.zimagez.com/miniature/screenshot2017-01-2304-22-40.png) (http://www.zimagez.com/zimage/screenshot2017-01-2304-22-40.php)

2 Minute 47 Seconds to install.. not bad, not bad at all
Title: Re: VSIDO Build 2017
Post by: PackRat on January 23, 2017, 02:54:28 PM

You know or have the specific Fluxbox startup command needed to get this going?  I have not used this in years and do not know

Found it

Code: [Select]
nm-applet &

I usually run it last (after tint2 anyway) with a sleep

Code: [Select]
(sleep 2s && nm-applet) &
As I recall, that was because the icon failed to show, or it was too big; making sure the tint2 system tray was running first fixed it.

Title: Re: VSIDO Build 2017
Post by: PackRat on January 23, 2017, 02:56:22 PM
Did you drop lvm2 from the default install? I don't see it on your list posted earlier.

No big deal, but doesn't the installer ask if the user wants to set up lvm?
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 03:08:04 PM
^ added now.. and please use the attached file to look through for anything else missuing

I had already added the sleep sections but will move it to last on the startup

Thanks Rat-Man
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 03:11:30 PM
Did you drop lvm2 from the default install? I don't see it on your list posted earlier.

No big deal, but doesn't the installer ask if the user wants to set up lvm?

Perfect example of where I can use the new hakerdefo vchroot script (http://vsido.org/index.php?topic=1267.msg14401#msg14401) to install lvm2 to the two build environments without booting to either one of them
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 03:23:17 PM
I moved the ongoing installed list and progress / status to the first message of this thread to make it easier to edit, share and find (http://vsido.org/index.php?topic=1260.msg14309#msg14309)
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 03:40:47 PM
@PackRat

On installing lvm2 I noticed this requirement:

Code: [Select]
service mountdevsubfs has to be enabled to start service lvm2
Is there another need or package for lvm2? Or does this happen on a restart?
Title: Re: VSIDO Build 2017
Post by: PackRat on January 23, 2017, 04:10:19 PM
The service should start when you reboot, then you can create the lvm drives.

You should be able to do a systemd start <service> to get it going.

I just installed lvm2 on a clean install of VSIDO test iso, didn't get that message.

Having issue with the locale though, and getting that 1 min 30 sec wait issue becuase of separate /home and or swap file. Sorting that out at the moment.

htop wasn't in the default install - didn't it use to be?
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 04:15:52 PM
Yes... and I just added htop back

I gut locale in the install process.. may need to just reinstall it and leave it be

I will also look at the script and add the correct systemd fstab parameters to stop that 90 second bullshit
Title: Re: VSIDO Build 2017
Post by: PackRat on January 23, 2017, 04:23:49 PM
I used hackerdefo's fix from that thread a while back.

It boots and everything is mounted.

Code: [Select]
dpkg-reconfigure locale
worked.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 05:07:53 PM
@PackRat what were the issues with locale?
Title: Re: VSIDO Build 2017
Post by: PackRat on January 23, 2017, 05:54:17 PM
aot-get install and dist-upgrade were sending an error that the locale (LOCALE) couldn't be determined and to make sure LC= was set.

I did the recommended "dpkg-reconfigure locale" from the Debian wiki, fixed the issue.

en_us_UTF8 was the only locale selected (which is correct) but at the end, I had to select it as the default - there were a couple other locales I could have selected. I'll try and get back to that computer later and see if the list is still there.

apt works fine now.
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 23, 2017, 06:47:20 PM
We need NetworkManager in VSIDO-LITE but not the "network-manager-gnome" package. That is a super-bloat! I would suggest you to drop it. IMO All we need is the following items,
Code: [Select]
network-manager modemmanager ppp usb-modeswitch usb-modeswitch-data mobile-broadband-provider-info

Create "Network-Manager.desktop" file under "/usr/share/applications" with the following content,

Code: [Select]
[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=Network-Manager
Comment=Manage Network Connections
Exec=xfce4-terminal -e nmtui
Icon=

In the above file only thing you'll have to do is add path to "Icon=".
Next just add the entry for this in Fluxbox Menu.
Who needs "nm-applet" and the bloat of  "network-manager-gnome" when "nmtui" is there.
Seriously remove "network-manager-gnome" package and add the packages I mentioned early in the post if they are not there.
Cheers!!!
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 23, 2017, 07:24:39 PM
Okay a task for Vastone if he doesn't mind :)
Create three test builds. First with "wicd"
Second with "network-manager"
Third with "network-manager-gnome"
And on the both second and third builds make sure following packages are also installed,
"modemmanager" "ppp" "usb-modeswitch" "usb-modeswitch-data" "mobile-broadband-provider-info"
And give us the size of three builds and resource usages of three builds via htop (cpu and ram) when connected to a wifi router without any extra running app.
Please Vasty do this ;)
Cheers!!!
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 07:32:40 PM
I will do this but why is wicd even in the equation?

As far as I am concerned ceni is the standard and NM going forward
Title: Re: VSIDO Build 2017
Post by: VastOne on January 23, 2017, 11:36:13 PM
Okay a task for Vastone if he doesn't mind :)
Create three test builds. First with "wicd"
Second with "network-manager"
Third with "network-manager-gnome"
And on the both second and third builds make sure following packages are also installed,
"modemmanager" "ppp" "usb-modeswitch" "usb-modeswitch-data" "mobile-broadband-provider-info"
And give us the size of three builds and resource usages of three builds via htop (cpu and ram) when connected to a wifi router without any extra running app.
Please Vasty do this ;)
Cheers!!!

I added both gnome settings (incredibly small) and modemmanager ppp usb-modeswitch usb-modeswitch-data  mobile-broadband-provider-info and the ISO increased by 5 MiB which is very small

I also fixed the locale issue (thanks Rat-Man) and have them built and tested.. will upload a bit later

ISO size now is 377 x64 and the x32 is 382
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 24, 2017, 05:58:10 AM
I'm interested in ram-cpu usage when connected to wireless via nm-applet, nmtui and wicd. If you don't want to build you can test the wicd resource usage via the regular build of VSIDO. Next remove nm-applet from the autostart in the test-build install and connect to wifi using nmtui and check the cpu-ram usage and finally re-add the nm-applet to autostart, connect to wifi using the applet and check the cpu-ram usage.
I'm interested in these numbers ;)
Cheers!!!
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 24, 2017, 06:07:12 AM
p.s. nm-applet is infamous for consuming resources. It can guzzle RAM in amount of 75-200 MB. Even Debian WIKI on ARM build suggests removing the applet for this reason. This is why I'm interested in those numbers.
Title: Re: VSIDO Build 2017
Post by: PackRat on January 24, 2017, 04:00:51 PM
Added network-manager and firefox-esr to the next levels.. increased each ISO 50 MiB which is not that bad.. both will come in at 375 mark now...

Building them and will upload them as soon as they are done

Can you boot into a session and check that. The current build of firefox-esr (45.6) on Void is broken - can't connect to any google servers or wikipedia. The current build of firefox (51.0) is all good. Don't know if Debian is effected.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 24, 2017, 04:06:30 PM
p.s. nm-applet is infamous for consuming resources. It can guzzle RAM in amount of 75-200 MB. Even Debian WIKI on ARM build suggests removing the applet for this reason. This is why I'm interested in those numbers.

I will do this today... and get the ISO's out

I do not use any machine in my build environment on wifi so I am not sure I can test the way needed.. unless of course you only want to see it loaded and not necessarily used
Title: Re: VSIDO Build 2017
Post by: VastOne on January 24, 2017, 04:10:54 PM

Can you boot into a session and check that. The current build of firefox-esr (45.6) on Void is broken - can't connect to any google servers or wikipedia. The current build of firefox (51.0) is all good. Don't know if Debian is effected.

Logged in now and accessing my gmail and google search for VSIDO PackRat and all over Wikipedia...

Not an issue with this build
Title: Re: VSIDO Build 2017
Post by: VastOne on January 24, 2017, 04:13:46 PM
Can anyone tell me what it is that ceni cannot do?
Title: Re: VSIDO Build 2017
Post by: PackRat on January 24, 2017, 04:15:21 PM
I just checked on my desktop - also Void. Firefox-esr was fine until an upgrade to the nss package (don't know what the Debian eqivalent is named) came through and borked it. Hopefully won't effect Debian.
Title: Re: VSIDO Build 2017
Post by: PackRat on January 24, 2017, 04:21:11 PM
Can anyone tell me what it is that ceni cannot do?

I am not sure if it will recognize a hidden wirelss network - same with nmtui, which is a ceni-like interface for NetworkManager. I have had issues with wicd connecting to one, nm-applet handled it just fine.

I have never tried to use my phone as a wireless hotspot so I don't know how ceni or wicd compare with NetworkManager - which appears to be the way to go for those that do that; can be handy if you travel a lot.

Other than that, ceni is an awesome tool. A bit inconvenient if you do a lot of roaming - like a university student who may connect to several wireless networks on any given day - because you have to go through the motions. Cannot be beat for a Debian desktop that stays put.
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 24, 2017, 05:36:46 PM
@PackRat to use nmtui with hidden wirelss try this,

nmtui -> Edit connection -> Add -> Wifi -> hidden_wifi_name -> Autometic -> OK

Next do,


nmtui -> Edit connection ->  hidden_wifi_name -> Activate

Cheers!!!
Title: Re: VSIDO Build 2017
Post by: jedi on January 25, 2017, 01:50:44 AM
From the wireless perspective, my experience with NetworkManager has not been very good.  I have a KDE Plasma install on a basic VSIDO build that uses Network-Manager and nm-applet and I've finally gotten rid of it and went back to Wicd.

Ceni is by far the lightest choice, and out of the box easily handles almost all wifi needs.  I have not really tried, but have never had an icon indicator that would work with ceni.  Another non-issue for me.  Ceni is easily reconfigured as well.  Just run it again!

On my goto lappy, I'm currently using Wicd-gtk.  Just because.  No really valid reasoning behind it, just what was the easiest choice at the moment this install occured back in November.  Another strong point in Wicd's favor is the ease of getting the systray icon to work so you can see your connected.  I think they call that 'icing'!

Network-Manager is pretty and all, but in the end on my equipment, I've always found a way to break it.  I can't think of a time I ever broke ceni.  Can't say the same for Wicd, it breaks too!  (Wicd broke on my wifes lappy just yesterday.)

For a VSIDO LITE I'd think for those of us with wireless, (and using Sid as well) that ceni would suffice just fine.  This is Linux though, and we can all do an apt-get!  The beauty of the tiny distro.  Build as you please!

Did I mention that vchroot is quite possibly the niftiest tool to grace our /usr/local/bin?  Well it is!!!  Good-bye reFind...
Title: Re: VSIDO Build 2017
Post by: VastOne on January 25, 2017, 02:14:02 AM
Good info Jedi... I am building ISO's with NM and nmtui... if nm-applet is as nasty as stated it does not get a space in this discussion at all and as I stated I cannot test wifi since I am desktop anchored to a wire

Title: Re: VSIDO Build 2017
Post by: VastOne on January 25, 2017, 05:17:45 AM
I have uploaded the latest VSIDO Lite test ISO's (http://www.nixnut.com/vsido/test/VSIDO_Lite_Tests/)

NM is installed and nmtui is a menu item under Internet

Small and fast with everything but Multimedia components that VSIDO regular has...

Check it out and please test all that hakerdefo has asked for
Title: Re: VSIDO Build 2017
Post by: PackRat on January 25, 2017, 03:45:46 PM
Live session running. Can get the wireless going with either Ceni or nmtui.

Is this network setup HowTo (http://vsido.org/index.php?topic=185.0) now obsolete, so a new one needs to be written once the iso is finalized?

Also, now that the system tray is empty by default, it's a bit confusing why windows do not maximize even after conky is killed.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 25, 2017, 04:20:44 PM
Does being empty mean that it is not there though? Chicken and the egg I know but I do not know this answer

As this goes forward we may have to rewrite a lot of things, including the papers needed to commit me to a local insane asylum

 :D ;D ??? ??? ???
Title: Re: VSIDO Build 2017
Post by: PackRat on January 25, 2017, 04:46:52 PM
It's there since the window won't maximize - system trays and tint2 are a type of window (like conky). In tilers, the user has to account for them, or they get tiled into the window stack etc ...

Installing to metal.

Install was smooth. I get that 1.5 min stall, but everything mounted. I did it a bit different this time and used the old-school fstab, not the UUID just to see if that made a difference.

Tinker around a bit and see what happens.
Title: Re: VSIDO Build 2017
Post by: jedi on January 25, 2017, 05:09:59 PM
Just a quick glance through the above mentioned 'howto' and looks as if it is still applicable.  If anyone sees anything I'm not let me know and I'll be happy to rewrite it.
Title: Re: VSIDO Build 2017
Post by: jedi on January 25, 2017, 05:11:15 PM
A quick disclaimer about that above post, I'll not be able to be of help writing a 'howto' about NM.  I just don't have enough experience with it and haven't ever had much luck with it either tbh...
Title: Re: VSIDO Build 2017
Post by: VastOne on January 25, 2017, 05:29:58 PM
One thing that may need to be changed... ifconfig -a no longer works ... yet another debian deprecation

Code: [Select]
ip a
is the replacement and though smaller to type, uglier to view

installing net-tools will get you ifconfig usage back and I will install that on next round of ISO's

This is only on these test ISO's.. everything is the same and functional on the released ISO's
Title: Re: VSIDO Build 2017
Post by: jedi on January 25, 2017, 05:34:46 PM
One thing that may need to be changed... ifconfig -a no longer works ... yet another debian deprecation

Code: [Select]
ip a

Try 'sudo ifconfig -a' and let me know what happens...  (works perfectly here)

EDIT: my bad, didn't read to the end of your post VastOne!  Sorry, too tired!  Too much snow!!!
Title: Re: VSIDO Build 2017
Post by: PackRat on January 25, 2017, 05:41:53 PM
^
Code: [Select]
ifconfig: command not found
clean install latest iso

synaptic not in default install; that by design?
Title: Re: VSIDO Build 2017
Post by: VastOne on January 25, 2017, 05:44:10 PM
Haven't got around to synaptic yet and evaluating the need for it

ifconfig is deprecated and and if you want it back

Code: [Select]
apt-get install net-tools
Title: Re: VSIDO Build 2017
Post by: VastOne on January 25, 2017, 05:49:40 PM
I must say again the new vchroot tool that hakerdefo made is unbelievable..

When I need to add a simple tool to the ISO's it is so damned nice to not have to boot into all of them.. this tool makes it a breeze... so damned easy

Takes one of the most complex ideas (chroot) and makes it a practical use tool

Thank you hakerdefo!!!!
Title: Re: VSIDO Build 2017
Post by: VastOne on January 25, 2017, 05:59:21 PM
What is the real need for synaptic?  A gui for terminal and dpkg?  I never ever use it so I need to know

aptitude is not even installed yet ... and everything functions at a normal level to what I do

So this is a legit question.. why do we need synaptic?  It adds 13.3 MiB of additional space for what?
Title: Re: VSIDO Build 2017
Post by: jedi on January 25, 2017, 06:39:50 PM
Never used it.   ;D
Title: Re: VSIDO Build 2017
Post by: PackRat on January 25, 2017, 07:10:32 PM
No need other than a gui; it can be handy to find the actual file name of a package you're looking to install.

Didn't it use to be default? Just curious if it was dropped.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 25, 2017, 07:13:54 PM
It is the default in Standard VSIDO and will remain so until if and when any of this expedition changes the Standard VSIDO

Chicken and the egg again?
Title: Re: VSIDO Build 2017
Post by: VastOne on January 25, 2017, 07:16:57 PM
I just setup these two aliases and honestly I do not know why I never thought of it before

Code: [Select]
alias ins='sudo dpkg -i ./*.deb'
alias deins='sudo dpkg -r ./*.deb'

The setup is clumsy though IMO.. The method for this would work for a single deb file in a directory but if there were more it would install more

Open to options
Title: Re: VSIDO Build 2017
Post by: PackRat on January 26, 2017, 08:13:54 PM
LVM is working OOTB.

For some reason, my #2 and #3 harddrives were assigned /dev/sde and /dev/sdg - usually it's the usual sdb and sdc. May have something to do with the sd-card reader I installed.

Also, in fstab, the LVM needs the fix like /home and swap or there will be the minute-thirty delay issue.

(http://en.zimagez.com/miniature/vsido-test.jpg) (http://en.zimagez.com/zimage/vsido-test.php)
Title: Re: VSIDO Build 2017
Post by: VastOne on January 26, 2017, 08:39:40 PM
^ Thanks for the heads up.. I am testing now how to change fstab settings.. not sure if the best approach is to alter the script or an after install function

That looks really good...

What are you booting to as far as memory use?  I have seen as low as 65 Mib on tests
Title: Re: VSIDO Build 2017
Post by: VastOne on January 26, 2017, 08:53:20 PM
@RatMan..

What is your minimal for Multimedia setup? What is your must haves is what I mean... that's my next level
Title: Re: VSIDO Build 2017
Post by: PackRat on January 26, 2017, 09:20:32 PM
For the recent screenshot, I have installed:

Code: [Select]
alsa-base
alsa-utils

audacious    <- gmusicbrowser is good
audacious-plugins
moc
mpv
asunder
hexchat

libdvdcss
gstreamer-plugins good, bad, and ugly 1.0
ffmpeg
moc-ffmpeg-plugin
flac
lame
sox

and the various dependencies that pulled in with those.

pretty much does what I need it to do. I get way better sound with just alsa.

To get to the 2.8G, I also have hexchat, gphoto2, a couple other cli apps installed, and the packages to build a custom kernel. I found some references to a kernel config option to prevent that minute-thirty delay so I went ahead and built a custom kernel. So that 2.8G includes those packages and 3 kernels with headers. Figure ~2.5G basic setup with multimedia.
Title: Re: VSIDO Build 2017
Post by: PackRat on January 26, 2017, 09:23:35 PM
Drop conky you say?

For the lite edition, why not drop conky? It should also remove any lua dependencies. You have nothing other than conky that needs lua installed correct? Save some space there.
Title: Re: VSIDO Build 2017
Post by: PackRat on January 26, 2017, 11:07:14 PM
Quote
What are you booting to as far as memory use?  I have seen as low as 65 Mib on tests

With network-manager running I was idling at 112 Mib with 2 terminals open.

This computer is hard-wired, no wireless, so i uninstalled network-manager and used ceni - idles at 107 Mib.

That's with lvm2 services running, so without that I can probably idle at ~100 Mib or maybe less.
Title: Re: VSIDO Build 2017
Post by: PackRat on January 27, 2017, 12:00:18 AM
I'll post this here, although it's more about this thread and the 1 min 30 sec boot delay. (http://vsido.org/index.php?topic=1217.0)

@vastone - is this line from the /etc/fstab actually needed for VSIDO?

Code: [Select]
proc /proc proc defaults 0 0
From the Debian wiki for fstab - (https://wiki.debian.org/fstab)

Quote
It is not necessary to list /proc and /sys in the fstab unless some special options are needed. The boot system will always mount them.

If you comapre the fstab for VSIDO that jed posted in the "A Start Job is running..." thread, he has the entry in fstab.
For the clean Debian testing I installed that entry no longer exists. (http://vsido.org/index.php?topic=1217.msg13718#msg13718)

I went ahead and copmmented the proc entry in the /etc/fstab for this install of vsido-lite and changed the options back to "default" for /home and lvm.
Reboot and no 1 min 30 sec delay, or errors/warning related to mounting.

Depricated entry messing with systemd?
Title: Re: VSIDO Build 2017
Post by: VastOne on January 27, 2017, 12:11:55 AM
^ thank you PackRat.. that narrows my search and solution down to a single setting which makes it hella lot easier

I appreciate that!
Title: Re: VSIDO Build 2017
Post by: PackRat on January 27, 2017, 12:23:28 AM
No problem.

Everything mounted and sitting at 108 MiB when all said and done; even with the dreaded conky 1.10 running:

(http://en.zimagez.com/miniature/vsido-lite-01272017-b.png) (http://en.zimagez.com/zimage/vsido-lite-01272017-b.php)

gimp, transmission, and filezilla installed now. Pretty much complete sysrtem for me at 2.6G; rip some music and set up an NFS server - maybe get to it tomorrow.

Well played vastone.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 27, 2017, 03:42:05 PM
Thank you RatMan...

No the proc line is not needed on the VSIDO fstab line and I am asking why it is necessary over at refracta (http://refracta.freeforums.org/proc-line-in-fstab-t685.html#p6445)
Title: Re: VSIDO Build 2017
Post by: PackRat on January 27, 2017, 04:48:36 PM
VSIDO-lite is pretty nice.

(http://en.zimagez.com/miniature/traficscreenshot2017-01-2711-43-52.png) (http://en.zimagez.com/zimage/traficscreenshot2017-01-2711-43-52.php)

Recognized my hardware out of the box, but this is an older machine. I did notice that the linux-firmware packages weren't included. Maybe cause some issues with newer machines?
Title: Re: VSIDO Build 2017
Post by: VastOne on January 27, 2017, 04:52:32 PM
Is linux-firmware a meta package?  One install for all I mean?

Will add it back if it is an absolute...

Thanks
Title: Re: VSIDO Build 2017
Post by: VastOne on January 27, 2017, 04:55:01 PM
Drop conky you say?

For the lite edition, why not drop conky? It should also remove any lua dependencies. You have nothing other than conky that needs lua installed correct? Save some space there.

I can do this too.. but is lua really a lot of packages?  Legit question, I have never looked..   ???
Title: Re: VSIDO Build 2017
Post by: PackRat on January 27, 2017, 05:05:59 PM
Is linux-firmware a meta package?  One install for all I mean?

Will add it back if it is an absolute...

Thanks

I believe it is - there are three packages actually

firmware-linux
firmware-linux-free
firmware-linux-nonfree

I think firmware-linux grabs both free and nonfree packages - is it apt-get --simulate that will do a dry run to see what gets installed?

There are also individual selections; firmware-realtek and firmware-atheros are the big 2 since that will cover just about every network card. There are some broadcom packages too, I think firmware-linux grabs those.

EDIT - my Void desktop has successfully mounted the VSIDO NFS share and currently playing Pink Floyd Animals   ;D
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 27, 2017, 05:11:00 PM
Code: [Select]
firmware-linuxis a meta-package that should be there in VSIDO. Plus add this one also,
Code: [Select]
firmware-misc-nonfreeNow coming to conky,
Code: [Select]
conky-allpackage will fetch
Code: [Select]
liblua5.1-0which is not lua persay but only runtime libs.
Cheers!!!
Title: Re: VSIDO Build 2017
Post by: PackRat on January 27, 2017, 05:12:30 PM
I can do this too.. but is lua really a lot of packages?  Legit question, I have never looked..   ???

Run apt and see what the deps for conky-all are. I suspect it has to be pulling some lua, cairo, imlib etc ... to run everything. Other packages probably need imlib2 and cairo, but as far as I know, conky is the only app on the system in need of any lua.

@hackerdefo - I just looked that up, that liblua package is the only lua installed.

terminal output - apt-cache:

Code: [Select]
conky-all
  Depends: libaudclient2
  Depends: libc6
  Depends: libcairo2
  Depends: libcurl3-gnutls
  Depends: libdbus-glib-1-2
  Depends: libgcc1
  Depends: libglib2.0-0
  Depends: libimlib2
  Depends: libiw30
  Depends: liblua5.1-0
  Depends: libncurses5
  Depends: libpulse0
  Depends: librsvg2-2
  Depends: libstdc++6
  Depends: libtinfo5
  Depends: libx11-6
  Depends: libxdamage1
  Depends: libxext6
  Depends: libxfixes3
  Depends: libxft2
  Depends: libxinerama1
  Depends: libxml2
  Depends: libxmmsclient6
  Depends: libxnvctrl0
  Conflicts: conky-cli
  Conflicts: conky-std
  Breaks: conky
  Suggests: apcupsd
  Suggests: audacious
  Suggests: moc
  Suggests: mpd
  Suggests: xmms2
  Replaces: conky
  Replaces: conky-cli
  Replaces: conky-std
doug@VSIDO-01:~$ apt-cache rdepends conky-all
conky-all
Reverse Depends:
  conky-all-dbg
  conky-std
  conky-std
  conky-cli
  conky-cli
  conky

apt-get purge conky-all

Code: [Select]
[The following packages were automatically installed and are no longer required:
  libaudclient2 libiw30 libxmmsclient6 libxnvctrl0
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  conky-all*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded./code]

Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 27, 2017, 05:18:33 PM
Thank you RatMan...

No the proc line is not needed on the VSIDO fstab line and I am asking why it is necessary over at refracta (http://refracta.freeforums.org/proc-line-in-fstab-t685.html#p6445)
Can you post the refracta installer scripts somewhere? They are bash scripts and I think we can fix the problem on our own.
Cheers!!!
Title: Re: VSIDO Build 2017
Post by: VastOne on January 27, 2017, 05:26:35 PM
Can you post the refracta installer scripts somewhere? They are bash scripts and I think we can fix the problem on our own.
Cheers!!!

The files are always left on any VSIDO install and on obviously the LiveCD... I have several that I am working on right now and will post them later (nvme, uefi, and standard)

I know how to eliminate the proc lines already, as a matter of fact it is an easy fix.. what I am trying to do is have it fixed upstream so I do not have to make so many edits when there are updates.. Right now with the snapshot tool and the installer this is what I have to perform:

refracta update steps

Quote
1st - install the new updates
2nd - check the following and make necessary changes

Edit    /etc/refractainstaller.conf

make sure window_title= is"

window_title=" VSIDO Installer "

Edit    /etc/refractasnapshot.conf

make sure snapshot_basename is:

snapshot_basename="VSIDO_x32"

Change edit_boot_menu="no" to edit_boot_menu="yes"

Change

#mksq_opt="-comp xz"

to

mksq_opt="-comp xz -Xbcj x86 -no-recovery -always-use-fragments -b 1048576"

find and uncomment

netconfig_opt="ip=frommedia"

____

/usr/lib

Edit /usr/lib/refractainstaller/post-install/cleanup-install.sh

put back

rm -rf /target/usr/share/initramfs-tools/hooks/live
rm -f /target/home/*/.config/vsido/vsido-welcome
mv /target/home/*/.fluxbox/menu1 /target/home/*/.fluxbox/menu

at the end BEFORE done

____


Edit /usr/lib/refractasnapshot/snapshot_exclude.list

Add

# - /home/vsido
- /home/remastersys
- /usr/share/doc

and uncomment this

- /home/*/.[a-z,A-Z,0-9]*

____

Add three files from x32 save directory to /usr/lib/refractasnapshot/iso/isolinux

menu.cfg
live.cfg
splash.png

____

/usr/bin

Edit /usr/bin/refractainstaller-yad

Replace

 This utility will install a
 
 with
 
  This will install VSIDO V-Ger x32 to your system


 This is free software that comes with no warranty or,
 of any type, including but not limited to express, implied, \n merchantability or fitness of purpose.
 ${custom_text}

 Copyright 2011-2014 fsmithred@gmail.com,
 based on refractainstaller-8.0.3 by Dean Linkous. \n Version: $version \n\n\
 ${custom_text}
"
mode="$?"
   case $mode in
      0) install="simple" ;;
      1) install="expert" ;;
      2) exit 0 ;;
   esac
__________   


**** Search and find:

rm -f /target/boot/grub/setup_left_core_image_in_filesystem


Add this after:

rm -rf /TARGET/etc/systemd/system/getty@tty1.service.d
rm -rf /TARGET/etc/systemd/system/getty@tty2.service.d
rm -rf /TARGET/etc/systemd/system/getty@tty3.service.d
rm -rf /TARGET/etc/systemd/system/getty@tty4.service.d
rm -rf /TARGET/etc/systemd/system/getty@tty5.service.d
rm -rf /TARGET/etc/systemd/system/getty@tty6.service.d

________

*** Add this as replacement at the end for a reboot on end of install

yad --image=gtk-dialog-info --title="$window_title" --text=$" Your VSIDO installation is complete. \n\n If everything went well you should have your new system installed and ready.\n\n Your system will reboot now.\n" --width=500 --button="OK":0

# copy error log to installation now before calling cleanup function
cp "$error_log" /target/home/"$newusername"/
chown 1000:1000 /target/home/"$newusername"/"${error_log##*/}"
cleanup

reboot

____

Edit /usr/bin/refractasnapshot-gui

Change md5 to this


filename="$snapshot_basename"-$(date +%Y%m%d_%H%M).iso

filename="$snapshot_basename"_$(date +%d%b%Y).iso

_____

Search for Pause to edit - add this on next line

chroot /home/work/myfs/ /home/vsido/remvsido.sh
__________

Edit /usr/lib/refractasnapshot/iso/isolinux/live.cfg and change union=aufs to union=overlay

Should be all
   
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 27, 2017, 05:34:50 PM
...I know how to eliminate the proc lines already, as a matter of fact it is an easy fix...
V'ger sees it all ;)
Cheers!!!
Title: Re: VSIDO Build 2017
Post by: VastOne on January 27, 2017, 05:52:12 PM
Thank you RatMan...

No the proc line is not needed on the VSIDO fstab line and I am asking why it is necessary over at refracta (http://refracta.freeforums.org/proc-line-in-fstab-t685.html#p6445)
Can you post the refracta installer scripts somewhere? They are bash scripts and I think we can fix the problem on our own.
Cheers!!!

Already solved by the refracta developer (http://refracta.freeforums.org/proc-line-in-fstab-t685.html#p6447) who will now be included it on the next build

Cheers!
Title: Re: VSIDO Build 2017
Post by: VastOne on January 28, 2017, 04:36:50 PM
I'll post this here, although it's more about this thread and the 1 min 30 sec boot delay. (http://vsido.org/index.php?topic=1217.0)

@vastone - is this line from the /etc/fstab actually needed for VSIDO?

I installed a new system that stalled for the 90 seconds.. I went into tty1 and edited fstab and removed that proc line and still got the delay

It was not until I added the these hakerdefo suggestions that it stopped

Code: [Select]
noauto,x-systemd.automount,x-systemd.device-timeout=2 0 2
I saw this on a new build of uefi vsido install ... test stuff ... I am waiting for a new release from refracta to test again and will let you know

I am also curious as to why I never ever see this on v-box installs and tests but every single time on a metal install
Title: Re: VSIDO Build 2017
Post by: PackRat on January 28, 2017, 04:45:36 PM
The Automount with systemd section (https://wiki.archlinux.org/index.php/Fstab#Automount_with_systemd) gives a brief explanation of using that fix for anyone curious.

@vastone - have you heard anything from Debian about using systemd to handle mounting? I was researching systemd.mount (https://www.freedesktop.org/software/systemd/man/systemd.mount.html) and couldn't find anything definitive - even from Red Hat.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 28, 2017, 05:11:33 PM
^ Nothing but rumors that systemd was phasing out fstab...  I think fstab is past its time and should be replaced and I am ready for it to happen

And then sit back and watch the naysayers have shit fits again

I thought FOSS was about choice?  I get my balls busted (on another site)  for using systemd.. not sure I get it anymore and it is getting old
Title: Re: VSIDO Build 2017
Post by: PackRat on January 28, 2017, 06:40:47 PM
I installed the nvidia driver - the dkms way through the Debian repos. I get this message now when the module is building, and when I did a dist-upgrade which included a kernel upgrade.


Code: [Select]
Setting up dpkg-dev (1.18.20) ...
Setting up linux-kbuild-4.9 (4.9.6-2) ...
Setting up linux-headers-4.9.0-1-amd64 (4.9.6-2) ...
/etc/kernel/header_postinst.d/dkms:
/etc/lsb-release: line 1: V-Ger: command not found

Doesn't appear to stop the module from building, although it seems to take longer tham expected. Maybe a syntax error in the lsb-release file?
Title: Re: VSIDO Build 2017
Post by: PackRat on January 28, 2017, 07:14:49 PM
Bit late, but I went ahead and ran the vsido-welcome script.

Couple of issues.

1. I decided to not install the java so I pressed "s" - skipped the install of java all right, but launched right into an install of libreoffice. I scrolled back and saw the opening screen where is asks if if a user wants to skip or install. The script just assumed I wanted libreoffice. Probably a sticky key on my keyboard. Ever happen before?

2. On the version control list, there are geany and - probably more importantly - thunar-vcs-plugin. Not sure geany is a version control tool, and won't that thunar plugin need to pull in thunar as a dependency? Legacy entry from when thunar was installed by default?

Other than that pretty smooth. After installing gimp (from apt), and cups w/ libreoffice from the welcome script, I'm sitting at 3G install. Pretty svelte.
Title: Re: VSIDO Build 2017
Post by: Snap on January 29, 2017, 07:57:40 AM
Amazing activity here, folks. That's how a team works! I really like the idea of this fat trimmed Vsido release.

If I'm allowed to chime in, now that you're finally fully adapting Vsido to systemd and redoing the exit script accordingly, is consolekit still necessary for anything else? I guess it might be left out of the equation. AFAIK, systemd is completely in charge of the former ck functions. Not sure about polkit. I guess it would be still needed for something.

Quote
Nothing but rumors that systemd was phasing out fstab...  I think fstab is past its time and should be replaced and I am ready for it to happen

Oh, it isn't already? I thought this switch was already completed. Not experienced enough with systemd I'm afraid.
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 29, 2017, 08:13:15 AM
@PackRat,
lsb-release problem could arise because of either of these two,
First the package "lsb - release" is missing.
Second there is a synax problem in "/etc/lsb-release" file. The correct synatx goes something like this,

Code: [Select]
DISTRIB_ID=Debian
DISTRIB_CODENAME=VSIDO
DISTRIB_DESCRIPTION="VSIDO (A Debian Sid Distribution)"
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 29, 2017, 08:17:12 AM
Regarding "vsido-welcome" perhaps time for a new one.
Give me the categories-packages list you would like to see in the "vsido-welcome" script and I can give you a new script :)
Title: Re: VSIDO Build 2017
Post by: hakerdefo on January 29, 2017, 08:26:50 AM
@Snap
consolekit can be dropped but polkit is required.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 29, 2017, 11:16:36 PM
I am taking a bit of a break from the complete heads down mode I have been in for several weeks. I am a wee bit tired

When I feel up to it again I will begin work with the login script

I need to golf and ride my bike.. that would solve a lot

Fucking winter
Title: Re: VSIDO Build 2017
Post by: VastOne on January 30, 2017, 12:07:10 AM
Amazing activity here, folks. That's how a team works! I really like the idea of this fat trimmed Vsido release.

This snap has always been my goal with VSIDO.. to have a think tank type philosophy and a working direction to build from..

I just want to be the 'creator' not the creation... What I have done over the last three weeks is to build (finally) a repeatable and functional build environment.. Now it is easy to implement things and start over just as fast as it is to install VSIDO.. you cannot imagine how different this is now.. For years I have 'hoped' nothing broke the build environment because it was the original creation and honestly I was not sure I could get it back outside of fsarchives.. but that is not a healthy environment depending on others and outside scripts to keep a build alive

That has changed now.. and after a little bit of a break to catch my breath, I want to get back at several different areas where we can all make VSIDO leaner, meaner and better than ever

Thank you all for being a part of this think tank
Title: Re: VSIDO Build 2017
Post by: PackRat on January 30, 2017, 01:59:33 PM
@PackRat,
lsb-release problem could arise because of either of these two,
First the package "lsb - release" is missing.
Second there is a synax problem in "/etc/lsb-release" file. The correct synatx goes something like this,

Code: [Select]
DISTRIB_ID=Debian
DISTRIB_CODENAME=VSIDO
DISTRIB_DESCRIPTION="VSIDO (A Debian Sid Distribution)"

It's installed by default.

original file:

Code: [Select]
DISTRIB_ID=VSIDO V-Ger x32
DISTRIB_RELEASE=V-Ger
DISTRIB_CODENAME=V-Ger
DISTRIB_DESCRIPTION="Debian V-SID-O"

I think that first line should be in quotes - like the last line. I changed it to:

Code: [Select]
DISTRIB_ID=VSIDO
DISTRIB_RELEASE=V-Ger
DISTRIB_CODENAME=V-Ger
DISTRIB_DESCRIPTION="Debian V-SID-O"

and did a dist-upgrade, icluding a kernel upgrade, and didn't see the error. I should have quoted that line, will try that next upgrade.
Title: Re: VSIDO Build 2017
Post by: VastOne on January 30, 2017, 03:05:13 PM
That first line was the only line with a space in it and not quoted... I am guessing that was the issue and will test and modify it

Thanks Packrat
Title: Re: VSIDO Build 2017
Post by: hakerdefo on February 01, 2017, 06:54:16 PM
I don't have the latest VSIDO ISO so can anyone post the output of the following commands from the latest version,

Code: [Select]
cat ~/.config/user-dirs.dirs
cat /etc/xdg/user-dirs.defaults
Title: Re: VSIDO Build 2017
Post by: PackRat on February 02, 2017, 02:37:52 AM
Code: [Select]
cat ~/.config/user-dirs.dirs
# This file is written by xdg-user-dirs-update
# If you want to change or add directories, just edit the line you're
# interested in. All local changes will be retained on the next run
# Format is XDG_xxx_DIR="$HOME/yyy", where yyy is a shell-escaped
# homedir-relative path, or XDG_xxx_DIR="/yyy", where /yyy is an
# absolute path. No other format is supported.
#
XDG_DESKTOP_DIR="$HOME/Desktop"
XDG_DOWNLOAD_DIR="$HOME/downloads"
XDG_TEMPLATES_DIR="$HOME/templates"
XDG_PUBLICSHARE_DIR="$HOME/public"
XDG_DOCUMENTS_DIR="$HOME/documents"
XDG_MUSIC_DIR="$HOME/music"
XDG_PICTURES_DIR="$HOME/images"
XDG_VIDEOS_DIR="$HOME/videos"
XDG_VIDEOS_DIR="$HOME/bin"
XDG_VIDEOS_DIR="$HOME/tmp"
XDG_VIDEOS_DIR="$HOME/backup"

Code: [Select]
$ cat /etc/xdg/user-dirs.defaults
# Default settings for user directories
#
# The values are relative pathnames from the home directory and
# will be translated on a per-path-element basis into the users locale
DESKTOP=Desktop
DOWNLOAD=Downloads
TEMPLATES=Templates
PUBLICSHARE=Public
DOCUMENTS=Documents
MUSIC=Music
PICTURES=Pictures
VIDEOS=Videos
# Another alternative is:
#MUSIC=Documents/Music
#PICTURES=Documents/Pictures
#VIDEOS=Documents/Videos
Title: Re: VSIDO Build 2017
Post by: VastOne on February 02, 2017, 03:06:33 AM
/etc/xdg/user-dirs.defaults is the actual default but is overridden by the initial /etc/skel copy on the very first login of a new user 
Title: Re: VSIDO Build 2017
Post by: VastOne on February 09, 2017, 04:12:42 AM
I have accomplished all that I wanted to do with these builds and processes..

I have a new repeatable build phase by phase process that is also documented

Phase I - Base of VSIDO with a new build of Debian Sid with just the etc/skel and /usr/local/bin and a few other areas (icons and cfg files) inact..these are the guts that are added to give VSIDO the look and assembly

Phase II was to add the most basic back Fluxbox, X11, terminal, SpaceFM

Phase III began the process of what apps were necessary for Network setup and Internet and fundamental tools for restoring or Recovery CD

Phase IV I just completed adding back the basics for multimedia. GMusicBrowser is and installed and is now ully functional. MPV is the video player that also acts as the audio device for music playback in GMB. I was not aware at how powerful MPV was as a media player. In short, it just plays everything

What is shocking to me is that adding the two of those and getting a VSIDO Multimedia build only added 12 more MiB to the ISO's. What I thought would be the most difficult was actually the easiest

They are now uploaded to the test site and are fully functional. (http://www.nixnut.com/vsido/test/VSIDO_Lite_Tests/) I have also cleaned up all the menus..

This could be released as a replacement for VSIDO if I wanted to go that route.. It is more than 200 MiB's smaller than the current full version ISO's

x32 is 374 MiB
x64 is 371 MiB

Mission accomplished
Title: Re: VSIDO Build 2017
Post by: PackRat on February 09, 2017, 03:58:19 PM
Looks good. Real quick boot time to live session.

The menu entry for mpv won't work. You can't just launch mpv, it needs some options (basically what to play).

Code: [Select]
launch mpv
will silently fail, run that in a terminal and you'll see some options along with:

Usage:   mpv [options] [url|path/]filename

Code: [Select]
launch mpv <path to my music directory>     # will start playing files in music (video) directory

launch mpv <path to music/video file>         # will play a particular file

launch mpv dvd://                                       # will play a dvd if libdvdcss is installed

There are some examples in the man page and on their websites for the various options.

Or you can install a frontend for mpv - smplayer which is qt based, or gnome-mpv which is gtk.
Title: Re: VSIDO Build 2017
Post by: VastOne on February 09, 2017, 04:05:13 PM
Correct... I had that listed to edit and forgot it..

Thanks
Title: Re: VSIDO Build 2017
Post by: zephyr on May 27, 2017, 04:57:50 AM
Decided to do a fresh install to metal with the 25May2017 build. Very fast, smooth install.

Wicd has been a pain for many distros so used Ceni without any issues at all.

Would like to comment constructively about the "dual" audio icon for VSIDO volume, reducing the tint2rc panel size from 35 to 32 then to 30 did the trick.  Now have a single icon!
(https://cdn.scrot.moe/images/2017/05/27/Shot-260517-233011.th.png) (https://scrot.moe/image/1kkaj)   (https://cdn.scrot.moe/images/2017/05/27/Shot-260517-232800.th.png) (https://scrot.moe/image/1kNXh)  (https://cdn.scrot.moe/images/2017/05/27/Shot-270517-000546.th.png) (https://scrot.moe/image/1kTBl)
Really very good looking build!
z

Title: Re: VSIDO Build 2017
Post by: VastOne on May 27, 2017, 03:11:46 PM
I will make those changes Z, thanks for digging in and finding it..

I am working this morning updating and adding the new installer and uEFI iso for the lite versions.. have not focused on them in a while since there seemed to be little interest in them

Thanks!
Title: Re: VSIDO Build 2017
Post by: VastOne on May 27, 2017, 09:44:00 PM
ISO's updated, installer updated, all tested and now uploaded including a uEFI lite version