jmolloy / pedigree Goto Github PK

Pedigree operating system

Home Page: http://pedigree.googlecode.com

License: ISC License

Python 14.06% Perl 0.48% Assembly 0.60% C++ 27.64% Shell 1.09% PHP 0.01% C 55.10% Objective-C 1.00% R 0.02%

pedigree's Introduction

BUILD README
=======================

We highly recommend you first try one of our Easy Build scripts before you try
and run SCons manually. There's a little bit of work involved in setting up a
build of Pedigree for the first time - after that it's as easy as just running
"scons" at the command line.

Just run ./easy_build_x86.sh, ./easy_build_x64.sh, or ./easy_build_arm.sh to
build Pedigree for the relevant architecture. Dependencies and a cross-compiler
will be installed/created, allowing you to jump straight into testing Pedigree.

To build Pedigree at any point after this, just run "scons".

To switch between architectures, just remove "options.cache" before you re-run
an easy build script.

Alternatively, you can build manually if you already have a cross-compiler:

Required: SCons 1.2.0

Simply run:

scons CROSS=/path/to/compilers/bin/i686-pedigree-

You should give SCons the path to gcc in CROSS, ending in '-' so it can add
'gcc', 'g++' or 'as' to the end of the stub and get a valid compiler. It'll
work out from the compiler chosen what default options and what architecture
to compile.

Run "scons -h" to obtain a full set of arguments you can pass to configure
the build.

NOTE: This must be a full path. It cannot contain bash expansions such as
environment variables or '~'.

IMAGES DIRECTORY
=======================

The images/local directory allows you to use Pup, Pedigree's package manager,
to manage your hard disk image file set. If you ran the Easy Build script, pup
is already configured and ready to go.

Simply run:
    ./run_pup.py sync
to synchronise your local pup repository with the server.

Then you can run:
    ./run_pup.py install <package>
to install a package.

If you visit http://pup.pedigree-project.org/pup you can see a list of all
packages that are available and can be downloaded.

Remember to re-run SCons after installing a package to ensure your disk image
has the new package on it. You may need to 'rm build/hdd.img' if SCons doesn't
detect that the images directory has changed.

You can also add arbitrary files to the images/local directory to use them at
runtime. For example, you might create a directory under 'users' for yourself,
and add a .bashrc and .vimrc.

USERS
=======================

A utility script 'scripts/manage_users.py' is provided to add or remove users
from the database for use at runtime.

ISSUES
=======================

Report any issues on the project tracker at http://pedigree-project.org

pedigree's People

Contributors

Stargazers

Watchers

Forkers

vinoh108 ckkashyap pwn2w1n herolf nomadarchitect

pedigree's Issues

uptime fails to return information

Results in: uptime: couldn't get boot time: Not enough space

Since http://pedigree-project.org/ is down, pup can't get required dependencies, code can't be built.

The build scripts rely on http://pedigree-project.org/ existing and providing extra libraries required to build this code. Since this site is down, the code can't be built.

May I suggest that all the required dependencies be provided on GitHub?

'logout' over ssh doesn't end ssh connection

Typing 'logout' or ctrl-d keeps the connection alive, you can still type, but nothing happens.

Trying to run a shell script using ./ results in the DynamicLinker trying to run the script

If you try to execute a shell script (such as a configure script), or even a non shell script such as a C code file, then the DynamicLinker will try to execute the file and crash and burn as you would expect.

When executing a code file: breakpoint as it knows it aint an ELF.
When executing a shell script: pagefault

Running stty causes segfault

Running stty with no arguments, or 'stty onlcr' causes segmentation fault.

x86_64 SMP problem

I modified the script file:

!/bin/bash

SERIAL_PORTS="-serial file:./../build/serial.txt -serial file:./../build/memlog.txt"

if [ ! -z "$NO_SERIAL_PORTS" ]; then
SERIAL_PORTS=""
fi

AIO="native"

if [ ! "$(uname -s)" == "Linux" ]; then
AIO="threads"
fi

qemu-system-x86_64 -smp 4 -m 512
-drive file=./../build/hdd.img,if=ide,media=disk,cache=writeback,aio=$AIO,index=0,format=raw
-drive file=./../build/pedigree.iso,if=ide,media=cdrom,cache=writeback,aio=$AIO,index=2,format=raw
-boot d -vga std $SERIAL_PORTS -rtc base=utc $*

However, the system enters the exception handler...

Untitled

env causes segfault

Running 'env' results in a segmentation fault.

Untitled

Scons build scripts die in kernel link

Build line:

scons

Causes output:

Linking build/src/system/kernel/kernel
/home/james/.pedigree_2/bin/i686-elf-ld: -f may not be used without -shared
scons: *** [build/src/system/kernel/kernel] Error 1
scons: building terminated because of errors.

TimeoutGuard Breakpoint in ~TimeoutGuard

TimeoutGuard's destructor calls Thread::cullEvent if the event did not fire when it goes out of scope.

However, cullEvent currently has a FATAL("cullEvent"); line in it, making it impossible to use TimeoutGuard properly. I'm not sure why it has this line, but I assume there's a good reason.

Failing code:
Semaphore sem(0);

{
    TimeoutGuard guard(5);
    if (!guard.timedOut())
        NOTICE("Acquired sem");
}

NOTICE("Ended!");
for(;;);

If the semaphore acquire is not commented the timeout occurs as per normal, and there is no breakpoint.