Linux-Development-Sys Digest #499

2001-02-18 Thread Digestifier

Linux-Development-Sys Digest #499, Volume #8 Mon, 19 Feb 01 03:13:09 EST

Contents:
  Two variables in two dlls with the same name. (Thaddeus L Olczyk)
  Re: ioremap and virt_to_phys (Jonathan Lundell)
  Re: 2.4.1 won't mount /dev/hdb1 as root (Neal Tucker)
  Re: Module Programming Question (Unresolved symbol printk) (Weirong Zhu)
  Re: mmap limits (Tim Roberts)
  Re: mmap limits (Ulrich Weigand)
  Re: Big Brother is watching youplease read   
.  9696 (Allodoxaphobia)
  Re: SCSI Programming - READ_CAPACITY ("Uncle Nick")
  atomic pointer reads/writes (Dave Peterson)
  ENOMEM from poll (Kaelin Colclasure)
  Re: Module Programming Question (Unresolved symbol printk) ("Paul Pluzhnikov")
  Re: Two variables in two dlls with the same name. ("Arthur H. Gold")
  Re: Beginner : Device driver (John Brockmeyer)
  Re: Module Programming - problem when including certain header files (John 
Brockmeyer)
  Re: ioremap and virt_to_phys (Pete Zaitcev)
  Re: ENOMEM from poll ([EMAIL PROTECTED])
  Problem in Module 



From: [EMAIL PROTECTED] (Thaddeus L Olczyk)
Subject: Two variables in two dlls with the same name.
Date: Mon, 19 Feb 2001 01:14:13 GMT
Reply-To: [EMAIL PROTECTED]

I was at a Borland demo of Kylix and the guy claimed that
you could not have two variables/functions with the same name in two
different dlls, it they are loaded statically ( at startup ).
He wasn't sure if you  could load them dynamically ( dlopen, dlsym (I
think)).
Is this trtue, what about dynamic loading?

--

From: Jonathan Lundell <[EMAIL PROTECTED]>
Subject: Re: ioremap and virt_to_phys
Date: Sun, 18 Feb 2001 17:26:04 -0800

In article <96pigj$20q$[EMAIL PROTECTED]>, [EMAIL PROTECTED] 
wrote:

> Can someone please sort out the following for me. Why doesn't
> (virt_to_phys(ioremap(physical_address,range)) == physical_address)
> evaluate to true?  If ioremap(physical_address,range) yields a virtual
> address, then what is virt_to_phys(ioremap(physical_address,range))?
> Is it a physical address?  To understand why I'm asking, here is
> what I'm trying to accomplish.

I assume we're talking x386 here. virt_to_phys() only works for the 
kernel's statically mapped memory. The kernel maps memory starting at 
physical 0 to virtual 0xc000. All virt_to_phys() does is subtract 
0xc000 from the virtual address. That doesn't work for dynamically 
mapped addresses such as those returned by ioremap(). It *should*, or at 
least there should be a general virtual-to-physical converter, but if 
there is I haven't been able to find it.

I haven't tested this, but something like the following should be able 
to do the trick for addresses returned by ioremap(). It should probably 
be smart enough to know when to call virt_to_phys() too, but

(pte_val(*pte_offset(pmd_offset(pgd_offset_k(va), (va)), (va))) & 
PAGE_MASK) + (va & ~PAGE_MASK)

-- 
/Jonathan Lundell.
[EMAIL PROTECTED]

--

From: [EMAIL PROTECTED] (Neal Tucker)
Subject: Re: 2.4.1 won't mount /dev/hdb1 as root
Date: 18 Feb 2001 17:58:57 -0800

Kasper Dupont  <[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] wrote:
>> Something must be
>> missing in the 2.4.1 kernel you have, like maybe the IDE driver
>> or the ext2 filesystem.
>> 
>
>At this point a more informative errormessage would be nice.
>Like: "can't mount device "341" as root because no block device
>is registered with major number 3".

That's a great idea.  How likely is it to get patches for stuff
like this accepted?

-Neal Tucker

--

From: Weirong Zhu <[EMAIL PROTECTED]>
Subject: Re: Module Programming Question (Unresolved symbol printk)
Date: Sun, 18 Feb 2001 20:06:58 -0600

I got the exactly same problem on my desktop. But it is not MP. So I guess it
has nothing to do with processor. I checked /proc/ksysm, there is no printk
symbol there. I tried to recompile my kernel with module support but this
problem stays. Did you get it work on your desktop now?

Weirong
[EMAIL PROTECTED]

Mudit wrote:

> Greeting,
>
> I'm trying to get up to speed on module programming. I typed the Hello World
> example from http://howto.tucows.com/LDP/LDP/lkmpg/node11.html (included
> below). It compiles ok (makefile also below). When I do an "insmod hello.o"
> from outside of X, I get:
>
> hello.o: unresolved symbol printk
>
> I'm guessing I'm missing something obvious. Any clues? I'm using RedHat 6.2.
> I believe my kernel has module support (I do an lsmod and there are modules
> loaded).
>
> Thanks,
> Mudit
>
> ---

Linux-Development-Sys Digest #499

1999-03-17 Thread Digestifier

Linux-Development-Sys Digest #499, Volume #6 Wed, 17 Mar 99 14:14:24 EST

Contents:
  CDR and Adaptec-1505 driver probs. (Frans Grotepass)
  Re: Threads and clone() (Roope Anttinen)
  Re: After Week 1 With Linux -- licking wounds. (Peter Samuelson)
  Re: kernel (Enrique Robledo Arnuncio)
  Re: After Week 1 With Linux -- licking wounds. (Alexander Viro)
  Re: After Week 1 With Linux -- licking wounds. (Peter Samuelson)
  Re: After Week 1 With Linux -- licking wounds. (Johan Kullstam)
  Re: After Week 1 With Linux -- licking wounds. (Mark Tranchant)
  newsgroup for fpk/ppc386 under linux (Thomas)
  Re: After Week 1 With Linux -- licking wounds. (Robert Krawitz)
  Re: Threads and clone() (accoday)
  select_wait (Wlmet)
  Re: kernel won't uncompress when boot from CD (Julian Robert Yon)
  Re: After Week 1 With Linux -- licking wounds. (Robert Krawitz)
  Re: Threads and clone() (Stefan Monnier)
  Re: After Week 1 With Linux -- licking wounds. (Anthony Ord)



From: Frans Grotepass <[EMAIL PROTECTED]>
Subject: CDR and Adaptec-1505 driver probs.
Date: Wed, 17 Mar 1999 16:03:52 +0200

I have driver problems it seems with my SCSI CDR.  I have an
adaptec-1505 controlling my 4020 HP CDR and a Connor harddrive. I bootup
on an IDE drive and I am presently running kernel 2.2.3.  I still have
the problems after upgrading from 2.0.36.  The problem arrises that.
when ripping with cdda2wav,  the system will simply hang under certain
circumstances.  The CD usually has a scratch on it and the process will
hang at the scratch.  The whole system dies.  I am not even capable to
access the system through ssh or even telnet.. The machine doesn't even
ping.  Under 2.0.36 I found that the cdda2wav will fall over and the
process willnot be removable from the process list, not even with kill
-9.

If anybody has any idea what is happening.  it would be cool,  since I'm
completely puzzled.   I am going to try cdparanoia again though.

Frans Grotepass



--

From: Roope Anttinen <[EMAIL PROTECTED]>
Subject: Re: Threads and clone()
Date: 17 Mar 1999 14:03:53 GMT
Reply-To: [EMAIL PROTECTED]

H. Reinecke <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Mike Delaney) writes:
> > Now, what I'd like to know is: Are we going to see the threads start sharing
> > the same PID, as the POSIX draft dictates?
> Errm, to achieve what ?
> I can't really think of a necessity for that, apart from being POSIX
> enslaved.

For example to be able to write some kind of "Task manager" which can tell
the amount of threads inside a process. You could with the recent approach
try to compare the size of processes inside a process family but that's not
very reliable way to identify a thread.

Roope

-- 
MicroSoft? is that some kind of a toilet paper?
PS: Look for address here, not from headers. And remove NOSPAM's
___
   [EMAIL PROTECTED]  /  [EMAIL PROTECTED]
+358 9 812 7567  /  +358 500 445 565  /  +358 49 445 565
http://myy.helia.fi/~anttiner/index.html
===
   Helsinki Business Polytechnic - Institute of information technology

--

From: [EMAIL PROTECTED] (Peter Samuelson)
Crossposted-To: comp.os.linux.advocacy,comp.os.linux.questions
Subject: Re: After Week 1 With Linux -- licking wounds.
Date: 17 Mar 1999 08:11:29 -0600
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>

[Steve Smith <[EMAIL PROTECTED]>]
> Most Windoze users don't read the manual.  (Big surprise, right? :-)
> Also, most Windoze users are not technical types, and are terrified
> of experimentation.  Might mess up the system.

To be fair, they come by it honestly.  Between personal experience and
peer advice, everyone knows that Windoze can get messed up -- freezing
and sometimes needing to be reinstalled -- more or less unpredictably.
And, furthermore, they know that this is not uncommon.  No wonder
Windoze users are gun-shy.

-- 
Peter Samuelson


--

From: Enrique Robledo Arnuncio <[EMAIL PROTECTED]>
Subject: Re: kernel
Date: Wed, 17 Mar 1999 15:18:13 +0100

Eldhose John wrote:
> 
> Hi,
> I am new comer to Linux. I wanted to find out how the kernel works,
> so I searched through the source code. But it was an unplesent experince
> I could not find any starting point. Please help me to solve the mistory.

The starting point is in fact architecture-dependent. You can find that
kind of stuff under arch/xxx/boot. Most of it is asm, some of it is
real-
mode code (for the i386). If you are interested in the detailed startup
files 
sequence, I can give you details for the i386 arch, 2.0.36 kernel
version 
(I don't think there have been any