Mailing List
Home
Linux - General Red Hat Linux discussion list
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Installation - Getting started with Red Hat Linux
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 8.0 - Discussion of Red Hat Linux 8.0 (Psyche)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Red Hat Linux 7.1 - Discussion of Red Hat Linux 7.1 (Seawolf)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
• application/x mplayer2 plugin
• RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
• Command stream end of file while reading
• X Windows problem (xauth)
• Upgrading openoffice 1 1 rpm
• FTP: connection refused
• FTP: connection refused
• mount: /dev/cdrom: is not a valid block device
• Dell Precision 650, RedHat 9, no sound
• how to trace the cause resulting in the crash of bind server
• Virus on the list
• UNINSTALL RPM MYSQL
• usb pen drives: mounting as a user
• broadcom network interface
• make mrproper
• sendmail configuration on redhat
• Couldn 't open PID file /var/run/named/named pid Permission denied
• Promise 378 controller
• kernel 2 6 and /dev/sound/mixer not found
• Problem using up2date
• mrtg step by step howto/configuration for a newbie?
• Compiling and Installing Kernel 2 6
• Can 't locate module ppp0, can 't locate module ppp compress 21
• HOW I CAN MAKE BOOTABLE FLOPPY DISKET
• Lotus Notes under Wine
• /etc/security/limits conf question
• Intel E/1000 driver
• Command stream end of file while reading
• rpm database corrupt
• qla2300 modules
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Diskless cluster and up2date

Diskless cluster and up2date

2004-02-27       - By Alois Treindl

 Back
Reply:     1     2     3     4     5  

On Fri, 27 Feb 2004, David J. Bianco wrote:

> I hope not. This sounds like a royal pain. You 'd have to somehow figure
> out which files in each update RPM were changed and then move them to the
> diskless area.
>
> I 've recently started planning the migration of our diskless machines
> from 7.3 to RHEL3, and although I haven 't done this yet, I think the idea
> is that all the directories with binaries that might be patched should be
> shared with the server, and the only client-writable directories should be
> things like /tmp and parts of /var that wouldn 't normally have patchable
> things in them anyway.
>
> Also, I think that for diskless booting, you won 't need a /boot
> partition, so this part is moot. The kernels will be downloaded at boot time
> rather than being accessed from the /boot partition.
>

Well, there is a redhat configuration tool to configure diskless clients
in RHEL 3.

Diskless clients are a standard redhat supported feature on RHEL 3.

One can actually expect under 'installation support ' and under 'update
support ' from redhat, that up2date does all the necessary work to keep
all diskless configuration files (which include complete special copies of
/boot, of /ect, of /var) current.

What is the point of up2date and rpms, if the user has afterwards to find
out which files were changed? This stuff MUST be automatic, and I actually
think the Redhat is obliged to provide and support it, or else
they need to take 'diskless clients ' out of the RHEL feature list.

See also: http://www.redhat.com/software/rhel/features/
from which I quote:

New in Red Hat Enterprise Linux, Version 3
Introduced in September 2003, Red Hat Enterprise Linux, version 3,
includes a broad range of new features:
Diskless systems:
Supports deployment of diskless clients.


I would like an official Redhat statement on that matter.

Alois


--
Taroon-list mailing list
Taroon-list@(protected)
http://www.redhat.com/mailman/listinfo/taroon-list