Bug 28851 - amanda is really 2.4.2 not 2.4.2p1
Summary: amanda is really 2.4.2 not 2.4.2p1
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: amanda
Version: 7.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-22 14:47 UTC by chrismcc
Modified: 2007-04-18 16:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-02-22 16:15:03 UTC
Embargoed:

Attachments (Terms of Use)
fix for /dev/root (4.42 KB, patch)
2001-02-22 14:50 UTC, chrismcc 		no flags Details | Diff
patch for spec file (1.19 KB, patch)
2001-02-22 14:51 UTC, chrismcc 		no flags Details | Diff
View All

Description chrismcc 2001-02-22 14:47:29 UTC 
[root@fester SOURCES]# head ../SPECS/amanda.spec
%define
_libexecdir
%{_prefix}/lib/amanda

# XXX append lib to current _localstatedir setting
%{expand: %%define	_localstatedir	%{_localstatedir}/lib}

Summary: A network-capable tape backup solution.
Name: amanda
Version: 2.4.2p1
Release: 1
Source: http://download.sourceforge.net/amanda/amanda-2.4.2.tar.gz

version says p1 but the tarball is not :(
Comment 1 chrismcc 2001-02-22 14:50:22 UTC 
Created attachment 10740 [details]
fix for /dev/root
Comment 2 chrismcc 2001-02-22 14:51:09 UTC 
Created attachment 10741 [details]
patch for spec file
Comment 3 chrismcc 2001-02-22 14:54:39 UTC 
There is a bug in 2.4.2p1 where in the disklist as entry like:

server     /     back-type

amanda reads proc so it sees:

[operator@lumiere /operator]$ cat /proc/mounts
/dev/root / ext2 rw 0 0


And there is no /dev/root device.


I haven't tried the patch yet, but It is from one of the amanda developers
Comment 4 Trond Eivind Glomsrxd 2001-02-22 16:14:59 UTC 
Doh. 2.4.2p1-2 will fix this.
Comment 5 Trond Eivind Glomsrxd 2001-02-22 17:15:04 UTC 
amanda-2.4.2p1-2 is now available from http://people.redhat.com/teg/
Note You need to log in before you can comment on or make changes to this bug.