Re: quick query.
thanks, it took me a while to find 2.2.39, but thanks to you guys its ok now. PEBKAC indeed... On 10 October 2012 21:05, Bob Beck wrote: > It is for me > > #export PKG_PATH= > http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64 > # pkg_add tor > tor-0.2.2.39: ok > The following new rcscripts were installed: /etc/rc.d/tor > See rc.d(8) for details. > # pkg_info tor > Information for inst:tor-0.2.2.39 > > Comment: > anonymity service using onion routing > > Description: > Tor is a connection-based low-latency anonymous communication system that > protects TCP streams: web browsing, instant messaging, irc, ssh, etc. > > Maintainer: Pascal Stumpf > > WWW: http://www.torproject.org/ > > > > Looks like PEBKAC. > > > On Wed, Oct 10, 2012 at 4:48 PM, sharon dvir wrote: > > it looks like Tor just isn't there. > > which means that in order to go from 2.2.35 to 2.2.39 i'll have to > compile > > it manually. > > which is no problem, but hence a need for the tool i originally asked > > about. > > or am i missing something? > > BTW, 2.2.39 fixes some remote exploits for Tor, in case anyone is > running > > it. > > thanks everyone. > > > > On 10 October 2012 18:09, Peter N. M. Hansteen wrote: > > > >> Martin Pelikan writes: > >> > >> > as sthen@ kindly corrected me the some time ago, we now have > >> > pkg.conf(5) and "installpath". > >> > >> You're right of course -- pkg.conf has been with us for a while (first > >> appearance in 4.8 it seems). > >> > >> > This way it'll work even if you don't invoke package updates from your > >> > shell, but using some kind of remote administration software for > >> > example. > >> > >> Yes. That functionality would be relevant to the OP. I'd managed to > >> forget all about it, probably because the old .profile trick works so > >> well in other contexts. > >> > >> - P > >> > >> -- > >> Peter N. M. Hansteen, member of the first RFC 1149 implementation team > >> http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ > >> "Remember to set the evil bit on all malicious network traffic" > >> delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: quick query.
On 2012-10-10, sharon dvir wrote: > it looks like Tor just isn't there. > which means that in order to go from 2.2.35 to 2.2.39 i'll have to compile > it manually. then you're running 5.1; you will either need to compile manually or move to -current. if you're looking to keep packages up-to-date then using -current binary snapshots is often the simplest method. at the moment, the 5.1-stable ports tree has 0.2.2.37 and the 5.2-stable tree has 0.2.2.38, -current has 0.2.2.39.
Re: quick query.
It is for me #export PKG_PATH=http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64 # pkg_add tor tor-0.2.2.39: ok The following new rcscripts were installed: /etc/rc.d/tor See rc.d(8) for details. # pkg_info tor Information for inst:tor-0.2.2.39 Comment: anonymity service using onion routing Description: Tor is a connection-based low-latency anonymous communication system that protects TCP streams: web browsing, instant messaging, irc, ssh, etc. Maintainer: Pascal Stumpf WWW: http://www.torproject.org/ Looks like PEBKAC. On Wed, Oct 10, 2012 at 4:48 PM, sharon dvir wrote: > it looks like Tor just isn't there. > which means that in order to go from 2.2.35 to 2.2.39 i'll have to compile > it manually. > which is no problem, but hence a need for the tool i originally asked > about. > or am i missing something? > BTW, 2.2.39 fixes some remote exploits for Tor, in case anyone is running > it. > thanks everyone. > > On 10 October 2012 18:09, Peter N. M. Hansteen wrote: > >> Martin Pelikan writes: >> >> > as sthen@ kindly corrected me the some time ago, we now have >> > pkg.conf(5) and "installpath". >> >> You're right of course -- pkg.conf has been with us for a while (first >> appearance in 4.8 it seems). >> >> > This way it'll work even if you don't invoke package updates from your >> > shell, but using some kind of remote administration software for >> > example. >> >> Yes. That functionality would be relevant to the OP. I'd managed to >> forget all about it, probably because the old .profile trick works so >> well in other contexts. >> >> - P >> >> -- >> Peter N. M. Hansteen, member of the first RFC 1149 implementation team >> http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ >> "Remember to set the evil bit on all malicious network traffic" >> delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: quick query.
On 10.10.2012, at 23:23, Peter N. M. Hansteen wrote: > My own take on keeping OpenBSD systems reasonably up to date can be > found at http://bsdly.blogspot.no/2012/07/keeping-your-openbsd-system-in-trim.html > (a "works for me" guide). worked for me: # uname -a OpenBSD reed.riedhausen.net 4.4 GENERIC#1021 i386 # uptime 12:57PM up 607 days, 3:16, 1 user, load averages: 0.25, 0.26, 0.24 thank you, OpenBSD! I can't write that in big enough letters. You made part of my life worry-free for 607 days _in a row_. side note to all you "running outdated systems is an invitation to get hacked" guys - point taken. Updates are not a value in themselves, but part of a larger picture... fl
Re: quick query.
it looks like Tor just isn't there. which means that in order to go from 2.2.35 to 2.2.39 i'll have to compile it manually. which is no problem, but hence a need for the tool i originally asked about. or am i missing something? BTW, 2.2.39 fixes some remote exploits for Tor, in case anyone is running it. thanks everyone. On 10 October 2012 18:09, Peter N. M. Hansteen wrote: > Martin Pelikan writes: > > > as sthen@ kindly corrected me the some time ago, we now have > > pkg.conf(5) and "installpath". > > You're right of course -- pkg.conf has been with us for a while (first > appearance in 4.8 it seems). > > > This way it'll work even if you don't invoke package updates from your > > shell, but using some kind of remote administration software for > > example. > > Yes. That functionality would be relevant to the OP. I'd managed to > forget all about it, probably because the old .profile trick works so > well in other contexts. > > - P > > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: quick query.
Martin Pelikan writes: > as sthen@ kindly corrected me the some time ago, we now have > pkg.conf(5) and "installpath". You're right of course -- pkg.conf has been with us for a while (first appearance in 4.8 it seems). > This way it'll work even if you don't invoke package updates from your > shell, but using some kind of remote administration software for > example. Yes. That functionality would be relevant to the OP. I'd managed to forget all about it, probably because the old .profile trick works so well in other contexts. - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: quick query.
2012/10/10 Peter N. M. Hansteen : > I tend to keep the following line in my ~/.profile > > export > PKG_PATH=http://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/packages/`uname -m`/ Hi, as sthen@ kindly corrected me the some time ago, we now have pkg.conf(5) and "installpath". This way it'll work even if you don't invoke package updates from your shell, but using some kind of remote administration software for example. -- Martin Pelikan
Re: quick query.
sharon dvir writes: > hello, i couldnt find an easy way to keep my packages updated with new > versions out of the repositories. I tend to keep the following line in my ~/.profile export PKG_PATH=http://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/packages/`uname -m`/ (which you really should adjust to look at an appropriate mirror and perhaps use `uname -r` to automagically select your release is if you're not running snapshost) and then do a $ sudo pkg_add -vui every now and then. Assuming you trust the mirror, this will give you updates relevant to the release you're running. For learning about the OpenBSD packages system, the canonical way to start is to read http://www.openbsd.org/faq/faq15.html and relevant man pages. My own take on keeping OpenBSD systems reasonably up to date can be found at http://bsdly.blogspot.no/2012/07/keeping-your-openbsd-system-in-trim.html (a "works for me" guide). - Peter -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
