Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - VastOne

#421
Larry has written an incredible VSIDO review here.

I am truly humbled by this.. Thank you Larry!

#422
The ISO was updated, built, installed, tested and uploaded with no issues this afternoon.  The primary changes were:

1 - Debian kernel updated to 3.8.3 from Experimental.  Any current VSIDO user wanting to get this just needs to do a

sudo apt-get update && sudo apt-get dist-upgrade

2 - Everything updated to the latest (2013-03-22 10:01 CST) levels of SID

3 - Updated the ISO and somd5 checksum file names to the correct level - Thanks Blaze!

VSIDO kernel 3.8 - Latest Upload 2013-03-22 10:01 CST

isomd5 checksum file - Latest Upload 2013-03-22 10:01 CST
#423
Several new git updates today

To update your git version of GMB to these latest changes simply follow this procedure in terminal

cd gmusicbrowser
git pull

#424
The ISO was updated, built, installed, tested and uploaded with no issues this afternoon.  The primary changes were:

1 - Installed lvm2 so easy lvm can be setup on the install, thanks xaos52!

2 - Fluxbox has now been made the primary WM of VSIDO.  Fluxbox will be the WM first seen on a LiveCD and Fluxbox will be the shown as the default on a first time login once installed.  Of course this can be changed to Xfce or OpenBox by using the drop down menu


#425
The ISO was updated, built, installed, tested and uploaded with no issues this afternoon.  The primary changes were:

1 - Updated the kernel to the latest Debian Stable kernel of 3.8.2

If you want to update to this kernel just do the following

sudo apt-get -t experimental install linux-headers-3.8-trunk-all-amd64

sudo apt-get -t experimental install linux-image-3.8-trunk-amd64


then

sudo update-grub

In my tests the kernel was running in a lot less ram and cpu usage
#426
The ISO was updated, built, tested and installed with no issues this morning.  The primary changes were:

1 - Added icons to the Fluxbox menus.  There is a menu_no_icons file in the same ~/.fluxbox directory if you do not want icons, simply rename it to menu after you remove the current menu file

2 - Added Fluxmenu, a very nice menu creation applet that modifies the Fluxbox menu

3 - Updated to the latest SID levels

___________________________________

Here are the changes for those who do not want to install new... I may or may not script this later...  This process was test by jedi, thank you!   :)

Make sure you back up your ~/.fluxbox/menu

menu - Save this to ~/.fluxbox

fluxmenu - Extract this to ~/

Extract all of these to /usr/share/icons/LinuxLex-8/apps

#427
Light patch to bring code up to latest level of Sid repository, installation of mesa-utils and replacing vsido-exit with the script that tlinsley created that handles both OpenBox and FluxBox environments

Thank you tlinsley for the script and Sector11 for the heads up on the need for mea-utils, great work!

I will not be adding a script for these

sudo apt-get install mesa-utils

and edit/usr/bin/vsido-exit as root and replace it with this:

#!/usr/bin/env python

import pygtk
pygtk.require('2.0')
import gtk
import os
import getpass

class cb_exit:
def disable_buttons(self):
self.cancel.set_sensitive(False)
self.logout.set_sensitive(False)
self.suspend.set_sensitive(False)
self.reboot.set_sensitive(False)
self.shutdown.set_sensitive(False)

def cancel_action(self,btn):
self.disable_buttons()
gtk.main_quit()

def logout_action(self,btn):
self.disable_buttons()
for line in os.popen("wmctrl -m"):
parts = line.split()
if parts[0] == "Name:":
wmName = parts[1].lower()
self.status.set_label("Exiting " + wmName + ", please standby...")
os.system("killall " + wmName)

def suspend_action(self,btn):
self.disable_buttons()
self.status.set_label("Suspending, please standby...")
os.system("cb-lock")
os.system("dbus-send --system --print-reply --dest=\"org.freedesktop.UPower\" /org/freedesktop/UPower org.freedesktop.UPower.Suspend")
gtk.main_quit()

def reboot_action(self,btn):
self.disable_buttons()
self.status.set_label("Rebooting, please standby...")
os.system("dbus-send --system --print-reply --dest=\"org.freedesktop.ConsoleKit\" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart")

def shutdown_action(self,btn):
self.disable_buttons()
self.status.set_label("Shutting down, please standby...")
os.system("dbus-send --system --print-reply --dest=\"org.freedesktop.ConsoleKit\" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop")

def create_window(self):
self.window = gtk.Window()
title = "Log out " + getpass.getuser() + "? Choose an option:"
self.window.set_title(title)
self.window.set_border_width(5)
self.window.set_size_request(500, 80)
self.window.set_resizable(False)
self.window.set_keep_above(True)
self.window.stick
self.window.set_position(1)
self.window.connect("delete_event", gtk.main_quit)
windowicon = self.window.render_icon(gtk.STOCK_QUIT, gtk.ICON_SIZE_MENU)
self.window.set_icon(windowicon)


#Create HBox for buttons
self.button_box = gtk.HBox()
self.button_box.show()

#Cancel button
self.cancel = gtk.Button(stock = gtk.STOCK_CANCEL)
self.cancel.set_border_width(4)
self.cancel.connect("clicked", self.cancel_action)
self.button_box.pack_start(self.cancel)
self.cancel.show()

#Logout button
self.logout = gtk.Button("_Log out")
self.logout.set_border_width(4)
self.logout.connect("clicked", self.logout_action)
self.button_box.pack_start(self.logout)
self.logout.show()

#Suspend button
self.suspend = gtk.Button("_Suspend")
self.suspend.set_border_width(4)
self.suspend.connect("clicked", self.suspend_action)
self.button_box.pack_start(self.suspend)
self.suspend.show()

#Reboot button
self.reboot = gtk.Button("_Reboot")
self.reboot.set_border_width(4)
self.reboot.connect("clicked", self.reboot_action)
self.button_box.pack_start(self.reboot)
self.reboot.show()

#Shutdown button
self.shutdown = gtk.Button("_Power off")
self.shutdown.set_border_width(4)
self.shutdown.connect("clicked", self.shutdown_action)
self.button_box.pack_start(self.shutdown)
self.shutdown.show()

#Create HBox for status label
self.label_box = gtk.HBox()
self.label_box.show()
self.status = gtk.Label()
self.status.show()
self.label_box.pack_start(self.status)

#Create VBox and pack the above HBox's
self.vbox = gtk.VBox()
self.vbox.pack_start(self.button_box)
self.vbox.pack_start(self.label_box)
self.vbox.show()

self.window.add(self.vbox)
self.window.show()

def __init__(self):
self.create_window()


def main():
    gtk.main()

if __name__ == "__main__":
    go = cb_exit()
    main()


And finally edit /home/youruser/.fluxbox/menu and change this line:

   [exec] (Exit) {/usr/bin/vsido-exit-fb} <>   

with this

   [exec] (Exit) {/usr/bin/vsido-exit} <>   

#428
Beginning with this thread, there will be scripts made available that will update users who have already installed VSIDO with the same updates

Attached is vsido_up.sh.  Simply save it to your /home directory and then follow these steps

Logout and drop to tty1 (ctrl + alt + f1)

chmod +x vsido_up.sh

sudo sh vsido_up.sh

At the end it suggests you reboot, but this is not necessary..

ctrl + d to log out of tty1

ctrl + f7  to get back to the login screen

Login

Profit

This particular update installs the correct conky menu xml and several new themes to Fluxbox and changes the Fluxbox menu to the normal default Fluxbox menu layout (for vrkalak)
#429
General Support / Python 2.7 update
March 02, 2013, 03:34:03 PM
Anyone doing a recent

sudo apt-get update && sudo apt-get dist-upgrade

will get an update of python to 2.7.3-4 and will most likely see a bug report and an error after updating which in turn will halt the apt process

All you need to do to correct it is to run:

sudo apt-get install -f

This will clear the error and allow python to update correctly and apt to clear

I have been running the new version of python for several days with no issues
#430
I updated the ISO with the latest SID updates and to make sure that Fluxbox was correctly setup

I built, tested and installed with no issues

For some tips on things you do after the initial install, see the Did You Know Thread
#431
General Support / Did you know?
March 01, 2013, 08:41:02 PM
A thread to park some tweaks that we do once installed

Here is one

For some reason, the tint2 icon for SpaceFM does not show up as it is supposed to

To correct it do this:

In SpaceFM go to View / Window Icon and put in

vsidosfm

Click OK and the issue is solved
#432
Artwork & Screenshots / March 2013 Screenshots
March 01, 2013, 03:48:30 PM
##Post your March 2013 Scrots Here##

My latest:

Fluxbox in VSIDO using ElderV.LaCoste's fb_black style

#433
fsarchiver (File System archiver) IMO is the absolute best for backing up and restoring not only the File System, but anything that you have on a partition

In this How To I am going to explain how I use it to backup the VSIDO build partition and use it on multiple machines

One of the greatest things about fsarchiver is that it does not care how big the partition is that you restore to, as long as it is big enough to handle the size of the original file system.  My build FS is right at the 5 gig mark and fsarchiver compresses that down to 1 gig... So you can put your FS on a thumb drive and take it anywhere and restore it.  Since my build process is pretty much hardware agnostic (except that it is 64 bit), you should be able to download the link I will provide and restore exactly the build machine / FS that I use to build VSIDO

Here we go.  fsarchiver a part of VSIDO already.  In this How To, I am going to describe exactly the steps I used on my machine

Backup the file system with fsarchiver

I am booted to sda1

Make sure that sdc2 is not mounted

1: Create the following directory in /mnt

sudo mkdir /mnt/iso

2: Run the savefs portion of fsarchiver

single-dual core PC with 1GB or less RAM,
sudo fsarchiver -z7 savefs /mnt/iso/buildos.fsa /dev/sdc2

single-dual core PC with more than 1GB of RAM,
sudo fsarchiver -z8 savefs /mnt/iso/buildos.fsa /dev/sdc2

quod core PC with 4GB or less RAM,
sudo fsarchiver -j3 -z8 savefs /mnt/iso/buildos.fsa /dev/sdc2

quod core PC with more than 4GB of RAM,
sudo fsarchiver -j3 -z9 savefs /mnt/iso/buildos.fsa /dev/sdc2

PC with more than four cores and a plenty of RAM,
sudo fsarchiver -j4 -z9 savefs /mnt/iso/buildos.fsa /dev/sdc2

buildos.fsa is the file name being built, saved to /mnt/iso.  You can change this name to anything you want as long as it is with the .fsa extension

The save will take 1-3 minutes and when done you will see something like this:

vastone@vsido:~$ sudo fsarchiver savefs /mnt/iso/buildos.fsa /dev/sdc2
Statistics for filesystem 0
* files successfully processed:....regfiles=92361, directories=10723, symlinks=13608, hardlinks=21, specials=44
* files with errors:...............regfiles=0, directories=0, symlinks=0, hardlinks=0, specials=0


You can now take that .fsa file anywhere you need to for restore

Restoring a fsarchiver fsa file

I am booted to sda1 and I want to restore /mnt/iso/buildos.fsa to sdc8 and it cannot be mounted, if it is, unmount it

Step 1: cd to where the buildos.fsa is

cd /mnt/iso

Step 2: Run the restore process with this command

sudo fsarchiver -j 4 restfs buildos.fsa id=0,dest=/dev/sdc8

This will take 1-3 minutes to restore and when it is done, you will see something like this

vastone@vsido:/mnt/iso$ sudo fsarchiver restfs buildos.fsa id=0,dest=/dev/sdc8
[sudo] password for vastone:
Statistics for filesystem 0
* files successfully processed:....regfiles=90272, directories=10191, symlinks=12503, hardlinks=21, specials=44
* files with errors:...............regfiles=0, directories=0, symlinks=0, hardlinks=0, specials=0


Step 3: Change the uuid of your swap partition on the new restored device

Note - Do this only if you have a swap section in your fstab

First in terminal run:

sudo blkid

You will see something like this as one of the entries

/dev/sdb8: UUID="c462e964-62a3-4119-ac3b-1a0367905b95" TYPE="swap"

In SpaceFM mount the new drive you just created

Edit /etc/fstab and make sure the entry for swap has the same drive and uuid that you got from blkid

Step 4: Now make sure grub sees the new partition

sudo update-grub

Reboot and login into the build OS...

Profit!

NOTE - If you run this restore on the same machine, there will be a uuid conflict and it will not boot.  In the next message I will write up how to get around that by making a grub tweak
#434
WM Designs and Discussions / Fluxbox Styles
February 28, 2013, 02:43:51 AM
ElderVLaCoste is an old friend from the Buntu days and onto #!... He has always been a FluxBox user and tried to get me to try it many times in the past... I should have listened !

He created an incredible theme posted here on devaint art

This will be the default theme for FluxBox on the next ISO build...

In the meantime, it is attached... Simply download it and extrat it to ~/.fluxbox/styles directory, then Restart Fluxbox from Right Click menu on the dekstop..  It will then be a choice as fb_black in Right Click Menu / Styles

My gratitude to ElderVLaCoste!
#435
Liquorix Kernel 3.7.0-9.dmz.1 has been release and smxi did another stellar job updating!
#436
The VSIDO ISO has been updated, built, tested and uploaded. The single major change was adding Fluxbox as a WM that is now available along with Xfce 4.10 and OpenBox. Everything else has been brought up to date with today's level of SID packages

I want to thank vrkalak for his encouragement and assistance through the process of getting to know and building Fluxbox

I am impressed with it, of course this version has the VSIDO look and touches..

Let me know what you think..
#437
Feedback & Suggestions / I am bored!
February 25, 2013, 07:48:17 PM
Everything is looking, behaving and building quite nicely... I am happy but I am BORED!

I am not looking to change anything, or break anything.. I would like to hear some thoughts on what could be different and/or added... For example, I am now using the NewSlicknessBrushed Xfce theme that Sector11 brought to my attention... I never knew about it and now consider it a better theme than the SlicknesS default theme now

I would be interested also in any other WM thoughts any of you may have...

There have been grumblings that VSIDO is too shiny... I would like to hear more on how it could look less shiny..

Don't be shy, throw out some thoughts and lets see how we can make VSIDO even better

The only real thing I am stuck on is Tint2, simply because IMO there is nothing as good as it from a memory perspective.. that does not mean the default layout of Tint2 needs to stay the same.. If someone creative enough wants to showcase a better setup, I am all eyes and ears..

Bring it on VSIDO'rs
#438
VSIDO Discussions / Interesting VSIDO Topic on #!
February 25, 2013, 07:39:58 PM
Interesting VSIDO Topic on #!

Thank you hinto for your review...  8)
#439
New VSIDO ISO uploaded tonight

I fixed the Conky's to a generic that should fit all..

I corrected the VSIDO Persona in Firefox.  I was never aware it was an issue until I installed as a different user than vastone and saw it was washed out white

This has been corrected

Everything else is up to date SID as of 20FEB2013 18:45 CST

The upload will be completed in 20 minutes, thus the 18:45 CST time   ???
#440
VSIDO Discussions / New installs
February 18, 2013, 08:35:26 PM
Installing from the latest ISO, and then upgrading to Liquorix 3.7.0-8 and nVidia beta drivers

On boot

113 MiB in use for Xfce

107 MiB in use for OB

Not bad for OOTB, IMO