Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming > #4799 > unrolled thread
| Started by | "Bill Cunningham" <nospam@nspam.invalid> |
|---|---|
| First post | 2014-09-18 16:08 -0400 |
| Last post | 2014-09-19 15:50 -0400 |
| Articles | 3 — 2 participants |
Back to article view | Back to comp.programming
flat binary "Bill Cunningham" <nospam@nspam.invalid> - 2014-09-18 16:08 -0400
Re: flat binary Jongware <jongware@no-spam.plz> - 2014-09-19 11:36 +0200
Re: flat binary "Bill Cunningham" <nospam@nspam.invalid> - 2014-09-19 15:50 -0400
| From | "Bill Cunningham" <nospam@nspam.invalid> |
|---|---|
| Date | 2014-09-18 16:08 -0400 |
| Subject | flat binary |
| Message-ID | <lvfe4g$6ao$1@speranza.aioe.org> |
I just learned how with my compiler to create a "flat binary". Now I
understand a flat binary to be a binary file that has "no headers" am I
correct on that. My system uses ELF as it's executable format so making an
executable as a flat binary would be pointless It seems to me.
In what situations would a developer need "flat binaries"? GIFs as I
understand are flat binaries by there is a binary format descriptor of
course so the file can be identified. I really can't find out much on this
subject looking anywhere else so I thought I would inquire here.
Bill
[toc] | [next] | [standalone]
| From | Jongware <jongware@no-spam.plz> |
|---|---|
| Date | 2014-09-19 11:36 +0200 |
| Message-ID | <541bf92e$0$2950$e4fe514c@news2.news.xs4all.nl> |
| In reply to | #4799 |
On 18-Sep-14 22:08 PM, Bill Cunningham wrote: > I just learned how with my compiler to create a "flat binary". Now I > understand a flat binary to be a binary file that has "no headers" am I > correct on that. My system uses ELF as it's executable format so making an > executable as a flat binary would be pointless It seems to me. > In what situations would a developer need "flat binaries"? GIFs as I > understand are flat binaries by there is a binary format descriptor of > course so the file can be identified. I really can't find out much on this > subject looking anywhere else so I thought I would inquire here. The header in an executable file is to inform an OS of what's in the file, but if there is no OS to start with, headers are of no use. GIF is a bad example, because not every 'binary' is "executable code". GIF files *do* have a header, but since a GIF is not executable it's an irrelevant example. Example #1: boot code. Example #2: burn your code onto a chip. Example #3: a custom OS. [Jw]
[toc] | [prev] | [next] | [standalone]
| From | "Bill Cunningham" <nospam@nspam.invalid> |
|---|---|
| Date | 2014-09-19 15:50 -0400 |
| Message-ID | <lvi1e2$fmn$1@speranza.aioe.org> |
| In reply to | #4800 |
"Jongware" <jongware@no-spam.plz> wrote in message
news:541bf92e$0$2950$e4fe514c@news2.news.xs4all.nl...
The header in an executable file is to inform an OS of what's in the
> file, but if there is no OS to start with, headers are of no use.
>
> GIF is a bad example, because not every 'binary' is "executable code". GIF
> files *do* have a header, but since a GIF is not executable it's an
> irrelevant example.
>
> Example #1: boot code.
> Example #2: burn your code onto a chip.
> Example #3: a custom OS.
So these 3 examples are situations you would need a flat binary then. I
see.
Bill
[toc] | [prev] | [standalone]
Back to top | Article view | comp.programming
csiph-web