Visit Our UNIX and Linux User Community

Full Discussion: OpenBSD: ports
Top Forums UNIX for Dummies Questions & Answers OpenBSD: ports Post 21330 by auswipe on Wednesday 15th of May 2002 11:01:06 AM
Old 05-15-2002
Yeah. That'll do it.

Next time I suggest that you sniff that tarball to make sure that it hasn't gone bad! Nobody likes old curdled tarballs Smilie
 
Test Your Knowledge in Computers #704
Difficulty: Medium
Under the same-origin policy, a web browser permits scripts contained in a first web page to access data in a second web page, but only if both web pages have the same origin.
True or False?

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

please help with openbsd 2.9

Please help. I have downloaded the openbsd 2.9 snapshot from ftp.openbsd.org. the following files were downloaded from the snapshot dir. ( the whole dir. was downloaded ) base29,bsd,bsd.rd,cdrom29.fs,cksum,comp29,etc29,all three floppy images,game29,index,install.ata,install.chs... (11 Replies)
Discussion started by: Blunt_Killer
11 Replies

2. UNIX for Dummies Questions & Answers

OpenBSD installation

Hello I'm trying to install OpenBSD on my computer.. My partitions are these: wd0c : Where I have windows XP (NTFS) wd0j : Where I want to install OpenBSD (4.2BSD) wd0k: Where I have the installation files (Fat32) When the installation comes to the part where it mounts... (6 Replies)
Discussion started by: Hamcha
6 Replies

3. UNIX for Dummies Questions & Answers

OpenBSD Questions

Hello Today I installed OpenBSD, and it went great (I hope) But I'm a little confused.. I've run ŽLinux slackware before, and when I recompiled the kernel there, I did it in /usr/src/linux-xxx But in OpenBSD the /usr/src dir is empty! And how do I get X-windows to work? I tried to... (2 Replies)
Discussion started by: Hamcha
2 Replies

4. UNIX for Dummies Questions & Answers

Error while setting up the Horde framework using OpenBSD ports

Hello everyone, while setting up the Horde framework on OpenBSD 3.0, I discovered the following error: configure: error: Cannot find rfc822.h. Please check your IMAP installation. *** Error code 1 Stop in /usr/ports/www/php4 (line 1703 of /usr/ports/infrastructure/mk/bsd.port.mk). ***... (1 Reply)
Discussion started by: Lexx
1 Replies

5. UNIX for Dummies Questions & Answers

OpenBSD: dircolors?

Hi, I'm wondering how I can get colors on the stuff that ls prints out in OpenBSD? //Maestin (4 Replies)
Discussion started by: Maestin
4 Replies

6. BSD

Snort on openbsd

Im trying to gather some info to set up snort on openbsd 3.2, has anyone out there managed to get it up and running ? My initial attempts seem to be quite below par (4 Replies)
Discussion started by: malcontent
4 Replies

7. BSD

Trying to get into OpenBSD

I am an eight year Linux user and after getting into an argument with someone about OpenBSD overiding my theory that OS security is 50% OS and 50% admin skill, I decided to try OpenBSD for myself. I've tried BSDs before and haven't been able to get into them for day to dy use, but I am going to... (7 Replies)
Discussion started by: deckard
7 Replies

8. BSD

openbsd-pf

hello , I wondered if anyone could assist me in writing a simple packet filter firewall on my OpenBSD v4.5. All I intend doing is to have two firewalling machine on a separate network : 192.168.1.1 ext_if = xl0 (dhcp) // Internet interface int_if=xl1 // Internatl interface ... (0 Replies)
Discussion started by: mattjam
0 Replies

9. BSD

OpenBSD pf problems

I am having troubles with this pf configuration, it seems when loaded nothing can access my server on the internal interface for the LAN, I cannot see why, and it's pretty much based off the very standard example in the OpenBSD faq. When I unload the configuration, I can access the DNS server on... (0 Replies)
Discussion started by: John Tate
0 Replies

10. BSD

PF troubles on OpenBSD 5.0

I am setting up a system as an ADSL gateway. ADSL is working fine. PF is not forwarding for some reason. # ifconfig lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33196 priority: 0 groups: lo inet6... (0 Replies)
Discussion started by: John Tate
0 Replies
PRISTINE-TAR(1) 						   pristine-tar 						   PRISTINE-TAR(1)

NAME
pristine-tar - regenerate pristine tarballs SYNOPSIS
pristine-tar [-vdk] gendelta tarball delta pristine-tar [-vdk] gentar delta tarball pristine-tar [-vdk] [-m message] commit tarball [upstream] pristine-tar [-vdk] checkout tarball pristine-tar [-vdk] list DESCRIPTION
pristine-tar can regenerate an exact copy of a pristine upstream tarball using only a small binary delta file and the contents of the tarball, which are typically kept in an upstream branch in version control. The delta file is designed to be checked into version control along-side the upstream branch, thus allowing Debian packages to be built entirely using sources in version control, without the need to keep copies of upstream tarballs. pristine-tar supports compressed tarballs, calling out to pristine-gz(1), pristine-bz2(1), and pristine-xz(1) to produce the pristine gzip, bzip2, and xz files. COMMANDS
pristine-tar gendelta tarball delta This takes the specified upstream tarball, and generates a small binary delta file that can later be used by pristine-tar gentar to recreate the tarball. If the delta filename is "-", it is written to standard output. pristine-tar gentar delta tarball This takes the specified delta file, and the files in the current directory, which must have identical content to those in the upstream tarball, and uses these to regenerate the pristine upstream tarball. If the delta filename is "-", it is read from standard input. pristine-tar commit tarball [upstream] pristine-tar commit generates a pristine-tar delta file for the specified tarball, and commits it to version control. The pristine-tar checkout command can later be used to recreate the original tarball based only on the information stored in version control. The upstream parameter specifies the tag or branch that contains the same content that is present in the tarball. This defaults to "refs/heads/upstream", or if there's no such branch, any branch matching "upstream". The name of the tree it points to will be recorded for later use by pristine-tar checkout. Note that the content does not need to be 100% identical to the content of the tarball, but if it is not, additional space will be used in the delta file. The delta files are stored in a branch named "pristine-tar", with filenames corresponding to the input tarball, with ".delta" appended. This branch is created or updated as needed to add each new delta. pristine-tar checkout tarball This regenerates a copy of the specified tarball using information previously saved in version control by pristine-tar commit. pristine-tar list This lists tarballs that pristine-tar is able to checkout from version control. OPTIONS
-v --verbose Verbose mode, show each command that is run. -d --debug Debug mode. -k --keep Don't clean up the temporary directory on exit. -m message --message=message Use this option to specify a custom commit message to pristine-tar commit. EXAMPLES
Suppose you maintain the hello package, in a git repository. You have just created a tarball of the release, hello-1.0.tar.gz, which you will upload to a "forge" site. You want to ensure that, if the "forge" loses the tarball, you can always recreate exactly that same tarball. And you'd prefer not to keep copies of tarballs for every release, as that could use a lot of disk space when hello gets the background mp3s and user-contributed levels you are planning for version 2.0. The solution is to use pristine-tar to commit a delta file that efficiently stores enough information to reproduce the tarball later. cd hello git tag -s 1.0 pristine-tar commit ../hello-1.0.tar.gz 1.0 Remember to tell git to push both the pristine-tar branch, and your tag: git push --all --tags Now it is a year later. The worst has come to pass; the "forge" lost all its data, you deleted the tarballs to make room for bug report emails, and you want to regenerate them. Happily, the git repository is still available. git clone git://github.com/joeyh/hello.git cd hello pristine-tar checkout ../hello-1.0.tar.gz LIMITATIONS
Only tarballs, gzipped tarballs, bzip2ed tarballs, and xzed tarballs are currently supported. Currently only the git revision control system is supported by the "checkout" and "commit" commands. It's ok if the working copy is not clean or has uncommitted changes, or has changes staged in the index; none of that will be touched by "checkout" or "commit". ENVIRONMENT
TMPDIR Specifies a location to place temporary files, other than the default. AUTHOR
Joey Hess <joeyh@debian.org> Licensed under the GPL, version 2 or above. perl v5.14.2 2013-06-01 PRISTINE-TAR(1)

Featured Tech Videos

All times are GMT -4. The time now is 12:35 PM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy