09-03-2009
You might want to get from a third party vendor for a cheaper rate.
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
How can I check if a Sun Ultra 10 workstation supports 40GB IDE drives?
Thanks! (6 Replies)
Discussion started by: oti
6 Replies
2. UNIX for Advanced & Expert Users
I still haven't got an answer to this question...
Excerpt from My SysAd Blog
A colleague of mine is having a problem with a Sun Fire v1280 server crashing. He tried Googling for the error message in red but hasn't found anything yet. Your insights would be greatly appreciated.
"cannot... (2 Replies)
Discussion started by: esofthub
2 Replies
3. UNIX for Dummies Questions & Answers
Hello all,
I'm lost and can't figure this problem out.
I have a Sun fire 280R running Solaris 8. Everything was working great. I have one drive in bay 1(not 0). But when I reboot the system it trys to open files in /dev/rdsk/c1t1d0s0. Should it have been opeing /dev/rdsk/c1t0d0s0, the... (4 Replies)
Discussion started by: larryase
4 Replies
4. Solaris
All,
After a power loss I went to power on our sun fire v120 that is running solaris 10 and now it will not boot. I tried power cycling it from the lom and pulling the cord but nothing works. All it does is after a power cycle it will start to boot and then start to spit out a bunch of hex... (2 Replies)
Discussion started by: jsandova
2 Replies
5. Solaris
Hi All,
My company has three V120 servers and two V245 servers. Currently we access ALOM on v245 thru NET MGT port. There are no NET MGT on V120. We use to access A/LOM on the V120s thru Windows Hyper Terminal connected to the Serial A port of v120. Since all of our Windows boxed are... (6 Replies)
Discussion started by: glieu
6 Replies
6. Solaris
I have come into my possesion a v120 server at work that was decommisioned from another project. I don't have the Solaris Installation CD nor do I have root or any user credentials on this server. My goal was to install OpenSolaris on this server and use it as a playground for learning UNIX... (6 Replies)
Discussion started by: stringzz
6 Replies
7. Solaris
I am new to Sun.
I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor?
Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies
8. Solaris
It's a DHCP server. We want to make a clone for fail over purpose since there are some identical systems available here. We do have a secondary DHCP server.
Hardware: Sun v120. OS: Solaris 9. Two disks without array, /var and /opt on the secondary disk.
How can I clone the system via network... (1 Reply)
Discussion started by: aixlover
1 Replies
9. Solaris
Hello,
I have purchaced an old SUn fire x2270 server .
I wanted to make ILOM upgrade to the latest version of software :
ILOM 3.0.9.18.a r126592
BIOS vers. 2.09
Server 2.2.3
(10-Aug-2018)
Because my version is very outdated.
But i can't download the updatebecause it's require... (4 Replies)
Discussion started by: LouisLakoute
4 Replies
LEARN ABOUT DEBIAN
emvendor
EMVENDOR(1) User Contributed Perl Documentation EMVENDOR(1)
Name
emvendor - retrieve vendor-specific package configuration strings
Synopsis
emvendor -V|--vendor VENDOR -p|--package PACKAGE -k|--key KEY
emvendor -?|-h|--help|--version
Commands
-v|--vendor VENDOR: the vendor name from dpkg-vendor
-p|--package PACKAGE: the package name (usually source)
-k|--key KEY: arbitrary string for the key of the data
All commands must be specified every time.
On success, the string is printed and emvendor exits with zero.
In the case of error, emvendor dies with an empty string on STDERR and exits with a non-zero return value.
Description
emvendor provides a way for debian/rules to call in a string for a particular package that fits into the rules for that package and
conforms to the requirements of the vendor.
http://wiki.debian.org/EmdebianAuditDetail#Vendor
It is fairly obvious that specifying each vendor in the debian/rules file of each package is not going to be particularly flexible.
DEB_VENDOR=$(shell dpkg-vendor --query vendor)
ifeq (Debian,$(DEB_VENDOR))
# Debian build
EXCONFARGS=--disable-mono --disable-monodoc
else
# any-vendor build
EXCONFARGS=$(shell emvendor --vendor $(DEB_VENDOR) --package avahi --key EXCONFARGS)
endif
or use the short options:
EXCONFARGS=$(shell foo-bar -V $(DEB_VENDOR) -p avahi -k EXCONFARGS)
The values themselves are in a vendor-specific conf file in /etc/emvendor.d/
$ cat /etc/foo-bar.d/emdebian-crush
[avahi]
EXCONFARGS=--disable-mono --disable-monodoc --disable-python
--disable-doxygen-doc --disable-pygtk --disable-python-dbus
--disable-core-docs --disable-qt3 --disable-qt4 --disable-gobject
--with-distro debian
[busybox]
foo=
(Note that the value has to be all on one line which is a little awkward - also note that values are not able to include the equals sign
which could be more of an issue.)
Packages that need two strings can do so - the key string is entirely arbitrary as long as it fits in the style of a typical ini file.
Therefore, the key can be matched to the needs of the relevant package.
"emdebian-buildsupport" provides /etc/emvendor.d/emdebian-crush with all the content for all packages that need such details.
emvendor and dpkg-vendor
dpkg-vendor supports vendor functionality but emvendor adds an extra hierarchy, organised by Debian source package name. It would be
possible to include the relevant strings in /etc/dpkg/origins/vendor but each identifier string would need to be unique across all packages
for each vendor, which is an unrealistic limitation.
perl v5.14.2 2012-09-26 EMVENDOR(1)