__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd

I usually only have AutoAddDevices. AFAIK, AllowEmptyInput is not necessary. man xorg.conf:

Quote:

Option "AllowEmptyInput" "boolean"
If enabled, don't add the standard keyboard and mouse drivers,
if there are no input devices in the config file. Enabled by
default if AutoAddDevices and AutoEnableDevices is enabled, oth-
erwise disabled. If AllowEmptyInput is on, devices using the
kbd, mouse or vmmouse driver are ignored.

Users may also have to enable/start the mouse daemon if they haven't already done so during/after the setup:

Quote:

Originally Posted by /etc/rc.conf

[...]
moused_enable="YES"
[...]

#/etc/rc.d/moused start

Finally, you may add -nolisten tcp to xinit if you don't need remote access to X.
You may also add an alias to your shell's rc file to save some typing:

I usually only have AutoAddDevices. AFAIK, AllowEmptyInput is not necessary.

I have just unscrewed my laptop (with FreeBSD) to make it little cleaner and to replace thermal grease, I will verify that after cleaning.

Quote:

Originally Posted by Beastie

Users may also have to enable/start the mouse daemon if they haven't already done so during/after the setup:

#/etc/rc.d/moused start

My fault, I assumed that everybody has moused enabled.

Quote:

Originally Posted by Beastie

, you may add -nolisten tcp to xinit if you don't need remote access to X.
You may also add an alias to your shell's rc file to save some typing:

Code:

alias xinit xinit -- -dpi 75 -nolisten tcp

Along with -br for black backgound (or -wr for white backgound) and -tst (disables testing extensions).

Thanks for adding your input mate.

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd

HAL will not be needed nor used by Xorg from the next release. All code relying on HAL is currently being removed from XOrg. Check the irc channel and developers mailing lists. I recently talked to one of core developers who came from the major XOrg conference.

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd

Anyway, I never used it. On all machines I've ever tried it, I had problems with optical drives. Automounting never worked and used to lock the drives and then the entire machine so bad, I had to power it down completely to recover (i.e. no power cycling possible). Options that were transfered from xorg.conf to HAL never worked anymore. As for polling every freaking piece of H/W every 2 seconds, argh!
Native drivers are like a billion times better and use way less reserved memory and processing power.

Let's hope DeviceKit (or any other replacement) will be just a *little bit* better. I'm not expecting too much, though.

According to several comparisions between hal and devicekit, hal is described as big monolithic shit that probes hardware every 2 seconds while devicekit is simple and modular blessing that heals all hal problems, we will have to wait to verify that, but IMHO we will be changing from one shit to another ... I just hope that I am wrong.

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd

That's what they always say every time they reimplement something for the hundredth time or ditch it for another "just-as-bad" (or at least "not-any-better") replacement.

*All* I hope for is that they continue to offer a choice between XYZ and nothing, and I'll only use native drivers as I've always done.
I personally never understood the use of such an additional layer.

Some form of Hardware Abstraction is usually a good idea when writing something like an X Server, just wait until HAL9000 starts speaking to your toaster oven :-P.

X developers sooner or later always sees the light of sanity... or meet an ALSA style straight jacket.

I've no beefs with PolicyKit or PackageKit, but no opinions on HAL, other then we've survived for years without it in X.Org, most of them perfectly fine. The changeover didn't screw me in the least, whatever's happened to anyone else.

I'm in the process of setting up NetBSD's pkgsrc on top of Slackware 13. I want to have an "old school" system without dbus/hal etc.

A lot of programs from pkgsrc have dbus as a non-optional dependency. I can't avoid not to install some of these. Firefox comes to my mind. Any idea how to install such programs without installing dbus/hal as well?

I'm in the process of setting up NetBSD's pkgsrc on top of Slackware 13. I want to have an "old school" system without dbus/hal etc.

A lot of programs from pkgsrc have dbus as a non-optional dependency. I can't avoid not to install some of these. Firefox comes to my mind. Any idea how to install such programs without installing dbus/hal as well?

I'm in the process of setting up NetBSD's pkgsrc on top of Slackware 13.

Slackware is still Linux, what You expected, that You could get away without hald or dbus these times with Linux?

If You find a way to get along without them, then let us know.

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd