The time now is Sun 19 May 2013, 01:22
All times are UTC - 4 |
|
Page 54 of 122 [1824 Posts] |
Goto page: Previous 1, 2, 3, ..., 52, 53, 54, 55, 56, ..., 120, 121, 122 Next |
| Author |
Message |
sickgut

Joined: 23 Mar 2010 Posts: 1157 Location: Tasmania, Australia in the mountains.
|
Posted: Sun 01 Jan 2012, 12:36 Post subject:
|
|
Ive been testing Pussy extensively, seems very stable and is reasonably complete for a live system there is the obvious hdd install issue and ntfs write to boot partition but as far as a live cdrom or usb or .img version imaged to a internal HDD this isnt a problem.
Development has kinda slowed as most the current problems are debian live related and i have to wait on them to correct things at their end. I released Pussy as a non hdd installable OS but then nooby and john3voltas educated us all in the wisdom of working fancy magic with grub and hdd install is not an officially supported option and only for experienced users.
It is a monumental task for me to setup a hdd install method that is as good as puppy. I dont even know where to begin. Right now however you can image the .img version to your hdd, this installs syslinux bootloader.... if you are dual booting between windows and pussy it can be a little tricky. Also the sheer method of dd'ing a hdd will kill any previous OS on there so if you need to install windows you have to install pussy then install windows, i hav ent tried this yet dual boot windows i dont know if modern vista/ win7 will pic.k up the bootloader and still work.
And its a real pain in the ass to support once we have a alpha quality hdd install method, newbies will simply say it doesnt work and how do i make it go ? just running the .img pussy on a hdd is no problem but dual booting... there will be so many different configs used on various computers that it would be impossible to support and help people effectively. Windows is to blame tho... how far should i bend things just to accommodate and boot an OS that has nothing to do with Pussy whatsoever. I think pussy can survive as a cdrom and usb image ok.
The thing is a professional quality hdd install script is out of my reach, and its better to leave it out rather then release something that only half works.
The main purpose of this post is to ask the community about improvemets they will like in the next version
Considering that i cant tackle the NTFS write to boot problem without help from the debian ive hit a rut The most recent version of Pussy seems really good and there are no major defects glaring at me.
There is swapfile setup and internal hdd mounting scripts being ironed out now but to tell you guys the truth, nothing much is happening on the dev front because there doesnt seem to be anything to improve.
So in order for Pussy to move forward, i am asking you guys to post what you would like to be included in the next release. Pussy is gaining in popularity and daily downloads seen to be increasing but there is less and less feedback on the forum. Apparently that is a sign of success, people generally come to the forum if there is a problem but if it is all working well no one says anything. This kinda keeps me isolated from the real world usage of Pussy by everyone running it. And because of lack of feedback.... i dont know what the people want.
So im asking the community here to please list what you need added or redone or fixed to Pussy, here on the forum. Since the initial alpha release i had achieved the goal i wanted to do, everything else that has came after is entirely from you guys, its you loyal pussy users here that have been improving pussy, ive just been adding your ideas and solutions and pussy has improved very nicely. I am still dedicated as i have ever been to improve Pussy i ever have been but im running out of things to fix. Also the fact that i have no idea of how a normal person uses a computer doesnt help much,
|
|
Back to top
|
|
 |
saintless

Joined: 11 Jun 2011 Posts: 481 Location: Bulgaria
|
Posted: Sun 01 Jan 2012, 13:51 Post subject:
|
|
Hi, Sickgut,
Pussy linux for me is fine the way it is. I even don't need most of the programs in the extra.squash file. Everything I need I can get with apt-get. This is the best part of having Pussy linux. Everything you need is easy to get and install.
The Rox-filler focus problem is partly solved for me by setting the system to open a file with double click. I saw that solution in rcrsn51 post somewhere in the forum. This way the previous selected file can't stay marked and can't be deleted by mistake.
It will be good to include CUPS in the next version if there is enough space.
About the HDD frugal install option we can give the examples we have in grub menu in a help text file. This way everyone can modify one of the examples for Grub or Grub4Dos for his needs. He just have to copy the live folder on the hard drive and it is done. With some linux experience and advice in the forum everyone will be able to do it.
Nooby can help a lot with Grub4Dos examples, I will give mine for Grub. It will be good to find someone with LILO boot loader and Pussy linux entry in it. We can do some testing on every file system and add working example for it.
Edit: We can include Xsane for scanner also.
_________________ KDpup-484 FoxyRoxyLinux Pussylinux BackUp forum
|
|
Back to top
|
|
 |
sickgut

Joined: 23 Mar 2010 Posts: 1157 Location: Tasmania, Australia in the mountains.
|
Posted: Sun 01 Jan 2012, 22:22 Post subject:
|
|
i found a bug in the media dir, and the desktop points to it. The issue is with cdrom ejection.
it wont work if there is no cdrom in the drive. When i coded thiss i mistakenly put eject mountpoint in the cdrom. (the mount point being a dir/folder). AND ofcause if you click mount cdrom nothing happens because no cdrom/ dvd.
The solution is to use: eject /dev/sr0 and the cdrom tray will eject from the computer inviting you to put cdrms or dvds in there even if the cdrom drve is empty
I see this as a major problem and if we dont get the next pussy done soon then i will release a patch for the cdrom thing and while we are at it ill incude a jwm menu patch removes the bogus camera monitor entry that doesnt link to anything at all
what do guys think about a audio cd icon on the dessktop? or does eveeryone use mplayer or alsa player for that??
|
|
Back to top
|
|
 |
saintless

Joined: 11 Jun 2011 Posts: 481 Location: Bulgaria
|
Posted: Mon 02 Jan 2012, 02:01 Post subject:
|
|
| sickgut wrote: | | what do guys think about a audio cd icon on the dessktop? or does eveeryone use mplayer or alsa player for that?? |
I use mplayer for every music or video file, but one more icon on the desktop is not a problem. It can be removed if you don't use it.
_________________ KDpup-484 FoxyRoxyLinux Pussylinux BackUp forum
|
|
Back to top
|
|
 |
nooby
Joined: 29 Jun 2008 Posts: 9383 Location: SwedenEurope
|
Posted: Mon 02 Jan 2012, 05:48 Post subject:
|
|
| Saintless wrote: | | Nooby can help a lot with Grub4Dos examples |
I trust it was sickgut teaching me how to?
title Pussy live
root (hd0,2)
kernel /live/vmlinuz live-media-path=/pussylive boot=live config noprompt quickreboot noautologin
initrd /live/initrd.img
But if you already have another Debian installed that make use of a live directory then do this
title Pussy live
root (hd0,2)
kernel /pussylive/vmlinuz live-media-path=/pussylive boot=live config noprompt quickreboot noautologin
initrd /pussylive/initrd.img
title Pussy Linux
kernel (hd0,2)/pussylive/vmlinuz live-media-path=/pussylive boot=live config quickreboot noprompt noautologin
initrd (hd0,2)/pussylive/initrd.img
I may have done something wrong but it does not help that the internal HD is ext3 I have such on Asus EeePC 900 and it still refuses to write
to the internal hd.
I trust it has to do with Unix/Linux policy that a "live session user" is
not given permission to write to the HD it boots from even if they are root.
I have tested this now many times so it seems to be built into the code
how it set up the "live session permissions" so root can do nothing about it. Unless you edit that place where it is but then you have to know
the secret password? At least on Ubuntu it is secret.
And Crunchbang had same problem them are Debian too now and
it can only be solved if one are full install as I get it.
Ubuntu 10.10 and 11.04 and 11.10 there one can do my "cheat iso boot" and that allow you to do anything even as non root. But that is more like a bug or loop hole and will be plugged by the devs ASAP I guess.
But one could maybe learn from that loop hole or cheat if one know
what is going on.
I have posted about it on Ubuntu, Linux Mint and LinuxQuestion forum
and none is interested.
And I am not on that level so I can not find what is going on either.
But my "cheat" prevent the script from setting up the restricted permissions for a "live session user" so in principle it is easy.
One look for where in the initrd code it sets up the "live session user"
and prevent it from doing this. But that would be to cheat and the Debian
community would ban us from their chat and forum.
_________________
I'm a noob so I use Google Search of Puppy Forum
|
|
Back to top
|
|
 |
aarf
Joined: 30 Aug 2007 Posts: 3620 Location: around the bend
|
Posted: Mon 02 Jan 2012, 05:54 Post subject:
|
|
| Quote: |
Also the fact that i have no idea of how a normal person uses a computer doesnt help much, | sorry cant help you. I dont associate with these either.
I also think the chances of non Linux users coming straight to Pussy with no intermediate Linux experience are close to zero.
_________________
ASUS EeePC Flare series 1025C 4x Intel Atom N2800 @ 1.86GHz RAM 2063MB 800x600p ATA 320G
_-¤-_
<º))))><.¸¸.•´¯`•.#.•´¯`•.¸¸. ><((((º>
|
|
Back to top
|
|
 |
sickgut

Joined: 23 Mar 2010 Posts: 1157 Location: Tasmania, Australia in the mountains.
|
Posted: Mon 02 Jan 2012, 10:35 Post subject:
|
|
| nooby wrote: | | Saintless wrote: | | Nooby can help a lot with Grub4Dos examples |
I trust it was sickgut teaching me how to?
title Pussy live
root (hd0,2)
kernel /live/vmlinuz live-media-path=/pussylive boot=live config noprompt quickreboot noautologin
initrd /live/initrd.img
But if you already have another Debian installed that make use of a live directory then do this
title Pussy live
root (hd0,2)
kernel /pussylive/vmlinuz live-media-path=/pussylive boot=live config noprompt quickreboot noautologin
initrd /pussylive/initrd.img
title Pussy Linux
kernel (hd0,2)/pussylive/vmlinuz live-media-path=/pussylive boot=live config quickreboot noprompt noautologin
initrd (hd0,2)/pussylive/initrd.img
I may have done something wrong but it does not help that the internal HD is ext3 I have such on Asus EeePC 900 and it still refuses to write
to the internal hd.
I trust it has to do with Unix/Linux policy that a "live session user" is
not given permission to write to the HD it boots from even if they are root.
I have tested this now many times so it seems to be built into the code
how it set up the "live session permissions" so root can do nothing about it. Unless you edit that place where it is but then you have to know
the secret password? At least on Ubuntu it is secret.
And Crunchbang had same problem them are Debian too now and
it can only be solved if one are full install as I get it.
Ubuntu 10.10 and 11.04 and 11.10 there one can do my "cheat iso boot" and that allow you to do anything even as non root. But that is more like a bug or loop hole and will be plugged by the devs ASAP I guess.
But one could maybe learn from that loop hole or cheat if one know
what is going on.
I have posted about it on Ubuntu, Linux Mint and LinuxQuestion forum
and none is interested.
And I am not on that level so I can not find what is going on either.
But my "cheat" prevent the script from setting up the restricted permissions for a "live session user" so in principle it is easy.
One look for where in the initrd code it sets up the "live session user"
and prevent it from doing this. But that would be to cheat and the Debian
community would ban us from their chat and forum. |
Hi nooby
Ive updated the README.txt on the website:
http://www.thepussycatforest.info/linux/README.txt
I know your having problems writing to the partition you booted from. Pussy will write to the boot partition if its not NTFS, all the others its fine, it will write to FAT, ext2, ext3, ext4. The Pussy grub layout is very very fussy the information in the README regarding grub was incorrect and so i have updated it with the correct method. When specifying the partition it is very sensitive and altho Pussy may boot and work it wont give you write access to your partition if grub isnt using the right method. Here is the method that gives you write access (pasted from the README):
menuentry 'Pussy live peristent' {
set root='(hd0,1)'
echo 'Meowing the kernel ...'
linux /live/vmlinuz boot=live config persistent noautologin quickreboot noprompt swapon
echo 'Almost over meowing now ...'
initrd /live/initrd.img
}
Note that if Pussy is installed to the same partition that the grub files are on then you dont need to specify the parition at all, and this will work and in these cases you simply leave out the set root= line.
The above way is the only way to get write access, with set root= on its own line. Also if you use /dev/sda2 way instead of the '(hd0,2)" way then it wont work either. It will boot but you wont have write access.
This is different from the way you are using to boot Pussy:
title Pussy Linux
kernel (hd0,2)/pussylive/vmlinuz live-media-path=/pussylive boot=live config quickreboot noprompt noautologin
initrd (hd0,2)/pussylive/initrd.img
^^ this above will boot pussy but you will not have write access.
and this way, altho its very similar wont work either, it will boot but you will not have write access to the boot partition:
title Pussy live
root (hd0,2)
kernel /pussylive/vmlinuz live-media-path=/pussylive boot=live config noprompt quickreboot noautologin
initrd /pussylive/initrd.img
^^ the above needs to be edited so that the second line that specifies that partition goes like this: set root='(hd0,2)'
so the complete entry is this:
title Pussy live
set root='(hd0,2)'
kernel /pussylive/vmlinuz live-media-path=/pussylive boot=live config noprompt quickreboot noautologin
initrd /pussylive/initrd.img
but, i am using grub2 and the example in the README on the site presumes you run grub2. With grub2 code your entry should be this:
menuentry ' Pussy live ' {
set root='(hd0,2)'
linux /pussylive/vmlinuz live-media-path=/pussylive boot=live config noprompt quickreboot noautologin
initrd /pussylive/initrd.img
}
So even tho other methods boot pussy, they do not allow write access. Pussy does allow you to write to the boot partition as long as its not NTFS.
I am not 100% sure on grub legacy or grub4dos code, but in grub2 the above works. I am only officially supporting grub 2 as that is what debian uses, altho debian-live uses syslinux, syslinux is very rarely used as a HDD bootloader.
Maybe it wouldnt be as fussy with syslinux as it is with grub? Its impossible for me to actually support grub legacy/ grub4dos and syslinux and grub2, everyone argues that i should use their favourite bootloader for HDD installs but grub2 is the only one of the grub series that is being updated, and syslinux isnt as familiar to people as grub2. However, when you dd the .img version of Pussy to a HDD it uses syslinux and this method will guarantee that you have write access to your boot partition but ofcause it isnt dual boot friendly, you can add other OSes after imaging your HDD with Pussy but when you image a HDD with Pussy it will completely wipe any OS there first.
when using the .img of pussy on a usb stick it will give you write access to the usb stick you boot from and this is a FAT32 as standard. Also on my personal desktop and laptop i am running Pussy with grub2 using ext3 and i have write access using the above example, on one eeepc i have used the .img version of Pussy and have dd'ed it to the internal SSD and that works perfectly fine and allows me to write to the boot partition.
|
|
Back to top
|
|
 |
nooby
Joined: 29 Jun 2008 Posts: 9383 Location: SwedenEurope
|
Posted: Mon 02 Jan 2012, 12:27 Post subject:
|
|
Puppy don't have Grub2 but Ubuntu and maybe Knoppix can install grub2
to an USB but the whole point of supporting Pussy for me was that it
would work as Puppy in that it boots frugally on NTFS and save to a save file like Puppy and neither need grub2 nor need ext3 or some other such formatting.
Even Knoppix allow me to use NTFS using grub4dos and Knoppix do save
to the NTFS so why would I use Pussy of Knoppix works better?
No criticism at all. I just compare how them appear to me.
I have tried to learn grub2 but failed. Lookj here
http://www.murga-linux.com/puppy/viewtopic.php?t=74673
| Quote: | | Slacko iso boot on grub2? invisible entry |
or here
http://www.murga-linux.com/puppy/viewtopic.php?p=548206#548206
I have also asked several times why entries never show up.
Grub2 is not easy to understand. Grub4dos never act up in that way.
_________________
I'm a noob so I use Google Search of Puppy Forum
|
|
Back to top
|
|
 |
saintless

Joined: 11 Jun 2011 Posts: 481 Location: Bulgaria
|
Posted: Thu 05 Jan 2012, 05:52 Post subject:
|
|
| nooby wrote: |
| Quote: | | All versions of Pussy at this point of asking for user and pass have already booted a webserver and ssh server and telnet server and ftp server. |
How do I put code in boot up so these servers don't get activated at boot? |
Nooby, I wrote this in puppylinux.info but I like to copy the information here for other readers:
OK, Nooby, I think I found very easy solution for you.
I've tested this with frugal pussy linux + live-rw save file on the same partition. The first time when you boot the system you have ssh, telnet and lighttpd running.
Open a terminal and remove them with those commands:
| Code: | | apt-get remove telnet |
Confirm with Y and hit Enter.
Confirm with Y and hit Enter.
| Code: | | apt-get remove lighttpd |
Here you will see warning for few packages no longer in use.
Confirm with Y and hit Enter.
Remove the no longer in use packages with this command:
Confirm with Y and hit Enter.
Reboot the system and you have no longer ssh, telnet, lighttpd running on your system at all, but you still have working from boot internet connection.
There should be another solution with editing some configuration files, but I prefer the easy and simple way to uninstall the packages. If you need them you can install them again with apt-get later.
Edit:If you like to remove gFTP also type:
| Code: | | apt-get remove gftp |
Here you will see warning for few packages no longer in use.
Confirm with Y and hit Enter.
Then type again:
Confirm with Y and hit Enter.
_________________ KDpup-484 FoxyRoxyLinux Pussylinux BackUp forum
|
|
Back to top
|
|
 |
nooby
Joined: 29 Jun 2008 Posts: 9383 Location: SwedenEurope
|
Posted: Thu 05 Jan 2012, 06:48 Post subject:
|
|
Oh thanks, Now I get curious on if Knoppix also has all these
activated from scratch
Re you say reboot. But that would only work if one have
the persistant working. I where not structured enough to get it working.
I made a few attempts but failed to get or grasp how one do it.
And that is for a computer that I seldom use now. I have moved it
to another place in the room to use when I do exercise on the "bike"
One can look on music clips while one exercise
So no hurry. I get back when I feel for it.
Much appreciated you took time to explain how to
apt-get things.
I guess if I install on USB then it would work? Now I am on NTFS HD
_________________
I'm a noob so I use Google Search of Puppy Forum
|
|
Back to top
|
|
 |
saintless

Joined: 11 Jun 2011 Posts: 481 Location: Bulgaria
|
Posted: Thu 05 Jan 2012, 06:58 Post subject:
|
|
| nooby wrote: | | I guess if I install on USB then it would work? Now I am on NTFS HD |
Yes, Nooby, I think it will work on USB without a problem. If I have time I will check how to edit the configuration files for ssh, telnet and lighttpd.
_________________ KDpup-484 FoxyRoxyLinux Pussylinux BackUp forum
|
|
Back to top
|
|
 |
nooby
Joined: 29 Jun 2008 Posts: 9383 Location: SwedenEurope
|
Posted: Thu 05 Jan 2012, 07:42 Post subject:
|
|
Only do it if it feel good for your own inner motivation.
The reason I was and still is somewhat active in Pussy threads
is that I had hoped sickgut could come up with a Pussy that equaled
Puppy in functions.
Debian does not seem to allow that.
Ubuntu if one cheat booting using their iso gives an almost similar
experience as a Puppy that one boot with pfix=ram and never do a
pupsave for. One are allowed to do anything if one cheat boot it.
Debian seems to have the prevention of such cheat well hidden
_________________
I'm a noob so I use Google Search of Puppy Forum
|
|
Back to top
|
|
 |
saintless

Joined: 11 Jun 2011 Posts: 481 Location: Bulgaria
|
Posted: Thu 05 Jan 2012, 07:57 Post subject:
|
|
OK, Nooby
I think Pussy linux will become more puppy like in time. Beta-preview-2 is much closer to puppy than the Alpha version was.
In some ways Pussy linux is better and easier to use than Puppy, but it still has too much to learn from Puppy also.
Joe (Big_bass) created TXZ_Pup from Slackware and it works perfect with Slackware packages.
Lets hope in time Pussy linux will became just like puppy with the same 100% working apt-get.
_________________ KDpup-484 FoxyRoxyLinux Pussylinux BackUp forum
|
|
Back to top
|
|
 |
jbv
Joined: 31 Dec 2010 Posts: 174
|
Posted: Fri 06 Jan 2012, 05:27 Post subject:
|
|
Hi sickgut,
Based one of your previous messages, I was hoping/expecting your new USB Image to be setup to allow someone with only a Windows machine to install it. Since it wasn't, I just went with the xtra-beta-preview2.iso and used the Universal USB installer and then tweaked the syslinux.cfg file again.
I've spent the last few days messing around with pussy and I've probably re-installed it more times than I can count, but I've almost got it right.
Along the way, I've had some interesting experiences. I lost the web-server at some point and no matter what I did, it wouldn't start. Somehow the ownership of the log file got changed to be root,root and lighttpd couldn't open it, so it just crashed at startup. I tried changing ownership and rights back and then doing another save-image, but for some reason the change wasn't being reflected. I ended up unpacking the save file manually, editing lighttpd.conf to create the log file in /tmp (ramdisk?) and then manually made the 99save file again. I have noticed there do seem to be a few little quirks with the update-save-file script, although I don't know if this is a problem with the script per-se or just some quirks in unsquashfs and mksquashfs that may need special switches or what.
The strange problem with lighttpd only started after I ran anyterm for the first time. Not sure if that is a coincidence or not.
I also discovered that plugging in another USB stick and it wouldn't enumerate. I kept getting "device descriptor read/64, error -71" faults. Messing around with sys/module/usbcore/parameters and remembering to make a save-file eventually sorted that out. The strange thing here though is that the usbcore/parameters ended up changin back to where they were originally after a reboot, but the USB sticks now work - strange.
I also had fun and games changing the host name, but got that sorted.
I've managed to change the default font and size in XTerm so that I can now read it and it is almost working properly. There is only one thing with XTerm that I can't get right and that is the keyboard function keys. I've got what should be a standard 104-key keyboard, I've used the parameter *sunKeyboard: true in /etc/X11/app-defaults/XTerm but the function keys still don't work. I've tried running the language and mapping script and selecting a generic 104-key keyboard, all to no avail.
Does anyone know how to get function keys to work properly in XTerm with a standard 104-key keyboard ? What am I missing?
There are two other (really dumb) things I couldn't work out or find clues to ...
1) How can I get the Rox-filer background to start automatically when FVM/X starts?
2) How do you get a link/icon/shortcut/whatever on the Rox-filer desktop?
Cheers
|
|
Back to top
|
|
 |
nooby
Joined: 29 Jun 2008 Posts: 9383 Location: SwedenEurope
|
Posted: Fri 06 Jan 2012, 07:11 Post subject:
|
|
I always log in as root on Pussy.
When it ask for user I write root and password pussy
and that way it is a bit like puppy also being root?
What is different is that when doing frugal install then in Puppy
you are given a lot of ntfs permissions that Debian by default only
give to full install?
Exception is Knoppix but that is the only exception.
Neither Mepis not AntiX nor Semplicity nor Crunchbang allow you to
be live session user and have write permission to the drive you boot from.
Not Pussy either.
_________________
I'm a noob so I use Google Search of Puppy Forum
|
|
Back to top
|
|
 |
|
|
Page 54 of 122 [1824 Posts] |
Goto page: Previous 1, 2, 3, ..., 52, 53, 54, 55, 56, ..., 120, 121, 122 Next |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|