Hi,
First post here!
I have a Sun V210 that I use occasionally for build testing things big-endian. I switched it on the other day, at it aint comin' up. I was wondering if anyone on this fine forum knows if it can be brought back from the dead.
With the SCC card in, and conencted to... (22 Replies)
Purchased a Sun Surefire V210 Server off eBay. Unable to Access the Terminal Mode via the Terminal MGT. Using Windows 7 home, and downloaded the ConEmu.
The ConEmu brings up a Command line on the PC, and that's it.
Being new to all this, I was expecting a Login prompt to pop up. Read the... (22 Replies)
I have bought from eBay a second hand Sun Fire V210 server and I'm really stumped at the lack of complete instructions on how to connect to it.
I don't have a Windows machine, I've only got Ubuntu and OS X computers. None of them have an old RS-232 port on them either.
In saying that, I have... (12 Replies)
Sun Fire V210, No Keyboard
Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.13.2, 4096 MB memory installed, Serial #61203679.
Ethernet address 0:3:ba:a5:e4:df, Host ID: 83a5e4df.
Boot device: net File and args:
100 Mbps FDX Link up
Timeout waiting for... (5 Replies)
Is there anyway to get a USB DVD ROM to work on a V210/V240/V440 SPARC systems for initial installation? I'm drawing a blank and I can't seem to find any documentation on this. (3 Replies)
I'm currently trying to move a perfectly find harddrive from a V210 to a V440. From what I can tell, the disk labeling a bit different, (V210 is c1t0d0 and V440 is c0t0d0). My question is, what all do I have to change to get the V440 to boot off of this with very little complications. Right now, it... (21 Replies)
I recently acquired a server for home use. Currently, I'm running a V210. I was wondering of a way to basically swap hard drives into the V440.
I would like to avoid reinstall on the V440 for many reasons.
Currently on the V440, when I try to boot up it forces itself into System Maintenance... (1 Reply)
Hi,
When I insert a cd to CDROM drive in SF V210 Solaris 10 it took seconds then eject it auto!
How can I solve this issue?
Thanks
Regards :) (8 Replies)
BUNDLE-EXEC(1)BUNDLE-EXEC(1)NAME
bundle-exec - Execute a command in the context of the bundle
SYNOPSIS
bundle exec command
DESCRIPTION
This command executes the command, making all gems specified in the Gemfile(5) available to require in Ruby programs.
Essentially, if you would normally have run something like rspec spec/my_spec.rb, and you want to use the gems specified in the Gemfile(5)
and installed via bundle install(1) bundle-install.1.html, you should run bundle exec rspec spec/my_spec.rb.
Note that bundle exec does not require that an executable is available on your shell's $PATH.
BUNDLE INSTALL --BINSTUBS
If you use the --binstubs flag in bundle install(1) bundle-install.1.html, Bundler will automatically create a directory (which defaults to
app_root/bin) containing all of the executables available from gems in the bundle.
After using --binstubs, bin/rspec spec/my_spec.rb is identical to bundle exec rspec spec/my_spec.rb.
ENVIRONMENT MODIFICATIONS
bundle exec makes a number of changes to the shell environment, then executes the command you specify in full.
o make sure that it's still possible to shell out to bundle from inside a command invoked by bundle exec (using $BUNDLE_BIN_PATH)
o put the directory containing executables (like rails, rspec, rackup) for your bundle on $PATH
o make sure that if bundler is invoked in the subshell, it uses the same Gemfile (by setting BUNDLE_GEMFILE)
o add -rbundler/setup to $RUBYOPT, which makes sure that Ruby programs invoked in the subshell can see the gems in the bundle
It also modifies Rubygems:
o disallow loading additional gems not in the bundle
o modify the gem method to be a no-op if a gem matching the requirements is in the bundle, and to raise a Gem::LoadError if it's not
o Define Gem.refresh to be a no-op, since the source index is always frozen when using bundler, and to prevent gems from the system leak-
ing into the environment
o Override Gem.bin_path to use the gems in the bundle, making system executables work
o Add all gems in the bundle into Gem.loaded_specs
Shelling out
When shelling out (using the system or backticks methods, for example), Bundler's environment changes will propagate to the subshell envi-
ronment. If you desire to shell out without Bundler's environment changes, simply employ the with_clean_env method. It will restore all
environment variables to what they were before Bundler was activated. For example:
Bundler.with_clean_env do
`brew install wget`
end
RUBYGEMS PLUGINS
At present, the Rubygems plugin system requires all files named rubygems_plugin.rb on the load path of any installed gem when any Ruby code
requires rubygems.rb. This includes executables installed into the system, like rails, rackup, and rspec.
Since Rubygems plugins can contain arbitrary Ruby code, they commonly end up activating themselves or their dependencies.
For instance, the gemcutter 0.5 gem depended on json_pure. If you had that version of gemcutter installed (even if you also had a newer
version without this problem), Rubygems would activate gemcutter 0.5 and json_pure <latest>.
If your Gemfile(5) also contained json_pure (or a gem with a dependency on json_pure), the latest version on your system might conflict
with the version in your Gemfile(5), or the snapshot version in your Gemfile.lock.
If this happens, bundler will say:
You have already activated json_pure 1.4.6 but your Gemfile
requires json_pure 1.4.3. Consider using bundle exec.
In this situation, you almost certainly want to remove the underlying gem with the problematic gem plugin. In general, the authors of these
plugins (in this case, the gemcutter gem) have released newer versions that are more careful in their plugins.
You can find a list of all the gems containing gem plugins by running
ruby -rubygems -e "puts Gem.find_files('rubygems_plugin.rb')"
At the very least, you should remove all but the newest version of each gem plugin, and also remove all gem plugins that you aren't using
(gem uninstall gem_name).
March 2013 BUNDLE-EXEC(1)