DSL Talk

I just want to say hi to everyone and I am enjoying DSL very much.

-lzy

I was thinking about my last entry and perhaps this one should have come first to make thing clearer. I was trying to show the use of sed for solving a problem. I wanted an example that was complex but still understandable. I was looking for a way to show how to explain the use of pattern and hold buffers in sed. I don't think that's what I got.

The pattern buffer contains the current line. It's what the "s" command performs its replacements to. The hold buffer is another buffer you can use. There are 5 commands (g G h H x) that move thing to and from the hold buffer. You can choose between appending to a buffer or overwriting the buffer. H appends the pattern buffer to the hold buffer, h overwrites the hold buffer with the pattern buffer, G appends the hold buffer to the pattern buffer, and g overwrites the pattern buffer with the hold buffer. x exchanges the hold and pattern buffers

I've been working on a sawfish window manager.dsl, and I made a .sawfish file that makes a few of the menu items, but I thought it would be nice to have a fluxbox menu converter (or at least an outline that others could use as well. I played around in sed and I got something that works so I thought I'd share the code, the results, and the sorrows.

The sawfish menu entries, like ion's, are in a different order than fluxbox's. The submenus must be fully defined before they are called by their owner. I looked at bash and C, but for whatever reason, I could see the answer in sed.

My basic strategy was to clean up the file a bit, then use the two buffers in sed to my advantage. Since sed is good at pattern matching, I thought I could use the next read [end] statement to tell me that the last [submenu] in the hold buffer was ready for writing. Then I would write that submenu out and replace everything in the hold buffer past that point with the call to the newly created submenu. Then when the next [end] comes around, you have everything set up. [exec] entries get reformatted and appended to the hold buffer.

I don't know if these blogs are the right place to ask questions?
I've managed to switch my keyboard layout to fi-latin1, which is great. The only problem is that I have to do this each time the system is restarted. How do I save my configuration changes?
By modifying filetool.lst? Modifying it how?
Also, the command startx wipes out all of Firefox's bookmarks, so I would have to add them everytime I change the keyboard layout. Not good.

I would also like to change the refresh rate, the size of the mouse cursor and the am/pm time display to a 24h clock. But these are all side-issues.

The "passed undefined mode number" problem is also quite annoying, and editing lilo.conf file doesen't help one bit: http://www.linuxquestions.org/questions/history/320298

Dear friends,
First of all, kudos to the DSL team for making a marvellous OS.I have the Live Cd Distro of Damn Small Linux.Its really cool.I am able to learn a lot of unix commands from the xterm.But alas,i aint able to compile any of the programs that i type in vi editor
(eg: i created a sample file a.c
in the $ prompt i gave :$cc a.c
cc : command not found.... was the reply.)
now is it possible to compile c progams in DSL?
pls tell me!
Thanks

I've installed DSL to a hard disk and it works great.

However, when I cloned the hard disk and put it in a PC with different hardware configurations it seems to be pretty random at getting the video card working correctly.

The DSL live CD or clean install finds the new hardware just fine ?

Is the hardware auto-detection turned off once it's installed onto a hard disk? If so how can I turn it back on.

Thanks for any help !

Mac
New Zealand.

Does anyone know how to enable virtual console by using ctrl alt Fx ? the three key combi?
like wat's mentioned here

1.1.0.4 Virtual Consoles

A useful feature of Linux is the virtual consoles. When you first log into a Linux system you are on the first ``virtual'' console of the system. On a standard Linux system you have eight virtual consoles. This is configurable, but we won't discuss that right now. Using the three key combination F(n), where F(n) is one of the function keys between F1 and F8, you can move between these virtual consoles. If you are in X when you do this, F7 becomes your X session, and you will see the error output from the X server, in virtual console 1 (VC1) when you go back to it. Virtual consoles allow you to do multiple things at the same time, in console mode.

Hi guys. I'm working in as a tech support guy for an ISP and most of our calls are from windows95-XP users. I get to have a few linux users. and most of the time, problems are within our network or the lines outside of their house, not with the linux machine. But believe me when I tell you that when a windows user calls in, 80% of the time, it's with windows (TCP/IP to corrupted NIC drivers) and not to mention clueless users.

anyway, im compiling a tech support manual for our account. i have a win98, me, 2000, and xp for 1 drive. as for my second drive, i have knoppix (hdd installed) and bayanihan linux.

(By Robert Shingledecker)

The timezone shoud be working for US zones.
If you don't do anything the default is EST and setting your BIOS to local
time is OK for most uses.

Now, if you want to try setting your timezone, must be in US, the others
were cut for space reasons. Try this at the first boot prompt:

dsl tz=US/Pacific

This will set the timezone to PST8PDT with an offset based on EST.

or use this

dsl tz=US/Pacific utc

Then the offest will be based on the hardware, BIOS, clock set to UTC time.

You can easily add these boot options during the execution mkmydsl script,

This is a list of scripts used in DSL as of version 1.5
The list does not include all scripts, but only those that
were created or modified specifically for DSL. The main
reason this was made is because I often refer to these
scripts to learn more about scripting myself, and to
better understand how DSL works. I thought it might also
be useful to others who are interested in learning the
details of DSL behavior. This list is probably not a full
representation of all DSL scripts, and will require edits.
Any additions and corrections are welcome.
Thanks goes out in particular to Robert Shingledecker,
whose hard work on most of these scripts has given DSL
life beyond that of a mere live CD.
-mikshaw