Skip to main content
  • Home
  • Development
  • Documentation
  • Donate
  • Operational login
  • Browse the archive

swh logo
SoftwareHeritage
Software
Heritage
Archive
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

Revision df716c98d203ab64cdf05f9c17fdae565b7daa1c authored by Eelco Dolstra on 23 June 2012, 04:28:35 UTC, committed by Eelco Dolstra on 23 June 2012, 04:28:35 UTC
In chroot builds, use a private network namespace
On Linux it's possible to run a process in its own network namespace,
meaning that it gets its own set of network interfaces, disjunct from
the rest of the system.  We use this to completely remove network
access to chroot builds, except that they get a private loopback
interface.  This means that:

- Builders cannot connect to the outside network or to other processes
  on the same machine, except processes within the same build.

- Vice versa, other processes cannot connect to processes in a chroot
  build, and open ports/connections do not show up in "netstat".

- If two concurrent builders try to listen on the same port (e.g. as
  part of a test), they no longer conflict with each other.

This was inspired by the "PrivateNetwork" flag in systemd.
1 parent 2f3f413
  • Files
  • Changes
  • 517c173
  • /
  • substitute.mk
Raw File Download

To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.

  • revision
  • directory
  • content
revision badge
swh:1:rev:df716c98d203ab64cdf05f9c17fdae565b7daa1c
directory badge
swh:1:dir:517c173c82cb5e65df3fd3ff4044ca0fadd04097
content badge
swh:1:cnt:eb489c97a50982025185a9d92590839e40c7329a

This interface enables to generate software citations, provided that the root directory of browsed objects contains a citation.cff or codemeta.json file.
Select below a type of object currently browsed in order to generate citations for them.

  • revision
  • directory
  • content
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
substitute.mk
%: %.in Makefile
	sed \
	 -e "s^@abs_top_srcdir\@^$(abs_top_srcdir)^g" \
	 -e "s^@abs_top_builddir\@^$(abs_top_builddir)^g" \
	 -e "s^@extra1\@^$(extra1)^g" \
	 -e "s^@prefix\@^$(prefix)^g" \
	 -e "s^@bindir\@^$(bindir)^g" \
	 -e "s^@datadir\@^$(datadir)^g" \
	 -e "s^@sysconfdir\@^$(sysconfdir)^g" \
	 -e "s^@localstatedir\@^$(localstatedir)^g" \
	 -e "s^@datadir\@^$(datadir)^g" \
	 -e "s^@libdir\@^$(libdir)^g" \
	 -e "s^@libexecdir\@^$(libexecdir)^g" \
	 -e "s^@storedir\@^$(storedir)^g" \
	 -e "s^@system\@^$(system)^g" \
	 -e "s^@shell\@^$(bash)^g" \
	 -e "s^@curl\@^$(curl)^g" \
	 -e "s^@bzip2\@^$(bzip2)^g" \
	 -e "s^@perl\@^$(perl)^g" \
	 -e "s^@perlFlags\@^$(perlFlags)^g" \
	 -e "s^@coreutils\@^$(coreutils)^g" \
	 -e "s^@sed\@^$(sed)^g" \
	 -e "s^@tar\@^$(tar)^g" \
	 -e "s^@gzip\@^$(gzip)^g" \
	 -e "s^@pv\@^$(pv)^g" \
	 -e "s^@tr\@^$(tr)^g" \
	 -e "s^@dot\@^$(dot)^g" \
	 -e "s^@xmllint\@^$(xmllint)^g" \
	 -e "s^@xmlflags\@^$(xmlflags)^g" \
	 -e "s^@xsltproc\@^$(xsltproc)^g" \
	 -e "s^@sqlite_bin\@^$(sqlite_bin)^g" \
	 -e "s^@version\@^$(VERSION)^g" \
	 -e "s^@perlbindings\@^$(perlbindings)^g" \
	 -e "s^@testPath\@^$(coreutils):$$(dirname $$(type -p expr))^g" \
	 < $< > $@ || rm $@
	if test -x $<; then chmod +x $@; fi
The diff you're trying to view is too large. Only the first 1000 changed files have been loaded.
Showing with 0 additions and 0 deletions (0 / 0 diffs computed)
swh spinner

Computing file changes ...

back to top

Software Heritage — Copyright (C) 2015–2026, The Software Heritage developers. License: GNU AGPLv3+.
The source code of Software Heritage itself is available on our development forge.
The source code files archived by Software Heritage are available under their own copyright and licenses.
Terms of use: Archive access, API— Content policy— Contact— JavaScript license information— Web API