I have a fresh installation of RHEL6 in front of me. For some reason there are no repo files in /etc/yum.repos.d/
What are the default repos to use so I can install packages?
To download software, updates, and security errata, your system should be registered to RHN.
For further information, have a look at these pages:
How do I access RHN Classic to download software, updates, and security errata?
Red Hat Network (RHN) Frequently Asked Questions
What is Yum and how do I use it?
Related
If I install stuff using brew or brew cask (on macOS) or npm or pip or composer or similar package/code/library managers, I have always wondered:
Where do they get their content from, who or what entity is managing or facilitating or hosting all those software or packages or modules or libraries?
Are there any checks, safety filters, audits, validation, or other mechanisms that prevent malware in the packages or libaries that are being distributed though these package managers?
Composer
List of packages is stored at https://packagist.org/, but there are only metadata. Packages are downloaded directly from related repositories (usually GitHub or GitLab), Packagist does not store or analyze its content. So while it may look a bit scary, the security model is based on trust to the vendor or direct code review. There is no magic solution which will pretend that it protects you from malware - you need to think what you're doing and what dependencies you're including into your project (or at least use some malware scanner on your own).
I would like to know from where does a package gets installed in Puppet when we write a manifest in Puppet for a package resource with below attribute.
ensure => installed,
I'm aware that there are providers in puppet which send the request to software installation tools on following path(/usr/lib/ruby/vendor_ruby/puppet/provider/package ) like yum, pip, gem, apt, etc which are responsible to get this done. However, i would like to know from which repository are these packages installed. Eg. like we configure a local yum repository when we want to install packages on the server via yum command.
Is it over the internet or the puppet nodes should be configured & connected to a local repository ? OR By default Puppet comes with pre-configured repositories for these software installation tools.
I would Appreciate a good explanation in this regards. Thanks in Advance.
If the puppet nodes should be connected to the internet or not is a question that you need to answer yourself in terms of how you would like your architecture to look like. Puppet only runs package install commands that should also work if you run it yourself in the shell, such as - yum install x , it doesn't matter if its over the internet or not.
It would work either way, and it depends on your repository configuration.
For example, yum repository configuration is under- /etc/yum.repos.d/*
You can see in the files there where it would go look for the packages you are trying to install
I have recently started using Atom editor. Its pretty great so far. I am planning to install it on several other machines.
How can I replicate the config and list of packages installed on my current machine to other machines. Is there a config that I can use to export and import them on other machines.
Use Git to version control your config file (~/.atom/config.cson), and any other config files (dotfiles) you may have.
You can then host your Git repository for free on somewhere like GitHub, and retrieve it on other computers simply by running git clone https://github.com/{username}/{repo}.
You can then keep it up to date using git push (to upload changes) and git pull (to download changes).
To track installed packages as well, you will need to run:
apm list --installed --bare > ~/.atom/package.list
And add that file to Git also. To restore, use:
apm install --packages-file ~/.atom/package.list
You can use the apm command to save/restore installed packages.
To export packages (only packages name):
apm list --installed --bare > ~/Gdrive/backup.txt
To import packages:
apm install --packages-file ~/Gdrive/backup.txt
On Linux apm is available if you install Atom from .deb file.
On OSX: open atom -> install shell command
Windows: apm in C:\Users\YOUR_NAME\AppData\Local\atom\bin
atom-package-sync is a package that I created a couple weeks ago. It works a little bit like the synchronization of Google Chrome, you just login and it syncs your packages and settings automatically across all your Atom instances.
I plan to release the source code for the server side in the coming weeks and add an export feature for alternative backups.
This question was already (if I understood you correctly) in how to sync Packages and settings for multiple computers in Github Atom Editor.
You might find the answer in a blog post I wrote. I hope it helps How to synchronize Atom between computers.
On OSX/macOS:
Open Terminal on the computer which has the settings you want to preserve / sync to others.
Move your ~/.atom folder to Dropbox or other synced service (~ represents your /users/<your_username> folder), like so:
mv ~/.atom ~/Dropbox/atom
Open terminal, and make a symlink that connects the place Atom expects its config to be (~/.atom), to your synced folder, like so:
ln -s ~/Dropbox/atom ~/.atom
On other computers you want to use these settings, open Terminal and run:
rm -rf ~/.atom && ln -s ~/Dropbox/atom ~/.atom
(This deletes the .atom folder and adds the symlink in one line.)
With this method, your settings are automatically in sync on each computer, no need to manually update anything.
The only potential bug I have noticed can occur if your settings specify a font which another computer does not have. Installing the font on that computer fixes. All packages, themes & settings installed by Atom are automatically there.
This same method can be used for many apps (WebStorm, Sublime Text, iTunes are a few examples).
The atom package manager supports starring packages, either online (through atom.io/packages and atom.io/themes) or on the commandline using
apm star <packagename>
or
apm star --installed
to star all of your installed packages.
Starred packages can then be easily installed using:
apm stars --install
Note that starring packages requires logging in to atom.io using your github account.
Install a package called sync-settings using atom package installer
Use Github Personal Access Token
And create Gist Secret for ~\username\.atom\config.cson file
On your primary Atom computer, navigate to packages > Synchronize Settings > backup
On target machines install sync-settings, then use Restore function from Synchronize settings.
Some of the packages that you had to run PIP, you would need to run pip on target machines as well, otherwise, you good to go.
I'm getting started with Vagrant and spent some time installing packages, setting up my DB and adding some data to the DB. Now that I have a base working box for my development environment, I would like to share this image with colleagues, that they can use as local VMs.
Is this not possible with vagrant? I just tried vagrant package and then destroyed it and did a vagrant up with my config.vm.box_url pointed to that packaged box location. To my dismay none of my installed packages, or files and configurations were included with my packaged vm.
Am I misunderstanding what vagrant is for or perhaps expecting vagrant to do something it's not designed to do here? If installed packages aren't the purpose of vagrant package, then what use cases is it for?
I've read through the docs and not found answers to these questions there.
Of course I can provision everything, and I'll get there too, but it's not what I'm getting at in this question.
I've since come to the conclusion that vagrant is basically for provisioning. If I need this I can just use virtual-box, but provisioning is a better approach because system packages and application dependencies etc. are a moving target.
Using provisioning allows future provisions to stay up to date and potentially expose incompatibilities.
I am getting following error while installing it
I already have git installed on eclipse
Help!!!
Cannot complete the install because one or more required items could not be found.
Software being installed: CloudBees Toolkit SVN Support (SUBVERSIVE MUST BE INSTALLED!!) (Optional) 2.0.2.201307232010 (com.cloudbees.eclipse.dev.scm.subversive.feature.group 2.0.2.201307232010)
Missing requirement: CloudBees Toolkit SVN Support (SUBVERSIVE MUST BE INSTALLED!!) (Optional) 2.0.2.201307232010 (com.cloudbees.eclipse.dev.scm.subversive.feature.group 2.0.2.201307232010) requires 'org.polarion.eclipse.team.svn.connector.feature.group 0.0.0' but it could not be found
Am I really suppose to install subversive
No you are not, indeed the SVN support is optional: you could just not install the Cloudbees svn support unchecking it before the installation.
But if you decide to proceed with the installation of the SVN support, then yes you would need subversive.