Weirdly, the menu system does not seem to have a way to start up the command-line interface.
There IS an icon on the desktop for it, "Console"
Saturday 16 March 2013
Accessing WD NAS from Puppy
Finally got a SAMBA package to work:
lameSMBqmount
(Info on the settings to get it working to follow)
lameSMBqmount
(Info on the settings to get it working to follow)
Friday 15 March 2013
SSH - Secure Shell remote log-in to the Puppy Linux machine from Windows
Here is the way to do it:
You require a Secure Shell daemon (or server) running on the Puppy Linux box.
For some reason, this seems to be quite immature on Puppy, but here is one:
http://murga-linux.com/puppy/viewtopic.php?mode=attach&id=12005
There is an ssh-gui package in the pet repository, but it does not state anywhere if it is a client or a server or both. It's set-up options do not make it any clearer.
On the Windows machine, this is then accessed using an SSH client, the preeminent one being PuTTY, available as a free download from www.putty.org
The initial PuTTY window lets you set up the remote device's IP address, etc. then brings up the terminal window.
Once the terminal window is open, there seems to be no dialogue box or menu option to change that setting, barring close the PuTTY ssh client app and re-start it.
You require a Secure Shell daemon (or server) running on the Puppy Linux box.
For some reason, this seems to be quite immature on Puppy, but here is one:
http://murga-linux.com/puppy/viewtopic.php?mode=attach&id=12005
There is an ssh-gui package in the pet repository, but it does not state anywhere if it is a client or a server or both. It's set-up options do not make it any clearer.
On the Windows machine, this is then accessed using an SSH client, the preeminent one being PuTTY, available as a free download from www.putty.org
The initial PuTTY window lets you set up the remote device's IP address, etc. then brings up the terminal window.
Once the terminal window is open, there seems to be no dialogue box or menu option to change that setting, barring close the PuTTY ssh client app and re-start it.
Sunday 17 February 2013
Fujitsu Futro S100 Linux drivers
The driver for the VIA Chrome 9 graphics chipset which makes up part of the VIA VX800 combined NorthBridge, SouthBridge and Graphics Adaptor is the Linux Kernel driver CONFIG_FB_VIA
The driver for the VIA VT6115 ethernet controller chip is via-rhine.
The driver for the VIA VT6115 ethernet controller chip is via-rhine.
Friday 15 February 2013
Fujitsu Futro S100 - boot from Network using PXE
Well, I've almost got my head around the network boot business.
There is a standard for BIOS boot from network - called PXE (for Preboot eXecution Environment), and apparently aka "pixie", and originally created by Intel for 32bit systems.
It makes use of a protocol that combines and extends DHCP and TFTP
The device booting up gets itself an IP address (either static or from the DHCP server)
Some useful links:
Windows software to serve the DHCP extensions and TFTP the boot files
http://www.vercot.com/~serva/an/NonWindowsPXE3.html
A good tutorial:
http://osdev.berlios.de/netboot.html
The wikipedia page
http://en.wikipedia.org/wiki/Preboot_Execution_Environment
The PXE spec
http://quimby.gnus.org/internet-drafts/draft-henry-remote-boot-protocol-00.txt
and v2.1
ftp://download.intel.com/design/archives/wfm/downloads/pxespec.pdf
PXELINUX
http://www.syslinux.org/wiki/index.php/PXELINUX
An interesting thread, though I'm still digesting it:
http://reboot.pro/topic/2936-is-it-possible-to-boot-any-bootable-iso-file-off-the-network/
Articles about tinyCore:
http://sirlagz.net/2011/05/16/how-to-pxe-boot-tiny-core-linux/
and Puppy
http://minipc.org/pxe/1-netbooting-readme.txt
http://puppylinux.org/wikka/PXELINUX
https://docs.google.com/document/d/1bkMJ-2wjAAC8HVZZTZBFxBELbojoGctLMg27KazqvRw/edit?hl=en&pli=1#
http://sirlagz.net/2011/06/13/how-to-boot-puppy-5-2-5-over-pxe/
and a thread
http://murga-linux.com/puppy/viewtopic.php?t=23615
Some ready-made netboot files (for Breeezy)
http://minipc.org/pxe/
Nitty-gritties of PXE
http://wiki.osdev.org/PXE#Files.2C_via_TFTP
There is a standard for BIOS boot from network - called PXE (for Preboot eXecution Environment), and apparently aka "pixie", and originally created by Intel for 32bit systems.
It makes use of a protocol that combines and extends DHCP and TFTP
The device booting up gets itself an IP address (either static or from the DHCP server)
Some useful links:
Windows software to serve the DHCP extensions and TFTP the boot files
http://www.vercot.com/~serva/an/NonWindowsPXE3.html
A good tutorial:
http://osdev.berlios.de/netboot.html
The wikipedia page
http://en.wikipedia.org/wiki/Preboot_Execution_Environment
The PXE spec
http://quimby.gnus.org/internet-drafts/draft-henry-remote-boot-protocol-00.txt
and v2.1
ftp://download.intel.com/design/archives/wfm/downloads/pxespec.pdf
PXELINUX
http://www.syslinux.org/wiki/index.php/PXELINUX
An interesting thread, though I'm still digesting it:
http://reboot.pro/topic/2936-is-it-possible-to-boot-any-bootable-iso-file-off-the-network/
Articles about tinyCore:
http://sirlagz.net/2011/05/16/how-to-pxe-boot-tiny-core-linux/
and Puppy
http://minipc.org/pxe/1-netbooting-readme.txt
http://puppylinux.org/wikka/PXELINUX
https://docs.google.com/document/d/1bkMJ-2wjAAC8HVZZTZBFxBELbojoGctLMg27KazqvRw/edit?hl=en&pli=1#
http://sirlagz.net/2011/06/13/how-to-boot-puppy-5-2-5-over-pxe/
and a thread
http://murga-linux.com/puppy/viewtopic.php?t=23615
Some ready-made netboot files (for Breeezy)
http://minipc.org/pxe/
Nitty-gritties of PXE
http://wiki.osdev.org/PXE#Files.2C_via_TFTP
Fujitsu Futro S100 Heat management
Fujitsu Futro S100 on stand |
The bottom side, hidden in this photo, is just as perforated as the visible upper side.
So I'm guessing that the key issue for a stand is to raise the perforated section of the underside up off the surface by... it looks like 6 to 10mm.
I'm now toying with creating a couple of U-shaped supports out of some 20mm veneered chipboard.
Linux VIA Rhine III ethernet driver and the VIA VT6115 chip
Wary Puppy picks up the via-rhine Linux driver module all by itself.
One of the interesting* things, is that the VIA VT6115 chip used in the Fujitsu Futro S100 isn't in the list of chips supported by via-rhine linux driver.
* for particular values of the word "interesting"
One of the interesting* things, is that the VIA VT6115 chip used in the Fujitsu Futro S100 isn't in the list of chips supported by via-rhine linux driver.
* for particular values of the word "interesting"
Subscribe to:
Posts (Atom)