I installed DSL, then did apt update, apt upgrade. This caused Terminal to stop working. (Or at least there's nothing visible on the desktop; maybe it's doing something I can't see.)

After installation (and before upgrading), conky says I'm using 80 MB of RAM, but free says I'm using 202 MB (whch is still very little, of course).

DSL 2024 works reasonably well on my Aspire One 522, with a two-core AMD C-50 APU and 2 GB of RAM (upgraded from 1 GB, with 256 MB reserved for video).

my wifi (ralink rt3062 doesn't work i use antix 23 but i have to use the dvd iso sadly.

Web "Brawsers" is a typo (not in the main menu, but under "Term Apps").

I am still on the hunt for potential candidates for removal.  Please post if you have any suggestions.  Please keep in mind that the target of this project is to serve older hardware.

As the title says. I used 

   
I wrote working and not running ;-)
Starting from live-cd took almost 10mins.
Installation on hdd took app. 20mins. (40GB - probably 20+ years old).

Starting from hdd than took app. 3mins.

It is usable - but a bit slow.
Not going to install and try firefox ;-)

A still have the advertising paper from this beast.
3999,-
for 128MB Ram and Win98SE.

Have fun.

Hi there,


I installed DSL on a SSD which I put in an about 15 yrs old Acer Aspire (2GB RAM).

Eveything is working, but the booting process needs more than 10 minutes. No error messages. 
Any suggestions what could go wrong or where I can get more information about this problem?

thx in advance

IMHO - DSL as-is .. is just another in a already fully-fluxed arena (Fatdog, Puppy ...etc.).

Better ... and simpler, would be a 'small' similar to my own. A vmlinuz with integral intiramfs, 25MB filesize, where all my modules/firmware are built into the kernel and the initramfs contains just enough to boot to a vesa/simpledrm framebuffer (very generic), wifi/eth net connect, alsa/sndio and has ssh/vnc. Very portable, many devices support vesa and can boot provided secure-boot is disabled, boots in a second, ssh/vnc connects in a couple more seconds, and drops you into a full gui desktop that may be running chrome to view youtubes ... whatever, and has the appearance of running at the net/cpu speed of whatever you vnc into.

Bloat the kernel, to include a broader range of device support, and the size increase is still relatively small. Perhaps a 50MB vmlinuz filesize (assuming xz compressed).

Booting in a second, dropping into a full gui desktop (libre office, chrome ...etc.) in a couple of seconds more - resuming where you left off, with a look-n-feel of running at whatever the server runs at ... can be impressive, and usable enough to retain users - I use mine as my primary choice of boot. As my ISP caps upload speeds to 20Mbs (2.5MB/sec) I've set a default of using 12 frames per second, 16 bit color depth ... and that still looks/feels fine, whilst typically seeing 2MB/sec (16Mbs) data rates when viewing a youtube. I also have a vncserver on my phone (termux (not rooted) based). The home server is a i5/nvidia/ethernet box, so for instance when out and about and vnc'd into that a online-internet-speed-test will appear to provide a 140Mbs download rate, as will high resolution videos/youtubes appear to play OK (but in reality where many frames are actually skipped/dropped).

And that transfers the overhead of having to maintain repos, as that's then the servers responsibility. I often have multiple vnc's running concurrently, windows, mac, linux, bsd, android ... whatever, according to whichever program/app is appropriate at the time.

As-is I see DSL being just a another novelty, try once for fun, maybe then just gathers dust or is removed. Missing out on a better market-share at the lower terminal-server style end that DSL could have thrown itself into. But fair enough, DSL could still be setup/used in a similar vein to my framebuffer boot, load Xvnc for a X session, run vncviewer in that to connect to a remote vncserver, and framebuffer vnc into that local Xvnc session (were all elements are set to 16 bit color depth, and the servers are set to 12 frames/second).

JMHO. Not intended as a criticism, congratulations to the DSL team for their hard work/efforts in reviving DSL.

The current alpha comes with xbacklight installed, which is a program for controlling backlight brightness. xbacklight does not work on my Eee PC 1001PX or on my ThinkPad T400. I have found a working replacement in brightnessctl. I would like to request adding it.

My impression is that xbacklight has poor compatibility. The Arch wiki seems to agree. So I would actually suggest removing xbacklight and only shipping brightnessctl.

Upon boot I see the ConnMan connection app with my wifi detected.  As I had to reboot my PC to get back online, this note is done from a  memory that might not be accurate.  Network manager usually detects possible network names followed by a window to enter the network password.  DSL is not going to be too popular if the wifi setup isn't simple, easily understood and quickly executed.

My help request is a walk-through for the ConnMan Tray.  I can see advantages of ConnMan. This is the first Linux distro that I've run into that uses it.  Sell me on it!

Need to put the ConnMan info in the FAQ folder. 

 I would also include the user name is "demo" with password "demo" and "root" is the password for the superuser root. If the user wants to play in the terminal and use connmanctl commands, they will soon need the passwords.

Don't mean to be a grump and feel free to flame me if I should have found the info somewhere in a help section.