comp.os.linux.development.system

• Thread Index

---

• Re: smp kernel : netperf
  • From: David Schwartz
• Re: error: error: can't find a register in class BREG' while reloading `asm'
  • From: Neel
• Re: error: error: can't find a register in class BREG' while reloading `asm'
  • From: Tim Roberts
• Re: error: error: can't find a register in class BREG' while reloading `asm'
  • From: David Schwartz
• error: error: can't find a register in class BREG' while reloading `asm'
  • From: Neel
• Re: hotplugging eSATA
  • From: phil-news-nospam
• Re: One socket - multiple ifaces
  • From: Dildo Bogumil di Boscopelo
• One socket - multiple ifaces
  • From: pitrew
• smp kernel : netperf
  • From: MB
• Re: hotplugging eSATA
  • From: Eric
• Re: Weirdness on Linux
  • From: Janaka
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: Lew Pitcher
• Re: regarding device driver
  • From: Grant Edwards
• Weirdness on Linux
  • From: keith
• Re: iopl
  • From: Rafael C. Almeida
• Re: regarding device driver
  • From: David Schwartz
• regarding device driver
  • From: siva
• Re: Reliable Vfat (or any reliable windows filesystem in linux)
  • From: Mark Hobley
• Re: Reliable Vfat (or any reliable windows filesystem in linux)
  • From: Mark Hobley
• Re: Reliable Vfat (or any reliable windows filesystem in linux)
  • From: GürüPràçäd
• Re: complie kernel 0.11
  • From: Waldek Hebisch
• Re: Reliable Vfat (or any reliable windows filesystem in linux)
  • From: Måns Rullgård
• Reliable Vfat (or any reliable windows filesystem in linux)
  • From: GürüPràçäd
• Re: iopl
  • From: David Schwartz
• iopl
  • From: Rafael C. Almeida
• Re: Module reference count
  • From: Mapisto
• Re: Module reference count
  • From: Mapisto
• Module reference count
  • From: Mapisto
• Re: How to generate Linux version flag at compile time, run time, from rpm spec.
  • From: Guido Scholz
• Re: UNICODE system calls?
  • From: Måns Rullgård
• Re: UNICODE system calls?
  • From: phil-news-nospam
• Re: How to trace a process with ptrace when it forks a new process ?
  • From: phil-news-nospam
• Re: UNICODE system calls?
  • From: takeout
• Re: UNICODE system calls?
  • From: Bob Hauck
• UNICODE system calls?
  • From: takeout
• Re: how to know a user application quit
  • From: Jan Kandziora
• Re: Problem with "Wake on Lan"
  • From: Josef Moellers
• Re: Problem with "Wake on Lan"
  • From: Jörg Schmitz-Linneweber
• Re: how to know a user application quit
  • From: Rainer Weikusat
• Re: how to know a user application quit
  • From: Jan Kandziora
• Re: How to trace a process with ptrace when it forks a new process ?
  • From: Zheng Da
• Re: How to generate Linux version flag at compile time, run time, from rpm spec.
  • From: adar
• Problem with "Wake on Lan"
  • From: Guenther Sohler
• How to generate Linux version flag at compile time, run time, from rpm spec.
  • From: adar
• fastes way to write to disk (mmap, write, ...)
  • From: Klaus Klingenbusch
• msync/fsync - block process or thread ?
  • From: Klaus Klingenbusch
• Re: How to trace a process with ptrace when it forks a new process ?
  • From: phil-news-nospam
• Re: How to trace a process with ptrace when it forks a new process ?
  • From: John Reiser
• Re: How to trace a process with ptrace when it forks a new process ?
  • From: Zheng Da
• Re: how elevator algorithm works in modern hard disks?
  • From: phil-news-nospam
• Re: How to trace a process with ptrace when it forks a new process ?
  • From: phil-news-nospam
• Re: how elevator algorithm works in modern hard disks?
  • From: Josef Moellers
• Re: how elevator algorithm works in modern hard disks?
  • From: forrest
• Re: serial port does not work on PC104
  • From: scstop
• Re: How to trace a process with ptrace when it forks a new process ?
  • From: John Reiser
• How to trace a process with ptrace when it forks a new process ?
  • From: Zheng Da
• Re: how elevator algorithm works in modern hard disks?
  • From: Josef Moellers
• how elevator algorithm works in modern hard disks?
  • From: forrest
• Re: findfirst, findnext and finddata_t
  • From: phil-news-nospam
• how to know a user application quit
  • From: Keep Asking
• Re: linux kernel and the desktop
  • From: Linonut
• Re: findfirst, findnext and finddata_t
  • From: Linonut
• Re: hotplugging eSATA
  • From: AZ Nomad
• Re: hotplugging eSATA
  • From: AZ Nomad
• hotplugging eSATA
  • From: phil-news-nospam
• UIO driver modules
  • From: Mike
• Re: linux kernel and the desktop
  • From: phil-news-nospam
• Re: linux kernel and the desktop
  • From: Bill Marcum
• Re: linux kernel and the desktop
  • From: Rainer Weikusat
• linux kernel and the desktop
  • From: cczjason
• Re: dxf parser
  • From: Joe Beanfish
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: fat_boy
• dxf parser
  • From: Guenther Sohler
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: Josef Moellers
• Re: serial port does not work on PC104
  • From: Mark Hobley
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: Grant Edwards
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: Grant Edwards
• Re: Problem with SSH connection
  • From: phil-news-nospam
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: phil-news-nospam
• Re: findfirst, findnext and finddata_t
  • From: phil-news-nospam
• Re: Problem with SSH connection
  • From: Guenther Sohler
• Re: findfirst, findnext and finddata_t
  • From: Linonut
• Re: findfirst, findnext and finddata_t
  • From: Linonut
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: Josef Moellers
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: Wolfgang Draxinger
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: fat_boy
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: fat_boy
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: Tim Roberts
• Re: Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: Lew Pitcher
• Hi all, knew to Linux, been doing Windows drivers for over ten years though, whats a good book?
  • From: fat_boy
• Re: How to find out the actual available serial ports on a system?
  • From: Neil Cherry
• Re: serial port does not work on PC104
  • From: scstop
• Re: How to find out the actual available serial ports on a system?
  • From: Grant Edwards
• Re: How to find out the actual available serial ports on a system?
  • From: Mike
• Re: How to find out the actual available serial ports on a system?
  • From: David Schwartz
• Re: Problem with SSH connection
  • From: phil-news-nospam
• Re: Problem with SSH connection
  • From: Guenther Sohler
• Re: serial port does not work on PC104
  • From: Mark Hobley
• Re: serial port does not work on PC104
  • From: scstop
• Re: How to find out the actual available serial ports on a system?
  • From: Neil Cherry
• Re: How to find out the actual available serial ports on a system?
  • From: Neil Cherry
• Re: How to find out the actual available serial ports on a system?
  • From: Mark Hobley
• Re: How to find out the actual available serial ports on a system?
  • From: Dances With Crows
• Re: How to find out the actual available serial ports on a system?
  • From: John Reiser
• Re: serial port does not work on PC104
  • From: Mark Hobley
• Re: serial port does not work on PC104
  • From: scstop
• Re: serial port does not work on PC104
  • From: Mark Hobley
• Re: concurrent calls to system(const char *)
  • From: Rainer Weikusat
• Re: serial port does not work on PC104
  • From: scstop
• Re: concurrent calls to system(const char *)
  • From: Tim Roberts
• Re: Question on interrupt stats and probe
  • From: Ramesh
• Re: serial port does not work on PC104
  • From:
• Re: Question on interrupt stats and probe
  • From: Gil Hamilton
• Re: Mapping Kernel memory to user space
  • From: Ramesh
• Question on interrupt stats and probe
  • From: Ramesh
• Solved - Was: weird, boot CPU (#0) not listed by the BIOS.
  • From: phil-news-nospam
• Problem with SSH connection
  • From: Guenther Sohler
• serial port does not work on PC104
  • From: scstop
• Re: msync - using MS_SYNC and MS_ASYNC interleaved
  • From: Rainer Weikusat
• msync - using MS_SYNC and MS_ASYNC interleaved
  • From: Klaus Klingenbusch
• Re: kernel module build with errors dos2unix or make system or my bug??
  • From: Jothy
• Re: concurrent calls to system(const char *)
  • From: Anthony GEAY - SFME/LGLS
• Re: concurrent calls to system(const char *)
  • From: David Schwartz
• concurrent calls to system(const char *)
  • From: anthony . geay
• Re: findfirst, findnext and finddata_t
  • From: Rainer Weikusat
• Re: findfirst, findnext and finddata_t
  • From: Rainer Weikusat
• Re: findfirst, findnext and finddata_t
  • From: Chris Friesen
• Re: findfirst, findnext and finddata_t
  • From: Rainer Weikusat
• Re: findfirst, findnext and finddata_t
  • From: David Schwartz
• Re: kernel module build with errors dos2unix or make system or my bug??
  • From: Bill Marcum
• kernel module build with errors dos2unix or make system or my bug??
  • From: Jothy
• Re: findfirst, findnext and finddata_t
  • From: phil-news-nospam
• Re: findfirst, findnext and finddata_t
  • From: phil-news-nospam
• Re: complie kernel 0.11
  • From: Bill Marcum
• Re: gcc inline asm
  • From: Rainer Weikusat
• Re: gcc inline asm
  • From: Rainer Weikusat
• Re: gcc inline asm
  • From: Tim Roberts
• Re: findfirst, findnext and finddata_t
  • From: Rainer Weikusat
• Re: findfirst, findnext and finddata_t
  • From: David Schwartz
• Re: findfirst, findnext and finddata_t
  • From: David Schwartz
• Re: findfirst, findnext and finddata_t
  • From: Lew Pitcher
• Re: findfirst, findnext and finddata_t
  • From: phil-news-nospam
• Re: findfirst, findnext and finddata_t
  • From: Måns Rullgård
• Re: USB attached memory card reader weirdness
  • From: phil-news-nospam
• Re: findfirst, findnext and finddata_t
  • From: phil-news-nospam
• Re: findfirst, findnext and finddata_t
  • From: phil-news-nospam
• Re: findfirst, findnext and finddata_t
  • From: Uwe Bonnes
• Re: findfirst, findnext and finddata_t
  • From: David Schwartz
• Re: USB attached memory card reader weirdness
  • From: phil-news-nospam
• Re: Question on pci-configuration space
  • From: Tim Roberts
• Re: findfirst, findnext and finddata_t
  • From: Rainer Weikusat
• Re: findfirst, findnext and finddata_t
  • From: David Schwartz
• Re: findfirst, findnext and finddata_t
  • From: Roger Leigh
• findfirst, findnext and finddata_t
  • From: Michel
• Re: Question on pci-configuration space
  • From: John
• Re: DMA curiosity
  • From: Rainer Weikusat
• Question on pci-configuration space
  • From: srblinux@xxxxxxxxx
• Re: Mapping Kernel memory to user space
  • From: Janaka
• Re: DMA curiosity
  • From: Janaka
• DMA curiosity
  • From: Rainer Weikusat
• Re: Mapping Kernel memory to user space
  • From: Milind Dumbare
• Re: USB attached memory card reader weirdness
  • From: Wolfgang Draxinger
• Re: Looking for jukebox software
  • From: Wolfgang Draxinger
• Mapping Kernel memory to user space
  • From: MAx
• Re: Accessing the same data defined in a shared object from multiple processes
  • From: pritamganguly
• Re: Accessing the same data defined in a shared object from multiple processes
  • From: Paul Pluzhnikov
• Accessing the same data defined in a shared object from multiple processes
  • From: pritamganguly
• USB attached memory card reader weirdness
  • From: phil-news-nospam
• Re: weird, boot CPU (#0) not listed by the BIOS.
  • From: Tris Orendorff
• Re: Looking for jukebox software
  • From: Tris Orendorff
• Re: question on Ethernet Devicedriver
  • From: Rainer Weikusat
• weird, boot CPU (#0) not listed by the BIOS.
  • From: phil-news-nospam
• question on Ethernet Devicedriver
  • From: srblinux@xxxxxxxxx
• pthreads, wait for multiple conditions?
  • From: takeout
• Re: fsync
  • From: Rainer Weikusat
• Re: fsync
  • From: David Schwartz

• Security
• UNIX
• Linux
• Coding
• Usenet

• Mailing-Lists
• Newsgroups
• About
• Privacy
• Search
• Imprint

linux.derkeiler.com  > Newsgroups  > comp.os.linux.development.system  > 2008-01