Refracta Development, Scripts, etc.
Post a reply

Re: Refracta wiki project

Sun Feb 24, 2013 2:02 pm

repsit (Refracta Extra Packages Selection and Installation Tool) is pretty easy to hack.
Add a line to define the package group.
Edit the first function (install) so the package group shows up in the menu (add one line for that) and add a test below that to detect if the group was selected.
Edit the second function (purge) in the same way as the first.

And I see that some of the package lists are outdated - pretty sure there's no more sun-java6-plugin, and I think some kind of dkms package needs to be added to the nvidia_driver list.

Edit: How minimal? We can work that out. I'm thinking minimal xfce and minimal applications. Would probably keep all the extra command-line tools, but maybe not. The wheezy-no-X version was around 440mb, I think.

Re: Refracta wiki project

Sun Feb 24, 2013 4:56 pm

Refracta xfce wheezy is already pretty minimal compared to a full-blown DE. Guess everything is relative . . .

Re: Refracta wiki project

Sun Feb 24, 2013 5:12 pm

golinux wrote:Refracta xfce wheezy is already pretty minimal compared to a full-blown DE. Guess everything is relative . . .

True. I recently made a kde-wheezy image for a friend, and I couldn't get the desktop to function in vbox until I gave it 640mb of ram. The xfce version works fine with 384 (and probably with 256). And I had one of Dean's versions (maybe v. 508 or 512) running fine on a PIII with 64mb ram. Antix only uses around 35mb - I'm not even going to try to compete with that.

Re: Refracta wiki project

Wed Feb 27, 2013 2:01 pm

Links for Yad

Instructions for adding the repo:
http://debs.slavino.sk/

Links for the deb files are under "Zoznam balíkov". Use the testing version, not the stable.
http://debs.slavino.sk/files-testing.php


Links for deadbeef are now irrelevant, as I replaced deadbeef with audacious. Any others I'm forgetting?

Re: Refracta wiki project

Wed Feb 27, 2013 2:32 pm

I'm a bit confused . . . nothing new here . . .

If the slavino repo is added as per the first link, is the second link really needed? Won't everything update automatically?

Are you waiting for wheezy to go stable before going 'live' with the new site? Or still just collecting documentation (in your 'spare' time when you're not shoveling snow - poor you!)?

Re: Refracta wiki project

Wed Feb 27, 2013 4:13 pm

Shovel don't work no more. I need a slush pump. The links for the deb files might be useful for those who want to use the tools with other debian distros and would rather have yad than zenity.

No, I'm not necessarily waiting until wheezy goes stable to change the website. The squeeze version can stay in the 606 folder, and I'm not sure when the "current" folder will be changed to point to wheezy. That one is just a symlink. Have the web page point to that, so that I only need to change the link when the time comes.

Re: Refracta wiki project

Wed Feb 27, 2013 4:24 pm

Just confirming . . . the ibiblio link goes to the 'current' folder which now contains 6.06 isos while the sourceforge download is for wheezy?

Please check the revised links.

Re: Refracta wiki project

Wed Feb 27, 2013 5:04 pm

golinux wrote:Just confirming . . . the ibiblio link goes to the 'current' folder which now contains 6.06 isos while the sourceforge download is for wheezy?


I'm not sure how I'm going to use the sourceforge site. That should be where the current version is or it should be where the biggest version is, because it's the faster server. For squeeze, I made a usb-hdd image, which is 1gb. Nadir uploaded it to someplace, because the space is limited at ibiblio. Right now, I'm not even sure where the link is.

Re: Refracta wiki project

Wed Feb 27, 2013 6:23 pm

Let me know when you figure it out. In the meantime . . . how are the installer and snapshot readmes coming? We also need to change out the package list and tweak the release notes. Not like you don't have anything else to do . . .

Re: Refracta wiki project

Wed Feb 27, 2013 7:02 pm

Whoa! Way cool. I just had a complete lockup as I was about to hit submit, had to press the reboot button on the front of the computer, and iceweasel restored this page and my login. (Gotta get a new ups, I think.)

Below is the revised vnc section. See if it makes more sense than the previous. Indented parts can go in code boxes. I may have missed some of those toward the end.

I thought I had some notes on things that needed fixing in the html release notes, but I guess it wasn't saved and got lost in a momentary power failure a few days ago. Oh well, I need to read it all again anyway. The one thing I remember is the passwords. Instead of a nice, proper paragraph, I'd rather see them on separate lines, so they're dead easy to find:
The root password is root.
The user password is user.
The next sentence starts here.


Code:
=================================

___ VNC over SSH ___

(Optional) Add ssh authorization key:

   ssh-add /path-to-key/id_rsa


There are several ways to start a vnc session.

1. Use custom scripts: vncssh (on client) and vncserv (on server)

If xserver is running  and user is logged in to desktop on remote-host,
open a terminal on the client and run vncssh.

   vncssh  [user@]<host>[:xdisplay]  [port]

   (user, xdisplay and port are optional)

   Examples:
      vncssh someserver.com:0
      vncssh fred@homeserver 1234 


If user is not logged in on remote host, but xserver is running:

   vncssh root@remote-host


2. If the server does not have the vncserv script, but it does have
x11vnc installed, you can edit /usr/local/bin/vncssh and change:

   cmd="/usr/local/bin/vncserv"
to
   cmd="x11vnc -auth /var/run/lightdm/root/:0 -localhost -display :0"


3. Do it manually, without the scripts:

Start remote vnc server over ssh:

   ssh -t -L 5900:localhost:5900 user@remote-host 'x11vnc -localhost -display :0'


If user is not logged in on remote host, or if the remote host is using
some display manager other than lightdm, do something like the following.

Log into remote host through ssh and get the auth file
from 'ps ax | grep auth'. For lightdm, it will probably be
/var/run/lightdm/root/:0 and for gdm3, find the line in the output
that has gmd3 in it and look to the end for a filename with random
characters in it.

Then exit and run:

   ssh -t -L 5900:localhost:5900 root@remote-host 'x11vnc -auth /path/to/authfile -localhost -display :0'

Once you've started the remote vnc server, open another terminal,
and connect to the remote desktop with:

   vncviewer -encodings "copyrect tight hextile" localhost:0


4. If xserver is not running on the remote-host, you won't be able to
use x11vnc. You can remedy this on the server by installing xvfb and
editing /usr/local/bin/vncserv to uncomment the following lines:

   #else
   #   x11vnc -create -env FD_PROG=/usr/bin/xfce4-session  \
   #      -env X11VNC_FINDDISPLAY_ALWAYS_FAILS=1 \
   #        -env X11VNC_CREATE_GEOM=${1:-1024x768x16} \
   #        -gone 'killall Xvfb' \
   #        -bg -nopw




___ YET ANOTHER WAY TO DO VNC ___

This way is ok on a local network but is not as secure as with ssh.

On the server:
Main menu --> Internet --> X11VNC Server
Click OK (or change the port if you want)
Another window comes up, check the box next to "Accept Connections"
Optionally, you can create a password.
Click Apply or OK

On the client, issue the command:
vncviewer
A small window comes up; enter the name or IP number of the remote server.
Click OK
(Alternate: 'vncviewer remote-host:0)

For more details, see http://www.karlrunge.com/x11vnc/

=================================


Edit: new package list will come with rc1, and I'll just name it "package_list" so that the link does not need changing. Well, there shouldn't be any changes in the packages once we're at rc1 anyway.
Post a reply