Page 18 of 22

Posted: Thu 29 Jan 2015, 15:51
by gcmartin
Hello @Jamesbond. I remember your asking for some coding for FirstRUN which could work for friendly user system start where user feels he has covered the basics, personally, at initial boot on one's system. A false sense of power, I know, yet, it begins a level of comfort to all PUP users.

Here is the FirstRUN facility that @TaZoC adapted for LightHouse (which his system models after FATDOG in basic system structure).

Hope this helps in some small way.

Posted: Thu 29 Jan 2015, 20:10
by boblark
Keyboard collision:
SD64 as with others, uses ALT-F4 to close an app. I need to disable it and it doesn't come from Sven. Can somebody steer me to the file that controls this?

(I must confess i altered this in Puppy 5.x and can't find how I did it---shame)

Posted: Thu 29 Jan 2015, 22:13
by WillM
Hi boblark

In the file /etc/xdg/openbox/rc.xml there is a key binding for A-F4 to close windows. rc.xml may also be in ~/.config/openbox

Posted: Thu 29 Jan 2015, 23:07
by boblark
WillM wrote:
In the file /etc/xdg/openbox/rc.xml there is a key binding for A-F4 to close windows. rc.xml may also be in ~/.config/openbox
SOLVED - That did it when I commented out the binding on the first file. I couldn't find any more rc.xml files in a search, and it all survived a reboot, so onward. Thanks

Posted: Thu 29 Jan 2015, 23:09
by gcmartin
Alt-F4 is a 30 year old International architectural standard for closing desktop windows. Just like the X in a dialogue box on the Window, itself.

Of course, I'm sure you know this.

Posted: Fri 30 Jan 2015, 05:43
by boblark
Yes, it is sort of a battle of old stuff. The colliding program goes back to 1996 used for controlling an SDR (DSP-10 radio), before they were called that. It uses SCROLL-ALT-F4 for ending the program.

The neat thing is that it runs just fine under SD64 and DOSBox. The last MS OS that was fully able to do that was Win98! XP ran it, but latency issues messed up a bunch of functionality.

Posted: Fri 30 Jan 2015, 06:59
by jamesbond
@gcmartin: thanks for the first-run scripts. Have you tested whether it works with Fatdog?
gcmartin wrote:Alt-F4 is a 30 year old International architectural standard for closing desktop windows. Just like the X in a dialogue box on the Window, itself.

Of course, I'm sure you know this.
Well, I certainly don't know that.

As far as I know, this Alt-F4 thingy comes from the world of Windows. No other GUI environments prior to Windows use Alt-F4 for closing a desktop window. Non-Windows keyboard may not even have an "Alt" key ... And 30 years ago, Windows was barely a standard (Windows 1.0 was released on November 1985) ...

Same as "X" to close windows. Windows 1.0 doesn't even have an "X", neither did early Macs, neither did early X Windows manager (twm, mwm). They all used little squares or different symbols; some didn't even have an icon - you'd had to right-click and choose "Kill" or something.

EDIT: Typo and clarification.

Posted: Fri 30 Jan 2015, 07:06
by stemsee
I just closed google chrome using alt-F4. and a rox window! cool..

Posted: Fri 30 Jan 2015, 07:20
by Ted Dog
Earliest was 25 years ago in Xwindows for AltF4 for me, but I also recall crazy three button mice and interweb was run with gophers. :lol:

Posted: Fri 30 Jan 2015, 19:57
by prehistoric
Ted Dog wrote:Earliest was 25 years ago in Xwindows for AltF4 for me, but I also recall crazy three button mice and interweb was run with gophers. :lol:
Bet you also know how to access an M.I.T. AI lab coke machine from the keyboard of a Lisp machine.

Posted: Fri 30 Jan 2015, 20:26
by jamesbond
Ted Dog wrote:Earliest was 25 years ago in Xwindows for AltF4 for me, but I also recall crazy three button mice and interweb was run with gophers. :lol:
Well, it ain't dead yet :lol: https://addons.mozilla.org/en-US/firefo ... verbiteff/

Posted: Fri 30 Jan 2015, 21:32
by anikin

Posted: Fri 30 Jan 2015, 22:37
by stemsee
That is 'Ctrl + Alt + Del' ... this 'Alt + F4' ... hellooo!

Posted: Fri 30 Jan 2015, 22:52
by Ted Dog
I recall it was so easy to use the interweb to setup remote file folders, why is it like pulling teeth now days on my private lan? No MIT was too far away we had a remote controlled coffee pot and its own little icon in X on a SUN server it would alert you on the freshness of the coffee. That was about 7 minute walk so useful :wink:

Posted: Fri 30 Jan 2015, 23:46
by anikin
stemsee wrote:That is 'Ctrl + Alt + Del' ... this 'Alt + F4' ... hellooo!
I'm just expanding gcmartin's theory a bit.

Posted: Sat 31 Jan 2015, 08:18
by neerajkolte
I tried making an SFS of Vivaldi Browser.
But when I run try to run it as spot, using following command, I get error

Code: Select all

# run-as-spot vivaldi-stable
su: can't execute '/bin/dash': Permission denied
stat /bin/dash says

Code: Select all

# stat /bin/dash
  File: '/bin/dash'
  Size: 74832     	Blocks: 152        IO Block: 4096   regular file
Device: 10h/16d	Inode: 238         Links: 1
Access: (0775/-rwxrwxr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2015-01-28 14:32:00.209338640 +0530
Modify: 2014-10-25 08:30:19.000000000 +0530
Change: 2015-01-28 14:32:00.209338640 +0530
 Birth: -
# 
Maybe I am using run-as-spot wrongly.
Any help?
Thanks.

- Neeraj.

Posted: Sat 31 Jan 2015, 09:37
by SFR
neerajkolte wrote:

Code: Select all

# run-as-spot vivaldi-stable 
su: can't execute '/bin/dash': Permission denied
Hmm, I've seen this before... I think you need to repack the SFS. But this time make sure all crucial directories like vivaldi/usr, vivaldi/usr/bin, vivaldi/usr/share etc. have proper permissions and ownership (in most cases it will be 0755/root:root), especially the top-most directory, which is later given as a parameter to mksquashfs (in this case: mksquashfs vivaldi vivaldi-browser.sfs).

HTH
Greetings!

Posted: Sat 31 Jan 2015, 15:46
by neerajkolte
Thanks SFR,
I will try it tomorrow.

- Neeraj.

Posted: Sat 31 Jan 2015, 16:23
by rufwoof
@JamesBond

I always remaster to a version where the ISO files have local copies of those files stored internally. i.e. all ISO files except the fd64.sfs and kernel-modules.sfs - which the remaster process creates anyway. Typically I create a /usr/sbin/remaster/ISO-FILES directory and copy them to there. That way you can remaster without either a CD or local ISO file (just point the remaster process to the vmlinuz in the /usr/sbin/remaster/ISO-FILES directory).

Particularly handy if your pup contains a PXE server as then any PXE booted client can remaster and drop the initrd/vmlinuz into the PXE server directory and become a PXE server itself.

I've changed my version of fatdog-remaster.sh to use gzip -1 mksquashfs compression and it remasters a lot more quickly - typically around a minute compared to around 5 mins when using xz high compression. Larger ISO output, but if you're only using the ISO to extract initrd/vmlinuz and frugal boot its better to have the faster remaster time.

Posted: Sat 31 Jan 2015, 19:06
by gcmartin
Removed. Sent as a PM, instead.