Welcome!

Please read this important information about MX sources lists.
News
  • MX Linux on social media: here
  • Mepis support still here
Current releases
  • MX-17 Final release info here
  • MX-16.1 release info here
  • antiX-17 release info here
    New users
    • Please read this first, and don't forget to add system and hardware information to posts!
    • Read Forum Rules

Systemback (Stevo for President!)

Message
Author
User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 13856
Age: 59
Joined: Fri Dec 15, 2006 8:07 pm

Re: Systemback (Stevo for President!)

#21 Postby Stevo » Sun Mar 23, 2014 1:37 pm

I'm getting a report that the menu entries don't launch a systemback GUI, that is, you don't get a root login dialog, or the message that something else has apt locked. Has anyone else seen this--I can't reproduce it.


Update:
Tim read the source code and found out why--it looks for a file in your /home called .Xauthority, and won't launch if missing. Rebuilt using gksu to get root authorization to get around this, should be in repos soon.
Last edited by Stevo on Sun Mar 23, 2014 3:14 pm, edited 1 time in total.

User avatar
anticapitalista
Forum Veteran
Forum Veteran
Posts: 5243
Joined: Sat Jul 15, 2006 10:40 am

Re: Systemback (Stevo for President!)

#22 Postby anticapitalista » Sun Mar 23, 2014 2:13 pm

GuiGuy wrote:
anticapitalista wrote:It is in the live boot menu as ... wait for it ... drum roll etc

Command Line Install.

Thanks, Anti.
I was trying to run it from my installed system :footinmouth:

Edit:-
I am still confused: if I put the snapshot.iso onto a DVD and live-boot from it, it will not offer a gui installer but it will offer a CLI installer ?


As I said, there is only the cli-installer option at the moment.
anticapitalista
Reg. linux user #395339.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX-15 "Killah P!" - lean and mean.
http://antix.mepis.org

User avatar
loco
Forum Regular
Forum Regular
Posts: 567
Joined: Mon Jan 14, 2008 2:00 am

Re: Systemback (Stevo for President!)

#23 Postby loco » Sun Mar 23, 2014 3:23 pm

Stevo wrote:I'm getting a report that the menu entries don't launch a systemback GUI, that is, you don't get a root login dialog, or the message that something else has apt locked. Has anyone else seen this--I can't reproduce it.
upp...

> removed text
Last edited by loco on Mon Mar 24, 2014 11:38 pm, edited 1 time in total.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 13856
Age: 59
Joined: Fri Dec 15, 2006 8:07 pm

Re: Systemback (Stevo for President!)

#24 Postby Stevo » Sun Mar 23, 2014 4:31 pm

Wheezy squashfs is now using squashfs-xz by default, which allows for what was maybe 820-850 MB with the older compression to now fit in 700 MB. It's still amazing that there's all these programs plus LibreOffice on there--I remember when I first tried a 700 MB Ubuntu disc years and years ago, and there was almost nothing on it compared to the MEPIS at the time.

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 3845
Joined: Wed Jul 12, 2006 4:05 pm

Re: Systemback (Stevo for President!)

#25 Postby timkb4cq » Sun Mar 23, 2014 5:16 pm

Stevo wrote:I'm getting a report that the menu entries don't launch a systemback GUI, that is, you don't get a root login dialog, or the message that something else has apt locked. Has anyone else seen this--I can't reproduce it.
Tracked it down. If the ~/.Xauthority file is missing then Systemback exits with a popup saying it can't connect to the X-Server. It doesn't have to a correct .Xauthority file - there just has to be one. One of my machines nearly always fails to get one when it should at install time. Can't figure out why. Just oddball hardware I guess. Stevo fixed the debs anyway to eliminate that problem. If you have Synaptic open you will get the message that something has apt locked - because it's true.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
BitJam
Forum Guide
Forum Guide
Posts: 2362
Joined: Sat Aug 22, 2009 11:36 pm

Re: Systemback (Stevo for President!)

#26 Postby BitJam » Sun Mar 23, 2014 5:45 pm

The .Xauthority file should be created anew. It should not be distributed. This would be akin to giving everyone the same root password. The .Xauthority file contains some random data called a cookie that acts like a password to gain access to the X-server.

This is one of the main differences between xinit and startx. The startx program calls xinit but it first secures access to the X-server by setting up authorization. You can look in the startx script for a (perhaps poor) example of how to set up X authorization.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 13856
Age: 59
Joined: Fri Dec 15, 2006 8:07 pm

Re: Systemback (Stevo for President!)

#27 Postby Stevo » Sun Mar 23, 2014 8:18 pm

OK...we aren't messing with that file, though. I just changed the .desktop launcher files for the GUI part of Systemback to use gksu to get root, instead of the method that is built into gambas3.

User avatar
qtech
Forum Regular
Forum Regular
Posts: 662
Joined: Wed Nov 28, 2007 12:21 pm

Re: Systemback (Stevo for President!)

#28 Postby qtech » Sun Mar 23, 2014 9:35 pm

Stevo wrote:OK...we aren't messing with that file, though. I just changed the .desktop launcher files for the GUI part of Systemback to use gksu to get root, instead of the method that is built into gambas3.


I wish I could be of some help to you but I got lazy and frustrated at some point and just threw the kitchen sink at it. I can say that both gtk and qt4 versions are fully functional. For what their worth, the commit logs are below.

Code: Select all

Commit Log for Fri Mar 21 23:18:14 2014

Installed the following packages:
systemback (0.7.7.501-1mcr120+1)
systemback-gtk (0.7.7.501-1mcr120+1)
systemback-gui (0.7.7.501-1mcr120+1)
systemback-gui-common (0.7.7.501-1mcr120+1)
systemback-qt4 (0.7.7.501-1mcr120+1)
unionfs-fuse (0.24-2.2)


Code: Select all

Commit Log for Fri Mar 21 23:29:54 2014

Installed the following packages:
gambas3-gb-gtk-opengl (3.5.2-1mcr120+1)
gambas3-gb-gui (3.5.2-1mcr120+1)
gambas3-gb-gui-opengl (3.5.2-1mcr120+1)
gambas3-gb-opengl (3.5.2-1mcr120+1)
gambas3-gb-qt4-opengl (3.5.2-1mcr120+1)
libgtkglext1 (1.2.0-2)

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 13856
Age: 59
Joined: Fri Dec 15, 2006 8:07 pm

Re: Systemback (Stevo for President!)

#29 Postby Stevo » Sun Mar 23, 2014 10:51 pm

gambas3-gb-gui is the critical package that was missing. The new version will have that as a dependency.

User avatar
m_pav
Forum Guide
Forum Guide
Posts: 2581
Age: 50
Joined: Sun Aug 06, 2006 3:02 pm

Re: Systemback (Stevo for President!)

#30 Postby m_pav » Mon Mar 24, 2014 3:53 am

Isn't it just a whole lot easier to boot a Live-USB, set it up the way you want it, add/remove apps as you wish and then run the remastercc tool before you close off your live-session?

This remastercc creates an alternative antix/linuxfs file on your USB stick with the extension .new and it contains all your changes to the installed base, minus user settings unless you copy them to the /etc/skel folder.
When you next boot, the original antix/linuxfs file is renamed to /antix/linuxfs.old and the .new is removed from the fresh linuxfs file so it becomes the standard boot selection by becoming the /antix/linuxfs compressed file system loaded as the OS. When you're satisfied that all is well, you can just delete the original file now renamed linuxfs.old and have your own fully customised boot USB.

If you have a relatively small amount of RAM, simply fire up the System profiler and benchmark tool (hardinfo) and keep it on the summary screen, you'll see your RAM usage in real time and you can keep consuming RAM until you have about 50Mb remaining, then run the remastercc to lock in your changes. If you can't do enough in one hit because you have too little RAM, do it over several boots and you can opt to lose the oldest backup of the linuxfs file.

If you also include isomaster, you can take edit the original ISO to remove the original /antix/linuxfs file and replace it with your modified version, then save the whole thing as a new ISO file and viola, you have both a live-USB and a fresh Live-ISO image that can be burned to CD/DVD while retaining the grub boot prompts, cheatcodes and the improved MX installer, but your original ISO is untouched because you have a new one that you made yourself.

Doing it this way, no changes are made to the grub boot menu offered on the live-ISO, but the installed OS is whatever you have on the ISO or live-USB and it can be used with unetbootin or the antix2usb script because it's a regular ISO, albeit a bit larger because you've added to it.

I used this process to make a fully customised multimedia ISO from RC2. I saved a new ISO of this build which measured 1.5GB and created a Live-USB using the new ISO. It starts like RC2 but it is better suited to media production, and it includes all the updates up to the point of running the remastercc. It installs perfectly using the MX installer.
Mike P

Regd Linux User #472293
(Mine)Lenovo T560, i7-6600U, 16GB, 2.0TB SSHD, MX16 64-bit
(Wifes) Asus M4A88TD-M, AMD Phenom II x4 955 CPU, nVidia GF610, 6Gb, 500GB+320GB, MX16 + KDE
(Kids) Intel NUC, J1900, 4GB, 64GB SSD, MX16


Return to “Community Repository (CR)”

Who is online

Users browsing this forum: No registered users and 1 guest