b-u-users

[bu-users] Happy Camper

[Mel S. <kd...@nw...>]

Well I did resolve the Pax problem and the Cannot stat 'usleep' too a 
bit of time searching. But the changelog for 3.0 Beta did make mention 
of the Makefile for usleep and on a Slackware box step # one before 
install is make. after install I did have to go to /root and do bu 
--newrc to have an rc file. So far the only Slackware box I am having 
trouble with is a clients critical server that is in production running 
Slackware 9.0 Will deal with it as time goes by.

-- 
System Janitor/Network Plumber http://www.nwla.com
Linux User #25446    Linux 2.6.18

Re: [bu-users] Happy Camper

[Vincent S. <bu...@hi...>]

On Sun, Jan 07, 2007 at 04:10:12AM -0600, Mel Sojka wrote:
> Well I did resolve the Pax problem and the Cannot stat 'usleep' too a 
> bit of time searching. But the changelog for 3.0 Beta did make mention 
> of the Makefile for usleep and on a Slackware box step # one before 
> install is make. after install I did have to go to /root and do bu 
> --newrc to have an rc file. So far the only Slackware box I am having 
> trouble with is a clients critical server that is in production running 
> Slackware 9.0 Will deal with it as time goes by.

Glad you got it resolved.

In the "Installing and getting started" section of the README it does
say to run "make install".  You can run the Install script directly, but
only if you have first run make.  This is not all platforms, not just
Slackware.

FYI: 
The --newrc option will create a new .burc in your home directory no
matter directory you are in (unless you use "-c /path/filename" option),
so you don't have to cd there first.  Also, if you remove your old
~/.burc, a new one will automatically be created with default settings,
or with settings you specify on the command line, the next time you run
bu (except with the --help switch).

I curious about what the problem is on your Slackware 9.0 box.  Bu
should run on pretty much any modern Unix as long as pax is installed.

Re: [bu-users] Happy Camper

[Vincent S. <bu...@hi...>]

On Sun, Jan 07, 2007 at 04:43:21PM -0600, Vincent Stemen wrote:
> You can run the Install script directly, but only if you have first
> run make.  This is not all platforms, not just Slackware.

Correction:  Sorry, I meant to say this is _on_ all platforms, not just
Slackware.

Re: [bu-users] Happy Camper

[Mel S. <kd...@nw...>]

Well on the Slackware 9 box I can't compile PAX  GCC libs to old to 
handle it, But did get 3.3 up and runniong on it no problem Just wish 
3.3 had the email option that makes it nice.

-- 
System Janitor/Network Plumber http://www.nwla.com
Linux User #25446    Linux 2.6.18

Re: [bu-users] Happy Camper

[Stefan M. <st...@mo...>]

On Mon, Jan 08, 2007 at 11:05:16AM -0600, Mel Sojka wrote:
> Well on the Slackware 9 box I can't compile PAX  GCC libs to old to 
> handle it, But did get 3.3 up and runniong on it no problem Just wish 
> 3.3 had the email option that makes it nice.

I may be heading slightly off topic, but it's a quiet list, so please bear
with me guys :)

What problems are you having bulding PAX? Slackware 9 is based on GCC 3 and 
glibc 2.3.1 which are, whilst not recent, not so terribly old either and 
shouldn't create issues.

It could simply be that you need to upgrade a few libraries, which can easily
be done from source, into /usr/local/lib if you are at all paranoid about 
polluting system installed libs.

You might also consider an upgrade, 2.4 kernel is looking a bit tired imho.

Stef
-- 
Quidquid latine dictum sit, altum viditur.

Re: [bu-users] Happy Camper

[Mel S. <kd...@nw...>]

Well this is a production box about to be replaced last of seven that 
have been upgraded in the past 12 months. 3.3 works fine I have a cron 
task setup to run BU and the task does not go to /dev/null so I get a 
notice on my personal box and all I have to do is open the door go into 
the lab and check the log. Easier to get Slack11 up than to do libs IMHO

-- 
System Janitor/Network Plumber http://www.nwla.com
Linux User #25446    Linux 2.6.18