M Harris wrote:
Most everything in
Linux is a text file "someplace". (unlike windoze which uses binaries, ini
files, and other hidden evil)
Taking that further: nearly everything in the whole system is from a
text file. And those files are freely available. Configs, as stated, but
also execu
Onsdag 14 februar 2007 18:44 skrev M Harris:
> On Wednesday 14 February 2007 11:22, M Harris wrote:
> > > - but I'd really like to be able to 100% tailor the KDE menu from the
> > > very beginning. Is this what you say you're able to do..
>
> This is of course theoretically possible---absolut
On Wednesday 14 February 2007 11:22, M Harris wrote:
> > - but I'd really like to be able to 100% tailor the KDE menu from the
> > very beginning. Is this what you say you're able to do..
This is of course theoretically possible---absolutely. Most everything
in
Linux is a text file "somep
On Wednesday 14 February 2007 03:46, Verner Kjærsgaard wrote:
> - but I'd really like to be able to 100% tailor the KDE menu from the very
> beginning. Is this what you say you're able to do..
>
> Quote: "When I was designing a user client-only desktop I started from
> scratch and built the desk wi
Mandag 12 februar 2007 22:23 skrev M Harris:
> On Sunday 11 February 2007 09:39, Verner Kjærsgaard wrote:
> > I don't want my users to be able to switch away from the traditional
> > SuSE/KDE menu system (i.e., select the new system).
>
> There are many ways of locking down the desktop (altho
On Sunday 11 February 2007 09:39, Verner Kjærsgaard wrote:
> I don't want my users to be able to switch away from the traditional
> SuSE/KDE menu system (i.e., select the new system).
There are many ways of locking down the desktop (although most folks on
this
list will kringe at the very
Hi list,
I don't want my users to be able to switch away from the traditional SuSE/KDE
menu system (i.e., select the new system).
How do I do that?
I suspect I'll need to put a "[$i]" into some KDE config file to lock it.
Which and where ?
--
