Unable to save settings

Post#1 by **nnriyer** » 12 Aug 2020, 14:07

Not able to save setting in browser after rebooting. This is linux partition installation. (ext4). The downloaded folder is empty after rebooting and time changes to not saving. Porteus RC5.2. As per the information available, there is no need of creating save file. Moreover, the unable to create save file.

Post#2 by **babam** » 13 Aug 2020, 06:41

nnriyer, changes=/dev/sdXX http://www.porteus.org/tutorials/26-gen ... -them.html

Post#3 by **nnriyer** » 13 Aug 2020, 14:07

As per your instruction, changes have been made, still not saving my settings in system and changes made in browser, etc.

see below my file

Code: Select all

PROMPT 0
TIMEOUT 90
UI vesamenu.c32
DEFAULT GRAPHICAL
MENU BACKGROUND porteus.png
MENU TITLE Porteus-5.0 64bit

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 GRAPHICAL
MENU LABEL Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=/dev/sda7
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 /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND nomagic base_only norootcopy
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 /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=/dev/sda7
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 /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND 3
TEXT HELP
    Run Porteus in text mode and
    start the command prompt only
ENDTEXT

LABEL pxe-boot
MENU LABEL Porteus as PXE server
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND pxe
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 /boot/syslinux/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

Post#4 by **Ed_P** » 13 Aug 2020, 23:08

On linux formatted partitions I thought the default location was the /porteus/changes/ folder and was automatic.

On my system with ntfs partitions I use a change code like this:

changes=EXIT:/porteus5.0/changes/porteussave.dat

with the /porteus5.0 folder on the root partition and the porteussave.dat file created by the Menu>Admin>Porteus Save File Manager before saving changes. And my save.dat file is 402MB.

Post#5 by **babam** » 14 Aug 2020, 09:40

nnriyer,

Code: Select all

$ mount | grep '^/dev' | grep -v '/dev/loop'

Post#6 by **nnriyer** » 14 Aug 2020, 15:14

oot@porteus:/home/guest# mount | grep '^/dev' | grep -v '/dev/loop'
/dev/sda1 on /mnt/sda1 type fuseblk (rw,noatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/sda2 on /mnt/sda2 type fuseblk (rw,noatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/sda3 on /mnt/sda3 type ext4 (rw,noatime,nodiratime)
/dev/sda5 on /mnt/sda5 type ext4 (rw,noatime,nodiratime)
/dev/sda6 on /mnt/sda6 type ext4 (rw,noatime,nodiratime)
/dev/sda7 on /mnt/sda7 type ext4 (rw,noatime,nodiratime)

Note : I have installed in sda7. ( full partition)

Post#7 by **babam** » 14 Aug 2020, 22:51

nnriyer,

Code: Select all

$ ls /mnt/sda7
$ cat /proc/cmdline

Post#8 by **nnriyer** » 15 Aug 2020, 03:39

guest@porteus:~$ ls /mnt/sda7
EFI/ boot/ porteus/
guest@porteus:~$ cat /proc/cmdline
quiet root=UUID=4bf85d63-b0ad-4dc6-8ce3-889c26fc3e83 rw
guest@porteus:~$

Post#9 by **babam** » 15 Aug 2020, 04:53

nnriyer wrote: ↑
15 Aug 2020, 03:39
cat /proc/cmdline
quiet root=UUID=4bf85d63-b0ad-4dc6-8ce3-889c26fc3e83 rw

This is odd, why is the output without changes=/dev/sda7?

Post#10 by **ncmprhnsbl** » 15 Aug 2020, 05:43

odd indeed...
try:

Code: Select all

cat /etc/bootcmd.cfg

Post#11 by **nnriyer** » 15 Aug 2020, 06:54

uest@porteus:~$ cat /etc/bootcmd.cfg
quiet
root=UUID=4bf85d63-b0ad-4dc6-8ce3-889c26fc3e83
rw
guest@porteus:~$

Post#12 by **nnriyer** » 15 Aug 2020, 06:56

babam wrote: ↑
15 Aug 2020, 04:53
This is odd, why is the output without changes=/dev/sda7?

Please clarify?

Now, I have also changed the settings like changes=porteus/save.dat. Still not saving.

Post#13 by **beny** » 15 Aug 2020, 08:47

hi save.dat is a container formatted fat 32 if you do not make it first you can't save files ...
/mnt/sdj1/porteus/changes/ the changes folder is inside the porteus folder or you can have it outside the partition but you have to edit the whole path to it

LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=/porteus
TEXT HELP
Run Porteus the best way we can.
Try to autoconfigure graphics
card and use the maximum
allowed resolution
ENDTEXT

Post#14 by **nnriyer** » 15 Aug 2020, 09:27

Now I dont know how to proceed further . In my front road bloc.

Post#15 by **beny** » 15 Aug 2020, 09:57

hi, you have the changes folder inside the porteus folder,if yes you have only do your tweak on system and you have at your next boot, your append line is too generic:APPEND changes=/dev/sda7
/run/media/root/7abe3dd6-7848-4d73-86da-6e83ed9292e0/porteus/base
/run/media/root/7abe3dd6-7848-4d73-86da-6e83ed9292e0/porteus/changes
/run/media/root/7abe3dd6-7848-4d73-86da-6e83ed9292e0/porteus/modules
/run/media/root/7abe3dd6-7848-4d73-86da-6e83ed9292e0/porteus/optional
/run/media/root/7abe3dd6-7848-4d73-86da-6e83ed9292e0/porteus/rootcopy
/run/media/root/7abe3dd6-7848-4d73-86da-6e83ed9292e0/porteus/make_iso.sh
/run/media/root/7abe3dd6-7848-4d73-86da-6e83ed9292e0/porteus/porteus-v5.0-x86_64.cfg
i am on another system so i have mounted the porteus system to show you the directories list.