9.0 base.txz ftp download time out

[Fbsd8]

I have a scripted ftp download for 8.x and 9.0 distribution files.
Yes I have the correct paths.
When I target 8.x releases it downloads the multiple distribution files.
To get the complete group takes about 20 minutes and ends cleanly.

But when I try to fetch the 9.0 base.txz file it says 100% completed and 
then times out. It also runs about 20 minutes just to download the 
single file. I do get the base.txz file downloaded but it ends uncleanly 
saying it timed out.


All the mirrors issue standard login messages saying there are 
restrictions in effect. My question is there some restriction about time 
allowed per file downloaded? And now that the layout of the 9.0 
distribution files has changed to a large file compared to many small 
files in a directory as for 8.0 is this causing the base.txz file 
download to time out? IE: does the ftp restrictions need to be changed 
for the new 9.0 distribution file?


Here is log of my ftp run.

230 Anonymous access granted, restrictions apply
Remote system type is UNIX.
Using binary mode to transfer files.
prompt off
Interactive mode off.
cd /pub/FreeBSD/releases/i386/i386/9.0-RELEASE
250 CWD command successful
epsv4 off
EPSV/EPRT on IPv4 off.
mreget  base.txz doc.txz
local: base.txz remote: base.txz
227 Entering Passive Mode (137,189,4,14,221,218).
150 Opening BINARY mode data connection for base.txz (54107736 bytes)
100% |***| 52839 KiB   42.93 KiB/s 
00:00 ETA

421 Service not available, remote server timed out. Connection closed.
54107736 bytes received in 21:30 (40.93 KiB/s)
ftp: No control connection for command



___
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: No updates needed to update system to 8.2-RELEASE-p6 but still on 8.2-RELEASE-p3

[Matthew Seaman]

On 19/02/2012 02:06, Antonio Olivares wrote:
> On Sat, Feb 18, 2012 at 8:04 PM, Robert Bonomi  
> wrote:
>>
>> Antonio,
>>  The 'upgrade' from _P5_ to P6 did not touch the kernel, hence the kernel ID
>> did not change.
>>
>>  Going from P3  you should have seen a kernel update.
>>
>>  what do you see if you do "strings /boot/kernel/kernel |grep 8"
> 
> It is a big file so I'll paste it to pastebin temporarily:
> 
> http://pastebin.com/K1PsTa0P

Heh.  The interesting bit is on line 4301 -- the last line of that
output.  A slightly more selective grep term would have been a good idea.

Anyhow, that shows the kernel on your system is 8.2-RELEASE-p3.  Which
implies that something ain't right somewhere.

Four possibilities, roughly in order of severity:

   1) None of the security patches between p3 and p6 did actually
  touch the kernel.  You can tell if this was the case by looking
  at the list of modified files in the security advisory.  The
  kernel is affected if any files under sys have been
  modified other than src/sys/conf/newvers.sh

  The last advisory that did touch the kernel was
  http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc

  which should have given you 8.2-RELEASE-p4.  However -- see
  below.

   2) An oversight in the freebsd-update process upstream meaning that
  the operational patches were applied, but not the changes to the
  kernel version number when the replacement kernel was compiled.
  Unlikely, as newvers.sh is always updated on each of the security
  branches even if the update doesn't touch the kernel.

   3) You've told freebsd-update not to touch your kernel.  Unlikely,
  and not in the default config, but useful where people need to
  use a custom kernel and maintain the rest of the system with
  freebsd-update.

  In this case, you'ld have modified /etc/freebsd-update.conf to
  change:

Components src world kernel

  to read:

Components src world

  Also you should be expecting to have to rebuild your kernel from
  sources, so I doubt this is the case.

   4) The kernel wasn't patched properly and hasn't been updated and
  you're still vulnerable.

Now, I believe that in fact the situation is in fact as described in
option (1) -- none of the patches since p3 have touched the kernel
distributed through freebsd-update.  (2) and (4) can be discounted -- if
such egregious mistakes had been made, they would long ago have been
noticed and corrected.

Here is the thing I alluded to under option (1).  The security patch for
the unix domain socket problem came out in two chunks.  There was an
original patch to fix the actual security problem, then a later followup
patch to fix a bug that exposed in the linux emulation layer.  It is
possible to tell this from the text of the advisory as it exists at the
moment, but you might not see it unless you are looking for it.  The
important bit of text is this:

  NOTE: The patch distributed at the time of the original advisory fixed
  the security vulnerability but exposed the pre-existing bug in the
  linux emulation subsystem.  Systems to which the original patch was
  applied should be patched with the following corrective patch, which
  contains only the additional changes required to fix the newly-
  exposed linux emulation bug:

Given that the second part of the patch was actually not a security fix,
there would not have been a modified kernel distributed.  So you got a
bundle of three advisories issued together on 2011-09-28 resulting in
FreeBSD 8.2-RELEASE-p3.  Then later on, at 2011-10-04 a further update
was issued modifying FreeBSD-SA-11:05-unix and technically taking the
system to FreeBSD 8.2-RELEASE-p4.  However, as this was not a security
fix, it was not applied to the freebsd-update distribution channel.  As
none of the updates since then have touched the kernel, it will still
show -p3 even though you are in fact fully patched against all known
security problems.

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

ps output

[jb]

Hi,

It's fb9-release.

Why the other ps entries do not display cron ?

$ top
...
  PID USERNAMETHR PRI NICE   SIZERES STATE   C   TIME   WCPU COMMAND
 1897 root  1  200  9644K  1208K nanslp  0   0:03  0.00% cron
...

$ ps -ax |grep cron
 1897  ??  Is  0:03.16 /usr/sbin/cron -s
62278   1  S+  0:00.01 grep cron
$ ps -a |grep cron
62337   1  S+   0:00.00 grep cron
$ ps -aux |grep cron

man ps
-x  When displaying processes matched by other options, include pro-
 cesses which do not have a controlling terminal.

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: No updates needed to update system to 8.2-RELEASE-p6 but still on 8.2-RELEASE-p3

[Antonio Olivares]

On Sun, Feb 19, 2012 at 4:22 AM, Matthew Seaman
 wrote:
> On 19/02/2012 02:06, Antonio Olivares wrote:
>> On Sat, Feb 18, 2012 at 8:04 PM, Robert Bonomi  
>> wrote:
>>>
>>> Antonio,
>>>  The 'upgrade' from _P5_ to P6 did not touch the kernel, hence the kernel ID
>>> did not change.
>>>
>>>  Going from P3  you should have seen a kernel update.
>>>
>>>  what do you see if you do "strings /boot/kernel/kernel |grep 8"
>>
>> It is a big file so I'll paste it to pastebin temporarily:
>>
>> http://pastebin.com/K1PsTa0P
>
> Heh.  The interesting bit is on line 4301 -- the last line of that
> output.  A slightly more selective grep term would have been a good idea.
>
> Anyhow, that shows the kernel on your system is 8.2-RELEASE-p3.  Which
> implies that something ain't right somewhere.
>
> Four possibilities, roughly in order of severity:
>
>   1) None of the security patches between p3 and p6 did actually
>      touch the kernel.  You can tell if this was the case by looking
>      at the list of modified files in the security advisory.  The
>      kernel is affected if any files under sys have been
>      modified other than src/sys/conf/newvers.sh
>
>      The last advisory that did touch the kernel was
>      http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc
>
>      which should have given you 8.2-RELEASE-p4.  However -- see
>      below.
>
>   2) An oversight in the freebsd-update process upstream meaning that
>      the operational patches were applied, but not the changes to the
>      kernel version number when the replacement kernel was compiled.
>      Unlikely, as newvers.sh is always updated on each of the security
>      branches even if the update doesn't touch the kernel.
>
>   3) You've told freebsd-update not to touch your kernel.  Unlikely,
>      and not in the default config, but useful where people need to
>      use a custom kernel and maintain the rest of the system with
>      freebsd-update.
>
>      In this case, you'ld have modified /etc/freebsd-update.conf to
>      change:
>
>        Components src world kernel
>
>      to read:
>
>        Components src world
>
>      Also you should be expecting to have to rebuild your kernel from
>      sources, so I doubt this is the case.

/etc/freebsd-update.conf has:

=line 1 col 0 lines from top 1 
# $FreeBSD: src/etc/freebsd-update.conf,v 1.6.2.2.6.1 2010/12/21 17:09:25 kensmi

# Trusted keyprint.  Changing this is a Bad Idea unless you've received
# a PGP-signed email from  telling you to
# change it and explaining why.
KeyPrint 800651ef4b4c71c27e60786d7b487188970f4b4169cc055784e21eb71d410cc5

# Server or server pool from which to fetch updates.  You can change
# this to point at a specific server if you want, but in most cases
# using a "nearby" server won't provide a measurable improvement in
# performance.
ServerName update.FreeBSD.org

# Components of the base system which should be kept updated.
Components src world kernel

. removed to save space 

>
>   4) The kernel wasn't patched properly and hasn't been updated and
>      you're still vulnerable.
>
> Now, I believe that in fact the situation is in fact as described in
> option (1) -- none of the patches since p3 have touched the kernel
> distributed through freebsd-update.  (2) and (4) can be discounted -- if
> such egregious mistakes had been made, they would long ago have been
> noticed and corrected.
>
> Here is the thing I alluded to under option (1).  The security patch for
> the unix domain socket problem came out in two chunks.  There was an
> original patch to fix the actual security problem, then a later followup
> patch to fix a bug that exposed in the linux emulation layer.  It is
> possible to tell this from the text of the advisory as it exists at the
> moment, but you might not see it unless you are looking for it.  The
> important bit of text is this:
>
>  NOTE: The patch distributed at the time of the original advisory fixed
>  the security vulnerability but exposed the pre-existing bug in the
>  linux emulation subsystem.  Systems to which the original patch was
>  applied should be patched with the following corrective patch, which
>  contains only the additional changes required to fix the newly-
>  exposed linux emulation bug:
>
> Given that the second part of the patch was actually not a security fix,
> there would not have been a modified kernel distributed.  So you got a
> bundle of three advisories issued together on 2011-09-28 resulting in
> FreeBSD 8.2-RELEASE-p3.  Then later on, at 2011-10-04 a further update
> was issued modifying FreeBSD-SA-11:05-unix and technically taking the
> system to FreeBSD 8.2-RELEASE-p4.  However, as this was not a security
> fix, it was not applied to the freebsd-update distribution channel.  As
> none of the updates since then have touched the kernel, it will still
> show -p3 even though you are in fact fully patched against all known
> security problems.

Re: No updates needed to update system to 8.2-RELEASE-p6 but still on 8.2-RELEASE-p3

[Erich Dollansky]

Hi,

On Sunday 19 February 2012 18:17:59 Antonio Olivares wrote:
> 
> I hope this is the case, but that -p3 makes me think?  I am hesistant
> to move to 9.0-RELEASE as of yet.  There will apparently be an
> 8.3-RELEASE and I am not sure whether I have to rebuild all ports if I

you could adapt my strategy. Stay with 8 until 10 appears at the scene.

You will have support for 8.x until 10.0 will be available. There is no need 
for you to switch to 9.x at all.

Erich
___
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: ps output

[RW]

On Sun, 19 Feb 2012 10:28:29 + (UTC)
jb wrote:

> Hi,
> 
> It's fb9-release.
> 
> Why the other ps entries do not display cron ?
> 
> $ top
> ...
>   PID USERNAMETHR PRI NICE   SIZERES STATE   C   TIME   WCPU
> COMMAND 1897 root  1  200  9644K  1208K nanslp  0   0:03
> 0.00% cron ...
> 
> $ ps -ax |grep cron
>  1897  ??  Is  0:03.16 /usr/sbin/cron -s
> 62278   1  S+  0:00.01 grep cron
> $ ps -a |grep cron
> 62337   1  S+   0:00.00 grep cron
> $ ps -aux |grep cron
> 


If you grep for cron's pid instead of "cron" you'll see that the
command is truncated.
___
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: No updates needed to update system to 8.2-RELEASE-p6 but still on 8.2-RELEASE-p3

[RW]

On Sun, 19 Feb 2012 10:22:57 +
Matthew Seaman wrote:


> Four possibilities, roughly in order of severity:
> 
>1) None of the security patches between p3 and p6 did actually
>   touch the kernel.  You can tell if this was the case by looking
>   at the list of modified files in the security advisory.  The
>   kernel is affected if any files under sys have been
>   modified other than src/sys/conf/newvers.sh
> 
>   The last advisory that did touch the kernel was
>   http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc
> 
>   which should have given you 8.2-RELEASE-p4.  However -- see
>   below.

But aren't all those changes the linux kernel module, rather than the
kernel itself. 

I think  8.2-RELEASE-p3 looks OK.
___
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: No updates needed to update system to 8.2-RELEASE-p6 but still on 8.2-RELEASE-p3

[Leslie Jensen]

RW skrev 2012-02-19 13:59:

On Sun, 19 Feb 2012 10:22:57 +
Matthew Seaman wrote:



Four possibilities, roughly in order of severity:

1) None of the security patches between p3 and p6 did actually
   touch the kernel.  You can tell if this was the case by looking
   at the list of modified files in the security advisory.  The
   kernel is affected if any files under sys have been
   modified other than src/sys/conf/newvers.sh

   The last advisory that did touch the kernel was
   http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc

   which should have given you 8.2-RELEASE-p4.  However -- see
   below.


But aren't all those changes the linux kernel module, rather than the
kernel itself.

I think  8.2-RELEASE-p3 looks OK.
___
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"


I don't know if it's the solution to your question but I asked the same 
a while back and the answer I got was that I had to recompile and 
install the kernel then you'll have p6 :-)


/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: No updates needed to update system to 8.2-RELEASE-p6 but still on 8.2-RELEASE-p3

[RW]

On Sun, 19 Feb 2012 14:11:09 +0100
Leslie Jensen wrote:

> 
> 

> I don't know if it's the solution to your question but I asked the
> same a while back and the answer I got was that I had to recompile
> and install the kernel then you'll have p6 :-)

The only thing you gain by that is that uname reports p6, it's purely
cosmetic.
___
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"

skype

[ajtiM]

Skype on my FreeBSD 9.0-RELEASE and KDE 4.7.4 working but after five, sometimes 
more or less minutes is sound dead. I need to recall again...

In /etc/rc.conf I  have:
linux_enable="YES" 

Thank you.

Mitja

http://jpgmag.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: No updates needed to update system to 8.2-RELEASE-p6 but still on 8.2-RELEASE-p3

[Matthew Seaman]

On 19/02/2012 11:17, Antonio Olivares wrote:
> I hope this is the case, but that -p3 makes me think?  I am hesistant
> to move to 9.0-RELEASE as of yet.  There will apparently be an
> 8.3-RELEASE and I am not sure whether I have to rebuild all ports if I
> update to newer release.  I have read some places that one does not
> have to rebuild all ports, and just install compat8.x/ special port.
> In FreeBSD Handbook, it still recommends to rebuild all ports.  It
> took me a while to get going last time I moved from 8.1-RELEASE to
> 8.2-RELEASE, so I am hesistant to do it :(   And not being sure about
> this, I am in the thinking process of what should I do.

If you upgrade from 8.2 to 8.3 then you don't need to rebuild all your
ports.  There's a guarantee of ABI compatibility for all 8.x releases,
meaning that with a very few exceptions, anything that runs on one 8.x
version will run on any of them.  The exceptions are programs that go
grovelling into kernel memory -- lsof(8) is probably the only one most
people will encounter.

On the other hand, if you upgrade from 8.x to 9.0, then yes you will
have to rebuild all your ports.  If you install compat8x you can /run/
programs built for 8.x on 9.0, but you can't[*] upgrade or install a lot
of programs that use shlibs from ports.   Ultimately it is less hassle
just to rebuild everything and be done with it.

Cheers,

Matthew


[*] Well, unless you are a Unix guru and wize in the ways of the dynamic
loader.

-- 
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: One or Four?

[Julian H. Stacey]

"Robison, Dave" wrote:
> On 02/17/2012 15:22, Julian H. Stacey wrote:
> >
> >
> >> Let the majority decide which layout is preferred for the default.
> > No. Bad idea. Not on questions@, the list of the least clued up,
> > the list raw beginners are referred to subscribe to.  At least get
> > a majority on hackers@ or current@ or arch@.  Some answers one sees
> > on questions@ are very good, but some are ... the other way.
> >
> >
> > Cheers,
> > Julian
> 
> Actually, the discussion and ideas so far have been very interesting and 
> helpful.

Beside the point: the Wrong list was posted to.
questions@ list was created to help beginners,
not to debate & invite votes to determine future design.

FreeBSD lists have remits so people can read & write lists most
tuned to interests.  Tossing non beginner support topics in questions@
deprives other lists. Not all on hackers@ current@ & the many other
list want to be on questions@ & vice versa.

Please read list remits & subscribe & post most appropriate list per topic.

Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
 Reply below not above, cumulative like a play script, & indent with "> ".
 Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
Mail from @yahoo dumped @berklix.  http://berklix.org/yahoo/
___
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: ps output

[Joshua Isom]

On 2/19/2012 6:44 AM, RW wrote:

On Sun, 19 Feb 2012 10:28:29 + (UTC)
jb wrote:


Hi,

It's fb9-release.

Why the other ps entries do not display cron ?

$ top
...
   PID USERNAMETHR PRI NICE   SIZERES STATE   C   TIME   WCPU
COMMAND 1897 root  1  200  9644K  1208K nanslp  0   0:03
0.00% cron ...

$ ps -ax |grep cron
  1897  ??  Is  0:03.16 /usr/sbin/cron -s
62278   1  S+  0:00.01 grep cron
$ ps -a |grep cron
62337   1  S+   0:00.00 grep cron
$ ps -aux |grep cron




If you grep for cron's pid instead of "cron" you'll see that the
command is truncated.


Or you can use the -w option twice.  I use it whenever piping to another 
process.


___
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: One or Four?

[Daniel Staal]

--As of February 19, 2012 3:30:15 PM +0100, Julian H. Stacey is alleged to 
have said:



Beside the point: the Wrong list was posted to.
questions@ list was created to help beginners,
not to debate & invite votes to determine future design.

FreeBSD lists have remits so people can read & write lists most
tuned to interests.  Tossing non beginner support topics in questions@
deprives other lists. Not all on hackers@ current@ & the many other
list want to be on questions@ & vice versa.

Please read list remits & subscribe & post most appropriate list per
topic.


--As for the rest, it is mine.

I don't get 'beginners' from 'User questions and technical support'.  It's 
probably the best place for most beginner's questions, but that isn't the 
same as 'the list is for beginners'.  Hackers@ might have been appropriate 
for this question, but it's not really a *technical* question: It's a 
*preference* question.  As such asking the group of general users isn't a 
bad idea, as it's their preferences that the question was aimed at...


It was a question for the users of FreeBSD.  Adressing it to the list for 
user questions may be an interesting interpretation of the grammar, but 
it's not an invalid one.


Daniel T. Staal

---
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---
___
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: skype

[ajtiM]

On Sunday 19 February 2012 08:20:43 ajtiM wrote:
> Skype on my FreeBSD 9.0-RELEASE and KDE 4.7.4 working but after five,
> sometimes more or less minutes is sound dead. I need to recall again...
> 
> In /etc/rc.conf I  have:
> linux_enable="YES"
> 
> Thank you.
> 
> Mitja
> 
> http://jpgmag.com/people/lumiwa

kern.hz=100 in /boot/loader.conf solved a problem.

Thanks.

Mitja

http://jpgmag.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: No updates needed to update system to 8.2-RELEASE-p6 but still on 8.2-RELEASE-p3

[Nikola Pavlović]

On Sun, Feb 19, 2012 at 05:17:59AM -0600, Antonio Olivares wrote:
> On Sun, Feb 19, 2012 at 4:22 AM, Matthew Seaman
>  wrote:
> > Here is the thing I alluded to under option (1).  The security patch for
> > the unix domain socket problem came out in two chunks.  There was an
> > original patch to fix the actual security problem, then a later followup
> > patch to fix a bug that exposed in the linux emulation layer.  It is
> > possible to tell this from the text of the advisory as it exists at the
> > moment, but you might not see it unless you are looking for it.  The
> > important bit of text is this:
> >
> >  NOTE: The patch distributed at the time of the original advisory fixed
> >  the security vulnerability but exposed the pre-existing bug in the
> >  linux emulation subsystem.  Systems to which the original patch was
> >  applied should be patched with the following corrective patch, which
> >  contains only the additional changes required to fix the newly-
> >  exposed linux emulation bug:
> >
> > Given that the second part of the patch was actually not a security fix,
> > there would not have been a modified kernel distributed.  So you got a
> > bundle of three advisories issued together on 2011-09-28 resulting in
> > FreeBSD 8.2-RELEASE-p3.  Then later on, at 2011-10-04 a further update
> > was issued modifying FreeBSD-SA-11:05-unix and technically taking the
> > system to FreeBSD 8.2-RELEASE-p4.  However, as this was not a security
> > fix, it was not applied to the freebsd-update distribution channel.  As
> > none of the updates since then have touched the kernel, it will still
> > show -p3 even though you are in fact fully patched against all known
> > security problems.
> 
> I hope this is the case, but that -p3 makes me think?  I am hesistant

If it will feel you more confident that everything is OK, I too have -p3
reported from the kernel, but -p6 in newvers.sh.  I remember a
discussion shortly after FreeBSD-SA-11:05-unix (maybe on
freebsd-security@ but I'm not sure) about this confusion with patch
level reported and if I remember correctly the conclusion was in
agreement with what Matthew wrote above.

> 
> Thank you very much for your kind explanation and hopefully I am in
> the (4) category.  How does one know when a new 8.2-RELEASE-pX, has
> been released?  where X is a number >= 6?
> 

You could follow freebsd-announce@, and/or optionally freebsd-security@.
All security advisories and errata patches are announced there.
Alternatively, there are http://www.freebsd.org/security/advisories.html
and http://www.freebsd.org/security/notices.html pages along with their
RSS feeds http://www.freebsd.org/security/rss.xml and
http://www.freebsd.org/security/errata.xml, respectively.


-- 
"Have you lived here all your life?"
"Oh, twice that long."

___
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: No updates needed to update system to 8.2-RELEASE-p6 but still on 8.2-RELEASE-p3

[Matthew Seaman]

On 19/02/2012 17:49, Nikola Pavlović wrote:
> If it will feel you more confident that everything is OK, I too have -p3
> reported from the kernel, but -p6 in newvers.sh.  I remember a
> discussion shortly after FreeBSD-SA-11:05-unix (maybe on
> freebsd-security@ but I'm not sure) about this confusion with patch
> level reported and if I remember correctly the conclusion was in
> agreement with what Matthew wrote above.

Um... it's not really surprising that the two posts are in agreement.  I
certainly read that other thread, and I may even have written that other
post you mention...

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: /usr/home vs /home

[parv]

I vote for multiple partitions with user specified names (or at least
be able to change /home mount point to something else) & allocated
space.


in message <4f3f1817.7030...@herveybayaustralia.com.au>,
wrote Da Rock thusly...
>
> On 02/18/12 12:16, Daniel Staal wrote:
> > --As of February 17, 2012 11:46:23 PM +0100, Polytropon is alleged to
> > have said:
> >
> >> Well, to be honest, I never liked the "old style" default
> >> with /home being part of /usr. As I mentioned before, _my_
> >> default style for separated partitions include:
> >>
> >> /
> >> swap
> >> /tmp
> >> /var
> >> /usr
> >> /home

I like having /var and/or /tmp to be separate from /, /usr, /home in
case it fills up or gets damaged. For me, they are not as much as
critical as the rest.


> >> In special cases, add /opt or /scratch as separate partitions
> >> with intendedly limited sizes.
> >>
> >> You can see that all user data is kept independently from
> >> the rest of the system. It can easily be switched over to
> >> a separate "home disk" if needed.
> >
> > --As for the rest, it is mine.
> >
> > I'm in agreement with you on that I like to have /home be a
> > separate partition, and not under /usr.  (Of course, my current
> > zfs system has 40 partitions...)  Partly though I recognize that
> > I like it because that's what I'm used to, and how I learned to
> > set it up originally.  (My first unix experience was with
> > OpenBSD, over 10 years ago now.)
> >
> > I've never seen anything listing the main reasons for having
> > /home under /usr though.  I figure there must be a decent reason
> > why.  Would anyone care to enlighten me?  What are the perceived
> > advantages?  (Particularly if you then make a symlink to /home.)
>
> But seriously, for the pedantic yes, but for a desktop user (at
> least) having home on /usr partition makes sense - balances space
> and functionality;

Give / + /usr a 1 or 2 GB for FreeBSD files; allot the rest to other
partitions.


> plus a lack of nodes on the disk for partitions? Limit was 8 I
> think. But now with /usr/home if you want to install from ports it
> can take a few gig, but that can be wasted because you're not
> always installing from ports, so might as well share space with
> the home directories and balance that way. Otherwise you'd need
> 30G (about) for /usr/ports and all the stuff you want to install
> and then that cannot be used at all for /home which could be
> cleared quite easily to make room if necessary if it was on the
> same partition.

  # df -h | egrep -v 'devfs|proc' ;  echo ; swapinfo ; echo ; \
  # ll -d /{var,home,tmp} /usr/{ports,local,src,obj} ;
  Filesystem SizeUsed   Avail Capacity  Mounted on
  /dev/ad4s4a2.9G1.5G1.2G56%/
  /dev/ad4s4d989M243M667M27%/var
  /dev/ad4s4e275G172G 80G68%/misc

  Device  1K-blocks UsedAvail Capacity
  /dev/ad4s210442880  1044288 0%

  lrwxr-xr-x   1 root  wheel   10 Apr  2  2010 /home@ -> /misc/home
  lrwxr-xr-x   1 root  wheel   13 Apr  2  2010 /tmp@ -> /var/tmp-root
  lrwxr-xr-x   1 root  wheel   11 Apr  2  2010 /usr/local@ -> /misc/local
  lrwxr-xr-x   1 root  wheel9 Apr  2  2010 /usr/obj@ -> /misc/obj
  lrwxr-xr-x   1 root  wheel   11 Apr  2  2010 /usr/ports@ -> /misc/ports
  lrwxr-xr-x   1 root  wheel9 Dec  6 20:35 /usr/src@ -> /misc/src
  drwxr-xr-x  27 root  wheel  512 Feb 18 13:11 /var/


(There is another partition, /toybox of 8.5 GB, currently not mounted,
to experiment with virtualbox.)


- parv

-- 

___
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: One or Four?

[Julian H. Stacey]

Hi,
Reference:
> From: Daniel Staal  
> Date: Sun, 19 Feb 2012 11:10:57 -0500 
> Message-id:

Daniel Staal wrote:
> --As of February 19, 2012 3:30:15 PM +0100, Julian H. Stacey is alleged to 
> have said:
> 
> > Beside the point: the Wrong list was posted to.
> > questions@ list was created to help beginners,
> > not to debate & invite votes to determine future design.
> >
> > FreeBSD lists have remits so people can read & write lists most
> > tuned to interests.  Tossing non beginner support topics in questions@
> > deprives other lists. Not all on hackers@ current@ & the many other
> > list want to be on questions@ & vice versa.
> >
> > Please read list remits & subscribe & post most appropriate list per
> > topic.
> 
> --As for the rest, it is mine.
> 
> I don't get 'beginners' from 'User questions and technical support'.  

I remember when & why the list was set up.
See src/ etc/motd


Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
 Reply below not above, cumulative like a play script, & indent with "> ".
 Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
Mail from @yahoo dumped @berklix.  http://berklix.org/yahoo/
___
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: DNS - slaving the root zone

[Terrence Koeman]

On Sun, 19 Feb 2012 at 01:14:47, Doug Barton wrote:

> On 02/18/2012 03:23, Damien Fleuriot wrote:
>>
>> On 2/18/12 12:57 AM, Doug Barton wrote:
>>>
>>> To clarify, almost universally the opposition to the idea centers
>>> around the problems of users who enable this method, and then don't
>>> notice if something changes/breaks, resulting in a stale zone (or
>>> zones, depending on what you choose to slave). I have always
>>> acknowledged that this is a valid concern, just not one that I think
>>> overwhelms the virtues of doing the slaving in the first place.
>>>
>>
>> Could you elaborate on the "something changes/breaks, admin doesn't
>> notice, results in a stale zone" bit ?
>
> Most commonly whatever auth. server the user is axfr'ing from suddenly
> stops offering that ability.
[snip]

I'm just done converting from named.root to slaving the root, I checked which 
servers allow axfr (at least for me...) and added them all as masters. Multiple 
masters would substantially decrease the risk of stale zones, yes? I have 
attached the relevant portion of my config, maybe it's useful.

Also, I was wondering, now that I slave . and arpa, is it still beneficial to 
retain the 'empty zones' that fall within those or are they redundant?

I figure they are, as the comments say 'Serving the following zones locally 
will prevent any queries for these zones leaving your network and going to the 
root name servers.' and now my server *is* the root as far as it knows.

Thanks.

--
Regards,
T. Koeman, MTh/BSc/BPsy; Technical Monk

MediaMonks B.V. (www.mediamonks.com)
Please quote relevant replies in correspondence.



named.conf
Description: Binary data
___
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"

Which mailinglist is appropriate for discussing uart changes?

[Terrence Koeman]

Could someone point me to the right mailinglist to discuss adding support for 
the MCS9904 chip to uart? I'm working on it, but I have some questions 
regarding FIFO sizes and how they are currently determined.

Thanks.

--
Regards,
T. Koeman, MTh/BSc/BPsy; Technical Monk

MediaMonks B.V. (www.mediamonks.com)
Please quote relevant replies in correspondence.




___
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: ps output

[Robert Bonomi]

> From owner-freebsd-questi...@freebsd.org  Sun Feb 19 04:35:10 2012
> To: freebsd-questions@freebsd.org
> From: jb 
> Date: Sun, 19 Feb 2012 10:28:29 + (UTC)
> Subject: ps output
>
> Hi,
>
> It's fb9-release.
>
> Why the other ps entries do not display cron ?

Add a 'ww' -- yes, -two- 'w' characters -- to the ps switches, and see what
happens.

Now append the pid, '1877' to the end of the ps switches, and try the various 
ps commands with and without 'ww' specified.

Enlightenment will follow.

>
> $ top
> ...
>   PID USERNAMETHR PRI NICE   SIZERES STATE   C   TIME   WCPU COMMAND
>  1897 root  1  200  9644K  1208K nanslp  0   0:03  0.00% cron
> ...
>
> $ ps -ax |grep cron
>  1897  ??  Is  0:03.16 /usr/sbin/cron -s
> 62278   1  S+  0:00.01 grep cron
> $ ps -a |grep cron
> 62337   1  S+   0:00.00 grep cron
> $ ps -aux |grep cron
>
> man ps
> -x  When displaying processes matched by other options, include pro-
>  cesses which do not have a controlling terminal.
>
> 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"
>
___
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: ps output

[jb]

Joshua Isom  gmail.com> writes:

> 
> On 2/19/2012 6:44 AM, RW wrote:
> > On Sun, 19 Feb 2012 10:28:29 + (UTC)
> > jb wrote:
> >
> >> Hi,
> >>
> >> It's fb9-release.
> >>
> >> Why the other ps entries do not display cron ?
> >>
> >> $ top
> >> ...
> >>PID USERNAMETHR PRI NICE   SIZERES STATE   C   TIME   WCPU
> >> COMMAND 1897 root  1  200  9644K  1208K nanslp  0   0:03
> >> 0.00% cron ...
> >>
> >> $ ps -ax |grep cron
> >>   1897  ??  Is  0:03.16 /usr/sbin/cron -s
> >> 62278   1  S+  0:00.01 grep cron
> >> $ ps -a |grep cron
> >> 62337   1  S+   0:00.00 grep cron
> >> $ ps -aux |grep cron
> >>
> >
> >
> > If you grep for cron's pid instead of "cron" you'll see that the
> > command is truncated.
> 
> Or you can use the -w option twice.  I use it whenever piping to another 
> process.
> ...

Hi guys,

The same entries and their outputs on randomly larger (column-wise) terminal:
$ ps -ax |less
  PID  TT  STAT   TIME COMMAND
...
 1891  ??  Is  0:00.43 sendmail: Queue runner@00:30:00 for /var/spool/clie
ntmqueue (sendmail)
 1897  ??  Ss  0:03.56 /usr/sbin/cron -s
...

$ ps -aux |less
USER PID  %CPU %MEMVSZRSS  TT  STAT STARTED   TIME COMMAND
...
smmsp   1891   0.0  0.1  11324   2404  ??  Is   Thu12PM0:00.43 sendmai
l: Queue runner@00:30:00 for /var/spool/client
root1897   0.0  0.1   9644   1208  ??  Is   Thu12PM0:03.56 /usr/sb
in/cron -s
...
 
I think the current application of terminal window size is incorrect.

command1 | command2

Right now it is:
command1 -> fd (stdout) -> win size "filter" -> | -> display
It should be:
command1 -> fd (stdout) -> | -> win size "filter" -> display

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"

Mail

[Daniel Lewis]

I just install free bsd 8.2 and i can send mail out but cant recieve. From
recipient end its combining the hostname and domain name.
___
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"

Fwd: Mail

[Daniel Lewis]

-- Forwarded message --
From: Daniel Lewis 
Date: Sun, Feb 19, 2012 at 2:23 PM
Subject: Mail
To: freebsd-questions@freebsd.org


I just install free bsd 8.2 and i can send mail out but cant recieve. From
recipient end its combining the hostname and domain name.
___
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: Mail

[jb]

Daniel Lewis  gmail.com> writes:

> 
> I just install free bsd 8.2 and i can send mail out but cant recieve. From
> recipient end its combining the hostname and domain name.
> ...

Check sendmail in /etc/hosts.allow

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: No updates needed to update system to 8.2-RELEASE-p6 but still on 8.2-RELEASE-p3

[Nikola Pavlović]

On Sun, Feb 19, 2012 at 06:00:50PM +, Matthew Seaman wrote:
> On 19/02/2012 17:49, Nikola Pavlović wrote:
> > If it will feel you more confident that everything is OK, I too have -p3
> > reported from the kernel, but -p6 in newvers.sh.  I remember a
> > discussion shortly after FreeBSD-SA-11:05-unix (maybe on
> > freebsd-security@ but I'm not sure) about this confusion with patch
> > level reported and if I remember correctly the conclusion was in
> > agreement with what Matthew wrote above.
> 
> Um... it's not really surprising that the two posts are in agreement.  I
> certainly read that other thread, and I may even have written that other
> post you mention...
> 

Sorry if I wasn't clear, I did not intend to question your answer
(which, as usual, was thorough and most helpful) in any way, but only to
point out, because Antonio expressed some doubt, that it isn't mere
speculation and that the issue is known, and that he isn't the only one with
"strange" -pX reported by uname (i.e. he can be confident that his system is
up to date, as far as this is concerned).  I don't remember who wrote what
(and laziness prevents me from searching the archives), only that people who
never use Linux emulation need not apply the follow up patch in which case
-p3 is correct.


-- 
About the only thing we have left that actually
discriminates in favor of the plain people is the stork.

___
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: Mail

[Odhiambo Washington]

On Sun, Feb 19, 2012 at 22:23, Daniel Lewis wrote:

> I just install free bsd 8.2 and i can send mail out but cant recieve. From
> recipient end its combining the hostname and domain name.
>
>
Hi Daniel,

In order to be able to "receive" e-mails on your server, a lot more is
involved than just installing the box. Your domain name (e.g. danlewis.name)
must be published in the web. I mean, you must have a registered domain
name. After it being registered, it must have some special records
published (DNS) and these records are called MX (Mail eXchanger) records.
They must point back to your server's *public *IP address if it is the one
you want to receive mail from. That public IP address needs to be
static/permanent or some other special DNS (dynamic DNS)  records need to
come into play. Once all that is done, you will need to setup a
fully-fledged mail server that can receive mail and let people retrieve it.
In that case, you will need to run two applications - one is an SMTP server
(the one that receives and places the mail into a 'mailbox') and the other
being a POP3/IMAP4 server (the one that allows a user with a valid username
and password to "retrieve" their e-mail from the mailbox).
I suggest you start looking at Exim ,
Postfix(for SMTP) and
Dovecot  (for POP3/IMAP).
There are several primers for setting these up, and so be prepared to start
reading all those and making decisions on what you need to do - because now
you are an aspiring "Server Administrator" (mail server for starters, and I
know soon you'll be becoming a web server, database server, etc
administrator, for that is the life you have chosen:))
May I start by pointing you to the following primers:

1. Exim+Dovecot - http://exim4u.org/
2. Postfix+Dovecot - http://www.purplehat.org/?page_id=4

The above two include using MySQL database as backend and have a GUI to
manage, which means you will soon be getting your hands dirty with MySQL
and Apache, and PHP - I feel so sad for you because of this, but it's
life:-)

3. http://rob0.nodns4.us/howto/ - This one was just posted to this list
today. It's about Postfix+Dovecot using SQLite database as backend. I guess
there is no GUI to manage this.

Remember, when faced with difficulties, a good sysadmin reads log files for
the different applications s/he runs and tries to figure it out using
Google, then when stuck, can post a question to a general mailing list like
this one, or to a specific mailing list dealing with the particular
application.

Welcome to FreeBSD, and to being a Systems Administrator.


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
I can't hear you -- I'm using the scrambler.
Please consider the environment before printing this email.
___
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: DNS - slaving the root zone

[Doug Barton]

On 02/19/2012 10:39, Terrence Koeman wrote:

> I'm just done converting from named.root to slaving the root, I
> checked which servers allow axfr (at least for me...) and added them
> all as masters.

Given that some of the root server operators don't really like people
doing this routinely it would be net.friendlier to list the ICANN
servers first. They are just as up to date as the live root servers.

> Multiple masters would substantially decrease the
> risk of stale zones, yes?

Yes.

> Also, I was wondering, now that I slave . and arpa, is it still
> beneficial to retain the 'empty zones' that fall within those or are
> they redundant?

They are not redundant, and yes, they are still beneficial.


Doug

-- 

It's always a long day; 86400 doesn't fit into a short.

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.com/

___
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: Which mailinglist is appropriate for discussing uart changes?

[Frank Shute]

On Sun, Feb 19, 2012 at 07:10:30PM +0100, Terrence Koeman wrote:
>
> Could someone point me to the right mailinglist to discuss adding
> support for the MCS9904 chip to uart? I'm working on it, but I have
> some questions regarding FIFO sizes and how they are currently
> determined.
> 
> Thanks.
> 
> -- Regards, T. Koeman, MTh/BSc/BPsy; Technical Monk

Hi Terrence,

Looking at the list of mailing lists, I'd say your best bet is to send
an e-mail to freebsd-net@ asking them if it's appropriate to ask the
question there and if not where.

uarts and FIFOs sounds like it's network stack to me and I'd guess
someone on that list might be able to supply you with an answer.


Regards,

-- 

 Frank

 Contact info: http://www.shute.org.uk/misc/contact.html




pgpR5gIHnfvDu.pgp
Description: PGP signature

Re: webcamd and device numbering

[Frank Shute]

On Sun, Feb 19, 2012 at 12:32:42PM +1000, Da Rock wrote:
>
> I've been struggling with this on my own for ages now, and I was 
> determined to try and sort it myself. But I'll now eat my humble pie and 
> ask for some help :)
> 
> I have (I believe I have mentioned this before) 5 dvb tuners in a 
> FreeBSD server (8.2): 1 cx88, 2 DiVico dual tuners (that totals 4 
> amongst just the DiVico's). I'm using webcamd to use these (thank God I 
> can get away from Linux!), and they work fine except I have to run ln -s 
> to link them to the right places after every reboot (Only the Divico's 
> use webcamd). So they should look like this:
> 
> $ls /dev/dvb/
> adapter0adapter1adapter2adapter3
> 
> instead:
> 
> ls /dev/dvb/
> adapter0adapter16adapter24adapter8
> 
> This is a real problem because 1. MPlayer only accepts 0-4, and 2. 
> GStreamer (including xine) only accept 1-16.
> 
> I tried working out how to resolve the issue any sane way; and then I 
> resorted to some quick hacks. I tried uding devfs.rules for links before 
> I found out it can't do that at all. devfs.conf is no good, as it sets 
> them up to begin with. And running some commands in rc.local didn't 
> work: `ln -s /dev/dvb/adapter8 /dev/dvb/adapter1` and so forth.
> 
> I googled and googled and there seem to be no real fix as webcamd won't 
> work without hal and relies on it for the numbering (but borks it 
> continuously). I've tried updates and so forth, but all to no avail. I'm 
> not too worried about a permanent fix because hal's death bells have 
> tolled, but I do need to fix this as it is really getting annoying now - 
> the server is on continuously but can go down from time to time and 
> catches the unwary :) (like when a scheduled recording which requires 
> say adapter1 finds it no longer there)
> 
> I'm using webcamd-3.2.0.2, which I recently updated.
> 
> Cheers

The manpage seems to indicate that HAL is an option for webcamd(8):

 -H  Register device by the HAL daemon.

If you still have problems you might want to post on multimedia@ as
the author of webcamd hangs out there (hselasky@).


Regards,

-- 

 Frank

 Contact info: http://www.shute.org.uk/misc/contact.html




pgpv1mdq18lDB.pgp
Description: PGP signature