Re: Newbie Header Q's

On Sun, Nov 08, 1998 at 01:47:28AM +, James wrote: ahh, that's a thing, what're te VI keys if your arrows don't work? h=left j=down k=up l=right also if you do not already know ... Ctrl-D=jumps down half a page (i think this is the right amount) Ctrl-U=jumps up half a page (")

pclose()

Does pclose() send an eof down the pipe or do I need to close it explicitly. The man page only stated that pclose wait4'd on the child process. Thanks Kevin Sivits ... [EMAIL PROTECTED] `:::' Kevin Sivits ... .. ::: * `::.::'one

Re: Bus error.

~ should produce similar (well almost) code. However, when in latter case I ~ run foo, I get Bus error(core dumped) message. Ideas what goes wrong here? ~ I think that's something to do with alignment, but not sure. ~ ~ Odd. Try adding `-g' to both commands and running the resulting ~

Re: Bus error.

~ gcc foo.c -o foo ~ and ~ gcc -S foo.c ~ gcc foo.s -o foo ~ ~ should produce similar (well almost) code. However, when in latter case I ~ run foo, I get Bus error(core dumped) message. Ideas what goes wrong here? ~ I think that's something to do with alignment, but not sure. ~ ~

Re: pclose()

Kevin Sivits wrote: Does pclose() send an eof down the pipe or do I need to close it explicitly. The man page only stated that pclose wait4'd on the child process. pclose() closes the pipe. If the other end was reading, it will get EOF. If it was writing, it will get SIGPIPE/EPIPE. --

RE: Bus error.

(gdb) where #0 0x20068c8e in ?? () #1 0x2007d060 in ?? () #2 0x2005c456 in ?? () #3 0x1646 in main () at foo.c:8 (gdb) isnt this a strange place for the program to be loaded (I cant remember seing programs in this address range... here's the code itself: #include stdio.h

RE: Bus error.

-- From: Glynn Clements[SMTP:[EMAIL PROTECTED]] Reply To: Glynn Clements Sent: 9. november 1998 10:07 To: [EMAIL PROTECTED] Cc: Linux C Programming List Subject: Re: Bus error. CyberPsychotic wrote: however, why would generate bus error? I

Do it for Yourself or We can Do it for You !

WANT TO DO IT YOURSELF Do you have a product or service that you want to market? Direct emailing is the most cost-effective way to advertise not only on the Internet, but out of any marketing media. Where else can you get your ad to millions for so little? 2 Million email

Re: Bus error.

~ The 80x86 architecture doesn't require that word accesses are aligned ~ to 4-byte boundaries (although you can force this to be the case by ~ setting a flag in the descriptor table entry, Linux doesn't do this). ~ ~ Searching for SIGBUS in the kernel source code indicates that it ~ occurs for

RE: Bus error.

~ #0 0x20068c8e in ?? () ~ #1 0x2007d060 in ?? () ~ #2 0x2005c456 in ?? () ~ #3 0x1646 in main () at foo.c:8 ~ (gdb) ~ ~ isnt this a strange place for the program to be loaded (I cant remember ~ seing programs in this address range... :-) yes.:-) -- 0x20 -- space, and so on..

Re: Checksums

On Sat, 7 Nov 1998, david wrote: Can someone explain how to compute checksums and how do they work ? Download GZIP and deflate compression specifications. They explain CRC (32-bit if my memory serves) and sample implementation. It was very easy to understand, even I did.

Re: Char device name block device

Glynn Clements wrote: Salil Kumar wrote: I have the block device name for disk, I want to find out associated raw device name. What do you mean by the `raw device'? I hope I got you correctly?We can access disk devices as raw/char and block devices.In the program I have the Block

Re: Char device name block device

Salil Kumar wrote: I have the block device name for disk, I want to find out associated raw device name. What do you mean by the `raw device'? I hope I got you correctly?We can access disk devices as raw/char and block devices.In the program I have the Block device name with me

Re: Char device name block device

What OS is this on? It doesn't look like anything that I've seen on Linux. My mistake, I assumed the case to be same for linux without crosschecking. Sorry about that.I am trying this on Solaris 2.x, and HPUX 11.0, currently. thanks, -Salil

Re: Checksums

Tuukka Toivonen wrote: Download GZIP and deflate compression specifications. They explain CRC (32-bit if my memory serves) and sample implementation. It was very easy to understand, even I did. I don't find it so easy ... : Spending 5 minutes reading the crc code, all i understood is that

Re: Newbie Header Q's

On Sun, 8 Nov 1998, Marc Evelyn wrote: Nah. They use ed. there's bits of that in VI, :q! and all that stuff. is it as bad as edlin?

Re: Char device name block device

These look like Solaris devices by the naming convention. Linux does not have raw devices that I know of. Does anyone else know differently. JP Glynn Clements wrote: Salil Kumar wrote: I have the block device name for disk, I want to find out associated raw device name. What

Re: (SPAM - HUNT) FW: Do it for Yourself or We can Do it for You !

On Mon, 9 Nov 1998, Mullen, Patrick wrote: I need your help with this one. I'm kinda confused on who originally sent this one. Received: from www.comune.collegno.to.it (atl-qbu-zpg-vty12.as.wcom.net [209.154.95.12]) by www.comune.collegno.to.it (8.8.6/8.8.6) with SMTP id

Cyclic redundancy Checks (was: Checksums)

Though you're original post mentioned checksums, the thread that has developed seems to be discussing Cyclic Redundancy Checks, which are quite different. If you really want to understand CRC's, the only thing which I have ever run across that explains them well was a document called "Painless

Re: Newbie Header Q's

James [on his mailserver] wrote: Nah. They use ed. there's bits of that in VI, :q! and all that stuff. All of vi's `:' commands are ex commands. is it as bad as edlin? Edlin is an ed clone. Obviously, ed isn't as newbie-friendly as a visual editor. OTOH, it does work on hardcopy