boinc???

Post here if you are a new Porteus member and you're looking for some help.
Locked
wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

boinc???

Post#1 by wacojohn » 06 Sep 2015, 18:04

Running 32 bit Porteus ... as of yesterday. Hoping it can run Boinc. If so, can someone tell me where to get it and how to install it? Thank you ... very much .. in advance.
Last edited by wacojohn on 13 Oct 2015, 20:03, edited 2 times in total.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#2 by Bogomips » 06 Sep 2015, 20:15

    1. download package if not already downloaded and
      cttan wrote:The BOINC package you downloaded from http://boinc.berkeley.edu/download.php
    2. wacojohn wrote: need to know what to do with boinc_7.2.42_i686-pc-linux-gnu.sh which now sits on my desktop.

      Code: Select all

      ln ~/Desktop/boinc_7.2.42_i686-pc-linux-gnu.sh ~
      sh boinc_7.2.42_i686-pc-linux-gnu.sh
      ls -lh
      
  1. Following directions within this post, download boinc-7.2.42.i686.xzm to /home/guest
  2. Need to strip Boinc of executables, placing them somewhere, where they can do no harm:

    Code: Select all

    mkdir /tmp/bnc
    for b in  BOINC/boinc*; do ! [[ $b =~ png$ ]] && mv $b /tmp/bnc; done
    
    1. Copy boinc-7.2.42.i686.xzm to modules folder

      Code: Select all

      cp boinc-7.2.42.i686.xzm /mnt/sda1/porteus/modules    # As root or sudo
      ls -lh /mnt/sda1/porteus/modules
    2. Make a real filesystem directory and copy BOINC to it:

      Code: Select all

      mkdir /mnt/sda1/disk		# As root or sudo
      chmod a+rw /mnt/sda1/disk	# As root or sudo
      cp -a BOINC /mnt/sda1/disk
      du -sh /mnt/sda1/disk/BOINC
  3. Obtain Measurements
      1. Create script boinc_mgr

        Code: Select all

        #!/bin/bash
        cd  /mnt/sda1/disk/BOINC
        boincmgr
      2. Make executable and insert in BOINC

        Code: Select all

        chmod a+x boinc_mgr
        cp boinc_mgr /mnt/sda1/disk/BOINC
    1. Edit boot/syslinux/porteus.cfg file to Set up Kernel Parameters (cheatcodes)
      1. Lines of interest (something like)

        Code: Select all

        LABEL gui
        MENU LABEL Graphics mode (xxx)
        KERNEL vmlinuz
        APPEND initrd=initrd.xz changes=/porteus 
        TEXT HELP
            Run Porteus the best way we can.
            Try to autoconfigure graphics
            card and use the maximum
            allowed resolution
        ENDTEXT
        
      2. Append following Parameters to APPEND line
        • Code: Select all

          cliexec=boinc~--dir~/mnt/sda1/disk/BOINC~--daemon
        • Code: Select all

          guiexec=/mnt/sda1/disk/BOINC/boinc_mgr
    2. Reboot
      1. Check Kernel Parameters

        Code: Select all

        cat /proc/cmdline
        cat /var/log/porteus-livedbg
        du -sh  /mnt/sda1/porteus/changes
        
      2. Additional info

        Code: Select all

        ls -lh /mnt/sda1/porteus/{,base,modules,optional}
        lsblk | grep loop
        free -m
        df -h ~
        ps -e | grep boinc
        
      3. Boinc Manager
        View > Advanced View > Advanced > Event Log > Copy All
        Place within
        as much from the beginning, until it becomes monotonous.
  4. Update Preparation
    1. Download
      1. systemd module into /mnt/sda1/disk
        md5sum systemd-224-1-i686-0-kde.xzm
        77fc39b5ec79b1dd3cfe9dfbb6f2c153 systemd-224-1-i686-0-kde.xzm
      2. gtk3 module into /mnt/sda1/disk
        md5sum gtk3-3.16.7.i686-pkg-1.xzm
        6ce1ec528052982f00ce2df87acd0938 gtk3-3.16.7.i686-pkg-1.xzm
    2. Verify md5 sums of downloaded modules:

      Code: Select all

      md5sum /mnt/sda1/disk/*.xzm
    3. Check everything is there

      Code: Select all

      ls -lh /mnt/sda1/disk
  5. Update Test
    1. Using porteus.tst as config file with append line APPEND initrd=initrd.xz fsck timezone=US/Central utc

      Code: Select all

      cp /mnt/sda1/boot/syslinux/porteus.tst /mnt/sda1/boot/syslinux/porteus.cfg
    2. Reboot
    3. Activate Update (as root)
      1. Code: Select all

        activate /mnt/sda1/disk/systemd-224-1-i686-0-kde.xzm
        
      2. Code: Select all

        activate /mnt/sda1/disk/gtk3-3.16.7.i686-pkg-1.xzm
    4. Code: Select all

      cd /home/guest
      cat /proc/cmdline
      lsblk | grep loop
      boinc --dir /mnt/sda1/disk/BOINC --daemon
      ldd /usr/bin/boinc | grep found
      ldd /usr/bin/boincmgr | grep found
      cat /var/log/porteus-livedbg 
      cd /mnt/sda1/disk/BOINC
      boincmgr 
      
  6. Further Test
      1. Edit porteus.cln so that has append line APPEND initrd=initrd.xz fsck timezone=US/Central utc cliexec=boinc~--dir~/mnt/sda1/disk/BOINC~--daemon
      2. Code: Select all

        cp /mnt/sda1/boot/syslinux/porteus.cln /mnt/sda1/boot/syslinux/porteus.cfg
    1. Reboot
    2. Activate Update (as root)
      1. Code: Select all

        activate /mnt/sda1/disk/systemd-224-1-i686-0-kde.xzm
        
      2. Code: Select all

        activate /mnt/sda1/disk/gtk3-3.16.7.i686-pkg-1.xzm
    3. Code: Select all

      cd /home/guest
      cat /proc/cmdline
      lsblk | grep loop
      ldd /usr/bin/boinc | grep found
      ldd /usr/bin/boincmgr | grep found
      cat /var/log/porteus-livedbg 
      cd /mnt/sda1/disk/BOINC
      boincmgr 
      
    4. Do 5c ii & 5c iii
  7. Streamlining Test
      1. Code: Select all

        cp /mnt/sda1/boot/syslinux/porteus.bnc /mnt/sda1/boot/syslinux/porteus.svd
      2. Edit porteus.svd so that has append line APPEND initrd=initrd.xz changes=EXIT:/disk fsck timezone=US/Central utc cliexec=boinc~--dir~/mnt/sda1/disk/BOINC~--daemon
      3. Code: Select all

        cp /mnt/sda1/boot/syslinux/porteus.svd /mnt/sda1/boot/syslinux/porteus.cfg
    1. Reboot
    2. Activate Update (as root)
      1. Code: Select all

        activate /mnt/sda1/disk/systemd-224-1-i686-0-kde.xzm
        
      2. Code: Select all

        activate /mnt/sda1/disk/gtk3-3.16.7.i686-pkg-1.xzm
    3. Code: Select all

      cd /home/guest
      cat /proc/cmdline
      lsblk | grep loop
      ldd /usr/bin/boinc | grep found
      ldd /usr/bin/boincmgr | grep found
      cat /var/log/porteus-livedbg 
      cd /mnt/sda1/disk/BOINC
      boincmgr 
      
    4. Do 5c ii & 5c iii
  8. To be continued
Superseded Original Post

Looked easy enough, but have hit a request for a versioned library, which is always a headache. :wall: Will only go ahead if no one else comes up with something in near future. Other than that, welcome to Porteus.

P.S. One other thing to know is if Non-X version acceptable.

Update

Despite above-mentioned obstacle, it seems to run. Been a while since tried out Boinc. Is this normal running?

Code: Select all

guest@porteus:~$ boinc
boinc: /usr/lib/libcurl.so.4: no version information available (required by boinc)
06-Sep-2015 21:20:58 [---] cc_config.xml not found - using defaults
06-Sep-2015 21:20:58 [---] Starting BOINC client version 7.2.42 for i686-pc-linux-gnu
06-Sep-2015 21:20:58 [---] log flags: file_xfer, sched_ops, task
06-Sep-2015 21:20:58 [---] Libraries: libcurl/7.36.0 OpenSSL/1.0.1c zlib/1.2.8 libidn/1.25
06-Sep-2015 21:20:58 [---] Data directory: /home/guest
execv: No such file or directory
06-Sep-2015 21:20:58 [---] GPU detection failed. error code 512
06-Sep-2015 21:20:58 [---] No usable GPUs found
06-Sep-2015 21:20:58 [---] Creating new client state file
06-Sep-2015 21:20:58 [---] Host name: porteus
06-Sep-2015 21:20:58 [---] Processor: 1 AuthenticAMD AMD Sempron(tm) 140 Processor [Family 16 Model 6 Stepping 2]
06-Sep-2015 21:20:58 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate npt lbrv svm_lock nrip_save vmmcall
06-Sep-2015 21:20:58 [---] OS: Linux: 3.18.21-porteus
06-Sep-2015 21:20:58 [---] Memory: 880.39 MB physical, 644.68 MB virtual
06-Sep-2015 21:20:58 [---] Disk: 264.12 MB total, 252.33 MB free
06-Sep-2015 21:20:58 [---] Local time is UTC +1 hours
06-Sep-2015 21:20:58 [---] No general preferences found - using defaults
06-Sep-2015 21:20:58 [---] Preferences:
06-Sep-2015 21:20:58 [---]    max memory usage when active: 440.20MB
06-Sep-2015 21:20:58 [---]    max memory usage when idle: 792.36MB
06-Sep-2015 21:20:58 [---]    max disk usage: 0.15GB
06-Sep-2015 21:20:58 [---]    don't use GPU while active
06-Sep-2015 21:20:58 [---]    suspend work if non-BOINC CPU load exceeds 25%
06-Sep-2015 21:20:58 [---]    (to change preferences, visit a project web site or select Preferences in the Manager)
06-Sep-2015 21:20:58 [---] Not using a proxy
06-Sep-2015 21:20:58 [---] This computer is not attached to any projects
06-Sep-2015 21:20:58 [---] Visit http://boinc.berkeley.edu for instructions
06-Sep-2015 21:20:58 Initialization completed
06-Sep-2015 21:22:48 [---] Suspending computation - CPU is busy
06-Sep-2015 21:22:59 [---] Resuming computation
06-Sep-2015 21:23:09 [---] Suspending computation - CPU is busy
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#3 by wacojohn » 06 Sep 2015, 22:30

Thank you for the welcome and the answer. I will bet you have it all correct. Only problem is answering your questions.
One other thing to know is if Non-X version acceptable.
Uhm .. don't know how to answer. Have a feeling you mean a non-gui installation??? I am accustomed to running Boinc in Lubuntu ... which has it in their repositories ... and it ends up on a clickable menu item. With the pkg, one can select projects, view statistics, etc etc. Was hoping for the same type of installation. I will take what I can get, however ... I think.
Is this normal running?
I got this with run_client --daemon

Code: Select all

wacojohn:$ run_client --daemon
./boinc: /lib/libssl.so.1.0.0: no version information available (required by ./boinc)
./boinc: /usr/lib/libcurl.so.4: no version information available (required by ./boinc)
./boinc: /lib/libcrypto.so.1.0.0: no version information available (required by ./boinc)
vector:/~/BOINC
wacojohn:$ run_manager
./boincmgr: error while loading shared libraries: libwx_gtk2u_html-2.8.so.0: cannot open shared object file: No such file or directory
vector:/~/BOINC
wacojohn:$ 




wacojohn:$ run_manager
./boincmgr: error while loading shared libraries: libwx_gtk2u_html-2.8.so.0: cannot open shared object file: No such file or directory
vector:/~/BOINC
wacojohn:$
Uh ... I never got that far. Your code looks like what Boinc Manager does after it is all set up in Lubuntu.

I followed the following from their installation guide:
The Berkeley Installer
The Berkeley Installer is available directly from the BOINC project. It is a self-extracting archive. This type of installation requires that you be familiar with the UNIX command-line interface. The download files have names like boinc_7.2.23_i686-pc-linux-gnu.sh. After downloading the file, you'll need to be in the directory where you download the archive to unpack it.
Here is an example. The archive is downloaded to the desktop. It is then moved to the home directory (~). Finally BOINC is unpacked and installed. All of this can be done within a regular user account; root privileges are not needed.
$ mv ~/Desktop/boinc_7.2.23_i686-pc-linux-gnu.sh ~
$ cd ~
$ sh boinc_7.2.23_i686-pc-linux-gnu.sh
This creates a directory called BOINC/ under the home directory containing the following files:
boinc
The BOINC core client.
boincmgr
The BOINC Manager.
boinccmd
A command line tool for controlling a running core client.
run_client
A script that cd's into the BOINC directory and runs the core client.
run_manager
A script that cd's into the BOINC directory and runs the manager.
To start the client manually enter the following terminal commands:
$ cd ~/BOINC
$ ./run_client --daemon
$ ./run_manager
The BOINC working directory can be moved elsewhere as you like, and can even be renamed. One common choice is ~/.boinc, since files and directories with names that begin with "dot" do not show up by default in Unix directory listings. Whatever the name, everything related to the BOINC client is contained within that directory, and you should always run the client and the manager from that working directory.

Maybe I should omit the

Code: Select all

 --daemon
?

If this is command line only, I have no idea how to select a project and all the other goodies that some with a pkg. Thank you immensely for your attention. Looking forward to your next reply.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#4 by Bogomips » 07 Sep 2015, 01:33

@wacojohn
Shall now just give code that was used to get Boinc sort of working. (Just copying and pasting commands should see you in good stead.) This is procedure to follow, and assumes you are using home directory:
  1. Code: Select all

    mkdir bnc
  2. Using browser download to bnc
  3. Script xz2txz
    • Copy and Paste into Text Editor xz2txz Enhanced Script here.
    • Save in home directory as xz2txz.sh
  4. Code: Select all

    sh xz2txz.sh -nv bnc
    
  5. Code: Select all

    mkdir fkr
    /sbin/installpkg -root fkr bnc/*.txz
    
  6. Enter in a terminal su and password toor, then as Superuser:

    Code: Select all

    dir2xzm fkr boinc-nox-7.2.42.i686-pkg-1.xzm
    activate boinc-nox-7.2.42.i686-pkg-1.xzm
    
  7. Invocation as ordinary user:

    Code: Select all

    boinc
    boinccmd
    The latter being the more appropriate invocation.
Invocation Examples

Code: Select all

guest@porteus:~$ boinc -h
boinc: /usr/lib/libcurl.so.4: no version information available (required by boinc)
Unknown option: -h
The command-line options for boinc are intended for debugging.
The recommended command-line interface is a separate program,'boinccmd'.
Run boinccmd in the same directory as boinc.

Usage: boinc [options]
    --abort_jobs_on_exit           when client exits, abort and report jobs
    --allow_remote_gui_rpc         allow remote GUI RPC connections
    --allow_multiple_clients       allow >1 instances per host
    --attach_project <URL> <key>   attach to a project
    --check_all_logins             for idle detection, check remote logins too
    --daemon                       run as daemon (Unix)
    --detach_console               detach from console (Windows)
    --detach_project <URL>         detach from a project
    --dir <path>                   use given dir as BOINC home
    --exit_after_app_start N       exit N seconds after an app starts
    --exit_after_finish            exit right after finishing a job
    --exit_before_start            exit right before starting a job
    --exit_before_upload           exit right before starting an upload 
    --exit_when_idle               exit when there are no results
    --fetch_minimal_work           fetch only 1 job per device
    --file_xfer_giveup_period N    give up on file xfers after N sec
    --gui_rpc_port <port>          port for GUI RPCs
    --help                         show options
    --master_fetch_interval N      limiting period of master retry
    --master_fetch_period N        reload master URL after N RPC failures
    --master_fetch_retry_cap N     exponential backoff limit
    --no_gpus                      don't check for GPUs
    --no_gui_rpc                   don't allow GUI RPC, don't make socket
    --no_info_fetch                don't fetch project list or client version info
    --no_priority_change           run apps at same priority as client
    --pers_giveup N                giveup time for persistent file xfer
    --pers_retry_delay_max N       max for file xfer exponential backoff
    --pers_retry_delay_min N       min for file xfer exponential backoff
    --redirectio                   redirect stdout and stderr to log files
    --reset_project <URL>          reset (clear) a project
    --retry_cap N                  exponential backoff limit
    --run_cpu_benchmarks           run the CPU benchmarks
    --run_by_updater               set by updater
    --sched_retry_delay_max N      max for RPC exponential backoff
    --sched_retry_delay_min N      min for RPC exponential backoff
    --show_projects                show attached projects
    --skip_cpu_benchmarks          don't run CPU benchmarks
    --start_delay X                delay starting apps for X secs
    --suppress_net_info            don't send network addrs to server
    --unsigned_apps_ok             allow unsigned apps (for testing)
    --update_prefs <URL>           contact a project to update preferences
    --version                      show version info

Code: Select all

guest@porteus:~$ boinccmd

usage: boinccmd [--host hostname] [--passwd passwd] command

Commands:
 --create_account URL email passwd name
 --file_transfer URL filename op    file transfer operation
   op = retry | abort
 --get_cc_status
 --get_daily_xfer_history           show network traffic history
 --get_disk_usage                   show disk usage
 --get_file_transfers               show file transfers
 --get_host_info
 --get_message_count                show largest message seqno
 --get_messages [ seqno ]           show messages > seqno
 --get_notices [ seqno ]            show notices > seqno
 --get_project_config URL
 --get_project_status               show status of all attached projects
 --get_proxy_settings
 --get_simple_gui_info              show status of projects and active tasks
 --get_state                        show entire state
 --get_tasks                        show tasks
 --get_old_tasks                    show reported tasks from last 24 hours
 --join_acct_mgr URL name passwd    attach account manager
 --lookup_account URL email passwd
 --network_available                retry deferred network communication
 --project URL op                   project operation
   op = reset | detach | update | suspend | resume | nomorework | allowmorework | detach_when_done | dont_detach_when_done
 --project_attach URL auth          attach to project
 --quit                             tell client to exit
 --quit_acct_mgr                    quit current account manager
 --read_cc_config
 --read_global_prefs_override
 --run_benchmarks
 --set_gpu_mode mode duration       set GPU run mode for given duration
   mode = always | auto | never
 --set_host_info product_name
 --set_network_mode mode duration   set network mode for given duration
   mode = always | auto | never
 --set_proxy_settings
 --set_run_mode mode duration       set run mode for given duration
   mode = always | auto | never
 --task url task_name op            task operation
   op = suspend | resume | abort
 --version, -V                      show client version
Now off for 40 x :wink:
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#5 by wacojohn » 07 Sep 2015, 03:23

Cannot thank you enough. Your support is most appreciated. I was hoping to install a package .... but that does not seem possible. Your instruction is a bit over my head, ... but I am perfectly willing to try it out. It will take me some time to tackle this. Possibly several days. I will update this thread once I have something to report. Thank you once again.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#6 by Bogomips » 07 Sep 2015, 11:28

Might in the meantime be able to make you a module, depending on how my time pans out. But don't depend on it. Have a go. It is not difficult. All you have to do is copy and paste into a terminal at the prompt, for the most part. If you have difficulty someone like francois or Jack, in your TZ, will always be able to help you. :) abc
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#7 by wacojohn » 07 Sep 2015, 13:17

Yes, Sir ... copy and paste ... within my abilities. The angst comes from a limited knowledge of Linux. In this case, I installed BOINC ... per The Berkeley Installer ... and I assume it prudent to uninstall it before attempting your advice. Sadly, I do not know how to do that ... and my only option is to do a complete new install of Porteus. This explains the delay. I am so grateful for your help, and don't wish to impose any more than necessary.

EDIT: I am so naive, I ask ... obtaining one of the packages (modules??) available such as a .deb, .rpm, ... whatever is appropriate from (say) Ubuntu repository would not be an option ... because (?)

Are not Ubuntu and Porteus "Debian" based? Obviously the answer is no, or we would be doing that, but the question is academic. I am surprised a boinc module(?) is not in the Porteus repository. I don't know exactly how repositories work .. why would it not be??

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#8 by Bogomips » 07 Sep 2015, 18:44

Quite a few of the people who come as Newbies are experienced Linux users. So I always assume this unless they say otherwise. Explaining in detail would be a waste of both our times, if they already know it all.
wacojohn wrote:I am so grateful for your help, and don't wish to impose any more than necessary.
No problem when it is appreciated :)
wacojohn wrote:Are not Ubuntu and Porteus "Debian" based? Obviously the answer is no, or we would be doing that, but the question is academic. I am surprised a boinc module(?) is not in the Porteus repository. I don't know exactly how repositories work .. why would it not be??
Don't need to bother yourself with the question of how repositories work. Porteus uses Slackware repositories. There is package manager which you can click on in taskbar. Already checked this for boinc.
wacojohn wrote:Yes, Sir ... copy and paste ... within my abilities. The angst comes from a limited knowledge of Linux. In this case, I installed BOINC ... per The Berkeley Installer ... and I assume it prudent to uninstall it before attempting your advice. Sadly, I do not know how to do that ... and my only option is to do a complete new install of Porteus.
If you used the Berkeley Installer while running Porteus, it would be prudent to do a complete new install. I make it a rule myself not to use proferred installers. You do not need a complete new install of Potreus if you installed boinc from Ubuntu.

Porteus is a live system, and you only need to install the programs you need. They come as modules. So making the module is the equivalent of apt-get without installing. Installing is done through activation of the module for a particular application. Upon session end, everything gets uninstalled from system, just like the files one does not save. There is no installation per se in Porteus.
wacojohn wrote:EDIT: I am so naive, I ask ... obtaining one of the packages (modules??) available such as a .deb, .rpm, ... whatever is appropriate from (say) Ubuntu repository would not be an option ... because (?)
There is no apt-get. It's a completely different universe, and I know, having come over from Mint.

So, to allay your worries, start Porteus in Always Fresh mode (without saving changes), I think that option is included when you choose copy2ram in the boot menu, or someone will put me right, there. If you are not saving changes, everything in your home directory will disappear at session end, so no worries.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
francois
Contributor
Contributor
Posts: 5080
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: boinc???

Post#9 by francois » 07 Sep 2015, 19:34

Alas, there is no changes= cheatcode in the always fresh or copy2ram menu options. You have to add them yourself.
Voltaire: Le mieux est l'ennemi du bien.

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#10 by wacojohn » 07 Sep 2015, 21:08

Bogomips wrote:Quite a few of the people who come as Newbies are experienced Linux users. So I always assume this unless they say otherwise. Explaining in detail would be a waste of both our times, if they already know it all.
Wondering what 'experienced' actually means. Been 'using' Linux for 6+ years .... self taught. What I don't know is measured by what I have not done .. which is mountainous.
Don't need to bother yourself with the question of how repositories work. Porteus uses Slackware repositories. There is package manager which you can click on in taskbar. Already checked this for boinc.
So did I. Boinc is in many repositories .. Raspberry Pi (Debian Wheezy), Ubuntu, ... etc etc. I figured surely one of them would work for Porteus.
If you used the Berkeley Installer while running Porteus, it would be prudent to do a complete new install. I make it a rule myself not to use proferred installers.
I did . and I will. Boinc website mentioned some pros and CONS to using it. Seemed to me to be the only choice that might work.
You do not need a complete new install of Potreus if you installed boinc from Ubuntu.
Right . their package manager allows installs/uninstalls.
Porteus is a live system, and you only need to install the programs you need. They come as modules. So making the module is the equivalent of apt-get without installing. Installing is done through activation of the module for a particular application. Upon session end, everything gets uninstalled from system, just like the files one does not save. There is no installation per se in Porteus.
Ahah!! Here is the core of the issue. I am pretty sure I know what a 'live' system is ... but, I thought there was an option to install this OS to hard drive .. thereby having an install that behaved more like what ... shall we say a 'dead' system?? There's the pkg manager etc etc ... use it much like I would Ubuntu ... no 'cheat' things .. whatever they are, or what one deals with on a 'live' system. I took that option. Before we go any further, is my premise correct? Install to HD and I have a system that behaves 'like' Ubuntu ... where pkg manager etc is concerned??? If not, then I have the wrong OS.

I should explain why I left Lubuntu ... looking for a 'smaller' OS. This machine is quite short on resources. 512MB memory, 8GB hard drive. Lubuntu took too much of it even though all I had on it was Boinc and Firefox. All I want to do is BOINC on this machine .. night and day. I figured Porteus to be just right for that. I tried Damn Small Linux and it would not see my network card (Ethernet). I tried Tiny Core and it did not work out either. There seems to be hundreds of choices ... so maybe I need to back up to a different OS. Recommendations are welcome if Porteus is not the one.
So, to allay your worries, start Porteus in Always Fresh mode (without saving changes), I think that option is included when you choose copy2ram in the boot menu, or someone will put me right, there. If you are not saving changes, everything in your home directory will disappear at session end, so no worries.
Uhm ... I don't think a LIVE system is for me, and it sounds like the above is how to use it as a live system. I am much more comfortable with a "dead" one ... if you get my meaning.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#11 by Bogomips » 07 Sep 2015, 22:05

wacojohn wrote:Recommendations are welcome if Porteus is not the one.
Checked memory requirements. Seems ok. If you are willing to learn you can certainly use Porteus, which you should be able to do with 6+ years Linux experience. You can get a lot of help Linux-wise from the community. If you just want to run boinc, then you do not need to have recourse to a package manager, and I can provide you with the module in due course. Let us know.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3322
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: boinc???

Post#12 by Ed_P » 07 Sep 2015, 23:37

wacojohn wrote:Uhm ... I don't think a LIVE system is for me, and it sounds like the above is how to use it as a live system. I am much more comfortable with a "dead" one ... if you get my meaning.
Porteus is a LIVE system in that it is easy to add apps/modules to it without installing them, whether on a hard drive or a USB drive. And changes can be saved or not saved, depending on how you are set up. Does it take some getting use to, sure, but what new thing doesn't. Is it worth it, I think so. :)
Ed

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: boinc???

Post#13 by cttan » 08 Sep 2015, 00:44

Hi wacojohn,

I am using 64 bit Porteus and require these 2 dependencies:-
libmspack-0.3alpha
wxPython-2.8.12.1


You can get the deps from USM:-
# usm -u all

# usm -g libmspack
# usm -g wxPython

You should be go to go after installing the deps and run
sh /<BOINC folder>/run_manager
In your case, maybe
# ~/BOINC/run_manager

wacojohn
Samurai
Samurai
Posts: 107
Joined: 04 Sep 2015, 18:26
Distribution: Porteus 3.1
Location: Waco, TX

Re: boinc???

Post#14 by wacojohn » 08 Sep 2015, 01:02

Bogomips wrote:
wacojohn wrote:Recommendations are welcome if Porteus is not the one.
Checked memory requirements. Seems ok. If you are willing to learn you can certainly use Porteus, which you should be able to do with 6+ years Linux experience. You can get a lot of help Linux-wise from the community. If you just want to run boinc, then you do not need to have recourse to a package manager, and I can provide you with the module in due course. Let us know.
Thanks to all who have replied. You guys are phenomenal, and I am privileged to be here ... NO DOUBT.

I would LOVE to master Porteus .... so I will take you up on your offers ... effectively run BOINC on it. I have the Porteus CD which I already did a HD install from ... and ASSUME I did THAT right. However, as mentioned before, best to start ALL over ... from it.

I will attempt to redo that .... from memory ... and hope I get it all right. At that point, I am your grateful servant. This .... UNLESS any of you advise a different installation .... so I will wait to hear.

Objective: Run Boinc ... with little or nothing else .. using this interesting OS. Utilize 512MB/8GB for as little else as possible. Hopefully, Boinc will present the way I am accustomed to . with a Boinc Manager that offers many services. If not ... I will have to learn.

Please ... do this at your leisure ... I have taken enough of your valuable time.

EDIT: By the way, .. I am a retired technical documentation editor (of sorts). What that means is once I get ALL the steps down, accomplished, and tested, I will be glad to write a tutorial on this topic . for the benefit of others ... if that holds any value to you/moderators.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: boinc???

Post#15 by Bogomips » 08 Sep 2015, 12:05

wacojohn wrote:EDIT: By the way, .. I am a retired technical documentation editor (of sorts). What that means is once I get ALL the steps down, accomplished, and tested, I will be glad to write a tutorial on this topic . for the benefit of others ... if that holds any value to you/moderators.
Tried to give a brief explanation of the system, which can be expanded upon by you when you have learnt the ropes. However IMHO it is at your stage of 'OK have installed Porteus, what now?', that needs documentation. Basically something which Newbies can refer to as they grope their way along. For me it was to get the essential apps going: favourite text editor, filemanager, browser, word processor of choice.

There is quite a bit of information on the web page, but have tended to go round in circles when wished to look up something. Now using Info > Tips and Tricks, as makeshift table of contents, which tends to serve me well.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

Locked