Sponsored Content
Full Discussion: Relocatable code, Etcetera
Top Forums UNIX for Dummies Questions & Answers Relocatable code, Etcetera Post 302573685 by theKbStockpiler on Tuesday 15th of November 2011 09:03:48 AM
Old 11-15-2011
I managed to find this Doc.

Introduction to System Software



I have no Idea if this is copywriten so I'll leave off the abbreviation for hyper text transfer protocol.

://www.google.com/url?sa=t&rct=j&q=introduction%2Bto%2Bsystem%2Bsoftware&source=web&cd=3&ved=0CDkQFjAC&url=http%3A%2F% 2Fwww.itswtech.org%2FLec%2FManal(system%2520programming)%2Fch4_8086_Architecture.pdf&ei=2G7CTtSIIIj0 2QWm7d3RDg&usg=AFQjCNGwfFe-FE1GCEbKChWL7sFACZSJNQ&cad=rja
 

7 More Discussions You Might Find Interesting

1. Linux

relocatable kernel

Hi, Is relocatable feature available in SLES? If it is can anyone please tell me the kernel version.. ~Nayana. (0 Replies)
Discussion started by: nayana
0 Replies

2. Linux

Find installed location of a relocatable package

Hi, I am finding the installed location of a package by: rpm -qi <package_name> And then parse the string "Relocations". If i relocate this package during installation with --relocate option , the "Relocations" string still shows the old value. Though the package has been installed on the... (0 Replies)
Discussion started by: vibhor_agarwali
0 Replies

3. AIX

AIX relocatable package help

Hi, I have created a relocatable AIX package named Test. The USIL is /abc bash-2.05b# lsusil INSTALL PATH = /abc COMMENTS = None Generally if a package gets installed in "/opt/Test" and i want to relocate it to "/abc" it gets installed under "/abc/Test". This happens the way in Solaris,... (2 Replies)
Discussion started by: vibhor_agarwali
2 Replies

4. AIX

Uninstall a relocatable package

Hi, If a package has been installed at normal location: installp -u <package_name> uninstalls the package However, if that has been installed relocatable, the above command fails. It requires the relocatable path as the parameter installp -R <relocation_path> -u <package_name> To find... (1 Reply)
Discussion started by: vibhor_agarwali
1 Replies

5. UNIX for Dummies Questions & Answers

If ‘922’ Code does not exist on ‘03’ Record, ‘901’ Code will be there instead, move ‘03’ R

01,011600033,011600033,110516,0834,2,90,,2/ 02,011600033,011103093,1,110317,0834,,2/ 03,105581,,015,+00000416418,,,901,+00000000148,,,922,+000000 00354,,/ 03,113806,,015,+00000559618,,,901,+00000000096,,,922,+000000 00621,,/ 88,902,+0000000025218,,/... (1 Reply)
Discussion started by: sgoud
1 Replies

6. Shell Programming and Scripting

Block of code replacement in Java source code through Unix script

Hi, I want to remove the following code from Source files (or replace the code with empty.) from all the source files in given directory. finally { if (null != hibernateSession && hibernateSession.isOpen()) { //hibernateSession.close(); } } It would be great if the script has... (2 Replies)
Discussion started by: hareeshram
2 Replies

7. UNIX for Dummies Questions & Answers

Can't install rpm package with --prefix in new path.Error: package is not relocatable

Hello, i have downloaded an rpm package "hadoop-0.20.205.0-1.amd64.rpm" in /usr/local/ directory. I'm trying to install the rpm package in a new path/location (/usr/local/hadoop-0.20.205), but i can't. I did: 1st try: Didn't work sudo rpm -i --prefix=/usr/local/hadoop-0.20.205... (1 Reply)
Discussion started by: g_p
1 Replies
GIT-CHERRY(1)							    Git Manual							     GIT-CHERRY(1)

NAME
git-cherry - Find commits yet to be applied to upstream SYNOPSIS
git cherry [-v] [<upstream> [<head> [<limit>]]] DESCRIPTION
Determine whether there are commits in <head>..<upstream> that are equivalent to those in the range <limit>..<head>. The equivalence test is based on the diff, after removing whitespace and line numbers. git-cherry therefore detects when commits have been "copied" by means of git-cherry-pick(1), git-am(1) or git-rebase(1). Outputs the SHA1 of every commit in <limit>..<head>, prefixed with - for commits that have an equivalent in <upstream>, and + for commits that do not. OPTIONS
-v Show the commit subjects next to the SHA1s. <upstream> Upstream branch to search for equivalent commits. Defaults to the upstream branch of HEAD. <head> Working branch; defaults to HEAD. <limit> Do not report commits up to (and including) limit. EXAMPLES
Patch workflows git-cherry is frequently used in patch-based workflows (see gitworkflows(7)) to determine if a series of patches has been applied by the upstream maintainer. In such a workflow you might create and send a topic branch like this: $ git checkout -b topic origin/master # work and create some commits $ git format-patch origin/master $ git send-email ... 00* Later, you can see whether your changes have been applied by saying (still on topic): $ git fetch # update your notion of origin/master $ git cherry -v Concrete example In a situation where topic consisted of three commits, and the maintainer applied two of them, the situation might look like: $ git log --graph --oneline --decorate --boundary origin/master...topic * 7654321 (origin/master) upstream tip commit [... snip some other commits ...] * cccc111 cherry-pick of C * aaaa111 cherry-pick of A [... snip a lot more that has happened ...] | * cccc000 (topic) commit C | * bbbb000 commit B | * aaaa000 commit A |/ o 1234567 branch point In such cases, git-cherry shows a concise summary of what has yet to be applied: $ git cherry origin/master topic - cccc000... commit C + bbbb000... commit B - aaaa000... commit A Here, we see that the commits A and C (marked with -) can be dropped from your topic branch when you rebase it on top of origin/master, while the commit B (marked with +) still needs to be kept so that it will be sent to be applied to origin/master. Using a limit The optional <limit> is useful in cases where your topic is based on other work that is not in upstream. Expanding on the previous example, this might look like: $ git log --graph --oneline --decorate --boundary origin/master...topic * 7654321 (origin/master) upstream tip commit [... snip some other commits ...] * cccc111 cherry-pick of C * aaaa111 cherry-pick of A [... snip a lot more that has happened ...] | * cccc000 (topic) commit C | * bbbb000 commit B | * aaaa000 commit A | * 0000fff (base) unpublished stuff F [... snip ...] | * 0000aaa unpublished stuff A |/ o 1234567 merge-base between upstream and topic By specifying base as the limit, you can avoid listing commits between base and topic: $ git cherry origin/master topic base - cccc000... commit C + bbbb000... commit B - aaaa000... commit A SEE ALSO
git-patch-id(1) GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-CHERRY(1)
All times are GMT -4. The time now is 01:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy