Page 8 of 13

Re: boinc???

Posted: 22 Oct 2015, 21:31
by wacojohn
Bogomips wrote:Now reboot using last porteus.cfg, and everything should be back.
must have done something wrong. Nothing missing came back;

porteus.cfg

Code: Select all

LABEL XFCE
MENU LABEL Graphics mode (XFCE)
KERNEL vmlinuz
APPEND initrd=initrd.xz fsck timezone=US/Central utc cliexec=boinc~--dir~/mnt/sda1/disk/BOINC~--daemon guiexec=/mnt/sda1/disk/BOINC/boinc_mgr
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT
porteus.cln

Code: Select all

LABEL XFCE
MENU LABEL Graphics mode (XFCE)
KERNEL vmlinuz
APPEND initrd=initrd.xz fsck timezone=US/Central utc cliexec=boinc~--dir~/mnt/sda1/disk/BOINC~--daemon guiexec=/mnt/sda1/disk/BOINC/boinc_mgr
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT
porteus.bnc

Code: Select all

LABEL XFCE
MENU LABEL Graphics mode (XFCE)
KERNEL vmlinuz
APPEND initrd=initrd.xz  changes=EXIT:/disk fsck timezone=US/Central utc cliexec=boinc~--dir~/mnt/sda1/disk/BOINC~--daemon guiexec=/mnt/sda1/disk/BOINC/boinc_mgr
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT
porteus.tst

Code: Select all

LABEL XFCE
MENU LABEL Graphics mode (XFCE)
KERNEL vmlinuz
APPEND initrd=initrd.xz fsck timezone=US/Central utc
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT
I am sorry. I am a disabled Viet Nam Vet with 'minor' concentration problems. When things get too convoluted, I might miss something. I am very sorry. Please .. look this over and see if you can rescue me. So sorry.

Also, have to leave house for a FEW hours. Will check as soon as I get back.

Re: boinc???

Posted: 22 Oct 2015, 23:22
by Bogomips
^Not necessarily done something wrong. Let's see what the command line looked like & what porteus did:

Code: Select all

cat /proc/cmdline
cat /var/log/porteus-livedbg

Re: boinc???

Posted: 22 Oct 2015, 23:43
by wacojohn

Code: Select all

guest@porteus:~$ cat /proc/cmdline
quiet initrd=initrd.xz fsck timezone=US/Central utc cliexec=boinc~--dir~/mnt/sda1/disk/BOINC~--daemon guiexec=/mnt/sda1/disk/BOINC/boinc_mgr BOOT_IMAGE=vmlinuz 
guest@porteus:~$ cat /var/log/porteus-livedbg
# Recognized devices:
/dev/sda1: LABEL="Porteus" UUID="c939d1c2-09d0-40c5-ad05-b731ccf9d66d" SEC_TYPE="ext2" TYPE="ext3" 
/dev/sda2: LABEL="Porteus Swap" UUID="dd28b0f1-74ea-455a-8ca7-ba09e4dfc9d6" TYPE="swap" 

# Booting device:
/mnt/sda1

# Porteus data found in:
/mnt/sda1/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/sda1/porteus/base/000-kernel.xzm
/mnt/sda1/porteus/base/001-core.xzm
/mnt/sda1/porteus/base/001-core_alldesktops-150124.xzm
/mnt/sda1/porteus/base/002-xorg.xzm
/mnt/sda1/porteus/base/002-xorg_alldesktops-150126.xzm
/mnt/sda1/porteus/base/003-xfce.xzm
/mnt/sda1/porteus/base/004-xfce_fixes-150124.xzm
/mnt/sda1/porteus/base/0099-settings.xzm
/mnt/sda1/porteus/base/04-firefox.xzm
/mnt/sda1/porteus/modules/boinc-7.2.42.i686.xzm
/mnt/sda1/porteus/modules/flashplayer-plugin-11.2.202.540-i386-1alien.xzm
/mnt/sda1/porteus/modules/nVidia-304.123-porteus-v3.1-i486-1ftm.xzm
guest@porteus:~$ 
If I am not mistaken, porteus.cfg and porteus.cln have the same content.

Re: boinc???

Posted: 23 Oct 2015, 00:32
by Bogomips
^ Expected last porteus.cfg append line to look like

Code: Select all

APPEND initrd=initrd.xz fsck timezone=US/Central utc
For when not testing just append changes=EXIT:/disk to line in /mnt/sda1/boot/syslinux/porteus.cfg to give a line like

Code: Select all

APPEND initrd=initrd.xz fsck timezone=US/Central utc changes=EXIT:/disk
The porteus.cfg with this line would then be used for rebooting, and hopefully restoring all saved changes.

Reboot followed by

Code: Select all

cat /proc/cmdline
cat /var/log/porteus-livedbg
Update Preparation

From post with miscellaneous modules need to download the systemd and gtk3 modules into /mnt/sda1/disk and verify md5 sums of downloaded modules.

Code: Select all

ls -lh /mnt/sda1/disk
To check everything is there.

Re: boinc???

Posted: 23 Oct 2015, 01:09
by Ed_P
Bogomips wrote:@Ed_P Any idea why changes folder approaching 1GB?
Changes? :Search:

I use changes=EXIT: and that limits changes to select folders. No /tmp changes for example. And my primary save.dat files are less than .5 GB.

I use this script to check my save.dat usage:

savedatspaceused.sh

Code: Select all

#!/bin/sh
#  http://forum.porteus.org/viewtopic.php?f=81&t=1941&start=15#p13272
#  http://forum.porteus.org/viewtopic.php?f=117&t=3205&p=25099#p25097

#  mloop requires changes= cheatcodes not used (Always Fresh mode)

BOOTDEV=`grep -A1 "Booting" /var/log/porteus-livedbg|tail -n1|sed 's^//^/^g'`
VERSION=$(cat /etc/porteus-version)
FOLDER=porteus${VERSION:9:3}
GUEST="$BOOTDEV/$FOLDER/Guest"
MODULES="$BOOTDEV/$FOLDER/Modules"
MYARCH=i586
if [ `arch` = x86_64 ]; then
   MYARCH=x86_64
   MODULES="$BOOTDEV/$FOLDER/Modules"
fi
if [ -d $BOOTDEV/Modules ]; then
   MODULES="$BOOTDEV/Modules"
fi

# Color definitions
txtbld=$(tput bold)               # Bold
txtred=${txtbld}$(tput setaf 1)   # Red
rst=$(tput sgr0)                  # Reset

function redpswd() {
echo -e "$1" $txtred  
}

if [ `whoami` != "root" ]; then
    redpswd "Enter root's password"
    su -c "sh $0 $1"
    exit
fi
echo $rst

if [ -a /mnt/live/memory/images/changes ]; then
   SPACEDATDIR=/mnt/live/memory/images/changes 
else
   echo mloop $BOOTDEV/$FOLDER/changes/porteussave.dat
   mloop $BOOTDEV/$FOLDER/changes/porteussave.dat
   SPACEDATDIR=/mnt/loop
fi

echo
echo du -sh
du -sh ${SPACEDATDIR}     # Show the amount used   
echo df -h
df -h  ${SPACEDATDIR}     # Show filesystem summary
echo
du -sh ${SPACEDATDIR}/etc
du -sh ${SPACEDATDIR}/home
du -sh ${SPACEDATDIR}/opt
du -sh ${SPACEDATDIR}/root
du -sh ${SPACEDATDIR}/usr
du -sh ${SPACEDATDIR}/var
echo
if [ -d "${SPACEDATDIR}/home/guest/.PlayOnLinux" ]; then
  du -sh ${SPACEDATDIR}/home/guest/.PlayOnLinux
fi
du -sh ${SPACEDATDIR}/home/guest/.wine
echo
echo Press Enter for more details, Ctrl+C to end.
read 
du -sh  ${SPACEDATDIR}/etc/usm
echo ls ${SPACEDATDIR}/etc/usm
ls      ${SPACEDATDIR}/etc/usm
#cat     ${SPACEDATDIR}/etc/usm/usm.conf
echo
du -sh  ${SPACEDATDIR}/var/log
du -sh  ${SPACEDATDIR}/var/usm
du -h   ${SPACEDATDIR}/var/usm/*
echo
du -sh  ${SPACEDATDIR}/home/guest/Downloads
du -sh  ${SPACEDATDIR}/home/guest/Desktop
du -h   ${SPACEDATDIR}/home/guest/Backups
echo
echo ls -s   ${SPACEDATDIR}/home/guest/Backups/FireFox
ls -s   ${SPACEDATDIR}/home/guest/Backups/FireFox
echo
du  -h ${SPACEDATDIR}/*|grep '[0-9][0-9]M'

if [ -a /mnt/live/memory/images/changes ]; then
   echo  
   echo "For more info use:" 
   echo " du -h /mnt/live/memory/images/changes/home/guest*"
   echo " du -h /mnt/live/memory/images/changes/home/*" and
   echo " du -h /mnt/live/memory/images/changes/*|grep  '[0-9][0-9]M'"
else
   uloop 
fi
Adjust the variables to fit your system.

Re: boinc???

Posted: 23 Oct 2015, 01:17
by wacojohn
Bogomips wrote:^ Expected last porteus.cfg append line to look like

Code: Select all

APPEND initrd=initrd.xz fsck timezone=US/Central utc
For when not testing just append changes=EXIT:/disk to line in /mnt/sda1/boot/syslinux/porteus.cfg to give a line like

Code: Select all

APPEND initrd=initrd.xz fsck timezone=US/Central utc changes=EXIT:/disk
The porteus.cfg with this line would then be used for rebooting, and hopefully restoring all saved changes.

Reboot followed by

Code: Select all

cat /proc/cmdline
cat /var/log/porteus-livedbg
OK, .. I am having problems discerning rhetoric from instructions. I just rebooted with the following porteus.cfg:

Code: Select all

PROMPT 0
TIMEOUT 90
UI vesamenu.c32
DEFAULT XFCE
MENU BACKGROUND porteus.png
MENU TITLE Porteus-3.1 32bit

MENU WIDTH 30
MENU MARGIN 2
MENU ROWS 10
MENU HELPMSGROW 17
MENU TIMEOUTROW 28
MENU TABMSGROW 15
MENU CMDLINEROW 22
MENU HSHIFT 4
MENU VSHIFT 5

	menu color screen	37;40      #00000000 #00000000 none
	menu color border	30;44      #00000000 #00000000 none
	menu color title	1;36;44    #ffF6FF00 #30003f07 none
	menu color unsel	37;44      #ffffffff #00000000 none
	menu color hotkey	1;37;44    #ff8037b7 #00000000 none
	menu color sel		7;37;40    #ff111B78 #003f7fbf none
	menu color hotsel	1;7;37;40  #ffaf67f7 #003f7fbf none
	menu color scrollbar	30;44      #00000000 #00000000 none

	menu color tabmsg	31;40      #ffB6F538 #00000000 none
	menu color cmdmark	1;36;40    #ffff0000 #00000000 none
	menu color cmdline	37;40      #ffffffff #ff000000 none
	menu color pwdborder	30;47      #ffff0000 #00000000 std
	menu color pwdheader	31;47      #ffff0000 #00000000 std
	menu color pwdentry	30;47      #ffff0000 #00000000 std
	menu color timeout_msg	37;40      #ff809aef #00000000 none
	menu color timeout	1;37;40    #ffb72f9f #00000000 none
	menu color help		37;40      #ffD5F538 #00000000 none
	menu color msg07	37;40      #90ffffff #00000000 std


LABEL XFCE
MENU LABEL Graphics mode (XFCE)
KERNEL vmlinuz
APPEND initrd=initrd.xz fsck timezone=US/Central utc
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL fresh
MENU LABEL Always Fresh
KERNEL vmlinuz
APPEND initrd=initrd.xz nomagic base_only norootcopy fsck timezone=US/Central utc
TEXT HELP
    Normally Porteus saves all changes
    to the /porteus/changes/ directory
    on the boot media (if writable)
    and restores them next boot.
    Use this option to start a fresh
    system, changes are not read from
    or written to any device
ENDTEXT

LABEL copy2ram
MENU LABEL Copy To RAM
KERNEL vmlinuz
APPEND initrd=initrd.xz copy2ram fsck timezone=US/Central utc
TEXT HELP
    Run Porteus the same as above,
    but first copy all data to RAM
    to get a huge speed increase
    (needs >768MB)
ENDTEXT

LABEL text
MENU LABEL Text mode
KERNEL vmlinuz
APPEND initrd=initrd.xz 3 fsck timezone=US/Central utc
TEXT HELP
    Run Porteus in text mode and
    start the command prompt only
ENDTEXT

LABEL pxe-boot
MENU LABEL Porteus as PXE server
KERNEL vmlinuz
APPEND initrd=initrd.xz pxe fsck timezone=US/Central utc
TEXT HELP
    Run Porteus as usual, but also
    initialize a PXE server.
    This will allow you to boot Porteus
    on other computers over a network
ENDTEXT

MENU SEPARATOR

LABEL plop
MENU LABEL PLoP BootManager
KERNEL plpbt
TEXT HELP
    Run the plop boot manager.
    This utility provides handy
    boot-USB options for machines
    with vintage/defective BIOS
ENDTEXT

LABEL hd
MENU LABEL Boot from the first hd
COM32 chain.c32
APPEND hd0 1
TEXT HELP
    Don't start Porteus at all, but
    rather run any operating system
    installed on the first partition
    of the hard drive
ENDTEXT
because you said that is what you expected the file to say. On reboot, all 'missing' objects are still missing. I assume you meant to use this porteus.cfg:

Code: Select all

PROMPT 0
TIMEOUT 90
UI vesamenu.c32
DEFAULT XFCE
MENU BACKGROUND porteus.png
MENU TITLE Porteus-3.1 32bit

MENU WIDTH 30
MENU MARGIN 2
MENU ROWS 10
MENU HELPMSGROW 17
MENU TIMEOUTROW 28
MENU TABMSGROW 15
MENU CMDLINEROW 22
MENU HSHIFT 4
MENU VSHIFT 5

	menu color screen	37;40      #00000000 #00000000 none
	menu color border	30;44      #00000000 #00000000 none
	menu color title	1;36;44    #ffF6FF00 #30003f07 none
	menu color unsel	37;44      #ffffffff #00000000 none
	menu color hotkey	1;37;44    #ff8037b7 #00000000 none
	menu color sel		7;37;40    #ff111B78 #003f7fbf none
	menu color hotsel	1;7;37;40  #ffaf67f7 #003f7fbf none
	menu color scrollbar	30;44      #00000000 #00000000 none

	menu color tabmsg	31;40      #ffB6F538 #00000000 none
	menu color cmdmark	1;36;40    #ffff0000 #00000000 none
	menu color cmdline	37;40      #ffffffff #ff000000 none
	menu color pwdborder	30;47      #ffff0000 #00000000 std
	menu color pwdheader	31;47      #ffff0000 #00000000 std
	menu color pwdentry	30;47      #ffff0000 #00000000 std
	menu color timeout_msg	37;40      #ff809aef #00000000 none
	menu color timeout	1;37;40    #ffb72f9f #00000000 none
	menu color help		37;40      #ffD5F538 #00000000 none
	menu color msg07	37;40      #90ffffff #00000000 std


LABEL XFCE
MENU LABEL Graphics mode (XFCE)
KERNEL vmlinuz
APPEND initrd=initrd.xz fsck timezone=US/Central utc changes=EXIT:/disk
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL fresh
MENU LABEL Always Fresh
KERNEL vmlinuz
APPEND initrd=initrd.xz nomagic base_only norootcopy fsck timezone=US/Central utc
TEXT HELP
    Normally Porteus saves all changes
    to the /porteus/changes/ directory
    on the boot media (if writable)
    and restores them next boot.
    Use this option to start a fresh
    system, changes are not read from
    or written to any device
ENDTEXT

LABEL copy2ram
MENU LABEL Copy To RAM
KERNEL vmlinuz
APPEND initrd=initrd.xz copy2ram fsck timezone=US/Central utc
TEXT HELP
    Run Porteus the same as above,
    but first copy all data to RAM
    to get a huge speed increase
    (needs >768MB)
ENDTEXT

LABEL text
MENU LABEL Text mode
KERNEL vmlinuz
APPEND initrd=initrd.xz 3 fsck timezone=US/Central utc
TEXT HELP
    Run Porteus in text mode and
    start the command prompt only
ENDTEXT

LABEL pxe-boot
MENU LABEL Porteus as PXE server
KERNEL vmlinuz
APPEND initrd=initrd.xz pxe fsck timezone=US/Central utc
TEXT HELP
    Run Porteus as usual, but also
    initialize a PXE server.
    This will allow you to boot Porteus
    on other computers over a network
ENDTEXT

MENU SEPARATOR

LABEL plop
MENU LABEL PLoP BootManager
KERNEL plpbt
TEXT HELP
    Run the plop boot manager.
    This utility provides handy
    boot-USB options for machines
    with vintage/defective BIOS
ENDTEXT

LABEL hd
MENU LABEL Boot from the first hd
COM32 chain.c32
APPEND hd0 1
TEXT HELP
    Don't start Porteus at all, but
    rather run any operating system
    installed on the first partition
    of the hard drive
ENDTEXT
but I do not elect to make assumptions any longer. So .... please ... no rhetoric ... just simple step by step instructions as to what to do next. If it is answer a question, .... I will, if it is to do something, make it clear and simple, and I will do it and give you the results.

I want to impress on you that the problem IS ME ... not YOU. Thank you immensely for your patience.

Re: boinc???

Posted: 23 Oct 2015, 01:33
by Ed_P
wacojohn wrote: I am a disabled Viet Nam Vet
FWIW Your in good company, I'm a Viet Nam vet also.

Re: boinc???

Posted: 23 Oct 2015, 01:37
by wacojohn
Ed_P wrote:
wacojohn wrote: I am a disabled Viet Nam Vet
FWIW Your in good company, I'm a Viet Nam vet also.
I am in excellent company, Brother. EVERYONE here has been terrific .... amazing support. BogoMips ... especially.

Re: boinc???

Posted: 23 Oct 2015, 12:22
by Bogomips
wacojohn wrote: I assume you meant to use this porteus.cfg:[/b]

Code: Select all

PROMPT 0
TIMEOUT 90
UI vesamenu.c32
DEFAULT XFCE
MENU BACKGROUND porteus.png
MENU TITLE Porteus-3.1 32bit

MENU WIDTH 30
MENU MARGIN 2
MENU ROWS 10
MENU HELPMSGROW 17
MENU TIMEOUTROW 28
MENU TABMSGROW 15
MENU CMDLINEROW 22
MENU HSHIFT 4
MENU VSHIFT 5

	menu color screen	37;40      #00000000 #00000000 none
	menu color border	30;44      #00000000 #00000000 none
	menu color title	1;36;44    #ffF6FF00 #30003f07 none
	menu color unsel	37;44      #ffffffff #00000000 none
	menu color hotkey	1;37;44    #ff8037b7 #00000000 none
	menu color sel		7;37;40    #ff111B78 #003f7fbf none
	menu color hotsel	1;7;37;40  #ffaf67f7 #003f7fbf none
	menu color scrollbar	30;44      #00000000 #00000000 none

	menu color tabmsg	31;40      #ffB6F538 #00000000 none
	menu color cmdmark	1;36;40    #ffff0000 #00000000 none
	menu color cmdline	37;40      #ffffffff #ff000000 none
	menu color pwdborder	30;47      #ffff0000 #00000000 std
	menu color pwdheader	31;47      #ffff0000 #00000000 std
	menu color pwdentry	30;47      #ffff0000 #00000000 std
	menu color timeout_msg	37;40      #ff809aef #00000000 none
	menu color timeout	1;37;40    #ffb72f9f #00000000 none
	menu color help		37;40      #ffD5F538 #00000000 none
	menu color msg07	37;40      #90ffffff #00000000 std


LABEL XFCE
MENU LABEL Graphics mode (XFCE)
KERNEL vmlinuz
APPEND initrd=initrd.xz fsck timezone=US/Central utc changes=EXIT:/disk
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL fresh
MENU LABEL Always Fresh
KERNEL vmlinuz
APPEND initrd=initrd.xz nomagic base_only norootcopy fsck timezone=US/Central utc
TEXT HELP
    Normally Porteus saves all changes
    to the /porteus/changes/ directory
    on the boot media (if writable)
    and restores them next boot.
    Use this option to start a fresh
    system, changes are not read from
    or written to any device
ENDTEXT

LABEL copy2ram
MENU LABEL Copy To RAM
KERNEL vmlinuz
APPEND initrd=initrd.xz copy2ram fsck timezone=US/Central utc
TEXT HELP
    Run Porteus the same as above,
    but first copy all data to RAM
    to get a huge speed increase
    (needs >768MB)
ENDTEXT

LABEL text
MENU LABEL Text mode
KERNEL vmlinuz
APPEND initrd=initrd.xz 3 fsck timezone=US/Central utc
TEXT HELP
    Run Porteus in text mode and
    start the command prompt only
ENDTEXT

LABEL pxe-boot
MENU LABEL Porteus as PXE server
KERNEL vmlinuz
APPEND initrd=initrd.xz pxe fsck timezone=US/Central utc
TEXT HELP
    Run Porteus as usual, but also
    initialize a PXE server.
    This will allow you to boot Porteus
    on other computers over a network
ENDTEXT

MENU SEPARATOR

LABEL plop
MENU LABEL PLoP BootManager
KERNEL plpbt
TEXT HELP
    Run the plop boot manager.
    This utility provides handy
    boot-USB options for machines
    with vintage/defective BIOS
ENDTEXT

LABEL hd
MENU LABEL Boot from the first hd
COM32 chain.c32
APPEND hd0 1
TEXT HELP
    Don't start Porteus at all, but
    rather run any operating system
    installed on the first partition
    of the hard drive
ENDTEXT
Yes. Use this porteus.cfg.

Reboot followed by

Code: Select all

cat /proc/cmdline
cat /var/log/porteus-livedbg
Update Preparation

From post with miscellaneous modules need to download the systemd and gtk3 modules into /mnt/sda1/disk and verify md5 sums of downloaded modules.

Code: Select all

ls -lh /mnt/sda1/disk
To check everything is there.

Re: boinc???

Posted: 23 Oct 2015, 13:33
by wacojohn
Yes. Use this porteus.cfg.
OK .. edited that porteus.cfg good and proper. Saved as porteus.cfg. Machine instantly froze. Hit pwr button, rebooted. ALL missing items appear to be back.
Reboot followed by

Code: Select all

cat /proc/cmdline
cat /var/log/porteus-livedbg

Code: Select all

guest@porteus:~$ cat /proc/cmdline
quiet initrd=initrd.xz fsck timezone=US/Central utc changes=EXIT:/disk BOOT_IMAGE=vmlinuz 
guest@porteus:~$ cat /var/log/porteus-livedbg
# Recognized devices:
/dev/sda1: LABEL="Porteus" UUID="c939d1c2-09d0-40c5-ad05-b731ccf9d66d" TYPE="ext3" SEC_TYPE="ext2" 
/dev/sda2: LABEL="Porteus Swap" UUID="dd28b0f1-74ea-455a-8ca7-ba09e4dfc9d6" TYPE="swap" 

# Booting device:
/mnt/sda1

# Porteus data found in:
/mnt/sda1/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/sda1/porteus/base/000-kernel.xzm
/mnt/sda1/porteus/base/001-core.xzm
/mnt/sda1/porteus/base/001-core_alldesktops-150124.xzm
/mnt/sda1/porteus/base/002-xorg.xzm
/mnt/sda1/porteus/base/002-xorg_alldesktops-150126.xzm
/mnt/sda1/porteus/base/003-xfce.xzm
/mnt/sda1/porteus/base/004-xfce_fixes-150124.xzm
/mnt/sda1/porteus/base/0099-settings.xzm
/mnt/sda1/porteus/base/04-firefox.xzm
/mnt/sda1/porteus/modules/boinc-7.2.42.i686.xzm
/mnt/sda1/porteus/modules/flashplayer-plugin-11.2.202.540-i386-1alien.xzm
/mnt/sda1/porteus/modules/nVidia-304.123-porteus-v3.1-i486-1ftm.xzm
/mnt/sda1//disk/changes
guest@porteus:~$ 
Will proceed according to your next instruction(s).

Re: boinc???

Posted: 23 Oct 2015, 17:20
by Bogomips
^ Step 6. of 2nd Post this thread, please.

Re: boinc???

Posted: 23 Oct 2015, 20:37
by wacojohn
Bogomips wrote:^ Step 6. of 2nd Post this thread, please.
Lot of instruction there that I don't understand:
Update Preparation

From post with miscellaneous modules download the systemd and gtk3 modules into /mnt/sda1/disk
Verify md5 sums of downloaded modules:

Code: Select all
md5sum /mnt/sda1/disk/*.xzm


Check everything is there

Code: Select all
ls -lh /mnt/sda1/disk
Entirely beyond my comprehension. Sorry. Unclear (to me) exactly what to download and from where. I am really sorry.

Re: boinc???

Posted: 23 Oct 2015, 21:30
by Bogomips
@wacojohn

Try Step 6 again. If it cannot be completed, it might be best, as suggested by you, to scrap the whole project. :wall:

Re: boinc???

Posted: 23 Oct 2015, 22:15
by wacojohn
Bogomips wrote:@wacojohn

Try Step 6 again. If it cannot be completed, it might be best, as suggested by you, to scrap the whole project. :wall:
Hmmm. That was easy. Somehow I was trying Step 6 in some other reply ...much more complex. :oops:

Code: Select all

guest@porteus:~$ md5sum /mnt/sda1/disk/*.xzm
6ce1ec528052982f00ce2df87acd0938  /mnt/sda1/disk/gtk3-3.16.7.i686-pkg-1.xzm
77fc39b5ec79b1dd3cfe9dfbb6f2c153  /mnt/sda1/disk/systemd-224-1-i686-0-kde.xzm
guest@porteus:~$ ls -lh /mnt/sda1/disk
total 47M
drwxr-xr-x  5 guest guest 4.0K Oct 23 14:54 BOINC/
dr-xr-xr-x 14 root  root  4.0K Oct 23 14:54 changes/
-rw-r--r--  1 root  root   35M Oct 23 17:00 gtk3-3.16.7.i686-pkg-1.xzm
-rw-r--r--  1 root  root   13M Oct 23 16:56 systemd-224-1-i686-0-kde.xzm
guest@porteus:~$
Last line Step 6, 2nd reply:
To be continued

Re: boinc???

Posted: 24 Oct 2015, 01:08
by Bogomips
^ All of Step 7. in 2nd Post of Thread.