Hi guys,

The first problem I have has nothing to do with Slackware specifically(AFAIK). I would just like to know how to join wifi networks from the commandline. From what I have been reading, I would need to set the ESSID, channel, mode, key etc, all as separate iwconfig commands. Which is absurdly cumbersome.

Is there no simple way, using the given tools, to list and switch between networks? Or, is WICD the only way to do this?

The second problem, is that I have a UK keybaord. Pretty much the same as the US, just with an alt gr key and a few extra symbols. In the console, this works fine, as I chose a UK keymap during setup.

In X, not so. It still thinks it is a US keyboard. From what I have read, the way to fix this requires slight HAL configuration. Is this correct? In previous versions of slack(I last used v8), the keymap I chose at setup was honored in X.

Why is that no longer the case, and why must a cumbersome step be taken post install? (if that is the case).

@second problem:
as Pat writes in CHANGES_AND_HINTS.TXT.

Hi,

I use the above script to setup my wlan device when I need too.
You can use the 'wireless tools' to get all the information. I really don't like 'WICD'. 'WICD' causes me a lot of headaches and heart aches. So I just removed the package.

You could setup a script to sed through the information from iwconfig then pass the information or setup variables to pass but I'm not that lazy.

Well..., color me slightly embarrassed. I should have known better to check that.

The point remains though...why is this step not part of the install? Just curious.

Hi,

Josh, this is Slackware!

Read the documentation to allow you to see or understand the intrinsic needs for your system;

RELEASE_NOTES
CHANGES_AND_HINTS.TXT
UPGRADE.TXT

I suggest that you read through the other 'TXT' files on your media.

Hi,

To setup for a local keyboard you are given that choice during the install. Once you decide to setup 'X' then you must decide that configuration.

Hi Onebuck,

I'm actually overly familiar with Slackware, and checked out that file before installing. My keyboard only became an issue recently, and that file was not something I thought to check.

More of a case of not using Slack for so long, and knowing it was something to do with HAL, which has been around for quite a while.

Well, my point was that the keyboard setup for X should be done automatically or as part of the install, as it possible used to be.

Hi,

The 'X' setup is unique and really not something that should be setup vanilla. Sure you can setup a FB but the input devices are to much of a variant. The current 'X' initialization suits me fine. Except for that damn 'ATI' but that's not their problem or fault.

I believe you happen to fall into the group of a lucky few for previous versions. I don't see the problem with setting up the local devices by the user as to identify(tickle) local devices overall would be a task that would lead to even more problems. The user should be the one to setup keyboards, mice or whatever the human interface device would be.

I cannot see the need to change the installer to suit such a simple task. Especially one that has so many variables that are dictated by the variety of devices that a user would/could change at some point. I think the end user does have some responsibility when using Slackware and it should remain that way. Just my

I for one don't want Slackware to be a hold my hand distribution as that will lead to more confusion/instability.

I completely disagree.

Keep in mind, I am only referring to the keymap, and not the general X setup.

This is not a hard step to do, and would only mean copying a file based on what keymap was selected.

Considering a full install is recommended, and most users of slack will probably use X, it should definitely be included. It simply makes sense. It could be triggered only if X was selected to be installed...not to difficult at all.

A keymap is kind of independent of hardware, to an extent.

There should be an expectation that your keyboard in X will function the same as it does in the console and as you set it up. It is a trivial step to do this(just copying a file), so why should it not be included?

It is no more handholding then any other part of the setup, it is just an extra step to ensure consistency.

On another note, does anyone have insight relating to my wireless question?

Hi,

Send your recommendations to the Slackware team. I just feel the setup you are suggesting is not that difficult to setup to begin with. A user that selects 'KDE' for instance will go through the 'X' configurations for the desktop.

I think your opinion from a Slackware perspective is totally wrong. The variants that are required to setup various input/output devices are unique to the user's hardware. Those setting are left to the user to polish as they see necessary. If you want to tweak your system to do that then create another install then that's up to you. To streamline Slackware to suit oneself is OK with me but to change the whole to benefit one is not.

Slackware is Unique!

From a slackware perspective, it would actually make more sense to do the extra step and copy the Xmodmap or HAL file, so that the keyboard in X would match what was setup during install.

I don't know why you mention KDE...I was talking about X, which is independant from KDE, Gnome, XFCE, etc...

I am also not sure why you keep bringing up different hardware and devices.

I am talking about a keymap. You set it up during install for the console, so why not set it up for X at the same time, which only requires copying an extra file. It would not even require an extra step.

I think it is amazing how fragmented the community now is.

Hi,

As I said before contact the Slackware team.

I made the statement about 'KDE' as an example of setting the keyboard on the initial startup.

I know you setup the keymap for the console at the initial startup.

Does anyone have an idea about the wireless stuff?