Porteus

hi fanthom apologize me if i post in wrong section but,i have a trouble with initrd 64bit version at boot loading modules ok but cp write error no space left in device,couldn't copy sbin/init file,you need at least 600kb free space inside initrd,i have build a bigger initrd ,but should be a script failure,tanks

especially for you
http://forum.porteus.org/viewtopic.php? ... 3504e#p569

dont forget to add [Solved]

hi fanthom thanks so much,i will report news.

Posted after 13 minutes 6 seconds:
hemm...what is the mean of launch me with full patch to initrd.lz

fixed typo and added an example
try again...

i am in the foggy

Posted after 28 minutes 28 seconds:
ok ,i have solved,

Well well well...

It seems that my system has no space and wont boot up the gui, this happened after I was downloading software at which time it froze and gave me a dialogue there was no space left on the system.

what should i do, can I just get into it somehow and delete the files it had partially downloaded?

thanks

run in 'Always Fresh' then remove unwanted files from your changes (mount save.dat with 'mloop' if necessary).

Holy moly, I fixed it!!!!

heres how...

I tried the 'always fresh' mode and yes that logged me in I deleted all the usm modules i had downloaded but it didnt fix the issue when i booted to the gui mode again. I didnt do the mount .dat file using mloop because i forgot about that tip, also I have never used that command anyway.

What I did was move the porteussave.dat to a different location so it wouldnt be accessed when booting the gui mode, I did this in always fresh mode. This booted me into gui mode when I restarted, but without the changes that I had made so in effect it was like an always fresh boot but I was also in the same account I was having trouble with.

Then I went to the porteus save file manager and resized the porteussave.dat file and then copied it back to the original location that was referenced in the porteus.cfg file. I then restarted and success! the original system with all the customizing I have done so far loaded as normal.

I was very happy and pleased I had successfully solved the issue.

Thanks for your help and I hope this helps others who may find the same issue.

I think its important to mention that i had heaps of room on my usb drive its a 16 gb one. This wouldnt work if you had limited space unless you could use some separate storage you could move the .dat file/s to and make the changes within that. If you had already maxed out the size of your .dat file on the bootable USB drive using the mount .dat approach with the mloop command as fanthom suggested might work unless you could copy your complete bootable usb drive contents to another larger usb drive but I think you would need to make it bootable somehow maybe using gparted?

i'm glad that you have resolved this.

I think you would need to make it bootable somehow maybe using gparted?
just run the installer again