View | Details | Raw Unified | Return to bug 12595
Collapse All | Expand All

(-)hackers.sgml 1999/07/11 13:54:49 (+91 lines)
Lines 35-40 Link Here
35
35
36
    <sect1>
36
    <sect1>
37
      <heading>
37
      <heading>
38
        Why shouldn't I just go ahead and run -current?  That's got
39
        all the latest stuff, right?
40
      </heading>
41
42
      <p>4.0 is the next major release of FreeBSD. For now, and for a
43
      while, all -stable releases of FreeBSD will be in the 3.x
44
      line. These are minor releases, which do not introduce big
45
      changes and we try our best to avoid breaking compatibility
46
      backward compatibility (binary, file formats, etc).
47
48
      <p>Meanwhile, our fearless developers are cooking the 4.0
49
      version. This branch is known as 4.0-current, or just -current
50
      (since when 4.0 becomes stable, the current branch will become
51
      5.0-current).
52
53
      <p>Our developers are fearless because a -current system is
54
      something in development, and, thus, subject to all sort of
55
      bugs, which can wipe out your disks, burn your monitor, erase
56
      your BIOS, overheat your CPU(s), spit out your PCI cards, send
57
      the fans flying (sometimes throwing stuff at them first), make
58
      international phone calls to phone sex services, print
59
      pornography until your printer runs out of paper/toner (sorry,
60
      no such luck... it's just the Stark report), send insulting
61
      faxes to your boss, cheat on the mob and blame you for it,
62
      attract attention for the gentle I.R.S. personel, blow your
63
      house fuses, open the gas and then set your house on fire, make
64
      your girlfriend break up with you (or your wife cheat on you),
65
      and bomb Yugoslavia. This last one we are trying to debug,
66
      though [NOTE: at the time of this writing, we have reports that
67
      this bug has been fixed].
68
69
      <p>Because of the above, we advise against using -current. If
70
      you so insist, the following rules must be obeyed:
71
72
      <itemize>
73
       <item>Read cvs-all. No, I'm not kidding. I mean it.</item>
74
75
       <item>Read freebsd-current. Yeah, that one too.</item>
76
77
       <item>If something fails, it's probably because you missed a
78
       message on cvs-all or freebsd-current.</item>
79
80
       <item>If that's not the case, it's probably a temporary
81
       bug. Cvsup again after the appropriate time (minimum of one
82
       hour, though one full day is not unreasonable).</item>
83
84
       <item>If it still crashes *at the same location*, then it's
85
       probably your fault. Junk your customized settings, and try to
86
       reproduce it with a vanilla system.</item>
87
88
       <item>If you can reproduce it even with a vanilla system, then
89
       you might actually have stumbled on a bug. Congratulations!
90
       Find out what the bug is, and send us the patches.</item>
91
92
       <item>If you are not capable of the above, you might just keep
93
       quiet and wait until someone fixes it. See steps 1 and 2 for
94
       how do you know someone fixed it.</item>
95
96
       <item>On the other hand, you might help track down the
97
       bug. See the handbook on getting crash dumps, kernel traces,
98
       and such stuff.</item>
99
100
       <item>If you loose all data on your hard disks because of a
101
       bug, that's one of the risks of running -current. Either you
102
       can deal with that, or you shouldn't be running
103
       -current.</item>
104
      </itemize>
105
106
      <p>These rules, though written tongue-in-cheek, are for
107
      real. FreeBSD 4.0-current is <bf/not/ supposed to work all the
108
      time. It is being <bf/developed/, and saying "Hey! I have a
109
      bug!"  does <bf/not/ help developers. Furthermore, sometimes it
110
      breaks <bf/on purpose/, while things are being changed, and the
111
      fixes are <bf/not/ immediate.
112
113
      <p>If you can live with that, and think you have any compelling
114
      reason to run -current, read the handbook for further
115
      instructions.
116
117
118
      <p>Sorry if this seems too harsh, but many people are just not
119
      used to the concept of a development tree available publicly,
120
      and think of it as the "latest version". It is <bf/not/ the latest
121
      version. When it is <bf/ready/, it will be the latest
122
      version. Until then... read the above.
123
124
    <p><em>Contributed by 
125
    <url url="mailto:dcs@freebsd.org" name="Daniel C. Sobral">.</em>
126
127
    <sect1>
128
      <heading>
38
        How do I make my own custom release?<label id="custrel">
129
        How do I make my own custom release?<label id="custrel">
39
      </heading>
130
      </heading>

Return to bug 12595