Printable View
Not sure you would need a different Linux distro Harry...you can just install the packages you need that Ubuntu doesn't have as default. (Putting them in /opt of course to show they are not part of the distro)Quote:
Originally Posted by harrybarracuda
:)Quote:
Originally Posted by baldrick
Then again, it shouldn't work on a linux install either. net-tools has been obsoleted for 7 years now. iproute is where it's at. As for wlan0, surely you mean w1p0s0 or maybe even wlx0012d372ba3?
please don't confuse baldrick :rofl:
Quote:
Originally Posted by Troy
Unless you were compiling from source that would make no sense. Even if you are compiling from source it makes no sense. To install software use a package manager, standard on all distros. Ubuntu defaults to Debian-style .dpkg package management and you'd normally use the aptitude command set to manage your packages. For example, if you wanted to install a webserver on your Ubuntu Distro you would more than likely start off by typing something like 'apt-get install httpd" at your command line, you would almost certainly not be typing something along the lines of './configure --prefix=/opt'!
To install software you've made yourself package up your code and then use a package manager to install it. Unless you have very specific need you would rarely, if ever, need to drop anything in /opt.
package manager are for pussies,Quote:
Originally Posted by DrB0b
real men use ftp to download their source, untar and run ./configure with all the right parameters
DrB why are you such a poof ? next you are going to tell me that you use Github for all your code sources :p
If that's not an oxymoron I'm a penguin.Quote:
Originally Posted by Dragonfly
Today I need to install nginx with a set of custom modules on 2,000 servers. 800 of them have specific requirements to disable caching for font-face fonts when requests come in from IE11 and are being proxied to specific back-end servers. There are 300 files in /etc/nginx/conf.d each of which have complex and different regex filters, condition dependent of course, in the location settings for proxied content. I wrote the new modules and compiled them into nginx myself and created the RPM packages I'm going to install. As we're using a number of different OS versions I used mock. I've just finished regression testing and am ready to deploy. The deployment has to be done with minimal downtime, each instance (note, instance and not server or service) cannot be down for any more than a second during the upgrade and ideally for a much shorter period than that. We also have to comply with our security divisions irritatingly complex rules about what can be accessed from where.Quote:
Originally Posted by Dragonfly
Your advice on how to do this deployment, maintain consistency across servers, and ensure that all of this fits into our Continuous Integration and Configuration Management systems while using only FTP, tar, and automake would be appreciated. BTW, the whole deployment should take less than 3 minutes from beginning to end.
Almost forgot, in the case of a problem what should be the rollback procedure?
0000001000101011
Glad you find it funny ;)Quote:
Originally Posted by david44
Answers please buTTers..................
Give him a moment :)Quote:
Originally Posted by crackerjack101
https://teakdoor.com/images/imported/2016/11/648.jpg
I think t is useful if you are installing packages or software not supported by Canonical and not written by yourself. You could put them in /usr/local but I prefer /opt. Call me a dinosaur if you will.Quote:
Originally Posted by DrB0b
The point is I don't think Ubuntu is lacking anything that would require installing a different distro but you may need to add packages/software that are not part of the default distro.
Your point is correct but your idea that you can just drop packages in /opt or /usr/local is not. A Dinosaur or not 99% of the time that just wouldn't work.Quote:
Originally Posted by Troy
A package manager will put the packages in the right place, that's what it's for. Nor does a package manager just add packages provided by the distributor, Canonical in Ubuntu's case. Package manager's can be, and almost always are, configured to use external repositories. That is the proper way to add software.
Let me put it to you another way. How do you think dropping packages into /opt or /usr/local/ would work? How would it be done?
As an example, I downloaded and installed eclipse into /opt. This was before the apt-get eclipse-platform was available.Quote:
Originally Posted by DrB0b
Ditto for chrome.
As time drifts slowly by....................Quote:
Originally Posted by DrB0bGive him a moment :)Quote:
Originally Posted by crackerjack101
https://teakdoor.com/images/imported/2016/11/648.jpg
That's because packages were built to install them into /opt or everything they require to run is in a self-contained directory tree containing pre-compiled binaries and their supporting libraries. Packages which were compiled for specific distributions. YOU didn't install them into /opt, they were self installing packages which installed into appropriate locations when ./install.sh or whatever was run or they were tarred-up directory trees. Packages like that, even if not immediately obvious come with installation scripts and pre-compiled binaries for the installation you're installing to. The binaries are often either statically linked or the shared libraries they require will also be installed as part of the installation procedure.Quote:
Originally Posted by Troy
This is not usual in the current Linux world, it is not the same as just dropping something into /opt, and not many packages install in this way. My question might not have been very clear. Let me put it another way. As you use eclipse I'll hazard a guess that you do some coding. Say you need a git installation on your workstation but there is no precompiled package for it. Without going through the compilation routine how would you get a copy of git onto that box.
If you did compile it how would you deal with upgrades as time went on? How would you deal with dependencies? How would you deal with that taking into account that time is money?
I guess all that verbiage I just wrote boils down to "what would you do in the pretty standard case that there is no pre-compiled package for the software you need?"
It looks like Buttplug's bluff has been well and truly called. He can only bullshit so much crap he's feverishly copying off the web before it becomes apparent he hasn't got a fucking clue what he's on about.
:)
I guess by no precompiled package you mean no debian package that can be obtained through apt....rather than source which would have to be compiled...:confused:Quote:
Originally Posted by DrB0b
So I have an executable and have it from a reliable source and have checksum verified. I can then drop it into /temp and then change the install script to have it install into /opt/<new app> which will have all the supporting directories below it. Or if it is a tarball without requiring any install then I can just cp it into /opt and untar.
Updates? I am waiting for a debian apt-get install, which will make everything easy. In the meantime I use what I have and check for updates as and when i feel like. The idea that I need the latest and greatest all the time is simply rubbish. After all I am still using v98 professionally rather than c11....and ada-95 rather than ada-2012 and fortran-77 instead of fortran-90 or whatever the latest is. Perl 5.8 with tk rather than 6 without it and python 2.7 or 3.x and mentally adjust to suit.
True for google/chrome but not for eclipseQuote:
Originally Posted by DrB0b
Fortran.
God that brings back memories of college I'd long since buried.
And huge piles of punched cards.
^ My first software editor:
https://teakdoor.com/images/imported/2016/11/653.jpg
...and people moan about vi...:rofl:
OK then, "/opt or any other specified directory or path". Sheesh, I thought that would have been obvious!Quote:
Originally Posted by Troy
Don't complain. They were great roach material. Try skinning up with an SSD.Quote:
Originally Posted by harrybarracuda
You are Ada Lovelace and I claim my 4 Shillings and Eightpence!Quote:
Originally Posted by Troy
Except /opt used to be the preferred directory. However, you made me read up a bit on how things are in free linux distros and the standard procedure is to use package managers wherever possible and let them handle the install mechanism. You are correct and for anyone learning, this should be adopted in the first instance.Quote:
Originally Posted by DrB0b
When it comes to commercial distribution and for professional use then things get a little more complicated. The distro may use compilers and applications that are not in line with current software or Custoemr requirements. In these cases the older/newer versions should always go into a separate directory so they are not confused with the distro. The standard for this was always /opt and I have a separate partition for this directory.
It allows a reinstall of the basic distro and then a drop of the backup of /opt and /home directories to get you back up to speed quickly in the event of a hard disk failure.
Apologies if I confused or upset anyone with my total lack of ability in communicating my thoughts. It comes with having used one of those X-Y machines....
^^ I did progress, moving swiftly to a teletype terminal, complete with punch tape and modem connection...similar to:
https://teakdoor.com/images/imported/2016/11/654.jpg
I managed to kill the mainframe at GCHQ one Friday afternoon from Cheltenham GS....The first time I killed a machine with a bit of crap code but definitely not the last. Luckily the crap code is not generated quite so often as it once was....
Apologies for the thread drift....