Pussy: potentially a Puppy with a perfect package manager

[john3voltas]

sickgut:
This thread has grow big!
Can't read it all.
Yesterday I think I caught you mentioning something about an issue when trying to mount the partition where Pussy boots from.
I'm not sure if you've noticed it already but /live/image is mounted RW and it is the partition where you boot from with Pussy.
Or have I misinterpreted you?
Cheers

EDIT: I'm running the beta-preview2 and I must let you know that I'm still having keyboard issues. Starting to think if this isn't an issue with debian itself...

[nooby]

sickgut:
This thread has grow big!
Can't read it all.
Yesterday I think I caught you mentioning something about an issue when trying to mount the partition where Pussy boots from.
I'm not sure if you've noticed it already but /live/image is mounted RW and it is the partition where you boot from with Pussy.
Or have I misinterpreted you?
Cheers

EDIT: I'm running the beta-preview2 and I must let you know that I'm still having keyboard issues. Starting to think if this isn't an issue with debian itself...

Maybe you mean when he told me about his IRC chat with Debian Developers and them told him them are working on it.

There is a huge differences between Ubuntu and Debian.

Ubuntu already works. I can save changes and edit and delete
any kind of file AFAIK but even this latest version of Pussy
does not even allow me to edit the menu.lst that I used to boot it on.

So it is not Sickgut's error it is the Debian people that set it up that way.
Way back in time Unix people decided on policies and Debian hold on to them.

I trust Ubuntu does too but that them made some human error and
that the current "permission" I have is some kind of bug.

[saintless]

john3voltas, what are the keyboard issues? Check if the information below solve them. Sickgut will add a fix for this in the next iso.

If someone wants to add different keyboard-layout before the official beta version is ready, here are the commands:

This one will install other keyboard layouts:

Code: Select all

apt-get install keyboards-rg

After that type:

Code: Select all

dpkg-reconfigure keyboard-configuration

Follow the instructions and choose your layout. BTW you can choose also to exit X with Ctrl+Alt+BackSpace.

We steel have a problem with RW on NTFS Boot partition only. All other vfat and ext boot partitions have RW access. If NTFS partition is not the one pussy boots from, it has RW access as well. Only NTFS Boot Partition is waiting to be fixed for debian (not only for pussy linux).

[sickgut]

sickgut:
This thread has grow big!
Can't read it all.
Yesterday I think I caught you mentioning something about an issue when trying to mount the partition where Pussy boots from.
I'm not sure if you've noticed it already but /live/image is mounted RW and it is the partition where you boot from with Pussy.
Or have I misinterpreted you?
Cheers

EDIT: I'm running the beta-preview2 and I must let you know that I'm still having keyboard issues. Starting to think if this isn't an issue with debian itself...

the writing to boot partition is only and issue with ntfs filesystems as the kernel read only driver mounts it before ntfs-3g can.

[nooby]

Yes that seems to be the best explanation for it.
Suprising things is that Ubuntu obviously has changed how
them set up things then because there it works?

[john3voltas]

Suprising things is that Ubuntu obviously has changed how them set up things then because there it works?

Well, buntoo has an history of doing things the way they want without letting anyone else on it, don't they?
A budd of mine is a developer and sometimes he does minor fixes in their code.
Not long ago he told me that the release logs don't show even 10% of all the changes made into the code.
It's a bloody mess.
Even so, they usually do a hell of a job fixing the mess before it hits the streets...
Anyway, I can't write in the partition where grub4dos is installed but I can write in the partition where I have Pussy's vmlinuz+initrd.img+allsquashfs.
Maybe my difference is that I have grub4dos installed in a separate partition that win7 creates with just a 100MB. That's where win7 puts it's bootloader and that's where I have put grub4dos too.
Regarding my keyboard issue, it's not a Debian issue because I've just tested on my Debian Frugal and it worked properly.
Took a setxkbmap -print on Debian and it shows:

Code: Select all

user@debian:~$ setxkbmap -print
xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+pt+inet(evdev)+level3(ralt_switch)+terminate(ctrl_alt_bksp)"	};
	xkb_geometry  { include "pc(pc105)"	};
};
user@debian:~$ 

Whereas a setxkbmap -print on puppy shows:

Code: Select all

sh-4.1# setxkbmap -print
xkb_keymap {
	xkb_keycodes  { include "xfree86+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc/pc(pc102)+pc/pt"	};
	xkb_geometry  { include "pc(pc102)"	};
};
sh-4.1#

I wonder what I'll get in Pussy's setxkbmap -print.
Let me check that and I'll get back here to report it ASAP.
Cheers

[john3voltas]

Now that's odd.
Just tried to write something in my /live/image with no success.
I don't know if yesterday I was so sleepy that I screwed up and wrote in the wrong mounting point. OR, something is up today that is preventing me from writing to that mouting point.
All in all, I guess I screwed up yesterday and I was never able to write into my /live/image...

[nooby]

Thanks, I am so chicken. Now I have two of them.
Acer Netbook 10" Atom CPU N270 D250 and then Acer Netbook 10" Atom CPU Nxxx D255 I've have forgotten what it was N470 maybe.

Anyway the D255 is more noisy I don't really like it. I could maybe wipe it
of Ms WinXP and do a real full install of Grub2 and that way I would be
able to have Debian and Arch and a lot of what most Linux users have.

I mean my persistent usage of only doing frugal install on NTFS is
a bit fanatic. Even I realize that. Frugal Fundamentalism oops the other way aroung Fundamentalistic Frugalism. grammar is important
I am a Fundy Frugal Guy. Never boot anything without being frugal.

Anyway you could be right. My hdd have three NTFS partitions.

If I formatted one of them as ext2 and booted from that one using grub2 then I would be able to boot anything and write back most likely.

[sickgut]

Suprising things is that Ubuntu obviously has changed how them set up things then because there it works?

Well, buntoo has an history of doing things the way they want without letting anyone else on it, don't they?
A budd of mine is a developer and sometimes he does minor fixes in their code.
Not long ago he told me that the release logs don't show even 10% of all the changes made into the code.
It's a bloody mess.
Even so, they usually do a hell of a job fixing the mess before it hits the streets...
Anyway, I can't write in the partition where grub4dos is installed but I can write in the partition where I have Pussy's vmlinuz+initrd.img+allsquashfs.
Maybe my difference is that I have grub4dos installed in a separate partition that win7 creates with just a 100MB. That's where win7 puts it's bootloader and that's where I have put grub4dos too.
Regarding my keyboard issue, it's not a Debian issue because I've just tested on my Debian Frugal and it worked properly.
Took a setxkbmap -print on Debian and it shows:

Code: Select all

user@debian:~$ setxkbmap -print
xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+pt+inet(evdev)+level3(ralt_switch)+terminate(ctrl_alt_bksp)"	};
	xkb_geometry  { include "pc(pc105)"	};
};
user@debian:~$ 

Whereas a setxkbmap -print on puppy shows:

Code: Select all

sh-4.1# setxkbmap -print
xkb_keymap {
	xkb_keycodes  { include "xfree86+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc/pc(pc102)+pc/pt"	};
	xkb_geometry  { include "pc(pc102)"	};
};
sh-4.1#

I wonder what I'll get in Pussy's setxkbmap -print.
Let me check that and I'll get back here to report it ASAP.
Cheers

@john3voltas
its quite possible that there are differences in the debian that you usually use and pussy due to a missing package or some such in pussy.

This fix from saintless seems to work:

apt-get install keyboards-rg

dpkg-reconfigure keyboard-configuration

in the next round of releases, pussy will have an entry in the catroll-panel that installs the keyboards-rg package then reconfigures it so you can then select your keyboard.

in regards to the writing to boot partition, once booted, open /etc/mtab and see if /live/image is mounted rw. Mostly unless your running ntfs the writing to boot partition just works but i have experienced some times when it doesnt. I narrowed it down to how grub boots it. I noticed that if i specified stuff like root=/dev/sda4/ etc etc that it didnt work, but if i didnt specify those things then it did work. Seems the less info in grub the better. If grub2 is installed on the same partition as pussy is installed on, you dont need to specify the root fs in grub2, it picks it up automatically.

Everything will work simply with:

menuentry 'Pussy'
{
linux /live/vmlinuz boot=live config swapon noprompt quickreboot noautologin
initrd /live/initrd.img
}

Or if you do need to specify the partition pussy resides on (ie grub is not installed on same partition as pussy)...then do it via the uuid like:

menuentry 'Pussy'
{
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 81b13c28-bddb-4ede-9edb-aee4159a93ba
linux /live/vmlinuz root=UUID=81b13c28-bddb-4ede-9edb-aee4159a93ba rw boot=live config swapon noprompt quickreboot noautologin
initrd /live/initrd.img
}

To find the uuid of a drive, pussy has a tool for that in the catroll-panel ---> filesystem ---->disk-uuid or you can use the blkid command.

there is something mysterious and magical about writing to the boot partition (ie. the live media). Mostly it works but when it doesnt its a bit of a puzzle, but the simpler the grub config the better. When i had this problem, i removed everything that didnt need to be in grub and it worked, but i dont know exactly what stops it working.

[EDIT] After testing i can confirm that this type of tag: root=/dev/sda4 rw
stops you having rw access and that is with and without the rw bit at the end.
Also, simply just specifying: set root='(hd0,1)'
this stops you having rw access aswell. I think you need to have the insmod bits in there if you need to specify a partition other than the one grub is installed on.

[aarf]

got pussy-beta-preview-xtra2.iso down with some accidents along the way. how do these checkout?

Code: Select all

sh-4.1# md5sum *
ae55d14d796070455dd909a77f30ac7d  1-filesystem.squashfs
203bcfb74392d985fa904e8604960aa4  2-pussyOS-beta.squashfs
fca1c3de5822e2c9d9ed17239911ffff  3-seamonkey.squashfs
e60599a41f7d0afa5a94e0b246772e4b  4-pussyxtra-beta.squashfs
16a091d4e2aa347f3badef825adf3d32  initrd.img
82c5831721e6ff9d069887207976ba1e  vmlinuz
sh-4.1# 

only
2-pussyOS-beta.squashfs and 4-pussyxtra-beta.squashfs are different from the preview beta. so those are the ones i need confirmation on.

[aarf]

this is the delta to create 2-pussyOS-beta.squashfs it is only 400k. http://www.datafilehost.com/download-2cd17dc2.html



724ed63683a4275c8b8cfc97c3c79eee pussyos-beta.squashfs___2-pussyOS-beta.squashfs.delta

if the name comes down incorrect just rename it to above

have checked that it produces the correct output before upload to hosting site. so at least you can get partial upgrade without a 650mb plus download.

203bcfb74392d985fa904e8604960aa4 2-pussyOS-beta.squashfs

have to rename the files in /live to get the to load in order. mine look like this after partial upgrade. no i didn't notice any difference but i have other appearance mods as well. will do the full upgrade when i decide which files to put into storage to make an extra few spare 100s of MBs

[saintless]

got pussy-beta-preview-xtra2.iso down with some accidents along the way. how do these checkout?

Code: Select all

sh-4.1# md5sum *
ae55d14d796070455dd909a77f30ac7d  1-filesystem.squashfs
203bcfb74392d985fa904e8604960aa4  2-pussyOS-beta.squashfs
fca1c3de5822e2c9d9ed17239911ffff  3-seamonkey.squashfs
e60599a41f7d0afa5a94e0b246772e4b  4-pussyxtra-beta.squashfs
16a091d4e2aa347f3badef825adf3d32  initrd.img
82c5831721e6ff9d069887207976ba1e  vmlinuz
sh-4.1# 

only
2-pussyOS-beta.squashfs and 4-pussyxtra-beta.squashfs are different from the preview beta. so those are the ones i need confirmation on.

Here are mine from the iso. They are the same:

Code: Select all

# md5sum *
203bcfb74392d985fa904e8604960aa4  2-pussyOS-beta.squashfs
e60599a41f7d0afa5a94e0b246772e4b  4-pussyxtra-beta.squashfs
#

[aarf]

got pussy-beta-preview-xtra2.iso down with some accidents along the way. how do these checkout?

Code: Select all

sh-4.1# md5sum *
ae55d14d796070455dd909a77f30ac7d  1-filesystem.squashfs
203bcfb74392d985fa904e8604960aa4  2-pussyOS-beta.squashfs
fca1c3de5822e2c9d9ed17239911ffff  3-seamonkey.squashfs
e60599a41f7d0afa5a94e0b246772e4b  4-pussyxtra-beta.squashfs
16a091d4e2aa347f3badef825adf3d32  initrd.img
82c5831721e6ff9d069887207976ba1e  vmlinuz
sh-4.1# 

only
2-pussyOS-beta.squashfs and 4-pussyxtra-beta.squashfs are different from the preview beta. so those are the ones i need confirmation on.

Here are mine from the iso. They are the same:

Code: Select all

# md5sum *
203bcfb74392d985fa904e8604960aa4  2-pussyOS-beta.squashfs
e60599a41f7d0afa5a94e0b246772e4b  4-pussyxtra-beta.squashfs
#

thanks saintless. i wasnt looking forward to downloading that big iso again.

[aarf]

something happened between screen shots

[aarf]

latest beta full 650mb frugal grub boot new savefile

Code: Select all

root@meow:~# apt-get update
Get:1 http://live.debian.net squeeze-snapshots Release.gpg [835 B]  
Ign http://live.debian.net/ squeeze-snapshots/main Translation-en
Get:2 http://live.debian.net squeeze-snapshots Release [62.7 kB]
Get:3 http://ftp.de.debian.org stable Release.gpg [1672 B]                     
Get:4 http://live.debian.net squeeze-snapshots/main Sources [1749 B]           
Ign http://ftp.de.debian.org/debian/ stable/contrib Translation-en  
Get:5 http://live.debian.net squeeze-snapshots/main i386 Packages [3267 B]     
Ign http://ftp.de.debian.org/debian/ stable/main Translation-en                
Ign http://ftp.de.debian.org/debian/ stable/non-free Translation-en            
Get:6 http://ftp.de.debian.org stable Release [87.3 kB]                        
Get:7 http://ftp.de.debian.org stable/main i386 Packages [6567 kB]             
Get:8 http://ftp.de.debian.org stable/contrib i386 Packages [54.1 kB]          
Get:9 http://ftp.de.debian.org stable/non-free i386 Packages [108 kB]          
Fetched 6887 kB in 2min 12s (51.8 kB/s)                                        
Reading package lists... Done
root@meow:~# apt-get install pmount
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Suggested packages:
  cryptsetup
The following NEW packages will be installed:
  pmount
0 upgraded, 1 newly installed, 0 to remove and 50 not upgraded.
Need to get 109 kB of archives.
After this operation, 901 kB of additional disk space will be used.
Get:1 http://ftp.de.debian.org/debian/ stable/main pmount i386 0.9.23-1 [109 kB]
Fetched 109 kB in 19s (5487 B/s)                                               
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously deselected package pmount.
(Reading database ... 48802 files and directories currently installed.)
Unpacking pmount (from .../pmount_0.9.23-1_i386.deb) ...
Processing triggers for man-db ...
/usr/bin/mandb: can't create index cache /var/cache/man/3814: No such file or directory
Setting up pmount (0.9.23-1) ...
root@meow:~# pmount
Printing mounted removable devices:
/dev/sdb1 on /live/image type ext3 (rw,relatime,errors=continue,data=ordered)
/dev/sdc1 on /mnt/sdc1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount-ro)
To get a short help, run pmount -h
root@meow:~#  pmount -h
Usage:

pmount [options] <device> [<label>]

  Mount <device> to a directory below /media/ if policy requirements
  are met (see pmount(1) for details). If <label> is given, the mount point
  will be /media/<label>, otherwise it will be /media/<device>.
  If the mount point does not exist, it will be created.

pmount --lock <device> <pid>
  Prevent further pmounts of <device> until it is unlocked again. <pid>
  specifies the process id the lock holds for. This allows to lock a device
  by several independent processes and avoids indefinite locks of crashed
  processes (nonexistant pids are cleaned before attempting a mount).

pmount --unlock <device> <pid>
  Remove the lock on <device> for process <pid> again.

Options:
  -r          : force <device> to be mounted read-only
  -w          : force <device> to be mounted read-write
  -s, --sync  : mount <device> with the 'sync' option (default: 'async')
 -A, --noatime
                mount <device> with the 'noatime' option (default: 'atime')
  -e, --exec  : mount <device> with the 'exec' option (default: 'noexec')
  -t <fs>     : mount as file system type <fs> (default: autodetected)
  -c <charset>: use given I/O character set (default: 'utf8' if called
                in an UTF-8 locale, otherwise mount default)
  -u <umask>  : use specified umask instead of the default (only for
                file sytems which actually support umask setting)
  --fmask <fmask>
                use specified fmask
  --dmask <dmask>
                use specified dmask
  -p <file>, --passphrase <file>
                read passphrase from file instead of the terminal
                (only for LUKS encrypted devices)
  -d, --debug : enable debug output (very verbose)
  -h, --help  : print this help message and exit successfuly
  -V, --version
                print version number and exit successfully
root@meow:~#

Code: Select all

 
root@meow:~# apt-get install pfind
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package pfind
root@meow:~# 

so still using my previously posted mount scripts and not pfinding anything. otherwise it is now enough to be my default boot.
after entering wlan0 in the preferences, wifi connects with less fuss than frisbee in puppy.
script to click-mount iso like puppy would be a plus

[sickgut]

got pussy-beta-preview-xtra2.iso down with some accidents along the way. how do these checkout?

Code: Select all

sh-4.1# md5sum *
ae55d14d796070455dd909a77f30ac7d  1-filesystem.squashfs
203bcfb74392d985fa904e8604960aa4  2-pussyOS-beta.squashfs
fca1c3de5822e2c9d9ed17239911ffff  3-seamonkey.squashfs
e60599a41f7d0afa5a94e0b246772e4b  4-pussyxtra-beta.squashfs
16a091d4e2aa347f3badef825adf3d32  initrd.img
82c5831721e6ff9d069887207976ba1e  vmlinuz
sh-4.1# 

only
2-pussyOS-beta.squashfs and 4-pussyxtra-beta.squashfs are different from the preview beta. so those are the ones i need confirmation on.

Yes there was a very minor adjustment to the pussyOS squashfs in the new xtra2.iso, i needed to delete a save-file catroll-panel entry for it to not double up some files in that part of catroll-panel. If you are running the new PussyXtra.squashfs without updating the pussyOS squash its no biggie you will just notice 2 entries for the compressed save file in the catroll-panel.

I apollogize for not supplying the md5 stuff on the site, i havent actually learned to do this yet but i see its the most popular way of verifying downloads and ill implement it soon.

[sickgut]

latest beta full 650mb frugal grub boot new savefile

Code: Select all

root@meow:~# apt-get install pfind
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package pfind
root@meow:~# 

yeah pfind isnt in the debian repos, nothing is wrong here its just that program isnt made for debian or debian call it something else. Do you find using pmount any easier? I am seriously looking at GUI automounting etc if we can i would really like to get it working on Pussy kinda like Puppy does it

[sickgut]

something happened between screen shots

lol now THAT takes the cake for seriously messed up save file or partition or something, i especially like the small picture next to the meow? start menu thing. Thats awesome, i couldnt do that even if i tried

[sickgut]

this is the delta to create 2-pussyOS-beta.squashfs it is only 400k. http://www.datafilehost.com/download-2cd17dc2.html



724ed63683a4275c8b8cfc97c3c79eee pussyos-beta.squashfs___2-pussyOS-beta.squashfs.delta

if the name comes down incorrect just rename it to above

have checked that it produces the correct output before upload to hosting site. so at least you can get partial upgrade without a 650mb plus download.

203bcfb74392d985fa904e8604960aa4 2-pussyOS-beta.squashfs

have to rename the files in /live to get the to load in order. mine look like this after partial upgrade. no i didn't notice any difference but i have other appearance mods as well. will do the full upgrade when i decide which files to put into storage to make an extra few spare 100s of MBs

im sorry youve had a hard time upgrading to the new version, i had to remove the individual squashfs files to save space on the site, however ive got 2 sites now and the other site will host the individual squashfs files. After ive finished uploading the files ill put a link to them on the front page of pussycatforest site.

rename your seamonkey to have a 3 at the start like 3-seamonkey.squashfs or 3seamonkey.squashfs. At present due to a lack of planning on my part, seamonkey needs to be loaded before the 4-pussyxtra-beta.squashfs or java wont work in the browser automatically. This is because seamonkey.squashfs was originally made for the base version of pussy without the xtra apps live java, but because the new pussyxtra.squashfs has java, it also has an updated browser install and cleanmode script to link java to the browser and needs to be layered onto the filesystem after the seamonkey.squashfs to overwrite the browser scripts with the new version. Its a little bit of a mess that ill sort out on next release.

Just to clarify, the optimum booting sequence should be setup like this with the names of the squashfs files:

1-filesystem.squashfs 2-pussyOS-beta.squashfs 3-seamonkey.squashfs 4-pussyxtra-beta.squashfs

I know this makes no sense at all to have the seamonkey as the 3rd loading squashfs but thats just how it is at the moment. Maybe ill have seamonkey.squashfs for the base OS version only and the xtra version will have seamonkey in with the other apps so there isnt a separate squashfs for it with the xtra version. whatever the case ill fix it up next release.

[sickgut]

updated the website www.thepussycatforest.info/linux with a new README.txt and also a known-issues.txt.

if anyone wants anything added to known issues then let me know.