Here is a question I have never gotten a grip on, I hope someone can clue
me in.
I wish to use a distribution with a modern package management scheme, i.e.
RPM, Yum, apt-get, ports, etc. Each of these systems come with certain
versions of each software package, for instance I am now dealing
On Tuesday 15 May 2007 10:04, Charlie Farinella wrote:
How does everyone else do this?
In the Debian world, at least, I generally follow this order of precedence.
1. If it's outside the distro availability, I look to upgrading. In this
case, Python 2.3.4 is pretty outdated, so I'm assuming
To do it with RPM's I need to do about a dozen of them which means I have
to find out which ones I need, etc. negating any advantage to the package
management system.
I could build it from source and either run the 2 versions of python
simultaneously, or replace the installed python, but
Neil Joseph Schelly [EMAIL PROTECTED] writes:
On Tuesday 15 May 2007 10:04, Charlie Farinella wrote:
How does everyone else do this?
In the Debian world, at least, I generally follow this order of precedence.
4. Finally, failing all that, I'll compile something from source
and keep it as
On Tuesday 15 May 2007 11:34, Paul Lussier wrote:
Bah!
$ apt-get source foo=desired package number
$ cd foo-version number
$ dpkg-buildpackage -rfakeroot
$ cd .. dpkg -i foo-version number
This will compile the source for whatever version of the debian
package foo you need against
From: Paul Lussier [EMAIL PROTECTED]
Date: Tue, 15 May 2007 11:34:21 -0400
Cc: gnhlug-discuss@mail.gnhlug.org
$ apt-get source foo=desired package number
$ cd foo-version number
$ dpkg-buildpackage -rfakeroot
$ cd .. dpkg -i foo-version number
I think you forgot to apt-get build-deps
Charlie Farinella wrote:
To do it with RPM's I need to do about a dozen of them which means I have
to find out which ones I need, etc. negating any advantage to the package
management system.
I could build it from source and either run the 2 versions of python
simultaneously, or
On Tuesday 15 May 2007 12:12, Charlie Farinella wrote:
Just to be clear, my question only uses CentOS/Python as an example and is
not the precise problem I want to solve. I want to pick a
distro/procedure and stick to it based on solving this kind of problem.
Thanks for the feedback. :-)
On Tuesday 15 May 2007, Neil Joseph Schelly wrote:
Then it seems your question is a disguised version of Which distro is
best?
I didn't ask anything at all about what is best, I only asked how other
people handle this particular issue.
Thanks again for the response.
--charlie
--
Charlie Farinella [EMAIL PROTECTED] writes:
That said, my option 3 didn't have that much detail and didn't make so
light of the potential library requirements a newer version may have,
because I didn't want to detail the Debian/APT commands here that are
useless to the CentOS installation at
On Tue, May 15, 2007 at 12:00:16PM -0400, [EMAIL PROTECTED] wrote:
In fact,
# ls -dl /usr/lib/python*
drwxr-xr-x 15 root root 17313 Mar 10 2006 /usr/lib/python2.3
drwxr-xr-x 19 root root 21465 Mar 14 2006 /usr/lib/python2.4
this system is already running 2.3 and 2.4 side-by-side.
In
[EMAIL PROTECTED] writes:
From: Paul Lussier [EMAIL PROTECTED]
Date: Tue, 15 May 2007 11:34:21 -0400
Cc: gnhlug-discuss@mail.gnhlug.org
$ apt-get source foo=desired package number
$ cd foo-version number
$ dpkg-buildpackage -rfakeroot
$ cd .. dpkg -i foo-version number
I think you
On Tue, May 15, 2007 at 01:40:50PM -0400, Paul Lussier wrote:
[EMAIL PROTECTED] writes:
From: Paul Lussier [EMAIL PROTECTED]
Date: Tue, 15 May 2007 11:34:21 -0400
Cc: gnhlug-discuss@mail.gnhlug.org
$ apt-get source foo=desired package number
$ cd foo-version number
$
Expand your environment. Segment your apps onto independent
server/instances to avoid issues like library/application conflicts. ssh
and scp with keys are fine tools to move data around and start
processes. If that means buying more machines or using virtualization so
be it, but it's easier (imho)
Christopher Schmidt [EMAIL PROTECTED] writes:
'emerge' is similar to 'apt', in that it is a top level command which
ties together lots of smaller commands, iirc. So, although that command
will build+install, there are also commands to just build, and just
install, if memory serves.
Ahh,
On Tuesday 15 May 2007 13:40, Paul Lussier wrote:
I think you forgot to apt-get build-deps or whatever that OTHER debian
magic command is.
Perhaps, though I've never done that.
Then you've missed out - that's the part that makes building Debian source
packages so easy. It will go into
I am trying to create a small domain within my house, strictly for the purpose
of getting more familiar with setting up DNS and Sendmail. Before any of my
changes, I started with the following configuration:
* Linksys router connected to my incoming cable internet line
* The router uses
On May 15, 2007, at 14:02, Flaherty, Patrick wrote:
it's easier (imho) to deal with 12 server instances with
different os version than 1 server with 12 hacked together services on
it
yeah, what Patrick said.
Using IP addresses and/or DNS names liberally is also helpful for
when you need to
On May 15, 2007, at 16:47, Tech Writer wrote:
Does anyone have any ideas why this might be? Is it possible that
my routes or gateway need to be updated now that I've switched from
a 192.168.1.n address to the 10.25.1.n address? If so, what needs
to be changed?
Two things I can think
On Tue, 2007-05-15 at 16:47 -0400, Tech Writer wrote:
I am trying to create a small domain within my house, strictly for the
purpose of getting more familiar with setting up DNS and Sendmail.
Before any of my changes, I started with the following
configuration:
* Linksys router
Thanks for all of the suggestions, so far. I'm going to look at them more
carefully, and see if I can fix this by changing my routing table.
Both replies suggested that I change my internal domain to a 192.168.1.x IP
range (to match the Linksys) or change my Linksys router to the 10.25.1.x
On Tue, 2007-05-15 at 20:10 -0400, Tech Writer wrote:
Thanks for all of the suggestions, so far. I'm going to look at them more
carefully, and see if I can fix this by changing my routing table.
Both replies suggested that I change my internal domain to a 192.168.1.x IP
range (to match
Neil Joseph Schelly [EMAIL PROTECTED] writes:
On Tuesday 15 May 2007 13:40, Paul Lussier wrote:
I think you forgot to apt-get build-deps or whatever that OTHER debian
magic command is.
Perhaps, though I've never done that.
Then you've missed out
Well, perhaps I should re-phrase. I've
I don't mean to sound condescending, so I apologize in advance if I
come across that way. I highly recommend you do some reading on IP
addressing and networking and get a good understanding of the basics.
Whether you realize it or not, you are using a variety of terms
interchangably, which
Andrew and Stephen,
Thanks for the tips! Your combined suggestions seemed to do the trick. I
edited my rc.local file and added the lines:
echo Set up IP alias interfaces
/sbin/ifconfig eth0:0 192.168.1.30
echo Set up routes
/sbin/route add -host 127.0.0.0 dev eth0
25 matches
Mail list logo
