Language Selection

English French German Italian Portuguese Spanish

Damn Small Linux - NOT

Filed under
Linux
Reviews
-s

Today brings another wonderful development in the world of Linux and open source software with the release of Damn Small Linux - Not. This is a distribution based on the famous Damn Small Linux, but adds welcome features and enhancements making it a more modern and complete operating sytem, yet still weights in at a meager 84mb. Tuxmachines took their alpha release for a livecd test drive and is here to report the findings.

As you can see the initial boot splash is a bit customized for this branch of the dsl distribution. The options appear basically the same as well as the actual boot process screen. It's quite a fast boot and one can find themselves in a full gui in right at a minute.

        

The desktop itself is almost the same as we encountered in DSL 2.3, except perhaps the lack of desktop icons. I myself have grown to prefer a less cluttered desktop, and as such welcome the tidying up. Otherwise, it's still the same lovely saturn wallpaper and Kharisma theme with torsmo, pager, and desklet.

It isn't really until you begin to explore the menus that you get a sense that something new is afoot. The first indication is a slightly rearranged menu. I think the new layout is much more logically constructed making applications easier to find. One might notice a few new players in the menus as well, or not. Mozilla is now the featured web browser, but the menu entry merely states "Web browser." Upon clicking this entry, it is revealed to be Mozilla 1.7.12 with the default homepage of dslos.com. Also ambigious, is an entry for IM Client. Executing this brings Gaim into sight. Gaim is a great replacement for their previous aol client as it features support for most im services available today. With further perusal, one might notice the new and strange-for-this-distro entry of Mplayer. Whoosh! Mplayer? Of course running this app revealed the first of my problems with dsl-n.

        

Damn Small Linux - Not comes with a newer 2.6.11 kernel as opposed to a 2.4 version found in the original DSL. This is to incorporate added support for more hardware configurations. However as with many debian based distros, its hardware detection fails to see all my partitions. But the problem with DSL-N lies in the area of filesystem support. Not only is auto detection a bit spotty, but support for reiser is completely missing. It isn't built into the kernel, nor is it included as a module. These conditions culminated into a lack of testing for the above mentioned addition of Mplayer at this time. If time permits, I may locate an ext2/3 partition in the upper sectors of my drive and copy some files there for testing. As it is, this is a definite faux paus. Saving space is one thing, but support for a few of the most popular filesystems is mandatory. In their defense, the kernel source is available through the DSL extension panel and this is an early alpha. Perhaps it's more of an oversight than a conscious decision.

    

In the MyDSL extension panel one can find many applications for installation. In this release we find a new category called Gtk2. Herein lies one of the main points of the new system. By allowing themselves a little more headroom, DSL can now include support for gtk2 applications making their distribution more up-to-date and usable for a larger range of users. Available for installation are applications such as firefox, gimp, gkrellm, and nvu. It was in this capacity that I encountered my second and third problems with DSL-N.

    

The lesser of the problems, and possibly not even the responsibity of the DSL crew, was in installing xfireworks. The app is not gtk2 related, yet none the less intriguing. It downloaded and installed just fine then placed a menu entry for my convenience. Clicking it did start the uber-cool xfirefox window background program. It could be used as a screensaver, but I think of it more as desktop enhancement in much the same ilk as xsnow. It performed wonderfully and ate no distinguishable cpu cycles or memory. The problem was discovered when I wished to turn it off. There is no menu entry to exit it or any gui way to stop it that I found. I issued a killall xfireworks and it stopped. However, the problem was I did not get my pretty saturn wallpaper back until going into the DSLpanel and reselecting it. This was a bit of a bummer, but certainly nothing serious.

    

However, it does lead to something I think is worth consideration. In trying to capture screenshots of the really pretty xfireworks, I wanted a program to view the 3 mb screendumps for review before feeling confident I had some nice shots. Gimp is listed in the Gtk2 MyDSL panel and I knew it could not only do the job, but would make for nice feature shots itself as well. It downloaded and installed just fine. It too gave me a menu entry and even a desktop icon. However it would not start. An error box was all I was given, complaining about not having a usable version of Freetype. More precisely it stated that the required version is 2.1.7 or later and the installed version is 2.1.6.

    

So all in all, I think DSL-N is a wonderful idea and is executed fairly well for an alpha. The desktop and menu improvements were welcome and hardware support was good. System performance and stability were still head and shoulders above the rest of the crowd. However I think an 84 mb download is a bit arbitrary. It's too big for a 64 meg usbkey, yet leaves plenty of room on the 128 mb versions. Update the freetype2 libs, add support for popular filesystems, put a coupla games back, and include scrot, pleeease.

Some listed features include:

1. Kernel 2.6.11 and modules
2. Mozilla Suite 1.7.12, browser,mail,irc,etc.
3. Mplayer 3.3.5 audio and video
4. Leafpad 0.7.9 editor/notepad
5. Abiword 2.2.7 wordprocessor
6. Gnumeric 1.4.3 spreadsheet
7. gTFP 2.0.18 ftp client
8. gaim 0.77 IM client
9. Xpdf 3.0.0 pdf viewer
10.Emelfm 0.9.2 file manager
11.Xpaint 2.7.6 paint program
12.Cups 1.1.14 printing
13.unionfs supported as an optional boot parameter
14.MyDSL system of extensions
15.Frugal Installs
16.USB Pendrive Install

Related Links:

why not Seamonkey?

Why not use Seamonkey rather than Mozilla Suite? It is more on par with Firefox but still is an integrated suite, so it saves room. Also it would be nice to include Ghostscript of Ghostview so more complex PDFs can be seen easier.

Comment viewing options

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

More in Tux Machines

Programming: WebAssembly, Mozilla GFX, Qt and Python

  • WebAssembly for speed and code reuse

    Imagine translating a non-web application, written in a high-level language, into a binary module ready for the web. This translation could be done without any change whatsoever to the non-web application's source code. A browser can download the newly translated module efficiently and execute the module in the sandbox. The executing web module can interact seamlessly with other web technologies—with JavaScript (JS) in particular. Welcome to WebAssembly. As befits a language with assembly in the name, WebAssembly is low-level. But this low-level character encourages optimization: the just-in-time (JIT) compiler of the browser's virtual machine can translate portable WebAssembly code into fast, platform-specific machine code. A WebAssembly module thereby becomes an executable suited for compute-bound tasks such as number crunching. Which high-level languages compile into WebAssembly? The list is growing, but the original candidates were C, C++, and Rust. Let's call these three the systems languages, as they are meant for systems programming and high-performance applications programming. The systems languages share two features that suit them for compilation into WebAssembly. The next section gets into the details, which sets up full code examples (in C and TypeScript) together with samples from WebAssembly's own text format language.

  • Mozilla GFX: moz://gfx newsletter #47

    Hi there! Time for another mozilla graphics newsletter. In the comments section of the previous newsletter, Michael asked about the relation between WebRender and WebGL, I’ll try give a short answer here. Both WebRender and WebGL need access to the GPU to do their work. At the moment both of them use the OpenGL API, either directly or through ANGLE which emulates OpenGL on top of D3D11. They, however, each work with their own OpenGL context. Frames produced with WebGL are sent to WebRender as texture handles. WebRender, at the API level, has a single entry point for images, video frames, canvases, in short for every grid of pixels in some flavor of RGB format, be them CPU-side buffers or already in GPU memory as is normally the case for WebGL. In order to share textures between separate OpenGL contexts we rely on platform-specific APIs such as EGLImage and DXGI. Beyond that there isn’t any fancy interaction between WebGL and WebRender. The latter sees the former as a image producer just like 2D canvases, video decoders and plain static images.

  • The Titler Revamp: QML Producer in the making

    At the beginning of this month, I started testing out the new producer as I had a good, rough structure for the producer code, and was only facing a few minor problems. Initially, I was unclear about how exactly the producer is going to be used by the titler so I took a small step back and spent some time figuring out how kdenlivetitle worked, which is the producer in use. Initially, I faced integration problems (which are the ones you’d normally expect) when I tried to make use of the QmlRenderer library for rendering and loading QML templates – and most of them were resolved by a simple refactoring of the QmlRenderer library source code. To give an example, the producer traditionally stores the QML template in global variables which is taken as a character pointer argument (which is, again, traditional C) The QmlRenderer lib takes a QUrl as its parameters for loading the Qml file, so to solve this problem all I had to do was to overload the loadQml() method with one which could accommodate the producer’s needs – which worked perfectly fine. As a consequence, I also had to compartmentalise (further) the rendering process so now we have 3 methods which go sequentially when we want to render something using the library ( initialiseRenderParams( ) -> prepareRenderer( ) -> renderQml( ) ) [...] The problem was resolved (thank you JB) finally and it was not due to OpenGL but it was simply because I hadn’t created an QApplication for the producer (which is necessary for qt producers). The whole month’s been a steep curve, definitely not easy, but, I enjoyed it! Right now, I have a producer which is, now, almost complete and with a little more tweaking, will be put to use, hopefully. I’m still facing a few minor issues which I hope to resolve soon and get a working producer. Once we get that, I can start work on the Kdenlive side. Let’s hope for the best!

  • How to Make a Discord Bot in Python

    In a world where video games are so important to so many people, communication and community around games are vital. Discord offers both of those and more in one well-designed package. In this tutorial, you’ll learn how to make a Discord bot in Python so that you can make the most of this fantastic platform.

  • Qt Visual Studio Tools 2.4 RC Released

    The Visual Studio Project System is widely used as the build system of choice for C++ projects in VS. Under the hood, MSBuild provides the project file format and build framework. The Qt VS Tools make use of the extensibility of MSBuild to provide design-time and build-time integration of Qt in VS projects — toward the end of the post we have a closer look at how that integration works and what changed in the new release. Up to this point, the Qt VS Tools extension managed its own project settings in an isolated manner. This approach prevented the integration of Qt in Visual Studio to fully benefit from the features of VS projects and MSBuild. Significantly, it was not possible to have Qt settings vary according to the build configuration (e.g. having a different list of selected Qt modules for different configurations), including Qt itself: only one version/build of Qt could be selected and would apply to all configurations, a significant drawback in the case of multi-platform projects. Another important limitation that users of the Qt VS Tools have reported is the lack of support for importing Qt-related settings from shared property sheet files. This feature allows settings in VS projects to be shared within a team or organization, thus providing a single source for that information. Up to now, this was not possible to do with settings managed by the Qt VS Tools.

Screenshots/Screencasts: 10 GNU/Linux Distros (Screenshots) and New Screencast/Video of Endeavour OS 2019.08.17

  • 10 Linux distros: From different to dangerous

    One of the great benefits of Linux is the ability to roll your own. Throughout the years, individuals, organizations, and even nation states have done just that. In this gallery, we're going to showcase some of those distros. Be careful, though. You may not want to load these, or if you do, put them in isolated VMs. We're not kidding when we say they could be dangerous.

  • Endeavour OS 2019.08.17 Run Through

    In this video, we are looking at Endeavour OS 2019.08.17.

A Cycle of Renewal, Broken: How Big Tech and Big Media Abuse Copyright Law to Slay Competition

In 1950, a television salesman named Robert Tarlton put together a consortium of TV merchants in the town of Lansford, Pennsylvania to erect an antenna tall enough to pull down signals from Philadelphia, about 90 miles to the southeast. The antenna connected to a web of cables that the consortium strung up and down the streets of Lansford, bringing big-city TV to their customers — and making TV ownership for Lansfordites far more attractive. Though hobbyists had been jury-rigging their own "community antenna television" networks since 1948, no one had ever tried to go into business with such an operation. The first commercial cable TV company was born. The rise of cable over the following years kicked off decades of political controversy over whether the cable operators should be allowed to stay in business, seeing as they were retransmitting broadcast signals without payment or permission and collecting money for the service. Broadcasters took a dim view of people using their signals without permission, which is a little rich, given that the broadcasting industry itself owed its existence to the ability to play sound recordings over the air without permission or payment. The FCC brokered a series of compromises in the years that followed, coming up with complex rules governing which signals a cable operator could retransmit, which ones they must retransmit, and how much all this would cost. The end result was a second way to get TV, one that made peace with—and grew alongside—broadcasters, eventually coming to dominate how we get cable TV in our homes. By 1976, cable and broadcasters joined forces to fight a new technology: home video recorders, starting with Sony's Betamax recorders. In the eyes of the cable operators, broadcasters, and movie studios, these were as illegitimate as the playing of records over the air had been, or as retransmitting those broadcasts over cable had been. Lawsuits over the VCR continued for the next eight years. In 1984, the Supreme Court finally weighed in, legalizing the VCR, and finding that new technologies were not illegal under copyright law if they were "capable of substantial noninfringing uses." Read more

Software, HowTos and Storage

  • Pause Music When Locking The Screen And Resume On Unlock For Spotify, Rhythmbox, Others

    When you lock your computer screen (without suspending the system), most desktop audio players continue playback in the background, sometimes not emitting any sound ¹. Due to this you may unintentionally skip parts of podcasts or songs in a playlist, etc. Enter pause-on-lock, a Bash script that pauses your music player when you lock the screen and resumes playback once the screen is unlocked. pause-on-lock works on Unity, GNOME, Cinnamon and MATE desktop environments, and by default it supports Spotify and Rhythmbox. With the help of playerctl (a command line controller for controlling media players that support the MPRIS D-Bus interface), this script can extend its supported music players to many others, including Audacious, VLC, Cmus, and others.

  • Easy Way to Screen Mirroring Android on Ubuntu!

    Screen Mirroring is one of the features found on smartphones, one of which is on Android. This feature serves to display the smartphone to a computer. This is very useful for example when used for demo applications that you make, or maybe for other things related to smartphones. In Ubuntu, we can do screen mirroring with applications available on Android, for example is AirDroid which can be used for screen mirroring through a browser. But I feel less optimal when using this instant method. Because there is a lag between activity on the smartphone and on the monitor screen on the computer, and the results are less than optimal. What might be the cause because it is opened through a browser and uses wi-fi? (Personal question). I am looking for another application for screen mirroring on Ubuntu, and one of the very good applications is Scrcpy. This application can be used for screen mirroring without a root device.

  • Command line quick tips: Searching with grep
  • How to Install Cezerin on Debian 9
  • How to Create a Bootable USB Stick from the Ubuntu Terminal
  • How to Install Git on Debian 10
  • How to Copy/Move a Docker Container to Another Host
  • Six practical use cases for Nmap
  • The Next Stage of Flash Storage: Computational Storage
  • NAS upgrade

    At some point in the future I hope to spend a little bit of time on the software side of things, as some of the features of my set up are no longer working as they should: I can't remote-decrypt the main disk via SSH on boot, and the first run of any backup fails due to some kind of race condition in the systemd unit dependencies. (The first attempt does not correctly mount the backup partition; the second attempt always succeeds).

  • Storage Concepts And Technologies Explained In Detail