Re: recover deleted file

[olli hauer]

Hi,
is there anyway easy to restore deleted file by accident in UFS


depends, years ago i had to use sysutils/testdisk to restore files from UFS 
after a HD crash.

Using the tools was easy but finding the right data in all the files the tool 
restored can be time consuming.

--
Good luck
olli

Re: Possible zpool online, resilvering issue

[olli hauer]

On 2016-08-04 07:22, Ultima wrote:
> Hello,
> 
> I recently had some issue with a PSU and ran several scrubs on a pool with
> around 35T. Random drives would drop and require a zpool online, this found
> checksum errors. (as expected) However, after all the scrubs I ran, I think
> I may have found a bug with zpool online resilvering process.
> 
> 24 disks total, 4 vdevs raidz2 (6 drives each).
> 
> Before this next part... I had a backup PSU, however it was also going bad
> and waiting for RMA. The current one seemed to be dieing but ran fine with
> less drives. So I decided I would run the server short 4 drives.
> 
> Started by offline(or already removed from psu) 4 drives from different
> vdevs, then ran a scrub to verify everything. Many sum errors were present
> on some of the drives, but this was expected due to faulty psu. Then
> offlined 4 different drives and onlined the other 4 and scrubbed once
> again. After resilver, again, many sum errors on these drives as expected.
> 
> After the scrub completed, I decided to offline 4 different drives, then
> online the ones that were out of pool for awhile. During the resilver,
> checksum errors were once again found. I was surprised due to the recent
> scrub, So I decided to run another scrub, and it found even more checksum
> errors on these recently onlined drives. I didn't think much about it,
> however after the replacement PSU arrived, I onlined all the drives out of
> pool and again, resilver had checksum errors as well as another scrub with
> more sum errors.
> 
> Is this issue known? Is it common for a scrub to be required after onlining
> a disk that was out of pool for some time?
> 
> The drives are ST4000NM0033, and until recent have never had a single
> checksum error in they're lifetime.(at least with zfs)
> FreeBSD S1 12.0-CURRENT FreeBSD 12.0-CURRENT #19 r303224: Sat Jul 23
> 10:41:12 EDT 2016
> root@S1:/usr/src/head/obj/usr/src/head/src/sys/MYKERNEL-NODEBUG
>  amd64
> 
> 
> Sorry for the wall of text, but I hope this helps in tracking down this
> possible bug.
> 

Perhaps on or more of the drives running out of Realloc Sectors?
I had once a case where smartctl showed no issues but zfs scrubbing showed
a defect, some weeks later smartctl was showing some reallocated sectors
and one week later the HD was out of spare sectors.

Have you already tested every single HD for smart issues?

-- 
olli
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Re: FreeBSD-11.0-BETA1-amd64-disc1.iso is too big for my 700MB CD-r

[Olli Hauer]

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

Re: Re: ATA? related trouble with r300299

[Olli Hauer]

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

Re: Heads up

[olli hauer]

On 2016-04-15 06:19, Warner Losh wrote:
> On Thu, Apr 14, 2016 at 9:56 PM, Warren Block  wrote:
> 
>> On Thu, 14 Apr 2016, Warner Losh wrote:
>>
>> The CAM I/O scheduler has been committed to current. This work is described
>>> in https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the
>>> default scheduler doesn't change the default (old) behavior.
>>>
>>> One possible issue, however, is that it also enables NCQ Trims on ada
>>> SSDs.
>>> There are a few rogue drives that claim support for this feature, but
>>> actually implement data corrupt instead of queued trims. The list of known
>>> rogues is believed to be complete, but some caution is in order.
>>
>>
> 
>> Is the list of drives queryable?  Is there an easy way to tell if the
>> currently-connected drives are on the list?
>>
> 
> /usr/src/sys/cam/ata/ata_da.c has the list.
> 
> dmesg will tell you if it detected a bad one since it prints the drive's
> quirks.
> But that's no big deal, because the bad one work just fine if you never
> issue
> a NCQ TRIM. This small group of drives were early adapters of this
> technology
> 
> Here's the full list of known rogues:
> 
> Crucial/Micron M500 (all firmware prior to MU07)
> Micron M510 MU01 firmware (newer firmware is good)
> Crucial/Micron M550 MU01 firmware (newer firmware is good)
> Crucial MX100 MU01 firmware (newer firmware is good)
> FCCT M500 all firmware
> Samsung 830 all firmware
> Samsung 840 all firmware
> Samsung 850 all firmware
> 
> All of these are at least 18 months old (if not older). There's some
> confusing in Linux lists on
> the full impact of the Samsung drives (there was a bug in the Linux
> implementation (that can't
> be present in the FreeBSD implementation) that may have been the root cause
> for the Samsung
> black listing). Out of an abundance of caution, I've kept them in the list.
> Also, it's my belief that
> the Crucial/Micron models with MU01 firmware were mostly corrected after
> early samples
> since most of the channel drives I've helped people debug had MU02
> firmware. Also, a quick
> google search shows the MU02 firmware for each of these models has been
> available for
> at least a year.
> 
> Warner

I suspect this was the reason why Samsung SSD's are listed on the Linux 
blacklist.
https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/

But the article also reports it was a Linux kernel issue ...

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

Re: how to recycle Inact memory more aggressively?

[olli hauer]

...

>> Just a point I've bought up elsewhere...
>> I've, if I recall, wrecked several filesystems (although EIDE) using
>> rsync at the normal bus rate, and sometimes
>> thumbdrives with whatever filesystem type on them.
>>
>> I settled on --bwlimit=1500,  max for unattended  rsync usage and
>> almost every day
>> use --bwlimit=700.

It happened also on VM's where the host is connected via FC to the storage
but only on the FreeBSD VM's.


>> The latter enables several resource-intensive processes ( music,
>> classical music videos, svn, pkg, browsing, etc) to
>> proceed apace concurrently on the desktop (SATA not EIDE) with nary a
>> hang nor slowdown.

I don't have any *NIX system with a gui, only around 110+ headless systems
and halve of them are running FreeBSD.


> I have no real idea what any of that is about, but before it turns into
> some kind of "rsync is bad" mythology, let me just say that I've been
> using rsync to copy gigabytes of backup data every day for years now. 
>  I've never had any kind of problem, especially system responsiveness
> problems, until this increased swapfile activity thing started
> happening on 10-stable in the past few months.
> 
> To reiterate: rsync is not in any way at fault here, and any suggestion
> that the unresponsiveness should be "fixed" by screwing around with
> rsync parms that have worked fine for a decade is just something I
> completely reject.
> 
> I'm sure I'd see the same kind of increased swapping with ANY process
> that read and wrote gigabytes of data in a short period of time.  And
> that's what this thread is about:  What has changed to cause this
> regression that multiple people are seeing where lots of IO now drives
> an unusual amount of swapfile activity on systems that used to NEVER
> write anything to swap?

All those systems are running already for years, for me it looks more
like a missing *free* (memory leak).

Looking at the net/rsync history the last update was in Dec. 2015. Perhaps
it is worth to test net/rsync r359474 for a while to get a comparsion, but
Gary reported the issue by using `cp' and not rsync.

-- 
olli
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: how to recycle Inact memory more aggressively?

[olli hauer]

On 2016-03-14 15:19, Ian Lepore wrote:
> On Sun, 2016-03-13 at 19:08 -0700, Adrian Chadd wrote:
>> On 13 March 2016 at 18:51, Mark Johnston  wrote:
>>> On Sun, Mar 13, 2016 at 06:33:46PM -0700, Adrian Chadd wrote:
 Hi,

 I can reproduce this by doing a mkimage on a large destination
 file
 image. it looks like it causes all the desktop processes to get
 paged
 out whilst it's doing so, and then the whole UI freezes until it
 catches up.
>>>
>>> mkimg(1) maps the destination file with MAP_NOSYNC, so if it's
>>> larger
>>> than RAM, I think it'll basically force the pagedaemon to write out
>>> the
>>> image as it tries to reclaim pages from the inactive queue. This
>>> can
>>> cause stalls if the pagedaemon blocks waiting for some I/O to
>>> complete.
>>> The user/alc/PQ_LAUNDRY branch helps alleviate this problem by
>>> using a
>>> different thread to launder dirty pages. I use mkimg on various
>>> desktop
>>> machines to build bhyve images and have noticed the problem you're
>>> describing; PQ_LAUNDRY helps quite a bit in that case. But I don't
>>> know
>>> why this would be a new problem.
>>>
>>
>> That's why I'm confused. I just know that it didn't used to cause the
>> whole UI to hang due to paging.
>>
> 
> I've been noticing this too.  This machine runs 10-stable and this use
> of the swap began happening recently when I updated from 10-stable
> around the 10.2 release time to 10-stable right about when the 10.3
> code freeze began.
> 
> In my case I have no zfs anything here.  I noticed the problem bigtime
> yesterday when rsync was syncing a ufs filesystem of about 500GB from
> one disk to another (probably 70-80 GB actually needed copying).  My
> desktop apps were noticibly unresponsive when I activated a window that
> had been idle for a while (like it would take a couple seconds for the
> app to begin responding).  I could see lots of swap In happening in top
> during this unresponsiveness, and noticible amounts of Out activity
> when nothing was happening except the rsync.
> 
> This is amd64, 12GB ram, 16GB swap, a tmpfs had about 400MB in it at
> the time.  Prior to the update around the 10.3 freeze, this machine
> would never touch the swap no matter what workload I threw at it (this
> rsync stuff happens every day, it's the usual workload).
> 

I'm not sure if it is the same problem, or port related.

On two systems without zfs but with many files e.g. svn servers I see now
from time to time they are running out of swap.

 kernel: swap_pager_getswapspace(9): failed
 kernel: swap_pager_getswapspace(16): failed
 ...

It also happened on one system during the nightly periodic tasks holding
only millions of backup files.

$ freebsd-version -ku
  10.2-RELEASE-p9
  10.2-RELEASE-p13


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

Whats the different between the two fingerprints?

[olli hauer]

Hi,

whats the different between the two fingerprints ?

1) 23eb3a878c79d9c982ffe8e0041dfb5d7526d9bce868f60bcd51b00c86215d9f
2) 23EB3A878C79D9C982FFE8E0041DFB5D7526D9BCE868F60BCD51B00C86215D9F


For human both are the same, but not if tested with 
(md5|sha1|sha256|sha512|rmd160) -c $string

Unluckily some vendors providing fingerprints in uppercase (pointing e.g. to 
HP).
The fix is really trivial to implement in src/sbin/md5/md5.c (low hanging fruit)

If a dev with src commit has 5min, it would be nice if the one can look at PR 
205598

-- 
Thanks,
olli
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Whats the different between the two fingerprints?

[olli hauer]

On 2016-01-12 19:41, Allan Jude wrote:
> On 2016-01-12 13:24, olli hauer wrote:
>> Hi,
>>
>> whats the different between the two fingerprints ?
>>
>> 1) 23eb3a878c79d9c982ffe8e0041dfb5d7526d9bce868f60bcd51b00c86215d9f
>> 2) 23EB3A878C79D9C982FFE8E0041DFB5D7526D9BCE868F60BCD51B00C86215D9F
>>
>>
>> For human both are the same, but not if tested with 
>> (md5|sha1|sha256|sha512|rmd160) -c $string
>>
>> Unluckily some vendors providing fingerprints in uppercase (pointing e.g. to 
>> HP).
>> The fix is really trivial to implement in src/sbin/md5/md5.c (low hanging 
>> fruit)
>>
>> If a dev with src commit has 5min, it would be nice if the one can look at 
>> PR 205598
>>
> 
> there is a PR for this. It is being worked on.
> 

Yes, I wrote the PR ;)
Until now it was not taken and I would be very happy to see the fix in 
stable9/10 before 10.3 is released.

-- 
olli
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pkg does not update the repo catalogue

[olli hauer]

On 2015-12-07 09:50, Matthias Apitz wrote:
> 
> Hello,
> 
> This is with 11-CURRENT and ports from July this year; I have the
> packages which I build with poudriere on some other host in a dir
> /usr/PKGDIR.20150726 and added 8 new packages there, the total number is
> now 1691:
> 
> # ls *.txz | egrep -v 'packagesite.txz|meta.txz|digests.txz' | wc -l 
> 1691
> 
> My repo definition is:
> 
> # cat /usr/local/etc/pkg/repos/myrepo.conf
>FreeBSD: {
>url: "file:/usr/PKGDIR.20150726",
>enabled: true,
>}
> 
> When I now want to update the 8 new packages to the repo catalogue, they
> are not added (i.e. the number stays with 1683 and I also can not
> install them with 'pkg instal ...'):
> 
> # pkg -v
> 1.5.5
> # pkg -R /usr/local/etc/pkg/repos/ update -f
> Updating FreeBSD repository catalogue...
> Fetching meta.txz: 100%260 B   0.3kB/s00:01
> Fetching packagesite.txz: 100%  382 KiB 391.6kB/s00:01
> Processing entries: 100%
> FreeBSD repository update completed. 1683 packages processed.
> 
> What I'm missing here?
> 
> Thanks
> 
>   matthias

Hi Matthias,

I see some possible issues.

- repo has same name as the official one (FreeBSD, see `cat 
/etc/pkg/FreeBSD.conf')
- file:/$path should be file:///$path
- repo catalog was not updated with command `pkg repo'
- REPO_AUTOUPDATE = true/false (in pkg.conf)

Does your repo match the output of the command
$ pkg -vv (all below Repositories:)



-- 
olli
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: em broken on current amd64

[olli hauer]

On 2015-09-07 23:10, Mark R V Murray wrote:
> 
>> On 5 Sep 2015, at 17:11, Garrett Cooper  wrote:
>>
>>
>>> On Sep 5, 2015, at 08:50, Manfred Antar  wrote:
>>>
>>> Recent changes to em have broken current on amd64.
>>> Booting kernel will hang when trying to load em0, then will continue 
>>> booting without the driver loading (No Network)
>>> This is on a HP SFF 8000 with em0 embedded on the motherboard.
>>>
>>> boot messages:
>>>
>>> em0:  port 0x3100-0x311f mem 
>>> 0xf310-0xf311,0xf3125000-0xf3125fff irq 19 at device 25.0 on pci0
>>> em0: attempting to allocate 1 MSI vectors (1 supported)
>>> em0: using IRQ 265 for MSI
>>> em0: Using an MSI interrupt
>>> em0: The EEPROM Checksum Is Not Valid
>>> device_attach: em0 attach returned 5
>>
>> Tijl said the same. The offending commit's r287467.
>> Cheers,
> 
> I’m also seeing breakage with the em0 device; this isn’t a kernel hang, it is 
> a failure to move data after about 10-15 minutes. The symptom is that my WAN 
> ethernet no longer moves traffic, no pings, nothing. Booting looks normal:
> 
> em0:  port 0x30c0-0x30df mem 
> 0x5030-0x5031,0x50324000-0x50324fff irq 20 at device 25.0 on pci0
> em0: Using an MSI interrupt
> em0: Ethernet address: 00:16:76:d3:e1:5b
> em0: netmap queues/slots: TX 1/1024, RX 1/1024
> 
> Fixing it is as easy as …
> 
> # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up
> 
> :-)
> 
> I’m running CURRENT, r287538. This last worked of me a month or so ago at my 
> previous build.
> 

Not sure if this is a current issue.

Some days ago I build a 10.2 system with an on-board em0 to test my new 
assigned IPv6 (only) connectivity and seeing similar symptoms.
Haven't measured the time but the system stops forwarding packages on the em0 
until I bring it down and up again (sometime additional restart pf)

# uname
FreeBSD 10.2-RELEASE #0 r28: Wed Aug 12 15:26:37 UTC 2015 
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

# ifconfig em0
em0: flags=8843 metric 0 mtu 1500

options=4219b
ether f8:b1:56:d7:a9:c4
inet6 fe80::fab1:56ff:fed7:a9c4%em0 prefixlen 64 scopeid 0x1
inet6 2001:9xx:1xxx::2 prefixlen 64
nd6 options=23
media: Ethernet autoselect (1000baseT )
status: active

# dmesg | grep em0
em0:  port 0xf040-0xf05f mem 
0xfb30-0xfb31,0xfb328000-0xfb328fff irq 20 at device 25.0 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: f8:b1:56:d7:a9:c4
ahciem0:  on ahci0
ses0 at ahciem0 bus 0 scbus1 target 0 lun 0


-- 
olli
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Import of DragonFly Mail Agent

[olli hauer]

On 2014-02-25 16:31, RW wrote:
 On Mon, 24 Feb 2014 19:24:02 -0500 (EST)
 Benjamin Kaduk wrote:
 
 On Mon, 24 Feb 2014, Lyndon Nerenberg wrote:


 What would really help is if the ports fetch-recursive-list target
 could extend to reliably include the distfiles for the runtime
 dependencies as well.  But I'm not even sure that's possible.  We
 tried a few different things, but in the end we had to brute force
 it by running 'make fetch' in every one of the ports directories in
 order to get all the distfiles onto an external system, which we
 then rsynced to a USB drive, marched inside, and rsynced to the
 fileserver.  Not pretty ... but with all the distfiles at hand we
 knew the inside ports builds wouldn't fail due to missing
 dependencies.

 I'm rather confused by why it isn't working for you. 
 http://svnweb.freebsd.org/ports/head/Mk/bsd.port.mk?revision=345884view=markup#l5187
  
 is quite clearly looking in ALL-DEPENDS-LIST, which includes runtime 
 dependencies.  The only thing I can think of is that non-default 
 configurations are in play, so that 'make config  make
 config-recursive' should be (re-)run until it does not prompt, and
 only then fetch-recursive-list be used.  
 
 
 One oddity is that fetch-recursive-list generates a script that
 downloads all the files into the current directory. It doesn't take
 account of the fact that some ports look for their files are in a
 sub-directory. 


Some snippets from a script that is used to manage updates,
tinderboxe builds, poudriere builds ...


I collected all ports that are required to build my environments
from tinderbox (./tc listPorts) and others in a plain txt file.
in the format $cat/$port.

...
databases/php5-pdo
databases/php5-pdo_mysql
databases/php5-pdo_pgsql
databases/php5-pdo_sqlite
databases/php5-pgsql
databases/postgresql92-client
databases/postgresql92-server
databases/postgresql93-client
databases/postgresql93-server
databases/py-gdbm
databases/rrdtool
databases/rrdtool12
databases/sqlite3
...


Reading this file in a loop with a command like the following
will fetch all required distfiles.

while read port; do
  env -i WRKDIRPREFIX=/tmp/rbtrash PKG_DBDIR=/var/empty \
   LOCALBASE=/var/empty make fetch -DBATCH -C /usr/ports/${port} \
   -DCLEAN_FETCH_ENV -DDISABLE_CONFLICTS
done  $path/to/interesting/port/list


A list of all required dependency's can be generated with this command
(for a single port or in the sample loop (s/fetch/all-depends-list/)

$ make all-depends-list /usr/ports/$cat/${port}


Ports tree updates (portsnap or svn up) are written to a log which is used
to generate a list of ports where the distfile is maybe missing, the loop
reads then only this new list.

The directory with all distfiles is distributed via httpd to all build
systems (make.conf: MASTER_SITE_OVERRIDE=$central/fetch/server/url )


Hope this gives some ideas ;)

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

Re: freebsd-update

[olli hauer]

On 2014-01-24 20:31, Mark Felder wrote:
 I agree with the rest of this thread. This is just awful. I'm basically
 forced to do source based updates when jumping major versions because
 freebsd-update is a nightmare to use.


Not tested, but maybe this works.
a) use etcmerge before freebsd-upgrade and exclude /etc in freebsd-update.conf
b) manually extract the sources, then use mergemaster and then run 
freebsd-update
c) if you have more then one system fix once freebsd-update and deploy the 
script to the rest of the systems

I use myself a mix of mergemaster and upgrade via the (kernel|src|man|...).txz 
and base.txz (exclude ^./etc).
Going this way since 6.x and also major upgrades 6.x-7.x-8.x ... main issue 
on older systems is the space required by the kernel symbols.

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

Re: PACKAGESITE spam

[olli hauer]

On 2013-12-22 15:00, Frank Seltzer wrote:
 
 On Sat, 21 Dec 2013, Steve Kargl wrote:
 
 On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote:
 I've just installed a very recent -CURRENT, and now I'm performing a big 
 portupgrade procedure. I get the following message spammed a lot:

 pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository 
 configuration file

 Yeah, I noticed that spam along with the spam that is being
 spewed to /var/log/messaage, e.g.,

 Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed
 Dec 21 10:31:15 laptop-kargl pkg-static: libcdr-0.0.14 installed
 Dec 21 10:32:35 laptop-kargl pkg-static: openjpeg-1.5.0_2 installed
 Dec 21 10:38:33 laptop-kargl pkg-static: poppler-data-0.4.6 installed
 Dec 21 10:39:48 laptop-kargl pkg-static: poppler-0.22.2 installed
 Dec 21 10:40:32 laptop-kargl pkg-static: ilmbase-2.1.0 installed
 Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed
 Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed
 Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed

 Can you (portmgr) please mute these messages?

 -- 
 Steve
 
 This received several responses.
 
 Greg Rivers said:
 
 Do you really feel that strongly about it?  Having a record of changes to
 the system has always seemed like a feature to me...
 
 Baptiste Daroussin said:
 
 this has been done and activated for reason, first for lot of companies, it 
 is important (PCI DSS requirement for example), secondly I receive tons of 
 request to actiavte on by default while you are the first to request it off 
 by default
 
 Adrian Chadd said:
 
 The point is that some people like an audit trail. The audit trail for
 some people involves remote logging of syslog messages to a log host.
 This would include when packages are installed.
 
 My thought:
 
 Then why can't the messages about installed ports have it's own log file 
 rather than /var/log/messages?
 
 As for this message:
 
 pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository 
 configuration file
 
 Glen Barber replied:
 
 echo 'SYSLOG: no'  /usr/local/etc/pkg.conf
 
 And Shane Ambler:
 
 now we can turn it off which I don't think we could before.
 
 Me again:
 
 Where is this documented?
 
 /root # man pkg.conf
 No manual entry for pkg.conf

Hm, on all my systems I have a man page for pkg.conf

Here is the referenced passage from man 5 pkg.conf

OPTIONS
  The following options can be defined in pkg.conf:
...
  SYSLOG: booleanThis option is enabled by default, log all
 the installation/deinstallation/upgrade oper-
 ation via syslog(3)


What I agree is having it would be nice to have dedicated syslog
(like yum.log) instead /var/log/messages since this is already
spammed by most every process.

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

Re: md2 on current and 10.

[olli hauer]

On 2013-12-20 01:44, Mikhail T. wrote:
 It would appear, neither md2.h nor openssl/md2.h are any longer available 
 on
 FreeBSD current and 10.x
 
 This breaks the devel/tcl-trf port, which I maintain... Could someone, please,
 comment? Should I patch-up the port to disable the functionality? Or?..
 
 Thank you!
 
 -mi

Hm the config script tests for md2 and sha1 ...
What happens if md2 support is removed from the code?

Btw.
This issue already exists for a longer time if openssl from ports is in use.
http://svnweb.freebsd.org/ports?view=revisionrevision=252255

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

Re: md2 on current and 10.

[olli hauer]

On 2013-12-20 19:04, Mikhail T. wrote:
 On 20.12.2013 12:52, olli hauer wrote:
 Hm the config script tests for md2 and sha1 ...
 What happens if md2 support is removed from the code?
 Yes, the md2 can be removed from the set of digests made available by the port
 -- that's not a problem.
 
 What I wanted to know, was why? Maybe, the header files should've been 
 replaced
 with ones containing an #error (like malloc.h was)... Oh well...
 
 -mi

md2 was deprecated in 2009 by the openssl project

 http://cvs.openssl.org/chngview?cn=18381
 CVE-2009-2409

As fas as I know some Linux based projects have removed md2 from openssl-0.9.x 
in 2009.

I have no answer why FreeBSD 8/9 has the old openssl-0.9.8y and md2 support was 
not removed.

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

Re: svn ports, or the hen egg

[olli hauer]

On 2013-12-18 22:09, Matthias Apitz wrote:
 El día Wednesday, December 18, 2013 a las 12:59:16PM -0800, Freddie Cash 
 escribió:
 
 On Wed, Dec 18, 2013 at 12:50 PM, Matthias Apitz g...@unixarea.de wrote:

 As ports are now for some time are to be pulled out via SVN (and not
 CVS) and the svn client is only in the ports tree and not in the base
 system, how is this thought to work in a clean way, without dusting the
 system before with some binary packages, only based on base system and
 sources?

 svnlite is included in the base OS for 10.0.

 See https://wiki.freebsd.org/WhatsNew/FreeBSD10 for details.  And
 http://svnweb.freebsd.org/base?view=revisionrevision=251886 for the commit
 message.
 
 Ok, thanks; but see this:
 
 $ uname -a
 FreeBSD tiny-r255948 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1: Fri Oct 18 12:10:57 
 CEST 2013 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC/i386
 $ svnlite
 Type 'svn help' for usage.
 $ svn help
 svn: not found
 
 :-)
 

One of my first commands until svn is is installed
$ alias svn svnlite

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

Re: mystery problem with SVN update in /head

[olli hauer]

On 2013-10-31 14:29, Matthias Apitz wrote:
 
 Hello,
 
 I have the following problem while updating an item in the ports tree:
 
 the SVN checkout was done on October 1; when I do now
 
 # cd /usr/ports/net
 # rm -r vnc
 # svn up vnc
 Updating 'vnc':
 Restored 'vnc'
 Restored 'vnc/pkg-plist'
 Restored 'vnc/Makefile'
 Restored 'vnc/distinfo'
 Restored 'vnc/pkg-descr'
 Restored 'vnc/files'
 Restored 'vnc/files/FreeBSD.cf-patch'
 Restored 'vnc/files/extra-patch-xc-config-util-printver.c'
 Restored 'vnc/files/vnc.def-patch'
 Restored 'vnc/files/extra-patch-fix_Xvnc_no_valid_address'
 Restored 'vnc/files/patch-unix-xc-programs-Xserver-vnc-Imakefile'
 Restored 'vnc/files/extra-patch-xfree86'
 Restored 'vnc/files/patch-unix-x0vncserver-x0vncserver.cxx'
 Restored 'vnc/files/patch-unix-xc-programs-Xserver-vnc-XserverDesktop.h'
 Restored 'vnc/files/patch-xc-programs-Xserver-vnc-vncExtInit.cc'
 At revision 332203.
 
 some files are missing (marked below)
 
 also a
 
 # rm -r vnc
 # svn co svn://svn.freebsd.org/ports/head/net/vnc
 
 does not help; only doing the checkout in an empty space like
 
 # cd /tmp
 # svn co svn://svn.freebsd.org/ports/head/net/vnc
 Avnc/pkg-plist
 Avnc/Makefile
 Avnc/distinfo
 Avnc/pkg-descr
 Avnc/files
 Avnc/files/patch-unix-tx-TXImage.cxx
  ^
 Avnc/files/patch-unix-x0vncserver-x0vncserver.cxx
 Avnc/files/patch-common-network-TcpSocket.cxx
  ^
 Avnc/files/patch-unix-xc-programs-Xserver-vnc-XserverDesktop.h
 Avnc/files/patch-xc-programs-Xserver-vnc-vncExtInit.cc
 Avnc/files/FreeBSD.cf-patch
 Avnc/files/extra-patch-xc-config-util-printver.c
 Avnc/files/vnc.def-patch
 Avnc/files/extra-patch-fix_Xvnc_no_valid_address
 Avnc/files/patch-unix-x0vncserver-Image.cxx
  ^
 Avnc/files/patch-unix-xc-programs-Xserver-vnc-Imakefile
 Avnc/files/extra-patch-xfree86
 Checked out revision 332240.
 
 brings the marked files to my disk; why is this?


It's more interesting to look with `svn stat' if your copy has cached some
local modifications or blocking conflicts from local editing.

Tip:
running from time to time the command `svn cleanup' should prevent this issue.
http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.cleanup.html


Nice side effect from `svn cleanup'

 du -h -d1 /usr/ports/.svn/
619M/usr/ports/.svn/pristine
2.0k/usr/ports/.svn/tmp
695M/usr/ports/.svn/

 find /usr/ports/.svn/ -type f | wc -l
  134004

 svn cleanup
 du -h -d1 /usr/ports/.svn/
430M/usr/ports/.svn/pristine
2.0k/usr/ports/.svn/tmp
506M/usr/ports/.svn/

 find /usr/ports/.svn/ -type f | wc -l
  117269

PS:
If you even want to get back some more space try the command
 sqlite3 .svn/wc.db vacuum


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

Re: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv

[olli hauer]

There are 13 ports using --with-iconv=${LOCALBASE}
 devel/apr1
 devel/apr2
 devel/git
 irc/epic5
 lang/gauche
 net-mgmt/ettercap
 net/ssltunnel-client
 net/yaz
 net/zebra-server
 textproc/libxml2
 textproc/py-libxml2
 www/apache22
 www/apache24


and devel/glib20, print/ghostscript8, print/ghostscript9 using
 --with-libiconv=gnu
 --with-libiconv=native
 --with-libiconv=no
 --with-libiconv=no


Unfortunately Uses/iconv.mk defines only --with-libiconv(-prefix).

If Uses/iconv.mk can be extended with something like ICON_PATH, then
the 13 ports can be changed quickly to use the right iconv.

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

Re: [head tinderbox] failure on arm/arm

[olli hauer]

On 2013-06-19 07:27, Tim Kientzle wrote: stage 4.2: building libraries
 stage 4.3: make dependencies
 stage 4.4: building everything
 [...]
 /src/usr.bin/svn/lib/libapr/../../../../contrib/apr/include/apr_ring.h:183:34:
  note: expanded from macro 'APR_RING_PREV'
 #define APR_RING_PREV(ep, link) (ep)-link.prev
 ^
 /src/usr.bin/svn/lib/libapr/../../../../contrib/apr/include/apr_ring.h:177:34:
  note: expanded from macro 'APR_RING_NEXT'
 #define APR_RING_NEXT(ep, link) (ep)-link.next
 ^
 fatal error: too many errors emitted, stopping now [-ferror-limit=]
 1 warning and 20 errors generated.
 *** Error code 1

 Stop.
 make: stopped in /src/usr.bin/svn/lib/libapr
 *** Error code 1
 
 This might be the OffsetOf bug for APR on ARM.
 We just got a fix pushed upstream for this a few
 days ago.
 
 I don't have time to look, but someone should take
 a peek at the following patch and see if it's
 needed:
 
 --- ./apr-1.4.7/include/apr_general.h.orig
 +++ ./apr-1.4.7/include/apr_general.h
 @@ -76,7 +76,7 @@
 ·*·@return·offset
 ·*/
 -#if·defined(CRAY)·||·(defined(__arm)··!defined(LINUX))
 +#if·defined(CRAY)·||·(defined(__arm)··!(defined(LINUX)·||·defined(__FreeBSD__)))
 #ifdef·__STDC__
 #define·APR_OFFSET(p_type,field)·_Offsetof(p_type,field)
 #else
 

Sorry for the late reply,

There is a new apr version on the way which contains the fix already,
I suspect it will be released during the next days (if no show stopper is found)

The following patch updates apr from 1.4.6 to 1.4.8
 http://people.freebsd.org/~ohauer/diffs/apr-1.4.8.1.4.1.diff

Would you mind to test the new version on the arm platform and run
$ make test (as non priv. user)

I have tested on 8.4 and 9.1 no 10-cur system available,
tests do not run on redports because of system restrictions (jail).

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

Please test upcoming DTrace port mod_usdt for apache22

[Olli Hauer]

Hi,

I've created together with Pedro Giffuni (pfg@) a new
DTrace apache port (www/mod_usdt).

We are interested in getting some more test results from
DTrace and apache users.

A complete description is here:
http://dtrace.org/blogs/dap/2011/12/13/usdt-providers-redux/

shar file for mod_usdt can be found here:
http://people.freebsd.org/~ohauer/shar/mod_usdt_2013051601.shar

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

Re: www/apache24: ports like lang/php5 or devel/subversion are disturbed by the apache24 port!

[Olli Hauer]

It will take a while until php is really apache24 ready.

Work is in progress on php upstream.

One of the issues is that APXS does not provide the
MPM model which is needed for php and others to build.

With a quick search I can find this entry
https://bugs.php.net/bug.php?id=61172

Even php build I don't think it is ready for apache24

--
Regards,
olli


On 2013-03-31 19:21, O. Hartmann wrote:
 It is hard to explain in the subject.
 
 I have Apache 2.4 running on a most recent FreeBSD 10.0:
 FreeBSD 10.0-CURRENT #1 r248935: Sat Mar 30 20:25:32 CET 2013
 
 I have successfully running port www/apache24. The port is really bumpy,
 if not to say crappy. Whenever I want to rebuild a port that has alos a
 module provided for apache24, the port, like php5, ends up crashing just
 before it gets installed with an obscure error message, that one of the
 configuration files of Apache 2.4 seems to be wrong - which is a
 complete non-sense statement, since Apache 2.4 runs well and the log
 does not show any complains about a wrong config.
 
 Below, I provided the error message that comes at the end of the
 installation of port lang/php5 (a similar error message complaining
 about AuthzSVN-tags arise when building and reinstalling
 devel/subversion):
 
 
 === Creating a backup package for old version php5-5.4.13
 Creating package for php5-5.4.13
 The following packages will be deinstalled:
 
 php5-5.4.13
 
 The deinstallation will free 15 MB
 Deleting php5-5.4.13...
 php5-5.4.13 is required by: cups-pdf-2.6.1_1 cups-smb-backend-1.0_6
 cups-base-1.5.4_1 drupal7-7.21 php5-ctype-5.4.13 php5-curl-5.4.13
 php5-dom-5.4.13 php5-fileinfo-5.4.13 php5-filter-5.4.13 php5-gd-5.4.13
 php5-gettext-5.4.13 php5-hash-5.4.13 php5-iconv-5.4.13 php5-json-5.4.13
 php5-ldap-5.4.13 php5-mbstring-5.4.13 php5-mysql-5.4.13
 php5-openssl-5.4.13 php5-pdo-5.4.13 php5-pdo_mysql-5.4.13
 php5-pdo_pgsql-5.4.13 php5-pdo_sqlite-5.4.13 php5-pgsql-5.4.13
 php5-session-5.4.13 php5-simplexml-5.4.13 php5-sqlite3-5.4.13
 php5-xml-5.4.13 php5-xsl-5.4.13 php5-zip-5.4.13 php5-zlib-5.4.13
 phpldapadmin-1.2.3,1 nagios-3.5.0 owncloud-5.0.0 websvn-2.3.3, deleting
 anyway
 [preparing module `php5' in /usr/local/etc/apache24/httpd.conf]
  done
 
 AH00526: Syntax error on line 199
 of /usr/local/etc/apache24/extra/httpd-authnz_ldap.conf:
 Invalid command 'php_flag', perhaps misspelled or defined by a module
 not included in the server configuration
 apxs:Error: Invalid query string `MPM_NAME'.
 /usr/ports/Mk/bsd.apache.mk, line 284: warning: /usr/local/sbin/apxs
 -q MPM_NAME returned non-zero status
 ===  php5-5.4.13 is marked as broken: : Error from bsd.apache.mk.
 apache is installed (or APACHE_PORT is defined) and port requires
 apache22 at least.
 *** [install] Error code 1
 
 Stop in /usr/ports/lang/php5.
 
 === A backup package for php5-5.4.13 should
be located in /usr/ports/packages/portmaster-backup
 
 === Installation of php5-5.4.13 (lang/php5) failed
 === Aborting update
 
 === Update for php5-5.4.13 failed
 === Aborting update
 
 === Killing background jobs
 Terminated
 
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: FreeBSD is very slow when Memory chip sizes are imbalanced in slots

[olli hauer]

On 2013-03-18 21:43, Mehmet Erol Sanliturk wrote:
 On Mon, Mar 18, 2013 at 9:48 AM, Scot Hetzel swhet...@gmail.com wrote:
 
 On Mon, Mar 18, 2013 at 11:06 AM, Mehmet Erol Sanliturk
 m.e.sanlit...@gmail.com wrote:
 Computer A : Memory Chip Sizes : ( 2 GB , 1 GB , 2 GB , 1 GB ) : Working
 SLOW . FreeBSD A
 Computer B  : Memory Chip Sizes : ( 2 GB , 2 GB , 2 GB , 2 GB ) : Working
 FAST . FreeBSD B

 Interchange memory chips :

 Computer A : Memory Chip Sizes : ( 2 GB , 2 GB , 2 GB , 2 GB ) : Working
 FAST . FreeBSD A
 Computer B  : Memory Chip Sizes : ( 2 GB , 1 GB , 2 GB , 1 GB ) : Working
 SLOW . FreeBSD B



 What happens if you configure the memory as ( 2 GB , 2 GB , 1 GB , 1 GB )?

 --
 DISCLAIMER:

 No electrons were maimed while sending this message. Only slightly bruised.

 
 
 This can NOT be done  , because
 
 Channel A : Slot 1 :
Slot 2 :
 
 Channel B : Slot 1 :
Slot 2 :
 
 ( Slot 1 , Slot 1 ) should be equivalent when chips inserted to both .
 ( Slot 2 , Slot 2 ) should be equivalent when chips inserted to both .
 
 Thank you ver much .
 

I suspect the BIOS does not detect the optimal timing for the SLOW RAM or
a RAM Module is running on a slower timing.

What happen if you test with only the 2GB or the 1GB modules (to identify 
possible CHIP issues).
How is the memory detected in the BIOS (timings ...) some newer BIOS can run 
manual tests to detect timing issues.



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

Re: pkgng default schedule... registering a few reasons for rethinking the final implementation...

[olli hauer]

On 2012-08-23 21:50, Kris Moore wrote:
 On 08/23/2012 13:10, Jeremy Messenger wrote:
 On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore k...@pcbsd.org wrote:
 On 08/23/2012 12:26, Jeffrey Bouquet wrote:
 I am following with dread the planned implementation of the deprecation of 
 /var/db/pkg as a package registry... I use each /var/db/pkg directory as a 
 database into the port installation/status, using 
 sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix 
 stuff.  For instance, an upgrade py26  py27.
 cd /var/db/pkg
 ls -lac | grep py26
 ls -lac | grep python
 as the more simple example.
 
 With due respect to its developers and the persons who agree that
 the package tools could be upgraded, the mandatory
 usage of a front-end database to a file directory one
 is here viewd as mutt-only-mbox, registry-and-bsod rather
 than /etc/local/rc files, deprecation of 
 sed/grep/find/locate/.sh/portmaster/portmanager as tools to fixup/upgrade 
 the ports that are registered;
 ...
 I see concurrently too few tests on lower-end p2, p3 as to whether
 pkg can run with lesser memory machines (routers...) (pfsense)
 ...
 I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd,
 pfsense..) due to less-reliability, more-possibility of bugs..

 This is of some concern to me as well. A number of our utilities /
 scripts rely on checking /var/db/pkg as a means to test if a particular
 package is installed. This is often much faster than running the pkg_*
 commands, especially when we may be checking thousands of packages in a
 single run. It will be some work to adjust our utilities to using the
 various pkg commands now, but it can be done. What worries me is
 performance. If this is significantly slower, it may cause some issues
 on our end.
 Guys, please test it before you say anything. Otherwise it's going to
 be moved forward without you.


 
 Well, it was about time I got to doing a benchmark of this anyway :)
 
 I did quick benchmark of how one of our utilities parses through a list
 of 1k packages on a newer i5 system:
 
 First test, using /var/db/pkg/pkg check we have been doing:
 
 0.178s 0:00.31 54.8%
 0.123s 0:00.26 61.5%
 0.099s 0:00.15 60.0%
  
 Second test, using pkg info pkg:
 
 5.347s 0:11.41 91.7% 
 5.444s 0:11.52 91.3%
 5.878s 0:11.32 91.4%
 
 The pkg info command is quite a bit slower in this case, but 5 seconds
 isn't horrible.
 
 Now I ran the same benchmark on a slower 1.66gz Atom system, checking
 about 1200~ packages:
 
 First test, using /var/db/pkg/pkg check we have been doing:
 
 0.604s 0:00.76 86.8%
 0.622s 0:00.77 84.4%
 0.614s 0:00.73 90.4%
  
 Second test, using pkg info pkg:
 
 28.507s 0:54.80 99.1%
 28.282s 0:54.60 99.4%
 28.302s 0:54.52 99.4%
 
 Now this is what concerns me a bit. It took closer to 30 seconds, which
 is quite a while to wait, especially if a utility like ours has to run
 these checks when it starts up, to show the user whats installed / not
 installed on the system.
 
 The only way around It I've found is to do a quick pkg info on the
 entire DB, dump that to a list, then begin to grep through that list for
 each item, but it still takes 10~ seconds on the atom. That may be what
 I end up having to do, but it still stinks to go from a half a second
 startup, to 10 seconds each time. Any other ideas on how to do this
 faster with the new pkgng?
 

Hi Kris,

can you describe what exactly the script is doing.

Are you aware that you can feed direct SQL to pkg ?
$ echo 'select origin,name,version,comment from packages;' | pkg shell

At the beginning I was also a little skeptic, but even for older (slow) 
machines it works well here.
One note, on small systems keep an eye on /var/cache/pkg

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

Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone?

[olli hauer]

On 2012-08-21 13:45, Lev Serebryakov wrote:
 Hello, Lev.
 You wrote 21 августа 2012 г., 15:40:35:
 
 GC Try reverting r239356 -- if that works, then please let jhb@ know.
 LS   I'm confused by  this commit, because it seems (from comment alone),
 LS that  dhclient  will not work without devd anymore (with synchronous
 LS dhcp option in rc.conf).
 LS   Am I right?
  Also,  I  don't  like idea of removing IP address from interface when
 cable is unplugged. It was very disturbing behavior of Windows
 machines for years. I've unplug cable to change switch port for only a
 second and all connections are broken, even if one second later
 dhcpclient receive SAME lease! I don't like this. FreeBSD was very
 tolerant to unplugging cable for eons, and I (and not only me) like
 it. If I understand this change properly, it is no more the case :(
 

Oh, this is certainly exciting for clients in the backbone when a switch
will be reloaded because of firmware upgrade.

This behavior was a reason for me to run MS machines only virtual instead
using fix IP addresses (using ip arp inspection and dhcp snooping on the
whole network so fix IPs are a no-go)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Is the :u behaves normal or not (a bug) in the make?

[Olli Hauer]

On 2012-07-26 22:11, Jeremy Messenger wrote:
 Hello all,
 
 While I was working on add the :build/:run feature in the
 bsd.gnome.mk. I got a bug where it will running some dependencies got
 duplicate. Thanks to the make(1) that shows me the :u feature to get
 rid of the duplicates. But it doesn't exactly help unless I use the :O
 to get the words in order to make the :u works. I am not sure if it's
 just limited on how it works (normal) or it's a bug. Here's an example
 test:
 
 -
 USE_TEST= foo bar bar foobar foo
 USE_TEST1=foo bar bar foobar foo
 
 test:
   @${ECHO_CMD} USE_TEST:  ${USE_TEST:u}
   @${ECHO_CMD} USE_TEST1:  ${USE_TEST1:O:u}
 -
 
 Here's result:
 -
 # make test
 USE_TEST:  foo bar foobar foo
 USE_TEST1:  bar foo foobar
 -


It's normal, from man(1) make
 u  Remove adjacent duplicate words (like uniq(1)).

from man(1) uniq
 Repeated lines in the input will not be detected if they are
 not adjacent, so it may be necessary to sort the files first.

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

Re: [HEADS-UP] BSD sort is the default sort in -CURRENT

[olli hauer]

On 2012-06-27 08:04, Gabor Kovesdan wrote:
 Hi Folks,
 
 as I announced before, the default sort in -CURRENT has been changed
 to BSD sort.  Since the import, the reported minor bugs have been
 fixed and BSD sort has passed the portbuild test. If you encounter any
 problems or incompatibility with the old GNU version, please report.
 
 Gabor

Thanks, I'm running textproc/bsdsort now a view weeks as BASE replacement
on 8.3 and haven't seen any issues even on files with a view GB.

Are you planing to update the port with your latest version?


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

Re: [HEADS-UP] BSD sort is the default sort in -CURRENT

[olli hauer]

On 2012-06-27 21:02, Oleg Moskalenko wrote:
 Olli,
 
 Thanks for the feedback. We are working on some minor improvements and fixes, 
 when we are done we will commit 
 them to the ports and to the base system.
 
 If you see any problems and inconsistencies, please let us know ASAP so we 
 can fix that.
 
 Regards,
 Oleg

Hi Oleg,

until now I haven't found any issues, and I'm already in love with the new '-h' 
parameter which is really useful for some reporting scripts :)

Regards,
olli

 
 -Original Message-
 From: olli hauer [mailto:oha...@gmx.de]
 Sent: Wednesday, June 27, 2012 10:56 AM
 To: FreeBSD Current
 Cc: Gabor Kovesdan; Oleg Moskalenko
 Subject: Re: [HEADS-UP] BSD sort is the default sort in -CURRENT

 On 2012-06-27 08:04, Gabor Kovesdan wrote:
 Hi Folks,

 as I announced before, the default sort in -CURRENT has been changed
 to BSD sort.  Since the import, the reported minor bugs have been
 fixed and BSD sort has passed the portbuild test. If you encounter
 any
 problems or incompatibility with the old GNU version, please report.

 Gabor

 Thanks, I'm running textproc/bsdsort now a view weeks as BASE
 replacement
 on 8.3 and haven't seen any issues even on files with a view GB.

 Are you planing to update the port with your latest version?


 --
 Regards,
 olli
 

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

Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?

[Olli Hauer]

On 2012-03-06 17:09, O. Hartmann wrote:
 Hello.
 
 Well, I run on a brand new luxury box the newest Intel CPU
 Sandy-Brideg-E in its incarnation of the Core i7-X3930K on a decent ASUS
 workstation motherboard. The box is running FreeBSD 9.0-STABLE/amd64 at
 the moment.
 I discovered some problems with the SATA/AHCI interface. Since the
 peripherial hardware didn't change, except mainboard and CPU (and a lot
 of more memory), I guess FreeBSD 9.0-STABLE does have some issues with
 the new hardware. So I'd like to use FreeBSD 10.0-CURRENT/amd64, which I
 use successfully on an oldish two core Core2Duo box.
 
 VirtualBox, for instance, on the FBSD 9.0 box with the new hardware,
 stops working from time to time, the Windows-7 is getting stuck. The
 implication, that FreeBSD 9 can not handle the new hardware is wrong at
 that point, since even the VBox could have it's issues with the new 6
 core Sandy Bridge-E, but the issues with the SATA 6GB subsystems are
 real. Sometimes the system gets stuck.
 
 Well, I tried to switch by doing a svn switch in /usr/src, building a
 kernel, restarting the kernel in single user mode and then trying to
 build the world. At some point in /usr/src/share (I forgot were exactly,
 it was somewhere with lots of locale stuff), the buildworld process
 fails so I couldn't build a world.
 
 It wouldn't be bad if the switch isn't possible at the moment by
 simply switching the sources, but I'm still inclined to give the new
 hardware the propper new OS - hoping, that new driver will pay tribute
 to new hardware ...
 
 
 Thanks for your comments in advance,
 Oliver
 


Maybe you can reach your update goal faster...

From your mails to current I know you already have a box running FBSD 10.

My way to upgrade machines is to share / rsync /usr/src from a central
machine to all others, same for /usr/obj if the architectur match.
Do not forget to sync also make.conf/src.conf and runing mergemaster.

If the machine is alive after the fast upgrade you can experiment
with different src.conf / kernel settings.

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

Re: Migrating from FreeBSD 9.0-STABLE/amd to 10.0-CURRENT/amd64?

[Olli Hauer]

On 2012-03-06 22:23, O. Hartmann wrote:
 On 03/06/12 19:03, Olli Hauer wrote:
 On 2012-03-06 17:09, O. Hartmann wrote:
 Hello.

 Well, I run on a brand new luxury box the newest Intel CPU
 Sandy-Brideg-E in its incarnation of the Core i7-X3930K on a decent ASUS
 workstation motherboard. The box is running FreeBSD 9.0-STABLE/amd64 at
 the moment.
 I discovered some problems with the SATA/AHCI interface. Since the
 peripherial hardware didn't change, except mainboard and CPU (and a lot
 of more memory), I guess FreeBSD 9.0-STABLE does have some issues with
 the new hardware. So I'd like to use FreeBSD 10.0-CURRENT/amd64, which I
 use successfully on an oldish two core Core2Duo box.

 VirtualBox, for instance, on the FBSD 9.0 box with the new hardware,
 stops working from time to time, the Windows-7 is getting stuck. The
 implication, that FreeBSD 9 can not handle the new hardware is wrong at
 that point, since even the VBox could have it's issues with the new 6
 core Sandy Bridge-E, but the issues with the SATA 6GB subsystems are
 real. Sometimes the system gets stuck.

 Well, I tried to switch by doing a svn switch in /usr/src, building a
 kernel, restarting the kernel in single user mode and then trying to
 build the world. At some point in /usr/src/share (I forgot were exactly,
 it was somewhere with lots of locale stuff), the buildworld process
 fails so I couldn't build a world.

 It wouldn't be bad if the switch isn't possible at the moment by
 simply switching the sources, but I'm still inclined to give the new
 hardware the propper new OS - hoping, that new driver will pay tribute
 to new hardware ...


 Thanks for your comments in advance,
 Oliver



 Maybe you can reach your update goal faster...

 From your mails to current I know you already have a box running FBSD 10.

 My way to upgrade machines is to share / rsync /usr/src from a central
 machine to all others, same for /usr/obj if the architectur match.
 Do not forget to sync also make.conf/src.conf and runing mergemaster.

 If the machine is alive after the fast upgrade you can experiment
 with different src.conf / kernel settings.

 
 
 Well, in my case one box is at home (the FBSD 10.0-CUR/amd64) and
 switched off ... the box which is supposed to be updated is in my lab
 and still in front of me and at the moment I see no chance to switch the
 other box on ;-)
 
 Well, I thought I do it the hard way - having a running system and
 carefully migrate ... The new hardware is trmendously fast, so compiling
 the whole bunch of ports (~ 1000) will take not that long.
 
 But at the moment I get plagued by an error when make buildworld ...
 

Maybe someone can help / has an idea if you share the issue ...
All we have at the moment is that you tried to switch /usr/src
and buildworld fails.

If you can remember the svn version you are running at home.
If you know time where you have checked out the sources at home
http://svnweb.freebsd.org/base/ can help to find the rev. num.

--
Regards,
olli



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

Re: FreeBSD9 ifnet + Member Function void (*if_watchdog)(struct ifnet *ifp)

[Olli Hauer]

On 2011-08-01 08:33, Sergey Kandaurov wrote:
 On 1 August 2011 03:09, Olli Hauer oha...@freebsd.org wrote:
 Hi,

 I just tried to build VMware modules for FreeBSD9-BETA1 and noticed
 the ifnet Member Function

  void (*if_watchdog)(struct ifnet *ifp)

 was removed from net/if_var.h.

 Is there a suggested replacement?
 
 Per-ifnet watchdogs were transformed to private per-softc callout timer
 in earlier 9.x. See this thread for details:
 http://lists.freebsd.org/pipermail/freebsd-net/2009-November/023677.html
 

 PS:
 The man page for ifnet(9) does not reflect the remove of this
 (now missing) Member Function.
 
 It is massively outdated. I plan to update it some day when I get
 some more spare time/review.
 

Ahh, thanks for the hint!

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

FreeBSD9 ifnet + Member Function void (*if_watchdog)(struct ifnet *ifp)

[Olli Hauer]

Hi,

I just tried to build VMware modules for FreeBSD9-BETA1 and noticed
the ifnet Member Function

  void (*if_watchdog)(struct ifnet *ifp)

was removed from net/if_var.h.

Is there a suggested replacement?

PS:
The man page for ifnet(9) does not reflect the remove of this
(now missing) Member Function.

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