subject:"portsnap"

Robert Bonomi bonomi at mail.r-bonomi.com writes:

 ... 
   You gave portsnap two commands - one succeeded and the other 
   failed.
   
Nope. I gave ONE command: 'portsnap fetch update'.
  
   FALSE TO FACT.
 
  No way. UNIX command (on a command line, also called CLI), is anything 
  between prompt
 
 *NOBODY* said Unix command.  _You_ falsely imputed that meaning to
 the respondants use of the word in a context with a different applicable
 meaning.
 
 'command' has many meanings -- *especially* in the Unix environment.
 
 [drivelectomy]
 
 You persist in repeating your error.
 ...

Well, yes - CLI applies to many environments (not only OSs), with the same
basic format.

http://en.wikipedia.org/wiki/Command-line_interface
...
The general pattern of an OS command line interface is:
prompt command param1 param2 param3 ... paramN

A simple CLI will display a prompt, accept a command line typed by the user
terminated by the Enter key, then execute the specified command and provide
textual display of results or error messages. Advanced CLIs will validate,
interpret and parameter-expand the command line before executing the specified
command, and optionally capture or redirect its output.
...
Command prompt
...
Arguments
...
Command-line option
...

Examples:
- OSs (e.g. UNIX)
  $ portsnap fetch update
- database and/or languages environments (e.g. SQL)
  sql  select fields from table
- applications (e.g. reservation system)
   pax dl123/12augdis
  which means:
  display a list of passengers
  for flight DL123, departing on 12 Aug, out of DIS (Disney Land)

So, we are discussing here things that are obvious.
People who write technical or user manuals should have a clue of what they are
writing and talking about (e.g. what is a command, also called an entry).
Otherwise they screw up the users and it's a software error sysadmins.
jb


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-20 Thread Steve O'Hara-Smith

On Tue, 20 Nov 2012 09:15:16 + (UTC)
jb jb.1234a...@gmail.com wrote:

 Robert Bonomi bonomi at mail.r-bonomi.com writes:
 
  You persist in repeating your error.
  ...
 
 Well, yes - CLI applies to many environments (not only OSs), with the same
 basic format.

Why don't the pair of you try and understand each other instead of
arguing over the meanings of words as though it was a matter of life and
death. As it happens you are *both* right about the usage of the word
command. You *both* fail to appreciate that like *every* other word in the
English language it has a context dependant meaning.

Stop masturbating over a dictionary and work on your problem or
take it elsewhere - please.

-- 
Steve O'Hara-Smith at...@sohara.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

Steve O'Hara-Smith ateve at sohara.org writes:

 ...
 
Educate yourselves, please. It's scary when one confuses command arguments
with a command because some nitwit described/called it that way.
jb


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-20 Thread Robert Bonomi

 From owner-freebsd-questi...@freebsd.org  Tue Nov 20 03:17:25 2012
 To: freebsd-questions@freebsd.org
 From: jb jb.1234a...@gmail.com
 Subject: Re: portsnap
 Date: Tue, 20 Nov 2012 09:15:16 + (UTC)

 Robert Bonomi bonomi at mail.r-bonomi.com writes:

  ...
You gave portsnap two commands - one succeeded and the 
other failed.

 Nope. I gave ONE command: 'portsnap fetch update'.

FALSE TO FACT.

   No way. UNIX command (on a command line, also called CLI), is 
   anything between prompt

  *NOBODY* said Unix command.  _You_ falsely imputed that meaning to 
  the respondants use of the word in a context with a different 
  applicable meaning.

  'command' has many meanings -- *especially* in the Unix environment.

  [drivelectomy]

  You persist in repeating your error.
  ...

 Well, yes - CLI applies to many environments (not only OSs), with the 
 same basic format.

 http://en.wikipedia.org/wiki/Command-line_interface
 ...
 The general pattern of an OS command line interface is: prompt command 
 param1 param2 param3 ... paramN

No argument -- for _that_ meaning of the word.  That, however, is not
the only valid usage or interpretation of it.

The truth that you refuse to acknowledge is that in *many* cases, one or
more of the 'params' on the command line are commands TO THE APPlICATION
BEING INVOKED.
 A simple CLI will display a prompt, accept a command line typed by the 
  [drivelectomy]
 So, we are discussing here things that are obvious. People who write 
 technical or user manuals should have a clue of what they are writing and 
 talking about (e.g. what is a command, also called an entry). 
 Otherwise they screw up the users and it's a software error sysadmins. 

the authors of the portsnap docs (and the _numerous_ other applications
that describe the use of certain keywords used as input to that appication
ARE correct -- despite your boneheaded denial of that fact.

A command specifies, to the application to which it is directed, _what_
(or _which_, if you prefer) operation/activity/function is to be performed.
In grammar terms it is a =verb=.

A 'parameter'/'option'/'switch'/etc. instructs the application to which it 
is directed to , _how_ to perform the particular action.  It _modifies_ the
action to be performed.  In grammar terms it is an =adverb=.

This distinction has been known to, understood, and employed by those who
write/read/use technical instructions for well over THREE HUNDRED years.
(early multi-function machinery, such as a crane, could only perform one
action at a time -- e.g. traverse, adjust boom, lift; you moved one set
of controls to command the machine _which_ action to perform, and then
another set of controls to ccntrol how it is done.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

Robert Bonomi bonomi at mail.r-bonomi.com writes:

 ... 
  http://en.wikipedia.org/wiki/Command-line_interface
  ...
  The general pattern of an OS command line interface is: prompt command 
  param1 param2 param3 ... paramN
 
 No argument -- for _that_ meaning of the word.  That, however, is not
 the only valid usage or interpretation of it.
 
 The truth that you refuse to acknowledge is that in *many* cases, one or
 more of the 'params' on the command line are commands TO THE APPlICATION
 BEING INVOKED.
  A simple CLI will display a prompt, accept a command line typed by the 
   [drivelectomy]
  So, we are discussing here things that are obvious. People who write 
  technical or user manuals should have a clue of what they are writing and 
  talking about (e.g. what is a command, also called an entry). 
  Otherwise they screw up the users and it's a software error sysadmins. 
 
 the authors of the portsnap docs (and the _numerous_ other applications
 that describe the use of certain keywords used as input to that appication
 ARE correct -- despite your boneheaded denial of that fact.
 
 A command specifies, to the application to which it is directed, _what_
 (or _which_, if you prefer) operation/activity/function is to be performed.
 In grammar terms it is a =verb=.
 
 A 'parameter'/'option'/'switch'/etc. instructs the application to which it 
 is directed to , _how_ to perform the particular action.  It _modifies_ the
 action to be performed.  In grammar terms it is an =adverb=.
 
 This distinction has been known to, understood, and employed by those who
 write/read/use technical instructions for well over THREE HUNDRED years.
 (early multi-function machinery, such as a crane, could only perform one
 action at a time -- e.g. traverse, adjust boom, lift; you moved one set
 of controls to command the machine _which_ action to perform, and then
 another set of controls to ccntrol how it is done.

... also responding to kpneal at pobox.com ...

With regard to definition of a command as we practice and argue about here:

In general (see bash(1), SHELL GRAMMAR, Simple Commands), a command is 
an executable preceded by optional vars and followed by optional parameters.

Look at PORTSNAP(8)'s synopsis again.
The command is 'portsnap', anything else are parameters to it.

If you call a parameter a command here, you imply that it has attributes of
a command, which clearly does not, as referenced by me above.

So, basically, it is an indicator, verbosely (but not required to be so if it
were also verbosely defined in man page) describing an action parameter, e.g.
extract, telling the actual 'portsnap' command what to do (yes - what to do,
and not how to do it).

jb


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-20 Thread Steve O'Hara-Smith

On Tue, 20 Nov 2012 10:46:55 + (UTC)
jb jb.1234a...@gmail.com wrote:


 Educate yourselves, please. It's scary when one confuses command arguments
 with a command because some nitwit described/called it that way.
 jb

Well with nearly 30 years in unix software development I do know a
thing or two about it. However that is not relevant, the sad thing is that
you have destroyed any chance of getting whatever help you wanted by
deciding to argue about what you think words should mean instead of
understanding how they are being used.

-- 
Steve O'Hara-Smith at...@sohara.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-20 Thread Robert Bonomi

 From owner-freebsd-questi...@freebsd.org  Tue Nov 20 11:14:25 2012
 To: freebsd-questions@freebsd.org
 From: jb jb.1234a...@gmail.com
 Subject: Re: portsnap
 Date: Tue, 20 Nov 2012 17:12:46 + (UTC)

 Robert Bonomi bonomi at mail.r-bonomi.com writes:

  ...
   http://en.wikipedia.org/wiki/Command-line_interface
   ...
   The general pattern of an OS command line interface is: prompt 
   command param1 param2 param3 ... paramN

   No argument -- for _that_ meaning of the word.  That, however, is not 
   the only valid usage or interpretation of it.

  The truth that you refuse to acknowledge is that in *many* cases, one 
  or more of the 'params' on the command line are commands TO THE 
  APPlICATION BEING INVOKED.

   A simple CLI will display a prompt, accept a command line typed by 
   the
[drivelectomy]
So, we are discussing here things that are obvious. People who write 
technical or user manuals should have a clue of what they are 
writing and talking about (e.g. what is a command, also called an 
entry). Otherwise they screw up the users and it's a software 
error sysadmins.

  the authors of the portsnap docs (and the _numerous_ other applications 
  that describe the use of certain keywords used as input to that 
  appication ARE correct -- despite your boneheaded denial of that fact.

  A command specifies, to the application to which it is directed, 
  _what_ (or _which_, if you prefer) operation/activity/function is to be 
  performed. In grammar terms it is a =verb=.

  A 'parameter'/'option'/'switch'/etc. instructs the application to which 
  it is directed to , _how_ to perform the particular action.  It 
  _modifies_ the action to be performed.  In grammar terms it is an 
  =adverb=.

  This distinction has been known to, understood, and employed by those 
  who write/read/use technical instructions for well over THREE HUNDRED 
  years. (early multi-function machinery, such as a crane, could only 
  perform one action at a time -- e.g. traverse, adjust boom, lift; you 
  moved one set of controls to command the machine _which_ action to 
  perform, and then another set of controls to ccntrol how it is done.

 ... also responding to kpneal at pobox.com ...

 With regard to definition of a command as we practice and argue about 
 here:

 In general (see bash(1), SHELL GRAMMAR, Simple Commands), a command is an 
 executable preceded by optional vars and followed by optional parameters.

Repeating:

  No argument -- for _that_ meaning of the word.  That, however, is not 
  the only valid usage or interpretation of it.

  The truth that you refuse to acknowledge is that in *many* cases, one 
  or more of the 'params' on the command line are commands TO THE 
  APPlICATION BEING INVOKED.

 Look at PORTSNAP(8)'s synopsis again. The command is 'portsnap', anything 
 else are parameters to it.

According to the manpage some of those parameters ARE described as commands.

A form of usage/description employed by the first *professional* documentation
specialists at Bell Labs (also Dartmouth, Xerox, and others) more than 40
years ago (yes, 'before Unix') and still in use by documentation professionals
_today_.

 If you call a parameter a command here, you imply that it has attributes 
 of a command, which clearly does not, as referenced by me above.

You lie.  A command does not have to have the attributes of a command-line
invocation.

 So, basically, it is an indicator, verbosely (but not required to be so 
 if it were also verbosely defined in man page) describing an action 
 parameter, e.g. extract, telling the actual 'portsnap' command what to do 
 (yes - what to do, and not how to do it).

It has been tradition in the Unix community (and elsewhere) to refer to
what you call 'action parameters' as commands -- especially in formal
system documentation -- for well over THREE DECADES.

Your insistance that 'command' can ONLY refer to a command-line invocation
is contrary to 'plain English', 30+ years of Unix history/tradition, and
another 25+ years of computing history before that.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

Robert Bonomi bonomi at mail.r-bonomi.com writes:

 ... 
   the authors of the portsnap docs (and the _numerous_ other applications 
   that describe the use of certain keywords used as input to that 
   appication ARE correct -- despite your boneheaded denial of that fact.

Yes, it is a keyword, a keyword parameter that tells CLI command what to do
(yes, a keyword that may be taken verbatim or translated into an internal
command parameter(s), a keyword that represents an action).
But, it is not a command, or parameter of type command.

  With regard to definition of a command as we practice and argue about 
  here:
 
  In general (see bash(1), SHELL GRAMMAR, Simple Commands), a command is an 
  executable preceded by optional vars and followed by optional parameters.

 You lie.  A command does not have to have the attributes of a command-line
 invocation.

Well, a second nature ... But, it is an honor :-)

To drive the point:
let's assume that it is a valid syntax to pass a parameter like this:
ls -al
or much better, command=command, like this:
command=ls -al
then it would be clear that a command (parameter) is passed to CLI command.
This kind of command parameter passing fulfilles the definition of a command
as referenced.

If you are familiar with C function system(), you will have easier time to
understand:
http://www.cplusplus.com/reference/clibrary/cstdlib/system/
The prototype is:
int system ( const char * command );
The command ls -al (yes, it is a command as referenced) is a parameter to
system() function:
system(ls -al);
It just says, execute that command ls -al in the existing execution
environment.

The reason I go so by the book about it is that words have meaning and
definitions :-)
jb


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

portsnap

Hi,
have i caught portsnap with its pants down ?

# rm -rf /usr/ports
# portsnap fetch update
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
Fetching snapshot metadata... done.
Updating from Sun Nov 11 15:54:03 CET 2012 to Mon Nov 19 15:34:57 CET 2012.
Fetching 4 metadata patches... done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 24085 patches.102030405060708090...
...
0240602407024080.. done.
Applying patches... done.
Fetching 18 new ports or files... done.
/usr/ports was not created by portsnap.
You must run 'portsnap extract' before running 'portsnap update'.
#
# ls /usr/ports
ls: /usr/ports: No such file or directory
#

# ls -al /var/db/portsnap/
total 6144
drwxr-xr-x   3 root  wheel  512 Nov 19 16:04 .
drwxr-xr-x  11 root  wheel  512 Nov  4 11:07 ..
-rw-r--r--   1 root  wheel  2063752 Nov 19 15:51 INDEX
drwxr-xr-x   3 root  wheel  4113920 Nov 19 16:04 files
-rw-r--r--   1 root  wheel  451 Oct 16 22:50 pub.ssl
-rw-r--r--   1 root  wheel  284 Nov 19 15:51 serverlist
-rw-r--r--   1 root  wheel  284 Nov 19 15:51 serverlist_full
-rw-r--r--   1 root  wheel   48 Nov 19 15:51 serverlist_tried
-rw-r--r--   1 root  wheel  527 Nov 19 15:51 tINDEX
-rw-r--r--   1 root  wheel   85 Nov 19 15:51 tag

So, why did it do so much work (ca. 5 min, 24085 patches), even claiming to
have applied patches, before telling me the env was not properly set up ?
jb


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-19 Thread RW

On Mon, 19 Nov 2012 15:21:19 + (UTC)
jb wrote:

 Hi,
 have i caught portsnap with its pants down ?
 
 # rm -rf /usr/ports
 # portsnap fetch update
 Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
 Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
 Fetching snapshot metadata... done.
 Updating from Sun Nov 11 15:54:03 CET 2012 to Mon Nov 19 15:34:57 CET
 2012. Fetching 4 metadata patches... done.
 Applying metadata patches... done.
 Fetching 0 metadata files... done.
 Fetching 24085
 patches.102030405060708090... ...
 0240602407024080.. done.
 Applying patches... done.
 Fetching 18 new ports or files... done.
 /usr/ports was not created by portsnap.
 You must run 'portsnap extract' before running 'portsnap update'.
 #
 # ls /usr/ports
 ls: /usr/ports: No such file or directory
 #
 
 ...
 So, why did it do so much work (ca. 5 min, 24085 patches), even
 claiming to have applied patches, before telling me the env was not
 properly set up ? jb

You gave portsnap two commands - one succeeded and the other failed.

fetch downloads and applies patches to the compressed 
snapshot. update uses the compressed snapshot to update a
pre-existing ports tree created by an extract 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

RW rwmaillists at googlemail.com writes:

 ... 
  ...
  So, why did it do so much work (ca. 5 min, 24085 patches), even
  claiming to have applied patches, before telling me the env was not
  properly set up ? jb
 
 You gave portsnap two commands - one succeeded and the other failed.
 
 fetch downloads and applies patches to the compressed 
 snapshot. update uses the compressed snapshot to update a
 pre-existing ports tree created by an extract 
 ...

OK.
But this looks like a flaky entry validation - it should be rejected up front
as invalid entry, even if it applied to the second part - update.
Because the effect of processing the entire entry fetch plus update is lost
anyway.
jb




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-19 Thread RW

On Mon, 19 Nov 2012 16:10:48 + (UTC)
jb wrote:


  You gave portsnap two commands - one succeeded and the other failed.
  
  fetch downloads and applies patches to the compressed 
  snapshot. update uses the compressed snapshot to update a
  pre-existing ports tree created by an extract 
  ...
 
 OK.
 But this looks like a flaky entry validation - it should be rejected
 up front as invalid entry, even if it applied to the second part -
 update. Because the effect of processing the entire entry fetch
 plus update is lost anyway.

Not isn't, you've brought the snapshot up to date.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

RW rwmaillists at googlemail.com writes:

 
 On Mon, 19 Nov 2012 16:10:48 + (UTC)
 jb wrote:
 
   You gave portsnap two commands - one succeeded and the other failed.

Nope. I gave ONE command: 'portsnap fetch update'. 

  But this looks like a flaky entry validation - it should be rejected
  up front as invalid entry, even if it applied to the second part -
  update. Because the effect of processing the entire entry fetch
  plus update is lost anyway.
 
 Not isn't, you've brought the snapshot up to date.

Well, yes. But as I already explained, there was ONE command.

If I wanted to be satisfied with two command outcomes, even if logically
linked by sequential execution, then I would do:
# portsnap fetch; portsnap update

There is a subtle, but important difference.

In general, if I wanted to check for command completion code, which is quite
common in UNIX CLI or scripting env, it would make a lot of difference if
a command failed half way in both cases:
'portsnap fetch update; check-completion-code'
and
'portsnap fetch; check-completion-code; portsnap update; check-completion-code'

jb


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-19 Thread Robert Bonomi

 From owner-freebsd-questi...@freebsd.org  Mon Nov 19 14:15:23 2012
 To: freebsd-questions@freebsd.org
 From: jb jb.1234a...@gmail.com
 Subject: Re: portsnap
 Date: Mon, 19 Nov 2012 20:13:45 + (UTC)

 RW rwmaillists at googlemail.com writes:

  On Mon, 19 Nov 2012 16:10:48 + (UTC) jb wrote:

You gave portsnap two commands - one succeeded and the other 
failed.

 Nope. I gave ONE command: 'portsnap fetch update'.

FALSE TO FACT.

You invoked one executable, 'portsnap',
giving IT two commands, 'fetch' and 'update' as parameters.

Which is *EXACTlY* the same as if you had invoked that
executable twice, giving it one command (in the order above)
on each invocation.

The 'fetch' command succeeded.
The 'update' command failed.

   But this looks like a flaky entry validation - it should be rejected 
   up front as invalid entry, even if it applied to the second part - 
   update. Because the effect of processing the entire entry fetch 
   plus update is lost anyway.

  Not isn't, you've brought the snapshot up to date.

 Well, yes. But as I already explained, there was ONE command.

You misunderstood the terminology -- you gave *TWO* commmands _to_the_
_portsnap_program_.

when portsnap is given multiple commands as invocation arguments,
it processes them sequentially, retuning an 'exit status' for the
first command that _fails, or 'success' if none of the commands 
failed.

 If I wanted to be satisfied with two command outcomes, even if logically 
 linked by sequential execution, then I would do:
 # portsnap fetch; portsnap update

 There is a subtle, but important difference.

Only in your expectations.  grin

 In general, if I wanted to check for command completion code, which is 
 quite common in UNIX CLI or scripting env, it would make a lot of 
 difference if a command failed half way in both cases:
 'portsnap fetch update; check-completion-code'
 and 'portsnap fetch; check-completion-code; portsnap update; 
 check-completion-code'

'portsnap fetch update' is the EXACT equivalent of:
  'portsnap fetch  portsnap update; `check-completion-code'`

Your: 'portsnap fetch; check-completion-code; portsnap update;
  check-completion-code'
is bad/incorrect scripting since it _unconditionally_ executes 
'portsnap update', which you do NOT want to do if/when 'fetch' 
fails.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

Robert Bonomi bonomi at mail.r-bonomi.com writes:

  From owner-freebsd-questions at freebsd.org  Mon Nov 19 14:15:23 2012
  To: freebsd-questions at freebsd.org
  From: jb jb.1234abcd at gmail.com
  Subject: Re: portsnap
  Date: Mon, 19 Nov 2012 20:13:45 + (UTC)

  RW rwmaillists at googlemail.com writes:

   On Mon, 19 Nov 2012 16:10:48 + (UTC) jb wrote:

 You gave portsnap two commands - one succeeded and the other 
 failed.

  Nope. I gave ONE command: 'portsnap fetch update'.

 FALSE TO FACT.

No way.
UNIX command (on a command line, also called CLI), is anything between prompt
(e.g. $) and ENTER, that is in general:
$ command option option
and this is how shell interprets it.
There are simple commands as above, and command constructs as pipeline and 
lists, e.g.
$ command options | command options ; command1; command2
but that does not change the meaning of how they are interpreted as commands.

You got confused by portsnap(8) vocabulary, which is misleading:
SYNOPSIS
 portsnap [-I] [-d workdir] [-f conffile] [-k KEY] [-l descfile]
  [-p portsdir] [-s server] command ... [path]
...
COMMANDS
 The command can be any one of the following:

 fetchFetch a compressed snapshot of the ports tree, or update the
...

The word command in SYNOPSIS is very unfortunate, outright wrong because
misleading - it represents an option or a parameter to a command portsnap.
This is how any command line parser/editor processes the entire entry.
No magic here.

This should explain your confusion in the rest of your post.

 ...

  In general, if I wanted to check for command completion code, which is 
  quite common in UNIX CLI or scripting env, it would make a lot of 
  difference if a command failed half way in both cases:
  'portsnap fetch update; check-completion-code'
  and 'portsnap fetch; check-completion-code; portsnap update; 
  check-completion-code'

 'portsnap fetch update' is the EXACT equivalent of:
   'portsnap fetch  portsnap update; `check-completion-code'`

No, it is not.

Your CLI command line above is an example of a list (see bash(1)): 
...
  Lists
   A list is a sequence of one or more pipelines separated by one  of  the
   operators ;, , , or ||, and optionally terminated by one of ;, , or
   newline.
...

In other words, it is a CLI command that is a composition of INDEPENDENT
commands, here logically linked with '.

It is not the same as your list - the difference is, once again, that when I
enter:
$ portsnap fetch update
this represents a CLI command, just one command with two options or params,
as understood in UNIX and as explained at the very beginning of this post,
regardless of how it is going to be executed internally (with subtasks fetch
and update playing only internal and logical role in the context of that
command's execution). It follows, that the completion code is of that one CLI
command, and not a logical  result of multiple commands in a list.

jb

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-19 Thread Robert Bonomi

 From: jb jb.1234a...@gmail.com
 Subject: Re: portsnap
 Date: Mon, 19 Nov 2012 22:05:41 + (UTC)

 Robert Bonomi bonomi at mail.r-bonomi.com writes:

   From owner-freebsd-questions at freebsd.org  Mon Nov 19 14:15:23 
   2012 To: freebsd-questions at freebsd.org From: jb jb.1234abcd 
   at gmail.com Subject: Re: portsnap Date: Mon, 19 Nov 2012 20:13:45 
   + (UTC)

   RW rwmaillists at googlemail.com writes:

On Mon, 19 Nov 2012 16:10:48 + (UTC) jb wrote:

  You gave portsnap two commands - one succeeded and the other 
  failed.

   Nope. I gave ONE command: 'portsnap fetch update'.

  FALSE TO FACT.

 No way. UNIX command (on a command line, also called CLI), is anything 
 between prompt

*NOBODY* said Unix command.  _You_ falsely imputed that meaning to
the respondants use of the word in a context with a different applicable
meaning.

'command' has many meanings -- *especially* in the Unix environment.

[drivelectomy]

You persist in repeating your error.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-14 Thread ajtiM

On Wednesday 14 November 2012 00:37:47 Elias Chrysocheris wrote:
 Yeap. Same here:
 
 pluto# portsnap fetch update
 Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
 Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
 Latest snapshot on server matches what we already have.
 No updates needed.
 Ports tree is already up to date.
 
 
 How can it be possible? 3 years now that I use FreeBSD there was not even a
 single day that we didn't have updates in the ports tree. How can it be
 possible for two consecutive days to have No updates needed.?
 
 Something is wrong...
 
 Regards
 Elias

We have updates but I red somewhere about problem with server. Should be nice 
to the users if someone sent email to mailing list about a problem.


Mitja

http://www.redbubble.com/people/lumiwa
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-13 Thread Jason Garrett

On Mon, Nov 12, 2012 at 6:13 PM, ajtiM lum...@gmail.com wrote:

 On Monday 12 November 2012 17:46:44 Aldis Berjoza wrote:
  13.11.2012, 01:27, ajtiM lum...@gmail.com:
   Hi!
  
   Is it something wrong with portsnap server or is something wrong with
 my
   system. When I run portsnap...:
   portsnap fetch update
   Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
   Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
   Latest snapshot on server matches what we already have.
   No updates needed.
   Ports tree is already up to date.
  
   but on http://www.freshports.org/ are many new ports (I like update
   Sage).
  
   Thanks in advance.
  
   Mitja
 
  It takes some time for mirrors to catch up.

 But is it about 12 hours okay (maybe more)?
 Thanks.

 Mitja
 


I have the same problem going on 2 days now...


 http://www.redbubble.com/people/lumiwa
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to 
 freebsd-questions-unsubscr...@freebsd.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-13 Thread Christer Solskogen

On Tue, Nov 13, 2012 at 11:19 PM, Jason Garrett kinged...@gmail.com wrote:
 On Mon, Nov 12, 2012 at 6:13 PM, ajtiM lum...@gmail.com wrote:

 On Monday 12 November 2012 17:46:44 Aldis Berjoza wrote:
  13.11.2012, 01:27, ajtiM lum...@gmail.com:
   Hi!
  
   Is it something wrong with portsnap server or is something wrong with
 my
   system. When I run portsnap...:
   portsnap fetch update
   Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
   Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
   Latest snapshot on server matches what we already have.
   No updates needed.
   Ports tree is already up to date.
  
   but on http://www.freshports.org/ are many new ports (I like update
   Sage).
  
   Thanks in advance.
  
   Mitja
 
  It takes some time for mirrors to catch up.

 But is it about 12 hours okay (maybe more)?
 Thanks.

 Mitja
 


 I have the same problem going on 2 days now...


Same. This is in Europe.

-- 
chs,
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-13 Thread Elias Chrysocheris

Yeap. Same here:

pluto# portsnap fetch update
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
Latest snapshot on server matches what we already have.
No updates needed.
Ports tree is already up to date.


How can it be possible? 3 years now that I use FreeBSD there was not even a 
single day that we didn't have updates in the ports tree. How can it be 
possible for two consecutive days to have No updates needed.?

Something is wrong...

Regards
Elias
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

portsnap

2012-11-12 Thread ajtiM

Hi!

Is it something wrong with portsnap server or is something wrong with my 
system. When I run portsnap...:
portsnap fetch update
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
Latest snapshot on server matches what we already have.
No updates needed.
Ports tree is already up to date.

but on http://www.freshports.org/ are many new ports (I like update Sage).

Thanks in advance.

Mitja

http://www.redbubble.com/people/lumiwa
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap

2012-11-12 Thread ajtiM

On Monday 12 November 2012 17:46:44 Aldis Berjoza wrote:
 13.11.2012, 01:27, ajtiM lum...@gmail.com:
  Hi!
  
  Is it something wrong with portsnap server or is something wrong with my
  system. When I run portsnap...:
  portsnap fetch update
  Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
  Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
  Latest snapshot on server matches what we already have.
  No updates needed.
  Ports tree is already up to date.
  
  but on http://www.freshports.org/ are many new ports (I like update
  Sage).
  
  Thanks in advance.
  
  Mitja
 
 It takes some time for mirrors to catch up.

But is it about 12 hours okay (maybe more)?
Thanks.

Mitja

http://www.redbubble.com/people/lumiwa
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: svn and/or portsnap

2012-09-12 Thread Thomas Mueller


Regarding my question,

How do you get the ports tree or svn in that case if not using portsnap?

Helmut Schneider had two suggestions:

 You install ports from CD/DVD. Or use pkg_add -r subversion. :)

 ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/

I guess I could use the latter and then build subversion among other ports, 
then subsequently switch to svn.

This would also work, I would guess, if ports tree is installed by bsdinstall 
or sysinstall.

Question arises whether the ports tree as downloaded in tarball by ftp would be 
compatible/in sync with portsnap or svn.

If in any doubt, either delete /usr/ports/* or move to /usr/ports-by-ftp and 
then restart fresh with svn.

I noticed the FreeBSD Handbook ports section was not up-to-date on the use of 
subversion with the ports tree.

Maybe with subversion now being elevated in importance for updating system 
source code and ports tree, it could become part of the base system.

Tom
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: svn and/or portsnap

2012-09-11 Thread Thomas Mueller

On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote:
 Hi,

 I'm running a custom kernel so I (guess I) need svn in future to fetch
 sources instead of cvsup. Should I still use portsnap then for ports or
 also fetch them via svn?

Polytropon responded:

 Ports and system sources are managed independently. You can
 use whatever tool you want. Note that portsnap _might_ not
 deliver the most current ports tree for a given point in
 time. For short time deltas, CVS has often proven to be
 the better tool, but of course portsnap has significant
 advantages (e. g. faster for longer pauses between ports
 tree updates, better integration with make update target).
 Depending on your updating habits, choose the tool that
 works best for you.

One question comes up that I didn't think of immediately.

How do you use svn on a fresh install of FreeBSD, no ports yet?

svn/subversion is not part of the base system.

How do you get the ports tree or svn in that case if not using portsnap?

Tom
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: svn and/or portsnap

2012-09-11 Thread Christer Solskogen

On Tue, Sep 11, 2012 at 10:15 AM, Thomas Mueller
muelle...@insightbb.com wrote:
 How do you get the ports tree or svn in that case if not using portsnap?

You use pkg_add (or the youngest newcomer pkg)


-- 
chs,
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: svn and/or portsnap

2012-09-11 Thread Helmut Schneider

Thomas Mueller wrote:

 On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote:
  Hi,
 
  I'm running a custom kernel so I (guess I) need svn in future to
  fetch sources instead of cvsup. Should I still use portsnap then
  for ports or also fetch them via svn?
 
 Polytropon responded:
 
  Ports and system sources are managed independently. You can
  use whatever tool you want. Note that portsnap might not
  deliver the most current ports tree for a given point in
  time. For short time deltas, CVS has often proven to be
  the better tool, but of course portsnap has significant
  advantages (e. g. faster for longer pauses between ports
  tree updates, better integration with make update target).
  Depending on your updating habits, choose the tool that
  works best for you.
 
 One question comes up that I didn't think of immediately.
 
 How do you use svn on a fresh install of FreeBSD, no ports yet?

You install ports from CD/DVD. Or use pkg_add -r subversion. :)

 svn/subversion is not part of the base system.
 
 How do you get the ports tree or svn in that case if not using
 portsnap?

ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: svn and/or portsnap

2012-09-11 Thread Polytropon

On Tue, 11 Sep 2012 04:15:24 -0400, Thomas Mueller wrote:
 One question comes up that I didn't think of immediately.
 
 How do you use svn on a fresh install of FreeBSD, no ports yet?
 
 svn/subversion is not part of the base system.
 
 How do you get the ports tree or svn in that case if not using portsnap?

As this is an O(1) kind of problem, I'd suggest the easiest
way: Use the package for svn. Install svn via

# pkg_add -r svn

(or however the svn package is called) and then use it to
incorporate the full ports tree (and maybe also bring your
OS sources to the branch you want, patched RELEASE, STABLE
or HEAD).

Afterwards, upgrade svn with the version from the ports tree
which will possibly be newer. Then continue using ports to
install software as usual.

When CVS was not part of the OS, I went the same way by
installing cvsup-without-x11 (or how the package was called)
to be able to update ports and sources via CVS. Today this
is not needed anymore, as CVS (as csup) is part of the OS.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap Generating a Bad file descriptor Error Message

2012-09-10 Thread Pierre-Luc Drouin

On Tue, Sep 4, 2012 at 10:14 AM, Pierre-Luc Drouin pldro...@gmail.comwrote:

 Hi,

 so I have been having problems using portsnap lately. I always get a Bad
 file descriptor message when trying using it on one of my i386 machine:

 Looking up portsnap5.freebsd.org mirrors... none found.
 Fetching snapshot tag from portsnap5.freebsd.org... done.
 Fetching snapshot metadata... done.
 Fetching snapshot generated at Mon Sep  3 20:04:44 EDT 2012:
 86abb3c6f24b24e7fdadda42805f9ae38f487177dcb949  0% of   67 MB0  Bps
 fetch:
 http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz:
 Bad file descriptor
 fetch:
 86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz: Bad
 file descriptor

 I tried fsck -y the /var, /tmp and /usr partitions and everything seems
 fine. What could the problem be?

 Thanks!


Hi,

Anyone has an idea about what could be causing this problem?

Thank you!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap Generating a Bad file descriptor Error Message

2012-09-10 Thread Polytropon

On Mon, 10 Sep 2012 08:56:29 -0400, Pierre-Luc Drouin wrote:
On Tue, Sep 4, 2012 at 10:14 AM, Pierre-Luc Drouin pldro...@gmail.comwrote:

Hi,

so I have been having problems using portsnap lately. I always get a Bad
file descriptor message when trying using it on one of my i386 machine:

Looking up portsnap5.freebsd.org mirrors... none found.
Fetching snapshot tag from portsnap5.freebsd.org... done.
Fetching snapshot metadata... done.
Fetching snapshot generated at Mon Sep 3 20:04:44 EDT 2012:
86abb3c6f24b24e7fdadda42805f9ae38f487177dcb949 0% of 67 MB0 Bps
fetch:
http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz:
Bad file descriptor
fetch:
86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz: Bad
file descriptor

I tried fsck -y the /var, /tmp and /usr partitions and everything seems
fine. What could the problem be?

Thanks!

Hi,

Anyone has an idea about what could be causing this problem?

I'm not familiar enough with portsnap (I use CVS) so I can just
throw some guesses around:

The message Bad file descriptor is issued by fetch and seems
to be for _your_ side of the connection, and I assume it is
regarding the place where the requested file will be fetched
to. I don't exactly know _where_ that is. It could be in
the ports tree or in a temporary location (from where the
results are then written to /usr/ports). The manpage mentions
a default workdir of /var/db/portsnap which is on the /var
partition. You checked that, no errors.

Just check what /var/db/portsnap contains. In worst case,
remove portsnap/ and recreate that directory. I have no
idea what it is supposed to contain, maybe make a copy of
it. You could also try to manually create the file, e. g.
by issuing

# touch
/var/db/portsnap/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz

Look if the file is there. Use

# stat
/var/db/portsnap/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz

to check if everything is okay.

You could also try to manually fetch the file using fetch or
maybe even wget, just to see if it can be downloaded and
written properly, to a different location, e. g.

# cd /tmp
# fetch
http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz

# cd /tmp
# wget
http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz

That should be _no_ problem (with the correct file name of course).

Again, Bad file descriptor is often seen in relation to file
system trouble. I've seen that in the past myself.

--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap Generating a Bad file descriptor Error Message

2012-09-10 Thread Pierre-Luc Drouin

Hi,

Yes, files are written to the /var filesystem. I have tried fetching the
file manually and I have even tried to newfs the partition again and to
copy the files back. I also tried to delete the portsnap directory
completely. None of this fixed the error. Note that I access the web
through a proxy, but I tried untaring the file
86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgzhttp://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgzand
I did not get any error from tar, so I guess the file I got is not
corrupted.

On Mon, Sep 10, 2012 at 9:43 AM, Polytropon free...@edvax.de wrote:

On Mon, 10 Sep 2012 08:56:29 -0400, Pierre-Luc Drouin wrote:
On Tue, Sep 4, 2012 at 10:14 AM, Pierre-Luc Drouin pldro...@gmail.com
wrote:

Hi,

so I have been having problems using portsnap lately. I always get a
Bad
file descriptor message when trying using it on one of my i386
machine:

http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz
:
Bad file descriptor
fetch:
86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz:
Bad
file descriptor

I tried fsck -y the /var, /tmp and /usr partitions and everything seems
fine. What could the problem be?

Thanks!

Hi,

Anyone has an idea about what could be causing this problem?

I'm not familiar enough with portsnap (I use CVS) so I can just
throw some guesses around:

# touch
/var/db/portsnap/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz

Look if the file is there. Use

# stat
/var/db/portsnap/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz

to check if everything is okay.

You could also try to manually fetch the file using fetch or
maybe even wget, just to see if it can be downloaded and
written properly, to a different location, e. g.

# cd /tmp
# fetch
http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz

# cd /tmp
# wget
http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz

That should be _no_ problem (with the correct file name of course).

Again, Bad file descriptor is often seen in relation to file
system trouble. I've seen that in the past myself.

--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

svn and/or portsnap

2012-09-09 Thread Helmut Schneider

Hi,

I'm running a custom kernel so I (guess I) need svn in future to fetch
sources instead of cvsup. Should I still use portsnap then for ports or
also fetch them via svn?

Thanks, Helmut

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: svn and/or portsnap

2012-09-09 Thread Polytropon

On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote:
 Hi,
 
 I'm running a custom kernel so I (guess I) need svn in future to fetch
 sources instead of cvsup. Should I still use portsnap then for ports or
 also fetch them via svn?

Ports and system sources are managed independently. You can
use whatever tool you want. Note that portsnap _might_ not
deliver the most current ports tree for a given point in
time. For short time deltas, CVS has often proven to be
the better tool, but of course portsnap has significant
advantages (e. g. faster for longer pauses between ports
tree updates, better integration with make update target).
Depending on your updating habits, choose the tool that
works best for you.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: svn and/or portsnap

2012-09-09 Thread Helmut Schneider

Polytropon wrote:

 On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote:
  Hi,
  
  I'm running a custom kernel so I (guess I) need svn in future to
  fetch sources instead of cvsup. Should I still use portsnap then
  for ports or also fetch them via svn?
 
 Ports and system sources are managed independently. You can
 use whatever tool you want.

The question should read: If I need to install svn anyway, is there an
advantage of portsnap over svn to fetch ports.

 Note that portsnap might not deliver the most current ports tree
 for a given point in time. For short time deltas, CVS has often
 proven to be the better tool, but of course portsnap has significant
 advantages (e. g. faster for longer pauses between ports
 tree updates, better integration with make update target).
 Depending on your updating habits, choose the tool that
 works best for you.

Currently I'm updating ports and src twice a day so I will keep using
svn for both.

Thanks.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: svn and/or portsnap

2012-09-09 Thread Polytropon

On Sun, 9 Sep 2012 11:26:50 + (UTC), Helmut Schneider wrote:
 Polytropon wrote:
 
  On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote:
   Hi,
   
   I'm running a custom kernel so I (guess I) need svn in future to
   fetch sources instead of cvsup. Should I still use portsnap then
   for ports or also fetch them via svn?
  
  Ports and system sources are managed independently. You can
  use whatever tool you want.
 
 The question should read: If I need to install svn anyway, is there an
 advantage of portsnap over svn to fetch ports.

As I said, it depends. If you don't update regularly (in
short time spans), portsnap might be faster than SVN (to
incorporate all the deltas). If you feel comfortable with
this approach, you can keep using it. I don't see a general
advantage here.



  Note that portsnap might not deliver the most current ports tree
  for a given point in time. For short time deltas, CVS has often
  proven to be the better tool, but of course portsnap has significant
  advantages (e. g. faster for longer pauses between ports
  tree updates, better integration with make update target).
  Depending on your updating habits, choose the tool that
  works best for you.
 
 Currently I'm updating ports and src twice a day so I will keep using
 svn for both.

Good choice, in that case you won't have any advantage using
portsnap as smaller amounts of deltas are no big deal when
using SVN (or traditional CVS).



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: svn and/or portsnap

2012-09-09 Thread C. P. Ghost

On Sun, Sep 9, 2012 at 1:26 PM, Helmut Schneider jumpe...@gmx.de wrote:
 Currently I'm updating ports and src twice a day so I will keep using
 svn for both.

While you certainly can, isn't it a bit excessive to update so frequently?
Remember, it's not just fetching the sources and ports, you must also
compile world _and_ ports if you want to stay current. I highly doubt that
you want to do this twice a day, even on a very fast machine.

And if you don't compile twice a day, it may be better to keep sources
(and ports) with the installed binaries in sync. Just in case you need to
investigate security breaches or buggy programs -- then you'll be glad
to have the _corresponding_ sources available instead of some sources
for binaries you have not installed yet.

 Thanks.

Regards,
-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: svn and/or portsnap

2012-09-09 Thread Helmut Schneider

C. P. Ghost wrote:

 On Sun, Sep 9, 2012 at 1:26 PM, Helmut Schneider jumpe...@gmx.de
 wrote:
  Currently I'm updating ports and src twice a day so I will keep
  using svn for both.
 
 While you certainly can, isn't it a bit excessive to update so
 frequently?  Remember, it's not just fetching the sources and ports,
 you must also compile world and ports if you want to stay current. I
 highly doubt that you want to do this twice a day, even on a very
 fast machine.

I meant I fetch sources for src and ports twice a day. While ports
helps me to track most recent changes src indeed might not require an
update twice a day.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

portsnap Generating a Bad file descriptor Error Message

2012-09-04 Thread Pierre-Luc Drouin

Hi,

so I have been having problems using portsnap lately. I always get a Bad
file descriptor message when trying using it on one of my i386 machine:

Looking up portsnap5.freebsd.org mirrors... none found.
Fetching snapshot tag from portsnap5.freebsd.org... done.
Fetching snapshot metadata... done.
Fetching snapshot generated at Mon Sep  3 20:04:44 EDT 2012:
86abb3c6f24b24e7fdadda42805f9ae38f487177dcb949  0% of   67 MB0  Bps
fetch:
http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz:
Bad file descriptor
fetch:
86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz: Bad
file descriptor

I tried fsck -y the /var, /tmp and /usr partitions and everything seems
fine. What could the problem be?

Thanks!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap Generating a Bad file descriptor Error Message

2012-09-04 Thread Jamie Paul Griffin

[ Pierre-Luc Drouin wrote on Tue  4.Sep'12 at 10:14:18 -0400 ]

 Hi,
 
 so I have been having problems using portsnap lately. I always get a Bad
 file descriptor message when trying using it on one of my i386 machine:
 
 Looking up portsnap5.freebsd.org mirrors... none found.
 Fetching snapshot tag from portsnap5.freebsd.org... done.
 Fetching snapshot metadata... done.
 Fetching snapshot generated at Mon Sep  3 20:04:44 EDT 2012:
 86abb3c6f24b24e7fdadda42805f9ae38f487177dcb949  0% of   67 MB0  Bps
 fetch:
 http://portsnap5.freebsd.org/s/86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz:
 Bad file descriptor
 fetch:
 86abb3c6f24b24e7fdadda42805f9ae38f487177dcb9493f5e0cb4f792490b2f.tgz: Bad
 file descriptor
 
 I tried fsck -y the /var, /tmp and /usr partitions and everything seems
 fine. What could the problem be?
 
I'm not getting that error but I am getting these:

sort: write failed: standard output: Broken pipe
sort: write error

Unrelated i'd imagine but seems portsnap has some issues?

Jamie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Power failure during portsnap fetch update

2012-07-22 Thread Robert Bonomi

 From owner-freebsd-questi...@freebsd.org  Sat Jul 21 09:40:20 2012
 Date: Sat, 21 Jul 2012 16:38:02 +0200
 From: Leslie Jensen les...@eskk.nu
 To: freebsd-questions@freebsd.org
 Subject: Power failure during portsnap fetch update

 My file system /usr/ports/net go damaged

 I've done fsck -F in single user mode but there are warnings about not 
 being able to fix this.

Insufficient Data for a meaningful response.  *sigh*

_Exactly_ WHAT the command line used was, and *WHAT* the exact text of
the error message says is needed before anyone can help.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Power failure during portsnap fetch update



My file system /usr/ports/net go damaged

I've done fsck -F in single user mode but there are warnings about not 
being able to fix this.


The directories below cannot be removed

How do I go about this?

Thanks

/Leslie




total 14
drwxr-xr-x  1 root  wheel  512 21 Jul 16:13 ccxstream/
drwxr-xr-x  1 root  wheel  512 21 Jul 16:28 netselect/
drwxr-xr-x  1 root  wheel  512 21 Jul 16:17 spread/
drwxr-xr-x  1 root  wheel  512 21 Jul 16:20 spread4/
drwxr-xr-x  1 root  wheel  512 21 Jul 16:20 spread4/
drwxr-xr-x  1 root  wheel  512 21 Jul 16:30 vde2/
drwxr-xr-x  1 root  wheel  512 21 Jul 16:30 vde2/

root@bsd01/usr/ports/net:rm -r *
rm: ccxstream: Invalid argument
rm: netselect: Invalid argument
rm: spread: Invalid argument
rm: spread4: Invalid argument
rm: spread4: Invalid argument
rm: vde2: Invalid argument
rm: vde2: Invalid argument

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Power failure during portsnap fetch update

2012-07-21 Thread Wojciech Puchar



I've done fsck -F in single user mode but there are warnings about not being 
able to fix this.


without the messages from fsck i cannot help you.

there are rare cases when mess gets written to inodes that fsck will not 
corrent it and you have to do it yourself. most often - using clri(8).

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Power failure during portsnap fetch update

2012-07-21 Thread Polytropon

On Sat, 21 Jul 2012 16:38:02 +0200, Leslie Jensen wrote:
 
 My file system /usr/ports/net go damaged
 
 I've done fsck -F in single user mode but there are warnings about not 
 being able to fix this.

First of all, you should give fsck a second try. Check the
damaged partition per fsck -y /dev/ad0s1f (which refers
to that partition, e. g. /usr).



 The directories below cannot be removed

That indicates a major file system defect.



 How do I go about this?

There is a nice tool in the base system: clri (clear inode).
Please note that you're going to get your hands dirty
with this approach!

First, determine the inodes of the offending directories.
Use ls -ldi to do this.

Example:

# cd /usr/ports/net
# ls -ldi ccxstream netselect spread vde2
288794 drwxr-xr-x  3 root  wheel  512 2011-08-21 03:14:43 ccxstream/
331753 drwxr-xr-x  3 root  wheel  512 2011-08-21 03:16:10 netselect/
424004 drwxr-xr-x  3 root  wheel  512 2011-08-21 03:17:50 spread/
424104 drwxr-xr-x  2 root  wheel  512 2011-08-21 03:18:04 vde2/

Alternative: You can also use stat to obtain information
about a file (and a directory) and its health.

Example:

# cd /usr/ports/net
# stat ccxstream netselect spread vde2
120 288794 drwxr-xr-x 3 root wheel 1139829 512 Jul 21 16:46:35 2012 Aug 21 
03:14:43 2011 Aug 21 03:14:43 2011 Feb 18 02:04:47 2011 16384 4 0 ccxstream
120 331753 drwxr-xr-x 3 root wheel 1325518 512 Jul 21 16:46:35 2012 Aug 21 
03:16:10 2011 Aug 21 03:16:10 2011 Feb 18 02:04:58 2011 16384 4 0 netselect
120 424004 drwxr-xr-x 3 root wheel 1696620 512 Jul 21 16:46:35 2012 Aug 21 
03:17:50 2011 Aug 21 03:17:50 2011 Feb 18 02:05:15 2011 16384 4 0 spread
120 424104 drwxr-xr-x 2 root wheel 1696720 512 Jul 21 16:46:35 2012 Aug 21 
03:18:04 2011 Aug 21 03:18:04 2011 Feb 18 02:05:18 2011 16384 4 0 vde2

You recognize the inode numbers here. Write down the inode numbers
or store them in a temporary file. You can script this process if
you like. :-)

Then go out of the partition and unmount it. You are safer
if you apply clri to an UNMOUNTED partition.

Then, for example, do this:

# clri /dev/ad0s1f 288794
# clri /dev/ad0s1f 331753
# clri /dev/ad0s1f 424004
# clri /dev/ad0s1f 424104

Note that this directly modifies file system bowels of the
/usr partition! When done, apply fsck again:

# fsck -yf /dev/ad0s1f

Maybe fsck finds some errors in inode construction and will
therefore recover lost data (which we will accept as irrelevant
at this point) into the lost+found/ root directory on that
partition. You can remove its content later on.

If fsck finishes with success, you should be able to mount the
/usr partition again. Of course, some subdirecories in the
ports tree are now missing, but that has been inteneded.

Side note:

You can use the program fsdb to investigate inode information
in detail. See man fsdb and man clri for details.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Power failure during portsnap fetch update




2012-07-21 16:44, Wojciech Puchar skrev:


I've done fsck -F in single user mode but there are warnings about not
being able to fix this.


without the messages from fsck i cannot help you.

there are rare cases when mess gets written to inodes that fsck will not
corrent it and you have to do it yourself. most often - using clri(8).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org



Here are the errors:


root@bsd01~:fsck -F /dev/ad4s3f
** /dev/ad4s3f (NO WRITE)
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
MISSING '.'  I=5021  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:13 2012
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? no

MISSING '.'  I=123745  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:17 2012
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? no

MISSING '.'  I=123796  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:20 2012
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? no

MISSING '.'  I=169253  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:30 2012
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? no

MISSING '.'  I=2571711  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:28 2012
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? no

MISSING '..'  I=2571711  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:28 2012
DIR=/ports/net/netselect

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? no

MISSING '..'  I=5021  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:13 2012
DIR=/ports/net/ccxstream

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? no

MISSING '..'  I=123745  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:17 2012
DIR=/ports/net/spread

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? no

MISSING '..'  I=123796  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:20 2012
DIR=/ports/net/spread4

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? no

MISSING '..'  I=169253  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:30 2012
DIR=/ports/net/vde2

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? no

** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
LINK COUNT DIR I=5021  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:13 2012  COUNT 1 SHOULD BE 2
LINK COUNT INCREASING
UNEXPECTED SOFT UPDATE INCONSISTENCY

ADJUST? no

LINK COUNT DIR I=123745  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:17 2012  COUNT 1 SHOULD BE 2
LINK COUNT INCREASING
UNEXPECTED SOFT UPDATE INCONSISTENCY

ADJUST? no

LINK COUNT DIR I=123796  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:20 2012  COUNT 1 SHOULD BE 2
LINK COUNT INCREASING
UNEXPECTED SOFT UPDATE INCONSISTENCY

ADJUST? no

LINK COUNT DIR I=169253  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:30 2012  COUNT 1 SHOULD BE 2
LINK COUNT INCREASING
UNEXPECTED SOFT UPDATE INCONSISTENCY

ADJUST? no

LINK COUNT DIR I=2124226  OWNER=root MODE=40755
SIZE=27136 MTIME=Jul 21 16:32 2012  COUNT 4 SHOULD BE 5
LINK COUNT INCREASING
UNEXPECTED SOFT UPDATE INCONSISTENCY

ADJUST? no

LINK COUNT DIR I=2571711  OWNER=root MODE=40755
SIZE=512 MTIME=Jul 21 16:28 2012  COUNT 1 SHOULD BE 2
LINK COUNT INCREASING
UNEXPECTED SOFT UPDATE INCONSISTENCY

ADJUST? no

** Phase 5 - Check Cyl groups
263573 files, 3718492 used, 6942235 free (204667 frags, 842196 blocks, 
1.9% fragmentation)


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Power failure during portsnap fetch update

2012-07-21 Thread Wojciech Puchar


how about fsck_ffs -y / in single user mode?

seems like no clri is needed.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Power failure during portsnap fetch update

2012-07-21 Thread Polytropon

On Sat, 21 Jul 2012 16:56:28 +0200, Leslie Jensen wrote:
 Here are the errors:
 
 
 root@bsd01~:fsck -F /dev/ad4s3f
 ** /dev/ad4s3f (NO WRITE)
  

In that case, fsck won't correct any errors. Good for checking,
bad for repairing!

Make sure the partition isn't mounted (e. g. right after entering
SUM after a boot -s system start) and run:

# fsck -yf /dev/ad4s3f

This will tell fsck to perform the check anyway (-f) and answer
YES (-y) to all questions regarding file system modification.
If you feel unhappy with this quite brutal approach, leave
out the -y parameter and answer the questions yourself.

The error messages you did show in the form of

 MISSING '.'  I=5021  OWNER=root MODE=40755
 SIZE=512 MTIME=Jul 21 16:13 2012
 DIR=?
 
 UNEXPECTED SOFT UPDATE INCONSISTENCY
 
 FIX? no

and

 MISSING '..'  I=2571711  OWNER=root MODE=40755
 SIZE=512 MTIME=Jul 21 16:28 2012
 DIR=/ports/net/netselect
 
 UNEXPECTED SOFT UPDATE INCONSISTENCY
 
 FIX? no

as well as

 LINK COUNT DIR I=5021  OWNER=root MODE=40755
 SIZE=512 MTIME=Jul 21 16:13 2012  COUNT 1 SHOULD BE 2
 LINK COUNT INCREASING
 UNEXPECTED SOFT UPDATE INCONSISTENCY
 
 ADJUST? no

show that the inodes of several directories have been damaged.
This perfectly fits your observation of not being able to
remove those directories.

You _need_ to repair the file system in order to proceed. First
let fsck try to do its job. If it fails to do so, attempt to
manually repair the inodes (by removing them altogether).




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Power failure during portsnap fetch update




2012-07-21 16:59, Wojciech Puchar skrev:

how about fsck_ffs -y / in single user mode?

seems like no clri is needed.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org



It fixed the problem :-)

Thank you very much.

/Leslie

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Power failure during portsnap fetch update

2012-07-21 Thread Wojciech Puchar


freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org



It fixed the problem :-)


you may risk putting

fsck_y_enable=YES

in your rc.conf




i put background_fsck=NO in /etc/rc.conf too
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Power failure during portsnap fetch update




2012-07-21 17:33, Wojciech Puchar skrev:

freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org



It fixed the problem :-)


you may risk putting

fsck_y_enable=YES

in your rc.conf




i put background_fsck=NO in /etc/rc.conf too
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org



Thank you for the advise. I'll put it in rc.conf

/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap update won't update original /usr/ports

2012-05-23 Thread RW

On Tue, 22 May 2012 21:30:44 -0400 (EDT)
Thomas Mueller wrote:

 - Original Message -
 From: Gary Aitken free...@dreamchaser.org
 To: freebsd-questions@freebsd.org
 Sent: Tue, 22 May 2012 19:02:30 -0400 (EDT)
 Subject: portsnap update won't update original /usr/ports

 According to the handbook, one can do
portsnap fetch
portsnap update
 and the update will work with a previously created ports tree;
 I presume this includes one created during system install.

It says:

If you are running Portsnap for the first time, extract the snapshot
into /usr/ports: # portsnap extract

If you already have a populated /usr/ports and you are just updating,
run the following command instead...

If you have the tree from the disk then that means you are running
portsnap for the first time, the second sentence refers to a /usr/ports
populated by a portsnap extract.

  My response: 

 Now I wonder if it's feasible to switch between portsnap fetch
 update and csup ports-supfile, or if it's strictly one or the
 other.

You'll probably get away with it most of the time, but it's not safe to
mix them.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

portsnap update won't update original /usr/ports

2012-05-22 Thread Gary Aitken


According to the handbook, one can do
  portsnap fetch
  portsnap update
and the update will work with a previously created ports tree;
I presume this includes one created during system install.

However, when I attempted this, portsnap complained:
  /usr/ports was not created by portsnap.
  You must run 'portsnap extract' before running 'portsnap update'.

Is there a way to use portsnap against this tree, or must I delete the 
existing /usr/ports and do an extract first?


Thanks,

Gary
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap update won't update original /usr/ports

2012-05-22 Thread Shane Ambler


On 23/05/2012 08:32, Gary Aitken wrote:

According to the handbook, one can do portsnap fetch portsnap update
and the update will work with a previously created ports tree; I
presume this includes one created during system install.

However, when I attempted this, portsnap complained: /usr/ports was
not created by portsnap. You must run 'portsnap extract' before
running 'portsnap update'.

Is there a way to use portsnap against this tree, or must I delete
the existing /usr/ports and do an extract first?



'portsnap extract' will write over whatever is in /usr/ports so you
don't have to delete what is there. Any distfiles or packages will
remain intact.

You need to start with 'portsnap extract' so that portsnap gets a
reference point to use for updates - which only adds changes since last
update

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap update won't update original /usr/ports

2012-05-22 Thread Thomas Mueller

- Original Message -
From: Gary Aitken free...@dreamchaser.org
To: freebsd-questions@freebsd.org
Sent: Tue, 22 May 2012 19:02:30 -0400 (EDT)
Subject: portsnap update won't update original /usr/ports

According to the handbook, one can do
   portsnap fetch
   portsnap update
and the update will work with a previously created ports tree;
I presume this includes one created during system install.

However, when I attempted this, portsnap complained:
   /usr/ports was not created by portsnap.
   You must run 'portsnap extract' before running 'portsnap update'.

Is there a way to use portsnap against this tree, or must I delete the 
existing /usr/ports and do an extract first?

Thanks,

Gary

 My response: 

I screwed up this way too, when I downloaded the USB memstick image for FreeBSD 
9.0_BETA1 and later, BETA2, I installed the ports from that, which worked to my 
disadvantage when I later ran portsnap fetch update.

I wound up deleting /usr/ports/* and starting fresh, may not necessarily have 
had to delete the ports tree.  But now it works.

Now I wonder if it's feasible to switch between portsnap fetch update and 
csup ports-supfile, or if it's strictly one or the other.

I am at webmail interface, which strongly favors top-posting over 
bottom-posting; feel more comfortable with vi editor.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

portsnap broken

2011-12-04 Thread Len Conrad

Never had a problem before

Freebsd 8.2

a couple weeks ago, on virgin 8.2, initial run of 

portsnap fetch extract

... ran great, and a couple of updates since then, also.  

but today:

# portsnap fetch
Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found.
Fetching snapshot tag from portsnap1.FreeBSD.org... done.
Fetching snapshot metadata... done.
Updating from Sun Dec  4 15:26:46 CET 2011 to Mon Dec  5 02:05:11 CET 2011.
Fetching 4 metadata patches... done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 27 patches.1020... done.
Applying patches... done.
Fetching 2 new ports or files... done.


# portsnap update
Removing old files and directories... done.
Extracting new files:
/usr/ports/MOVED
/usr/ports/Mk/bsd.sites.mk
/usr/ports/Mk/bsd.wx.mk
/usr/ports/archivers/rpm4/
/usr/ports/astro/google-earth/
/usr/ports/astro/match/
/usr/ports/astro/xearth/
/usr/ports/astro/xtide/
/usr/ports/audio/audacity-devel/
/usr/ports/audio/thunar-media-tags-plugin/
/usr/ports/cad/brlcad/
/usr/ports/chinese/Makefile
/usr/ports/chinese/opencc/
/usr/ports/comms/Makefile
/usr/ports/comms/p5-SMS-Send-NexmoUnicode/
/usr/ports/converters/enca/
/usr/ports/databases/msql3/
/usr/ports/databases/p5-DBD-ODBC/
/usr/ports/databases/p5-DBD-SQLite/
/usr/ports/databases/p5-DBIx-Inspector/
/usr/ports/databases/pecl-rrd/
/usr/ports/databases/phpmyadmin/
/usr/ports/databases/postgresql-jdbc/
/usr/ports/databases/redis/
/usr/ports/deskutils/gtg/
/usr/ports/devel/Makefile
/usr/ports/devel/bglibs/
/usr/ports/devel/binutils/
/usr/ports/devel/fistgen/
/usr/ports/devel/glui/
/usr/ports/devel/imake/
/usr/ports/devel/libdombey/
/usr/ports/devel/mdds/
/usr/ports/devel/mingw32-libffi/
/usr/ports/devel/mingw32-libyaml/
/usr/ports/devel/mingw32-zlib/
/usr/ports/devel/p4v/
/usr/ports/devel/p5-App-cpanminus/
/usr/ports/devel/p5-CHI/
/usr/ports/devel/p5-Config-Model/
/usr/ports/devel/p5-FindBin-libs/
/usr/ports/devel/p5-Sepia/
/usr/ports/devel/p5-Test-SharedFork/
/usr/ports/devel/py-urwid/
/usr/ports/devel/rubygem-chronic/
/usr/ports/devel/rubygem-columnize/
/usr/ports/devel/rubygem-devise/
/usr/ports/devel/rubygem-gemcutter/
/usr/ports/devel/rubygem-hoe/
/usr/ports/devel/rubygem-jammit/
/usr/ports/devel/rubygem-json/
/usr/ports/devel/rubygem-json_pure/
/usr/ports/devel/rubygem-little_plugger/
/usr/ports/devel/rubygem-minitest/
/usr/ports/devel/rubygem-multi_json/
/usr/ports/devel/rubygem-sequel/
/usr/ports/devel/rubygem-sexp_processor/
/usr/ports/devel/rubygem-tins/
/usr/ports/devel/valgrind/
/usr/ports/devel/websvn/
/usr/ports/devel/zziplib/
/usr/ports/dns/dnsjava/
/usr/ports/dns/rubygem-dnsruby/
/usr/ports/editors/paredit-mode.el/
/usr/ports/emulators/qemu-devel/
/usr/ports/emulators/virtualbox-ose-additions/
/usr/ports/emulators/virtualbox-ose-kmod/
/usr/ports/emulators/virtualbox-ose/
/usr/ports/emulators/wine/
/usr/ports/ftp/R-cran-RCurl/
files/260946d9401adc15de38730058d50c9798d7cb6a547da435f7308f9fb0515670.gz not 
found -- snapshot corrupt.

Len




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap broken

2011-12-04 Thread Sergio Tam

2011/12/4 Len Conrad lcon...@go2france.com:
 Never had a problem before

 Freebsd 8.2

 a couple weeks ago, on virgin 8.2, initial run of

 portsnap fetch extract

 ... ran great, and a couple of updates since then, also.

 but today:

 # portsnap fetch
 Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found.
 Fetching snapshot tag from portsnap1.FreeBSD.org... done.
 Fetching snapshot metadata... done.
 Updating from Sun Dec  4 15:26:46 CET 2011 to Mon Dec  5 02:05:11 CET 2011.
 Fetching 4 metadata patches... done.
 Applying metadata patches... done.
 Fetching 0 metadata files... done.
 Fetching 27 patches.1020... done.
 Applying patches... done.
 Fetching 2 new ports or files... done.


 # portsnap update
 Removing old files and directories... done.
 Extracting new files:
 /usr/ports/emulators/virtualbox-ose-additions/
 /usr/ports/emulators/virtualbox-ose-kmod/
 /usr/ports/emulators/virtualbox-ose/
 /usr/ports/emulators/wine/
 /usr/ports/ftp/R-cran-RCurl/
 files/260946d9401adc15de38730058d50c9798d7cb6a547da435f7308f9fb0515670.gz not 
 found -- snapshot corrupt.

 Len



rm -rf /var/db/portsnap/*
 portsnap fetch
 portsnap extract update


Regards
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

portsnap fails: look: tINDEX.new: File too large

2011-10-15 Thread Hartmann, O.

Since today's morning I receive on every box this message shown below
while doing a 'portsnap fetch'.

What's wrong and how to repair?

Regards,

Oliver

Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found.
Fetching snapshot tag from portsnap1.FreeBSD.org... done.
Fetching snapshot metadata... done.
look: tINDEX.new: File too large

Portsnap metadata appears bogus.
Cowardly refusing to proceed any further.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

cvs mirror on 8, 5G dvd? Re: Extract particular date snapshot from /var/db/portsnap?

2011-10-13 Thread Peter Vereshagin

Hello.

I think I should correct myself as what I found that way was unexpected, even
after aside from portsnap.

2011/06/15 06:51:32 +0400 Peter Vereshagin pe...@vereshagin.org = To 
freebsd-questions@freebsd.org :
PV GL cvs -d :ext:anon...@anoncvs1.freebsd.org:/home/ncvs export -D 2010-10-01
PV GL -d ports-2010-10-01 ports
PV GL 
PV GL In this example, I am exporting (no CVS metadata dirs) a full ports tree
PV GL as of Oct 1st, 2010 into the directory ports-2010-10-01.

First of all Thank you very much as it was unobvious to know that from manuals 
like: 

http://cvsbook.red-bean.com/cvsbook.htm

PV Sure, I know I can do it with (x)VCS.

This one was wrong: ports are available from CVS only. No svn, p4, etc.

PV But hell yes, having VCS before such a situation to happen is good. Just 
if we

This one seem insufficient now. I checked out ports from 'anoncvs':

cvs -d anon...@anoncvs.tw.freebsd.org:/home/ncvs co ports

and there is no backup for the deleted ports of my interest. I mean for
example I can not get the directory of x11/wmfstatus as it is deleted at this
moment.

I suppose such a download is not the all what I assume it to be: backup of
each and every port's versions till the moment being. So I just

rsync rsync://mirrorsite/pub/FreeBSD/development/FreeBSD-CVS/ports ./

and later I can just 'cvs export' any directory for any date from there,
right? I suppose I'd put it on a double-layer dvd, is it possible to export
from there? It is noted that:

http://www.freebsd.org/doc/en/articles/hubs/mirror-requirements.html

5.4G is sufficient.

Another question wth cvs is: can I get the particular port in its state of
N(=1,2, ...) changes ago? It seems to be possible only to look up particular
version for the particular file and checkout it but not for the directory
(assuming the port is a directory). At the least how to look up the list of
dates when the directory was changed should be great.

--
Peter Vereshagin pe...@vereshagin.org (http://vereshagin.org) pgp: A0E26627 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Extract particular date snapshot from /var/db/portsnap?

2011-06-15 Thread Peter Vereshagin

You can't take no for an answer, freebsd-questions!
2011/06/15 08:51:22 +0100 RW rwmailli...@googlemail.com = To 
freebsd-questions@freebsd.org :
R  - From what I see in /var/db/portsnap/files/ it keeps every file it
R  had ever downloaded: they all have different times.
R 
R It doesn't, it's a snapshot. The timestamps just reflect the last time
R each particular object was updated.

Hmm... looks like only a current ports state is kept in those tars:

$ tar -ztf 
/var/db/portsnap/files/12312e0e54a707a22613b0394a976c9d2044e98728b51c592d6e9a42c989300c.gz
 
Makefile
distinfo
pkg-descr
pkg-plist

such a single '.gz' extension was a false hint to me those are diffs.
Thanks all.

73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB  12F8 0CE1 4AAC A0E2 6627)
--
http://vereshagin.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Extract particular date snapshot from /var/db/portsnap?

2011-06-15 Thread RW

On Wed, 15 Jun 2011 12:44:30 +0400
Peter Vereshagin pe...@vereshagin.org wrote:

 You can't take no for an answer, freebsd-questions!
 2011/06/15 08:51:22 +0100 RW rwmailli...@googlemail.com = To
 freebsd-questions@freebsd.org :
 R  - From what I see in /var/db/portsnap/files/ it keeps every file
 R  it had ever downloaded: they all have different times.
 R 
 R It doesn't, it's a snapshot. The timestamps just reflect the last
 R time each particular object was updated.
 
 Hmm... looks like only a current ports state is kept in those tars:
 
 $ tar
 -ztf 
 /var/db/portsnap/files/12312e0e54a707a22613b0394a976c9d2044e98728b51c592d6e9a42c989300c.gz
 Makefile distinfo
 pkg-descr
 pkg-plist
 
 such a single '.gz' extension was a false hint to me those are diffs.

It does download diffs, but it applies them to the snapshot, and then
discards them.




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Can't fetch portsnap because of network problem


Hi,

I'm trying to fetch portsnap but can't because probably of network problem.

Whenever I try to run command
# portsnap fetch extract

the process stall and never reach 20%. It is sad. :(

The computer on wich I try to run this command is on my home LAN
that has a gateway/router.

What can I do to solve this problem?

--
Best Regards,
Paul

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Can't fetch portsnap because of network problem

2011-04-03 Thread Matthew Seaman

On 03/04/2011 14:45, Paul Chany wrote:
 I'm trying to fetch portsnap but can't because probably of network problem.
 
 Whenever I try to run command
 # portsnap fetch extract
 
 the process stall and never reach 20%. It is sad. :(
 
 The computer on wich I try to run this command is on my home LAN
 that has a gateway/router.
 
 What can I do to solve this problem?

You need to diagnose why your fetch is bombing out.  Start by checking
over your own equipment and try to eliminate that as a source of
problems.  Make sure all your cabling is in good condition and that all
network plugs are correctly seated.  Check for packet errors:

   # netstat -i

Anything non-zero in the Ierrs or Oerrs columns is a cause for concern,
especially if the error counters are going up over time.  If your
gateway/router has the capability, check for the same sort of errors there.

Having eliminated your own kit as a source of problems, try looking for
network problems between the portsnap servers and you.  mtr(8) is good
for this purpose, but (of course) catch22: to install it, you'ld need a
working ports tree... mtr will show up packet loss on intermediate
network links, and various sorts of routing problems.  If these are
present, then you need to contact your ISP who should be able to sort
things out on your behalf.

Finally, one thing that can screw up portsnap is a poorly implemented
transparent HTTP proxy.  My advice: *don't use ISPs that force you to
use transparent proxying*.  However, if this is what you are lumbered
with, then there is a simple work-around: use csup(1) instead of
portsnap(8).  csup doesn't run over HTTP, so it can't be mangled by
broken proxies.

Now, if you need help with any of this, you can certainly post here, but
for best results you'll need to supply a lot more detail about exactly
what it was you did and exactly what the result was.  Cut'n'paste from
the terminal is good, or use script(1) to save a transcript of a
terminal session.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: Can't fetch portsnap because of network problem


2011-04-03 16:19 keltezéssel, Matthew Seaman írta:

On 03/04/2011 14:45, Paul Chany wrote:
   

I'm trying to fetch portsnap but can't because probably of network problem.

Whenever I try to run command
# portsnap fetch extract

the process stall and never reach 20%. It is sad. :(

The computer on wich I try to run this command is on my home LAN
that has a gateway/router.

What can I do to solve this problem?
 

You need to diagnose why your fetch is bombing out.  Start by checking
over your own equipment and try to eliminate that as a source of
problems.  Make sure all your cabling is in good condition and that all
network plugs are correctly seated.  Check for packet errors:

# netstat -i

   
All my cabling is in good condition and all network plugs are correctly 
seated.


I attached the output of '# netstat -i' command in netstat.log file.
One can see there are 26 Oerrs in the file.

Informations of my home LAN are:
domain: excito
gateway: 192.168.10.1
name server: 192.168.10.1
netmask: 255.255.255.0

Any advices will be appreciated!

--
Best Regards,
Paul
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Can't fetch portsnap because of network problem


2011-04-03 18:35 keltezéssel, Paul Chany írta:

2011-04-03 16:19 keltezéssel, Matthew Seaman írta:

On 03/04/2011 14:45, Paul Chany wrote:
I'm trying to fetch portsnap but can't because probably of network 
problem.


Whenever I try to run command
# portsnap fetch extract

the process stall and never reach 20%. It is sad. :(

The computer on wich I try to run this command is on my home LAN
that has a gateway/router.

What can I do to solve this problem?

You need to diagnose why your fetch is bombing out.  Start by checking
over your own equipment and try to eliminate that as a source of
problems.  Make sure all your cabling is in good condition and that all
network plugs are correctly seated.  Check for packet errors:

# netstat -i

All my cabling is in good condition and all network plugs are 
correctly seated.


I attached the output of '# netstat -i' command in netstat.log file.


Well, it seems that one can't to send mail with attached file onto list, 
right?

Here is the output of netstat -i:
NameMtu Network   Address  Ipkts Ierrs Idrop
Opkts Oerrs  Coll
plip0  1500 Link#1   0 0 0
0 0 0
lo0   16384 Link#2   0 0 0
0 0 0
lo0   16384 fe80:2::1 fe80:2::10 - -
0 - -
lo0   16384 localhost ::1  0 - -
0 - -
lo0   16384 your-net  localhost0 - -
0 - -
ue01500 Link#3  00:00:e8:00:11:f172968 0 0
4867126 0
ue01500 192.168.10.0  cspetoile.localdo72934 - -
48682 - -


--
Best Regards,
Paul

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Can't fetch portsnap because of network problem


2011-04-03 16:19 keltezéssel, Matthew Seaman írta:

On 03/04/2011 14:45, Paul Chany wrote:
   

I'm trying to fetch portsnap but can't because probably of network problem.

Whenever I try to run command
# portsnap fetch extract

the process stall and never reach 20%. It is sad. :(

The computer on wich I try to run this command is on my home LAN
that has a gateway/router.

What can I do to solve this problem?
 

You need to diagnose why your fetch is bombing out.  Start by checking
over your own equipment and try to eliminate that as a source of
problems.  Make sure all your cabling is in good condition and that all
network plugs are correctly seated.  Check for packet errors:

# netstat -i

Anything non-zero in the Ierrs or Oerrs columns is a cause for concern,
especially if the error counters are going up over time.  If your
gateway/router has the capability, check for the same sort of errors there.
   

On my gateway/router the output of 'netstat -i' command is_

Kernel Interface table
Iface   MTU Met   RX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP 
TX-OVR Flg
eth0   1500 0   7914770  0  0  0  3427615  0  0  
0 BRU
eth1   1500 0   3369182  0  0  0  5234370  0  0  
0 ABMRU
lo16436 0  1193  0  0  0 1193  0  0  
0 LRU


--
Best Regards,
Paul

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Can't fetch portsnap because of network problem