1 |
<!DOCTYPE html> |
2 |
<html> |
3 |
<head> |
4 |
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> |
5 |
<title>MidnightBSD Developers</title> |
6 |
<link rel="shortcut icon" href="/favicon.ico"> |
7 |
<link rel="stylesheet" type="text/css" href="../css/essence.css"> |
8 |
</head> |
9 |
|
10 |
<body> |
11 |
<div id="globe"> |
12 |
<div id="header"><h1 title="MidnightBSD Home"><a href="../" title="MidnightBSD Home">MidnightBSD: The BSD For Everyone</a></h1></div> |
13 |
<!--#include virtual="/menu.html"--> |
14 |
<div class="clear"></div> |
15 |
<div id="text"> |
16 |
<h2 class="icon"><img src="../images/oxygen/developer32.png" alt="Developer"> Welcome to MidnightBSD Development</h2> |
17 |
<div class="devupdate fleft"> |
18 |
<h4>Update: (February 2012)</h4> |
19 |
<blockquote> |
20 |
<p>Our current big project is replacing sysinstall with a modified version of bsdinstall from FreeBSD 9.0-RELEASE. As part |
21 |
of this project, several major changes have been made to GEOM in the kernel. MidnightBSD now supports it's own |
22 |
GPT partition schemes, and understands GPT types from several other operating systems including Microsoft Windows, |
23 |
Apple Mac OS X (and Apple TV), Linux, FreeBSD and NetBSD.</p> |
24 |
|
25 |
<p>mport has had several improvements. An article on mport tools appeared in the February 2012 issue of BSD Magazine.</p> |
26 |
|
27 |
<p>The OpenBSD sensors framework code was updated to use fine grain locking along with many sysctl's in 0.4-CURRENT. This |
28 |
should improve performance.</p> |
29 |
|
30 |
<p>Apple's mDNSResponder 330.10 was recently imported.</p> |
31 |
|
32 |
<p>Several stability problems have been corrected in the 0.4-CURRENT kernel introduced in November. CURRENT kernels now |
33 |
have WITNESS and INVARIANTS enabled by default. This slows down performance, but allows us to catch a lot of subtle problems. |
34 |
Historically, this was disabled after a buggy patch was introduced to the TCP network stack years ago. This code was replaced |
35 |
during development of 0.3.</p> |
36 |
|
37 |
<p>The release building architecture is undergoing significant changes to work with the new installer. Current documentation on |
38 |
this process is out of date and one should look at the src/Makefile, src/Makefile.inc1 and release/* for the current procoess. |
39 |
</p> |
40 |
</blockquote> |
41 |
<h4>Update: (September 2011)</h4> |
42 |
<blockquote> |
43 |
<p>ctriv@ started the libmport project several years ago. Today, we have a functioning replacement for pkg_tools |
44 |
on MidnightBSD. We're in the bug fixing phase for the next release.</p> |
45 |
<p>Perl has been updated to 5.14 in CURRENT. We've got most of Gnome 2.32 working, KDE 3.5.10, X.org 7.4 (plus some updates), |
46 |
and I'm in the process of updating GNUstep to the latest version. Several Etoile ports are now on 0.4.1. Opera 11.51, |
47 |
Linux versions of Firefox 6 and Thunderbird 6 work on current with some minor problems, Flash 10, Chrome 5 (needs updating badly), |
48 |
and openjdk 6.</p> |
49 |
<p>MidnightBSD gained a new search tool called msearch. This uses sqlite3 to index files on the system. It contains |
50 |
a list of files that can be searched with sql queries using sqlite3 or on the command line and a full text |
51 |
index of files on the system. The indexer runs out of periodic as nobody so really sensitive files can be hidden |
52 |
as necessary by changing the permissions. While gzip compression is used with the full text index and some |
53 |
logic with libmagic helps us avoid indexing some files, the database sizes can be rather large on some systems. It's |
54 |
recommended that one only use this if they have a large /var partition over 5GB.</p> |
55 |
</blockquote> |
56 |
<h4>Update: (March 2011)</h4> |
57 |
<blockquote> |
58 |
<p>MidnightBSD 0.3-RELEASE was shipped a little over a month ago. Since then, we've focused on getting contributed |
59 |
software up-to-date as well as work on mport tools. 0.4 will be the first release with mport tools as default. |
60 |
</p> |
61 |
</blockquote> |
62 |
<h4>Update: (May 2009)</h4> |
63 |
<blockquote> |
64 |
<p>ctriv@ has been testing libmport and the mport tools for the 0.3 release. We're currently working on |
65 |
importing GCC 4.2.1 into src. We now use bsdcpio and bsdtar, sudo 1.6.9p20, OpenSSH 5.2, OpenSSL .98, |
66 |
ZFS version 6, gjournal, pcc .99, Perl 5.10</p> |
67 |
<p>With mports, we now have KDE 3.5.10 (still in progress for some parts), X.org 7.4, Gnome 2.20, |
68 |
GNUstep is working again, Etoile 0.2 (although this needs to be updated), unbranded F* browser as www/browser, |
69 |
Midori + webkit.</p> |
70 |
</blockquote> |
71 |
<h4>Update: (October 2007)</h4> |
72 |
<blockquote> |
73 |
<p>Seirei@ has imported Etoile 0.2 into our mports collection. |
74 |
You can test the window manager and many other features. We also offer KDE 3.5.4 and WindowMaker among other environments. |
75 |
About half of Gnome is in as well. We still plan to focus on GNUstep + Etoile.</p> |
76 |
</blockquote> |
77 |
<blockquote> |
78 |
<p>0.1 Release shipped with WindowMaker and KDE on the CD as well as GNUstep. The |
79 |
installer did not automatically install the ports though. 0.1.1 Release will fix some bugs with the |
80 |
packages as well as enable "mports" by default. Work has begun on bringing X.org 7.3 |
81 |
into the tree, although 0.1.1 will continue to use 6.9.</p> |
82 |
</blockquote> |
83 |
<h4>Update: (March 2007)</h4> |
84 |
<blockquote> |
85 |
<p>We are planning on using WindowMaker until the Etoile Project is |
86 |
farther along with their work. Etoile is in mports as are many other GNUstep based software packages.</p> |
87 |
</blockquote> |
88 |
</div> |
89 |
<p>If you are interested in joining the MidnightBSD project, please contact |
90 |
<a href="mailto:questions@midnightbsd.org">questions@midnightbsd.org |
91 |
</a>. We are looking for programmers with all types of skills, port maintainers, |
92 |
documentation and website maintainers, and people interested in mirroring. |
93 |
</p> |
94 |
<div id="devresources" class="fright"> |
95 |
<h3>Developer Resources</h3> |
96 |
<p>The CVS |
97 |
<a href="http://www.webhostingsearch.com/dedicated-server.php">dedicated server</a> |
98 |
for MidnightBSD is <span class="highlight">stargazer.midnightbsd.org</span>. |
99 |
This is where you can do your checkouts, commits, etc. To checkout anonymously, use |
100 |
<span class="highlight">anoncvs</span> (with password <span class="highlight">anoncvs</span>):</p> |
101 |
<p class="code"> |
102 |
cvs -z7 -d <span class="highlight">anoncvs</span>@stargazer.midnightbsd.org:/home/cvs co src<br /> |
103 |
anoncvs@stargazer.midnightbsd.org's password:<br /> |
104 |
cvs checkout: Updating src<br /> |
105 |
U src/COPYRIGHT<br /> |
106 |
U src/MAINTAINERS<br /> |
107 |
...<br /> |
108 |
</p> |
109 |
Or to checkout as a MidnightBSD developer with your username and password:<br /> |
110 |
<p class="code"> |
111 |
cvs -z7 -d <span class="highlight">username</span>@stargazer.midnightbsd.org:/home/cvs co src<br /> |
112 |
<span class="highlight">username</span>@stargazer.midnightbsd.org's password:<br /> |
113 |
cvs checkout: Updating src<br /> |
114 |
U src/COPYRIGHT<br /> |
115 |
U src/MAINTAINERS<br /> |
116 |
...<br /> |
117 |
</p> |
118 |
|
119 |
<p>Source code and mports can also be viewed using <a href="/cgi-bin/viewvc.cgi/midnightbsd/">ViewVC</a>, <a href="http://cvsweb.midnightbsd.org/">CVSWeb</a>, and <a href="/opengrok/">OpenGrok</a>.</p> |
120 |
</div> |
121 |
<div class="clear"></div> |
122 |
<h3>Background</h3> |
123 |
<p>MidnightBSD is based on FreeBSD 6.1 pre-release. The goal of the project is to create a BSD with ease of use and simplicity in mind.</p> |
124 |
<h3>Goals</h3> |
125 |
<div id="list"> |
126 |
<ul> |
127 |
<li>Create an easy to use desktop environment with basic functionality and a full graphical administration interface.</li> |
128 |
<li>Create a unique window manager designed with ease of use in mind. We will not use full blown desktop environments like KDE or Gnome.</li> |
129 |
<li>Integrate GNUstep into the system, but maintain BSD licensing on our own code whenever possible. The kernel and most userland software must be BSD licensed.</li> |
130 |
<li>Incorperate new technologies from other BSD projects that may interest desktop users. OpenBSD's OpenNTPD, OpenSSH, and wireless drivers are examples.</li> |
131 |
<li>Create our own ports system based on FreeBSD's ports. The system would have a graphical interface and existing utilities would be merged into a library so identical functionality is maintained on the gui and command line.</li> |
132 |
<li>Setup a binary update system so that users do no need to compile patches or new releases to get security updates or bug fixes.</li> |
133 |
<li>Listen to user feedback to improve the system. At times, many open source projects fail to listen to users making systems more difficult to use and decreasing scope.</li> |
134 |
</ul> |
135 |
</div> |
136 |
<p>Initially for 1.0 release, I'd like to have a new installer (wheither it be DragonFlyBSD's or a new one) along with a basic graphical environment. WindowMaker, Firefox, Thunderbird, and a few other applications. From there, based on user feedback, I'd like to build on the solid base of FreeBSD.</p> |
137 |
<p>To clarify, this is a fork of FreeBSD. I'm not creating a distro<span class="ast">*</span> like DesktopBSD or PC-BSD.</p> |
138 |
<p class="devnote"><span class="devasterisk">*</span> distro is often used in the Linux community. Some BSD folks hate that term applied to other projects. My working definition is a system with core componets (kernel, large parts of userland) that are not developed by the entity releasing the operating environment. It is a collection of software grouped together possibly with an installer. This can be applied to Live CD projects, BSD firewall projects, PC-BSD, DesktopBSD, and non BSD projects like Fedora, Gentoo, and so on.</p> |
139 |
</div> |
140 |
<!--#include virtual="/footer.html"--> |
141 |
</body> |
142 |
</html> |