1. Skip to Menu
  2. Skip to Content
  3. Skip to Footer>

พื้นที่ลงโฆษณา

Thin Client Server

พื้นที่ลงโฆษณา

Linux Authentication

พื้นที่ลงโฆษณา

Local YUM Repository

PDF Print E-mail

Written by Mr. Sontaya Photibut Saturday, 02 May 2009 14:33

Setting Local YUM Repo Server:

1. Install WebServer (apache2)
2. Install createrepo

Configure Apache:
$ vi /etc/apache2/conf.d/updates.conf

Alias /updates /backup/updates
<Directory /backup/updates>
     Options None
     AllowOverride None
     Order allow,deny
     Allow from all
</Directory>
<IfDefine SSL>
     SSLEngine off
</IfDefine>

Restart Apache:
$ rcapache2 restart

Install & Create Repo:
$ rpm -ivh createrepo-0.4.3-4.noarch.rpm
$ mkdir /backup/updates/sled10-sp2

Copy Source updated & Repo to new path:
$ cd /var/cache/zmd/web/files/nu.novell.com/repo/$RCE/SLED10-SP2-Updates/sled-10-i586
$ cp rpm -Rv /backup/updates/sled10-sp2/

Copy Source (sled10-sp2) from DVD:
$ cd /media/SLED10SP_001/suse/i586/
$ cp * -v /backup/updates/sled10-sp2/rpm/i586/

$ cd /backup/updates
$ chown wwwrun.www sled10-sp2 -R
$ chmod 775 /backup/updates/sled10-sp2/rpm/i586 -R

Create Repo:
$ createrepo /backup/updates/sled10-sp2
$ cd /backup/updates/sled10-sp2/repodata

Added is signing the "repomd.xml" file
$  gpg -a --detach-sign repomd.xml

Supply GPG key
$ gpg -a --export 06F46BD9 > repomd.xml.key

Set Up Clients Updates From The Local YUM Repo Server:

rug is the command line front end to access ZENworks Management Daemon (ZMD) You can list the sources of installation, and or delete.

ZENworks management daemon (ZMD) is a daemon written in C#

Yast package management  is package manager users libzypp but not ZMD.

Libzypp  is the new package/patch/pattern/product management library written in C++. Currently, it installs, upgrades and removes packages by running “rpm” on the command-line.

Zen Updater  zen-updater, zen-installer, and zen-remover is small applets written in Mono set of GUI frontends for zmd.
zypper is an easy to use command line package manager using the software package management library called libzypp.


Checking if zmd is running:
$ rug ping

ZMD 7.2.2, Copyright (C) 2007 Novell, Inc.
Started at 02/06/2009 18:00:41 (uptime: 0 days, 0 hours, 2 minutes)
RSS size: 26592
Network Connected: Yes
Running on Mono 1.2.2

OS Target: SUSE Linux Enterprise Desktop 10 (i586)

Module Name        | Description
-------------------+-------------------------------------------------
Inventory          | Software and Hardware inventory module for Linux
NetworkManager     | NetworkManager support
Package Management | Package Management module for Linux
ZENworks Server    | SOAP methods used by a ZENworks server
XML-RPC interface  | Export ZMD public interfaces over XML-RPC

If zmd isn't running.
$ rug ping
ERROR: ZMD does not appear to be running.


Adding a Service:
rug sa <repo_URL> <repo_description>

$ rug sa http://192.168.1.100/updates/sled10-sp2 -t yum updates-sled10-sp2

Check Service:
$ rug service-list
# | Status | Type | Name                                        | URI
--+--------+------+---------------------------------------------+---------------
1 | Active | ZYPP | SUSE Linux Enterprise Desktop 10 SP2 10.2-0 | cd:///?devi...
2 | Active | YUM  | updates-sled10-sp2                          | http://192....


Check Catalogs:
$ rug catalogs
Sub'd? | Name                                        | Service
-------+---------------------------------------------+--------------------------------------------
Yes    | SUSE Linux Enterprise Desktop 10 SP2 10.2-0 | SUSE Linux Enterprise Desktop 10 SP2 10.2-0
         | updates-sled10-sp2                          | updates-sled10-sp2


Verify Catalogs:
$ rug ca updates-sled10-sp2

Subscribe to catalogs:
$ rug subscribe updates-sled10-sp2
Subscribed to 'updates-sled10-sp2'


Check Package:
$ rug search firefox
S | Catalog                                     | Bundle | Name                        | Version      | Arch
--+---------------------------------------------+--------+-----------------------------+--------------+-----
v | SUSE Linux Enterprise Desktop 10 SP2 10.2-0 |        | beagle-firefox              | 0.2.18-78.9  | i586
  | SUSE Linux Enterprise Desktop 10 SP2 10.2-0 |        | mhtml-firefox               | 0.4-1.10     | i586
v | updates-sled10-sp2                          |        | MozillaFirefox              | 2.0.0.18-0.3 | i586
v | updates-sled10-sp2                          |        | MozillaFirefox              | 2.0.0.19-0.3 | i586
 2.0.0.18-0.5 | i586


Update the System:
$ rug up

Resolving Dependencies...

.
  openldap2-client 2.3.32-0.30 (http://192.168.1.100/updates/sled10-sp2)

  OpenOffice_org 3.0-0.4 (http://192.168.1.100/updates/sled10-sp2)

  OpenOffice_org-gnome 3.0-0.4 (http://192.168.1.100/updates/sled10-sp2)

  OpenOffice_org-nld 3.0-0.4 (http://192.168.1.100/updates/sled10-sp2)

  opensc 0.9.6-17.9 (http://192.168.1.100/updates/sled10-sp2)

  openssh 4.2p1-18.38.3 (http://192.168.1.100/updates/sled10-sp2)
.
.
Proceed with transaction? (y/N) y
End User License Agreement
ADOBE® SOFTWARE LICENSE AGREEMENT

NOTICE TO USER: PLEASE READ THIS CONTRACT CAREFULLY. BY USING, COPYING OR DISTRIBUTING ALL OR ANY PORTION OF THE ADOBE SOFTWARE ("SOFTWARE") YOU ACCEPT ALL THE TERMS AND CONDITIONS OF THIS AGREEMENT, INCLUDING, IN PARTICULAR THE LIMITATIONS ON: USE CONTAINED IN SECTION 2; TRANSFERABILITY IN SECTION 4; WARRANTY IN SECTION
7; AND LIABILITY IN SECTION 8. YOU AGREE THAT THIS AGREEMENT IS ENFORCEABLE LIKE ANY WRITTEN NEGOTIATED AGREEMENT SIGNED BY YOU. THIS AGREEMENT IS ENFORCEABLE AGAINST YOU AND ANY LEGAL ENTITY THAT OBTAINED THE SOFTWARE AND ON WHOSE BEHALF IT IS USED. IF YOU DO NOT AGREE, DO NOT USE THIS SOFTWARE.


<Shift+q>
Do you accept the license? [y/N] y
Downloading Packages...

Testing Upgrade MozillaFirefox, OpenOffice-3.0
$  rug install MozillaFirefox
$  rug install OpenOffice_org-3.0-0.4.i586

Resolving Dependencies...

The following packages will be installed:
  OpenOffice_org 3.0-0.4 (http://192.168.1.100/updates/sled10-sp2)

  OpenOffice_org-gnome 3.0-0.4 (http://192.168.1.100/updates/sled10-sp2)
    OpenOffice_org-gnome-3.0-0.4.i586[updates-sled10-sp2] needed by OpenOffice_org-3.0-0.4.i586[updates-sled10-sp2]

  OpenOffice_org-nld 3.0-0.4 (http://192.168.1.100/updates/sled10-sp2)
    OpenOffice_org-nld-3.0-0.4.i586[updates-sled10-sp2] needed by OpenOffice_org-3.0-0.4.i586[updates-sled10-sp2]


Proceed with transaction? (y/N) y

Downloading Packages...
                                                                                       100%, 8.7 MB/s

Procedures with transaction Finished.


Troubleshooting zmd

rug can't add new unsigned repositories:
ERROR: Could not add 'http://192.168.1.100/updates/sled10-sp2': Failed to parse XML metadata: Untrusted key 'Sontaya Photibut (admin) <email@domain>' (75DA497B06F46BD9)

Solution: run command (root)
$ rug set security-level checksum


Remote repo channel:
#rug sd <channel_number> or name
$rug sd updates-sled10-sp2

Setting system-wide ZMD Preferences:
$ rug get

4 preferences one might want to change
max-cache-age    (default 30 day)
refresh-interval    (default 24 hours)
run-transaction-test (default False)
security-level  (default signature)

check for updates every 4 hours:

$ rug set refresh-interval 14400
$ rug set refresh-interval-software 14400
$ rug set refresh-interval-hardware 14400
$ rug set refresh-interval-system 14400
$ rug set run-transaction-test True


Ref: http://www.softpanorama.org/Commercial_linuxes/Suse/Patching/rug.shtml
       http://wiki.suselinuxsupport.de/wikka.php?wakka=HowToAddReposUsingRug
       http://en.opensuse.org/Secure_Installation_Sources#The_.22repomd.22_or_.22YUM.22_format
Note path files: /var/cache/zmd/web/files/

END.
       
Comments (0)Add Comment

Write comment

security code
Write the displayed characters


busy
 

SUSE Linux Enterprise Cool Solutions

  • 2011 Novell Knowledge Partner nominations are now open!

    Nominations for 2011 Novell Knowledge Partners are now open! Wouldn't it be a shame if someone helpful in the forums, in the beta program, in Cool Solutions was denied an opportunity to become a Novell Knowledge Partner because nobody they helped took the time to nominate them? Is there someone you have seen that loves to share their knowledge and experience and takes the time out of THEIR busy day to help you? Do YOU take time out of your busy day to help others in the Novell communities? Nominations are being taken until the end of October for next year's Novell Knowledge Partners. If you have a favorite NKP that you feel should continue in the program, or know someone that would make a good candidate for admission to the program, please take a few minutes and nominate them. It would be appreciated. Go to http://support.novell.com/community/nkp.html to read more and submit a nomination. Thanks for taking the time to help us identify the people that help you the most.

  • supportconfig for Linux
    download url: 
    http://download.opensuse.org/repositories/Novell:/NTS/SLE_10/noarch/supportutils-1.20-18.2.noarch.rpm
    license: 
    GPLv2
    home page url: 
    http://en.opensuse.org/Supportutils

    Download Now

    The supportconfig RPM package has been renamed from ntsutils to supportutils.

    Installation Instructions

    1. Uninstall the ntsutils RPM package
    2. rpm -e ntsutils

    3. Download the supportutils package
    4. Install the RPM
    5. rpm -Uvh supportutils-1.20-18.2.noarch.rpm

    6. Run the supportconfig command as root; use -h or man page to see more options.
    7. supportconfig

    8. To view the information files, assuming the tarball filename is: /var/log/nts_host1_100125_1500.tbz

      cd /var/log
      tar jxf nts_host1_100125_1500.tbz
      cd nts_host1_100125_1500
      ls -l

    9. Perform a Basic Server Health Check with Supportconfig

    If you have difficulties installing the RPM, do the following:

    1. Change to the root of the file system
    2. cd /

    3. Download the supportutils package
    4. Extract the RPM files
    5. rpm2cpio supportutils-1.20-18.2.noarch.rpm | cpio -ivd

    6. The preferred method is to install the RPM using the rpm command, not rpm2cpio.

    Reporting Bugs

    Updates to Version 2.25-223:

    • Added a %B filename qualifier to normalize_base
    • Added running application pmap data to memory.txt
    • Fixed alsa-info.sh output collector
    • Added ctdb information to ha.txt
    • Fixed third party proc hang
    • Excludes kernel-source rpm validation from boot.txt
    • Added initrd output to boot.txt

    Updates to Version 2.25-216:

    • Fixed an additional hang issue with NSS volumes
    • Fixed validate_rpm error in scplugin.rc
    • Fixed a logger -b error

    Note: Detailed system information and logs are collected and organized in a manner that helps reduce service request resolution times. Private system information can be disclosed when using this tool. If this is a concern, please prune private data from the log files. Several startup options are available to exclude more sensitive information. Refer to the man page to see these options.

    AttachmentSize
    supportutils-1.20-18.2.noarch.rpm79.16 KB
  • Submit your Dilbert stories, and win prizes

    We all know that Dilbert isn't the only one with a pointy-haired man in his life. We're guessing you've had some close encounters with your own absurd managers. Managers who dictate new policies that fly in the face of reason. Crazy decisions made without any thought for unexpected consequences. Pronouncements unburdened by facts, yet defended to the death. (This is why Scott Adams is a billionaire today.)

    We thought it would be fun to see your Dilbert-esque stories dealing with strange ways that PHPs (pointy-haired people) have dealt with file management and file storage issues. We're launching a contest to find the best real-life 'storage insanity' story as told by our beloved IT professionals worldwide. Grand prize: a pass to BrainShare 2011 (Salt Lake City or EMEA)

    Here is how the contest works:

    1. Write an account of an absurd real-life incident that has something to do with file storage, file management, file archiving and restoration, etc.
    2. Email your story to coolguys@novell.com with "Dilbert" in the subject line, by November 30, 2010.
    3. We will edit all stories to remove any incriminating references to real people and real companies.
    4. You may enter more than one story. If you have a lot of good stories, we want to hear them all.
    5. We will publish all submissions that are fit to print.

    PRIZES

    * The first 100 published entrants will earn a limited-edition Dilbert t-shirt.
    * The Top 25 submissions will receive a Dilbert mug customized with the Novell comic strip. (These will be selected based on reader ratings, so get all your friends to rate your entry.)
    * The best entry, selected by a panel of judges, will earn a pass to BrainShare 2011.

    Note: Since these aren't really technical tips, we won't be giving Novell Rewards Points for published entries.

    PRIME THE PUMP
    Need some ideas?

  • From Gerald to Larry: One Down, Solaris to Go

    So I hear you are killing OpenSolaris. Admittedly it never was all that successful as an Open Source project, unlike the Linux Kernel, Apache, Firefox, GCC, Samba, and hundreds/thousands of others that make up openSUSE and SUSE Linux Enterprise.

    While I guess I can see your logic, I sympathize with those volunteers who had engaged. Luckily, there are communities around other operating systems which are a lot more open than OpenSolaris ever was, and I hope they will find a new home.

    Let's be clear on one thing, though. This is not the end of our quest; Solaris shall be next. We are taking share, and have for years. We run on a wider range of hardware than Solaris ever has or ever will. (Remind me, what happened to Solaris on System z? Just in case you wonder, 80% of System z workloads not running directly on IBM's own operating systems use SUSE Linux Enterprise Server.) Our portfolio of ISVs and applications is ever growing. We are cloud ready and readily found in various clouds, slim as in JeOS (Just Enough OS) and easy to build. No vendor lock in. Ah, and more brains and eyeballs than even you can afford. That's the power of Open Source, the power of Linux, the power of collaboration. And that's why I would not bet on the future of proprietary UNIX systems. Of which SUSE Linux Enterprise Server alone has already superseded several.

    Who is we, you may ask? It's those of us behind openSUSE, SUSE Linux Enterprise, our peers behind other distributions and thousands of upstream projects we participate in, contribute to, and leverage.

    Me, I am the Director of Product Management for the SUSE Linux Enterprise family, Novell's Appliances products (around SUSE Studio), and openSUSE. As time allows I am still contributing to various Open Source projects, and all opinions above are my own even if shared by many.

    d'Ehre, and watch out, Larry!

  • New Product Lifecycle Site is Live

    The new Product Support Lifecycle site is now live: http://support.novell.com/lifecycle/. Benefits include:

    • Faster search results.
    • Product nesting so you can easily view the lifecycle dates associated with products in a suite or bundle.
    • Ability to display additional notes for products

    Take a look and let us know what you think.

Sponsors List