Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: kernel param listings
Operating Systems HP-UX kernel param listings Post 302162790 by Perderabo on Wednesday 30th of January 2008 05:31:48 AM
Old 01-30-2008
You cannot create a kernel and a system file simultaneously so the timestamps are destined to be different. But which is newer? That is the question. The tools to create kernels vary fast with HP-UX, but with 11.11, here are some comments...

A copy of the system file used to create the kernel has been stored inside the kernel itself. To build a new kernel via the command line, HP suggests as a first step...
cd /stand/build
/usr/lbin/sysadm/system_prep -v -s system
This will suck the system file out of the kernel and deposit it /stand/build. The next step is to fiddle with some parameters with kmtune with -S /stand/build/system to use this particular system file. As you do, the system file changes and kmtune reports the changed value as "planned". It will become the real value if you proceed.

Unfortunately, HP then suggests you build the kernel via some steps that do not update /stand/system. Not a super big deal, since a new system file will be obtained to rebuild a kernel, but it leaves kmtune without a -S parameter a little bit in the dark. This is why I copy or move /stand/build/system to /stand/system as my last step in a kernel rebuild from the command line on 11.11. On the other hand, building a kernel via sam does update /stand/system correctly.

So this is why the confusion exists. Is your system file old and obsolete, or does it reflect your intentions for a change? Only you can say...
 

9 More Discussions You Might Find Interesting

1. Programming

sites with the listings

Is anybody know sites with the listings of simple programs for Linux (in text mode) (0 Replies)
Discussion started by: Studenttt
0 Replies

2. Programming

Listings of the games for Linux

Hello! I need tne listings of the very simple games(like mad builders or snake) in text mode, when is running only bash. If you got one, please send me on e-mail or post it just in this thread. I also need the following programms, if you have one of them or can quickly write it, please help me: 1)... (4 Replies)
Discussion started by: Studenttt
4 Replies

3. Shell Programming and Scripting

file listings by date

Hi all, First post, be gentle ;) OK I'm trying to list all files in a directory that are between x days and y days old, where I need to treat days as being from 00:00 to 23:59. i.e. a list of all files between 1 day and 8 days old would include all files between 00:00 8 days ago and 23:59 1... (1 Reply)
Discussion started by: Boothy
1 Replies

4. Solaris

listings file of a package

Hi, Is there a command to list all files within an installed package ? A command to print out a file's package owner ? I have trouble to install a temporary license for FTAM and OSI 9.0 on my sunfire280r and i suspect the licensing software is the reason... Any SUN guru out there ? Thanks (4 Replies)
Discussion started by: andryk
4 Replies

5. Programming

Fingerlines in GCC Listings

I recently moved from an AIX to a Linux environment, currently using GCC. I've searched the manpages, to no avail on this one. Q: Does gcc have an option to include finger lines in the listing? In other words, the equivalent compile option for AIX's -qsource and -qsrcmsg? If you don't know... (1 Reply)
Discussion started by: marcus121
1 Replies

6. Shell Programming and Scripting

displaying 3 directory listings in 3 separate columns.

i having problems figuring out how to 'read' in 3 different directory listings and then display them on the screen into 3 separate columns. i thought i could use a 'for' loop to grab each directory and then assign a unique variable to each line 'read' in. of course, as you experts all know,... (16 Replies)
Discussion started by: mjays
16 Replies

7. UNIX for Advanced & Expert Users

param with awk

Hi All, I have this script: #!/bin/ksh lsvg -l $1|grep -v $1:|grep -v LV|awk '{print "mklvcopy ",$1," 2 $2 $3"}' I want to pass three param with "vg2 hdisk1 hdisk2" but the output is "mklvcopy lv1 2 $2 $3". I want to pass the hdisk1 and hdisk2 and not the $2 and $3. Please help! ... (1 Reply)
Discussion started by: itik
1 Replies

8. Shell Programming and Scripting

param with awk

Hi All, I have this script: #!/bin/ksh lsvg -l $1|grep -v $1:|grep -v LV|awk '{print "mklvcopy ",$1," 2 $2 $3"}' I want to pass three param with "vg2 hdisk1 hdisk2" but the output is "mklvcopy lv1 2 $2 $3". I want to pass the hdisk1 and hdisk2 and not the $2 and $3. Please help! ... (3 Replies)
Discussion started by: itik
3 Replies

9. UNIX for Dummies Questions & Answers

sqlplus script out param

For starters, I have read the forums from top to bottom and cannot find a solution to this particular scenario. Just finished up two hours or scouring the archives. Here is my question which has been asked numerous times before but never fully explained for this particular solution: How do I pass a... (2 Replies)
Discussion started by: jwil0m0
2 Replies

LEARN ABOUT DEBIAN

build

build(1)						      General Commands Manual							  build(1)

NAME

       build - build SuSE Linux RPMs in a chroot environment

SYNOPSIS

       build [--clean|--no-init] [--rpms path1:path2:...]  [--arch arch1:arch2:...]  [--root buildroot] [specfile|srcrpm]
       build --help
       build --verify

DESCRIPTION

       build is a tool to build SuSE Linux RPMs in a safe and clean way.  build will install a minimal SuSE Linux as build system into some direc-
       tory and will chroot to this system to compile the package.  This way you don't risk to corrupt your working system (due to a  broken  spec
       file for example), even if the package does not use BuildRoot.

       build  searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed.	Otherwise a selec-
       tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified	rpms  have  to	be
       sufficient for the build.

       If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If
       a srcrpm is specified, build automatically unpacks it for the build.  If neither is given, build will use all the specfiles in the  current
       directory.

OPTIONS

       --clean
	      remove the build system and reinitialize it from scratch.

       --no-init
	      skip the build system initialization and start with build immediately.

       --list-state
	      list rpms that would be used to create a fresh build root.  Does not create the build root or perform a build.

       --rpms path1:path2:path3...
	      Where  build  can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari-
	      able.

       --arch arch1:arch2:arch3...
	      What architectures to select from the RPMs.  build automatically sets this to a sensible value for your host if  you  don't  specify
	      this option.

       --root buildroot
	      Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable.

       --useusedforbuild
	      Tell  build  not	to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none
	      are found, from all "BuildRequires" lines.  This option is useful if you want to re-build a package from a srcrpm with  exactly  the
	      same packages used for the srcrpm build.

       --norootforbuild

       --help Print a short help text.

       --verify
	      verify the files in an existing build system.

.spec FILE OPTIONS
       The build command interprets some special control comments in the specfile:

       # norootforbuild
       # needsrootforbuild
	      build  uses  either  user root or user abuild in the build system to do the build.  For non-SUSE distros as well as since SUSE 10.2,
	      the default build user is abuild.  For 10.2 and before, the default build user is root.  These two flags in the spec file  allow	to
	      deviate  from  the  defaults  and  force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec-
	      tively.

       # needsbinariesforbuild
	      provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root.

ENVIRONMENT

       BUILD_ROOT
	      The directory where build should install the chrooted build system.  "/var/tmp/build-root" is used by default.

       BUILD_RPMS
	      Where build can find the SuSE Linux RPMs.  build needs them to create the build system.	"/media/dvd/suse"  is  the  default  value
	      which will do the trick if you have the SuSE Linux DVD mounted.

       BUILD_RPM_BUILD_STAGE
	      The  rpm	build  stage  (-ba, -bb, ...).	This is just passed through to rpm, check the rpm manpage for a complete list and descrip-
	      tions.  "-ba" is the default.  You can use this to add more options to RPM.

SEE ALSO

       rpm(1),

       Maximum RPM:
	      http://www.rpm.org/max-rpm/

       cross distribution packaging:
	      http://en.opensuse.org/Build_Service/cross_distribution_package_how_to

       SUSE packaging standards and guidelines:
	      http://en.opensuse.org/Packaging

						  (c) 1997-2008 SuSE Linux AG Nuernberg, Germany					  build(1)
All times are GMT -4. The time now is 01:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy