brokenman wrote:The default root password is: toor
Inside the porteus settings centre there is a button to edit the porteus.cfg file. If you find this doesn't open the correctly then you will need to open it another way. You can try right clicking on the file and 'open with application' or a better option would be to open a terminal and change to root.
To do this ... open the terminal and type: su followed by the root password. Then open the file in kwrite using: kwrite /mnt/sdxY/boot/syslinux/porteus.cfg
Substitute the xY for the path to your drive containing Porteus. You can get this from the console with: cat /var/log/porteus-livedbg
It will be just under "Porteus data found in".
It would also be helpful to know what trouble you had with the installer. We'd like to make Porteus as easy to install as possible.
Hi François
Porteus-v2.1
RAZOR
Kernel: 3.9.4-porteus
I'm sorry I didn't get back to you yesterday. It was a very busy day. I think I may have found the source of the problem. It appears that when I make the .dat file to the root of my Thumb Drive (FAT32) it doesn't make the file or, the file is unreadable. The progress box says it is converting and making the file. Then within 2 or 3 seconds it says it has completed and that I need to change the .cfg files bla bla. When I check the root of the thumb drive via the file manager there is no .dat file. It does showup it I try to recreate a .dat using the Porteus save File Manager, albeit greyed out. I thought that the process was a little too quick. Opening kwrite to double check using kwrite /mnt/sdxY(sdb1)/boot/syslinux/porteus.cfg from the terminal opens a blank kwrite page. If I click on the open tab, it goes into meltdown and crashes.
I tested it with a different build of Porteus with RAZOR desktop. The GUI install for USB worked as described. Again the Portius save File Mangager says it is creating .dat file in the chosen location, (root of the thumb drive) and shows up greyed out. When I open the Portius Settings Centre and navigate to Portius Changes/Edit Porteus .cfg this time it opens up with no problem. However I cannot find any reference to the saved .dat file. See Below:
Fig 1
PROMPT 0
TIMEOUT 90
UI vesamenu.c32
DEFAULT razor
MENU BACKGROUND porteus.png
MENU TITLE Porteus-2.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 #ffA32F2F #30003f07 none
menu color unsel 37;44 #ff111B78 #003f7fbf none
menu color hotkey 1;37;44 #ff8037b7 #00000000 none
menu color sel 7;37;40 #ffffffff #00000000 none
menu color hotsel 1;7;37;40 #ffaf67f7 #003f7fbf none
menu color scrollbar 30;44 #00000000 #00000000 none
menu color tabmsg 31;40 #ffA32222 #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 #ff666C85 #00000000 none
menu color msg07 37;40 #90ffffff #00000000 std
LABEL razor
MENU LABEL Graphics mode (razor)
KERNEL vmlinuz
APPEND initrd=initrd.xz changes=/porteus zram=60% timezone=Europe/Amsterdam kmap=uk
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 zram=60% timezone=Europe/Amsterdam kmap=uk
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 zram=60% timezone=Europe/Amsterdam kmap=uk
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 zram=60% timezone=Europe/Amsterdam kmap=uk
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 zram=60% timezone=Europe/Amsterdam kmap=uk
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
It maybe my inexperience with Linux and the solution is there, (can't see the tree because the forest is in the way) lol!
As for the trying to install Porteous 2 to a USB stick problems. This was from the official down site,
http://www.porteus.org/. I was using the XFCE version. The iso was unpacked to the Desktop. I was logged in as 'root' and the usb stick was freshly formatted to FAT32. The Porteus installer was opened and the instructions followed. When I get to the final checks, I check the boxes and click next. The progress box opens for a nano second and then closes. The task completed message appears. The first time I did this, I thought to myself this Porteus is ridiculously fast. Of course nothing had happened and there was no Bootable USB stick. I tried several times after rebooting the result was the same bar one time it worked. I tried to repeat this with no success. The terminal install worked with no problems.
I hope the additional info helps.
Groetjes
Andy Mitchell