04-30-2015
the boot and root floppies are from a different identical system, there are 4 of these system running on site. they were all purchased at the same time, I have been told all parts are identical in them. I cannot take the tools down to do a component level check on these to verify so I have to take their word on this. But the original vendor for these historically did use all the same parts until there was a different version to eliminate hardware issues.
Sorry if the pic is bad quality, It looked good when I took it. I cannot get a better picture at this point.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hello guys The company i work for just got a new client, there old datebase is in Unix SCO openserver 5.0.5.
The manager of this new client can login but not as a root , they forgot there own root password. There old IT company never gave it to them and they have no way of getting a hold of them
... (2 Replies)
Discussion started by: josramon
2 Replies
2. SCO
Hi!
Sorry, but I am'not spesialist in SCO OpenServer. I need to add hard disk from SCO Open Server ( "a") in my SCO OpenServer 5.6. I need data from "a". When I added, I see only swap disk, and didn't see root file system. I need to add IDE and SCSI
Please, help me. How right to add disk?... (0 Replies)
Discussion started by: fedir
0 Replies
3. SCO
Hi,
I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone.
I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies
4. SCO
I would like to expand the size of the root area, currently 800 kb, to a size of 2000 kb. Is that possible to do without loosing any data in the /u area? There is plenty of space available in the /u area. (2 Replies)
Discussion started by: pschnell
2 Replies
5. SCO
I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd.
I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies
6. Solaris
Hi all
I wish to mirror for the root disk, but last time i do, make the server cannot boot up. :p So this time, hope you guys can assist me on it. =)
At the last code, is the step i wish to do. Please help to check and correct me if got any wrong.
root@leo # format </dev/null
Searching for... (17 Replies)
Discussion started by: SmartAntz
17 Replies
7. SCO
DEAR Team,
I need some help in sco open server 5
while booting server beloow message giving server
HTFS no space dev HD 1/42
Thanks
Skb (4 Replies)
Discussion started by: sudhir69
4 Replies
8. Solaris
Hi All
Hope it's okay to post on this sub-forum, couldn't find a better place
I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
9. SCO
Hi,
We have an old SCO Openserver 5.0.7 server that I have inherited that currently has two issues that we are trying to resolve.
1. We do not know the root password. I have contacted the old admin, looked for rescue disk and documentation but there appears to be nothing.
I have tried... (1 Reply)
Discussion started by: acerimmer10
1 Replies
LEARN ABOUT DEBIAN
bundle-package
BUNDLE-PACKAGE(1) BUNDLE-PACKAGE(1)
NAME
bundle-package - Package your needed .gem files into your application
SYNOPSIS
bundle package
DESCRIPTION
Copy all of the .gem files needed to run the application into the vendor/cache directory. In the future, when running bundle install(1)
bundle-install.1.html, use the gems in the cache in preference to the ones on rubygems.org.
GIT AND PATH GEMS
In Bundler 1.0, the bundle package command only packages .gem files, not gems specified using the :git or :path options. This will likely
change in the future.
REMOTE FETCHING
By default, if you simply run bundle install(1) bundle-install.1.html after running bundle package(1) bundle-package.1.html, bundler will
still connect to rubygems.org to check whether a platform-specific gem exists for any of the gems in vendor/cache.
For instance, consider this Gemfile(5):
source "http://rubygems.org"
gem "nokogiri"
If you run bundle package under C Ruby, bundler will retrieve the version of nokogiri for the "ruby" platform. If you deploy to JRuby and
run bundle install, bundler is forced to check to see whether a "java" platformed nokogiri exists.
Even though the nokogiri gem for the Ruby platform is technically acceptable on JRuby, it actually has a C extension that does not run on
JRuby. As a result, bundler will, by default, still connect to rubygems.org to check whether it has a version of one of your gems more spe-
cific to your platform.
This problem is also not just limited to the "java" platform. A similar (common) problem can happen when developing on Windows and deploy-
ing to Linux, or even when developing on OSX and deploying to Linux.
If you know for sure that the gems packaged in vendor/cache are appropriate for the platform you are on, you can run bundle install --local
to skip checking for more appropriate gems, and just use the ones in vendor/cache.
One way to be sure that you have the right platformed versions of all your gems is to run bundle package on an identical machine and check
in the gems. For instance, you can run bundle package on an identical staging box during your staging process, and check in the ven-
dor/cache before deploying to production.
June 2012 BUNDLE-PACKAGE(1)