Usage

Virtual Terminals

There are 3 virtual terminals (fewer than most distros, to save memory). You can cycle between them with L_ALT + LEFT/RIGHT keys.

Xvesa

Running startx from the LiveCD will run a script asking for your X config parameters. jwm and icewm are installed by default. Only PS/2 and Serial (COM1/COM2) mice are supported by default, but USB mice can be enabled by passing usbhid on the kernel command line.

Any additional options passed to startx will in turn be passed to Xvesa. For example, you could override the screen mode with startx -mode 0x011A (run Xvesa -listmodes to get a list of supported settings). Note the script will still prompt for a resolution/depth, but if you provide -mode, any resolution you specify will be ignored.

After installing to the HDD, startx will automatically save your X configuration choices in /etc/Xconfig. If you need to adjust your configuration, edit that file; you can also delete the file entirely and re-run startx to generate a new config. Running NOSAVEX=true startx will run the script without saving your chosen config, even on an HDD installation.

When prompted for a window manager, you can specify any command you want - for example, startkde or gnome-session (the script does not list all installed window managers)

Gimp

Gimp wants to load all of its Pattern files into RAM at startup. The version of Gimp shipped with BasicLinux includes 10MB of pattern files. Thus, no system with less than 12MB of RAM stands a chance of running Gimp out of the box.

To remove this requirement, all of the pattern files have been moved onto a disk image. By default, Gimp will see an empty patterns/ directory, and will function within 8MB of RAM. If you have more than 12MB of RAM and want to use patterns in Gimp, you can run:

On a hard drive installation, you could then copy only the patterns you want to ~/.gimp/patterns and unmount the disk image. This would conserve RAM while allowing you to still use the patterns feature.

glibc2 and Opera

BasicLinux documentation indicates that Opera 8 will work with BasicLinux, if you first install the glibc2 packages from Slackware 9. The two library packages are in LiveCD/extras/slackware-9.0.

Note that as of Beta 1 Revision 4, Opera is fully untested, and may not be compatible.

Opera 8.54 has been found! A mirror of all of the Opera Linux builds for versions 7-9 that I found is included in the repo in /contrib/opera and 8.54 is included on the LiveCD at LiveCD/extra/opera8.tbz

Unfortunately, I have been unable to locate a copy of Opera 8 for Linux. I have included Opera 7.54 instead. It is not yet tested.

If you find Opera 8 for Linux, statically linked for Qt (opera-8.xx-YYYYMMDD-static-qt-i386.tar.gz) please open an Issue and let me know.

See the BasicLinux documentation on-disc (LiveCD/docs) for more info.

Java

The ancient JDK 1.1.7 for Solaris (including/compatible with JRE 1.1), ported by the Blackdown `java-linux` porting team was provided in the original Slackware 4.0 contrib repo. The package kinda works as-is, but it includes "helpful" wrapper scripts which attempt to automatically set the JAVA_HOME, CLASSPATH, and LD_LIBRARY_PATH variables appropriately. They manage OK for CLASSPATH, but not so much for the others.

The problem is, these scripts don't work with some Busybox builtins, like basename and dirname. Even when I install the Slack 4 versions of shell utilities, it doesn't fully work.

I've modified the scripts to work well with BasicLinux. I've also added a manfile (run man java for info), and two examples:

hellorld which is a simple [verbose] hello world program to verify Java runs (source in /usr/local/java/examples/Hellorld.java)

javademo which is an X11 demo app pulled from the upstream JDK 1.1 package

My package will live on the liveCD in /packages/contrib/jdk117.tgz while the unmodified original distribution will live at /contrib/java/original in the repo. My package should work on BasicLinux 3 floppy-based installs as well.

Samba

The default smb.conf is set to share the entire root filesystem, unprotected, to any guest user with no password. Utterly insecure, but in line with the BasicLinux principle of being DOS-like and offering maximal "rescue disc" potential. This share is accessible from \\BasicLinux\baslin or \\<IP ADDRESS>\baslin

Unfortunately, the version of Samba shipped with BasicLinux is very old (2.0.3) which does not support SMB2 (not its fault, it hadn't been invented yet). SMB2 is the minimum required protocol for modern clients (Samba 4, Windows 10). For reasons unknown, Windows XP seems to be reluctant to connect as well. So SMB is likely not the best way to access your BasicLinux host.

On the plus side, smbclient works fine for an FTP-like SMB interface. Connecting to RetroNAS (Samba 4.17) from BasicLinux succeeds, but is limited to the older smbfs 2GB file limits.

or

Even better, smbmount works to mount SMB shares as Linux filesystems. The mount -t smbfs syntax is mysteriously broken, but the following works:

I have to install the nls_cp437 codepage (and smbfs) first:

This is how I find BasicLinux-LCARS to be most useful: I can mount my RetroNAS instance, and dd a complete vintage HDD over LAN. Slow, but so far very reliable.