Damn Small Linux (DSL) Forums
Welcome, Guest. Please login or register.
Did you miss your activation email?
September 02, 2014, 07:16:02 AM

Login with username, password and session length
The new DSL forums are now open.
297715 Posts in 294148 Topics by 221 Members
Latest Member: ngorock
Search:     Advanced search
* Home Help Search Login Register
Get The Official Damn Small Linux Book. Great VPS hosting provided by Tektonic

  Show Posts
Pages: [1] 2 3 ... 10
1  Damn Small Linux / DSL Ideas and Suggestions / Re: Flash or Gnash?? on: August 26, 2014, 11:23:04 PM
The version of the Linux Kernel used in DSL limits the software that can be run with it. New Adobe Flash doesn't work. I'd have to check the kernel version required by Gnash, but it probably won't work either.

There are plenty of posts about this in the old forum archive, Flash compatibility broke down with DSL a number of years ago. I believe at least relatively recent versions of Java work though, however the old Firefox version prevents them from running in the web browser.
2  Damn Small Linux / Other Help Topics / Re: Making a faxserver out of DSL on: August 26, 2014, 10:56:29 PM
It's tricky to get Apt working because DSL is based on such an old system. Even if you did get it to work, you'd be limited to an old version of the software you want to run. You need to use a package respository for Debian 3 "Woody", packages.debian.net is the official archive.

If the program isn't in the MyDSL respository, then the best option these days is to compile the software from source. Though you need to check that it, and its dependancies, will work with v. 2.4 of the Linux Kernel.

There's a guide to compiling software here (http://www.damnsmalllinux.org/wiki/creating_a_compressed_extension_from_source.html). You don't need to make a tar.gz package for the MyDSL respository, but you are encouraged to so that you can help others who want the program.

That page doesn't tell you how to set up a compiling environment. An easy way to do this is to first install the following packages from the MyDSL repository: gcc1-with-libs, gnu-utils, compile-3.3.5.

For making changes in DSL permanent, see the DSL Wiki pages on "Persistance" and "HDD Install". You'll need a HDD Install if you're going to compile software without making MyDSL extensions as well.
3  Damn Small Linux / HD Install / Re: "Loading sata_vsc.o..." on: August 09, 2014, 10:02:53 PM
Thought I'd brought out my CD pile for this purpose once before, looks like I did a similar list in this post (http://damnsmalllinux.org/forums/index.php?topic=838.msg1441#msg1441).

The ones I missed this time around are Plop Linux and TinyMe Linux. Both are on the fringe of Linux distro development, but I remember Plop is meant to be built from the ground up, so it could work where a lot of others don't (or the other way around).

Anyhow, good luck and do report back your results.
4  Damn Small Linux / Other Help Topics / Re: Android tethering on: August 04, 2014, 10:07:57 PM
Ah, right. I'm not into modern phones, so I thought you were asking how to connect your phone to the internet, not to a computer.

My mistake.
5  Damn Small Linux / HD Install / Re: "Loading sata_vsc.o..." on: August 03, 2014, 10:47:27 PM
I believe the problem with supporting recent hardware along with old examples from the 90s is that the modern Linux kernel has been stripped of much of the hardware support for the older systems. Additionally, its total size has grown.

The result is that in order to maintain a small size and good support for old hardware, DSL enevitably ends up getting left behind the pack as Linux marches forwards. As time goes on, fewer new developments in Linux software are able to be passed on to DSL - most apparent with the limited Firefox version.

However DSL-N was designed to counter these problems by presenting an alternative version of DSL that continued the same philisophy, but submitted to the need for newer software (particularly a newer version of the kernel, 2.6.x instead of 2.4.x). The problem is that this has seen a longer time without development than DSL, so in some ways DSL is still newer and both are still very far away from the current generation of Linux distributions.

SATA wise, DSL usually works, but the old drivers mean that you have to rely on BIOS designers playing by the same rules that they did a few years ago. I've actually never had a problem with DSL and SATA, but I usually use PCs that are a few years old anyway.

So practically speaking, I'd first start with DSL-N and see if it has the same problem (I've often found it to behave very differently in terms of hardware detection, for better or for worse). If that doesn't work, or you don't like DSL-N's older software and/or design, you can try these picks from my Live CD stack:

  • Puppy Linux - An actively developed distro for old hardware using a much newer kernel. Lots of versions and spin-offs, many of which can use mainstream package repos.
  • Puppy Linux Pulp - A little known spin-off that's also now rather dated development-wise (last I checked), but seems to have an ultra-light approach more like DSL.
  • Tiny Core - Done by Robert, who left DSL development some time ago. Uses a different approach by coming with minimal software as standard and requiring the manual addition of the particular software packages you desire
    . Uses its own package system like DSL though, so choice can be a bit limited if you don't want to compile.
  • Slitaz - I don't know too much about this one (except I used one PC for which this was the only Linux distro which would boot from CD), another low resource usage distro. Wide language support.
  • Knoppix - DSL is based on an early version of this. It runs quite light and pretty (often very) fast on PCs from the last ten years or so. It's what I install if I want a Linux that can run newer software (it can use Debian packages). Note that it's really meant just to be run from CD (though HDD installation usually goes alright).

Well there you go, hope it helps. Sorry it's such a long post.
6  Damn Small Linux / Other Help Topics / Re: Android tethering on: August 02, 2014, 03:46:51 AM
Unless you've managed to install Damn Small Linux on your phone, in which case I'd say you're pretty lucky if internet is the only thing not working, I'd say you'd be better finding a forum about Android phones.

You could also post in the "Water Cooler" section, but your chances of finding help probably make getting hit by a meteorite look like an normal lifetime hazard.
7  Damn Small Linux / HD Install / Re: "Loading sata_vsc.o..." on: August 02, 2014, 03:39:17 AM
In case you're still checking this topic, here are some anwsers:

I'm not sure of the exact age of the DSL SATA drivers, but they would be from 2008 at the latest, and probably much earlier. As is the usual line with DSL, the OS is designed to run on older hardware with the trade-off being that it doesn't readilly support many new systems. Its current, lets call it intermittent, development doesn't help this at all either.

Basically, the SATA drivers probably don't play well with your more modern motherboard BIOS because they were likely designed some time before it existed.

I did once install DSL on a machine which wouldn't recognise a SATA HDD until "IDE Emulation" was turned off in the BIOS (that's to say it didn't recognise it pretending to be an IDE drive). So there are all sorts of strange things that can go on.

If you install to hdb9, it should boot from hdb9 as long as GRUB is set up with the "kernel" path in the /boot/grub/menu.lst file pointing to /dev/hdb9. In theory the installation script should do this automatically, but it's the first thing to check if booting fails.

If you change the BIOS settings to use the HDD as a SATA device, the partition address will become /dev/sd?9 and the "kernel" line in menu.lst will need to be changed for DSL to boot.

I can't remember if it's impossible, but it would take some work to get DSL to boot from GRUB2 directly. When I needed to do this in the past, I was lazy and set up the GRUB in DSL (v. 0.91) on the DSL partition, then chainloaded it from GRUB2 like one would a Windows installation.

Actually now that I think of it, I did that the other way around and chainloaded GRUB2, but that was because DSL was installed first and I wanted to keep some menu options for booting it (the menu was disabled for GRUB2 so that one isn't even aware of the multi-step process).

I remember the HDD installation script asks you if you want to install a boot loader (in your case I would anwser "no" and do it manually to hdb9). I expect the frugal one does the same.
8  Damn Small Linux / User Feedback / Re: I have DSL installed on a Fujitsu Stylistic 1200. How to reset firefox size? on: August 02, 2014, 02:54:59 AM
If you do "firefox --help" and look under "Mozilla options", there are options "-height" and "-width" to specify window size.

So you just have to use the command "firefox -width <pixels> -height <pixels>" to start it with the size specified in pixels. The height should be a bit less than the screen resolution so that the window doesn't cover the task bar at the bottom.

You can put the full command in a menu item by editing "/home/dsl/.jwmrc", or make a script file with the command and create a link to it on the desktop.
9  Non-DSL Topics / water cooler / Re: personal spam filter? on: July 13, 2014, 12:50:41 AM
I looked but never found anything. Just had to wait it out (as I expect did you).
10  Damn Small Linux / Laptops / Re: How to find what's happening if DSL gives me "read error...-problem reading. on: July 13, 2014, 12:43:45 AM
The permissions errors are because some tasks must be done by the "root" user. Use the root terminal to execute commands (can be found in the Xshells menu of the DSL menu), or "emelfm as Super-User" which can be found in "Apps>Tools>Emelfm File Manager". You can also execute commands as root from a normal user terminal by preceding them with the "sudo" command, eg. "sudo nano /etc/fstab".

Extensions can be loaded by double clicking on them in Emelfm, or using the command "mydsl-load <extension name>". On a HDD install, ".dsl" and ".tar.gz" extensions will be permaently installed on the system while ".uci" and ".unc"  types will be gone at the next reboot. In a Frugal install, nothing stays. You can have them auto-load by placing them in a "mydsl" folder on a partition you specify in the menu.lst kernel line (see the "cheatcodes" page of the Wiki), or putting "mydsl-load" commands for each extension in the "/opt/bootlocal" file.

Did you get the floppy drive working, if you were only trying one disk it could have just gone bad.
11  Damn Small Linux / User Feedback / I can see clearly now the Spam has gone! on: July 13, 2014, 12:01:28 AM
Thanks John, I was giving up hope on the Forum.

Strange what its done to the forum statistics though.
12  Damn Small Linux / Laptops / Re: How to find what's happening if DSL gives me "read error...-problem reading. on: May 20, 2014, 10:39:00 PM
Hmm, strange. Perhaps try creating the two files (as root) and checking that the "nofstab" option isn't in your startup commands on the "kernel" line of /boot/grub/menu.lst, then restart and see if things work.

You can create fstab entries manually (search for guides online, there are plenty), but it probably wouldn't be practical if your machine has USB. It could also be that DSL is having trouble reading the spot on the disk with fstab (though I don't know why it wouldn't show up in a directory listing), try running fsck on the DSL partition.

You could look at the dmesg log (can be viewed in the "System Stats" window (in the DSL menu "System>System Stats")) to see that DSL is detecting the drives at all, they should be there with a short description (though the floppy drive will just say it's 1.44MB (unless it's an old DD type)).

For a short-term fix, you can tell Linux what to mount where directly with the "mount /dev/<device> <mountpoint>". For example your floppy drive could be mounted using "mount /dev/fd0 /mnt/auto/floppy". Or was that what hung the terminal?
13  Damn Small Linux / Laptops / Re: How to find what's happening if DSL gives me "read error...-problem reading. on: May 19, 2014, 09:21:11 PM
Have you tried reading the same partition of the drive from other Linux Distros? If it doesn't work with them, it might be a problem with the file system (run fsck) or the HDD itself.

I don't know of any better way to kill a process started with Emelfm than killing Emelfm itself. There's no command in the keyboard shortcuts list.

I don't fully understand why you want a list of terminal commands. in any case, you mount with the command "mount", unmount with the command "umount" and install MyDSL extensions with the command "MyDSL <extension name>". Look at mount --help for how to use the commands fully, but basically just put the path to the mount point after the command, eg. "mount /mnt/hda3" to mount partition hda3. If it says the entry isn't in fstab, that means the system hasn't automatically set up a partition to use with that mount point.
14  Damn Small Linux / Other Help Topics / Re: How can I install FLwriter on DSL 4.11.rc2? on: May 12, 2014, 11:55:26 PM
I believe the kernel has changed since those versions of DSL, so you'd likely run in to problems trying to get the compiled software from them to run on the latest DSL release.

Find the source release and compile it yourself. The page on making a tar.gz MyDSL extension in the DSL Wiki describes the basic process of compiling software. There are some extensions in the MyDSL respository with the software for a compiling environment.

If you can find a package for Debian 3 "woody", that could be installed on DSL too, but it doesn't seem to be in the Debian package archive (http://archive.debian.net).
15  MyDSL Extensions / Extension Development / Re: synchronal stopwatch on: April 25, 2014, 11:11:31 PM
OK, that makes more sense. As you mentioned the speed of your PC, I thought Avidemux might have been having trouble keeping the audio and video in sync at some stage. I suggested the other programs because some jobs could be done with them instead (cutting video, changing video specs, etc.).

Actually I'm not sure that a stopwatch would be the best method as any delay in the video wouldn't be accounted for so you'd have to rely on the video playback working perfectly (or at least being able to keep up with lag by dropping frames). VirtualDub might give you the video time in miliseconds, I'd have to check.

Might be possilbe to make a script to operate on Mplayer play time printed by the terminal program, I just don't know how.
Pages: [1] 2 3 ... 10
Powered by SMF 1.1.19 | SMF © 2013, Simple Machines
Mercury design by Bloc