01-05-2010
New to linux. Which distro should i use?
want to know which Linux distro is 4 me. want 2 teach my self programing and problem solving. i want to learn code and write code. i have an acer aspire one 2GB memory 160 GB HDD intel Atom. look im as noobie as it gets im a MS xp, vista boy want to go beyond graphical click and do... any help sweet thanx BizilStank
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
I'm have old toshiba laptop(t1900) 486, 4mbRAM and ~120MB of hdd
I'm looking for distro to suite my comp, no need for X windows but not enything that runs on FAT, just normal small Linux.
Actually, *BSDs will do as well. If u know any distro that would do this I will be thankful for hint
... (4 Replies)
Discussion started by: wolk
4 Replies
2. UNIX for Advanced & Expert Users
Hola. Here is how my partition table looks:
Device Boot Start End Blocks Id System
/dev/hde1 1 1689 13566861 7 HPFS/NTFS
/dev/hde2 * 1690 2783 8787555 83 Linux
/dev/hde3 2784 2813 240975 82 Linux swap
/dev/hde4 ... (5 Replies)
Discussion started by: Mr_Proper
5 Replies
3. Shell Programming and Scripting
hello ALL,
I wander, is there an easy way to get information which linux distro and its version a script runs on?
I'm looking for a function like getDistroInfo(), which would return strings like "Ubuntu7.10" or "SLES10" or "RHEL5" etc.
uname returns lots of stuff, but distro info.... (1 Reply)
Discussion started by: Samtim74
1 Replies
4. AIX
Hi,
I would like to know, is there a thing that AIX would do it, and RHEL or SLES would not? Something specific and great in the same time.
It might sound weird, but I'm very curios.
Thanks a lot guys! (7 Replies)
Discussion started by: aixn00b
7 Replies
5. What is on Your Mind?
I have been using Linux OS since 4 years and I'm very interested to know how to create a Linux Distro. I have heard about LFS.
I would just like to know, what do I need to create a Linux Distro?
I'm not a programmer, if I have to create a Linux Distro, what programming languages do I need to... (3 Replies)
Discussion started by: Auzern
3 Replies
6. Linux
I hate the fact that my first post is this. Anyhow, I've been using Linux distros such as Ubuntu, Fedora, Debian, openSUSE, and a few others for quite some time now. I've never had a problem with any distro, thus saying that they were all good in my opinion. I've been reading a lot on different... (2 Replies)
Discussion started by: Vex
2 Replies
7. UNIX for Advanced & Expert Users
Hi all, for a while now I've been working on a linux distro and I'm a couple of tweaks away from it to be perfected so if any experts want to help me out please message me.
Thanks in advance.
(I know I've posted a similar thread on the same topic but it was closed due to an unhelpful title... (0 Replies)
Discussion started by: allk
0 Replies
8. Linux
Hello,
I have a Compaq Presario v3000 5 year old laptop, with 1 GB RAM and currently running the (slow and stupid) Windows 7 32 bit, thus I would like to dual boot it with an appropriate distro of Linux that
1) Doesnt consume too much resources (1 GB RAM is not a lot of space) and it ll be... (4 Replies)
Discussion started by: ajayram
4 Replies
9. Open Source
What is your favorite Linux distro?
and possibly why?
Personally, I have Fedora 3 on my computer. I have used Ubuntu and Slackware, too. But I think I liked Ubuntu more, maybe because of its speed and easy installation of packages. (192 Replies)
Discussion started by: milhan
192 Replies
LEARN ABOUT OSF1
isobjbuilt
atom_object_management(5) File Formats Manual atom_object_management(5)
NAME
atom_object_management, BuildObj, IsObjBuilt, WriteObj, ReleaseObj - Allows an Atom tool's InstrumentAll routine to build, release, and
write objects
SYNOPSIS
#include <cmplrs/atom.inst.h>
unsigned BuildObj(
Obj * ); unsigned IsObjBuilt(
Obj * ); void WriteObj(
Obj * ); void ReleaseObj(
Obj * );
DESCRIPTION
Atom's object management routines allow an Atom tool's InstrumentAll routine to build, write, and release objects.
You can use these routines only from an Atom tool's instrumentation file. See atom(1) for a description of Atom.
An InstrumentAll routine must call the BuildObj routine before calling AddCallObj to add analysis routine calls to the object and before
traversing the procedures in the object. BuildObj builds the internal data structures Atom uses to manipulate the object. After the Atom
tool traverses and instruments the object, the InstrumentAll routine must call the WriteObj routine to write out the instrumented version
of the object. For example:
unsigned InstrumentAll(int iargc, char **iargv) {
Obj * obj;
AddCallProto("Startup()");
AddCallProto("Finish()");
AddCallProto("foo(int, REGV)");
AddCallProgram(ProgramBefore, "Startup");
AddCallProgram(ProgramAfter, "Finish");
for (obj = GetFirstObj(); obj; obj = GetNextObj(obj))
{
if (BuildObj(obj))
return(1);
/* instrument obj */
WriteObj(obj);
}
return(0); }
The WriteObj routine writes the instrumented version of the specified object, deallocating the internal data structures BuildObj previously
created.
Note that BuildObj may return an error code. It returns a nonzero value (and issues an appropriate error message) if it encounters an error
in the executable file for the Obj0. You should propagate this error value back to Atom by returning 1 from InstrumentAll.
The ReleaseObj routine deallocates the internal data structures for the given object, but does not write out the instrumented version the
object. You should not call ReleaseObj if you have added any analysis routine calls to the object.
The IsObjBuilt routine returns a nonzero value if the specified object has been built with BuildObj, but not yet written with WriteObj or
unbuilt with ReleaseObj.
Whenever possible, tools should build and write out each object only once. Some tools, however, may build and release an object several
times, ultimately writing out its instrumented version. This can be very time-consuming for a tool with very large objects.
Similarly, tools should normally build only one object at a time. Certain tools may simultaneously build several objects, instrument each
one, and then write each out. This has advantages for tools that call ResolveNamedProc or ResolveTargetProc. However, having more than one
large object built at a single time will cause Atom to run slowly and to consume a large amount of memory.
RETURN VALUES
These routines return values as described above.
FILES
Header file containing external definitions of Atom routines
SEE ALSO
Commands: atom(1)
AtomTools: hiprof(5), pixie(5), third(5)
Functions: atom_application_instrumentation(5), atom_application_query(5), atom_application_navigation(5), atom_description_file(5),
atom_application_resolvers(5), atom_instrumentation_routines(5), AnalHeapBase(5), Xlate(5), Thread(5)
Programmer's Guide
atom_object_management(5)