Keeping installed ports up-to-date
HELO, whatbs the correct procedure for keeping ports that are installed up to date when the system is updated with CVS? Do I need to make uninstall the ports, perform the cvs update, build the new system and then make the new ports? Giridhari
CVS checkout for OPENBSD_5_0 : aborted
HELO have tried a cvs checkout of OPENBSD_5_0 several times in the last week or two and have seen cvs abort: cvs checkout: Updating src/games/snake cvs [chckout aborted]: could not chdir to src/games/snake/snake : Not a directory Could someone have a look at this please.
Re: CVS checkout for OPENBSD_5_0 : aborted
I'm not sure what you mean. Are you suggesting I should read up on how to operate cvs, or is there something specific about CVS and OPenBSD I should be aware of? I'm following the faq. I have updated several times in the past with CVS with no trouble at all. -Original Message- From: Richard Toohey Sent: Tuesday, February 14, 2012 5:15 PM To: Giridhari Cc: misc@openbsd.org Subject: Re: CVS checkout for OPENBSD_5_0 : aborted On 14/02/2012, at 5:01 PM, Giridhari wrote: HELO have tried a cvs checkout of OPENBSD_5_0 several times in the last week or two and have seen cvs abort: cvs checkout: Updating src/games/snake cvs [chckout aborted]: could not chdir to src/games/snake/snake : Not a directory Could someone have a look at this please. Have you tried Google yet?
Re: CVS checkout for OPENBSD_5_0 : aborted
$ ls -F src/games/snake/ did you `make build' without `make obj' first? --patrick I'm not sure why I would do that. CVS doesn't build anything. Can you explain a bit about why you suggest that? Please excuse me if I don't know what you mean. Giridhari
NFS : RPC: Program not registered
HELO. I am following http://openbsd.org/faq/faq6.html#NFS and have the server running, and showmount shows an export but on the client when I get to the line in the faq # mount -t nfs 10.0.0.1:/work /mnt and adapt it to the setup I have here I get the message RPC: Program not registered I did a bit of searching but couldnbt find anything for OpenBSD about this. Everything else in the faq has worked fine. What am I doing wrong? Giridhari
Re: Program not registered
Thankyou all for such prompt replies. I have confirmed that portmap, mountd and nfs are all reported as running by rpcinfo, just like it says in the faq. I have concentrated on the server first. What I have done: Exactly what the faq says for setting up NFS. I have added a line in /etc/exports /tmp -all dirs -maproot=user1 -network=10.1.1.1 -mask=255.255.255.0 and restarted mountd. showmount -e lists the export correctly, corresponding to the exports file in the /etc/exports file. Since the output rom rpcinfo is from the response from mountd, it would appear to be working (10.1.1.1:/tmp is exported). showmount -a does not show anything though; does this only show what is actually mounted, not just exported? So, still on the server, I tried mounting 10.1.1.1:/tmp but nfs_mount returned Permission denied. That was with just the mount command- as suggested by lilit-aibolit - allowing mount to select the filesystem-specific program itself. I should be able to mount an NFS on the server it is exported from shouldn't I? I'm pretty sure I've done this before, though maybe not on OpenBSD. -Original Message- From: lilit-aibolit Sent: Thursday, January 19, 2012 11:54 PM To: misc@openbsd.org ; giridh...@live.com.au Subject: Re: NFS : RPC: Program not registered 19.01.2012 13:29, Giridhari P?P8QP5Q: HELO. I am following http://openbsd.org/faq/faq6.html#NFS and have the server running, and showmount shows an export but on the client when I get to the line in the faq # mount -t nfs 10.0.0.1:/work /mnt and adapt it to the setup I have here I get the message RPC: Program not registered I did a bit of searching but couldnbt find anything for OpenBSD about this. Everything else in the faq has worked fine. What am I doing wrong? Giridhari . try mount without -t nfs also be sure /mnt is created on clinet also try sudo mount
Re: Program not registered
ERRATA Since the output rom rpcinfo is from the response from mountd, it would appear to be working (10.1.1.1:/tmp is exported). Should be Since the output from showmount is from the response from mountd, it would appear to be working (10.1.1.1:/tmp is exported). Excuse me. -Original Message- From: Giridhari Sent: Friday, January 20, 2012 3:04 PM To: misc@openbsd.org Subject: Re: Program not registered Thankyou all for such prompt replies. I have confirmed that portmap, mountd and nfs are all reported as running by rpcinfo, just like it says in the faq. I have concentrated on the server first. What I have done: Exactly what the faq says for setting up NFS. I have added a line in /etc/exports /tmp -all dirs -maproot=user1 -network=10.1.1.1 -mask=255.255.255.0 and restarted mountd. showmount -e lists the export correctly, corresponding to the exports file in the /etc/exports file. Since the output rom rpcinfo is from the response from mountd, it would appear to be working (10.1.1.1:/tmp is exported). showmount -a does not show anything though; does this only show what is actually mounted, not just exported? So, still on the server, I tried mounting 10.1.1.1:/tmp but nfs_mount returned Permission denied. That was with just the mount command- as suggested by lilit-aibolit - allowing mount to select the filesystem-specific program itself. I should be able to mount an NFS on the server it is exported from shouldn't I? I'm pretty sure I've done this before, though maybe not on OpenBSD. -Original Message- From: lilit-aibolit Sent: Thursday, January 19, 2012 11:54 PM To: misc@openbsd.org ; giridh...@live.com.au Subject: Re: NFS : RPC: Program not registered 19.01.2012 13:29, Giridhari P?P8QP5Q: HELO. I am following http://openbsd.org/faq/faq6.html#NFS and have the server running, and showmount shows an export but on the client when I get to the line in the faq # mount -t nfs 10.0.0.1:/work /mnt and adapt it to the setup I have here I get the message RPC: Program not registered I did a bit of searching but couldnbt find anything for OpenBSD about this. Everything else in the faq has worked fine. What am I doing wrong? Giridhari . try mount without -t nfs also be sure /mnt is created on clinet also try sudo mount
Re: Dennis Ritchie
Reading openbsd source code is like reading eloquent poetry, and in itself is a fitting tribute to Dennis Ritchie. It is hard to imagine that one man developed a software language that is so versatile, and not only is not just a historical milestone, but after it's release by Dennis, and Brian Kernighan in 1978 is still a mainstay after over 30 years. Thankyou Dennis. I love C and you created something I love, and I don't think I'm alone. I think that there are few things in this world that are held in as high esteem as the C language. It is a privilege to be able to write it really, and now the creator of that privilege is on his way to heaven : ) -Original Message- From: Dunceor Sent: Thursday, October 13, 2011 8:56 PM To: dco...@gmail.com Cc: misc@openbsd.org Subject: Re: Dennis Ritchie On Thu, Oct 13, 2011 at 12:14 PM, David Coppa dco...@gmail.com wrote: Today is a sad sad day :( Rest in Peace. Without you, we would never be here. Cheers, David Actually he died already the night between 8-9 oct. Rest in Peace Dennis!
CVS
Why does it say on http://www.openbsd.org/anoncvs.html a.. NOTE: If you are updating a source tree that you initially fetched from a different server, or from a CD, you must add the -d anon...@anoncvs.ca.openbsd.org:/cvs options to cvs. # cd /usr/src # cvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd Why But this is not mentioned on http://www.openbsd.org/faq/faq5.html#BldGetSrc in the section on Pre-loading the tree ?
Re: 64bit (or better) memory reads in i386
Thankyou for the prompt reply. Excuse me please, I made a mistake. I meant 64bit Intel hardware. -Original Message- From: Matthew Dempsky Sent: Sunday, June 12, 2011 3:25 PM To: Giridhari Cc: misc@openbsd.org Subject: Re: 64bit (or better) memory reads in i386 On Sat, Jun 11, 2011 at 10:55 PM, Giridhari giridh...@live.com.au wrote: Is there much activity in porting OpenBSD to x64 architecture? http://www.openbsd.org/amd64.html
Re: 64bit (or better) memory reads in i386
Further, can you tell me what the cp and cpio commands would be like- will they take advantage of 64 or 128bit memory reads and writes? -Original Message- From: Otto Moerbeek Sent: Sunday, June 12, 2011 3:37 PM To: Giridhari Cc: misc@openbsd.org Subject: Re: 64bit (or better) memory reads in i386 On Sun, Jun 12, 2011 at 03:35:00PM +0930, Giridhari wrote: Thankyou for the prompt reply. Excuse me please, I made a mistake. I meant 64bit Intel hardware. Intel makes loads of processors doing just that. -Original Message- From: Matthew Dempsky Sent: Sunday, June 12, 2011 3:25 PM To: Giridhari Cc: misc@openbsd.org Subject: Re: 64bit (or better) memory reads in i386 On Sat, Jun 11, 2011 at 10:55 PM, Giridhari giridh...@live.com.au wrote: Is there much activity in porting OpenBSD to x64 architecture? http://www.openbsd.org/amd64.html
Re: 64bit (or better) memory reads in i386
Your criticism is welcome- it gives me perspective of what I am looking at, and how to tackle this. You've told me to think and what to think about. I am not trying to get out of work I will have to do anyway, I just wasn't sure where to look at this from, and you've given me exactly that. I do not consider you my free slaves! Seriously, I have a very high regard for OpenBSD, and it's developers and supporters. Basically I have concluded I may have to write a custom tool that performs bulk memcopys or similar that is ideally Assembly optimised. Thankyou for your prompt attention. It is most appreciated. Giridhari
64bit (or better) memory reads in i386
Hare Krsna I am developing an OpenBSD build for which will be critically sensitive to memory copy speed. Can someone fill me in on the status of memory copy in OpenBSD on i386? Is it possible to avail oneself of SSE or similar? Is memory copy on i386 only 32 bit? Is there much activity in porting OpenBSD to x64 architecture? Excuse me if this has been thrashed out already. Giridhari
Fw: pico and/or nano in the releases and snapshots
Hare Krsna. From: Giridhari Sent: Thursday, February 04, 2010 7:37 AM To: dera...@cvs.openbsd.org ; dera...@openbsd.org Subject: Fw: pico and/or nano in the releases and snapshots ATTENTION Last night I saved a rat from certain death at the hands of a cat whose ovaries had been cut out. This is the cutting edge of bhakti in the interests of OpenBSD. You have been notified. Note: The below message has been slightly adjusted to that which was sent to dera...@theos.org. From: Giridhari Sent: Thursday, February 04, 2010 7:28 AM To: dera...@theos.com Subject: pico and/or nano in the releases and snapshots Hare Krsna Mr. DeRaadt. I am trying to write a new security implementation for OpenBSD, but find vi to be clumsy and hampering. I was very comfortable with pico, and nano. I am running a new system with multiprocessor kernel, and currently have no support for the ZTE MF626 modem I connect via cellular network with. I have tried installing the package of pico but it failed, so I installed it's dependencies, but pico still would not install because it had partially installed, would not pkg_delete (not even when forced), and I could not find a way to clean this up. I would really appreciate if pico or nano, which are simple and elegant, perhaps not with the frills vi uses apparently seem to appreciate, but simple and natural nonetheless, we part of the distribution. I fly with those. PLEASE INCLUDE PICO OR NANO OR BOTH IN A NEW SNAPSHOT, and from now-on, and please overlook the apparent justifications for vi-only exclusivity, and help please. FOR BHAKTA GIRIDHARI. Krsna is your friend. PLEASE!!! I know its is a non-standard request, but honestly, vi is so clumsy, and I have LOTS of coding to do, including writing support for umodem for the MF626, and I would like to write it as a learning exercise in assembly. The new security mechanism is brute force resilient, and it is for particularly nasty weather. Pull a Torvaldsesque dictatorship because-I-said-so if you have to. Hare Bol.
