Sponsored Content
Operating Systems Solaris error in jumpstart while cretaing rules.ok with ./check Post 302357725 by seg on Wednesday 30th of September 2009 12:23:12 PM
Old 09-30-2009
Edit the rules file and comment out or remove the line that references sample_host.
 

8 More Discussions You Might Find Interesting

1. Solaris

Jumpstart Error

I 've configured jumpstart and everything is fine but the installation starts asking human intervention and go till NFS conifugration .. Setting up Java. Please wait... Serial console, reverting to text install Beginning system identification... Searching for configuration file(s)... Using... (3 Replies)
Discussion started by: fugitive
3 Replies

2. Solaris

Error after Jumpstart

I have a Solaris 10 U6 flash nothing has changed on my Jumpstart expect for some finish files and profiles. after I jump either a client or a server I always get the same error the following files in / differ from the boot archive changed /kernel/drv/md.conf then I enter in the root... (4 Replies)
Discussion started by: deaconf19
4 Replies

3. Solaris

boot Error for jumpstart

Hi community, I am installing Solaris 10 using a jumpstart installation. Both Server and Client are in the same netmask. When I perform the "boot net - install" command, I receive the following error: Timeout waiting for ARP/RARP packets Timeout waiting for ARP/RARP packets Timeout... (1 Reply)
Discussion started by: Sunb3
1 Replies

4. Solaris

Jumpstart client flash archive error....

Hi , I am facing this issue while restoring flash archive from jumpstart server.The image was aroung 9 gb (5.9 release) and we have restored the other images successfully bigger than this size to other machines we have never faced this issue .Please advice me on this issue . Extracted 100 %... (0 Replies)
Discussion started by: knl.sundeep
0 Replies

5. Solaris

Jumpstart -- Warning: Could not find matching rule in rules.ok

I just setup a new jumpstart server, and I'm having problems with rules.ok errors. I'm coming up blank after many Google searches, forum searches, etc..... This is the error I receive: Skipped interface e1000g1 Attempting to configure interface e1000g0... Configured interface e1000g0... (0 Replies)
Discussion started by: christr
0 Replies

6. Solaris

Jumpstart Error: Unsupported version (3.0).

Hello, The OS version of the ZFS flar is Solaris 10 U9 . Here is the screen output from my attempted jumpstart: System identification is completed. System identification complete. Starting Solaris installation program... Searching for JumpStart directory... Using rules.ok from... (5 Replies)
Discussion started by: Siralos
5 Replies

7. Solaris

help me! jumpstart installation error

Hi actualy my two machines are sun sparc ultra 60. Both are same configuration. I am trying jumpstart Installation in my two machines, i got no errors in server side but in the client side actually it detects the server machine with correct hostname and domainname but after showed that it will... (2 Replies)
Discussion started by: Grovestreet
2 Replies

8. Solaris

Solaris 10 Jumpstart Error

Hey All, I'm trying to jump start a new Sun Server from an existing jump start server, but this last machine is giving me driver errors :s It doesn't make sense as we've built a few of these exact same servers just recently, but this last one displays: "No driver (or driver binding)... (2 Replies)
Discussion started by: UnxAdm1101
2 Replies
MAVEN(1)							   User Commands							  MAVEN(1)

NAME
Maven - Patches the POM files using the Maven dependency rules. SYNOPSIS
mh_patchpoms [option]... DESCRIPTION
Reads the file debian/$package.poms and tranform each POM file listed in the .poms file into a POM file using the Debian versions of the libraries. Also keeps a backup of each POM file which can be restored with mh_unpatchpoms OPTIONS
-h --help: show this text -V --version: show the version -p<package> --package=<package>: package to act on -k --keep-pom-version: keep the original version of the POMs but, convert all other versions in dependencies and plugins If there is a parent POM, keeps its version except when the parent is already registered in the Maven repository -e<version>, --set-version=<version>: set the version for the POM, do not use the version declared in the POM file. -r<rules> --rules=<rules>: path to the file containing the rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules -R<rule>, --extra-rule=<rule>: extra rule to apply when cleaning the POM May occur multiple times, instead of or in addition to -r -u<rules> --published-rules=<rules>: path to the file containing the extra rules to publish in the property debian.mavenRules in the cleaned POM. Optional, the default location is debian/maven.pub- lishedRules -U<rule>, --extra-published-rule=<rule>: extra rule to publish May occur multiple times, instead of or in addition to -u -i<rules> --ignore-rules=<rules>: path to the file containing the rules used to remove certain dependencies from the cleaned POM Optional, the default location is debian/maven.ignoreRules -I<rule>, --extra-ignore-rule=<rule>: extra rule used to remove dependencies from the transformed POM May occur multiple times, instead of or in addition to -i -c<rules> --clean-ignore-rules=<rules>: path to the file containing the rules use to remove certain dependencies from the cleaned POM, in addition to the ignore rules specified previously. This is useful in situations such as when the Maven clean target requires more dependencies or plugins to ignore than the build target. All rules defined in clean-ignore-rules will be added to the existing rules in ignore-rules. Optional, the default location is debian/maven.cleanIgnoreRules -s --no-rules: don't apply any rules for converting versions, do not even convert versions to the default 'debian' version --no-publish-used-rule: don't publish the rule used to transform a POM's own attributes in debian.mavenRules -d --debian-build: transform during a Debian build, which means that some POM elements will be removed -b --build-no-docs: if the build doesn't need to build documentation, use this option to remove some POM elements (in particular plugins) which are useless here and may require extra dependencies and make the packaging harder. -m<repo root>--maven-repo=<repo root>: location of the Maven repository, used to force the versions of the Maven plugins used in the current POM file with the versions found in the repository -v --verbose: show more information while running -n --no-act: don't actually do anything, just print the results See also: mh_installpoms(1), mh_patchpom(1) Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)
All times are GMT -4. The time now is 08:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy