Language Selection

English French German Italian Portuguese Spanish

DSL 2.1r1 on old Laptop

Filed under
Linux
Reviews
-s

The developers of Damn Small Linux have announced the availability of the first release candidate of version 2.1. My gentoo install is quite dated on my aging laptop, and due to speed and other certain hardware considerations (like a whiny harddrive after a couple hours of compiling), it isn't likely to be updated again. I decided to see if dsl could run on this ancient Dell laptop.

Damn Small Linux is a damn small linux distribution, literally. For those who don't know, it's a 50mb livecd that is also installable onto your harddrive or an usb key. It's a fully functional system consisting of an graphical interface featuring the fluxbox window manager and many useful applications and utilities/tools.

The Change log for 2.1r1 includes:
1. Improved SATA boot time support (see f3)
2. USB 2.0 boot time support fixed typo
3. Torsmo replaces asmem, wmcpuload, & wmnet to better support both window managers.
4. Ted replaces Flwriter
5. Updated xtdesk improved dragging when double click enabled.
6. New Icontool GUI controls many icon features.
7. Added missing tools section to jwm menu.

Well, the first test, to see if it would boot with only 80mb ram.

I needed to download and dd the bootfloppy img due to the fact that this laptop is so old, it doesn't support booting from the cdrom. How long before it's a fish sinker? Well, that may be inevitable, but it's not a fact today. My old laptop did in fact boot dsl on a p1 with only 80mb ram. However, (you knew there was a however, right?), the video/display wasn't very readable when just hitting enter at the boot prompt. I decided to reboot and try some of those fb modes the F2 options screen suggests is for laptops. Crossing my fingers I tried fb1024x768. When that didn't work, I tried fb800x600. That was the ticket. I was in. I was thrilled. I was comforted by the telltale "beep, beep" of the pcmcia network being activated (although it turned out to be short-lived). Then I was asked about which x server module to use, xvesa or xfbdev. I chose xfbdev and was asked about my lang and mouse. At the answering of those questions, X started and looked beautiful and my scroll ball mouse device worked too. Damn Small Linux scores again!

        

Fly in the ointment:

My old and commonly recognized pcmcia wireless network card (linksys wpc11 rev3 that uses orinoco) was incorrectly detected as some Bromax unsupported/unknown card. One can modprobe orinoco and it'd get loaded without error. Still no wlan or eth0 device was available. Also not correctly setup was my netgear FA411 wired pcmcia netcard (that uses 8390). However, we did have some luck with a 3Com/Megahertz 3CCFEM556B. So, whoops. One strike against. Have to, a laptop just isn't any fun if the wireless doesn't work. It's not just me, please see this post for confirmation.

Sound is another small issue. Actually it isn't. It wasn't correctly detected or setup, but in all fairness, it never is. It works fine in Linux, but I have to pass some specific options to the kernel for it to work. It's an old dell latitude XPIcd and I always have to use /sbin/modprobe sb io=0x230 irq=5 dma16=5. I can't tell you how long I spent finding that solution my first Linux install on this thing! Big Grin So, we'll give dsl the brownie point there.

But how would it perform on such a low resource system?

Well, overall, most excellent. Most light applications, like emelfm, Ted or xpaint opened within a few seconds. Dillo took about 9. Sylpheed required 3 or 4. However, mozilla took about 70 seconds to open and another 4 or 5 to render the dslos.com start page. It took about 6 second to render other sites at that point and there was a marked delay or unevenness (is that a word?) with scrolling. Of course, this isn't really a reflection on damn small, just an interesting note. Another thing, xmms was running at the time, which was requiring some cpu cycles to stream that default classical station it was playing. In addition, we're still running from the livecd at this point as well. I'd have to install Opera if I was going to install this onto my hard drive for sure, but given the fact that the pcmcia stuff is somewhat broken, I think I'll forgo the install and wait for the next rc.

        

Conclusion:

I found dsl to work rather well on this old laptop. Applications functioned well and looked quite nice, save mozilla. The video was great looking, the mouse device, cdrom and floppy worked fine of course, and the sound works with a bit of nudging. Some pcmcia cards work and some that should don't. The torsmo looked and worked great. I never did find that gui icontool in the menu (oh, ok, founnd it... hey, that's neato). In addition, I think there should be some kind of battery monitor. Once they sort out the pcmcia stuff, I'm sure it would perform much better from the harddrive.

        

Re: A wonderful review on DSL ?

atang1 wrote:

Its wonderful and tell tale DSL install.

Love your review of DSL.

Yeah, I'm going to soon replace gentoo with a binary distro and I think dsl will be the one.

Thanks for saying! I suffered with the "butterfly syndrome" as I hit submit, as I often do. I appreciate it. Smile

great review... UPDATE .....

UPDATE...

Added 128 mb of memory for a total of 160mb.

DSL now loads and works like a hot damm. Even found an older PCMCIA 3com network card and I had connectivity. Looks like the perfect distro for this laptop. Never would have beleived it if I hadn't tried it.

Nick

But tried it on a compaq presario 1200 with 32 meg mem. (k6 475 mhz processor)and it was next to useless. It booted up but took way too much time to get anything running.

Will try to upgrade the memory to 128m and try again

Nick

Great review but... Sorry for the duplicate...

DSL has lots of trouble on a compaq presario 1200 k6 475 with 32 m memory.

DSL boots up but just thrashes away continously. Got to find a 128 meg memory module to add or else its a doorstop.

nicsmr

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Leftovers: BSD

Security Leftovers

  • Stop using SHA1 encryption: It’s now completely unsafe, Google proves
    Security researchers have achieved the first real-world collision attack against the SHA-1 hash function, producing two different PDF files with the same SHA-1 signature. This shows that the algorithm's use for security-sensitive functions should be discontinued as soon as possible. SHA-1 (Secure Hash Algorithm 1) dates back to 1995 and has been known to be vulnerable to theoretical attacks since 2005. The U.S. National Institute of Standards and Technology has banned the use of SHA-1 by U.S. federal agencies since 2010, and digital certificate authorities have not been allowed to issue SHA-1-signed certificates since Jan. 1, 2016, although some exemptions have been made. However, despite these efforts to phase out the use of SHA-1 in some areas, the algorithm is still fairly widely used to validate credit card transactions, electronic documents, email PGP/GPG signatures, open-source software repositories, backups and software updates.
  • on pgp
    First and foremost I have to pay respect to PGP, it was an important weapon in the first cryptowar. It has helped many whistleblowers and dissidents. It is software with quite interesting history, if all the cryptograms could tell... PGP is also deeply misunderstood, it is a highly successful political tool. It was essential in getting crypto out to the people. In my view PGP is not dead, it's just old and misunderstood and needs to be retired in honor. However the world has changed from the internet happy times of the '90s, from a passive adversary to many active ones - with cheap commercially available malware as turn-key-solutions, intrusive apps, malware, NSLs, gag orders, etc.
  • Cloudflare’s Cloudbleed is the worst privacy leak in recent Internet history
    Cloudflare revealed today that, for months, all of its protected websites were potentially leaking private information across the Internet. Specifically, Cloudflare’s reverse proxies were dumping uninitialized memory; that is to say, bleeding private data. The issue, termed Cloudbleed by some (but not its discoverer Tavis Ormandy of Google Project Zero), is the greatest privacy leak of 2017 and the year has just started. For months, since 2016-09-22 by their own admission, CloudFlare has been leaking private information through Cloudbleed. Basically, random data from random sites (again, it’s worth mentioning that every site that used CloudFlare in the last half year should be considered to having fallen victim to this) would be randomly distributed across the open Internet, and then indefinitely cached along the way.
  • Serious Cloudflare bug exposed a potpourri of secret customer data
    Cloudflare, a service that helps optimize the security and performance of more than 5.5 million websites, warned customers today that a recently fixed software bug exposed a range of sensitive information that could have included passwords and cookies and tokens used to authenticate users. A combination of factors made the bug particularly severe. First, the leakage may have been active since September 22, nearly five months before it was discovered, although the greatest period of impact was from February 13 and February 18. Second, some of the highly sensitive data that was leaked was cached by Google and other search engines. The result was that for the entire time the bug was active, hackers had the ability to access the data in real-time by making Web requests to affected websites and to access some of the leaked data later by crafting queries on search engines. "The bug was serious because the leaked memory could contain private information and because it had been cached by search engines," Cloudflare CTO John Graham-Cumming wrote in a blog post published Thursday. "We are disclosing this problem now as we are satisfied that search engine caches have now been cleared of sensitive information. We have also not discovered any evidence of malicious exploits of the bug or other reports of its existence."

Security Leftovers

  • Change all the passwords (again)
    Looks like it is time to change all the passwords again. There’s a tiny little flaw in a CDN used … everywhere, it seems.
  • Today's leading causes of DDoS attacks [Ed: The so-called 'Internet of things' (crappy devices with identical passwords) is a mess; programmers to blame, not Linux]
    Of the most recent mega 100Gbps attacks in the last quarter, most of them were directly attributed to the Mirai botnet. The Mirai botnet works by exploiting the weak security on many Internet of Things (IoT) devices. The program finds its victims by constantly scanning the internet for IoT devices, which use factory default or hard-coded usernames and passwords.
  • How to Set Up An SSL Certificate on Your Website [via "Steps To Secure Your Website With An SSL Certificate"]
  • SHA-1 is dead, long live SHA-1!
    Unless you’ve been living under a rock, you heard that some researchers managed to create a SHA-1 collision. The short story as to why this matters is the whole purpose of a hashing algorithm is to make it impossible to generate collisions on purpose. Unfortunately though impossible things are usually also impossible so in reality we just make sure it’s really really hard to generate a collision. Thanks to Moore’s Law, hard things don’t stay hard forever. This is why MD5 had to go live on a farm out in the country, and we’re not allowed to see it anymore … because it’s having too much fun. SHA-1 will get to join it soon.
  • SHA1 collision via ASCII art
    Happy SHA1 collision day everybody! If you extract the differences between the good.pdf and bad.pdf attached to the paper, you'll find it all comes down to a small ~128 byte chunk of random-looking binary data that varies between the files.
  • PayThink Knowledge is power in fighting new Android attack bot
    Android users and apps have become a major part of payments and financial services, carrying an increased risk for web crime. It is estimated that there are 107.7 million Android Smartphone users in the U.S. who have downloaded more than 65 million apps from the Google App Store, and each one of them represents a smorgasbord of opportunity for hackers to steal user credentials and other information.
  • Red Hat: 'use after free' vulnerability found in Linux kernel's DCCP protocol IPV6 implementation
    Red Hat Product Security has published details of an "important" security vulnerability in the Linux kernel. The IPv6 implementation of the DCCP protocol means that it is possible for a local, unprivileged user to alter kernel memory and escalate their privileges. Known as the "use-after-free" flaw, CVE-2017-6074 affects a number of Red Hat products including Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 and Red Hat Openshift Online v2. Mitigating factors include the requirement for a potential attacker to have access to a local account on a machine, and for IPV6 to be enabled, but it is still something that will be of concern to Linux users. Describing the vulnerability, Red Hat says: "This flaw allows an attacker with an account on the local system to potentially elevate privileges. This class of flaw is commonly referred to as UAF (Use After Free.) Flaws of this nature are generally exploited by exercising a code path that accesses memory via a pointer that no longer references an in use allocation due to an earlier free() operation. In this specific issue, the flaw exists in the DCCP networking code and can be reached by a malicious actor with sufficient access to initiate a DCCP network connection on any local interface. Successful exploitation may result in crashing of the host kernel, potential execution of code in the context of the host kernel or other escalation of privilege by modifying kernel memory structures."

Android Leftovers