Porteus

The funny thing is that I have to write your url twice every time i come here, because my brain is still putting that "o" in the name every time :-D

Hi guys, after a long time i come back to this forum just to say that a new version of PixieLive was released (i hope this is not against the rules...) I post here since we worked together for some time when Porteous was born and you could find interesting features to copy from PixieLive to Porteous...

This project: http://www.osst.co.uk asked me to be allowed to host the PixieLive torrent on their server.

I suppose they would be happy to host also Porteus (if an official torrent is already present, they will use it, just seeding, otherwise they have their own tracker)

than you for the prompt reply, i will take a look into the script did you notice they released a new version called httpfs2 some months ago, may be they also improved compatibility with web servers, gotta take a look into the source soon... http://sourceforge.net/projects/httpfs/files/httpfs2 Posted...

for module activation and similar you can write a script using sudo and configure /etc/sudoers to not ask password at all this is a smaller security issue than run everything as root...

hiya developers, a new patch for linuxrc (it's made for lls, but you can port it easily to your porteus linuxrc if you wish) this patch allow you to boot from a device specified by the uuid with the cheatcode uuid=***** i assume your blkid give you an output like: /dev/sdxY: UUID="*******" TYPE="***...

hiya, how can boot from IP (IP cheatcode) be done?

is there something special needed or just a porteus folder and an http server?

thank you

fanthom wrote:are you sure that your output comes from blkid which is built into busybox and not /mnt/live/bin/blkid binary?
show me the output of:
"/mnt/live/bin/busybox blkid"

ehm... i didn't compile blkid into the busybox... it's from /mnt/live/bin/blkid

i'm getting pixielive@pixielive ~ $ cat /mnt/live/var/log/blkid.log /dev/loop0: TYPE="squashfs" /dev/loop1: TYPE="squashfs" /dev/sda1: UUID="EE64B80564B7CF19" TYPE="ntfs" /dev/sda3: LABEL="PE" UUID="CCED-990E" TYPE="vfat" /dev/sda5: UUID="7f3ecb12-74a1-44ae-9759-5c2f6953f518" TYPE="ext4" /dev/sda6: ...

are those config lines in the new busybox-1.18.1: # # Filesystem/Volume identification # CONFIG_FEATURE_VOLUMEID_EXT=y # CONFIG_FEATURE_VOLUMEID_BTRFS is not set CONFIG_FEATURE_VOLUMEID_REISERFS=y CONFIG_FEATURE_VOLUMEID_FAT=y CONFIG_FEATURE_VOLUMEID_HFS=y CONFIG_FEATURE_VOLUMEID_JFS=y CONFIG_FEATUR...

Did a bit of googling last night (morning/afternoon for the rest of you) while waiting for the poll (yeah still sulking losing by a nose :cry: ) found a site mentioning virtual CD, apparently with one of those usb thingy bob including 32MB storage so there is a chance of ruling the world after all ...

Yesterday i made some tests with my SandDisk Cruzer 16GB USB pendrive, this is what i discovered (i know, most of you already know that, but for the others that could be interesting): U3 pendrives are made by a CD-like read-only partition + a mass storage device (USB pendrive) They appear as 2 diffe...

Yesterday i made some tests with my SandDisk Cruzer 16GB USB pendrive, this is what i discovered (i know, most of you already know that, but for the others that could be interesting): U3 pendrives are made by a CD-like read-only partition + a mass storage device (USB pendrive) They appear as 2 diffe...

yes, definitely it should be something similar to U3.
But in my case U3 tools won't recognize any device...

anyway, an U3 device with liveOS on the CD part, and data on the other would be interesting, and with the right tools and an U3 pendrive, it doesn't seems to difficult to obtain

damn, you are right, it works... but with the patch you don't have to predict the name of the device where the iso is located, which may be a problem for unexperienced users