Login | Register
My pages Projects Community openCollabNet
Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

Reply to message

* = Required fields
* Subject
* Body
Send reply to
Author (directly in email)
Please type the letters in the image above.

Original message

Author theslack
Full name Jack Neely
Date 2007-03-21 07:29:33 PDT
Message 1) I don't really recal on the old 1.6 branch. That was a while ago.
Although, both the GUI and TUI should work there.

2) You can add any RPMs you like to the directories that make up your
channel in Current. All you need to do is re-run cadmin scan.


On 3/21/07, Berezovski, Vladimir <Vberezovski at nds dot com> wrote:
> Hi Jack . I seems that I succeeded to stabilize current server to work . So
> far with Sqlite option only . But it works .
> Now I've been dealing with building tree infrastructure for few RHEL clients
> . I predict there will be some questions indeed . At the moment two
> questions :
> 1 .When I register the client against current server the only option for
> that is to run up2date --register --nox command . The problem here is that
> registration cannot be done via GUI .Am I right ?
> 2. If it is possible to update current server with RPMs can be received from
> RHEL between updates ? I'm asking that since I used to build a channel for
> specific RHEL update . How can we add kernel updated version to the
> current's repository for example ? Simple copy does not help .
> for instance kernel version from update 4 for RHEL 4 is 2.6.9-42.EL
> whereas the latest version from errata is kernel-2.6.9-42.0.3.EL.i686.rpm ?
> Thanks . Vladimir
> ********************​********************​********************​********************​***
> This email message and any attachments thereto are intended only for use by
> the addressee(s) named above, and may contain legally privileged and/or
> confidential information. If the reader of this message is not the intended
> recipient, or the employee or agent responsible to deliver it to the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If you
> have received this communication in error, please immediately notify the
> postmaster at nds dot com and destroy the original message.
> ********************​********************​********************​********************​***