Porteus

Set up on fat32 usb and ran pman -Syu after setting the initial configs via automated scripts.

Ran and am looking at a desktop after rebooting. Did the same for firefox but when I went to activate the module the error that returned indicated that there was a missing "xactivate" from /usr/local/bin line 90

root ~ # activate /mnt/sdd1/nemesis/modules/firefox-41.0.2-1-x86_64.bundle.xzm
/usr/local/bin/activate: line 90: /usr/local/bin/xactivate: No such file or directory

Hit pman for the missing package via a but no returns

Once again, I am on stage 001 at the moment. There is no X. It will come soon. Please test and report bugs only related to 001. Example, try the config scripts in the config folder. Boot to text mode and run things like: setup-time

The scripts are found in /usr/local/bin /usr/local/sbin

is having /usr/local/bin/, /sbin/, /share/ .. in /rootcopy a temporary thing or a permanent feature?

Temporary. Will correct my scripts. Thanks.

For one reason or another my nemesis 151022 install on hdd will not run the wizard. This seems to result in an inability to run /usr/bin/pman which will exit:
no modules config

Did you copy the config folder onto the install media?

Yes:
/64bit_v31_nemesis/config/modules

Do any units fail during boot?

Presently, I am on my second linux box. I have found that two installation one on root and the other in a subfolder seems to be mixing nemesis, maybe due to nemesis.sgn.

On the toshiba satellite z930. First run does not work on an installation hdd with eos on the same partition. /usr/local/bin/firstrun has to be started manually.
In addition, error message for network config:
no gateway, connection failure
error message time config:
unfortunately cannot write to /mnt/sda2/config/time, not writable
** file is on /mnt/sda2/64bit_nemesis/config/time

There is a write check on sda2 which does not pass. What is the files system?

Can you test with: [ ! -w /mnt/sda2 ] && echo unwritable

The problem seems to be related to a nemesis subfolder installation. I will have to wait tomorrow, the satellite z930 is at the office. This is evening time with nemesis on the msi340x, here I am working only directly on /.

Ah, i see. Yes you're right.

Please boot on the problem machine and give the output of: I have exported all the paths as environment variables. BOOTDEV is the boot device while BASEDIR is the path to the nemesis folder. In some scripts I notice I have used BOOTDEV for the root of the install.

echo $BOOTDEV
/mnt/sda2
echo $BASEDIR
/mnt/sda2/64bit_v31_nemesis

Thanks. Will see that this is fixed.