If a client doesn't know the server IP in advance, run PeasyPort and scan for Port 8000.

------------------

Read here, here and here for additional tools to use with the Python HTTP Server.

--------------------------

Setting MIME-type associations for audio files

Suppose that you have set up the server to stream audio files like MP3s. The client computer is also running a version of Stretch-Live with PeasyMP3 as the audio player and Firefox as the browser. In order that Firefox can recognize PeasyMP3 as a "helper" application, the client needs some configuring.

1. Make sure that PeasyMP3 works with locally installed MP3 files and is set as the default application. You can confirm this by looking in the file ~/.config/mimeapps.list.

2. Open /etc/mime.types and search for "mp3". The associated mime type is "audio/mpeg".

3. Open /etc/mailcap. Under "User Section Begins", add the line "audio/mpeg; peasymp3 %s"

@all
New version of "Google-drive Filemanager" v2, it's a complete rewrite, added to repos "googledrivegui2" (previous package name was just "googledrivegui")
Install with Synaptic or from terminal with apt-get:

This system uses Bluez5 and its bluetoothctl tool for basic pairing/connection operations. But it avoids the need for PulseAudio by using bluez-alsa.

The main screen has several Help buttons. There is a learning curve to using bt4stretch.

Update:Version 1.2 is a major upgrade. It now produces a standard ALSA device called "bluetooth" that will be recognized by most media players. Set it as the default ALSA output in your .asoundrc by UNcommenting the bottom two lines. You can even play Youtube audio through Pale Moon to a BT speaker!

Be aware that Mplayer does not work properly with BT in a 64bit setup. But VLC, Deadbeef, Audacious, etc. work fine.

Note: If you have a .asoundrc file from a previous version, you must delete it first.

Note:If the "bluetooth" ALSA device is properly configured and set as default, you can control its volume from your tray Volume applet. If the applet is not working, there is a problem with your BT4Stretch setup. Either the BT speaker has not paired/connected properly or your .asoundrc is wrong.

Hints: Learn the blink and beep codes of your BT device. For example, the device may blink like it's connected when it's not. Do a disconnect, wait until the blink changes, and connect.

If the Quick Connect button doesn't work, use Control so you can see what's happening.

In my experience, switching between OS's can cause flaky behaviour with your BT hardware. If necessary, do a BT Reset, cold reboot and re-pair the device.

Here is a stand-alone script for doing frugal installs of Stretch-Live ISOs. You can run it from Stretch or from various Puppies.

This tool can also install onto USB devices. The preferred USB destination is an unjournaled ext4 partition.

1. Download and extract the script attached below. It is NOT a fake .gz file!
2. This is a clickable script. Save it somewhere like /root.
3. Make an EMPTY folder on an ext partition to hold the frugal install. It can also be a subfolder.
4. Run the script. Select the ISO, the target partition and the install folder. Click Install.
5. The "live" folder from the ISO will be copied into the install folder.
6. A window will pop-up showing the new Grub4Dos menu entry.
7. Copy and paste the entry into your menu.lst file. Hint: Use Ctrl-A, Ctrl-C, Ctrl-V. Keep the long "kernel" line as a SINGLE line.
8. A backup copy of the GRUB entry is saved in the frugal install folder.
9. Reboot.

--------------------------

The Bootloader section does a basic Grub4Dos setup to make a hard/flash drive bootable. Read the warning about Windows.

The new Puppy section does a standard frugal install of a Puppy ISO.

----------------------

Update: The regular Basic Install uses the Porteus boot method. But some newer hardware has a problem on USB devices with this method and the stock 4.9.0 kernel. You will get a "file not found" error. Here are some solutions:

1. Use the alternate install procedure under the new Live-boot tab. Be aware that this method does NOT permit a save file/folder.

2. Change the initrd1.xz in the "live" folder of your USB install. This should allow a Porteus boot with persistence.
a. Download initrd1.xz-usb.tar.gz
b. Extract the package. It contains 32/64 bit versions of a patched initrd1.xz
c. Select your version, rename it as initrd1.xz and drop it into your live folder.

3. Do a kernel switch, using the same technique as in Puppy. Read here.

Here is a strategy for building a system from scratch that can run a variety of Stretch-Live and Puppy versions.

1. Boot the machine from a system disc or flash drive.

2. Run Gparted and make the following partitions:
a. an ext3 "boot" partition. It will contain the Grub4Dos boot files. It can also store your original ISO files, devx files and application SFS packages. If this is UEFI system, the first partition must be FAT32.
b. an ext4 partition to hold the frugal installs.
c. an ext4 partition to hold common data like a music collection.

4. Run the script, select Bootloader and install Grub4Dos to drive sda.

5. For each ISO:
a. make a matching folder on sda2.
b. Do a Basic install or Puppy install. In each case, the target partition is /dev/sda2.
c. Copy/paste the GRUB menu entry into your menu.lst file on sda1.
d. Make at least one CleanMode entry to act as a "back-door" into your system for maintenance purposes.

Here is the p910nd-print-server. It has two functions - it can share your attached printer across the network and it provides a control panel to manage your printers. The instructions are here. The dependency is arp-scan.

Recommended to upgrade the kernel to the latest security release, at this time it's 4.9.0-5 (package version: 4.9.65-3+deb9u2 (2018-01-04))
See info here (Meltdown patch, not sure if/when Spectre will be addressed):
https://www.debian.org/security/2018/dsa-4078
Therefore install latest upgrade-kernel (v1.0.5) from Synaptic or with apt-get,

Code:

apt-get update
apt-get install upgrade-kernel

and run "Upgrade kernel" from Menu > System and it will upgrade to 4.9.0-5 (on a frugal install)

Also updated mklive-stretch script
Change is that latest kernel 4.9.0-5 will be installed (previously was 4.9.0-4).
And (at github) the archive name containing basic boot scripts, configs, aufs and squashfs modules (for 4.9.0-5) is now:
dog-boot-stretch-20180112.tar.gz
(used in the script now to extract and copy files to the chroot)

rcrsn51 wrote:

Here is a stand-alone script for doing hard drive frugal installs of Stretch-Live ISOs. It is intended for Puppy-like systems booted by Grub4Dos.

Nice ! never tried before from=UUID and changes=UUID, works well.
Added to first post a link to your post and added to "Norepo" packages:
https://fredx181.github.io/StretchDog/NoRepo/
Also added your latest packages to repos.

EDIT: @ALL, It may come in handy to quickly load the DEVX in case compiling.
Here's DEVX containing most important build tools and latest linux-headers (4.9.0-5)
https://github.com/fredx181/StretchDog/releases/tag/v2.1
For i386 (pae) or amd64: 61-DEVX-Stretch-20180113-k4.9.0-5-....

I tried this on another nvidia machine and it worked the same way. Apparently only a small part of the nvidia install package is actually kernel-related.

If you remove the driver and re-install it, it's smart enough to just build the new kernel module.

Is there a better way in apt-get to remove-install in one step?

BTW, I have used the same procedure when I forgot to install the kernel headers at the beginning of the install and the operation failed.

---------------------

Regarding UUID in the frugal-installer. I started using this when working with "split installs". If you just use "from=/", Porteus triggers a search. Under certain conditions, it can find the wrong "live" folder.

By using UUID, you can specify the unique path to your install.

BillLast edited by rcrsn51 on Sun 14 Jan 2018, 12:15; edited 1 time in total

Regarding UUID in the frugal-installer. I started using this when working with "split installs". If you just use "from=/", Porteus triggers a search. Under certain conditions, it can find the wrong "live" folder.

Yes, the UUID option is nice, for info, another way to prevent finding the wrong "live" folder you can place "live" in folder "unique_name" and use "from=/unique_name"
EDIT: I see now that your installer does that already, so you are right that the chance is zero when using UUID that it finds the wrong "live"

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum