Slashdot Mirror

re 331: It's from BSD

Man Pages
Manual Reference Pages - ELF (5)

NAME
elf - format of ELF executable binary files CONTENTS

Synopsis
Description
See Also
History
Authors

SYNOPSIS

.In elf.h

DESCRIPTION

The header file
.In elf.h defines the format of ELF executable binary files. Amongst these files are normal executable files, relocatable object files, core files and shared libraries.

An executable file using the ELF file format consists of an ELF header, followed by a program header table or a section header table, or both. The ELF header is always at offset zero of the file. The program header table and the section header table's offset in the file are defined in the ELF header. The two tables describe the rest of the particularities of the file.

Applications which wish to process ELF binary files for their native architecture only should include .In elf.h in their source code. These applications should need to refer to all the types and structures by their generic names "Elf_xxx" and to the macros by "ELF_xxx". Applications written this way can be compiled on any architecture, regardless whether the host is 32-bit or 64-bit.

Should an application need to process ELF files of an unknown architecture then the application needs to include both .In sys/elf32.h and .In sys/elf64.h instead of .In elf.h . Furthermore, all types and structures need to be identified by either "Elf32_xxx" or "Elf64_xxx". The macros need to be identified by "ELF32_xxx" or "ELF64_xxx".

Whatever the system's architecture is, it will always include .In sys/elf_common.h as well as .In sys/elf_generic.h .

These header files describe the above mentioned headers as C structures and also include structures for dynamic sections, relocation sections and symbol tables.

...

[snippage]

...

HISTORY

The ELF header files made their appearance in Fx 2.2.6 . ELF in itself first appeared in AT&T V . The ELF format is an adopted standard.

This is the problem with SCO's case - OldSCO/Caldera only could have gotten what Novell originally had to give, if Novell HAD assigned copyrights to OldSCO. A lot of the stuff was from BSD.

I ask because your name is wrong, it should be a P not a p.

My nick is not wrong. You should drop the habit of assuming "Linux" every time you see something Unixy.

Which doesn't preclude me from having an Ubuntu install on my desktop. So, back to my original question: how do you play BluRay on Linux? So far as I can see, there is a messy workaround, in the best tradition of Linux HOWTOs circa late 90s, but it seems like a temporary solution at best (until the keys are revoked).

I didn't know about this feature set before, and appreciate the information. A little research on Google led me to a page on padlock, a "driver for the cryptographic functions and RNG in VIA C3, C7 and Eden processors."

From the description: "The C3 and Eden processor series from VIA include hardware acceleration for AES. The C7 series includes hardware acceleration for AES, SHA1, SHA256 and RSA. All of the above processor series include a hardware random number generator.

The padlock driver registers itself to accelerate AES operations and if available HMAC/SHA1 and HMAC/SHA256 for crypto(4). It also registers itself to accelerate other HMAC algorithms, although there is no hardware acceleration for those algorithms. This is only needed, so padlock can work with fast_ipsec(4)."

They really meant 'tun' of helium (man page found here: http://www.gsp.com/cgi-bin/man.cgi?section=4&topic=tun).

Well, according to one of the earlier posters: You can create a leaner hello world.

Well, that's not entirely fair, since he's just using a leaner library that you could use in C++, but the point remains that once the STL gets sucked in (since he apparently can't use shared libraries for some reason) your code is going to bloat up a lot faster than if you just grabbed the crusty old stdio stuff from libc.

Seriously though, if your platform only has 256k of main memory it would be a good idea to set up some sort of shared library mechanism, especially if you're sticking with the unix philosophy of lots of small tools to get the job done. At the very least consider something like Crunchgen to avoid loading duplicate code into memory.

No kidding, some other people's source in comparision sometimes feels like a child's homework essay next to a master's printed novel.

ssh

[/reinvent-wheel]

which is when the UNIX 32 bit time representation wraps round - I doubt that anyone will survive. Think of all the coding effort that that will save and the Y2K type panics!

I initially ran apt-cache search gasp, which turned up nothing relevent. I suppose I should have tried harder to figure it out.

Bah, who am I kidding? This is Slashdot!

There's also the Unix 2038 problem.

gif doesn't have fricking transparency

I'm not sure about the "fricking" type of transparency. But GIF89s have had transparency for a while.

This is a web site that claims the cookie expires in 2038 because of pending 'brain implants.'

Surely it couldn't be because they're using a large number of 32-bit UNIX-like systems, and that there's the UNIX epoch in all UNIX-like OSes on 32-bit systems is 2038.

I mean, that'd just be kha-raaaaaaazie!1! It's obvious that they set the cookie to 2036 so they could steal our Precious Bodily Fluids. Where's the tin foil? Where?

Err. Yah. Yah, at that point I think it's safe to say anything on the site can be honestly diregarded as bunk. Or at best poorly writen SciFi. Either way, it's relationship with reality is on the rocks, and reality is already calling it's mother and a divorce laywer.

Those 80-100 lines of code SCO is referring to were from BSD. Bruce and others said it shouldn't have been there and got rid of it because it was a bad implementation.

Actually I believe SCO showed two examples.

The first was an implementation of a simple malloc routine. That was traced back to a C language book written by Richie(?) back in the 70s, and you're right, the code had already been removed from the 2.5 kernel.

The second was the BPF (Berkeley Packet Filter) which had been ported to BSD back in the 80s.

Of course, SCO (those sterling guardians of intellectual property) were claiming the copyright on both of them.

certain hardware manufacturers utterly refuse to support anything other than Windows

Since you mentioned you did some coding, you may want to check out Linux Device Drivers plus some of their other kernel tweaking/modding books.

Buying a book isn't going to get her the board spec, unfortunately. To get the job done quickly, she'll need the board spec.

Otherwise, she could start by using the generic pci driver to probe the board's parameters in freebsd, or use phob to observe the board's parameters.

This would be an excellent chore for a grad student, as it would provide her with a useful skill while not really interrupting her studies of, e.g. The Effect of Gamma Rays on Man-in-the-Moon Marigolds

I read this article a few days ago and bookmarked most of the links I thought valueable. If anyone else is interested add some more to this thread so I can grab them :)

Exported bookmarks Fingerprint
blackhole(4) - a sysctl(8) MIB for manipulating TCP
Help Net Security OS-FngrPrint article in PDF
Honeyd - Network Rhapsody for You
http://ojnk.sourceforge.net/stuff/iplog.readme
http://www.insecure.org/nmap/nmap-fingerprinting-a rticle.txt
IP Personality - Home
Kernel Options
p0f file listing
PhoneBoys FireWall-1 FAQs: Blocking queSO packets
s0ftpr0ject 2000 Fingerprint Fucker
Security Technologies
SourceForge.net: Project Info - SING
Sys-Security.com - Because Security is not Trivial
USENIX Technical Program - Abstract - Security Symposium - 2000

I only found out recently, but FreeBSD has realtime support, accessable via POSIX realtime API.

Check out the "rtprio" call on FreeBSD:

man rtprio

It really is quite good - even for "normal" uses. Give your mp3 player an rtprio value via command line and it will never "chop" or "stutter" again, even under the heaviest of loads. Set XFree86 to have a "rtprio" via command line and it runs so much more responsively (even that Linux IMHO).

While your at it set:

options HZ=1000

In your kernel configuration and you have a realtime capable system, with really low latency (thanks to the hz value). :o)

Another option as well as the Linux options...

Jamie Burns.

I was under the impression that jail(2) did that, too.

My bad.

http://www.gsp.com/2038/ states 19 Jan 2038 at 03:14:07 as the rollover date.