Author Topic: VSIDO Build 2017  (Read 10267 times)

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: VSIDO Build 2017
« Reply #90 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
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

PackRat

  • Posts: 1915
    • View Profile
Re: VSIDO Build 2017
« Reply #91 on: January 27, 2017, 04:48:36 PM »
VSIDO-lite is pretty nice.



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?
I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: VSIDO Build 2017
« Reply #92 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
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: VSIDO Build 2017
« Reply #93 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..   ???
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

PackRat

  • Posts: 1915
    • View Profile
Re: VSIDO Build 2017
« Reply #94 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
I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo

hakerdefo

  • Posts: 520
    • View Profile
    • Looking at Linux through the Windows of Life
Re: VSIDO Build 2017
« Reply #95 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!!!
You Can't Always Git What You Want

PackRat

  • Posts: 1915
    • View Profile
Re: VSIDO Build 2017
« Reply #96 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]

I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo

hakerdefo

  • Posts: 520
    • View Profile
    • Looking at Linux through the Windows of Life
Re: VSIDO Build 2017
« Reply #97 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
Can you post the refracta installer scripts somewhere? They are bash scripts and I think we can fix the problem on our own.
Cheers!!!
You Can't Always Git What You Want

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: VSIDO Build 2017
« Reply #98 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
   
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

hakerdefo

  • Posts: 520
    • View Profile
    • Looking at Linux through the Windows of Life
Re: VSIDO Build 2017
« Reply #99 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!!!
You Can't Always Git What You Want

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: VSIDO Build 2017
« Reply #100 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
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 who will now be included it on the next build

Cheers!
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: VSIDO Build 2017
« Reply #101 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.

@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
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

PackRat

  • Posts: 1915
    • View Profile
Re: VSIDO Build 2017
« Reply #102 on: January 28, 2017, 04:45:36 PM »
The Automount with systemd section 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 and couldn't find anything definitive - even from Red Hat.
I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: VSIDO Build 2017
« Reply #103 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
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

PackRat

  • Posts: 1915
    • View Profile
Re: VSIDO Build 2017
« Reply #104 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?
I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo