Here you can post about non-standard installation methods
(for example when using grub4dos).
-
H3llGhost
- White ninja

- Posts: 14
- Joined: 22 Aug 2011, 11:46
- Location: localhost
Post#1
by H3llGhost » 25 Aug 2011, 12:05
Hello,
I tried today to create a pendrive with porteus. The windows sided variant works perfect, but for a "change saving" porteus, I need the .dat-container or a posix compatible file system.
So I decided to create a ext3 partition on the pendrive, copy the files and execute the lin_start_here.sh.
Here is the output:
Code: Select all
_.====.._
,:._ ~-_
'\ ~-_
\ \.
,/ ~-_
-..__..-'' PORTEUS ~~--..__
--==--==--==--==--==--==--==--==--==--==--==--==
Welcome to Porteus-v1.0
--==--==--==--==--==--==--==--==--==--==--==--==
[1] Check for Porteus update
[2] Read Porteus requirements
[3] Read Porteus installation instructions
[4] Read Porteus cheatcodes
[5] Read about bootloaders
[6] Install Porteus to EXTx partition (extlinux)
[7] Install Porteus to FATx partition (syslinux)
[8] Install Porteus to any partition (lilo)
no graphical - only text menu available
[9] Quit this application
Please choose a menu item ...
6
~/usb/porteus ~/usb/boot
-e \e[36mChecking md5sums - wait a while...
[: 41: 2fc88f67f4d67999fee2a929c4bd3f0f: unexpected operator
-e checking md5sum for ../boot/vmlinuz \e[31mfail!
[: 41: eef4c7d9e410d4099171ac083eda0cef: unexpected operator
-e checking md5sum for ../boot/initrd.xz \e[31mfail!
[: 41: bb530ef1b0d9f714ba3ba707525690d1: unexpected operator
-e checking md5sum for ./base/000-kernel.xzm \e[31mfail!
[: 41: daf2b3afdb61e305b1fd3f62a2682e13: unexpected operator
-e checking md5sum for ./base/001-core.xzm \e[31mfail!
[: 41: bd15c3b7aebb3f1e5a490d49296d312b: unexpected operator
-e checking md5sum for ./base/002-xorg.xzm \e[31mfail!
[: 41: 494ac56997d995eb0be1af3bb4bee858: unexpected operator
-e checking md5sum for ./base/003-lxde.xzm \e[31mfail!
[: 41: be6268a95287a4e9aa0b62eceec22289: unexpected operator
-e checking md5sum for ./base/004-kde.xzm \e[31mfail!
[: 41: c47dcad4fdc2df7c9ba16d6acd51ebd0: unexpected operator
-e checking md5sum for ./base/005-kdeapps.xzm \e[31mfail!
[: 41: 8950543bff042c6d4cc48b1ea80bb1e4: unexpected operator
-e checking md5sum for ./base/006-koffice.xzm \e[31mfail!
[: 41: 56f555d51b13ea46877745bd07297261: unexpected operator
-e checking md5sum for ./base/007-devel.xzm \e[31mfail!
[: 41: 52e4f1541450eaf9312a43345110b628: unexpected operator
-e checking md5sum for ./base/008-firefox.xzm \e[31mfail!
-e \e[31mSome md5sums doesn't match or some files from default ISO are missing,
please check above...
-e \e[31mBe aware that vmlinuz, initrd.xz, 000-kernel.xzm and 001-core.xzm
are most important and booting wont be possible when they are missing.
-e \e[36mPress enter to continue or ctrl+c to exit
read: 54: arg count
I use Debian 5 64-Bit.
What can I do?
H3llGhost
-
Hamza
- Warlord

- Posts: 1908
- Joined: 28 Dec 2010, 07:41
- Distribution: Porteus
- Location: France
Post#2
by Hamza » 25 Aug 2011, 12:18
Hello,
This issue is due to color customization.
When the devs written this script, they have customized it to display some texts in color. And with your current log, it appear that does not works with yout current system (Debian).
It appear, there is an syntax error with "base module checking" part of the chkbase.sh script
You need to wait the devs answer.
The main developer of this script (chkbase.sh) is fanthom
Thank you for this bug report.
Regards,
NjVFQzY2Rg==
Hamza
-
H3llGhost
- White ninja

- Posts: 14
- Joined: 22 Aug 2011, 11:46
- Location: localhost
Post#3
by H3llGhost » 25 Aug 2011, 12:53
Thanks for the advice with the chkbase.sh script.
The script runs without any problems, when you call it directly, so I commented out the line, where it is called.
There are only problems executing it out of the bootextlinux.sh.
@fanthom:
Why do you use
instead of
to end the colored line?
Perhaps it would be nice to check the file permissions. I don't know the reasons but
lilo and
extlinux wasn't executable.
H3llGhost
-
Ahau
- King of Docs

- Posts: 1331
- Joined: 28 Dec 2010, 15:18
- Distribution: LXDE & Xfce 32/64-bit
- Location: USA
Post#4
by Ahau » 25 Aug 2011, 15:22
I've moved this thread to "General Chat" -- it's not a bug within Porteus, it's apparently a lack of feature support in Debian's version of the echo utility, as Hamza noted. I've heard of this before, and should have put up a thread about it.
There's a little bit about it at the end of this thread:
http://porteus.org/forum/viewtopic.php?f=48&t=654
Basically, since we can't guarantee compatibility with all versions of all distro's, the user's best bet (if the install fails from their native distro) is to burn Porteus to a CD, boot from that, and then run lin_start_here.sh from that CD.
Thank you very much for putting up this thread!
I'll be curious to hear fanthom's response regarding the scripting -- if you modify the script on your end to use 'e='\e[m', does it both display color and work from within Debian?
Please take a look at our online documentation, here. Suggestions are welcome!
Ahau
-
fanthom
- Moderator Team

- Posts: 5588
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
-
Contact:
Post#5
by fanthom » 25 Aug 2011, 16:43
@H3llGhost
as mentioned by guys above - Debian's version of 'echo' utility does not support '-e' switch. please try this script under Debian and report if that works:
Code: Select all
#!/bin/sh
echo "[1;32m""Debian test""[0m"
if yes then i'll tweak installation scripts to fix this issue. hopefully this gonna work for all non-debian distros as well.
Second thing: non executable files on FAT/NTFS. this is again Debian's problem (feature) as all files on Windows fs are mounted without executable bit. this bug is covered by our installation guide: /boot/docs/install.txt:
Code: Select all
*NOTE* Some modern linux distributions, such as Ubuntu, Fedora,
Mandriva, etc, use 'udisk' to automount usb drives from within
KDE/Gnome/LXDE, etc. In versions higher than 1.0.2, udisk will not
automount these drives with executable permissions (attempting to run
the script will result in an error stating that permissions have been
denied), and you must mount your device manually as root in order to
execute the script. For example:
mkdir /tmp/media
mount /dev/sdXY /tmp/media
/tmp/media/boot/lin_start_here.sh
(where sdXY is the device and partition to which you are installing
Porteus)
This script will bring up a menu.
please read this doc as it was created for a reason.
Cheers
Moved to "Installation methods" as this tread contains some info which may be helpful for others (i'm aware that nobody want's to read the docs)
Please add [Solved] to your thread title if the solution was found.
fanthom
-
H3llGhost
- White ninja

- Posts: 14
- Joined: 22 Aug 2011, 11:46
- Location: localhost
Post#6
by H3llGhost » 25 Aug 2011, 17:48
First:
echo -e works fine with Debian. I have executed
chkbase.sh script and all is colored.
I can't copy your posted code, there are some characters which aren't copy.
Second:
I have used the mentioned commands to mount it, but it doesn't works for me.

Furthermore I should say, that I used the generated iso and tried to mount it.

I know the function of a manual/guide.

H3llGhost
-
fanthom
- Moderator Team

- Posts: 5588
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
-
Contact:
Post#7
by fanthom » 27 Aug 2011, 18:32
I can't copy your posted code, there are some characters which aren't copy.
you could use kwrite or leafpad for example
Second:
I have used the mentioned commands to mount it, but it doesn't works for me.
worked for me on latest debian's livecd with lxde on board
i have tweaked installation scripts once again (Debian is very strict about bash syntax, also some features are not avail like 'read -n1 answer'). once scripts were working ok i have got this:
Code: Select all
Flushing filesystem buffers, this may take a while...
Setting up MBR on /dev/sda...
boot/syslinux/lilo: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory
the only fix for this would be to provide statically compiled tools: lilo/extlinux/syslinux in /boot/syslinux folder which is not easy:
http://porteus.org/forum/viewtopic.php?f=63&t=508
as for now (in case of similar troubles) i would recommend burning porteus to CD and then performing installation on usb/hd from Porteus and not other distros. Porteus delivers all libs and tools needed for installation while other distros may be lacking of something.
Cheers
Please add [Solved] to your thread title if the solution was found.
fanthom