Les Mikesell (lesmik...@gmail.com)

In case people don't understand what you mean by that, you can
simply drag things out of the gnome menus onto the desktop
where they become double-click launchers or onto the quick-launch
panel (by the firefox/evolution/OO icons) where they start with
a single click.  I've usually done that with the terminal icon
even on versions that had it on the right-click menu.

Now, does anyone know how to execute the gnome menu button
remotely?  I normally connect to several different machines
and would like to have access to their menus and be able to
launch any available program without having to run the rest
of the desktop remotely.

On Wed, 2006-05-10 at 17:48, Michael A. Peters wrote:

> One of the issues though with doing this (grrr) is the Fedora Trademark.
> To do it - all the Fedora artwork legally has to be removed and
> replaced.

Interesting - the equivalent to Centos but with fedora as the
base...

However if all you really want to do is become the expert who
decides what 'everything' means for some set of people that
might care about your opinion, couldn't you do that by
publishing the output of some invocation of 'rpm -q' in
a format that could be used directly by anyone's yum to
load up the same packages?

There is a lot of old documentation around that still says you
have to extract all the rpms into a common directory to do
a network install.   And it could be better: the boot sequence
has a timeout so if you walk away and aren't there at the
exactly the right time to enter 'linux askmethod' at the boot
prompt (and servers with a lot of RAM to test can take a long
time to get there) it bypasses the option and tries to install
from the CD's you didn't burn.   I'd rather see 'askmethod'
as the default, with the local CD as the default choice so
it's just one more keypress if you do use the CDs but you'd
always get your choice.

The installer does all the magic necessary.  Just download
the iso images to a directory under an nfs export and when
installing fill in the nfs server and the path to that directory.
The loopback mounts of the individual isos happen under
the covers during the install.

Thanks - but it looks like everything has to be on one server
for this to work.  I was hoping to let the menu select from
several servers for the actual kernel/initrd load so they
could be maintained separately.  Did I miss something or is
that not possible?

It's not /etc/hosts.  It is the system hostname, which you
can set with the hostname command or with the fedora GUI
system-config-network program.  Sendmail must be restarted to
pick up the new name.

On Wed, 2006-05-10 at 11:26, Ron Watson wrote:
> >
> By "setting your hostname" I was speaking not of the sendmail config,
> but of the hostname(1) cmd.

And on fedora systems, this will be set to whatever you
put in the Hostname: field under the DNS tab in the
system-config-network program.

How do you control which of those is loaded when you boot a new
client?  I'd like to do that at the client side - and have a
timeout/default to load the ltsp thin client instead of an
installer.

On Wed, 2006-05-10 at 07:58, Gilboa Davara wrote:
> >
>
> No need to burn the first CD. In the long run, it's much easier to setup
> a pxeboot/tftp setup and boot from the network...

Is there a way to do this that isn't version-specific?  With
the CDs I've always had to boot from the exact version
that I wanted to install and I normally have several
NFS-installable copies on line at once (different fedora's,
centos, k12tsp, etc.).  And I have a default network boot
for ltsp thin clients.  Is there a way to set up a network
grub boot or something similar that could give a menu for
the load wanted?

NFS is really the easy way to go if it isn't your first
linux install.  Just download the iso images to an nfs-exported
directory, burn only the first disk and boot from it with
'linux askmethod' at the boot prompt.  Then pick nfs as
the method and fill in the server / directory info.  

There is also an assortment of things to be found here:
http://www.tldp.org/tldp-redirect.php

I think you've forgotten the way they learn about these things
(which is not by avoiding installing them) and the fact that
they change daily.

The same thing happened to me although I kept the current kernel
and it worked after removing and re-installing kernel-devel
and kernel-smp-devel.  As far as I could tell the same versions
were re-installed but I might have missed something in the
process.