Porteus

Hi again, sorry for being absent the last day or so. -Crash does not happen when not booting without changes= (It boots normally without changes= cheatcode, always fresh boots correctly 100% of the time) -I just tried it without the ati-fglrx module and the crash also did not happen (but it took ove...

Okay, removing xconf from startup cheat codes did let it boot into KDE4, but plasma desktop immediately crashed when doing so (not to mention it took a good 10 minutes for it to start up). if xconf is a cheatcode, KDE4 still crashes and starting it from tty1 immediately resolves the problem and KDE ...

I tried all of that and the .dat files (except the 1.2 GiB one I made) don't appear to be the problem. Actually the problem appears to be happening in the step where it makes a xorg.conf for ATI drivers (where it runs xconf). I tried running it outside of X and it seemed to function just fine. Then ...

Hi, I'm having a problem where using a save.dat file results in not being able to start KDE4 during boot. KDE4 can be started subsequently by changing to another tty session, logging in as guest, and then using startx from there. Then it works just fine. Size of save.dat file was 1.2GiB, I was havin...

Finally got around to trying it out. (I know, a bit late, it's almost out of beta)

Spectacular job Fanthom and co. Thank you all for the great OS.

Thanks brokenman! Usually I've been extracting base modules or regular modules to some arbitrary directory (let's say, ./tempdirectory) and using the ROOT=./tempdirectory/ upgradepkg <package name> command, then using dir2l/xzm to get a nice functioning module again. I think I'll be using your scrip...

I ran into an interesting problem earlier when I went to look at a website that used Japanese and Korean characters. In particular I got a collection of boxes that meant nothing to me or Google translate. It needs to be known that Porteus does not come standard with East Asian language support or fo...

fanthom: The package that first didn't convert properly was the rtorrent package located on the debian lenny repository. It's this one to be exact: http://packages.debian.org/lenny/rtorrent There are too many missing dependencies to make installing it file by file to be worth the effort, however. I ...

Posting because I had the same problem (using the deb2lzm cli utility produced an error, telling me dpkg was not found and does not exist, using the Dolphin utility produced no package) I solved that by getting the dpkg slackbuild, building a slackware package, and converting that to LZM. This is pr...

One more possible problem to report (though unrelated). Adding modules no longer seems to move the module to the modules folder (as in it is forgotten and not loaded at startup). Is anyone else getting this problem or is it just me? Posted after 4 hours 24 minutes 33 seconds: Re: Problem with normal...

Okay I've been doing some testing, and I seem to have found the problem. First off, fanthom was correct. The way of adding users by copying over the root directory to the user's new home directory seems to be the only way to add a user. Before (as in slax-remix) I would use the adduser command and f...

Sorry for taking so long to report back, I'm not quite in the same timezone. I've made the recommended changes to rc.S. As well as to the user in question (added to group netdev). Unfortunately, wicd continues to hang and KDE continues to crash for the new user. Nothing has changed since last report...

USB: 2.0
Size: 8.0 GB
Partition: W95 FAT32
It's essentially this drive:
http://www.newegg.com/Product/Product.a ... 6820220263

It worked just fine for every slax and slax remix version before this. However, before this I used primarily x86 versions.

Hi, I almost reported a problem earlier that I'm not sure is a cause or a symptom of the problem I'm having now When using the changes files slaxsave.dat. I'm having the issue of having KDE4 crash when attempting to boot into X as a normal user of my creation. It seems to work just fine for root, I ...

Uh oh, I just finished downloading the latest x86_64 image.

Will the fix come in the form of a patch or a new image? (I'm okay with either, I'd just like to know in advance)