You are not logged in.

#1 2003-08-06 23:07:26

Mt.Tam-Luxer
Member
From: San Rafael, CA, U.S.A.
Registered: 2003-07-24
Posts: 32

How do you 'IMAGE' your drives in Arch?

I've used GHOST 2003 and it works for Ext3 but not ReiserFS.  I've just completed the _painful_ compilation of MondoRescue (www.mondorescue.org), but have yet to test.  It claims to do ReiserFS, NTFS, and almost all other LINUX types, etc and is free/oss.  Hope it works and I think it would be a valuable addition to ARCH repositories.  I just haven't learned how to 'makepkg', yet.

Please post with any other suggestions/tools you use.

Thanx.

Offline

#2 2003-09-09 22:28:45

rls
Member
From: contracosta, california
Registered: 2003-08-20
Posts: 60

Re: How do you 'IMAGE' your drives in Arch?

I recently used partimage to successfully image the FAT32 and ext2 filesystems in upgrading my hard disk. partimage will handle other filesystems.

Another step is needed if the partition to which the image file is being "restored" is larger than the source partition for the image file. For example, suppose the image file came from a 2 GB partition and the destination partition is 4 GB. After running partimage in restore mode the filesystem will be only 2 GB, not 4 GB.

The remedy is to use parted. Run the resize command in parted with the start and end points of the partition. That moves the data and creates a filesystem with the same size as the partition.  Magic

Regards, Rick


"Es gibt nichts mehr praktish als theorie" L. Boltzmann

Offline

#3 2003-09-10 18:31:47

marin_linuxer
Member
From: San Rafael, CA U.S.A.
Registered: 2003-09-03
Posts: 111
Website

Re: How do you 'IMAGE' your drives in Arch?

Great.

I have learned that the latest release of 'KNOPPIX' includes the latest release of PARTIMAGE.  The PARTIMAGE website recommends using KNOPPIX as the boot-disk when using their product, so I'll try it.  Thanx for the response.


-- Linux!  Isn't it time?

Offline

#4 2003-09-11 18:53:02

marin_linuxer
Member
From: San Rafael, CA U.S.A.
Registered: 2003-09-03
Posts: 111
Website

Re: How do you 'IMAGE' your drives in Arch?

Worked great!

No more Norton Ghost !!!

Wheeeeee!!!


-- Linux!  Isn't it time?

Offline

#5 2003-09-11 20:55:08

dp
Member
From: Zürich, Switzerland
Registered: 2003-05-27
Posts: 3,363
Website

Re: How do you 'IMAGE' your drives in Arch?

is there a need for archlinux-package of partimage and needed libs ( http://www.partimage.org/download.en.html )?


The impossible missions are the only ones which succeed.

Offline

#6 2003-09-12 13:52:48

rls
Member
From: contracosta, california
Registered: 2003-08-20
Posts: 60

Re: How do you 'IMAGE' your drives in Arch?

dp:

My answer would be yes, but it will be a good exercise. Being impatient, I tried to build partimage-0.6.2 from source by downloading the tarball into /usr/local and doing the usual proceedure. ./configure gave the error message that libnewt was not found, even though newt-1.08 had been installed by pacman. Since the partimage home page specifically called for newt-0.50, I downloaded that  tar ball into /usr/local. make for newt-0.50 quit with the message that the tcl library was not found even though I had installed tcl with pacman.

At that point I raised the white flag, downloaded and installed the statically linked version of pacman-0.6.2, and continued on my way upgrading my hard drive.

Perhaps marin-luxer was more skilled in cutting through the dependency jungle than I. After all the weather is better on his(her?) side of the bay.

Best of Luck.

Rick, alias the contracosta_linuxer


"Es gibt nichts mehr praktish als theorie" L. Boltzmann

Offline

#7 2003-09-12 17:09:23

marin_linuxer
Member
From: San Rafael, CA U.S.A.
Registered: 2003-09-03
Posts: 111
Website

Re: How do you 'IMAGE' your drives in Arch?

rls wrote:

dp:

Perhaps marin-luxer was more skilled in cutting through the dependency jungle than I. After all the weather is better on his(her?) side of the bay.

Best of Luck.

Rick, alias the contracosta_linuxer

Hey Rick,

OK -- so I owe ya a beer if you ever head this way(just 'cause the weather is nice and I cheated -- used the KNOPPIX boot cd version).  I think I tried to compile PartImage a while back and gave-up before you did.  No big deal, I'm used to the way Norton Ghost requires a re-boot in order to image the system partitions.  I'm mostly glad to have a solution for ReiserFS --- that is easy.

BTW:  I'm a 'his', so don't get excited  wink

Chris(topher), from the sunny-side.


-- Linux!  Isn't it time?

Offline

#8 2003-09-12 21:08:53

dp
Member
From: Zürich, Switzerland
Registered: 2003-05-27
Posts: 3,363
Website

Re: How do you 'IMAGE' your drives in Arch?

rls wrote:

dp:

My answer would be yes, but it will be a good exercise. Being impatient, I tried to build partimage-0.6.2 from source by downloading the tarball into /usr/local and doing the usual proceedure. ./configure gave the error message that libnewt was not found, even though newt-1.08 had been installed by pacman. Since the partimage home page specifically called for newt-0.50, I downloaded that  tar ball into /usr/local. make for newt-0.50 quit with the message that the tcl library was not found even though I had installed tcl with pacman. [...]

before i waited for any answer i realized that it is a good idea having something like partimage on arch as package ... and i tried to build the 0.6.2 with the exactly same thing you tried (downgrade newt -> problem with tcl ...) what i tried then was downgrading tcl to a really low version and it tried to compile but messed with some functions --- wrong way

then i was trying to build the new 0.7.1 of partimage (the needed lzo and the lzop for using lzo in commandline is in incoming... working great)

[+] no problem with ./configure
[-] some stupid error in building (see down)

the PKGBUILD i used:

# Contributor: Damir Perisa <damir.perisa@bluewin.ch>
pkgname=partimage
pkgver=0.7.1
pkgrel=1
pkgdesc="Partition Image is a utility which saves partitions in many formats to an image file. The image file can be compressed in the GZIP/BZIP2 formats to save disk space, and split into multiple files to be copied on removable floppies. Partitions can be saved across the network."
url="http://www.partimage.org/"
depends=('bzip2>=1.0.0' 'libmcrypt>=2.4.14' openssl newt 'zlib>=1.1.4' lzo glibc e2fsprogs 'parted>=1.6.0')
conflicts=()
backup=()
install=
source=(http://unc.dl.sourceforge.net/sourceforge/partimage/$pkgname-$pkgver.tar.bz2)

build() {
  cd $startdir/src/$pkgname-$pkgver
  ./configure --prefix=/usr
  make || return 1
  make prefix=$startdir/pkg/usr install
}

the error it gave building:

[...]
config.status: config.h is unchanged
config.status: executing default-1 commands
config.status: executing pitype commands
creating pitypes.h
pitypes.h is unchanged

Type 'make' to compile Partimage.
cd . 
  && CONFIG_FILES= CONFIG_HEADERS=config.h 
     /bin/sh ./config.status
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing default-1 commands
config.status: executing pitype commands
make  all-recursive
make[1]: Entering directory `/building/partimage/src/partimage-0.7.1'
Making all in src
make[2]: Entering directory `/building/partimage/src/partimage-0.7.1/src'
Making all in shared
make[3]: Entering directory `/building/partimage/src/partimage-0.7.1/src/shared'
Making all in fs
make[4]: Entering directory `/building/partimage/src/partimage-0.7.1/src/shared/fs'
source='fs_base.cpp' object='fs_base.o' libtool=no 
depfile='.deps/fs_base.Po' tmpdepfile='.deps/fs_base.TPo' 
depmode=gcc3 /bin/sh ../../../depcomp 
g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. -I../../../src/shared -I../../../src/shared/modules -I../../../src/shared/network -I../../../src/client -I../../../src/client/fs  -fexceptions   -c -o fs_base.o `test -f fs_base.cpp || echo './'`fs_base.cpp
source='fs_hfs.cpp' object='fs_hfs.o' libtool=no 
depfile='.deps/fs_hfs.Po' tmpdepfile='.deps/fs_hfs.TPo' 
depmode=gcc3 /bin/sh ../../../depcomp 
g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. -I../../../src/shared -I../../../src/shared/modules -I../../../src/shared/network -I../../../src/client -I../../../src/client/fs  -fexceptions   -c -o fs_hfs.o `test -f fs_hfs.cpp || echo './'`fs_hfs.cpp
source='fs_unknown.cpp' object='fs_unknown.o' libtool=no 
depfile='.deps/fs_unknown.Po' tmpdepfile='.deps/fs_unknown.TPo' 
depmode=gcc3 /bin/sh ../../../depcomp 
g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. -I../../../src/shared -I../../../src/shared/modules -I../../../src/shared/network -I../../../src/client -I../../../src/client/fs  -fexceptions   -c -o fs_unknown.o `test -f fs_unknown.cpp || echo './'`fs_unknown.cpp
In file included from fs_unknown.cpp:18:
fs_unknown.h:30: error: `struct CInfoUnknownHeader::<anonymous union>::val'
   invalid; an anonymous union can only have non-static data members
make[4]: *** [fs_unknown.o] Error 1
make[4]: Leaving directory `/building/partimage/src/partimage-0.7.1/src/shared/fs'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/building/partimage/src/partimage-0.7.1/src/shared'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/building/partimage/src/partimage-0.7.1/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/building/partimage/src/partimage-0.7.1'
make: *** [all] Error 2
==> Build Failed.  Aborting...
[damir@Asteraceae partimage]$

... the thing is: i dont like statically built things on my pc ... so using knoppix for using partimage is the only solution till i (or someone else) managed to build it properly


The impossible missions are the only ones which succeed.

Offline

#9 2003-09-13 00:01:07

rls
Member
From: contracosta, california
Registered: 2003-08-20
Posts: 60

Re: How do you 'IMAGE' your drives in Arch?

dp, you are a better man than I Gunga-Din. From the green hell of the dependency jungle to the valley of compiler death.

An alternative to the Knoppix route is http://sourceforge.net/projects.partimage. You can download the source tarball for 0.6.2 (stable), 0.7.1 (unstable), and 0.7.2 (more unstable?). You can also download the statically linked binary for 0.6.2 and 0.7.1 if your machette is dull and/or your rod and staff are small.

Regards, Rick


"Es gibt nichts mehr praktish als theorie" L. Boltzmann

Offline

#10 2003-09-13 11:30:57

dp
Member
From: Zürich, Switzerland
Registered: 2003-05-27
Posts: 3,363
Website

Re: How do you 'IMAGE' your drives in Arch?

rls wrote:

dp, you are a better man than I Gunga-Din. From the green hell of the dependency jungle to the valley of compiler death.

sorry, but this is too high english to me --- if it is a compliment, thanx

rls wrote:

An alternative to the Knoppix route is http://sourceforge.net/projects.partimage. You can download the source tarball for 0.6.2 (stable), 0.7.1 (unstable), and 0.7.2 (more unstable?). You can also download the statically linked binary for 0.6.2 and 0.7.1 if your machette is dull and/or your rod and staff are small.

well, the 0.6.2 will not go ./configure , because of version conflicting with netw and tcl

the 0.7.1 will not build (see other post)

the 0.7.2 i cannot find on the internet --- maybe they solved  the problem from 0.7.1 there (the link you gave comes to a "PAGE NOT FOUND" on sourceforge, sorry i cant find this version on the internet)

but hey, we are not in a hurry, because there is knoppix working great if you must do some backups of your parts :-)

Endless Loop, n.:
        see Loop, Endless.
Loop, Endless, n.:
        see Endless Loop.
                -- Random Shack Data Processing Dictionary


The impossible missions are the only ones which succeed.

Offline

#11 2003-09-13 13:39:52

rls
Member
From: contracosta, california
Registered: 2003-08-20
Posts: 60

Re: How do you 'IMAGE' your drives in Arch?

dp:

Yes, it was a compliment.

Sorry for the bad URL. The correct one is http://sourceforge.net/projects/partimage

Rick


"Es gibt nichts mehr praktish als theorie" L. Boltzmann

Offline

#12 2003-09-13 14:19:24

dp
Member
From: Zürich, Switzerland
Registered: 2003-05-27
Posts: 3,363
Website

Re: How do you 'IMAGE' your drives in Arch?

ok, thanx, now i can get it --- but we are not really fortunate:

[+] ./configure no problem (use the deps i used in my first PKGBUILD up)
[-] as you said: we are now in "compiler death":

g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. -I../../../src/client -I../../../src/shared -I../../../src/shared/modules -I../../../src/shared/network  -fexceptions   -c -o gui.o `test -f 'gui.cpp' || echo './'`gui.cpp
In file included from gui.cpp:29:
gui.h:21:18: newt.h: No such file or directory
In file included from /usr/include/c++/3.3.1/backward/iostream.h:31,
                 from ../../../src/shared/network/net.h:31,
                 from ../../../src/shared/network/netclient.h:27,
                 from interface_net.h:22,
                 from gui.h:29,
                 from gui.cpp:29:
/usr/include/c++/3.3.1/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <sstream> instead of the deprecated header <strstream.h>. To disable this warning use -Wno-deprecated.
In file included from /usr/include/c++/3.3.1/string:53,
                 from /usr/include/c++/3.3.1/bits/locale_classes.h:47,
                 from /usr/include/c++/3.3.1/bits/ios_base.h:47,
                 from /usr/include/c++/3.3.1/ios:49,
                 from /usr/include/c++/3.3.1/ostream:45,
                 from /usr/include/c++/3.3.1/iostream:45,
                 from /usr/include/c++/3.3.1/backward/iostream.h:32,
                 from ../../../src/shared/network/net.h:31,
                 from ../../../src/shared/network/netclient.h:27,
                 from interface_net.h:22,
                 from gui.h:29,
                 from gui.cpp:29:
/usr/include/c++/3.3.1/bits/basic_string.h: In member function `int
   std::basic_string<_CharT, _Traits, _Alloc>::compare(const
   std::basic_string<_CharT, _Traits, _Alloc>&) const':
/usr/include/c++/3.3.1/bits/basic_string.h:830: error: parse error before `;'
   token
In file included from /usr/include/c++/3.3.1/string:57,
                 from /usr/include/c++/3.3.1/bits/locale_classes.h:47,
                 from /usr/include/c++/3.3.1/bits/ios_base.h:47,
                 from /usr/include/c++/3.3.1/ios:49,
                 from /usr/include/c++/3.3.1/ostream:45,
                 from /usr/include/c++/3.3.1/iostream:45,
                 from /usr/include/c++/3.3.1/backward/iostream.h:32,
                 from ../../../src/shared/network/net.h:31,
                 from ../../../src/shared/network/netclient.h:27,
                 from interface_net.h:22,
                 from gui.h:29,
                 from gui.cpp:29:
/usr/include/c++/3.3.1/bits/basic_string.tcc: In member function `
   std::basic_string<_CharT, _Traits, _Alloc>& std::basic_string<_CharT,
   _Traits, _Alloc>::append(const std::basic_string<_CharT, _Traits, _Alloc>&,
   typename _Alloc::size_type, typename _Alloc::size_type)':
/usr/include/c++/3.3.1/bits/basic_string.tcc:693: error: parse error before `('
   token
/usr/include/c++/3.3.1/bits/basic_string.tcc: In member function `typename
   _Alloc::size_type std::basic_string<_CharT, _Traits, _Alloc>::rfind(const
   _CharT*, typename _Alloc::size_type, typename _Alloc::size_type) const':
/usr/include/c++/3.3.1/bits/basic_string.tcc:824: error: parse error before `('
   token
/usr/include/c++/3.3.1/bits/basic_string.tcc: In member function `int
   std::basic_string<_CharT, _Traits, _Alloc>::compare(typename
   _Alloc::size_type, typename _Alloc::size_type, const
   std::basic_string<_CharT, _Traits, _Alloc>&) const':
/usr/include/c++/3.3.1/bits/basic_string.tcc:963: error: parse error before `('
   token
/usr/include/c++/3.3.1/bits/basic_string.tcc:964: error: parse error before `('
   token
/usr/include/c++/3.3.1/bits/basic_string.tcc: In member function `int
   std::basic_string<_CharT, _Traits, _Alloc>::compare(typename
   _Alloc::size_type, typename _Alloc::size_type, const
   std::basic_string<_CharT, _Traits, _Alloc>&, typename _Alloc::size_type,
   typename _Alloc::size_type) const':
/usr/include/c++/3.3.1/bits/basic_string.tcc:982: error: parse error before `('
   token
/usr/include/c++/3.3.1/bits/basic_string.tcc:983: error: parse error before `('
   token
/usr/include/c++/3.3.1/bits/basic_string.tcc:984: error: parse error before `('
   token
/usr/include/c++/3.3.1/bits/basic_string.tcc: In member function `int
   std::basic_string<_CharT, _Traits, _Alloc>::compare(const _CharT*) const':
/usr/include/c++/3.3.1/bits/basic_string.tcc:1000: error: parse error before `(
   ' token
/usr/include/c++/3.3.1/bits/basic_string.tcc: In member function `int
   std::basic_string<_CharT, _Traits, _Alloc>::compare(typename
   _Alloc::size_type, typename _Alloc::size_type, const _CharT*) const':
/usr/include/c++/3.3.1/bits/basic_string.tcc:1018: error: parse error before `(
   ' token
/usr/include/c++/3.3.1/bits/basic_string.tcc:1019: error: parse error before `(
   ' token
/usr/include/c++/3.3.1/bits/basic_string.tcc: In member function `int
   std::basic_string<_CharT, _Traits, _Alloc>::compare(typename
   _Alloc::size_type, typename _Alloc::size_type, const _CharT*, typename
   _Alloc::size_type) const':
/usr/include/c++/3.3.1/bits/basic_string.tcc:1036: error: parse error before `(
   ' token
/usr/include/c++/3.3.1/bits/basic_string.tcc:1037: error: parse error before `(
   ' token
/usr/include/c++/3.3.1/bits/basic_string.tcc:1038: error: parse error before `(
   ' token
/usr/include/c++/3.3.1/bits/basic_string.tcc: In function `void
   std::_S_string_copy(const std::basic_string<_CharT, _Traits, _Alloc>&,
   _CharT*, typename _Alloc::size_type)':
/usr/include/c++/3.3.1/bits/basic_string.tcc:1052: error: parse error before `(
   ' token
In file included from /usr/include/c++/3.3.1/bits/locale_facets.tcc:43,
                 from /usr/include/c++/3.3.1/locale:47,
                 from /usr/include/c++/3.3.1/bits/ostream.tcc:37,
                 from /usr/include/c++/3.3.1/ostream:535,
                 from /usr/include/c++/3.3.1/iostream:45,
                 from /usr/include/c++/3.3.1/backward/iostream.h:32,
                 from ../../../src/shared/network/net.h:31,
                 from ../../../src/shared/network/netclient.h:27,
                 from interface_net.h:22,
                 from gui.h:29,
                 from gui.cpp:29:
/usr/include/c++/3.3.1/limits:205:22: macro "min" requires 2 arguments, but only 1 given
In file included from /usr/include/c++/3.3.1/bits/locale_facets.tcc:43,
                 from /usr/include/c++/3.3.1/locale:47,
                 from /usr/include/c++/3.3.1/bits/ostream.tcc:37,
                 from /usr/include/c++/3.3.1/ostream:535,
                 from /usr/include/c++/3.3.1/iostream:45,
                 from /usr/include/c++/3.3.1/backward/iostream.h:32,
                 from ../../../src/shared/network/net.h:31,
                 from ../../../src/shared/network/netclient.h:27,
                 from interface_net.h:22,
                 from gui.h:29,
                 from gui.cpp:29:
/usr/include/c++/3.3.1/limits: At global scope:
/usr/include/c++/3.3.1/limits:205: error: parse error before `throw'
/usr/include/c++/3.3.1/limits:206:22: macro "max" requires 2 arguments, but only 1 given
/usr/include/c++/3.3.1/limits:206: error: ISO C++ forbids defining types within
   return type
/usr/include/c++/3.3.1/limits:206: error: syntax error before `throw'
/usr/include/c++/3.3.1/limits:206: error: syntax error before `throw'
/usr/include/c++/3.3.1/limits:207: error: syntax error before `(' token
/usr/include/c++/3.3.1/limits:208: error: syntax error before `(' token
/usr/include/c++/3.3.1/limits:209: error: syntax error before `(' token
/usr/include/c++/3.3.1/limits:210: error: syntax error before `(' token
/usr/include/c++/3.3.1/limits:211: error: syntax error before `(' token
/usr/include/c++/3.3.1/limits:212: error: syntax error before `(' token
/usr/include/c++/3.3.1/limits:219: error: `numeric_limits' is not a template
/usr/include/c++/3.3.1/limits:220: confused by earlier errors, bailing out
make[4]: *** [gui.o] Error 1
make[4]: Leaving directory `/building/partimage/src/partimage-cvs-0.7.2/src/gui-client/shared'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/building/partimage/src/partimage-cvs-0.7.2/src/gui-client'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/building/partimage/src/partimage-cvs-0.7.2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/building/partimage/src/partimage-cvs-0.7.2'
make: *** [all] Error 2
==> Build Failed.  Aborting...
[damir@Asteraceae partimage]$

:-( --- will contact the author for more help ... maybe (s)he can help with this


The impossible missions are the only ones which succeed.

Offline

#13 2003-09-13 17:07:57

rls
Member
From: contracosta, california
Registered: 2003-08-20
Posts: 60

Re: How do you 'IMAGE' your drives in Arch?

The modern world has an interesting situation in all technological fields. One can maintain backward compatibility or one can forget about legacy to maximize "performance." I had C source code that wouldn't compile with gcc 3.3 because stdargs.h had been eliminated.

As I understand it, every version of the kernel compiles with some, but not all, versions of gcc. The same phenomenon seems applicable to all C source code.

So one has to hope, with every new version of gcc, that the old source code will compile. As well as all the dependency issues.

I find it slightly amusing that people criticize Microsoft when old apps don't work with new versions of Windows, but don't we have an analogous situation in Linux, old apps not working with new versions of the system's programs? Then again, if everything worked perfectly "right out of the box", Linux wouldn't be "educational."

Rick


"Es gibt nichts mehr praktish als theorie" L. Boltzmann

Offline

#14 2003-09-13 18:24:06

dp
Member
From: Zürich, Switzerland
Registered: 2003-05-27
Posts: 3,363
Website

Re: How do you 'IMAGE' your drives in Arch?

rls wrote:

The modern world has an interesting situation in all technological fields. One can maintain backward compatibility or one can forget about legacy to maximize "performance." I had C source code that wouldn't compile with gcc 3.3 because stdargs.h had been eliminated.

As I understand it, every version of the kernel compiles with some, but not all, versions of gcc. The same phenomenon seems applicable to all C source code.

So one has to hope, with every new version of gcc, that the old source code will compile. As well as all the dependency issues.

I find it slightly amusing that people criticize Microsoft when old apps don't work with new versions of Windows, but don't we have an analogous situation in Linux, old apps not working with new versions of the system's programs? Then again, if everything worked perfectly "right out of the box", Linux wouldn't be "educational."

Rick

you are right at any site you look on the situation ... the only thing is: linux users are more educated (on the side how computers work) and more flexible than windows users: some of them patch the source, hack the code, do something to make it working with the newest version --- but to tell the truth: i'm not content with some things that changed in the gcc in the 3.x versions

as i'm a student in biology i can compare this to the evolution in nature: if you want (as an animal or plant or bacteria) to have a new feature, this costs some time, some resources and giving up some other features that can be usefull, but not that much usefull the new feature will be

if you are too slow evoluating, you will be swept from the surface of this planet: like some projects that need gnome1.4 ... if they do nothing about it :-)


The impossible missions are the only ones which succeed.

Offline

#15 2003-09-13 20:10:48

rls
Member
From: contracosta, california
Registered: 2003-08-20
Posts: 60

Re: How do you 'IMAGE' your drives in Arch?

Your points are well taken. Evolve or go extinct. I had never thought about extinct software.

Speaking of evolution, I have a question. Let me preface the question by saying I have the highest regard for programmers. My question concerns the ./configure phase of building an executable/lib from source. How many times has ./configure failed because lib XXX not found? Why didn't the programmer require the package, version, name and directory info to appear if  lib XXX  was not located. More specifically, lib XXX not found, libXXX is generated by program ZZZ, version YYY, name NNN and lib XXX was expected to be in directory /???. Without this information troubleshooting is tedious to say the least. One doesn't know if the lib is present but in the wrong directory, is present and in the right directory but has the wrong name, and so on and so on.

This would require a little more work for the programmer, but overall benefit the Linux community. And thus be good evolutionarily. If there is a technical reason why it can't be done, I would be most thankful in knowing it.

Regards, Rick


"Es gibt nichts mehr praktish als theorie" L. Boltzmann

Offline

#16 2003-09-14 04:42:36

Xentac
Forum Fellow
From: Victoria, BC
Registered: 2003-01-17
Posts: 1,797
Website

Re: How do you 'IMAGE' your drives in Arch?

There's a file called 'config.log' that's generated by ./configure that gives you information like that.  Usually, to detect libraries, ./configure runs gcc on a file and checks to see if there are errors.

The problem with your solution is that a lot of programs can work with multiple versions of libraries, in multiple places (all the places listed in /etc/ld.so.conf, plus some others), and sometimes even supplied by multiple programs (curses and ncurses, bad example but you get the idea).

The idea behind configure is to give you as many options as possible.


I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal

Offline

#17 2003-09-14 14:20:57

rls
Member
From: contracosta, california
Registered: 2003-08-20
Posts: 60

Re: How do you 'IMAGE' your drives in Arch?

Xentac:

Many thanks for the good intel. config.log does all that I wanted and more.

I will suggest to Dennis that a Section 6.20 "Trouble Shooting Dependency Issues during a Build from Source" be added to the ARCH LINUX Documentation. The first point will be to look at the config.log file. Actually, that should be the second point. The first point is not to be impatient and read all of the documentation in the unpacked source tarball, especially README.

Since we are on a roll, I will ask for your thoughts on the compile phase of a build from source. When the compiler quits, I have quit not being a proficient C programmer or well versed in the worklings of gcc. Is that the correct course of action or do you have some intel on troubleshooting compile issues?

Regards, Rick


"Es gibt nichts mehr praktish als theorie" L. Boltzmann

Offline

#18 2003-09-14 16:44:48

Xentac
Forum Fellow
From: Victoria, BC
Registered: 2003-01-17
Posts: 1,797
Website

Re: How do you 'IMAGE' your drives in Arch?

Generally with compile issues, if you don't know a little bit of C they're really difficult.  You might want to google for the name of the package and the error message, to see if other people have had similar problems.  Or if it's a fairly non-standard problem (one created by gcc 3.x, though you wouldn't know that without knowing some C), you can search just for the error message.  Sometimes it takes a little research and patience.

Another option is to contact the developer of the program and ask if they can help.  I'm sure most of them would be glad to help you build a package for arch.


I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal

Offline

#19 2003-09-16 20:35:47

marin_linuxer
Member
From: San Rafael, CA U.S.A.
Registered: 2003-09-03
Posts: 111
Website

Re: How do you 'IMAGE' your drives in Arch?

Hey there, new discovery.  I still prefer 'partimage', but I thought this might be good to post for those seeking an alternative and who don't care about 'raw' copy vs. intelligent 'used-space' imagers:

g4u -- Ghost4Unix

http://www.feyrer.de/g4u/


-- Linux!  Isn't it time?

Offline

Board footer

Powered by FluxBB