From: Haris Bogdanovi� on
> Please direct FUD elsewhere. Amazingly enough, many people use linux on
> modern and/or ancient hardware without trouble.

This is no "FUD". I just told my experience.
Now,for example, I have Fujitsu-Siemens v5535 laptop and there are no
drivers
for my graphic card (VIA somethnig), it works ok in virtual machine
(uses WINDOWS DRIVERS obviouslly). All drivers are generic (allmost all I
guess).
I have an audio interface M-Audio MobilePre USB for which there are NO
DRIVERS
for linux. Professional audio software like from Native Instruments is made
just for
Windows and Mac OS. So there is no problem in linux, linux is great,
but no software and drivers for it in lots of cases.
I


From: Pascal J. Bourguignon on
"Haris Bogdanovi�" <fbogdanovic(a)xnet.hr> writes:

>> Please direct FUD elsewhere. Amazingly enough, many people use linux on
>> modern and/or ancient hardware without trouble.
>
> This is no "FUD". I just told my experience.
> Now,for example, I have Fujitsu-Siemens v5535 laptop and there are no
> drivers
> for my graphic card (VIA somethnig)

Then why don't you write your own graphic card driver?

When I had a Dell Lattitude XP90ST laptop running NeXTSTEP 3.3, there
was no driver for the video chip either, so I wrote my own driver and
everybody was happy.

That's the point of opensource: you can solve your problem doing your
own programming.

Just contact the maker of your video chip asking for the
documentation, hardware makers are quite happy to provide you the
documentation of their chip if you mention that you will write a
driver for it.


--
__Pascal Bourguignon__
http://www.informatimago.com
From: Captain Obvious on
HB> I tried the same thing in clisp:

HB> (hunchentoot:start (make-instance 'hunchentoot:acceptor :port 8080))

HB> but it says that there is no package hunchentoot even though there is
HB> when I open emacs.

I would guess it cannot find .clisprc because of a different environment.
E.g. your Emacs might set HOME=c:\whatever, but you don't have it on naked
commandline, or something like that.

Anyway, you can load it explicitly:

clisp -i path\to\.clisprc

HB> I see that this probablly won't work, I will try cl-http or
HB> alegroserve.

Well, if you want a web server which works on CLISP, actually CLISP comes
with one internally.
You can run it this way:

(setq custom:*inspect-frontend* :http)
(inspect '(1 2 3))

This will show you an URL which you can type in browser and it will serve a
page.
(It can even automatically start a browser, by the way, if you say it to.)

Source code for this server is in src/inspect.lisp
But to load it you need to unlock system packages because it uses them a lot
(setf (ext:package-lock :ext) nil)

Once I've made a simple "Five in a Row" game with that web server.
Here it is: http://paste.lisp.org/display/99024
I guess it might be easier to understand than inspect.lisp because there is
less code.
It is not a good web server, and in fact it is quite buggy -- doesn't work
with Opera web browser, but works with Firefox.
(I mean my stripped-down version, probably src/inspect.lisp in current
version of CLISP is better.)

But nevertheless, it might be good to read this code if you want to study
how to make a web server in general.

If you want to do it, here are interesting parts:
with-html-output is a macro which formats HTML code and writes it into a
stream
(it also creates some local macros like with-tag to format HTML easier)
with-http-output is a macro which writes an object (normally, a string
created via with-html-output) into a stream together with HTTP headers
http-command waits for HTTP request, reads it and analyzes URL
serverloop creates listener socket and reads requests in a loop and
processes them

Then there are process-command and do-start-session functions which
implement application itself.

To be honest, this is not a best way to implement a web server and it is not
a best way to generate HTML output (I belive CL-WHO is better than
with-html-output in this code).

But it is relatively simple, give it a try.

To load this stuff in clisp, save code from paste into httpserve.lisp in the
directory with CLISP (or any other directory), then call it:

clisp -i httpserve.lisp
Calling function (serverloop) will create a server and print you an URL to
connect to it.
Then it will be processing requests until you hit link "Quit" with URL
/0/:q -- this signals server loop to finish.

HB> when programming in lisp. I would forget about windows long ago but
HB> nothing works
HB> in linux (hardware), no drivers, always some awkward ways of getting
HB> things to work,
HB> if possible at all.

Hm, that's strange -- last time I've checked, Ubuntu picked up all drivers
automatically, so I did not even need to install anything -- it just worked
While in Windows I needed to.
So, Ubuntu is now more automatic that Windows!
Except if you have some rare hardware, then you can find drivers for Windows
but for Ubuntu they simply do not exist.

But if you prefer Windows, virtual machine is a way to go. You can get
better video performance and integration if you run X server on Windows.
I work with it this way:
* on Windows I run cygwin/X (or Xming)
* then I configure Putty to use X forwarding
* I connect via Putty to my Linux VM, get a terminal, and run "emacs &"
* Emacs uses X server on Windows for output.
* So Emacs runs in a native Windows window, I can easily switch between
emacs and my Windows windows, copy/paste freely, etc.
* the only downside is that font support and font rendering might differ,
but perhaps current version of Xming supports good set of fonts already.

Another option is to run Emacs on Windows and connect to a CL instance
running in Linux, but then you need to setup remote access and stuff like
that, too much hassle to configure and doesn't always work well... But
sometimes I do that if I need to work with a remote server.

From: Captain Obvious on
??>> This is no "FUD". I just told my experience.
??>> Now,for example, I have Fujitsu-Siemens v5535 laptop and there are no
??>> drivers
??>> for my graphic card (VIA somethnig)

PJB> Then why don't you write your own graphic card driver?

:)

I guess if you don't need 3D acceleration, some generic VGA drivers will
just work.
If you need 3D acceleration, then driver writing is a bit hard...

PJB> When I had a Dell Lattitude XP90ST laptop running NeXTSTEP 3.3, there
PJB> was no driver for the video chip either, so I wrote my own driver and
PJB> everybody was happy.

Cool!
But what's about generic drivers? There is some common interface, no?

I guess video problems in Linux mostly happen when X auto-configuration
think it has a driver which will work with hardware, but in fact it is not
compatible and it fails miserably.
So you just need to say X explicitly to use generic driver.