diff --git a/website/content/en/art.adoc b/website/content/en/art.adoc index 9c4c1620e8..cdbfe371c4 100644 --- a/website/content/en/art.adoc +++ b/website/content/en/art.adoc @@ -1,70 +1,70 @@ --- title: "FreeBSD Art" sidenav: about --- include::shared/authors.adoc[] = FreeBSD Art * <> * <> * <> * <> This page contains miscellaneous FreeBSD "art". Suggestions for additions can be sent to www@FreeBSD.org. Please note the <> for these graphics. [[bsd-daemon]] == link:..copyright/[BSD Daemon] [.center] image:../gifs/daemon-phk.png[BSD Daemon,width=191,height=208] [.center] Created by {phk-name} + -Source: https://svnweb.freebsd.org/base/head/share/examples/BSD_daemon/[/usr/share/examples/BSD_daemon/] on FreeBSD systems. +Source: https://cgit.freebsd.org/src/tree/share/examples/BSD_daemon/[/usr/share/examples/BSD_daemon/] on FreeBSD systems. [.center] link:../../gifs/daemon_hammer.jpg[image:../../gifs/daemon_hammer-tn25.jpg[BSD Daemon wielding a hammer,width=150,height=178]] image:../../gifs/power.jpg[BSD Daemon waiting tables,width=160,height=246] [.center] image:../gifs/news.jpg[BSD Daemon editing the news,width=193,height=144] image:../gifs/doc.jpg[BSD Daemon reading documentation,width=274,height=163] image:../gifs/releases.jpg[BSD Daemon delivering the latest release,width=259,height=178] [[powered-by]] == "Powered by FreeBSD" Logos [.center] image:../gifs/powerlogo.gif[Powered by FreeBSD Logo] image:../gifs/power-button.gif[Powered by FreeBSD Logo] [.center] image:../gifs/pbfbsd2.gif[Powered by FreeBSD Logo,width=171,height=64] image:../gifs/powerani.gif[Powered by FreeBSD Logo,width=171,height=64] image:../gifs/fhp_mini.jpg[FreeBSD Hardware Partner Logo,width=145,height=50] [.center] image:../gifs/banner1.gif[FreeBSD The Power To Serve Logo,width=446,height=63] [.center] image:../gifs/banner2.gif[FreeBSD The Power To Serve Logo,width=310,height=63] [.center] image:../gifs/banner3.gif[FreeBSD The Power To Serve Logo,width=250,height=35] [.center] image:../gifs/banner4.gif[FreeBSD The Power To Serve Logo,width=225,height=46] [[adv]] == Old Advertisement Banners [.center] image:../gifs/freebsd-advert.gif[Adv Banner1,width=455,height=60] image:../gifs/freebsd_3.gif[Adv Banner2,width=306,height=94] [[use]] == Graphics Use The "Powered by FreeBSD" logos above may be link:../gifs/powerlogo.gif[downloaded] and displayed on personal or commercial home pages served by FreeBSD machines. Use of this logo or the likeliness of the link:../copyright/daemon/[BSD Daemons] for profitable gain requires the consent of mailto:taob@risc.org[Brian Tao] (creator of the "power" logo) and mailto:mckusick@mckusick.com[Marshall Kirk McKusick] (copyright holder for the BSD Daemon image). -{phk-name}'s rendering of the BSD Daemon is released under "THE BEER-WARE LICENSE". See the https://svnweb.freebsd.org/base/head/share/examples/BSD_daemon/README?view=markup[README] for more information. +{phk-name}'s rendering of the BSD Daemon is released under "THE BEER-WARE LICENSE". See the https://cgit.freebsd.org/src/plain/share/examples/BSD_daemon/README[README] for more information. [[trademark]] == Trademarks The https://www.freebsdfoundation.org[FreeBSD Foundation] holds several FreeBSD related trademarks (among them the trademark for the term "FreeBSD" itself). For more information about these trademarks read the https://www.freebsdfoundation.org/legal/trademark-usage-terms-and-conditions/[FreeBSD Trademark Usage Terms and Conditions]. diff --git a/website/content/en/copyright/_index.adoc b/website/content/en/copyright/_index.adoc index 82c154c68a..4d2111b28d 100644 --- a/website/content/en/copyright/_index.adoc +++ b/website/content/en/copyright/_index.adoc @@ -1,24 +1,24 @@ --- title: "FreeBSD Copyright and Legal Information" sidenav: about --- = FreeBSD Copyright and Legal Information == link:freebsd-license[The FreeBSD Copyright] == link:freebsd-doc-license[The FreeBSD Documentation License] == link:trademarks[Trademark Legend] == link:license[The BSD Copyright] == link:daemon[The BSD Daemon] -== http://svnweb.FreeBSD.org/ports/head/LEGAL?revision=HEAD&view=co[FreeBSD Ports redistribution restrictions] +== https://cgit.FreeBSD.org/ports/plain/LEGAL[FreeBSD Ports redistribution restrictions] == link:COPYING[GNU GENERAL PUBLIC LICENSE] == link:COPYING.LIB[GNU LIBRARY GENERAL PUBLIC LICENSE] == link:../privacy[FreeBSD's Privacy Policy] diff --git a/website/content/en/gnome/docs/porting.adoc b/website/content/en/gnome/docs/porting.adoc index 22977520c9..fb3b88c879 100644 --- a/website/content/en/gnome/docs/porting.adoc +++ b/website/content/en/gnome/docs/porting.adoc @@ -1,199 +1,199 @@ --- title: "FreeBSD GNOME Project: How To Make a Port" sidenav: gnome --- include::shared/en/urls.adoc[] = FreeBSD GNOME Project: How To Make a Port This document assumes that you already know how the port system works, and therefore only provides GNOME-specific hints and tips. General instructions can be found in the link:{porters-handbook}[FreeBSD Porter's Handbook]. == Example Makefile There is an link:../example-makefile/[example Makefile] for a GNOME port, which uses many of the tricks outlined in this document. Please feel free to use it as a guide for creating your own ports. == GNOME Makefile Macros GNOME applications under FreeBSD use the *USE_GNOME* infrastructure. To specify which components of the GNOME system your port needs in order to build, simply list them all as a space-separated list. For example: .... USE_XLIB= yes USE_GNOME= gnomeprefix gnomehack libgnomeui .... The *USE_GNOME* components are divided into the following two lists: * link:../gnome_porting/[GNOME desktop-version-independent components] * link:../gnome2_porting/[GNOME 2 components] * link:../gnome1_porting/[GNOME 1 components] If your port needs only *GTK2* libraries, the following is the shortest way to define this: .... USE_GNOME= gtk20 .... If your port needs only *GTK1* libraries, the following is the shortest way to define this: .... USE_GNOME= gtk12 .... Even if your application needs only the GTK libraries, other *USE_GNOME* components may be useful. Please scan the entire list to make sure your port uses all relevant components. Once you have finished with your port, it is a good idea to verify that your port depends on the correct list of components. To see a list of what packages your port will actually require, use the command `make package-depends` from within your port's directory. To aid in creating the list of necessary components, it can be helpful to examine the output of `make configure`. At the end of the `checking for...` list, there will be a line similar to this: .... checking for libgnomeui-2.0 >= 2.0.0 cspi-1.0 >= 1.1.7 libspi-1.0 >= 1.1.7 libbonobo-2.0 >= 2.0.0 atk >= 1.0.0 gtk+-2.0 >= 2.0.0 gail libwnck-1.0 esound... yes .... This is a list of the components upon which this application relies to build. Pay close attention to the hierarchical layout of the *USE_GNOME* system; many components are implied from other *USE_GNOME* directives. In the above example, `USE_GNOME= libgnomeui` implies use of `libbonoboui`, which implies `libgnomecanvas`, which implies `libglade2`, which implies `gtk20`. Thus, even though `gtk+-2.0` appears in the list of requisite components, `gtk20` can be eliminated from the *USE_GNOME* list. There are a number of other such redundancies that can be eliminated from this list. For the above list (taken from `sysutils/gok`), the following is defined in the `Makefile`: .... USE_GNOME= gnomehack gnomeprefix libgnomeui atspi libwnck .... == GNOME 1 Desktop vs. GNOME 2 Desktop In the beginning, there was only `GNOME 1`. When the `GNOME 2` desktop came around, maximum backwards compatibility was ensured, within reason. `GNOME 1` applications can run fine under the `GNOME 2` desktop, provided that the applications do not utilize functionality specific to the `GNOME 1` desktop environment. The `GNOME 1` desktop, and all applications that will not run under the `GNOME 2` desktop, have been removed from the ports tree. What this means for you, as an application porter, is simply that you should not add `GNOME 1`-specific applications to the ports tree. If you wish to determine which version of the GNOME desktop environment is present on a user's machine, you can check the value of *GNOME_DESKTOP_VERSION*. This variable is set to either `"1"` or `"2"` depending upon whether the `GNOME 1` or `GNOME 2` desktop is installed. == Optional GNOME Dependencies If your port can optionally use GNOME, you must set `WANT_GNOME= yes` in your Makefile, then check to see if `HAVE_GNOME` is set for each component from the list above that your port can use. Since this is a conditional evaluation, you need to stick it between `bsd.port.pre.mk` and `bsd.port.post.mk`. For example: .... WANT_GNOME= yes .include .if ${HAVE_GNOME:Mgnomepanel}!="" USE_GNOME+= gnomeprefix gnomepanel CONFIGURE_ARGS+= --with-gnome PKGNAMESUFFIX= -gnome .else CONFIGURE_ARGS+= --without-gnome .endif .include .... Here, `WANT_GNOME` tells the ports system to check for the existence of the various GNOME components listed above. For each component found, its name is appended to `HAVE_GNOME`. Since this port can use `gnomepanel`, we check `HAVE_GNOME` to see if it contains `gnomepanel` (for more on the :M`pattern` make syntax, please refer to the link:https://www.freebsd.org/cgi/man.cgi?query=make&sektion=0&format=html[make(1)] manpage). If `gnomepanel` is found, then it is added the list of `USE_GNOME` dependencies, and the port-specific `--with-gnome` `CONFIGURE_ARG` is passed. In an old GNOME infrastructure, `PKGNAMESUFFIX` was automatically adjusted by the proper `USE_*` macro. Now it is up to the individual porter to do this. Our example port appends `-gnome` to the port name to indicate it has been built with GNOME support. The same is true for the `DATADIR` `PLIST_SUB`. The individual porter must decide when do the `DATADIR` substitution. A good rule of thumb is to add the `DATADIR` `PLIST_SUB` when using the `gnomeprefix` component. *Note:* You cannot add extra default `USE_GNOME` components after the `.include `. That is, the following is *wrong* : .... .include .if ${HAVE_GNOME:Mgnomelibs}!="" USE_GNOME+= libgnome .else USE_GNOME+= gtk12 # WRONG! .endif .... This will make the build system think that GNOME _is_ desired, and mark the `pkg-plist` accordingly, thus breaking package builds. If you need to add default `USE_GNOME` components, do so *above* the ` .include ` line. To enforce use of optional GNOME dependencies unconditionally, you can add `WITH_GNOME= yes` to `/etc/make.conf` or on the make command line. This will always return true when checking for optional GNOME dependencies. If you want the system to always return false when checking for optional GNOME dependencies, you can add `WITHOUT_GNOME= yes` to `/etc/make.conf` or to the make command line. More information on the USE_GNOME infrastructure can be found by looking at the source and comments of `${PORTSDIR}/Mk/bsd.gnome.mk`. [[prefix]] == GNOME PREFIX Since the release of 2.16, GNOME now lives in `LOCALBASE` instead of `X11BASE`. To make it easier for GNOME ports that must also be installed into the same PREFIX as GNOME, a hack has been added to `bsd.gnome.mk` to force the PREFIX to `LOCALBASE` whenever the `gnomeprefix` component is used. This can be overridden by manually specifying `PREFIX` in your port's `Makefile` or on the command line. [[omf]] == OMF Installation A large number of GNOME applications (especially GNOME 2 applications) install Open Source Metadata Framework (OMF) files which contain the help file information for those applications. These OMF files require special processing by ScrollKeeper in order for applications like Yelp to find help documentation. In order to accomplish proper registry of these OMF files when installing GNOME applications from packages, you should make sure that `omf` files are listed in `pkg-plist` and that your `Makefile` has this defined: .... INSTALLS_OMF="yes" .... == GConf Schema Installation GConf is the XML-based database that virtually all GNOME applications use for storing their settings. This database is defined by installed schema files that are used to generate `%gconf.xml` key files. Previously, these schema files and `%gconf.xml` key files were listed in the port's `pkg-plist`. Since this proved to be problematic, handling of GConf schemas was changed to something similar to that of link:{porters-handbook}[MANn] files. That is, for each schema file installed by your port, you must have the following listed in the `Makefile`: .... GCONF_SCHEMAS= my_app.schemas my_app2.schemas my_app3.schemas .... For example in `audio/gnome-media`: .... GCONF_SCHEMAS= CDDB-Slave2.schemas gnome-audio-profiles.schemas \ gnome-cd.schemas gnome-sound-recorder.schemas .... The schema files and `%gconf.xml` key files should not be in the `pkg-plist`. If you notice that the port doesn't has any `%gconf.xml` key files, but has schema files then you should not be use `GCONF_SCHEMAS`. It means, this port has broke either schema files or installation of GConf. == Shared MIME database If your port install files like `application/x-portname.xml` in `share/mime`, you have to add these two lines at the end of the `pkg-plist`: .... @exec %%LOCALBASE%%/bin/update-mime-database %D/share/mime @unexec %%LOCALBASE%%/bin/update-mime-database %D/share/mime .... Also make sure `shared-mime-info` is among the dependencies of your port. If your port use `gtk20`, you will have `shared-mime-info` indirectly. You can check indirect dependencies with `make describe`. -Example port to look at: https://svnweb.FreeBSD.org/ports/head/deskutils/drivel/[`deskutils/drivel`] +Example port to look at: https://cgit.FreeBSD.org/ports/tree/emulators/tilem/[`emulators/tilem`] == Desktop database Some ports provide MIME definitions in their `.desktop` files. If your port install `.desktop` file into `share/applications` and there is a line starting with `MimeType` in it, you need to update desktop database after install and deinstall. This database is represented by `share/applications/mimeinfo.cache` file. Add dependency on GNOME component `desktopfileutils` and these lines to the end of `pkg-plist`: .... @exec %%LOCALBASE%%/bin/update-desktop-database > /dev/null || /usr/bin/true @unexec %%LOCALBASE%%/bin/update-desktop-database > /dev/null || /usr/bin/true .... Also add following to the `post-install` target in port's Makefile: .... -@update-desktop-database .... -Example port to look at: https://svnweb.FreeBSD.org/ports/head/editors/leafpad/[`editors/leafpad`] +Example port to look at: https://cgit.FreeBSD.org/ports/tree/editors/leafpad/[`editors/leafpad`] [[libtool]] == Libtool Issues Most, if not all, GNOME applications depend on GNU's libtool. They also use the GNU configure system. If your port installs shared libraries, and includes an `ltmain.sh` script in its `${WRKSRC}` directory, you should add `USES=libtool` to your port's Makefile. == Distfiles To separate GNOME 2 distfiles from the GNOME 1 distfiles, and to keep the distfiles directory clean, GNOME 1 ports that download their distfiles from `${MASTER_SITE_GNOME}` must add the following to their Makefile: .... DIST_SUBDIR= gnome .... GNOME 2 ports that download their distfiles from `${MASTER_SITE_GNOME}` must include the following in their Makefile: .... DIST_SUBDIR= gnome2 .... Some GNOME distfiles come in both tar gzip as well as tar bzip2 format. To save time when downloading distfiles over slow links, you should use the bzip2 distfiles whenever possible. To do this, add the following to your port's Makefile: .... USE_BZIP2= yes .... If you still need help with your port, have a look at some of the existing ports for examples. The mailto:freebsd-gnome@FreeBSD.org[freebsd-gnome mailing list] is also there for you. diff --git a/website/content/en/java/_index.adoc b/website/content/en/java/_index.adoc index 71e77949db..8d528b6ae9 100644 --- a/website/content/en/java/_index.adoc +++ b/website/content/en/java/_index.adoc @@ -1,98 +1,98 @@ --- title: "FreeBSD Java® Project" sidenav: developers --- include::shared/en/urls.adoc[] = FreeBSD Java(R) Project [.right] image::../gifs/j2j.gif[Jump to Java(R)] == Getting Java There are two choices of Java Development Kits on FreeBSD: === OpenJDK The OpenJDK(R) project provides a native open-source implementation of the Java(R) SE Platform. It is available for all currently supported FreeBSD releases in the following combinations of versions (by architecture): *aarch64*: `openjdk8`, `openjdk11`, `openjdk12`, `openjdk13` *amd64*: `openjdk7`, `openjdk8`, `openjdk11`, `openjdk12`, `openjdk13` *arm6*: `openjdk8` *arm7*: `openjdk8` *i386*: `openjdk7`, `openjdk8`, `openjdk11`, `openjdk12`, `openjdk13` *powerpc*: `openjdk8` *powerpc64*: `openjdk8`, `openjdk11`, `openjdk12`, `openjdk13` -OpenJDK(R) is frequently updated, and it is suggested to refer to https://svnweb.freebsd.org/ports/head/java/[revision logs] for detailed release history. Additionally, one may choose to review more information at https://www.freshports.org/search.php?query=openjdk&search=go&num=10&stype=name&method=match&deleted=excludedeleted&start=1&casesensitivity=caseinsensitive[FreshPorts]. +OpenJDK(R) is frequently updated, and it is suggested to refer to https://cgit.freebsd.org/ports/log/java/[revision logs] for detailed release history. Additionally, one may choose to review more information at https://www.freshports.org/search.php?query=openjdk&search=go&num=10&stype=name&method=match&deleted=excludedeleted&start=1&casesensitivity=caseinsensitive[FreshPorts]. To install OpenJDK(R) package use the link:https://www.freebsd.org/cgi/man.cgi?query=pkg[`pkg`] utility or the ports system: `pkg install openjdk[version]` or `cd /usr/ports/java/openjdk[version]` `make install clean` where [version] is one of 7, 8, 11, 12, or 13. An example (`openjdk11`): `pkg install openjdk11` or `cd /usr/ports/java/openjdk11` `make install clean` === Oracle JDK for Linux This port installs the Java Development Kit from Oracle which was built for Linux. It will run under FreeBSD using the Linux compatibility. `pkg install linux-oracle-jdk18` or `cd /usr/ports/java/linux-oracle-jdk18` `make install clean` *Note:* Please note that due to the current licensing policy the Oracle JDK on FreeBSD binaries can not be distributed and you are only permitted to use them personally. For the same reason, the sources must be fetched manually. == Documentation * link:{porters-handbook}#using-java[Creating Ports] == I want to help by... === ... fixing bugs or adding new features The main repositories for the BSD port of OpenJDK are publically available on Github. Pull requests are welcome. You can find more information on this https://wiki.freebsd.org/Ports/openjdk_11[Wiki] === ... testing The best thing you can do is download the latest release, install it, and try all your favorite Java applications. If they don't work, see below. === ... reporting a bug If you find an application that does not work, or crashes, here are the steps you should follow before reporting it: . Try it again. . Check your settings for this application. Check to see if you made a mistake in starting it up. . Try it on a different platform. If you have access to a reference platform, try it there. (We need to determine if it is an application error, a Java bug, or a FreeBSD specific bug.) . Narrow down the problem. If it is your own code, narrow down the bug to the offending code. Otherwise, determine the steps required to reproduce the problem. . Notify the JDK porting team. Send email to freebsd-java@FreeBSD.org. Be sure to include the steps you have followed. . Finally, and most importantly, be willing to work with the team to fix the problem. === ...writing documentation Everyone can help here. If you have a suggestion to add to the documentation, write it up and send it to freebsd-java@FreeBSD.org diff --git a/website/content/en/platforms/arm.adoc b/website/content/en/platforms/arm.adoc index f990539a45..6531aa353e 100644 --- a/website/content/en/platforms/arm.adoc +++ b/website/content/en/platforms/arm.adoc @@ -1,123 +1,123 @@ --- title: "FreeBSD/ARM Project" sidenav: developers --- include::shared/authors.adoc[] include::shared/en/urls.adoc[] = FreeBSD/ARM Project == Introduction This page contains information about the FreeBSD port to the 32- and 64-bit ARM architectures and hardware. Discussion of the ARM ports takes place on the https://lists.freebsd.org/mailman/listinfo/freebsd-arm[freebsd-arm] mailing list. == Table Of Contents * <> * <> * <> * <> * <> * <> [[status]] == Status 32-bit ARM is officially a link:{committers-guide}#archs[Tier 2] architecture, as the link:../../[FreeBSD] project does not provide official releases or pre-built packages for this platform due to it primarily targeting the embedded arena. However, FreeBSD/ARM is being actively developed and maintained, is well supported, and provides an excellent framework for building ARM-based systems. FreeBSD/arm supports ARMv4 and ARMv5 processors. FreeBSD/armv6 supports ARMv6 and ARMv7 processors, including SMP on the latter. Initial support for 64-bit ARM is complete. 64-bit ARM platforms follow a set of standard conventions, and a single FreeBSD build will work on hardware from multiple vendors. As a result, FreeBSD will provide official releases for FreeBSD/arm64 and packages will be available. FreeBSD/arm64 is on the path to becoming a link:{committers-guide}#archs[Tier 1] architecture. [[hw]] == FreeBSD/ARM Hardware Notes FreeBSD/arm and FreeBSD/armv6 support a large range of ARM CPUs and development boards. Not every peripheral is supported on every CPU or board, though work continues towards this and contributions are always welcome. Conversely, many CPUs and boards not listed may work with only minimal changes needed. -Listing all supported devices on all CPUs and boards is impractical here, however much information can be obtained from the mailing list and archives, https://wiki.freebsd.org/FreeBSD/arm[the FreeBSD/arm Wiki pages], and also from the https://svnweb.freebsd.org/base/head/sys/arm/conf/[Kernel Configuration files] +Listing all supported devices on all CPUs and boards is impractical here, however much information can be obtained from the mailing list and archives, https://wiki.freebsd.org/FreeBSD/arm[the FreeBSD/arm Wiki pages], and also from the https://cgit.freebsd.org/src/tree/sys/arm/conf/[Kernel Configuration files] === Cores Supported * ARM9E * Most XScale * Marvel Feroceon * Marvel Sheeva * ARM10E * ARM11J * Cortex A5 * Cortex A7 * Cortex A8 * Cortex A9 * Cortex A12 * Cortex A15 === SoCs * Allwinner A10/A20 * Atmel AT91RM92 and AT91SAM9 families * Broadcom BCM2835 (used in Raspberry Pi) * Cavium CNS11xx * Freescale i.MX51, i.MX53, i.MX6 and Vybrid Family * Intel XSCALE * Marvell Orion, Kirkwood and Discovery Innovation families of systems-on-chip * Marvell Armada 500 (ARMv6) and Armada XP (ARMv7) * NXP LPC32x0 * Qualcomm Snapdragon * Rockchip RK3188 * Samsung Exynos5 and S3C24xxx * Texas Instruments DaVinci Digital Media SoC * TI OMAP * Xilinx Zynq7 family Note that not all peripherals are supported on all CPUs. === Boards * ArndaleBoard (Samsung Exynos5250) * Atmel AT91RM9200 * BeagleBoard and BeagleBoard-xM (TI OMAP3) * BeagleBone * Colibri VF50 Evaluation Board * Cubieboard(1,2) (Allwinner A10/A20) * Device Solutions Quartz * Gateworks Avila GW2348 and Cambria GW2358 * Genesi Efika MX Smarttop and Smartbook * Globalscale Technologies OpenRD platform * Google Chromebook * Kwikbyte KB9202B (as well as the older KB9202 and KB9202A) * Linksys NSLU2 * Marvell DB-88F5182, DB-88F5281, DB-88F6281, RD-88F6281, DB-78100 * Marvell DB-88F6781 (ARMv6) * Marvell DB-78460 (ARMv7) * Marvell Sheeva Plug and Dream Plug * Pandaboard (OMAP4) * Phytec Cosmic Board (Freescale Vybrid Family) * Raspberry Pi * Radxa Rock (Work in progress) * SBC6045 with Atmel at91sam9g45 * Technologic Systems TS-7200 and TS-7800 * Wandboard * Zedboard (Xilinx Zynq) Note that not all peripherals are supported on all boards. [[todo]] == What Needs To Be Done * SATA support needs to be added for boards currently missing it. * Other devices, such as watchdog, i2c and bus should be merged from NetBSD. [[links]] == FreeBSD/ARM Related Links * http://esd.et.ntust.edu.tw/downloads/2008_Embedded_Programming/2008_ESW/Embedded_3_ARM.pdf[Brief history of ARM] * http://www.netbsd.org/ports/#ports-by-cpu[NetBSD Arm projects] [[miniinst]] == Mini-Install guide {cognet} has written a mini-install guide for the current FreeBSD source. It is https://people.FreeBSD.org/~cognet/arm.html[available here]. [[list]] == FreeBSD/ARM mailing list To subscribe to this list, send mail to `` or visit http://lists.FreeBSD.org/mailman/listinfo/freebsd-arm[mailman interface]. diff --git a/website/content/en/platforms/mips.adoc b/website/content/en/platforms/mips.adoc index ab29b40770..e70abddd0c 100644 --- a/website/content/en/platforms/mips.adoc +++ b/website/content/en/platforms/mips.adoc @@ -1,78 +1,78 @@ --- title: "FreeBSD/MIPS Project" sidenav: developers --- include::shared/en/urls.adoc[] = FreeBSD/MIPS Project == Introduction This page contains information about porting FreeBSD to the MIPS(R) platform. Discussion of the MIPS port takes place on the https://lists.freebsd.org/mailman/listinfo/freebsd-mips[freebsd-mips] mailing list. == Table Of Contents * <> * <> * <> [[status]] == Status MIPS is a link:{committers-guide}#archs[Tier 2] architecture, and as such is not fully supported by the link:../../[FreeBSD] project. [[hw]] == FreeBSD/MIPS Hardware Notes FreeBSD/MIPS is a port of the FreeBSD operating system to platforms based around MIPS processors. At the moment, several MIPS32 and MIPS64 development boards and embedded platforms are being targeted. -Listing all supported devices on all CPUs and boards is impractical here, however much information can be obtained from the mailing list and archives, https://wiki.freebsd.org/FreeBSD/MIPS[the FreeBSD/MIPS Wiki pages], and also from the https://svnweb.freebsd.org/base/head/sys/mips/conf/[Kernel Configuration files] +Listing all supported devices on all CPUs and boards is impractical here, however much information can be obtained from the mailing list and archives, https://wiki.freebsd.org/FreeBSD/MIPS[the FreeBSD/MIPS Wiki pages], and also from the https://cgit.freebsd.org/src/tree/sys/mips/conf/[Kernel Configuration files] === CPUs The following non-exhaustive list of CPUs and CPU families are supported: * MIPS4Kc * MIPS24Kc * MIPS74Kc * Atheros AR71xx, AR724x, AR91xx, AR933x, AR934x * Cavium OCTEON * NetLogic XLR/XLS CPU family * SRI/Cambridge's BERI and CHERI open-source FPGA soft-cores Note that not all peripherals are supported on all CPUs. === Boards The following boards are supported: * Ubiquiti Networks Router-Station (AR7130) * Ubiquiti Networks Router-Station Pro (AR7161) * Ubiquiti Networks PicoStation M2HP (AR7241) * Ubiquiti Networks EdgeRouter Lite (OCTEON) * TP-Link TL-WR1043ND (AR9132) * Mikrotik RouterBoard RB450G * Alfa Networks Hornet UB (AR933x) * D-Link DIR-825 (AR7161) * Atheros PB44, PB47, AP94, AP96 reference designs (AR7161) * Atheros DB120 reference design (AR9344) * 8devices Carambola-2 (AR9330) * Engenius ENH-200 (AR7240+AR9285) * Buffalo Airstation WZR-300HP B0 A1 * MIPS Malta evaluation board * Lanner MR-320, MR-730, MR-995 (OCTEON) * Portwell CAM-0100 (OCTEON) * Radisys AMC-7211 / ATCA-7220 (OCTEON) * D-Link DSR-500, DSR-500N, DSR-1000 and DSR-1000N (OCTEON) * GE Intelligent Platforms WANIC 6354 (OCTEON) * Cavium development boards CN5860-EVB-NIC4, CN5650-EVB-NIC16, CN5200-EVB-MB4 Note that not all peripherals are supported on all boards. [[list]] == FreeBSD/MIPS mailing list Join the link:#list[FreeBSD/MIPS mailing list] to contribute code or learn about the status of the project. To subscribe to this list, send an email to `` or visit the http://lists.FreeBSD.org/mailman/listinfo/freebsd-mips[mailman interface]. diff --git a/website/content/en/ports/references.adoc b/website/content/en/ports/references.adoc index 7b8725e310..d5417016cd 100644 --- a/website/content/en/ports/references.adoc +++ b/website/content/en/ports/references.adoc @@ -1,25 +1,25 @@ --- title: "FreeBSD Ports -- References" sidenav: ports --- include::shared/en/urls.adoc[] = FreeBSD Ports -- References {{< form-ports >}} ''''' To start learning more about ports and packages, see link:{handbook}#ports[Installing Applications: Packages and Ports], a section of the link:{handbook}[FreeBSD Handbook]. The link:{porters-handbook}[Porter's Handbook] is the master reference for both creating new ports and maintaining existing ports, including a section on link:{porters-handbook}#keeping-up[Keeping Up]. It also contains more detail about the topics below, as well as more references for further study. You may also find the following to be useful: * The archives of the https://docs.FreeBSD.org/mail/current/freebsd-ports.html[FreeBSD ports mailing list]. * The article link:{contributing}#ports-contributing[Contributing to the FreeBSD Ports Collection]. * https://www.FreshPorts.org[FreshPorts.org] is a valuable tool for further information about individual ports, such as current version, last checkin, and many other useful statistics. You may subscribe to a mailing list to get the latest information about your favorite ports. * The manual pages for link:https://www.FreeBSD.org/cgi/man.cgi?query=ftp[`ftp`], link:https://www.FreeBSD.org/cgi/man.cgi?query=pkg&sektion=8[`pkg`], and link:https://www.FreeBSD.org/cgi/man.cgi?query=ports[`ports`]. * The link:../../portmgr/[Ports Management Team] (portmgr) pages. -* The https://svnweb.FreeBSD.org/ports[Web Interface to the Source Repository] allows you to browse the files in the source repository. Changes that affect the entire port system are now documented in the https://svnweb.FreeBSD.org/ports/head/CHANGES?view=markup[CHANGES] file. Changes that affect individual ports are now documented in the https://svnweb.FreeBSD.org/ports/head/UPDATING?view=markup[UPDATING] file. However, the definitive answer to any question is undoubtedly to read the source code of https://svnweb.FreeBSD.org/ports/head/Mk/bsd.port.mk?view=markup[bsd.port.mk], and associated files. +* The https://cgit.FreeBSD.org/ports/tree[Web Interface to the Source Repository] allows you to browse the files in the source repository. Changes that affect the entire port system are now documented in the https://cgit.FreeBSD.org/ports/tree/CHANGES[CHANGES] file. Changes that affect individual ports are now documented in the https://cgit.FreeBSD.org/ports/tree/UPDATING[UPDATING] file. However, the definitive answer to any question is undoubtedly to read the source code of https://cgit.FreeBSD.org/ports/tree/Mk/bsd.port.mk[bsd.port.mk], and associated files. diff --git a/website/content/en/ports/searching.adoc b/website/content/en/ports/searching.adoc index 5fc81596d3..1eb385770e 100644 --- a/website/content/en/ports/searching.adoc +++ b/website/content/en/ports/searching.adoc @@ -1,16 +1,16 @@ --- title: "Searching FreeBSD Ports" sidenav: ports --- = Searching FreeBSD Ports {{< form-ports >}} ''''' The form above will allow you to search for ports on this site. A completed search will take you to a link:https://www.FreeBSD.org/cgi/ports.cgi[more complete search page]. -However, if you already have the Ports Collection installed on your machine, you may also search by changing to the `/usr/ports` directory and performing `make search name=`__string__. See http://svnweb.FreeBSD.org/ports/head/Mk/bsd.port.subdir.mk?view=log[bsd.port.subdir.mk] for all the options. +However, if you already have the Ports Collection installed on your machine, you may also search by changing to the `/usr/ports` directory and performing `make search name=`__string__. Instead of by `name` you can search by port path (`path`), port information (`info`), maintainer (`maint`), port category (`cat`), build dependencies (`bdeps`), run dependencies (`rdeps`), the project web site (`www`), or any of these fields (`key`). Use `make quicksearch ...` to only display the port name, port directory, and one line description of the port. Another option is to visit https://www.FreshPorts.org[FreshPorts.org] and either browse the site or subscribe to the lists hosted there. diff --git a/website/content/en/ports/updating.adoc b/website/content/en/ports/updating.adoc index 4c6bad0010..be8e8dabb4 100644 --- a/website/content/en/ports/updating.adoc +++ b/website/content/en/ports/updating.adoc @@ -1,20 +1,20 @@ --- title: "Updating FreeBSD Ports" sidenav: ports --- include::shared/en/urls.adoc[] = Updating FreeBSD Ports {{< form-ports >}} ''''' The ports listed on these web pages are continually being updated. It is strongly recommended that you refresh the entire collection together, as many ports depend on other parts of the tree, even where that might seem counterintuitive (e.g. `japanese/`.) -Changes that affect the entire port system are now documented in the http://svnweb.FreeBSD.org/ports/head/CHANGES?view=markup[CHANGES] file. Changes that affect individual ports are now documented in the http://svnweb.FreeBSD.org/ports/head/UPDATING?view=markup[UPDATING] file. +Changes that affect the entire port system are now documented in the https://cgit.FreeBSD.org/ports/tree/CHANGES[CHANGES] file. Changes that affect individual ports are now documented in the https://cgit.FreeBSD.org/ports/tree/UPDATING[UPDATING] file. For more information about new, changed or removed ports/packages, or if you wish to search for a specific application to see if it's available as a port/package, you may use the form above; alternatively, you may wish to visit https://www.FreshPorts.org[FreshPorts.org] and either browse the site or subscribe to the lists hosted there. To learn more about installing and maintaining ports, see link:{handbook}#ports[Installing Applications: Packages and Ports], a section of the link:{handbook}[FreeBSD Handbook]; the section of the Porter's Handbook called link:{porters-handbook}#keeping-up[Keeping Up]; and the link:https://www.FreeBSD.org/cgi/man.cgi?query=ports[`ports manual page`].