Umm, how's that?jamesbond wrote:Well, you are already running as root,
Yeah, I hadn't ticked the box to make it persistent. In other puppies it automatically became persistent if loaded on the fly.shinobar wrote:Maybe we need to load the sfs from the control panel and make a check on the 'permanent'.smokey01 wrote:I have also noticed loading the fd64-devx_600.sfs is not persistent.
Actually, does not workshinobar wrote:getnvidia-0.2-64.pet, NVIDIA driver installer/PET/SFS builder.
Code: Select all
blacklist nouveau
You did better than me, I couldn't even get graphics to work after I tried. Had to delete the savefile and start again.shinobar wrote:Actually, does not workshinobar wrote:getnvidia-0.2-64.pet, NVIDIA driver installer/PET/SFS builder.
It purges the nvouveau driver by listing it up on the blaklist, /etc/modprobe.d/blacklist,conf:It seems success for the first time, but the next boot, the nouveau revives. Why?Code: Select all
blacklist nouveau
yes, woks, I had no idea to double-click for checking the mark.jamesbond wrote:1. Choose the package you want to uninstall (double-click or press Enter)
2. Click uninstall
OK, I know SFS incompatibility with the kernel, but this is the first time to see incompatible PET.jamesbond wrote:600 uses xz compression for the pet.
/usr/bin/petspec at line 169 wrote: <default>${DEF_compiledrelease}</default><variable>DB_compiledrelease</variable> </entry>
Fix wrote: <default>"${DEF_compiledrelease}"</default><variable>DB_compiledrelease</variable> </entry>
Right.smokey01 wrote:I couldn't even get graphics to work after I tried. Had to delete the savefile and start again.
Code: Select all
# rm /etc/X11/xorg.conf
# xwinSylvander, as I get it they set it up that way.Sylvander wrote:Umm, how's that?jamesbond wrote:Well, you are already running as root,
I'm not aware that I changed to running as root.
How did I do it do you think?
Yes.smokey01 wrote:Did you get Recorder to work in FatDog?
I thought of saving the file to /mnt/home but that's not foolproof either. It only ever makes one file. Each time you create a new recording it overwrites the old one. It took a little while to work out how to do that. Files need to be moved after each recording that's why I made the window pop up to make it easy to find.shinobar wrote:Yes.smokey01 wrote:Did you get Recorder to work in FatDog?
But i think these recorders need more function, at least to specify the saving folder because the /usr/local/recorder folder is on the aufs and easily filled up under frugal installations.
Another impression, the icon on the buttons are better to be the same of the gtk stock icons, gtk-media-record, gtk-media stop, and etc. That is, red circle for record and white box for stop.
I just used dir2pet and it worked. Maybe it was fixed in B1.shinobar wrote:yes, woks, I had no idea to double-click for checking the mark.jamesbond wrote:1. Choose the package you want to uninstall (double-click or press Enter)
2. Click uninstall
OK, I know SFS incompatibility with the kernel, but this is the first time to see incompatible PET.jamesbond wrote:600 uses xz compression for the pet.
BTW, how to make pet on Fatdog64? The dir2pet does not work because of the bug in the petspec./usr/bin/petspec at line 169 wrote: <default>${DEF_compiledrelease}</default><variable>DB_compiledrelease</variable> </entry>Fix wrote: <default>"${DEF_compiledrelease}"</default><variable>DB_compiledrelease</variable> </entry>
Mick informed me this is not yet multiuser compatible, so I will hold it off uploading it to the pet repo. But it does work as long as you only use root.Jim1911 wrote:GUI to download LibreOffice version 0.17 is out and works fine with Fatdog64-600
Nooby is right. By default when you boot in Fatdog you auto-login and run as root, just like in any puppies.nooby wrote:Sylvander, as I get it they set it up that way.Sylvander wrote:Umm, how's that?jamesbond wrote:Well, you are already running as root,
I'm not aware that I changed to running as root.
How did I do it do you think?
Seamonkey and many other applications run under user Spot.
But the x or GUI desktop is root? As you know I am a true noob I only guess.
One get automatically logged in as root for X?
For to not be root you most likely need to create a user using root
and then log into that user after boot? Am I right?
Perhaps the text is not obvious. I have changed "load permanently" to "load at every boot".smokey01 wrote:Yeah, I hadn't ticked the box to make it persistent. In other puppies it automatically became persistent if loaded on the fly.shinobar wrote:Maybe we need to load the sfs from the control panel and make a check on the 'permanent'.smokey01 wrote:I have also noticed loading the fd64-devx_600.sfs is not persistent.
So many little, but subtle changes in Fatdog.
Right on target, Grant !smokey01 wrote:Sylvander my FD64-600b1 boots from grub to desktop in 10 seconds. It takes about 3 more sec to show the 10 drive icons.
The drive icons will only kick-in 3 seconds after the desktop is loaded, to ensure that X desktop is running and ready.I need to test this, it shouldn't be the case. blacklist.conf should not be cleared at next boot.shinobar wrote:Actually, does not workshinobar wrote:getnvidia-0.2-64.pet, NVIDIA driver installer/PET/SFS builder.
It purges the nvouveau driver by listing it up on the blaklist, /etc/modprobe.d/blacklist,conf:It seems success for the first time, but the next boot, the nouveau revives. Why?Code: Select all
blacklist nouveau
EDIT: the /etc/modprobe.d/blacklist,conf is cleared after boot. Who and when?
If you hover the mouse cursor over the listview titles, you will get a tooltip saying soshinobar wrote:yes, woks, I had no idea to double-click for checking the mark.jamesbond wrote:1. Choose the package you want to uninstall (double-click or press Enter)
2. Click uninstall
600 supports both gzip compressed pets and xz compressed pets; but only creates xz compressed pets. If you want to create gzip-compressed pets you need to run dir2pet from other puppies; or otherwise you have to go through convoluted process of: dir2pet, followed by pet2txz; followed by tar -xJvf; followed by tar -czvf; follewed by tgz2pet.OK, I know SFS incompatibility with the kernel, but this is the first time to see incompatible PET.jamesbond wrote:600 uses xz compression for the pet.
Thank you shinobar, fix applied.BTW, how to make pet on Fatdog64? The dir2pet does not work because of the bug in the petspec./usr/bin/petspec at line 169 wrote: <default>${DEF_compiledrelease}</default><variable>DB_compiledrelease</variable> </entry>Fix wrote: <default>"${DEF_compiledrelease}"</default><variable>DB_compiledrelease</variable> </entry>
Use the pkeys= boot parameter. You can specify anything which exist in /lib/keymapsshinobar wrote:BTW, How to change the keyboard map on console?
The Keyboard localization on the control panel only effective with X.
I tried that and it didn't help.shinobar wrote:Right.smokey01 wrote:I couldn't even get graphics to work after I tried. Had to delete the savefile and start again.
If i cannot get the desktop at boot, i type next 2 commands on console:Code: Select all
# rm /etc/X11/xorg.conf # xwin
Thanks, fixed for next release. If you want to fix it now, edit /usr/sbin/fatdog-drive-icon-start.sh, line 13, change:smokey01 wrote:Small problem but annoying.
Note the drive sequence on the attached.
Will look again at Fatdog as it boots, and see what it's doing NOW.smokey01 wrote:Sylvander my FD64-600b1 boots from grub to desktop in 10 seconds. It takes about 3 more sec to show the 10 drive icons.
There is a time race between the load_sfs.sh and the rc.nvidia(.copy).shinobar wrote: the /etc/modprobe.d/blacklist,conf is cleared after boot. Who and when?