Borrow Poul-Henning's Axe and chop out old information for 4.x, 5.x
and unsupported 6.x releases. Tom started this process a while ago and I'll follow up on that for the latest EoL round. The old versions can still be found in the doc archives: http://docs.freebsd.org/doc/
This commit is contained in:
Remko Lodder
parent
f03b953d50
commit
52425992c2
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=32117
8 changed files with 34 additions and 250 deletions
|
|
@ -2165,11 +2165,6 @@ ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
|
|||
ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3,
|
||||
wMaxPacketSize=49, nframes=6, buffer size=294</screen>
|
||||
|
||||
<note>
|
||||
<para>The Bluetooth stack has to be started manually on &os; 6.0, and
|
||||
on &os; 5.X before 5.5. It is done automatically from &man.devd.8;
|
||||
on &os; 5.5, 6.1 and newer.</para>
|
||||
|
||||
<para>Copy
|
||||
<filename>/usr/share/examples/netgraph/bluetooth/rc.bluetooth</filename>
|
||||
into some convenient place, like <filename>/etc/rc.bluetooth</filename>.
|
||||
|
|
@ -2190,7 +2185,6 @@ Max. ACL packet size: 192 bytes
|
|||
Number of ACL packets: 8
|
||||
Max. SCO packet size: 64 bytes
|
||||
Number of SCO packets: 8</screen>
|
||||
</note>
|
||||
|
||||
</sect2>
|
||||
|
||||
|
|
@ -2509,12 +2503,6 @@ Bluetooth Profile Descriptor List:
|
|||
|
||||
<screen>&prompt.root; <userinput>/etc/rc.d/sdpd start</userinput></screen>
|
||||
|
||||
<para>On &os; 6.0, and on &os; 5.X before 5.5,
|
||||
<application>sdpd</application> is not integrated into the system
|
||||
startup scripts. It has to be started manually with:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>sdpd</userinput></screen>
|
||||
|
||||
<para>The local server application that wants to provide Bluetooth
|
||||
service to the remote clients will register service with the local
|
||||
SDP daemon. The example of such application is &man.rfcomm.pppd.8;.
|
||||
|
|
|
|||
|
|
@ -2169,7 +2169,7 @@ device_probe_and_attach: cbb0 attach returned 12</screen>
|
|||
connected at once, the resources needed may be similar to a
|
||||
high-scale web server.</para>
|
||||
|
||||
<para>As of FreeBSD 4.5, <varname>kern.maxusers</varname> is
|
||||
<para>The variable <varname>kern.maxusers</varname> is
|
||||
automatically sized at boot based on the amount of memory available
|
||||
in the system, and may be determined at run-time by inspecting the
|
||||
value of the read-only <varname>kern.maxusers</varname> sysctl.
|
||||
|
|
@ -2182,9 +2182,7 @@ device_probe_and_attach: cbb0 attach returned 12</screen>
|
|||
boot-time or run-time in <filename>/boot/loader.conf</filename> (see
|
||||
the &man.loader.conf.5; man page or the
|
||||
<filename>/boot/defaults/loader.conf</filename> file for some hints)
|
||||
or as described elsewhere in this document. Systems older than
|
||||
FreeBSD 4.4 must set this value via the kernel &man.config.8;
|
||||
option <option>maxusers</option> instead.</para>
|
||||
or as described elsewhere in this document.</para>
|
||||
|
||||
<para>In older releases, the system will auto-tune
|
||||
<literal>maxusers</literal> for you if you explicitly set it to
|
||||
|
|
@ -2216,14 +2214,7 @@ device_probe_and_attach: cbb0 attach returned 12</screen>
|
|||
limit the number of users which can log into your machine. It
|
||||
simply sets various table sizes to reasonable values considering
|
||||
the maximum number of users you will likely have on your system
|
||||
and how many processes each of them will be running. One keyword
|
||||
which <emphasis>does</emphasis> limit the number of simultaneous
|
||||
remote logins and X terminal windows is <link
|
||||
linkend="kernelconfig-ptys"><literal>pseudo-device pty
|
||||
16</literal></link>. With &os; 5.X, you do not have to
|
||||
worry about this number since the &man.pty.4; driver is
|
||||
<quote>auto-cloning</quote>; you simply use the line
|
||||
<literal>device pty</literal> in your configuration file.</para>
|
||||
and how many processes each of them will be running.</para>
|
||||
</note>
|
||||
|
||||
</sect3>
|
||||
|
|
|
|||
|
|
@ -393,9 +393,8 @@ options ALTQ_NOPCC # Required for SMP build</programlisting>
|
|||
<warning>
|
||||
<para>When browsing the pf user's guide, please keep in mind that
|
||||
different versions of &os; contain different versions of pf. The
|
||||
<application>pf</application> firewall in &os; 5.X is at the level
|
||||
of OpenBSD version 3.5 and in &os; 6.X is at the level of OpenBSD
|
||||
version 3.7.</para>
|
||||
<application>pf</application> firewall in &os; 6.X is at the level
|
||||
of OpenBSD version 3.7.</para>
|
||||
</warning>
|
||||
|
||||
<para>The &a.pf; is a good place to ask questions about
|
||||
|
|
|
|||
|
|
@ -975,7 +975,7 @@ device sc</programlisting>
|
|||
#device apm</programlisting>
|
||||
|
||||
<para>Advanced Power Management support. Useful for laptops,
|
||||
although in &os; 5.X and above this is disabled in
|
||||
although this is disabled in
|
||||
<filename>GENERIC</filename> by default.</para>
|
||||
|
||||
<programlisting># Add suspend/resume support for the i8254.
|
||||
|
|
|
|||
|
|
@ -702,12 +702,6 @@ postmaster@example.com postmaster@noc.example.net
|
|||
<sect2 id="mail-disable-sendmail">
|
||||
<title>Disable <application>sendmail</application></title>
|
||||
|
||||
<para>The procedure used to start
|
||||
<application>sendmail</application> changed significantly
|
||||
between 4.5-RELEASE, 4.6-RELEASE, and later releases.
|
||||
Therefore, the procedure used to disable it is subtly
|
||||
different.</para>
|
||||
|
||||
<warning>
|
||||
<para>If you disable <application>sendmail</application>'s
|
||||
outgoing mail service, it is important that you replace it
|
||||
|
|
@ -724,49 +718,6 @@ postmaster@example.com postmaster@noc.example.net
|
|||
never be delivered.</para>
|
||||
</warning>
|
||||
|
||||
<sect3>
|
||||
<title>FreeBSD 4.5-STABLE before 2002/4/4 and Earlier
|
||||
(Including 4.5-RELEASE and Earlier)</title>
|
||||
|
||||
<para>Enter:</para>
|
||||
|
||||
<programlisting>sendmail_enable="NO"</programlisting>
|
||||
|
||||
<para>into <filename>/etc/rc.conf</filename>. This will disable
|
||||
<application>sendmail</application>'s incoming mail service,
|
||||
but if <filename>/etc/mail/mailer.conf</filename> (see below)
|
||||
is not changed, <application>sendmail</application> will
|
||||
still be used to send e-mail.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>FreeBSD 4.5-STABLE after 2002/4/4
|
||||
(Including 4.6-RELEASE and Later)</title>
|
||||
|
||||
<para>In order to completely disable
|
||||
<application>sendmail</application>, including the outgoing
|
||||
mail service, you must use</para>
|
||||
|
||||
<programlisting>sendmail_enable="NONE"</programlisting>
|
||||
|
||||
<para>in <filename>/etc/rc.conf.</filename></para>
|
||||
|
||||
<para>If you only want to disable
|
||||
<application>sendmail</application>'s incoming mail service,
|
||||
you should set</para>
|
||||
|
||||
<programlisting>sendmail_enable="NO"</programlisting>
|
||||
|
||||
<para>in <filename>/etc/rc.conf</filename>. However, if
|
||||
incoming mail is disabled, local delivery will still
|
||||
function. More information on
|
||||
<application>sendmail</application>'s startup options is
|
||||
available from the &man.rc.sendmail.8; manual page.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>FreeBSD 5.0-STABLE and Later</title>
|
||||
|
||||
<para>In order to completely disable
|
||||
<application>sendmail</application>, including the outgoing
|
||||
mail service, you must use</para>
|
||||
|
|
@ -787,55 +738,19 @@ sendmail_msp_queue_enable="NO"</programlisting>
|
|||
<para>in <filename>/etc/rc.conf</filename>. More information on
|
||||
<application>sendmail</application>'s startup options is
|
||||
available from the &man.rc.sendmail.8; manual page.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Running Your New MTA on Boot</title>
|
||||
|
||||
<para>You may have a choice of two methods for running your
|
||||
new MTA on boot, again depending on what version of FreeBSD
|
||||
you are running.</para>
|
||||
<para>The new MTA can be started during boot by adding a
|
||||
configuration line to <filename>/etc/rc.conf</filename>
|
||||
like the followin example for postfix:</para>
|
||||
|
||||
<sect3>
|
||||
<title>FreeBSD 4.5-STABLE before 2002/4/11
|
||||
(Including 4.5-RELEASE and Earlier)</title>
|
||||
|
||||
<para>Add a script to
|
||||
<filename>/usr/local/etc/rc.d/</filename> that
|
||||
ends in <filename>.sh</filename> and is executable by
|
||||
<username>root</username>. The script should accept <literal>start</literal> and
|
||||
<literal>stop</literal> parameters. At startup time the
|
||||
system scripts will execute the command</para>
|
||||
|
||||
<programlisting>/usr/local/etc/rc.d/supermailer.sh start</programlisting>
|
||||
|
||||
<para>which you can also use to manually start the server. At
|
||||
shutdown time, the system scripts will use the
|
||||
<literal>stop</literal> option, running the command</para>
|
||||
|
||||
<programlisting>/usr/local/etc/rc.d/supermailer.sh stop</programlisting>
|
||||
|
||||
<para>which you can also use to manually stop the server
|
||||
while the system is running.</para>
|
||||
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>FreeBSD 4.5-STABLE after 2002/4/11
|
||||
(Including 4.6-RELEASE and Later)</title>
|
||||
|
||||
<para>With later versions of FreeBSD, you can use the
|
||||
above method or you can set</para>
|
||||
|
||||
<programlisting>mta_start_script="filename"</programlisting>
|
||||
|
||||
<para>in <filename>/etc/rc.conf</filename>, where
|
||||
<replaceable>filename</replaceable> is the name of some
|
||||
script that you want executed at boot to start your
|
||||
MTA.</para>
|
||||
</sect3>
|
||||
<screen>&prompt.root; echo '<replaceable>postfix</replaceable>_enable=<quote>YES</quote>' >> /etc/rc.conf</screen>
|
||||
|
||||
<para>The MTA will now be automatically started during
|
||||
boot.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
|
|
|||
|
|
@ -348,11 +348,10 @@
|
|||
<listitem>
|
||||
<para>Identifies the device to which the modem is
|
||||
connected. <devicename>COM1</devicename> is
|
||||
<filename>/dev/cuad0</filename> (or
|
||||
<filename>/dev/cuaa0</filename> under &os; 5.X) and
|
||||
<filename>/dev/cuad0</filename>
|
||||
and
|
||||
<devicename>COM2</devicename> is
|
||||
<filename>/dev/cuad1</filename> (or
|
||||
<filename>/dev/cuaa1</filename>).</para>
|
||||
<filename>/dev/cuad1</filename>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -1842,8 +1841,7 @@ exit 1
|
|||
so, you are not required to rebuild the kernel.
|
||||
When matching up sio modem is on <devicename>sio1</devicename> or
|
||||
<devicename>COM2</devicename> if you are in DOS, then your
|
||||
modem device would be <filename>/dev/cuad1</filename> (or
|
||||
<filename>/dev/cuaa1</filename> under &os; 5.X).</para>
|
||||
modem device would be <filename>/dev/cuad1</filename>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
|
@ -1867,8 +1865,7 @@ exit 1
|
|||
<screen>ppp ON example> <userinput>set device <filename>/dev/cuad1</filename></userinput></screen>
|
||||
|
||||
<para>We set our modem device, in this case it is
|
||||
<devicename>cuad1</devicename> (or
|
||||
<filename>/dev/cuaa1</filename> under &os; 5.X).</para>
|
||||
<devicename>cuad1</devicename>.</para>
|
||||
|
||||
<screen>ppp ON example> <userinput>set speed 115200</userinput></screen>
|
||||
|
||||
|
|
@ -2519,18 +2516,18 @@ tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
|
|||
<para>First, determine which serial port your modem is connected to.
|
||||
Many people set up a symbolic link, such as
|
||||
<filename>/dev/modem</filename>, to point to the real device name,
|
||||
<filename>/dev/cuadN</filename> (or <filename>/dev/cuaaN</filename>
|
||||
under &os; 5.X). This allows you to abstract the actual device
|
||||
<filename>/dev/cuadN</filename>.
|
||||
This allows you to abstract the actual device
|
||||
name should you ever need to move the modem to a different port. It
|
||||
can become quite cumbersome when you need to fix a bunch of files in
|
||||
<filename>/etc</filename> and <filename>.kermrc</filename> files all
|
||||
over the system!</para>
|
||||
|
||||
<note>
|
||||
<para><filename>/dev/cuad0</filename> (or
|
||||
<filename>/dev/cuaa0</filename> under &os; 5.X) is
|
||||
<devicename>COM1</devicename>, <filename>cuad1</filename> (or
|
||||
<filename>/dev/cuaa1</filename>) is
|
||||
<para><filename>/dev/cuad0</filename>
|
||||
is
|
||||
<devicename>COM1</devicename>, <filename>cuad1</filename>
|
||||
is
|
||||
<devicename>COM2</devicename>, etc.</para>
|
||||
</note>
|
||||
|
||||
|
|
|
|||
|
|
@ -498,10 +498,6 @@
|
|||
for modems. You may use the call-out port if the serial cable
|
||||
or the terminal does not support the carrier detect
|
||||
signal.</para>
|
||||
|
||||
<note><para>Call-out ports are named
|
||||
<filename>/dev/cuaa<replaceable>N</replaceable></filename> in
|
||||
&os; 5.X and older.</para></note>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
|
@ -595,18 +591,12 @@ sio3: type 16550A</screen>
|
|||
and <filename>/dev/cuad<replaceable>N</replaceable></filename>
|
||||
(call-out) devices. FreeBSD also provides initialization devices
|
||||
(<filename>/dev/ttyd<replaceable>N</replaceable>.init</filename> and
|
||||
<filename>/dev/cuad<replaceable>N</replaceable>.init</filename> on
|
||||
&os; 6.X,
|
||||
<filename>/dev/ttyid<replaceable>N</replaceable></filename> and
|
||||
<filename>/dev/cuaia<replaceable>N</replaceable></filename> on
|
||||
&os; 5.X) and
|
||||
<filename>/dev/cuad<replaceable>N</replaceable>.init</filename>
|
||||
and
|
||||
locking devices
|
||||
(<filename>/dev/ttyd<replaceable>N</replaceable>.lock</filename> and
|
||||
<filename>/dev/cuad<replaceable>N</replaceable>.lock</filename> on
|
||||
&os; 6.X,
|
||||
<filename>/dev/ttyld<replaceable>N</replaceable></filename> and
|
||||
<filename>/dev/cuala<replaceable>N</replaceable></filename> on
|
||||
&os; 5.X). The
|
||||
<filename>/dev/cuad<replaceable>N</replaceable>.lock</filename>)
|
||||
The
|
||||
initialization devices are used to initialize communications port
|
||||
parameters each time a port is opened, such as
|
||||
<literal>crtscts</literal> for modems which use
|
||||
|
|
@ -779,10 +769,7 @@ sio3: type 16550A</screen>
|
|||
<para>Where <quote>serial-port-device</quote> is the name of a
|
||||
special device file denoting a serial port of your system.
|
||||
These device files are called
|
||||
<devicename>/dev/cuaa<replaceable>N</replaceable></devicename>
|
||||
for &os; versions older than 6.0, and
|
||||
<devicename>/dev/cuad<replaceable>N</replaceable></devicename>
|
||||
for 6.0 and later versions.</para>
|
||||
<devicename>/dev/cuad<replaceable>N</replaceable></devicename>.</para>
|
||||
|
||||
<para>The <quote>N</quote>-part of a device name is the serial
|
||||
port number.</para>
|
||||
|
|
@ -2696,14 +2683,6 @@ comconsole_speed="115200"
|
|||
console="comconsole,vidconsole"</programlisting>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<note>
|
||||
<para>&os; versions before 6.1-RELEASE do not support the
|
||||
<option>-S</option> or the <varname>comconsole_speed</varname>
|
||||
option in <filename>/boot/loader.conf</filename>, so you will have
|
||||
to recompile the boot blocks if you are using such a version of
|
||||
&os;.</para>
|
||||
</note>
|
||||
</sect3>
|
||||
|
||||
<sect3 id="serialconsole-com2">
|
||||
|
|
@ -2829,7 +2808,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
|
|||
|
||||
<para>You can easily specify the boot loader and the kernel to use the
|
||||
serial console by writing just one line in
|
||||
<filename>/boot/loader.rc</filename>:</para>
|
||||
<filename>/boot/loader.conf</filename>:</para>
|
||||
|
||||
<programlisting>set console="comconsole"</programlisting>
|
||||
|
||||
|
|
@ -2837,7 +2816,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
|
|||
block discussed in the previous section.</para>
|
||||
|
||||
<para>You had better put the above line as the first line of
|
||||
<filename>/boot/loader.rc</filename> so as to see boot messages on
|
||||
<filename>/boot/loader.conf</filename> so as to see boot messages on
|
||||
the serial console as early as possible.</para>
|
||||
|
||||
<para>Likewise, you can specify the internal console as:</para>
|
||||
|
|
@ -2849,23 +2828,9 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
|
|||
kernel, will use whichever console indicated by the
|
||||
<option>-h</option> option in the boot block.</para>
|
||||
|
||||
<para>In versions 3.2 or later, you may specify the console in
|
||||
<filename>/boot/loader.conf.local</filename> or
|
||||
<filename>/boot/loader.conf</filename>, rather than in
|
||||
<filename>/boot/loader.rc</filename>. In this method your
|
||||
<filename>/boot/loader.rc</filename> should look like:</para>
|
||||
|
||||
<programlisting>include /boot/loader.4th
|
||||
start</programlisting>
|
||||
|
||||
<para>Then, create <filename>/boot/loader.conf.local</filename> and
|
||||
put the following line there.</para>
|
||||
|
||||
<programlisting>console=comconsole</programlisting>
|
||||
|
||||
<para>or</para>
|
||||
|
||||
<programlisting>console=vidconsole</programlisting>
|
||||
<para>The console can be specified in
|
||||
<filename>/boot/loader.conf.local</filename> or in
|
||||
<filename>/boot/loader.conf</filename>.</para>
|
||||
|
||||
<para>See &man.loader.conf.5; for more information.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -1052,9 +1052,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
|
|||
start</command> command.</para>
|
||||
|
||||
<note><para>The following paragraphs are outlining the steps
|
||||
needed for FreeBSD 5.X and above. The setup required for
|
||||
FreeBSD 4.X differs, and is described below in <xref
|
||||
linkend="vinum-root-4x">.</para></note>
|
||||
needed for FreeBSD.</para></note>
|
||||
|
||||
<para>By placing the line:</para>
|
||||
|
||||
|
|
@ -1365,75 +1363,6 @@ Subdisk root.p1.s0:
|
|||
bootstrap no longer collide.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="vinum-root-4x">
|
||||
<title>Differences for FreeBSD 4.X</title>
|
||||
|
||||
<para>Under FreeBSD 4.X, some internal functions required to
|
||||
make Vinum automatically scan all disks are missing, and the
|
||||
code that figures out the internal ID of the root device is
|
||||
not smart enough to handle a name like
|
||||
<filename>/dev/vinum/root</filename> automatically.
|
||||
Therefore, things are a little different here.</para>
|
||||
|
||||
<para>Vinum must explicitly be told which disks to scan, using a
|
||||
line like the following one in
|
||||
<filename>/boot/loader.conf</filename>:</para>
|
||||
|
||||
<programlisting>vinum.drives="/dev/<replaceable>da0</replaceable> /dev/<replaceable>da1</replaceable>"</programlisting>
|
||||
|
||||
<para>It is important that all drives are mentioned that could
|
||||
possibly contain Vinum data. It does not harm if
|
||||
<emphasis>more</emphasis> drives are listed, nor is it
|
||||
necessary to add each slice and/or partition explicitly, since
|
||||
Vinum will scan all slices and partitions of the named drives
|
||||
for valid Vinum headers.</para>
|
||||
|
||||
<para>Since the routines used to parse the name of the root
|
||||
filesystem, and derive the device ID (major/minor number) are
|
||||
only prepared to handle <quote>classical</quote> device names
|
||||
like <filename>/dev/ad0s1a</filename>, they cannot make
|
||||
any sense out of a root volume name like
|
||||
<filename>/dev/vinum/root</filename>. For that reason,
|
||||
Vinum itself needs to pre-setup the internal kernel parameter
|
||||
that holds the ID of the root device during its own
|
||||
initialization. This is requested by passing the name of the
|
||||
root volume in the loader variable
|
||||
<literal>vinum.root</literal>. The entry in
|
||||
<filename>/boot/loader.conf</filename> to accomplish this
|
||||
looks like:</para>
|
||||
|
||||
<programlisting>vinum.root="root"</programlisting>
|
||||
|
||||
<para>Now, when the kernel initialization tries to find out the
|
||||
root device to mount, it sees whether some kernel module has
|
||||
already pre-initialized the kernel parameter for it. If that
|
||||
is the case, <emphasis>and</emphasis> the device claiming the
|
||||
root device matches the major number of the driver as figured
|
||||
out from the name of the root device string being passed (that
|
||||
is, <literal>"vinum"</literal> in our case), it will use the
|
||||
pre-allocated device ID, instead of trying to figure out one
|
||||
itself. That way, during the usual automatic startup, it can
|
||||
continue to mount the Vinum root volume for the root
|
||||
filesystem.</para>
|
||||
|
||||
<para>However, when <command>boot -a</command> has been
|
||||
requesting to ask for entering the name of the root device
|
||||
manually, it must be noted that this routine still cannot
|
||||
actually parse a name entered there that refers to a Vinum
|
||||
volume. If any device name is entered that does not refer to
|
||||
a Vinum device, the mismatch between the major numbers of the
|
||||
pre-allocated root parameter and the driver as figured out
|
||||
from the given name will make this routine enter its normal
|
||||
parser, so entering a string like
|
||||
<literal>ufs:da0d</literal> will work as expected. Note
|
||||
that if this fails, it is however no longer possible to
|
||||
re-enter a string like <literal>ufs:vinum/root</literal>
|
||||
again, since it cannot be parsed. The only way out is to
|
||||
reboot again, and start over then. (At the
|
||||
<quote>askroot</quote> prompt, the initial
|
||||
<filename>/dev/</filename> can always be omitted.)</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue