Slacko 5.7 - March 2014
Thanks Mavrothal, for your attention to this problem.
I did a frugal/pupmode 13 installation of Slacko 5.7.0 to a USB stick (the full install described earlier was to HHD).
I then used SFS Manager to download and install kernel_sources-3.10.32-slacko_PAE.sfs, checking the same numbers as before: in the process, /usr/src grew from 57k (pre-install) to 482 M (post-install), in the ball park with what you described, so the problem would seem to be limited to full install/pupmode 2.
Although the modules I compiled appear to be working properly, perhaps it would be prudent to avoid using SFS Manager with a full install.
I did a frugal/pupmode 13 installation of Slacko 5.7.0 to a USB stick (the full install described earlier was to HHD).
I then used SFS Manager to download and install kernel_sources-3.10.32-slacko_PAE.sfs, checking the same numbers as before: in the process, /usr/src grew from 57k (pre-install) to 482 M (post-install), in the ball park with what you described, so the problem would seem to be limited to full install/pupmode 2.
Although the modules I compiled appear to be working properly, perhaps it would be prudent to avoid using SFS Manager with a full install.
-
- Posts: 17
- Joined: Thu 27 Mar 2014, 20:41
Hi. How can I set the time-view in the 24 hours format on the bottom/right of the desktop ? (19:35 and NOT 7:35 pm). Thankyou
--------------
I'm sorry!
I didn't search very well. I've found the answer here:
"Posted: Tue 15 Apr 2014, 13:45
SFR wrote:
Try Menu -> Desktop -> JWM Window Manager Settings -> Clock
Yes, it solved both problems completely:
Thank you very much."
--------------
I'm sorry!
I didn't search very well. I've found the answer here:
"Posted: Tue 15 Apr 2014, 13:45
SFR wrote:
Try Menu -> Desktop -> JWM Window Manager Settings -> Clock
Yes, it solved both problems completely:
Thank you very much."
- ThoriumBlvd
- Posts: 159
- Joined: Fri 04 Oct 2013, 09:04
- Location: N.E. USA
Any non-office version availible with FreeOffice link to register?
I did the following...
DL the iso then Burnt to CD (161Mb)
Register and DL FO-690.tgz
Used ISO Master to add the tgz to the iso files (222Mb)
Burnt to CD ---> Slack57XLpuppy.iso
Both Slacko_5.7 and Slack57XL as spares when I have real time to investigate.
However I did ShutDown and Run the Slacko 5.7.
Opines/observations
FF17ESR a good choice, FF23 here is also OK (From Slacko 5.5XL)
NEEDS: AdBlock Edge, Redirect Cleaner, Better privacy pre-installed
OMG: Google as search engine, may I suggest DuckDuckGo.
mtpaint 3.44.48 OK
Good job on back-off on OverWrite my 5.5XL sfs. pfix --> RAM
The rest would be personal choices not improvements. So Great job, booted and ran w/o issue(s) on an EEE900a.
Cheers,
Thorium
I did the following...
DL the iso then Burnt to CD (161Mb)
Register and DL FO-690.tgz
Used ISO Master to add the tgz to the iso files (222Mb)
Burnt to CD ---> Slack57XLpuppy.iso
Both Slacko_5.7 and Slack57XL as spares when I have real time to investigate.
However I did ShutDown and Run the Slacko 5.7.
Opines/observations
FF17ESR a good choice, FF23 here is also OK (From Slacko 5.5XL)
NEEDS: AdBlock Edge, Redirect Cleaner, Better privacy pre-installed
OMG: Google as search engine, may I suggest DuckDuckGo.
mtpaint 3.44.48 OK
Good job on back-off on OverWrite my 5.5XL sfs. pfix --> RAM
The rest would be personal choices not improvements. So Great job, booted and ran w/o issue(s) on an EEE900a.
Cheers,
Thorium
[img]http://www.am3radio.us/image3.jpg[/img] . [img]http://www.am3radio.us/image4.jpg[/img]
-
- Posts: 17
- Joined: Thu 27 Mar 2014, 20:41
Hi.
I used USB slacko 5.6 till a week ago. Everything worked with ‘autorun Time Sync’ (I want a time synchronization at each boot).
I connect to web by Ethernet cable (eth0). Wireless is not configurated.
Now I installed USB Slacko 5.7 and I have problems with Time Sync at each boot.
I set autorun in Psync (and correctly “timesync.sh
I used USB slacko 5.6 till a week ago. Everything worked with ‘autorun Time Sync’ (I want a time synchronization at each boot).
I connect to web by Ethernet cable (eth0). Wireless is not configurated.
Now I installed USB Slacko 5.7 and I have problems with Time Sync at each boot.
I set autorun in Psync (and correctly “timesync.sh
-
- Posts: 17
- Joined: Thu 27 Mar 2014, 20:41
Hi . I’ve found a workaround to fix the problem, depending by the fact that I didn’t define a wireless profile.neversaynever wrote:Hi.
I used USB slacko 5.6 till a week ago. Everything worked with ‘autorun Time Sync’ (I want a time synchronization at each boot).
I connect to web by Ethernet cable (eth0). Wireless is not configurated.
Now I installed USB Slacko 5.7 and I have problems with Time Sync at each boot.
...
It consists in modifying “timesync.sh
Has anyone had success in running Sweet Home 3D 4.4 in Slacko 5.7?
It loads ok but the walls keep disappearing after they are drawn.
http://www.sweethome3d.com/
TIA
It loads ok but the walls keep disappearing after they are drawn.
http://www.sweethome3d.com/
TIA
It worked fine in 5.7 when I increased the savefile yesterday by 512k.stemsee wrote:Using studio1337 V2 (slacko 5.7 based) I can't successfully resize savefile. i don't know if anyone else has reported this bug! I will take a look at the script and see if I can pin point the error ... sometime ... before I leave this world ... hopefully
Stemsee you are quite right it was 512M not 512k and I never changed the resize script.stemsee wrote:"512k" - I never noticed a 512 kilobyte enlargement option when resizing a savefile! I was sure 32MB was the minimum resize function - but hey I am a noob not a veteran - You surely have your reasons for such customisations!
Maybe you could share your resize script so I too can make 512kb resizes!
Cheers
I have the same resizie failure, tried on usb, sata, ssd drives, and usbstick,stemsee wrote:Using studio1337 V2 (slacko 5.7 based) I can't successfully resize savefile. i don't know if anyone else has reported this bug! I will take a look at the script and see if I can pin point the error ... sometime ... before I leave this world ... hopefully
tried with various sizes. The process seems to be skipped/ignored.
It's very important to have control over sizing the room to work!
Cheers
I can't find a problem in resizpfile.sh in standard slacko-5.7.
You should end up with a file in the home partition with these contents.
If that isn't there with sane values then something has gone wrong in studio 1337 with either /etc/DISTRO_SPECS or /etc/rc.d/PUPSTATE.
This little venture did expose a bug @line 52. The calculation is way off.
A suggestion to replace that line is:..although stat -c %s works just as well.
You should end up with a file in the home partition with these contents.
Code: Select all
KILOBIG=131072
PUPSAVEFILEX=/0test/slackosave-mar15.4fs
This little venture did expose a bug @line 52. The calculation is way off.
A suggestion to replace that line is:
Code: Select all
ACTUALSIZK=`ls -l --block-size=K $HOMELOCATION|awk '{print $5}'|tr -d 'K'`
Puppy Linux Blog - contact me for access
Don't use save files, store data outside the Puppy file system and use symbolic links to these stored directories and/or files.It's very important to have control over sizing the room to work!
Will increase your room to work extensively.
[b][url=http://lazy-puppy.weebly.com]LazY Puppy[/url][/b]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
Make a smallish save, reboot then run the resize. Post the contents of pupsaveresizenew.txt in the root of the home partition, if it gets created.
EDIT: did you base this on slacko-5.5? (as seen in the DISTRO_SPECS). If so you will need to hack the init script for support of the new way we are increasing savefile space. It addresses an old bug where the next puppy booted got the treatment, bad if you run multiple pups.
EDIT: did you base this on slacko-5.5? (as seen in the DISTRO_SPECS). If so you will need to hack the init script for support of the new way we are increasing savefile space. It addresses an old bug where the next puppy booted got the treatment, bad if you run multiple pups.
Puppy Linux Blog - contact me for access
I never thought of that! Another save to directory option via savefile symlinks - opens a whole new world of possibilities! Only downside is the symlinked dirs cannot get copied to ram!RSH wrote:Don't use save files, store data outside the Puppy file system and use symbolic links to these stored directories and/or files.
Will increase your room to work extensively.
Should be another thread!