Hi!
There's a little problem I can't solve myself.
When starting my FVWM-session (fvwm2), I'm generating my fvwmrc. As I
want to use the same configuration-files on different architectures
(Linux and Solaris mixed on Suns, PCs and IBM PowerPCs), I need to
generate them while starting my X. The graphics are completely mixed up,
so there's no way of guessing geometry or depth by CPU or OS. Builing a
list of all computers is no way of solving my problem, as there are too
many and new ones are often being baught.
I need # of bitplanes, height, width, OS, CPU and name of the system.
>From those, I build my rc. Offcourse, it's a nice thing on a fast
machine. But, as You may guess, on rather slow machines or lot's of
traffic on the nfs-server, FVWM is up before the rc has been finished.
Well, all modules, like FvwmM4, are being spawned.
Writing a xinitrc would include writing X-Tools for reading the display.
I don't want that, because that would mean five different binaries. And
will it be easy? I don't know any X.
What I'm doing at this time:
my .fvwmrc starts FvwmM4 and reads the file, I generate.
Generating a file means doing some nasty M4-things and reading my
definition-files. Out comes the main rc for this session.
This way, there's no problem when restarting. BTW: That's what I need to
do to read the new rc, except I logged in on the same architecture
before.
So. Can any cool reader help me? I know, it is not trivial. But there
has to be a way to solve it, has it?
Thanks in advance! Even if it's just a "No ***** way, man!"
--
Matthias Intemann
intemann_at_tzi.de
University of Bremen
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Aug 28 2000 - 17:15:14 BST