Titre:zewaren.net | the personal website of erwan martin
La description :skip to main content zewaren.net main menu about me not so frequently asked questions and stuff files pxe articles en français main menu about me not so frequently asked questions and stuff electronic...
Geo IP vous fournit comme la latitude, la longitude et l'ISP (Internet Service Provider) etc. informations.
Notre service GeoIP a trouvé l'hôte zewaren.net.Actuellement, hébergé dans France et son fournisseur de services est Saveho SARL .
Les informations d'en-tête HTTP font partie du protocole HTTP que le navigateur d'un utilisateur envoie à appelé nginx contenant les détails de ce que le navigateur veut et acceptera de nouveau du serveur Web.
MX preference = 1, mail exchanger = mail1.enceinte.tf.
HtmlToText
skip to main content zewaren.net main menu about me not so frequently asked questions and stuff files pxe articles en français main menu about me not so frequently asked questions and stuff electronics and embedded systems (6) freebsd and linux (69) samba (6) miscelaneous (8) programming (47) windows (23) remote desktop (3) files software profiles (2) pxe hardware related tools (4) operating system installers (3) utilities (4) articles en français articles en français (6) welcome to zewaren.net. this site presents myself and mostly archives the solutions to some problems i once had. build your own freebsd ports and make packages out of them using jails, poudriere and portshaker sun, 2017-12-10 00:09 — zewaren situation you make custom ports of your applications. you would like to use pkg to install them on your production and development machines. solution build a poudriere server with portshaker! requirements: custom ports come in the form of a git port tree everything should run in a jail. git has many dependencies you don't want on your host systems (i'm looking a you bash). everything should use zfs as much as possible setting up the base system make sure the following kernel modules are loaded: tmpfs linux linux64 nullfs procfs fdescfsu linprocfs load them now: # kldload tmpfs # kldload linux # kldload linux64 # kldload nullfs # kldload procfs # kldload fdescfsu # kldload linprocfs make sure they're loaded on boot: # sysrc -f /boot/loader.conf tmpfs_load="yes" # sysrc -f /boot/loader.conf linux_load="yes" # sysrc -f /boot/loader.conf nullfs_load="yes" # sysrc -f /boot/loader.conf procfs_load="yes" # sysrc -f /boot/loader.conf fdescfsu_load="yes" # sysrc -f /boot/loader.conf linux64_load="yes" # sysrc -f /boot/loader.conf linprocfs_load="yes" make sure jails can use ipc # sysctl security.jail.sysvipc_allowed=1 # sysrc jail_sysvipc_allow=yes create a zfs dataset for the poudriere system: # zfs create zroot/poudriere create a jail, and make sure the jail is allowed to create build jails and manage its zfs dataset. here the relevant configuration for a ezjail jail: # cat /usr/local/etc/ezjail/poudriere [...] export jail_poudriere_zfs_datasets="zroot/poudriere" export jail_poudriere_parameters="children.max=20 allow.mount allow.mount.tmpfs allow.mount.devfs allow.mount.procfs allow.mount.zfs allow.mount.nullfs allow.mount.linprocfs allow.raw_sockets allow.socket_af allow.sysvipc allow.chflags enforce_statfs=1 ip6=inherit ip4=inherit" setting up poudriere in the jail install poudriere and dialog4ports : # make -c /usr/ports/ports-mgmt/dialog4ports install clean # make -c /usr/ports/ports-mgmt/poudriere install clean set the moundpoint of the zfs dataset: # zfs set mountpoint=/poudriere zroot/poudriere make sure the zfs dataset for the ports and the distfiles exists: # zfs create zroot/poudriere/ports # zfs create zroot/poudriere/ports/distfiles configure poudriere in /usr/local/etc/poudriere.conf : zpool: zroot zrootfs: /poudriere freebsd_host: "ftp.xxx.freebsd.org" distfiles_cache: /usr/local/poudriere/ports/distfiles no_linux: 1 create a port tree, but don't populate it. it will be done by portshaker later: # poudriere ports -c -f -f none -m /usr/local/poudriere/ports/main -p main create a build jail: # poudriere jail -c -j 111x64 -v 11.1-release -a amd64 # poudriere jail -l jailname version arch method timestamp path 111x64 11.1-release amd64 ftp 2017-12-08 14:58:09 /usr/local/poudriere/jails/111x64 hehe, we have a jail in a jail. setting up portshaker we're going to build a port tree consisting of the regular freebsd main one (using portsnap ) merged with our own (using git ). portskaker is an awesome tool. it will merge different port tree, handling conflicts intelligently, and even merging the uids/gids files properly. this example will only build a single port tree, but you can configure as many as you want. install portshaker : # make -c /usr/ports/ports-mgmt/portshaker install clean install git: # make -c /usr/ports/devel/git install clean write /usr/local/etc/portshaker.conf : mirror_base_dir="/var/cache/portshaker" ports_trees="main" main_ports_tree="/usr/local/poudriere/ports/main" main_merge_from="portsnap custom" write the portshaker tree source for portsnap , in /usr/local/etc/portshaker.d/portsnap : #!/bin/sh . /usr/local/share/portshaker/portshaker.subr if [ "$1" != '--' ]; then err 1 "extra arguments" fi shift method="portsnap" run_portshaker_command $* write the portshaker tree source for custom , in /usr/local/etc/portshaker.d/custom : #!/bin/sh . /usr/local/share/portshaker/portshaker.subr if [ "$1" != '--' ]; then err 1 "extra arguments" fi shift method="git" git_clone_uri="git@example.com:somegroup/freebsd-ports.git" git_branch=master run_portshaker_command $* make sure both files are executable. fetch both port trees: # portshaker -u you should see portsnap and a git clone being executed. merge the port trees: # portshaker -m you should have a complete port tree in /usr/local/poudriere/ports/main/ . look for your custom ports and check that they're here. setting up nginx we want to use poudriere's web interface. install nginx: # make -c /usr/ports/www/nginx install clean add a server in /usr/local/etc/nginx/nginx.conf server { listen 80 default; server_name _; root /usr/local/share/poudriere/html; location /data { alias /usr/local/poudriere/data/logs/bulk; autoindex on; } location /packages { root /usr/local/poudriere/data; autoindex on; } } that's it! no cgi, no proxy, no whatever. just plain files to serve. test it all write a list of package into a pkglist file ( /usr/local/etc/poudriere.d/someports-pkglist ): www/nginx sysutils/tmux set the port options: poudriere options -j 111x64 -p main -f /usr/local/etc/poudriere.d/someports-pkglist start the build: # poudriere bulk -j 8 -j 110x64 -p main -f /usr/local/etc/poudriere.d/someports-pkglist -v -v -v [00:00:00] ====>> creating the reference jail... done [00:00:00] ====>> mounting system devices for 111x64-main [00:00:00] ====>> mounting ports/packages/distfiles [00:00:00] ====>> using packages from previously failed build [00:00:00] ====>> mounting packages from: /usr/local/poudriere/data/packages/111x64-main [00:00:00] ====>> copying /var/db/ports from: /usr/local/etc/poudriere.d/111x64-options [00:00:00] ====>> appending to make.conf: /usr/local/etc/poudriere.d/111x64-make.conf /etc/resolv.conf -> /usr/local/poudriere/data/.m/111x64-main/ref/etc/resolv.conf [00:00:00] ====>> starting jail 111x64-main [00:00:00] ====>> logs: /usr/local/poudriere/data/logs/bulk/111x64-main/2017-12-08_16h59m32s [00:00:00] ====>> loading moved [00:00:01] ====>> calculating ports order and dependencies [...] creating repository in /tmp/packages: 100% packing files for repository: 100% [00:16:07] ====>> committing packages to repository [00:16:07] ====>> removing old packages [00:16:07] ====>> built ports: ports-mgmt/pkg devel/automake-wrapper devel/autoconf-wrapper print/indexinfo devel/pkgconf devel/pcre devel/gettext-runtime www/nginx lang/perl5.24 devel/gettext-tools devel/p5-locale-gettext devel/gmake misc/help2man print/texinfo devel/m4 devel/libtool devel/autoconf devel/automake devel/libevent sysutils/tmux [111x64-main] [2017-12-08_16h59m32s] [committing:] queued: 20 built: 20 failed: 0 skipped: 0 ignored: 0 tobuild: 0 time: 00:16:07 [00:16:07] ====>> logs: /usr/local/poudriere/data/logs/bulk/111x64-main/2017-12-08_16h59m32s [00:16:07] ====>> cleaning up [00:16:07] ====>> unmounting file systems connect to the web interface: look at the build lists: look at the build report: use your pkg repository on other systems now that our packages are built, let's use them on other systems: make sure the config directory exists: # mkdir -p /usr/local/etc/pkg/repos write a pkg repository config file in /usr/local/etc/pkg/repos/poudriere.conf : poudriere: { url: "http://pkg.example.com/packages/1
Whois est un protocole qui permet d'accéder aux informations d'enregistrement.Vous pouvez atteindre quand le site Web a été enregistré, quand il va expirer, quelles sont les coordonnées du site avec les informations suivantes. En un mot, il comprend ces informations;
For more information on Whois status codes, please visit https://icann.org/epp
NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.
TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.
The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.
REGISTRAR OVH
SERVERS
SERVER net.whois-servers.net
ARGS domain =zewaren.net
PORT 43
TYPE domain RegrInfo DOMAIN
NAME zewaren.net
CHANGED 2017-07-24
CREATED 2005-08-22
STATUS clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Nous utilisons des cookies pour personnaliser votre expérience sur notre site. En poursuivant votre navigation, vous acceptez cette utilisation. Apprendre encore plus
zewaren.net rapport :
Visitez le site