You can subscribe to this list here.
2000 |
Jan
(2) |
Feb
(15) |
Mar
(1) |
Apr
(11) |
May
(9) |
Jun
(22) |
Jul
(23) |
Aug
(21) |
Sep
(21) |
Oct
(7) |
Nov
(13) |
Dec
(58) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(20) |
Feb
(33) |
Mar
(24) |
Apr
(27) |
May
(48) |
Jun
(12) |
Jul
(35) |
Aug
(37) |
Sep
(41) |
Oct
(37) |
Nov
(29) |
Dec
(4) |
2002 |
Jan
(35) |
Feb
(17) |
Mar
(33) |
Apr
(65) |
May
(53) |
Jun
(43) |
Jul
(38) |
Aug
(37) |
Sep
(11) |
Oct
(25) |
Nov
(26) |
Dec
(38) |
2003 |
Jan
(44) |
Feb
(58) |
Mar
(16) |
Apr
(15) |
May
(11) |
Jun
(5) |
Jul
(70) |
Aug
(3) |
Sep
(25) |
Oct
(8) |
Nov
(16) |
Dec
(15) |
2004 |
Jan
(16) |
Feb
(27) |
Mar
(21) |
Apr
(23) |
May
(14) |
Jun
(16) |
Jul
(5) |
Aug
(5) |
Sep
(7) |
Oct
(17) |
Nov
(15) |
Dec
(44) |
2005 |
Jan
(37) |
Feb
(3) |
Mar
(7) |
Apr
(13) |
May
(14) |
Jun
(23) |
Jul
(7) |
Aug
(7) |
Sep
(12) |
Oct
(11) |
Nov
(11) |
Dec
(9) |
2006 |
Jan
(17) |
Feb
(8) |
Mar
(6) |
Apr
(14) |
May
(18) |
Jun
(16) |
Jul
(6) |
Aug
(1) |
Sep
(5) |
Oct
(12) |
Nov
(1) |
Dec
(1) |
2007 |
Jan
(3) |
Feb
(6) |
Mar
(6) |
Apr
|
May
|
Jun
(7) |
Jul
(8) |
Aug
(5) |
Sep
(4) |
Oct
|
Nov
(8) |
Dec
(14) |
2008 |
Jan
(31) |
Feb
(3) |
Mar
(9) |
Apr
|
May
(15) |
Jun
(9) |
Jul
|
Aug
(13) |
Sep
(10) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
(11) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(9) |
Jul
(23) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(10) |
2011 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(5) |
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
From: <phu...@wi...> - 2009-07-14 23:10:13
|
> I figure that I can't be the only one doing dump/restores > over NFS. Restore maybe, but dump expects to read the filesystem directly AFAIK -- that's why we need a different version to handle ext2fs than for ufs. I've always run dump on the machine where the disk being backed up actually is, and preferably with the filesystem unmounted and/or the machine in single-user mode. The output can, of course, be sent elsewhere via rmt, ssh, etc. |
From: Kenneth P. <sh...@se...> - 2009-07-14 22:59:27
|
--On Tuesday, July 14, 2009 4:19 PM -0700 Brian Krusic <br...@kr...> wrote: > Actually, in my version of centos 5.3 (kernal 2.6.18-128.1.16), I saw > everything get labeled upon selinux activation. > > Perhaps your behavior was due to an earlier kernel version? Was this on initial installation or later? I didn't initially install dovecot (IMAP server) and it was failing to access individual mail folders until I manually relabeled them. This was about 2 months ago, after updating the whole system first. I did a minimal install, then used yum to pull all the packages I really needed, to get the latest of everything. Oh, I'd copied all the home folders from an old FC2 system, so they naturally lacked any labeling at all. So perhaps disabling and re-enabling SELinux with the right magic command would have relabeled those files. |
From: Brian K. <br...@kr...> - 2009-07-14 22:19:30
|
Actually, in my version of centos 5.3 (kernal 2.6.18-128.1.16), I saw everything get labeled upon selinux activation. Perhaps your behavior was due to an earlier kernel version? - Brian On Jul 14, 2009, at 3:00 PM, Kenneth Porter wrote: > --On Tuesday, July 14, 2009 1:05 PM -0700 Brian Krusic <br...@kr... > > > wrote: > >> When you activate selinux, it will automatically relable the files >> and >> then one must reboot. > > It will relabel some, but not all. I wouldn't expect relabeling of any > files in /home, since you might customize the labeling of files in > your > home dir for various reasons. I know that when I had trouble with > mail, I > had to manually relabel mail folders in ~/mail. > > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited > time, > vendors submitting new applications to BlackBerry App World(TM) will > have > the opportunity to enter the BlackBerry Developer Challenge. See > full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Dump-users mailing list > Dum...@li... > https://lists.sourceforge.net/lists/listinfo/dump-users |
From: Kenneth P. <sh...@se...> - 2009-07-14 22:00:37
|
--On Tuesday, July 14, 2009 1:05 PM -0700 Brian Krusic <br...@kr...> wrote: > When you activate selinux, it will automatically relable the files and > then one must reboot. It will relabel some, but not all. I wouldn't expect relabeling of any files in /home, since you might customize the labeling of files in your home dir for various reasons. I know that when I had trouble with mail, I had to manually relabel mail folders in ~/mail. |
From: Brian K. <br...@kr...> - 2009-07-14 19:33:55
|
Well, actually I dunno jak but thanks. I've seen your name around the boards over the years and would have to say that you know an order of magnitude more than I. I'll submit a feature request as tar, etc... can ignore EA fromage if one desires. I figure that I can't be the only one doing dump/ restores over NFS. And if I am, then mebbe I am just old skewl. - Brian On Jul 14, 2009, at 12:27 PM, Stelian Pop wrote: > On Tue, Jul 14, 2009 at 12:05:10PM -0700, Brian Krusic wrote: > >> Actually I tested this. >> >> When you activate selinux, it will automatically relable the files >> and >> then one must reboot. >> >> You can also manually relable them. > > Ah ok. You obviously know better about selinux than me :) > > Stelian. > -- > Stelian Pop <st...@po...> |
From: Stelian P. <st...@po...> - 2009-07-14 19:27:31
|
On Tue, Jul 14, 2009 at 12:05:10PM -0700, Brian Krusic wrote: > Actually I tested this. > > When you activate selinux, it will automatically relable the files and > then one must reboot. > > You can also manually relable them. Ah ok. You obviously know better about selinux than me :) Stelian. -- Stelian Pop <st...@po...> |
From: Brian K. <br...@kr...> - 2009-07-14 19:05:24
|
Actually I tested this. When you activate selinux, it will automatically relable the files and then one must reboot. You can also manually relable them. - Brian On Jul 14, 2009, at 11:59 AM, Stelian Pop wrote: > On Tue, Jul 14, 2009 at 11:56:26AM -0700, Brian Krusic wrote: > >> I found a solution. >> >> Here it is; >> >> cd / && find . -exec setfattr -h -x security.selinux '{}' \; >> >> This removes all selinux context data so that my dump/restores are >> clean and the logs don't get filled with junk. >> >> This only works with selinux disabled of course. > > Right. But this also modifies your disk files, so if you ever decide > to reactivate selinux it will no longer work... > > -- > Stelian Pop <st...@po...> |
From: Stelian P. <st...@po...> - 2009-07-14 19:00:11
|
On Tue, Jul 14, 2009 at 11:56:26AM -0700, Brian Krusic wrote: > I found a solution. > > Here it is; > > cd / && find . -exec setfattr -h -x security.selinux '{}' \; > > This removes all selinux context data so that my dump/restores are > clean and the logs don't get filled with junk. > > This only works with selinux disabled of course. Right. But this also modifies your disk files, so if you ever decide to reactivate selinux it will no longer work... -- Stelian Pop <st...@po...> |
From: Brian K. <br...@kr...> - 2009-07-14 18:56:45
|
Hi, I found a solution. Here it is; cd / && find . -exec setfattr -h -x security.selinux '{}' \; This removes all selinux context data so that my dump/restores are clean and the logs don't get filled with junk. This only works with selinux disabled of course. - Brian On Jul 14, 2009, at 11:51 AM, Stelian Pop wrote: > Hi Brian, > > On Tue, Jul 07, 2009 at 04:32:46PM -0700, Brian Krusic wrote: > >> Is there a way to exclude xattr from dumps? > > Sorry for taking so long to answer. > > Unfortunately no, there is no way right now to ignore the dumping of > EAs. > > It would be indeed be nice to have an option in dump and/or restore to > inhibit the treatment of EAs. > > I'm not sure I'll implement this very soon, but anyway it would be > nice > if you could submit an enhancement request on sourceforge, > so I will not forget about this. > > Thanks! > > -- > Stelian Pop <st...@po...> |
From: Stelian P. <st...@po...> - 2009-07-14 18:51:35
|
Hi Brian, On Tue, Jul 07, 2009 at 04:32:46PM -0700, Brian Krusic wrote: > Is there a way to exclude xattr from dumps? Sorry for taking so long to answer. Unfortunately no, there is no way right now to ignore the dumping of EAs. It would be indeed be nice to have an option in dump and/or restore to inhibit the treatment of EAs. I'm not sure I'll implement this very soon, but anyway it would be nice if you could submit an enhancement request on sourceforge, so I will not forget about this. Thanks! -- Stelian Pop <st...@po...> |
From: MargoAndTodd <mar...@gm...> - 2009-07-13 20:06:35
|
Hi All, Just figured it out (and feel a bit stupid). I have to do two dumps to backup up my system as I have two partitions. The "/" partition and the "/export" partition. All the users data -- the private stuff -- is on the export partition. So, partition my backup drive into two. One in the clear for the "/" partition and the other one as an encrypted partition for "/export". To restore, use the install disk in "rescue" mode and restore the "/" partition. At that point, boot normally and restore the encrypted, now readable, "/export" partition. One of those "duh" moments. Hope this rambling helps someone else, -T |
From: Stelian P. <st...@po...> - 2009-07-11 19:31:01
|
On Sat, Jul 11, 2009 at 11:16:39AM -0400, Tony Nelson wrote: > On 09-07-11 06:36:52, Takis Peppas wrote: > > 2009/7/11 Takis Peppas <tak...@gm...> > > > > > > Thank you for the immediate replies, > > > > > > installing e2fslibs-dev took care of the configure task > > > (./configure --enable-static --disable-transselinux), but I get the > > > attached error when make.. [...] > > > (.text+0x22d): undefined reference to `sem_wait' Looking again at the compile logs it looks like the static compile needs an explicit -lpthread at the end of the linker command line... -- Stelian Pop <st...@po...> |
From: Takis P. <tak...@gm...> - 2009-07-11 15:42:22
|
Thanks, I'll remote static, until I'm more familiar with Linux... All the best, Takis 2009/7/11 Tony Nelson <ton...@ge...>: > On 09-07-11 06:36:52, Takis Peppas wrote: >> 2009/7/11 Takis Peppas <tak...@gm...> >> > >> > Thank you for the immediate replies, >> > >> > installing e2fslibs-dev took care of the configure task >> > (./configure --enable-static --disable-transselinux), but I get the >> > attached error when make.. > > Simplest would be to remove --enalbe-static, but if you insist on it, > you will need to install the various *-static RPMs for the packages > containing the non-static libs being used. You can list the available > *-static libs with `yum list \*-static` and install all of them with > `yum install \*-static`, though that will pull in lots of other stuff. > Probably the libs you need would be the -static versions of libs listed > on the failing link command, though "-Ldir" makes that harder to figure > out. > > >> > gcc -static -o dump itime.o main.o optr.o tape.o traverse.o >> unctime.o ../common/dumprmt.o -L../compat/lib -lcompat -lext2fs >> -lcom_err -lblkid -luuid -ldevmapper -lselinux -lsepol >> > optr.o: In function `set_operators': >> > /home/takis/dump-0.4b42/dump/optr.c:211: warning: Using 'getgrnam' >> in statically linked applications requires at runtime the shared >> libraries from the glibc version used for linking >> > /home/takis/dump-0.4b42/dump/optr.c:212: warning: Using 'endgrent' >> in statically linked applications requires at runtime the shared >> libraries from the glibc version used for linking >> > ../common/dumprmt.o: In function `rmtgetconn': >> > /home/takis/dump-0.4b42/common/dumprmt.c:189: warning: Using >> 'getpwuid' in statically linked applications requires at runtime the >> shared libraries from the glibc version used for linking >> > /home/takis/dump-0.4b42/common/dumprmt.c:178: warning: Using >> 'getservbyname' in statically linked applications requires at runtime >> the shared libraries from the glibc version used for linking >> > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libc.a(rcmd.o): >> In >> function `__validuser2_sa': >> > (.text+0x447): warning: Using 'getaddrinfo' in statically linked >> applications requires at runtime the shared libraries from the glibc >> version used for linking >> > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a >> (error_message.o): >> In function `et_list_unlock': >> > (.text+0x1b0): undefined reference to `sem_post' >> > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a >> (error_message.o): >> In function `fini_et_lock': >> > (.text+0x1ce): undefined reference to `sem_destroy' >> > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a >> (error_message.o): >> In function `setup_et_lock': >> > (.text+0x1fe): undefined reference to `sem_init' >> > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a >> (error_message.o): >> In function `et_list_lock': >> > (.text+0x22d): undefined reference to `sem_wait' > > -- > ____________________________________________________________________ > TonyN.:' <mailto:ton...@ge...> > ' <http://www.georgeanelson.com/> > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Dump-users mailing list > Dum...@li... > https://lists.sourceforge.net/lists/listinfo/dump-users > |
From: Tony N. <ton...@ge...> - 2009-07-11 15:16:59
|
On 09-07-11 06:36:52, Takis Peppas wrote: > 2009/7/11 Takis Peppas <tak...@gm...> > > > > Thank you for the immediate replies, > > > > installing e2fslibs-dev took care of the configure task > > (./configure --enable-static --disable-transselinux), but I get the > > attached error when make.. Simplest would be to remove --enalbe-static, but if you insist on it, you will need to install the various *-static RPMs for the packages containing the non-static libs being used. You can list the available *-static libs with `yum list \*-static` and install all of them with `yum install \*-static`, though that will pull in lots of other stuff. Probably the libs you need would be the -static versions of libs listed on the failing link command, though "-Ldir" makes that harder to figure out. > > gcc -static -o dump itime.o main.o optr.o tape.o traverse.o > unctime.o ../common/dumprmt.o -L../compat/lib -lcompat -lext2fs > -lcom_err -lblkid -luuid -ldevmapper -lselinux -lsepol > > optr.o: In function `set_operators': > > /home/takis/dump-0.4b42/dump/optr.c:211: warning: Using 'getgrnam' > in statically linked applications requires at runtime the shared > libraries from the glibc version used for linking > > /home/takis/dump-0.4b42/dump/optr.c:212: warning: Using 'endgrent' > in statically linked applications requires at runtime the shared > libraries from the glibc version used for linking > > ../common/dumprmt.o: In function `rmtgetconn': > > /home/takis/dump-0.4b42/common/dumprmt.c:189: warning: Using > 'getpwuid' in statically linked applications requires at runtime the > shared libraries from the glibc version used for linking > > /home/takis/dump-0.4b42/common/dumprmt.c:178: warning: Using > 'getservbyname' in statically linked applications requires at runtime > the shared libraries from the glibc version used for linking > > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libc.a(rcmd.o): > In > function `__validuser2_sa': > > (.text+0x447): warning: Using 'getaddrinfo' in statically linked > applications requires at runtime the shared libraries from the glibc > version used for linking > > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a > (error_message.o): > In function `et_list_unlock': > > (.text+0x1b0): undefined reference to `sem_post' > > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a > (error_message.o): > In function `fini_et_lock': > > (.text+0x1ce): undefined reference to `sem_destroy' > > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a > (error_message.o): > In function `setup_et_lock': > > (.text+0x1fe): undefined reference to `sem_init' > > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a > (error_message.o): > In function `et_list_lock': > > (.text+0x22d): undefined reference to `sem_wait' -- ____________________________________________________________________ TonyN.:' <mailto:ton...@ge...> ' <http://www.georgeanelson.com/> |
From: Takis P. <tak...@gm...> - 2009-07-11 12:08:12
|
I see your point Stelian, "core" in my mind represents this small set of static build commands that will make possible the restoration of a system from scratch. Thanks, Takis 2009/7/11 Stelian Pop <st...@po...>: > On Sat, Jul 11, 2009 at 01:36:52PM +0300, Takis Peppas wrote: > >> 2009/7/11 Takis Peppas <tak...@gm...> >> > >> > Thank you for the immediate replies, >> > >> > installing e2fslibs-dev took care of the configure task (./configure --enable-static --disable-transselinux), but I get the attached error when make.. > >> > By the way I was really surprised when realized that dump/restore are not part of the linux core. They have saved my a,, many times in BSD. > > Well, there is no such thing as the linux "core". Each Linux distributor > (Ubuntu in your case, but there are quite a few others) chooses to > include some packages into their distribution, each package being > developped upstream by an independent group of developers. A (small) > subset of those packages gets installed by default. > > Dump is packaged by most (all ?) of the Linux distributions. But it > may not be installed by default. > > For example, if you just do a: > sudo apt-get install dump > on your Ubuntu distribution you will be able to install it. > > Of course, it may not be the latest version of dump... > > Stelian. > -- > Stelian Pop <st...@po...> > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Dump-users mailing list > Dum...@li... > https://lists.sourceforge.net/lists/listinfo/dump-users > |
From: Stelian P. <st...@po...> - 2009-07-11 11:41:52
|
On Sat, Jul 11, 2009 at 01:36:52PM +0300, Takis Peppas wrote: > 2009/7/11 Takis Peppas <tak...@gm...> > > > > Thank you for the immediate replies, > > > > installing e2fslibs-dev took care of the configure task (./configure --enable-static --disable-transselinux), but I get the attached error when make.. > > By the way I was really surprised when realized that dump/restore are not part of the linux core. They have saved my a,, many times in BSD. Well, there is no such thing as the linux "core". Each Linux distributor (Ubuntu in your case, but there are quite a few others) chooses to include some packages into their distribution, each package being developped upstream by an independent group of developers. A (small) subset of those packages gets installed by default. Dump is packaged by most (all ?) of the Linux distributions. But it may not be installed by default. For example, if you just do a: sudo apt-get install dump on your Ubuntu distribution you will be able to install it. Of course, it may not be the latest version of dump... Stelian. -- Stelian Pop <st...@po...> |
From: Takis P. <tak...@gm...> - 2009-07-11 10:36:59
|
2009/7/11 Takis Peppas <tak...@gm...> > > Thank you for the immediate replies, > > installing e2fslibs-dev took care of the configure task (./configure --enable-static --disable-transselinux), but I get the attached error when make.. > > By the way I was really surprised when realized that dump/restore are not part of the linux core. They have saved my a,, many times in BSD. > > All the best, > Takis > > > make[1]: Entering directory `/home/takis/dump-0.4b42/dump' > gcc -c -D_BSD_SOURCE -D_USE_BSD_SIGNAL -g -O2 -pipe -I.. -I../compat/include -I../dump -DRDUMP -DRRESTORE -DLINUX_FORK_BUG -DHAVE_LZO -D_PATH_DUMPDATES=\"/usr/local/etc/dumpdates\" -D_DUMP_VERSION=\"0.4b42\" itime.c -o itime.o > gcc -c -D_BSD_SOURCE -D_USE_BSD_SIGNAL -g -O2 -pipe -I.. -I../compat/include -I../dump -DRDUMP -DRRESTORE -DLINUX_FORK_BUG -DHAVE_LZO -D_PATH_DUMPDATES=\"/usr/local/etc/dumpdates\" -D_DUMP_VERSION=\"0.4b42\" main.c -o main.o > gcc -c -D_BSD_SOURCE -D_USE_BSD_SIGNAL -g -O2 -pipe -I.. -I../compat/include -I../dump -DRDUMP -DRRESTORE -DLINUX_FORK_BUG -DHAVE_LZO -D_PATH_DUMPDATES=\"/usr/local/etc/dumpdates\" -D_DUMP_VERSION=\"0.4b42\" optr.c -o optr.o > gcc -c -D_BSD_SOURCE -D_USE_BSD_SIGNAL -g -O2 -pipe -I.. -I../compat/include -I../dump -DRDUMP -DRRESTORE -DLINUX_FORK_BUG -DHAVE_LZO -D_PATH_DUMPDATES=\"/usr/local/etc/dumpdates\" -D_DUMP_VERSION=\"0.4b42\" tape.c -o tape.o > gcc -c -D_BSD_SOURCE -D_USE_BSD_SIGNAL -g -O2 -pipe -I.. -I../compat/include -I../dump -DRDUMP -DRRESTORE -DLINUX_FORK_BUG -DHAVE_LZO -D_PATH_DUMPDATES=\"/usr/local/etc/dumpdates\" -D_DUMP_VERSION=\"0.4b42\" traverse.c -o traverse.o > gcc -c -D_BSD_SOURCE -D_USE_BSD_SIGNAL -g -O2 -pipe -I.. -I../compat/include -I../dump -DRDUMP -DRRESTORE -DLINUX_FORK_BUG -DHAVE_LZO -D_PATH_DUMPDATES=\"/usr/local/etc/dumpdates\" -D_DUMP_VERSION=\"0.4b42\" unctime.c -o unctime.o > gcc -static -o dump itime.o main.o optr.o tape.o traverse.o unctime.o ../common/dumprmt.o -L../compat/lib -lcompat -lext2fs -lcom_err -lblkid -luuid -ldevmapper -lselinux -lsepol > optr.o: In function `set_operators': > /home/takis/dump-0.4b42/dump/optr.c:211: warning: Using 'getgrnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking > /home/takis/dump-0.4b42/dump/optr.c:212: warning: Using 'endgrent' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking > ../common/dumprmt.o: In function `rmtgetconn': > /home/takis/dump-0.4b42/common/dumprmt.c:189: warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking > /home/takis/dump-0.4b42/common/dumprmt.c:178: warning: Using 'getservbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libc.a(rcmd.o): In function `__validuser2_sa': > (.text+0x447): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a(error_message.o): In function `et_list_unlock': > (.text+0x1b0): undefined reference to `sem_post' > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a(error_message.o): In function `fini_et_lock': > (.text+0x1ce): undefined reference to `sem_destroy' > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a(error_message.o): In function `setup_et_lock': > (.text+0x1fe): undefined reference to `sem_init' > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libcom_err.a(error_message.o): In function `et_list_lock': > (.text+0x22d): undefined reference to `sem_wait' > collect2: ld returned 1 exit status > make[1]: *** [dump] Error 1 > make[1]: Leaving directory `/home/takis/dump-0.4b42/dump' > make: *** [all] Error 1 > root@dovey:~/dump-0.4b42# > > > > 2009/7/11 Tony Nelson <ton...@ge...> >> >> On 09-07-10 16:51:21, Kenneth Porter wrote: >> > --On Friday, July 10, 2009 11:24 PM +0300 Takis Peppas >> > <tak...@gm...> wrote: >> >> > > I'm trying to compile dump-0.4b42.tar.gz <http://sourceforge.net/ >> > > projects/dump/files/dump/dump-0.4b42.tar.gz/download> after >> > > imstalling (make install and make install-libs) the >> > > e2fsprogs-1.41.7.tar.gz >> > > <http://sourceforge.net/projects/e2fsprogs/files/e2fsprogs/ >> > > e2fsprogs-1.41.7.tar.gz/download> and this is the output of >> > > ./configure: >> ... >> > > checking for ext2fs/ext2fs.h... yes >> > > checking for ext2fs_open in -lext2fs... no >> > > configure: error: You need to install the Ext2fs libraries from the >> > > E2fsprogs distribution first - hint: make install-libs >> >> > I'm not familiar with how Ubuntu packages (I use a Red Hat derivative >> > that uses RPM packages), but check with your Ubuntu source to see how >> > to install e2fsprogs. That's needed by dump. >> >> He did install e2fsprogs with `make install-libs`, and its header was >> found but not the library (I think). If he looks at dump's config.log >> or ./configure he may find out where the library is expected to be. >> >> -- >> ____________________________________________________________________ >> TonyN.:' <mailto:ton...@ge...> >> ' <http://www.georgeanelson.com/> >> >> ------------------------------------------------------------------------------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> vendors submitting new applications to BlackBerry App World(TM) will have >> the opportunity to enter the BlackBerry Developer Challenge. See full prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> Dump-users mailing list >> Dum...@li... >> https://lists.sourceforge.net/lists/listinfo/dump-users > |
From: Tony N. <ton...@ge...> - 2009-07-11 03:11:22
|
On 09-07-10 16:51:21, Kenneth Porter wrote: > --On Friday, July 10, 2009 11:24 PM +0300 Takis Peppas > <tak...@gm...> wrote: > > I'm trying to compile dump-0.4b42.tar.gz <http://sourceforge.net/ > > projects/dump/files/dump/dump-0.4b42.tar.gz/download> after > > imstalling (make install and make install-libs) the > > e2fsprogs-1.41.7.tar.gz > > <http://sourceforge.net/projects/e2fsprogs/files/e2fsprogs/ > > e2fsprogs-1.41.7.tar.gz/download> and this is the output of > > ./configure: ... > > checking for ext2fs/ext2fs.h... yes > > checking for ext2fs_open in -lext2fs... no > > configure: error: You need to install the Ext2fs libraries from the > > E2fsprogs distribution first - hint: make install-libs > I'm not familiar with how Ubuntu packages (I use a Red Hat derivative > that uses RPM packages), but check with your Ubuntu source to see how > to install e2fsprogs. That's needed by dump. He did install e2fsprogs with `make install-libs`, and its header was found but not the library (I think). If he looks at dump's config.log or ./configure he may find out where the library is expected to be. -- ____________________________________________________________________ TonyN.:' <mailto:ton...@ge...> ' <http://www.georgeanelson.com/> |
From: Stelian P. <st...@po...> - 2009-07-10 21:57:59
|
On Fri, Jul 10, 2009 at 01:51:21PM -0700, Kenneth Porter wrote: > > configure: error: You need to install the Ext2fs libraries from the > > E2fsprogs distribution first - hint: make install-libs > > > > The system is "Linux dovey 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 > > 02:48:10 UTC 2009 i686 GNU/Linux" > > > > I really have very little exposure with Linux, been using FreeBSD for some > > time. > > I'm not familiar with how Ubuntu packages (I use a Red Hat derivative that > uses RPM packages), but check with your Ubuntu source to see how to install > e2fsprogs. That's needed by dump. sudo apt-get install e2fslibs-dev Stelian. -- Stelian Pop <st...@po...> |
From: Kenneth P. <sh...@se...> - 2009-07-10 21:35:31
|
--On Friday, July 10, 2009 11:24 PM +0300 Takis Peppas <tak...@gm...> wrote: > configure: error: You need to install the Ext2fs libraries from the > E2fsprogs distribution first - hint: make install-libs > > The system is "Linux dovey 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 > 02:48:10 UTC 2009 i686 GNU/Linux" > > I really have very little exposure with Linux, been using FreeBSD for some > time. I'm not familiar with how Ubuntu packages (I use a Red Hat derivative that uses RPM packages), but check with your Ubuntu source to see how to install e2fsprogs. That's needed by dump. |
From: Takis P. <tak...@gm...> - 2009-07-10 19:24:58
|
Hello, I'm trying to compile dump-0.4b42.tar.gz<http://sourceforge.net/projects/dump/files/dump/dump-0.4b42.tar.gz/download>after imstalling (make install and make install-libs) the e2fsprogs-1.41.7.tar.gz<http://sourceforge.net/projects/e2fsprogs/files/e2fsprogs/e2fsprogs-1.41.7.tar.gz/download>and this is the output of ./configure: root@dovey:~/dump-0.4b42# ./configure checking whether make sets $(MAKE)... yes checking whether ln -s works... yes checking for cp... /bin/cp checking for mv... /bin/mv checking for rm... /bin/rm checking for ar... ar checking for ranlib... ranlib checking for patch... patch checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for a BSD-compatible install... /usr/bin/install -c checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for sys/types.h... (cached) yes Not including debugging code by default Linking dump and restore dynamically by default Linking libz and libbz2 dynamically by default Compiling rmt by default Not compiling ermt by default Not compiling kerberos extensions by default Including readline support by default Using new style F script by default Enabling Large File System support by default Enabling Quick File Access support by default Not including Quick File Access debugging code by default Not including Mac OSX restore compatibility code by default restore can translate SELinux EAs by default CC defaults to gcc LD defaults to gcc BINOWNER defaults to root BINGRP defaults to tty BINMODE defaults to 0755 MANOWNER defaults to man MANGRP defaults to tty MANMODE defaults to 0644 DUMPDATESPATH defaults to ${prefix}/etc/dumpdates checking for ext2fs/ext2fs.h... yes checking for ext2fs_open in -lext2fs... no configure: error: You need to install the Ext2fs libraries from the E2fsprogs distribution first - hint: make install-libs The system is "Linux dovey 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:48:10 UTC 2009 i686 GNU/Linux" I really have very little exposure with Linux, been using FreeBSD for some time. Thank you in advance for your time, Takis |
From: Brian K. <br...@kr...> - 2009-07-07 23:34:45
|
Hi, Is there a way to exclude xattr from dumps? I am dump/restoring over the network via NFS and keep getting EA errors even though I have selinux disabled. An example of an error; restore: ./etc/ysyconfig/network-scripts/ifcfg-eth0: EA set security.selinux:system_u:object_r:etc_t:s0 failed: Operation not supported. I understand the NFS doesn't preserve xattr and when I do lsxattr, I get nothing in terms of extended attributes used. My command; dump -f - / | restore -r -f - Should I pipe dump to ssh or rsync to avoid NFS and xattr issues? - Brian |
From: Kenneth P. <sh...@se...> - 2009-06-25 19:12:05
|
--On Thursday, June 25, 2009 8:21 PM +0100 "Keith G. Robertson-Turner" <dum...@sl...> wrote: > If you can't update RPM to 4.7 on Centos, then if I were you I'd just > stick with ext3 and the older version of dump Note that ext4 is not the only reason to update dump, and in fact I don't really have any interest in ext4 at this time. But I do want all the other things that were updated. I can build the SRPM with "rpm -i --nomd5" and bypass the check, and presumably tar will catch any corruption issues with downloading the package as part of deflating the compression, and that's the main thing I worry about in checking its integrity. My server is also handling mail, which means I'm running ClamAV and SpamAssassin. I really need the "bleeding edge" versions of those packages, since AV and anti-spam need to move fast to catch the latest malware. So updating RPM to deal with that wouldn't just be a benefit with dump. |
From: Kenneth P. <sh...@se...> - 2009-06-25 17:51:47
|
--On Thursday, June 25, 2009 7:06 PM +0100 "Keith G. Robertson-Turner" <dum...@sl...> wrote: > Yes, as of version 4.7, RPM now uses SHA1 checksums instead of MD5, > therefore older versions of RPM trying to verify packages built with > the new version, will fail with the above error. > > http://rpm.org/wiki/Releases/4.7.0 Is it safe to upgrade to that on a RHEL/CentOS 5.3 system? Seems like that would be the easiest way to deal with the problem long-term. Will the newer RPM deal ok with packages from the older repos? Will yum get along with it? I went with CentOS instead of staying with Fedora because I didn't want to have to upgrade the whole OS every 6 months, just critical packages (including dump). I prefer to space the giant upgrades out to be every few years, and RHEL/CentOS has a very long service cycle. For critical packages where I want the latest upstream features and bug fixes, I grab the source package from Rawhide (Red Hat development repo) and rebuild it to create a distro-specific binary package. |
From: Kenneth P. <sh...@se...> - 2009-06-25 16:51:34
|
--On Wednesday, June 24, 2009 11:00 PM -0400 Tony Nelson <ton...@ge...> wrote: > Also, as I'm still on F9, I got the usual error from rpmbuild ("error: > unpacking of archive failed on file /home/tonyn/rpmbuild/SOURCES/ > dump-0.4b42.tar.gz;4a42cc95: cpio: MD5 sum mismatch") and had to > manually unpack the SRPM I got this error, too, on CentOS 5.3 (a respin of RHEL 5.3). Any idea what causes that? Has something changed in the rpmbuild/rpm utilities that causes the older system to fail to understand files produced with the latest one? |