I like to have black background as it offers the easiest to view contrast, and the first one could be edited so the cat is on the bottom right hand corner and the carpet underneath the cat could be edited out. This cat as a small logo on the bottom right hand corner with the Pussy linux version information under it is what im thinking. I think its best to keep the background artwork away from the icons that are at the top left hand corner, and something in the middle could clash with the icons, this is why i prefer to have the artwork on the bottom right hand corner.

The seccond one altho goes against what i just said might work.....

The 3rd one is perfect just how it is.

what does everyone else think?

i think something needs to be done about the background, in its present state its so bad quality that we are probably better off just having it black.

While we are on the subject of artwork, what is your opinions of the boot splash screen that is used in the live cdrom iso? i think is in /isolinux/splash.png . This was custom ordered for pussy, it started life as a modified debian live boot screen but was changed to make it more cartoonish and the cat outline has the different coloured eye the same as the puppy logo, i wanted to have a splash screen that incorporated parto of debian live, puppy and ofcause a pussy. I personally think this is fantastic and i love how the whiskers encircle the boot menu options.

SickGut here is a wild suggestion.
As you know I am a complete Noob and Challenged
using computers and logic but what if it works?

TinyCore did not allow us to use NTFS formatted either.
Then suddenly RobertS change mind or something.
So here is how them did it for a while. I try to show
Now this is many month old so them do it other ways now I guess.

pylaivng is a set of tools to help the development of Debian-based distributions.

It is currently the official build system of Semplice Linux.

So most likely one can make any kind of Debian using it?
I guess it needs Python language compiler? but I am just guessing._________________I use Google Search on Puppy Forum
not an ideal solution though

pylaivng is a set of tools to help the development of Debian-based distributions.

It is currently the official build system of Semplice Linux.

So most likely one can make any kind of Debian using it?
I guess it needs Python language compiler? but I am just guessing.

im only going to stick with the least modified debian=live and never break compatibility with it, i will slim the whole thing down by removing files that dont need to be there (pussy would be 1.7gb in size, not 244mb if i didnt slim it down) however this doesnt break compatibility with anything. Soon as i start doing non standard stuff is when we loose support from the debian-live community. However there is way way way more potential and way more options that are standard with debian live that i have not learned about yet, when i do learn this, we will find pussy can do anything we want.

pussy will always live in the realms of what is possible with a standard debian live system, as soon as we break this... we have created something completely new and it is up to us to completely support it, and im sorry to say im not willing to do that as i dont completely understand the normal debian live yet and creating something else is out of the question as i will not be able to support it and not be able to provide our users with the support they need. If we keep it standard, our users can still get support from debian and debian live communities, and these communities can offer more knowledgeable support than i can.

i wont ever take the plunge to create something other than a standard debian live system until i have learned 100% there is to know about this one, then if we do change i will know what the changes will mean and what they do and be able to support it..

also i will never do anything that would break compatibility with the debian repos in any way.

While we are on the subject of artwork, what is your opinions of the boot splash screen that is used in the live cdrom iso?

I like it. I think you should not change it.
The third cat wallpaper is fine for me too.

cool, glad you like the boot screen. I am currently in the stages of designing the new pussyxtra.squashfs that contains the extra apps, i think i will use the cats eye wall paper in it and see what everyone thinks about it.

may I ask. which other debian i there out there?
Is crunchbang maybe pure debian? Do them tell such on DW?
Maybe Mephis? AntiX maybe is too changed to be seen as pure?
Seems only ubuntu like distros work for me here

the following iso works for me doing iso NTFS booting with permission to write to the hdd I booted from.
LMDE-11 linuxmint-11-gnome-dvd-32bit.iso
Peppermint-Two.iso
Elementary OS elementaryos0.1-jupiter-i386.iso
Bodhi Linux boots from bodhi_1.2.1.iso

While your Pussy, AntiX, Swift, Semplice_2.0 Crunchbang Staedtler
and some more fails to give me permissions. And that seems to be
a Debian policy that every version hold on to while Ubuntu has allowed
it in latest versions._________________I use Google Search on Puppy Forum
not an ideal solution though

I think pussy linux have a future even if the boot NTFS partition writing problem continue to exist.
Sickgut made it for Live CD use with save file anyway. Frugal install is a big bonus, because it has a RW access to all other boot partitions. Only NTFS has a problem.
There is a simple solution of that. Just have to make a small vfat or ext partition on the HDD to boot from it.

am reading and writing persistently to folder /liverw on the same sdcard while pussy is running.
modifications into the /live folder itself eg /ect/wvdial.conf are not holding through reboot. have to experiment more.

Its not because of a secret betrayal that once Pussy moves away from the 100% debain-live that pussy users wouldnt be able to get the same support from the debian-live community, if there are core things changed in the OS then what works on normal debian-live wont always work on Pussy, so the advice will not always be correct and Pussy users might send info to do with configs or files and the debian-live experts would see it and realize that there are fundamental differences and this means they would simply say "we cant support this type of change, we only support debian-live, what you have here is something different, you should contact the people who made the changes for support...."

but normal debian obviously allows writing to the ntfs drive it booted from... the problem is that being a debian-live system, not a debian normal... the boot partition is always treated as live-media (ie. a cdrom drive) and writing to it isnt really a high priority. When you use a cdrom or usb stick for the live system its expected that none of these will be NTFS, the usb is always meant to be a FAT32 and the CDROM is unwritable anyway........

the debian-live isnt designed to be copied to a HDD and then booted with grub, so there will be problems. When you have a ntfs partition on your computer, pussy will now write to the save file if its on this partition if you use a cdrom or usb to boot from, once the ntfs parition is also the live-media, its treated like a cdrom or an iso... both are unwritable...

its always been my goal to make pussy a live distro for usb sticks, then i discovered i could remaster it to cdrom, then you guys came up with HDD install..... and thats cool.

we could solve the HDD ntfs issue immediately by going with normal debian not debian li ve..... but we would loose easy usb and cdrom live support and i see that as more important than HDD support.

oh well i havent exausted all my options for making pussy write to ntfs boot partition yet... even if i dont find a way to fix this, the debian-live team have realized alot of people are using hdd install and they will fix the NTFS thing on their end. Debian is slow to introduce new features, its rigorous testing of all new additions before they are released means its very stable.... it may seem we have to always wait forever for new features but if we compare our stability and speed to the next logical choice for something more bleeding edge... Ubuntu... its easy to see we are working with the right base, as Ubuntu is slower, bigger and not as stable and doesnt work with older hardware as well.

whatever happends now with solutions for the ntfs boot partition writing problem... it will get fixed, either we will sort it out ourselves or the debian team will include a fix in the next release. Either way its just patience, it will get fixed either way with the worst case being that its fixed in a few months.

am reading and writing persistently to folder /liverw on the same sdcard while pussy is running.
modifications into the /live folder itself eg /ect/wvdial.conf are not holding through reboot. have to experiment more.

also posting this from pussy using my /sdb3 located portable opera-next.
effectively nearly a complete ordinary puppy.

glad its all working for you with your other puppies on the sdcard and you have write access. If you are using a /live-rw folder.... this is not the same as the live-rw save file or live-rw partition, in such a case... /etc/ folder will accept changes while pussy is running but they will return to normal and be lost on reboot, however ... writing to the /live/image/ or /live/image/live folder will be persistent through reboot, and if you mount the sdcard: mount /dev/sdb3 /mountpoint and write it will also persist through reboot.

the "drive" icon on the desktop also is a direct link to /live/image/ and clicking on "drive" and saving in the folder it opens will be persistent through reboot with or without a save file.

if you wish to have the standard savefile or save partition setup that is updated in realtime and is noncompressed (recommended) then you use gparted in pussy to changed a partition label to: live-rw and next time pussy boots it will write to this partition and all your changes will be kept. The live-rw savefile way is to extract the example save file from the website onto any of your drives and the next time you boot pussy it will write to this file. You can create the live-rw file manually with:

dd if=/dev/null of=live-rw bs=1M seek=2000
mkfs.ext2 -F "live-rw"

this makes a 2gb save file, the seek= value is the size of the save file in MB. Make sure to cd to the drive / partition you wanna have the save file on before you enter the commands in the terminal.

Note: to use the normal live-rw save method, you need a live-rw save file or live-rw partition only.... NOT a live-rw folder. Pussy will not automatically detect a /live-rw folder and save your changes in it

/live/image/ <----- live media is located here, non writable if its a cdrom, but usb or sdcard installs should be writable even without a save file.

/live/cow <------ if you have no save file, your changes are saved in ram, and the changes are saved in this folder. Also if you have a save file the changes are saved here too but they are also saved in the save file, this is because /live/cow is a mountpoint for the save file. COW stands for copy on write, ie its the complete set of changes to the normal pussy since it was booted.

In the catroll-panel ---> save file ----> update save file... if you are using usb or non ntfs hdd to boot from then using this save method copies everything in /live/cow to a new squashfs file and saves it in /live/image/ may take a while to create the new squashfs if there are alot of changes. This is the compressed save file method and doesnt require the normal live-rw save file setup, but if you use this compressed save file method, chages are saved ONLY when you click update save file. This compressed way doesnt work on cdrom booted systems because it writes to the live media itself and cdroms arent writable directly. This way is also cool because it requires no setup process, on first boot you click update save file and boom, its done.

you can run this yourself from a terminal instead of clicking the icon in the catroll-panel and you can see it working. The save file becomes part of the live system just like the pussy-os.squashfs and this is a quick way of remastering pussy, you can rename the savefile to something else and upload it to the internet and people can download it and put it in their /live/image folder and they are now running any modifications you made
this is how i have been making the additional squashfs files like the pussyxtra.squashfs that contains the extra apps that im working on.

@sickgut sorry to make you repeat all that save stuff again. read the release notes for alpha pussy before you posted and the save info is mostly in there. i had forgotten it has been so long since i read it. but some useful new tips about squashfs in your latest post. thanks.
note i couldn't non-grub boot the latest iso when extracted and copied to usb flashdrive without first copying/adding the different boot things (isoliux folder and ldlinux.sys) from the alpha._________________
ASUS EeePC Flare series 1025C 4x Intel Atom N2800 @ 1.86GHz RAM 2063MB 800x600p ATA 320G
_-¤-_<º))))><.¸¸.•´¯`•.#.•´¯`•.¸¸. ><((((º>

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum