User Feedback :: DSL FAQ Boot camp - Bring a helmet.
Everything you need to know about managing windows in Fluxbox can be found at http://fluxbox.sourceforge.net/docbook.php
note: Some things in the docs do not apply to fluxbox 0.1.x
It's not a bad idea to have at least a link under the fluxbox section of the documentation. I think the biggest problem is that this is a volunteer project, and creating/managing documentation is just plain tedious work.
I don't think it should be documented in the "getting started" page....DSL and its included applications are pretty much undocumented on the CD due to strict size limitation.
Anywho, to answer your question....
Alt+drag moves/resizes windows; left mouse moves, right mouse resizes.
You could also set these actions, as well as close, iconify, menu, maximize, etc., to hotkeys in /home/dsl/.fluxbox/keys
Q1:
I have DSL on my keydrive, however when I boot i get a text interface, how do I get a GUI?
A1:
type startx
Q2:
I got it to work, but since my moniter is old as crap I can only display 800X600. Is there any way I can change the resolution to that so i can use it?
A2:
while in bash, type xsetup.sh or on fluxbox right click on the desktop and goto system>xsetup
I'm a DSL newbie and inexperienced in linux.
After installing a DSL frugal install I wanted to change the lilo boot options
but couldn't find any documentation to describe the process.
I managed to work it out and thought it may be usefull if added to the FAQ.
Here is what I did. Please feel free to correct and improve.
Boot up frugal to the fluxbox desktop.
Open a shell window by right clicking and selecting Xshells>Root Access.
In the shell window, mount the HD partition with your DSL image.
ie SUDO MOUNT /dev/hda2 -w
now to edit the lilo.conf
i.e SUDO BEAVER /mnt/hda2/boot/lilo.conf
Use Edit>Toggle Readonly to be able to edit the file.
Make your changes then File>Save and then File> Exit
Now update the lilo boot loader
i.e. CHMOD 644 /mnt/hda2/boot/lilo.conf
LN -sf /mnt/hda2/boot /
SUDO LILO -C /mnt/hda2/boot/lilo.conf
Now exit the shell window by typing exit.
And then reboot.
Hope this help someone.
Regards b1m1
I am not sure why you posted some commands in CAPS.
With Linux being case sensitive it would be confusing to the newer user.
Also since you opened a root shell no need for repeating the sudo command.
Here is what I use:
1. Open a root shell Xhells>Root Access
2. mount /mnt/hda2
3. Now using your editor of choice... edit the following file for your boot options:
/mnt/hda2/boot/lilo.conf
4. ln -sf /mnt/hda2/boot /
5. lilo -C /mnt/hda2/boot/lilo.conf
6. reboot
Q: How do I save passwords between reboots?
A: Valid for DSL 1.2.1, frugal install
If you have a persistent /opt directory:
1) Open an Xterminal.
2) Switch to root access:
sudo su
3) Create an additional directory /pwd in your /opt folder:
mkdir /opt/pwd
4) Copy all password files into this directory:
cd /opt/pwd
cp -f /etc/passwd passwd
cp -f /etc/passwd- passwd-
cp -f /etc/group group
cp -f /etc/group- group-
cp -f /etc/shadow shadow
cp -f /etc/shadow- shadow-
cp -f /etc/gshadow gshadow
cp -f /etc/gshadow- gshadow-
5) Open the file /home/dsl/bootlocal.sh with any editor and add
the following lines:
/etc/init.d/ssh_addusers
cp -f /opt/pwd/passwd /etc/passwd
cp -f /opt/pwd/passwd- /etc/passwd-
cp -f /opt/pwd/group /etc/group
cp -f /opt/pwd/group- /etc/group-
cp -f /opt/pwd/shadow /etc/shadow
cp -f /opt/pwd/shadow- /etc/shadow-
cp -f /opt/pwd/gshadow /etc/gshadow
cp -f /opt/pwd/gshadow- /etc/gshadow-
Now you should be ready to use SSH for example.
Remark 1: Other, older and newer releases, might use a
different set of files. Look into /etc/init.d/ssh_addusers
for at least some of those files.
Remark 2: It is not possible to just add the password files to filetool.lst,
because when DSL does the restore operation, the destination files
in /etc might still be write protected. To make them (over-)writable,
the command ssh_addusers has to be executed in advance.
To execute a command, it should be placed in bootlocal.sh ,
which is restored as well, but the script itself is only executed
after the restore (when the copy operation for the password files
failed already).
Pio
Next Page...
original here.