I just completed my first 5.2 install. For 'completeness' I 'tested out' yum update.
Guess what? For this minimum install, there were 43Mb of updates to download.
So I went over to my local repo server and setup a /centos/5.2/updates directory and started the rsync to get all the updates:
155 files taking up 943Mb. Already. Wow! Perhaps something to do with the initial build problem? But anyone that does an install from the CDs/DVD and includes OpenOffice, then turns around and updates, is in for a scary supprise. Yet another reason for the local repos....
Robert Moskowitz wrote:
I just completed my first 5.2 install. For 'completeness' I 'tested out' yum update.
Guess what? For this minimum install, there were 43Mb of updates to download.
So I went over to my local repo server and setup a /centos/5.2/updates directory and started the rsync to get all the updates:
155 files taking up 943Mb. Already. Wow! Perhaps something to do with the initial build problem? But anyone that does an install from the CDs/DVD and includes OpenOffice, then turns around and updates, is in for a scary supprise. Yet another reason for the local repos....
I thought the 'updates' directory contained updates for everything from 5.0 forward ?
John R Pierce wrote:
Robert Moskowitz wrote:
I just completed my first 5.2 install. For 'completeness' I 'tested out' yum update.
Guess what? For this minimum install, there were 43Mb of updates to download.
So I went over to my local repo server and setup a /centos/5.2/updates directory and started the rsync to get all the updates:
155 files taking up 943Mb. Already. Wow! Perhaps something to do with the initial build problem? But anyone that does an install from the CDs/DVD and includes OpenOffice, then turns around and updates, is in for a scary supprise. Yet another reason for the local repos....
I thought the 'updates' directory contained updates for everything from 5.0 forward ?
There are only 2 rpms dated Jun 18, all the rest are more recent So I would say they are all updates to 5.2. Plus the way that Johnny maintains the symlink, he would change over the the 5.2 updates the same time he changes over to the 5.2 base.
Ralph Angenendt wrote:
John R Pierce wrote:
I thought the 'updates' directory contained updates for everything from 5.0 forward ?
No.
updates/ gets emptied out on a new point release and then is rebased on the os/ tree for the new release.
Right ... BUT, base + updates are all the latest RPMS in the release, so no one should think that is a problem.
Johnny Hughes wrote:
Ralph Angenendt wrote:
John R Pierce wrote:
I thought the 'updates' directory contained updates for everything from 5.0 forward ?
No.
updates/ gets emptied out on a new point release and then is rebased on the os/ tree for the new release.
Right ... BUT, base + updates are all the latest RPMS in the release, so no one should think that is a problem.
So how can you do an install based on all the latest?
Can I create a /centos/install/i386 directory structure where I first rsync over the /centos/os/i386, then the /centos/update/i386, and then keep it current from both from the Centos mirrors?
I would guess I would have to run createrepo myself as neither the base nor the update repodata would be right for the combined directory. I have quite a few installs to do still this week. I had been holding off on some builds, waiting for 5.2 to do them 'clean'.
Robert Moskowitz wrote:
updates/ gets emptied out on a new point release and then is rebased on the os/ tree for the new release.
Right ... BUT, base + updates are all the latest RPMS in the release, so no one should think that is a problem.
So how can you do an install based on all the latest?
Install from the current tree (5.2) and do a yum update after that.
Ralph
Ralph Angenendt wrote:
Robert Moskowitz wrote:
updates/ gets emptied out on a new point release and then is rebased on the os/ tree for the new release.
Right ... BUT, base + updates are all the latest RPMS in the release, so no one should think that is a problem.
So how can you do an install based on all the latest?
Install from the current tree (5.2) and do a yum update after that.
I know that. I do/done that. But it just seems backwards to go through all the steps of an install, followed by a 300Mb upgrade (where,for example, OpenOffice was installed). At least now I do have the local repo, so I am not killing my WAN anymore.
I know I can go through the steps for a minimal install then try and add everything later. Command line yum is hard to use for this. Yumex is not much better for the initial adding of packages. The Gnome Software Updater is almost as reasonable to work with as the one in the installer.
Well for today I have at least 2 systems to install. I have to build my new Scalix server that the lvm create failed yesterday. I also want to try a direct install on a DecTOP (that failed with 5.1, I had to put the drive in another system for the install, then move it and system-config-display to change the video)....
I also have a kernel panic on an existing DecTOP that I upgraded yesterday. I am going to see what a new install will do.
Hi,
I'm using Centos 2.4.21-37.ELsmp.
Under root user I can erase and burn a CDRW with succes.
But under normal user it's impossible and the following error message appeared
this is on the same machine.
Any help ?
Under normal user: Error ! --------------------------
/usr/bin/cdrecord -v dev=4,0,0 blank=fast Cdrecord-Clone 2.01a32-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla Note: The author of cdrecord should not be bothered with problems in this version. TOC Type: 1 = CD-ROM scsidev: '4,0,0' scsibus: 4 target: 0 lun: 0 Linux sg driver version: 3.1.25 Using libscg version 'schily-0.8'. Segmentation fault
With root user: Succes ! -----------------------
# /usr/bin/cdrecord -v dev=4,0,0 blank=fast Cdrecord-Clone 2.01a32-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla Note: The author of cdrecord should not be bothered with problems in this version. TOC Type: 1 = CD-ROM scsidev: '4,0,0' scsibus: 4 target: 0 lun: 0 Linux sg driver version: 3.1.25 Using libscg version 'schily-0.8'. /usr/bin/cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling'). SCSI buffer size: 64512 atapi: 1 Device type : Removable CD-ROM Version : 0 Response Format: 1 Vendor_info : 'PHILIPS ' Identifikation : 'DVD+-RW DVD8801 ' Revision : '4D28' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x000A Profile: 0x002B Profile: 0x001B Profile: 0x001A Profile: 0x0014 Profile: 0x0013 Profile: 0x0011 Profile: 0x0010 Profile: 0x000A (current) Profile: 0x0009 Profile: 0x0008 Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R16 RAW/R96R Drive buf size : 1073152 = 1048 KB Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Reference speed: 2 Is not unrestricted Is erasable ATIP start of lead in: -11635 (97:26/65) ATIP start of lead out: 359849 (79:59/74) 1T speed low: 0 (reserved val 0) 1T speed high: 4 2T speed low: 8 2T speed high: 0 (reserved val 10) power mult factor: 4 6 recommended erase/write power: 3 A1 values: 02 4C B0 A2 values: 4A C8 36 Disk type: Phase change Manuf. index: 3 Manufacturer: CMC Magnetics Corporation Starting to write CD/DVD at speed 4.0 in real BLANK mode for single session. Last chance to quit, starting real write 0 seconds. Operation starts. Performing OPC... Blanking PMA, TOC, pregap Blanking time: 49.918
__________________________
Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et établi à l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'IFP décline toute responsabilité au titre de ce message.
This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. IFP should not be liable for this message.
Visitez notre site Web / Visit our web site : http://www.ifp.fr __________________________
On Thu, Jun 26, 2008 at 02:58:59PM +0200, MOKRANI Rachid wrote:
Hi,
Hi Rachid,
Gentle quidelines reminder: - don't hijack threads, create a new one.
I'm using Centos 2.4.21-37.ELsmp.
Under CentOS 3, you should be running 2.4.21-57.ELsmp...
Under root user I can erase and burn a CDRW with succes.
permissions issues, probably.
But under normal user it's impossible and the following error message appeared this is on the same machine.
What are the permissions of your /dev/{cdrom/cdwriter}?
you could probably make a specific cdrecoed entry in /etc/sudoers and use sudo(8).
Cheers,
Tru
Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et établi à l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'IFP décline toute responsabilité au titre de ce message.
This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. IFP should not be liable for this message.
Visitez notre site Web / Visit our web site : http://www.ifp.fr __________________________
very funny on a public mailing list ;)
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Robert Moskowitz wrote:
I know I can go through the steps for a minimal install then try and add everything later. Command line yum is hard to use for this. Yumex is not much better for the initial adding of packages. The Gnome Software Updater is almost as reasonable to work with as the one in the installer.
Then use kickstart for installation, import the CentOS gpg-Key in %post and then use "yum -y -e0 -d0 update" in the %post section.
Ralph
On Wed, Jun 25, 2008 at 10:38 PM, Robert Moskowitz rgm@htt-consult.com wrote:
I just completed my first 5.2 install. For 'completeness' I 'tested out' yum update.
Guess what? For this minimum install, there were 43Mb of updates to download.
So I went over to my local repo server and setup a /centos/5.2/updates directory and started the rsync to get all the updates:
155 files taking up 943Mb. Already. Wow! Perhaps something to do with the initial build problem? But anyone that does an install from the CDs/DVD and includes OpenOffice, then turns around and updates, is in for a scary supprise. Yet another reason for the local repos....
This is actually perfectly normal. If you install C5.2 from the install media you will get what upstream released a month ago. Between then and now they released different updates. These are not but on the install media but end up in the updates repository to make sure the our and upstreams install media are as identical as possible.
And no, the updates repo only contains updates for the running minor release. So currently it contains updates for 5.2.
Regards, Tim
Tim Verhoeven wrote:
On Wed, Jun 25, 2008 at 10:38 PM, Robert Moskowitz rgm@htt-consult.com wrote:
I just completed my first 5.2 install. For 'completeness' I 'tested out' yum update.
Guess what? For this minimum install, there were 43Mb of updates to download.
So I went over to my local repo server and setup a /centos/5.2/updates directory and started the rsync to get all the updates:
155 files taking up 943Mb. Already. Wow! Perhaps something to do with the initial build problem? But anyone that does an install from the CDs/DVD and includes OpenOffice, then turns around and updates, is in for a scary supprise. Yet another reason for the local repos....
This is actually perfectly normal. If you install C5.2 from the install media you will get what upstream released a month ago.
Is there some other way to do an install? I build my local repo from the install media as I learned from the wiki.
Between then and now they released different updates. These are not but on the install media but end up in the updates repository to make sure the our and upstreams install media are as identical as possible.
And no, the updates repo only contains updates for the running minor release. So currently it contains updates for 5.2.
Regards, Tim
-
John R Pierce -
Johnny Hughes -
MOKRANI Rachid -
Ralph Angenendt -
Robert Moskowitz -
Tim Verhoeven -
Tru Huynh