summaryrefslogtreecommitdiff
path: root/service_solahart_jakarta_selatan__082122541663/mach-defpager_vs_defpager.mdwn
blob: f03bc67fd2695e57d466dc5ae0beba298a7c0dac (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
[[!meta copyright="Copyright © 2010, 2011 Free Software Foundation, Inc."]]

[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]

[[!tag open_issue_gnumach open_issue_hurd]]

IRC, freenode, #hurd, end of May/beginning of June 2010

    <cfhammar> whats the difference between mach-defpager and defpager?
    <cfhammar> i'm guessing defpager is a hurdish version that uses libstore
      but was never finished or something
    <cfhammar> found an interesting thread about it:
      http://mirror.libre.fm/hurd/list/msg01232.html
    <slpz> antrik: an interesting thread, indeed :-)
    <pochu> slpz: btw is mach-defpager linked statically but not called
      mach-defpager.static on purpose?
    <slpz> antrik: also, I can confirm that mach-defpager needs a complete
      rewrite ;-)
    <slpz> pochu: I think the original defpager was launched by serverboot
    <slpz> pochu: that could be the reason to have it static, like ext2fs
    <slpz> and since there's no need to execute it again during the normal
      operation of the system, they probably decided to not create a
      dynamically linked version
    <slpz> (but I'm just guessing)
    <slpz> of perhaps they wanted to prevent mach-defpager from the need of
      reading libraries, since it's used when memory is really scarce (guessing
      again)