Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Aug 2014 09:20:27 +1000
From:      Tracy Williams <tracy_sw_au@hotmail.com>
To:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   Help
Message-ID:  <BLU181-W56EC044F98AAEDC01BA9E2A2EF0@phx.gbl>
In-Reply-To: <mailman.2253.1407624924.845.freebsd-questions@freebsd.org>
References:  <mailman.2253.1407624924.845.freebsd-questions@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Could you please unsubscribe me. I tried to do it online but I don't have a=
 clue what my password isThank you
Kind reagrds
Tracy=20

> From: freebsd-questions-request@freebsd.org
> Subject: freebsd-questions Digest=2C Vol 531=2C Issue 10
> To: freebsd-questions@freebsd.org
> Date: Sat=2C 9 Aug 2014 22:55:24 +0000
>=20
> Send freebsd-questions mailing list submissions to
> 	freebsd-questions@freebsd.org
>=20
> To subscribe or unsubscribe via the World Wide Web=2C visit
> 	http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> or=2C via email=2C send a message with subject or body 'help' to
> 	freebsd-questions-request@freebsd.org
>=20
> You can reach the person managing the list at
> 	freebsd-questions-owner@freebsd.org
>=20
> When replying=2C please edit your Subject line so it is more specific
> than "Re: Contents of freebsd-questions digest..."
>=20
>=20
> Today's Topics:
>=20
>    1. install xorg question .... (William A. Mahaffey III)
>    2. ipfw question .... (William A. Mahaffey III)
>    3. Re: ipfw question .... (Matthew Seaman)
>    4. Re: ipfw question .... (Mike Tancsa)
>    5. Re: install xorg question .... (Matthew Seaman)
>    6. Re: ipfw question .... (William A. Mahaffey III)
>    7. Re: install xorg question .... (William A. Mahaffey III)
>    8. ps question .... (William A. Mahaffey III)
>    9. Re: ps question .... (Polytropon)
>   10. Re: Freebsd-update to 9.3 from 9.2 (Victor Sudakov)
>   11. Re: ps question .... (William A. Mahaffey III)
>   12. Re: ps question .... (Polytropon)
>   13. X11 setup .... (William A. Mahaffey III)
>   14. Re: cpio and hard links (Victor Sudakov)
>   15. pkg schema upgrade? (Patrick)
>   16. Re: pkg schema upgrade? (Matthew Seaman)
>   17. Re: X11 setup .... (doug)
>   18. pkg-register question (doug@safeport.com)
>   19. Re: X11 setup .... (William A. Mahaffey III)
>   20. tcsh login question .... (William A. Mahaffey III)
>   21. Re: ipfw question .... (Mike Tancsa)
>   22. Re: pkg-register question (Matthew Seaman)
>   23. Re: tcsh login question .... (kpneal@pobox.com)
>   24. pkg upgrade failed again (Jamie Griffin)
>   25. watchdog timeout msk0 (Martin Smith)
>   26. Re: X11 setup .... (doug)
>   27. Re: pkg-register question (doug)
>   28. Re: Freebsd-update to 9.3 from 9.2 (Andrew Berg)
>   29. seriously hacked off!! Re: pkg upgrade failed again
>       (Jamie Griffin)
>   30. Re: X11 setup .... (William A. Mahaffey III)
>   31. BIOS monitoring goodies .... (William A. Mahaffey III)
>   32. Re: TCP/IP on the way out? (Perry Hutchison)
>   33. Re: X11 setup .... (doug)
>=20
>=20
> ----------------------------------------------------------------------
>=20
> Message: 1
> Date: Sat=2C 09 Aug 2014 09:02:19 -0500
> From: "William A. Mahaffey III" <wam@hiwaay.net>
> To: "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
> Subject: install xorg question ....
> Message-ID: <53E629EB.7050604@hiwaay.net>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
>=20
>=20
> I am rying to install xorg-7.7 under FreeBSD 9.3 apparently needed by=20
> XFCE. I get the following:
>=20
>=20
> [root@kabini1=2C /etc=2C 8:56:00am] 353 % pkg install xorg-7.7
> Updating repository catalogue
> FreeBSD repository is up-to-date
> All repositories are up-to-date
> The following 131 packages will be affected (of 0 checked):
>=20
> New packages to be INSTALLED:
>          xorg: 7.7
>          xorg-libraries: 7.7_1
>              .
>              .
>              .
>          xf86-input-keyboard: 1.8.0_2
>=20
> The process will require 98 MB more space
> 37 MB to be downloaded
>=20
> Proceed with this action [y/N]: y
> Fetching xorg-apps-7.7.txz: 100% of 2 kB
> pkg: xorg-apps-7.7 failed checksum from repository
> [root@kabini1=2C /etc=2C 8:56:19am] 354 %
>=20
>=20
> I had already fetched the 1st part of the list. How do I work around=20
> this :-/ ?
>=20
>=20
> --=20
>=20
> 	William A. Mahaffey III
>=20
>   ----------------------------------------------------------------------
>=20
> 	"The M1 Garand is without doubt the finest implement of war
> 	 ever devised by man."
>                             -- Gen. George S. Patton Jr.
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 2
> Date: Sat=2C 09 Aug 2014 09:15:35 -0500
> From: "William A. Mahaffey III" <wam@hiwaay.net>
> To: "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
> Subject: ipfw question ....
> Message-ID: <53E62D07.2030703@hiwaay.net>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
>=20
>=20
> Why is there a limit on the # of logged denials by ipfw ?
>=20
>=20
> Aug  6 18:52:20 kabini1 kernel: ipfw: limit 500 reached on entry 65500
>=20
>=20
> --=20
>=20
> 	William A. Mahaffey III
>=20
>   ----------------------------------------------------------------------
>=20
> 	"The M1 Garand is without doubt the finest implement of war
> 	 ever devised by man."
>                             -- Gen. George S. Patton Jr.
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 3
> Date: Sat=2C 09 Aug 2014 15:14:56 +0100
> From: Matthew Seaman <matthew@FreeBSD.org>
> To: freebsd-questions@freebsd.org
> Subject: Re: ipfw question ....
> Message-ID: <53E62CE0.6040807@FreeBSD.org>
> Content-Type: text/plain=3B charset=3D"iso-8859-1"
>=20
> On 09/08/2014 15:15=2C William A. Mahaffey III wrote:
> > Why is there a limit on the # of logged denials by ipfw ?
> >=20
> >=20
> > Aug  6 18:52:20 kabini1 kernel: ipfw: limit 500 reached on entry 65500
>=20
> Because otherwise someone could DoS you by causing ipfw to fill up a
> partition with log messages simply by sending a stream of packets at you
> over the network.
>=20
> 	Cheers=2C
>=20
> 	Matthew
>=20
> --=20
> Dr Matthew J Seaman MA=2C D.Phil.
> PGP: http://www.infracaninophile.co.uk/pgpkey
>=20
>=20
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 1036 bytes
> Desc: OpenPGP digital signature
> URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20=
140809/0ab725ef/attachment-0001.sig>
>=20
> ------------------------------
>=20
> Message: 4
> Date: Sat=2C 09 Aug 2014 10:15:10 -0400
> From: Mike Tancsa <mike@sentex.net>
> To: "William A. Mahaffey III" <wam@hiwaay.net>=2C "FreeBSD Questions
> 	!!!!" <freebsd-questions@freebsd.org>
> Subject: Re: ipfw question ....
> Message-ID: <53E62CEE.7060202@sentex.net>
> Content-Type: text/plain=3B charset=3Dwindows-1252=3B format=3Dflowed
>=20
> On 8/9/2014 10:15 AM=2C William A. Mahaffey III wrote:
> >
> >
> > Why is there a limit on the # of logged denials by ipfw ?
>=20
> The limit is there to prevent conditions where syslog would be=20
> overwhelmed with hits=2C as in the case for example of a DoS.  You can=20
> change it as discussed in the man pages
>=20
>=20
> If net.inet.ip.fw.verbose is set to 1=2C packets will be logged to=20
> syslogd(8) with a LOG_SECURITY facility up to a maximum of logamount=20
> packets.  If no logamount is specified=2C the limit is taken from the=20
> sysctl variable net.inet.ip.fw.verbose_limit.  In both cases=2C a value o=
f=20
> 0 means unlimited logging.
>=20
> Once the limit is reached=2C logging can be re-enabled by clearing the=20
> logging counter or the packet counter for that entry=2C see the resetlog=
=20
> command.
>=20
> 	---Mike
>=20
>=20
> --=20
> -------------------
> Mike Tancsa=2C tel +1 519 651 3400
> Sentex Communications=2C mike@sentex.net
> Providing Internet services since 1994 www.sentex.net
> Cambridge=2C Ontario Canada   http://www.tancsa.com/
>=20
>=20
> ------------------------------
>=20
> Message: 5
> Date: Sat=2C 09 Aug 2014 15:26:25 +0100
> From: Matthew Seaman <m.seaman@infracaninophile.co.uk>
> To: freebsd-questions@freebsd.org
> Subject: Re: install xorg question ....
> Message-ID: <53E62F91.8020100@infracaninophile.co.uk>
> Content-Type: text/plain=3B charset=3D"iso-8859-1"
>=20
> On 09/08/2014 15:02=2C William A. Mahaffey III wrote:
> > I am rying to install xorg-7.7 under FreeBSD 9.3 apparently needed by
> > XFCE. I get the following:
>=20
> > [root@kabini1=2C /etc=2C 8:56:00am] 353 % pkg install xorg-7.7
> > Updating repository catalogue
> > FreeBSD repository is up-to-date
> > All repositories are up-to-date
> > The following 131 packages will be affected (of 0 checked):
> >=20
> > New packages to be INSTALLED:
> >         xorg: 7.7
> >         xorg-libraries: 7.7_1
> >             .
> >             .
> >             .
> >         xf86-input-keyboard: 1.8.0_2
> >=20
> > The process will require 98 MB more space
> > 37 MB to be downloaded
> >=20
> > Proceed with this action [y/N]: y
> > Fetching xorg-apps-7.7.txz: 100% of 2 kB
> > pkg: xorg-apps-7.7 failed checksum from repository
> > [root@kabini1=2C /etc=2C 8:56:19am] 354 %
> >=20
> >=20
> > I had already fetched the 1st part of the list. How do I work around
> > this :-/ ?
>=20
> This is quite possibly a bug that occurs when upgrading from pkg-1.2.7
> to pkg-1.3.5.1.  The solution is to run:
>=20
>    # pkg clean -a
>    # pkg update -f
>=20
> That will delete everything you've got in your package cache and force
> pkg to refetch all the catalogues from the repositories you're using.
>=20
> Oh -- depending on your hardware=2C you might want to use the new-xorg
> repository.  See
>=20
>   https://wiki.freebsd.org/Graphics
>   https://wiki.freebsd.org/Graphics/WITH_NEW_XORG
>   http://daemon-notes.com/articles/desktop/kde
>=20
> 	Cheers=2C
>=20
> 	Matthew
>=20
> --=20
> Dr Matthew J Seaman MA=2C D.Phil.
>=20
> PGP: http://www.infracaninophile.co.uk/pgpkey
> JID: matthew@infracaninophile.co.uk
>=20
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 1036 bytes
> Desc: OpenPGP digital signature
> URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20=
140809/c4c23b72/attachment-0001.sig>
>=20
> ------------------------------
>=20
> Message: 6
> Date: Sat=2C 09 Aug 2014 09:39:15 -0500
> From: "William A. Mahaffey III" <wam@hiwaay.net>
> To: "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
> Subject: Re: ipfw question ....
> Message-ID: <53E63293.3090901@hiwaay.net>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
> On 08/09/14 09:15=2C Mike Tancsa wrote:
> > On 8/9/2014 10:15 AM=2C William A. Mahaffey III wrote:
> >>
> >>
> >> Why is there a limit on the # of logged denials by ipfw ?
> >
> > The limit is there to prevent conditions where syslog would be=20
> > overwhelmed with hits=2C as in the case for example of a DoS.  You can=
=20
> > change it as discussed in the man pages
> >
> >
> > If net.inet.ip.fw.verbose is set to 1=2C packets will be logged to=20
> > syslogd(8) with a LOG_SECURITY facility up to a maximum of logamount=20
> > packets.  If no logamount is specified=2C the limit is taken from the=20
> > sysctl variable net.inet.ip.fw.verbose_limit.  In both cases=2C a value=
=20
> > of 0 means unlimited logging.
> >
> > Once the limit is reached=2C logging can be re-enabled by clearing the=
=20
> > logging counter or the packet counter for that entry=2C see the resetlo=
g=20
> > command.
> >
> >     ---Mike
> >
> >
>=20
>=20
> Hmmmm .... OK=2C sounds good. I would like a bit more granularity on=20
> deciding what to log & what to not log. For example=2C 99% of the time=2C=
 I=20
> would drop denials from my LAN=2C except when I am trying to figure out=20
> why I can't get NFS working=2C for example. I'd like to be able to choose=
=20
> that when I (re)start ipfw. I am using the default rc.firewall located=20
> in /etc=2C BTW. I might like to specify denial-logging by protocol *and*=
=20
> port #=2C rather than just por
> t # .... Is there a way to implement any of=20
> this ? Thanks & TIA ....
>=20
> --=20
>=20
> 	William A. Mahaffey III
>=20
>   ----------------------------------------------------------------------
>=20
> 	"The M1 Garand is without doubt the finest implement of war
> 	 ever devised by man."
>                             -- Gen. George S. Patton Jr.
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 7
> Date: Sat=2C 09 Aug 2014 09:47:55 -0500
> Fro
> m: "William A. Mahaffey III" <wam@hiwaay.net>
> To: freebsd-questions@freebsd.org
> Subject: Re: install xorg question ....
> Message-ID: <53E6349B.7070900@hiwaay.net>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
> On 08/09/14 09:26=2C Matthew Seaman wrote:
> > On 09/08/2014 15:02=2C William A. Mahaffey III wrote:
> >> I am rying to install xorg-7.7 under FreeBSD 9.3 apparently needed by
> >> XFCE. I get the following:
> >> [root@kabini1=2C /etc=2C 8:56:00am] 353 % pkg install xorg-7.7
> >> Updating repository catalogue
> >> FreeBSD repository is up-to-date
> >> All repositories are up-to-date
> >> The following 131 packages will be affected (of 0 checked):
> >>
> >> New packages to be INSTALLED:
> >>          xorg: 7.7
> >>          xorg-libraries: 7.7_1
> >>              .
> >>              .
> >>              .
> >>          xf86-input-keyboard: 1.8.0_2
> >>
> >> The process will require 98 MB more space
> >> 37 MB to be downloaded
> >>
> >> Proceed with this action [y/N]: y
> >> Fetching xorg-apps-7.7.txz: 100% of 2 kB
> >> pkg: xorg-apps-7.7 failed checksum from repository
> >> [root@kabini1=2C /etc=2C 8:56:19am] 354 %
> >>
> >>
> >> I had already fetched the 1st part of the list. How do I work around
> >> this :-/ ?
> > This is quite possibly a bug that occurs when upgrading from pkg-1.2.7
> > to pkg-1.3.5.1.  The solution is to run:
> >
> >     # pkg clean -a
> >     # pkg update -f
> >
> > That will delete everything you've got in your package cache and force
> > pkg to refetch all the catalogues from the repositories you're using.
> >
> > Oh -- depending on your hardware=2C you might want to use the new-xorg
> > repository.  See
> >
> >    https://wiki.freebsd.org/Graphics
> >    https://wiki.freebsd.org/Graphics/WITH_NEW_XORG
> >    http://daemon-notes.com/articles/desktop/kde
> >
> > 	Cheers=2C
> >
> > 	Mat
> thew
> >
>=20
>=20
> Thanks=2C worked like a champ !!!!!
>=20
>=20
> --=20
>=20
> 	William A. Mahaffey III
>=20
>   ----------------------------------------------------------------------
>=20
> 	"The M1 Garand is without doubt the finest implement of war
> 	 ever devised by man."
>                             -- Gen. George S. Patton Jr.
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 8
> Date: Sat=2C 09 Aug 2014 10:01:00 -0500
> From: "William A. Mahaffey III" <wam@hiwaay.net>
> To: "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
> Subject: ps question ....
> Message-ID: <53E637AC.3010008@hiwaay.net>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
>=20
>=20
> .... is there a way to get ps to show me *everything* running ? 'ps=20
> -elf' works nicely under Fedora 14 ....
>=20
>=20
> --=20
>=20
> 	William A. Mahaffey III
>=20
>   ----------------------------------------------------------------------
>=20
> 	"The M1 Garand is without doubt the finest implement of war
> 	 ever devised by man."
>                             -- Gen. George S. Patton Jr.
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 9
> Date: Sat=2C 9 Aug 2014 17:01:50 +0200
> From: Polytropon <freebsd@edvax.de>
> To: "William A. Mahaffey III" <wam@hiwaay.net>
> Cc: FreeBSD Questions !!!! <freebsd-questions@freebsd.org>
> Subject: Re: ps question ....
> Message-ID: <20140809170150.0b1c9486.freebsd@edvax.de>
> Content-Type: text/plain=3B charset=3DUS-ASCII
>=20
> On Sat=2C 09 Aug 2014 10:01:00 -0500=2C William A. Mahaffey III wrote:
> >=20
> >=20
> > .... is there a way to get ps to show me *everything* running ? 'ps=20
> > -elf' works nicely under Fedora 14 ....
>=20
> What about "ps aux"? See "man ps" for details.
>=20
>=20
>=20
> --=20
> Polytropon
> Magdeburg=2C Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe=2C Mousa=2C ...
>=20
>=20
> ------------------------------
>=20
> Message: 10
> Date: Sat=2C 9 Aug 2014 22:08:16 +0700
> From: Victor Sudakov <vas@mpeks.tomsk.su>
> To: freebsd-questions@freebsd.org
> Subject: Re: Freebsd-update to 9.3 from 9.2
> Message-ID: <20140809150815.GA65785@admin.sibptus.tomsk.ru>
> Content-Type: text/plain=3B charset=3Dus-ascii
>=20
> Andrew Berg wrote:
> > The best thing to do since you need to build world and kernel is to
> > just use svn and do all updates via source. freebsd-update does
> > nothing for you. Grab a completely new copy of the 9.3 source with
> > svn and then build and install it.
>=20
> Would it be safe to use freebsd-update to install binary security patches
> after upgrading a system from source?
>=20
>=20
> --=20
> Victor Sudakov=2C  VAS4-RIPE=2C VAS47-RIPN
> sip:sudakov@sibptus.tomsk.ru
>=20
>=20
> ------------------------------
>=20
> Message: 11
> Date: Sat=2C 09 Aug 2014 10:18:08 -0500
> From: "William A. Mahaffey III" <wam@hiwaay.net>
> To: "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
> Subject: Re: ps question ....
> Message-ID: <53E63BB0.2080700@hiwaay.net>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
> On 08/09/14 10:01=2C Polytropon wrote:
> > On Sat=2C 09 Aug 2014 10:01:00 -0500=2C William A. Mahaffey III wrote:
> >>
> >> .... is there a way to get ps to show me *everything* running ? 'ps
> >> -elf' works nicely under Fedora 14 ....
> > What about "ps aux"? See "man ps" for details.
> >
> >
> >
>=20
>=20
> Thanks=2C I forgot about the different behavior w/ & w/o the minus sign=20
> :-/ ....
>=20
> --=20
>=20
> 	William A. Mahaffey III
>=20
>   ----------------------------------------------------------------------
>=20
> 	"The M1 Garand is without doubt the finest implement of war
> 	 ever devised by man."
>                             -- Gen. George S. Patton Jr.
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 12
> Date: Sat=2C 9 Aug 2014 17:22:39 +0200
> From: Polytropon <freebsd@edvax.de>
> To: "William A. Mahaffey III" <wam@hiwaay.net>
> Cc: FreeBSD Questions !!!! <freebsd-questions@freebsd.org>
> Subject: Re: ps question ....
> Message-ID: <20140809172239.ae877c88.freebsd@edvax.de>
> Content-Type: text/plain=3B charset=3DUS-ASCII
>=20
> On Sat=2C 09 Aug 2014 10:18:08 -0500=2C William A. Mahaffey III wrote:
> > On 08/09/14 10:01=2C Polytropon wrote:
> > > On Sat=2C 09 Aug 2014 10:01:00 -0500=2C William A. Mahaffey III wrote=
:
> > >>
> > >> .... is there a way to get ps to show me *everything* running ? 'ps
> > >> -elf' works nicely under Fedora 14 ....
> > > What about "ps aux"? See "man ps" for details.
> > >
> > >
> > >
> >=20
> >=20
> > Thanks=2C I forgot about the different behavior w/ & w/o the minus sign=
=20
> > :-/ ....
>=20
> As far as I can tell=2C there is no difference in behaviour.
> The commands
>=20
> 	% ps aux
>=20
> and
>=20
> 	% ps -aux
>=20
> as well as
>=20
> 	% ps -a -u -x
>=20
> produce the same output.
>=20
>=20
>=20
> --=20
> Polytropon
> Magdeburg=2C Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe=2C Mousa=2C ...
>=20
>=20
> ------------------------------
>=20
> Message: 13
> Date: Sat=2C 09 Aug 2014 10:44:03 -0500
> From: "William A. Mahaffey III" <wam@hiwaay.net>
> To: "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
> Subject: X11 setup ....
> Message-ID: <53E641C3.4040409@hiwaay.net>
> Content-Type: text/plain=3B charset=3D"ISO-8859-1"
>=20
>    .... I am following the instructions at
>    [1]http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.=
h
>    tml to get my newly installed xorg setup. I stepped through everything
>    up to the 'Xorg -config xorg.conf.new -retro' which didn't fail=2C bit
>    didn't behave quite like it was supposed to .... Machine is AMD Jaguar
>    Kabini based=2C quad core=2C 1.3 GHz=2C 25W=2C gfx on die:
>    Aug  9 10:23:34 kabini1 kernel: CPU: AMD Sempron(tm) 3850 APU with
>    Radeon(tm) R3     (1297.59-MHz K8-class CPU)
>    xorg detects it as: BoardName   "Kabini [Radeon HD 8280 / R3 Series]"
>    The above test is supposed to give a black & grey grid on the screen=
=2C
>    w/ an X-mouse. I have the mouse=2C & it moves around=2C although
>    click-&-drag does nothing=2C & I might have the grid=2C although it is
>    pixel-by-pixel=2C not finitely sized grid .... The troubleshooting pag=
e
>    is little help .... Am I good to go or not :-/ ? TIA ....
> --
>=20
>         William A. Mahaffey III
>=20
>  ----------------------------------------------------------------------
>=20
>         "The M1 Garand is without doubt the finest implement of war
>          ever devised by man."
>                            -- Gen. George S. Patton Jr.
>=20
> References
>=20
>    1. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.=
html
>=20
>=20
> ------------------------------
>=20
> Message: 14
> Date: Sat=2C 9 Aug 2014 23:17:45 +0700
> From: Victor Sudakov <vas@mpeks.tomsk.su>
> To: freebsd-questions@freebsd.org
> Subject: Re: cpio and hard links
> Message-ID: <20140809161745.GB65785@admin.sibptus.tomsk.ru>
> Content-Type: text/plain=3B charset=3Dus-ascii
>=20
> Ronald F. Guilmette wrote:
> >=20
> >=20
> > Given a directory "tmp" which contains two files=2C "foo" and "bar"=2C
> > both of which are merely hard links to one another=2C the following
> > command will=2C apparently=2C produce an archive of the directory in
> > question which contains only a single instance of the actual file
> > contents:
> >=20
> > 	tar cvf tmp.tar tmp
> >=20
> > The resulting tmp.tar file can later be unpacked=2C using tar=2C result=
ing
> > in a directory structure which exactly mirrors the original "tmp"
> > directory=2C including preservation of the hard link(s).
> >=20
> > I note however that=2C given the same original directory structure=2C t=
he
> > following command generates an archive file containing two complete
> > instances of the file data:
> >=20
> > 	find tmp -depth -print | cpio -ovm > tmp.cpio
> >=20
> > For the the cpio program that is part of FreeBSD=2C is there any option
> > which would have the effect of causing cpio to only archive a single
> > instance of the data associated with each unique inode... as tar appare=
ntly
> > does=2C by default?
>=20
> Try 'cpio -H ustar'.
>=20
>=20
> --=20
> Victor Sudakov=2C  VAS4-RIPE=2C VAS47-RIPN
> sip:sudakov@sibptus.tomsk.ru
>=20
>=20
> ------------------------------
>=20
> Message: 15
> Date: Sat=2C 9 Aug 2014 09:21:30 -0700
> From: Patrick <gibblertron@gmail.com>
> To: FreeBSD Questions <questions@freebsd.org>
> Subject: pkg schema upgrade?
> Message-ID:
> 	<CA+dWbmYd1=3D6pu8-BGhSYg66thLm4HNai6t=3DgpJRDGv16B8nC2A@mail.gmail.com>
> Content-Type: text/plain=3B charset=3DUTF-8
>=20
> I'm getting the following warning/error with pkg on FreeBSD 10 (since it
> self-updated to 1.3.5.1:
>=20
>=20
> pkg: Repo FreeBSD needs schema upgrade from 2006 to 2010 but it is opened
> readonly
>=20
> pkg: need to re-create repo FreeBSD to upgrade schema version
>=20
>=20
> It sure would be nice if in addition to saying what needs to happ
> en=2C it
> said how to make it happen. I don't see anything in the man page that tal=
ks
> about this=2C and my Google-fu is failing me.
>=20
>=20
> ------------------------------
>=20
> Message: 16
> Date: Sat=2C 09 Aug 2014 17:42:54 +0100
> From: Matthew Seaman <matthew@FreeBSD.org>
> To: freebsd-questions@freebsd.org
> Subject: Re: pkg schema upgrade?
> Message-ID: <53E64F8E.7080401@FreeBSD.org>
> Content-Type: text/plain=3B charset=3D"iso-8859-1"
>=20
> On 09/08/2014 17:21=2C Patrick wrote:
> > I'm getting the following warning/error with pkg on FreeBSD 10 (since i=
t
> > self-updated to 1.3.5.1:
> >=20
> >=20
> > pkg: Repo FreeBSD needs schema upgrade from 2006 to 2010 but it is open=
ed
> > readonly
> >=20
> > pkg: need to re-create repo FreeBSD to upgrade schema version
> >=20
> >=20
> > It sure would be nice if in addition to saying what needs to happen=2C =
it
> > said how to make it happen. I don't see anything in the man page that t=
alks
> > about this=2C and my Google-fu is failing me.
>=20
>   # pkg clean -a
>   # pkg update -f
>=20
> should restore sanity.
>=20
> 	Cheers=2C
>=20
> 	Matthew
>=20
> --=20
> Dr Matthew J Seaman MA=2C D.Phil.
> PGP: http://www.infracaninophile.co.uk/pgpkey
>=20
>=20
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 1036 bytes
> Desc: OpenPGP digital signature
> URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20=
140809/57f76afc/attachment-0001.sig>
>=20
> ------------------------------
>=20
> Messa
> ge: 17
> Date: Sat=2C 9 Aug 2014 13:03:20 -0400 (EDT)
> From: doug <doug@fledge.watson.org>
> To: "William A. Mahaffey III" <wam@hiwaay.net>
> Cc: FreeBSD Questions !!!! <freebsd-questions@freebsd.org>
> Subject: Re: X11 setup ....
> Message-ID: <alpine.BSF.2.11.1408091258160.96880@fledge.watson.org>
> Content-Type: TEXT/PLAIN=3B charset=3DUS-ASCII=3B format=3Dflowed
>=20
> On Sat=2C 9 Aug 2014=2C William A. Mahaffey III wrote:
>=20
> >   .... I am following the instructions at
> >   [1]http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config=
.h
> >   tml to get my newly installed xorg setup. I stepped through everythin=
g
> >   up to the 'Xorg -config xorg.conf.new -retro' which didn't fail=2C bi=
t
> >   didn't behave quite like it was supposed to .... Machine is AMD Jagua=
r
> >   Kabini based=2C quad core=2C 1.3 GHz=2C 25W=2C gfx on die:
> >   Aug  9 10:23:34 kabini1 kernel: CPU: AMD Sempron(tm) 3850 APU with
> >   Radeon(tm) R3     (1297.59-MHz K8-class CPU)
> >   xorg detects it as: BoardName   "Kabini [Radeon HD 8280 / R3 Series]"
> >   The above test is supposed to give a black & grey grid on the screen=
=2C
> >   w/ an X-mouse. I have the mouse=2C & it moves around=2C although
> >   click-&-drag does nothing=2C & I might have the grid=2C although it i=
s
> >   pixel-by-pixel=2C not finitely sized grid .... The troubleshooting pa=
ge
> >   is little help .... Am I good to go or not :-/ ? TIA ....
> > --
> Look in /var/log/Xorg.0.log. Errors are somewhat esoteric unless you know=
 a lot=20
> about X11 but they are clearly marked. You can subscribe to the X11 maili=
ng list=20
> or just search the archives of that list.
>=20
> You can see if you are good to go by trying startx.
>=20
>=20
> ------------------------------
>=20
> Message: 18
> Date: Sat=2C 9 Aug 2014 13:39:42 -0400 (EDT)
> From: doug@safeport.com
> To: freebsd-questions@FreeBSD.ORG
> Subject: pkg-register question
> Message-ID:
> 	<alpine.BSF.2.00.1408091325180.41601@bucksport.safeport.com>
> Content-Type: TEXT/PLAIN=3B format=3Dflowed=3B charset=3DUS-ASCII
>=20
> I think this was a user error. I have been making & killing systems (vmwa=
re is=20
> cool) to figure out pkg and how to use freebsd-update to update jails. So=
 I am=20
> fuzzy on things I did not actually document along the way.
>=20
> Anyway I was checking a system that had pkg=2C subversion=2C and ezjail. =
All were=20
> registered except ezjail. I could tell from /usr/ports that I had build i=
t so I=20
> must have done so before adding 'WITH_PKGNG=3Dyes' to make.conf.
>=20
> I assumed one would fix this with 'pkg register' but after man and google=
 I=20
> decided to use 'pkg check -r -v -a'. This [seemingly] worked.
>=20
> The logical thing would seem to be 'pkg register -x ezjail'. Except no su=
ch=20
> syntax exists. Does 'pkg register metadatafile' mean use the full name?
>=20
> _____
> Douglas Denault
> http://www.safeport.com
> doug@safeport.com
> Voice: 301-217-9220
>    Fax: 301-217-9277
>=20
>=20
> ------------------------------
>=20
> Message: 19
> Date: Sat=2C 09 Aug 2014 13:22:40 -0500
> From: "William A. Mahaffey III" <wam@hiwaay.net>
> To: "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
> Subject: Re: X11 setup ....
> Message-ID: <53E666F0.809@hiwaay.net>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
> On 08/09/14 12:03=2C doug wrote:
> > On Sat=2C 9 Aug 2014=2C William A. Mahaffey III wrote:
> >
> >>   .... I am following the instructions at
> >> [1]http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.=
h
> >>   tml to get my newly installed xorg setup. I stepped through everythi=
ng
> >>   up to the 'Xorg -config xorg.conf.new -retro' which didn't fail=2C b=
it
> >>   didn't behave quite like it was supposed to .... Machine is AMD Jagu=
ar
> >>   Kabini based=2C quad core=2C 1.3 GHz=2C 25W=2C gfx on die:
> >>   Aug  9 10:23:34 kabini1 kernel: CPU: AMD Sempron(tm) 3850 APU with
> >>   Radeon(tm) R3     (1297.59-MHz K8-class CPU)
> >>   xorg detects it as: BoardName   "Kabini [Radeon HD 8280 / R3 Series]=
"
> >>   The above test is supposed to give a black & grey grid on the screen=
=2C
> >>   w/ an X-mouse. I have the mouse=2C & it moves around=2C although
> >>   click-&-drag does nothing=2C & I might have the grid=2C although it =
is
> >>   pixel-by-pixel=2C not finitely sized grid .... The troubleshooting p=
age
> >>   is little help .... Am I good to go or not :-/ ? TIA ....
> >> --=20
> > Look in /var/log/Xorg.0.log. Errors are somewhat esoteric unless you=20
> > know a lot about X11 but they are clearly marked. You can subscribe to=
=20
> > the X11 mailing list or just search the archives of that list.
> >
> > You can see if you are good to go by trying startx.
> >
>=20
>=20
> Thanks. My question was poorly articulated=2C should have been 'am I OK=20
> for XFCE ?' .... I plunged on & started XFCE=2C & it works mostly pretty=
=20
> good=2C but the gfx is definitely spotty=2C lotta flickering=2C backgroun=
d on=20
> desktop looks a bit dicey=2C window frames are granular & flickery. I jus=
t=20
> looked through /var/log/Xorg.0.log & there are *no* errors (no '(EE)'s)=20
> .... what now :-/ ....
>=20
> --=20
>=20
> 	William A. Mahaffey III
>=20
>   ----------------------------------------------------------------------
>=20
> 	"The M1 Garand is without doubt the finest implement of war
> 	 ever devised by man."
>                             -- Gen. George S. Patton Jr.
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 20
> Date: Sat=2C 09 Aug 2014 13:27:12 -0500
> From: "William A. Mahaffey III" <wam@hiwaay.net>
> To: "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
> Subject: tcsh login question ....
> Message-ID: <53E66800.8000005@hiwaay.net>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
>=20
>=20
> .... when I shell into my newly minted FreeBSD 9.3 desktop=2C or login w/=
=20
> a console login=2C everything under tcsh gets initialized AOK. I then=20
> activated xdm to manage logins (I like it that way)=2C the /ect/csh.login=
=20
> file clearly does  *not* get sourced. I have many aliases=2C prompt=20
> setting=2C & other goodies which are absent. The tcsh manpage clearly say=
s=20
> it will be sourced at login=2C what gives ?
>=20
>=20
> --=20
>=20
> 	William A. Mahaffey III
>=20
>   ----------------------------------------------------------------------
>=20
> 	"The M1 Garand is without doubt the finest implement of war
> 	 ever devised by man."
>                             -- Gen. George S. Patton Jr.
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 21
> Date: Sat=2C 09 Aug 2014 14:26:26 -0400
> From: Mike Tancsa <mike@sentex.net>
> To: "William A. Mahaffey III" <wam@hiwaay.net>=2C "FreeBSD Questions
> 	!!!!" <freebsd-questions@freebsd.org>
> Subject: Re: ipfw question ....
> Message-ID: <53E667D2.7070601@sentex.net>
> Content-Type: text/plain=3B charset=3Dwindows-1252=3B format=3Dflowed
>=20
> On 8/9/2014 10:39 AM=2C William A. Mahaffey III wrote:
> >>
> >>
> >> If net.inet.ip.fw.verbose is set to 1=2C p
> ackets will be logged to
> >> syslogd(8) with a LOG_SECURITY facility up to a maximum of logamount
> >> packets.  If no logamount is specified=2C the limit is taken from the
> >> sysctl variable net.inet.ip.fw.verbose_limit.  In both cases=2C a valu=
e
> >> of 0 means unlimited logging.
> >>
> >> Once the limit is reached=2C logging can be re-enabled by clearing the
> >> logging counter or the packet counter for that entry=2C see the resetl=
og
> >> command.
> >>
> >>     ---Mike
> >>
> >>
> >
> >
> > port #=2C rather than just port # .... Is there a way to implement any =
of
> > this ? Thanks & TIA ....
>=20
>=20
> It there in the man pages of ipfw how to do it on a per rule basis.=20
> logamount can be set on a per rule basis.
>=20
> 	---Mike
>=20
>=20
> --=20
> -------------------
> Mike Tancsa=2C tel +1 519 651 3400
> Sentex Communications=2C mike@sentex.net
> Providing Internet services since 1994 www.sentex.net
> Cambridge=2C Ontario Canada   http://www.tancsa.com/
>=20
>=20
> ------------------------------
>=20
> Message: 22
> Date: Sat=2C 09 Aug 2014 19:39:32 +0100
> From: Matthew Seaman <m.seaman@infracaninophile.co.uk>
> To: freebsd-questions@freebsd.org
> Subject: Re: pkg-register question
> Message-ID: <53E66AE4.7040004@infracaninophile.co.uk>
> Content-Type: text/plain=3B charset=3D"iso-8859-1"
>=20
> On 09/08/2014 18:39=2C doug@safeport.com wrote:
> > I think this was a user error. I have been making & killing systems
> > (vmware is cool) to figure out pkg and how to use freebsd-update to
> > update jails. So I am fuzzy on things I did not actually document along
> > the way.
> >=20
> > Anyway I was checking a system that had pkg=2C subversion=2C and ezjail=
. All
> > were registered except ezjail. I could tell from /usr/ports that I had
> > build it so I must have done so before adding 'WITH_PKGNG=3Dyes' to
> > make.conf.
> >=20
> > I assumed one would fix this with 'pkg register' but after man and
> > google I decided to use 'pkg check -r -v -a'. This [seemingly] worked.
> >
> > The logical thing would seem to be 'pkg register -x ezjail'. Except no
> > such syntax exists. Does 'pkg register metadatafile' mean use the full
> > name?
>=20
> That's not really the intended use for pkg-register.  It takes a
> previously written +MANIFEST which describes some software that has
> already been installed on a system and inserts the data from the
> +MANIFEST plus checksums etc it calculates from the installed files into
> the package database.  The +MANIFEST is the 'metadatafile' the man page
> is talking about.
>=20
> Before staging=2C this was the way the ports operated.  Now=2C with stagi=
ng=2C
> you use the very similar pkg-create to build a package from the staging
> area=2C and then simply install that package.  Not sure what the long ter=
m
> plans are for 'pkg register' but making it obsolete in the future
> probably should not be discounted.
>=20
> What you probably wanted was 'pkg convert' -- or in fact=2C the pkg2ng
> script which is basically a wrapper around pkg convert.
>=20
> 	Cheers=2C
>=20
> 	Matthew
>=20
> --=20
> Dr Matthew J Seaman MA=2C D.Phil.
>=20
> PGP: http://www.infracaninophile.co.uk/pgpkey
> JID: matthew@infracaninophile.co.uk
>=20
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 1036 bytes
> Desc: OpenPGP digital signature
> URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20=
140809/3923f551/attachment-0001.sig>
>=20
> ------------------------------
>=20
> Message: 23
> Date: Sat=2C 9 Aug 2014 15:43:02 -0400
> From: kpneal@pobox.com
> To: "William A. Mahaffey III" <wam@hiwaay.net>
> Cc: FreeBSD Questions !!!! <freebsd-questions@freebsd.org>
> Subject: Re: tcsh login question ....
> Message-ID: <20140809194302.GA62677@neutralgood.org>
> Content-Type: text/plain=3B charset=3Dus-ascii
>=20
> On Sat=2C Aug 09=2C 2014 at 01:27:12PM -0500=2C William A. Mahaffey III w=
rote:
> >=20
> >=20
> > .... when I shell into my newly minted FreeBSD 9.3 desktop=2C or login =
w/=20
> > a console login=2C everything under tcsh gets initialized AOK. I then=20
> > activated xdm to manage logins (I like it that way)=2C the /ect/csh.log=
in=20
> > file clearly does  *not* get sourced. I have many aliases=2C prompt=20
> > setting=2C & other goodies which are absent. The tcsh manpage clearly s=
ays=20
> > it will be sourced at login=2C what gives ?
>=20
> That file doesn't get sourced because tcsh is not run as a "login shell"
> when run from whatever that gets run by xdm. This is correct since loggin=
g
> into an X11 session is not the same as logging into a shell session.
>=20
> It sounds like you need to move a good chunk of your /etc/csh.login file
> into the /etc/csh.cshrc file instead.
> --=20
> Kevin P. Neal                                http://www.pobox.com/~kpn/
>=20
> "Nonbelievers found it difficult to defend their position in \=20
>     the presense of a working computer." -- a DEC Jensen paper
>=20
>=20
> ------------------------------
>=20
> Message: 24
> Date: Sat=2C 09 Aug 2014 20:48:31 +0100
> From: Jamie Griffin <griffin8j@gmail.com>
> To: FreeBSD Questions <freebsd-questions@freebsd.org>
> Subject: pkg upgrade failed again
> Message-ID: <53E67B0F.2010500@gmail.com>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
> Just waited 9 hours for all the new packages to download to find this=20
> happens:
>=20
> Checking for upgrades: 100%
> Assertion failed: (var =3D=3D elt->var)=2C function pkg_solve_sat_problem=
=2C=20
> file pkg_solve.c=2C line 508.
> Child process pid=3D5148 terminated abnormally: Abort trap
>=20
> When with a problematic package qt4-qtestlib conflicting with=20
> qt4-testlib=2C pkg upgraded itself to 1.3.3 first=2C I thought the solver=
=20
> was supposed to sort things like this?
>=20
>=20
> ------------------------------
>=20
> Message: 25
> Date: Sat=2C 09 Aug 2014 20:55:36 +0100
> From: Martin Smith <lists@rakupottery.org.uk>
> To: questions@freebsd.org
> Subject: watchdog timeout msk0
> Message-ID: <53E67CB8.5050000@rakupottery.org.uk>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
> I am just installing 10.0 onto a Vaio VGN-SR41N and am getting watchdog=20
> timeout on the built in msk0=2C the system does not seem to recognise an=
=20
> expresscard startech EC1000S which has a realtek chip.
> I remember the watchdog timeout from years ago on
>  older systems=2C though=20
> not on this machine=2C can someone remind me and point me in the right=20
> direction=2C cheers
>=20
> --=20
> Martin
>=20
>=20
> ------------------------------
>=20
> Message: 26
> Date: Sat=2C 9 Aug 2014 16:37:55 -0400 (EDT)
> From: doug <doug@fledge.watson.org>
> To: "William A. Mahaffey III" <wam@hiwaay.net>
> Cc: FreeBSD Questions !!!! <freebsd-questions@freebsd.org>
> Subject: Re: X11 setup ....
> Message-ID: <alpine.BSF.2.11.1408091628040.96880@fledge.watson.org>
> Content-Type: TEXT/PLAIN=3B charset=3DUS-ASCII=3B format=3Dflowed
>=20
> On Sat=2C 9 Aug 2014=2C William A. Mahaffey III wrote:
>=20
> > On 08/09/14 12:03=2C doug wrote:
> >> On Sat=2C 9 Aug 2014=2C William A. Mahaffey III wrote:
> >>
> >>>   .... I am following the instructions at
> >>> [1]http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config=
.h
> >>>   tml to get my newly installed xorg setup. I stepped through everyth=
ing
> >>>   up to the 'Xorg -config xorg.conf.new -retro' which didn't fail=2C =
bit
> >>>   didn't behave quite like it was supposed to .... Machine is AMD Jag=
uar
> >>>   Kabini based=2C quad core=2C 1.3 GHz=2C 25W=2C gfx on die:
> >>>   Aug  9 10:23:34 kabini1 kernel: CPU: AMD Sempron(tm) 3850 APU with
> >>>   Radeon(tm) R3     (1297.59-MHz K8-class CPU)
> >>>   xorg detects it as: BoardName   "Kabini [Radeon HD 8280 / R3 Series=
]"
> >>>   The above test is supposed to give a black & grey grid on the scree=
n=2C
> >>>   w/ an X-mouse. I have the mouse=2C & it moves around=2C although
> >>>   click-&-drag does nothing=2C & I might have the grid=2C although it=
 is
> >>>   pixel-by-pixel=2C not finitely sized grid .... The troubleshooting =
page
> >>>   is little help .... Am I good to go or not :-/ ? TIA ....
> >>> --=20
> >> Look in /var/log/Xorg.0.log. Errors are somewhat esoteric unless you k=
now a=20
> >> lot about X11 but they are clearly marked. You can subscribe to the X1=
1=20
> >> mailing list or just search the archives of that list.
> >>=20
> >> You can see if you are good to go by trying startx.
> >
> > Thanks. My question was poorly articulated=2C should have been 'am I OK=
 for=20
> > XFCE ?' .... I plunged on & started XFCE=2C & it works mostly pretty go=
od=2C but=20
> > the gfx is definitely spotty=2C lotta flickering=2C background on deskt=
op looks a=20
> > bit dicey=2C window frames are granular & flickery. I just looked throu=
gh=20
> > /var/log/Xorg.0.log & there are *no* errors (no '(EE)'s) .... what now =
:-/=20
> > ....
> Ah - my desktop of choice. The X11 list might help. I excel at choosing P=
Cs=20
> whose video card are not supported. However flickering and worse in my=20
> experience has meant driver errors. Have you tried the vesa driver? You w=
ill not=20
> get the full use of the card but if that driver does not work it may mean=
=20
> hardware issues. If you have a windows partition=2C it is good to test th=
e=20
> hardware.
>=20
> I am afraid this one is above my pay grade :(
>=20
>=20
> ------------------------------
>=20
> Message: 27
> Date: Sat=2C 9 Aug 2014 16:46:57 -0400 (EDT)
> From: doug <doug@fledge.watson.org>
> To: Matthew Seaman <m.seaman@infracaninophile.co.uk>
> Cc: freebsd-questions@freebsd.org
> Subject: Re: pkg-register question
> Message-ID: <alpine.BSF.2.11.1408091638580.96880@fledge.watson.org>
> Content-Type: TEXT/PLAIN=3B charset=3DUS-ASCII=3B format=3Dflowed
>=20
> On Sat=2C 9 Aug 2014=2C Matthew Seaman wrote:
> [cut]
> > That's not really the intended use for pkg-register.  It takes a
> > previously written +MANIFEST which describes some software that has
> > already been installed on a system and inserts the data from the
> > +MANIFEST plus checksums etc it calculates from the installed files int=
o
> > the package database.  The +MANIFEST is the 'metadatafile' the man page
> > is talking about.
> >
> > Before staging=2C this was the way the ports operated.  Now=2C with sta=
ging=2C
> > you use the very similar pkg-create to build a package from the staging
> > area=2C and then simply install that package.  Not sure what the long t=
erm
> > plans are for 'pkg register' but making it obsolete in the future
> > probably should not be discounted.
>=20
> Thank you that was exactly the information I was seeking
>=20
> > What you probably wanted was 'pkg convert' -- or in fact=2C the pkg2ng
> > script which is basically a wrapper around pkg convert.
>=20
> Excellent - thanks again
>=20
>=20
> ------------------------------
>=20
> Message: 28
> Date: Sat=2C 9 Aug 2014 16:00:00 -0500
> From: Andrew Berg <aberg010@my.hennepintech.edu>
> To: <freebsd-questions@freebsd.org>
> Subject: Re: Freebsd-update to 9.3 from 9.2
> Message-ID: <53E68BD0.5090209@my.hennepintech.edu>
> Content-Type: text/plain=3B charset=3D"UTF-8"
>=20
> On 2014.08.09 10:08=2C Victor Sudakov wrote:
> > Andrew Berg wrote:
> >> The best thing to do since you need to build world and kernel is to
> >> just use svn and do all updates via source. freebsd-update does
> >> nothing for you. Grab a completely new copy of the 9.3 source with
> >> svn and then build and install it.
> >=20
> > Would it be safe to use freebsd-update to install binary security patch=
es
> > after upgrading a system from source?
> Since you have your own changes=2C no. IIRC=2C there are instructions in =
the
> announcements for building only what has changed so that you do not need =
to
> rebuild the entire world and kernel.
>=20
>=20
> ------------------------------
>=20
> Message: 29
> Date: Sat=2C 09 Aug 2014 22:12:47 +0100
> From: Jamie Griffin <griffin8j@gmail.com>
> To: FreeBSD Questions <freebsd-questions@freebsd.org>
> Subject: seriously hacked off!! Re: pkg upgrade failed again
> Message-ID: <53E68ECF.3070006@gmail.com>
> Content-Type: text/plain=3B charset=3Dwindows-1252=3B format=3Dflowed
>=20
>=20
> On 09/08/2014 20:48=2C Jamie Griffin wrote:
> > Just waited 9 hours for all the new packages to download to find this=20
> > happens:
> >
> > Checking for upgrades: 100%
> > Assertion failed: (var =3D=3D elt->var)=2C function pkg_solve_sat_probl=
em=2C=20
> > file pkg_solve.c=2C line 508.
> > Child process pid=3D5148 terminated abnormally: Abort trap
> >
> > When with a problematic package qt4-q
> testlib conflicting with=20
> > qt4-testlib=2C pkg upgraded itself to 1.3.3 first=2C I thought the solv=
er=20
> > was supposed to sort things like this?
> Once again pkg has completely f**ked up my packages and i'll have to=20
> remove everything and start over. That's the second time in as many=20
> months. Why are these things released when they cause so many problems=20
> for people. I actually dread upgrading FreeBSD now because I know it's=20
> going to involve stress.
>=20
> Thanks.
>=20
>=20
> ------------------------------
>=20
> Message: 30
> Date: Sat=2C 09 Aug 2014 16:32:26 -0500
> From: "William A. Mahaffey III" <wam@hiwaay.net>
> To: "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
> Subject: Re: X11 setup ....
> Message-ID: <53E6936A.900@hiwaay.net>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
> On 08/09/14 15:37=2C doug wrote:
> > On Sat=2C 9 Aug 2014=2C William A. Mahaffey III wrote:
> >
> >> On 08/09/14 12:03=2C doug wrote:
> >>> On Sat=2C 9 Aug 2014=2C William A. Mahaffey III wrote:
> >>>
> >>>>   .... I am following the instructions at
> >>>> [1]http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-confi=
g.h=20
> >>>>
> >>>>   tml to get my newly installed xorg setup. I stepped through=20
> >>>> everything
> >>>>   up to the 'Xorg -config xorg.conf.new -retro' which didn't fail=2C=
 bit
> >>>>   didn't behave quite like it was supposed to .... Machine is AMD=20
> >>>> Jaguar
> >>>>   Kabini based=2C quad core=2C 1.3 GHz=2C 25W=2C gfx on die:
> >>>>   Aug  9 10:23:34 kabini1 kernel: CPU: AMD Sempron(tm) 3850 APU with
> >>>>   Radeon(tm) R3     (1297.59-MHz K8-class CPU)
> >>>>   xorg detects it as: BoardName   "Kabini [Radeon HD 8280 / R3=20
> >>>> Series]"
> >>>>   The above test is supposed to give a black & grey grid on the=20
> >>>> screen=2C
> >>>>   w/ an X-mouse. I have the mouse=2C & it moves around=2C although
> >>>>   click-&-drag does nothing=2C & I might have the grid=2C although i=
t is
> >>>>   pixel-by-pixel=2C not finitely sized grid .... The troubleshooting=
=20
> >>>> page
> >>>>   is little help .... Am I good to go or not :-/ ? TIA ....
> >>>> --=20
> >>> Look in /var/log/Xorg.0.log. Errors are somewhat esoteric unless you=
=20
> >>> know a lot about X11 but they are clearly marked. You can subscribe=20
> >>> to the X11 mailing list or just search the archives of that list.
> >>>
> >>> You can see if you are good to go by trying startx.
> >>
> >> Thanks. My question was poorly articulated=2C should have been 'am I O=
K=20
> >> for XFCE ?' .... I plunged on & started XFCE=2C & it works mostly=20
> >> pretty good=2C but the gfx is definitely spotty=2C lotta flickering=2C=
=20
> >> background on desktop looks a bit dicey=2C window frames are granular =
&=20
> >> flickery. I just looked through /var/log/Xorg.0.log & there are *no*=20
> >> errors (no '(EE)'s) .... what now :-/ ....
> > Ah - my desktop of choice. The X11 list might help. I excel at=20
> > choosing PCs whose video card are not supported. However flickering=20
> > and worse in my experience has meant driver errors. Have you tried the=
=20
> > vesa driver? You will not get the full use of the card but if that=20
> > driver does not work it may mean hardware issues. If you have a=20
> > windows partition=2C it is good to test the hardware.
> >
> > I am afraid this one is above my pay grade :(
> > _______________________________________________
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe=2C send any mail to=20
> > "freebsd-questions-unsubscribe@freebsd.org"
> >
>=20
>=20
> It's already on the vesa driver=2C & the 'gfx card' is on die w/ the CPU=
=20
> .... No sweat=2C I figured I might have a few glitches w/ such new=20
> hardware .... When you say X11 list=2C do you mean the FreeBSD/X11 list=
=2C=20
> or X.org ? Thanks :-) ....
>=20
>=20
> --=20
>=20
> 	William A. Mahaffey III
>=20
>   ----------------------------------------------------------------------
>=20
> 	"The M1 Garand is without doubt the finest implement of war
> 	 ever devised by man."
>                             -- Gen. George S. Patton Jr.
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 31
> Date: Sat=2C 09 Aug 2014 16:47:29 -0500
> From: "William A. Mahaffey III" <wam@hiwaay.net>
> To: "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
> Subject: BIOS monitoring goodies ....
> Message-ID: <53E696F1.9050102@hiwaay.net>
> Content-Type: text/plain=3B charset=3DISO-8859-1=3B format=3Dflowed
>=20
>=20
>=20
> .... Linux has myriad tools=2C utilities=2C apps=2C etc. (hddtemp=2C lmse=
nsors=2C=20
> jwclock=2C etc.) for monitoring info from the BIOS &/or OS hardware info=
=20
> .... Surely there must be some such for FreeBSD=2C could someone point me=
=20
> to them :-) ? TIA ....
>=20
>=20
> --=20
>=20
> 	William A. Mahaffey III
>=20
>   ----------------------------------------------------------------------
>=20
> 	"The M1 Garand is without doubt the finest implement of war
> 	 ever devised by man."
>                             -- Gen. George S. Patton Jr.
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 32
> Date: Sat=2C 09 Aug 2014 14:38:11 -0700
> From: perryh@pluto.rain.com (Perry Hutchison)
> To: odhiambo@gmail.com
> Cc: questions@freebsd.org
> Subject: Re: TCP/IP on the way out?
> Message-ID: <53e694c3.Z9pgoYYlNshz0fcD%perryh@pluto.rain.com>
> Content-Type: text/plain=3B charset=3Dus-ascii
>=20
> Odhiambo Washington <odhiambo@gmail.com> wrote:
> > I have seen this article which sounds much like a dream=2C but seems tr=
ue.
> > http://www.networkworld.com/article/2459286/why-tcp/why-tcp/ip-is-on-th=
e-way-out.html
> > I'd love to hear the views of those who understand the network stack.
>=20
> I haven't read the article -- the page crashed Firefox -- but the
> idea of anything replacing TCP/IP reminds me of:
>=20
>   They who do not understand TCP are doomed to reinvent it=2C poorly.
>=20
> I think that quote may have originated with Henry Spencer.
>=20
>=20
> ------------------------------
>=20
> Message: 33
> Date: Sat=2C 9 Aug 2014 18:55:18 -0400 (EDT)
> From: doug <doug@fledge.watson.org>
> To: "William A. Mahaffey III" <wam@hiwaay.net>
> Cc: FreeBSD Questions !!!! <freebsd-questions@freebsd.org>
> Subject: Re: X11 setup ....
> Message-ID: <alpine.BSF.2.11.1408091850330.96880@fledge.watson.org>
> Content-Type: TEXT/PLAIN=3B charset=3DUS-ASCII=3B format=3Dflowed
>=20
> On Sat=2C 9 Aug 2014=2C William A. Mahaffey III wrote:
>=20
> > On 08/09/14 15:37=2C doug wrote:
> >> On Sat=2C 9 Aug 2014=2C William A. Mahaffey III wrote:
> >>=20
> >>> On 08/09/14 12:03=2C doug wrote:
> >>>> On Sat=2C 9 Aug 2014=2C William A. Mahaffey III wrote:
> >>>>
> >>>>>   .... I am following the instructions at
> >>>>> [1]http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-conf=
ig.h
> >>>>>   tml to get my newly installed xorg setup. I stepped through every=
thing
> >>>>>   up to the 'Xorg -config xorg.conf.new -retro' which didn't fail=
=2C bit
> >>>>>   didn't behave quite like it was supposed to .... Machine is AMD J=
aguar
> >>>>>   Kabini based=2C quad core=2C 1.3 GHz=2C 25W=2C gfx on die:
> >>>>>   Aug  9 10:23:34 kabini1 kernel: CPU: AMD Sempron(tm) 3850 APU wit=
h
> >>>>>   Radeon(tm) R3     (1297.59-MHz K8-class CPU)
> >>>>>   xorg detects it as: BoardName   "Kabini [Radeon HD 8280 / R3 Seri=
es]"
> >>>>>   The above test is supposed to give a black & grey grid on the scr=
een=2C
> >>>>>   w/ an X-mouse. I have the mouse=2C & it moves around=2C although
> >>>>>   click-&-drag does nothing=2C & I might have the grid=2C although =
it is
> >>>>>   pixel-by-pixel=2C not finitely sized grid .... The troubleshootin=
g page
> >>>>>   is little help .... Am I good to go or not :-/ ? TIA ....
> >>>>> --=20
> >>>> Look in /var/log/Xorg.0.log. Errors are somewhat esoteric unless you=
 know=20
> >>>> a lot about X11 but they are clearly marked. You can subscribe to th=
e X11=20
> >>>> mailing list or just search the archives of that list.
> >>>>=20
> >>>> You can see if you are good to go by trying startx.
> >>>=20
> >>> Thanks. My question was poorly articulated=2C should have been 'am I =
OK for=20
> >>> XFCE ?' .... I plunged on & started XFCE=2C & it works mostly pretty =
good=2C=20
> >>> but the gfx is definitely spotty=2C lotta flickering=2C background on=
 desktop=20
> >>> looks a bit dicey=2C window frames are granular & flickery. I just lo=
oked=20
> >>> through /var/log/Xorg.0.log & there are *no* errors (no '(EE)'s) ....=
 what=20
> >>> now :-/ ....
> >> Ah - my desktop of choice. The X11 list might help. I excel at choosin=
g PCs=20
> >> whose video card are not supported. However flickering and w
> orse in my=20
> >> experience has meant driver errors. Have you tried the vesa driver? Yo=
u=20
> >> will not get the full use of the card but if that driver does not work=
 it=20
> >> may mean hardware issues. If you have a windows partition=2C it is goo=
d to=20
> >> test the hardware.
> >>=20
> >> I am afraid this one is above my pay grade :(
> >>=20
> >
> > It's already on the vesa driver=2C & the 'gfx card' is on die w/ the CP=
U ....=20
> > No sweat=2C I figured I might have a few glitches w/ such new hardware =
....=20
> > When you say X11 list=2C do you mean the FreeBSD/X11 list=2C or X.org ?=
 Thanks=20
> > :-) ....
> >
> "FreeBSD X11 mailing list" <freebsd-x11@freebsd.org> is the one I follow.=
 I am=20
> hoping for a solution to the console switching issue. Either list is prob=
ably=20
> okay for this issue.
>=20
>=20
> ------------------------------
>=20
> Subject: Digest Footer
>=20
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe=2C send any mail to "freebsd-questions-unsubscribe@freebsd=
.org"
>=20
> ------------------------------
>=20
> End of freebsd-questions Digest=2C Vol 531=2C Issue 10
> **************************************************
 		 	   		  =



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BLU181-W56EC044F98AAEDC01BA9E2A2EF0>