Re: # portmaster -r pixman fails with !#/bin/sh list too long

[Lowell Gilbert]

Antonio Olivares  writes:

> I tried your advice with the -R option, it worked, but for only pixman
> the other ports that depend on it don't get rebuilt :(
>
> I try to use -x 'texlive-*' but it does not work :(
> I get
>
> Could not execute shell
> "/usr/ports/Mk/bsd.port.mk",  line 1192:  warning "/usr/bin/awk
> '/^#define[[:blank:]]FreeBSD_version/ {print $3}
>  /usr/local/sbin/portmaster:  rm: Argument list too long
>
> and it justs sits there.  Out of 3 machines only 1 is working because
> I overlooked the pixman update entry in /usr/src/UPDATING :(
>
> Please advice me as to how to get the desktop working again on these
> machines.  I did not want to shoot myself in the foot but I did so :(

Try the '-R' again; it may get a bit farther each time. 

You can always recover by removing some of the ports and reinstalling
them after the remaining ports are updated. You're going to have to
rebuild a huge number of ports anyway, so this is not very different
from using portmaster on everything.

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

Re: # portmaster -r pixman fails with !#/bin/sh list too long

[Lowell Gilbert]

Antonio Olivares  writes:

> Dear folks,
>
> In updating ports I encounter above issue and cannot proceed.
>
> 20130929:
>   AFFECTS: users of x11/pixman
>   AUTHOR: zeis...@freebsd.org
>
>   The library version of x11/pixman has changed, and portrevision has
>   been bumped in all dependent ports.  If you have external software that
>   depends on pixman, this software needs to be recompiled.
>   To recompile all software dependent on pixman, run:
>
>   # portmaster -r pixman
>   or
>   # portupgrade -rf pixman
>
> The messages are that a pkg texlive-ub* and that #!/bin/sh list
> too long.  I try to run
> # portmaster -d -r pixman -x 'texlive-*'
> but it still fails in the same place :(

I continued with portmaster's "-R" option and got a lot further. You
could try either that or the command line that portmaster suggests 
when it bails out. 

> I am using texlive-freebsd from Romain Tartiere's googlecode page in
> case it is important.  Please advice me so I can succeed to fix these
> issue.  I lost X because I failed to read the /usr/src/UPDATING advice
> and then I realized that I overlooked this :(

I don't think that texlive is relevant; if you continue the process
instead of starting from scratch, you'll probably get farther. 

I'd prefer to actually debug the problem at its root, but it's the
middle of the night and I don't seem to have enough brain cells awake 
to figure anything out.

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

Re: Vulnerability

[Lowell Gilbert]

Jerry  writes:

> Has this been rectified:
> 

If you read the page at that link, you will find the answer.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: persistence in freeBSD

[Lowell Gilbert]

atar  writes:
>
> What does the '-u' option do? I've not find in the 'mount' man page
> any explanation on this option.

The man page includes:

 -u  The -u flag indicates that the status of an already mounted file
 system should be changed.  Any of the options discussed above
 (the -o option) may be changed; also a file system can be changed
 from read-only to read-write or vice versa.  An attempt to change
 from read-write to read-only will fail if any files on the file
 system are currently open for writing unless the -f flag is also
 specified.  The set of options is determined by applying the
 options specified in the argument to -o and finally applying the
 -r or -w option.

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

Re: persistence in freeBSD

[Lowell Gilbert]

atar  writes:

> Will the 'mount -o rw /' command work although the filesystem has
> already been mounted as readonly?

You'll need the "-u" option as well.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Support

[Lowell Gilbert]

sopo...@promonitor.com.mx writes:

> Hello, i have a "Server" whith the screen information like attach
> Server.jpg, assumed that are to save the record of IP cameras like
> network folder (see network.jpg), but another IP cameras need a FTP
> folder and other that folder don't have blank spaces.
>
> If possible make this (FTP and other folder network) in the "server"
> whit freeBSD, the person what config and install the machine isn't
> more available so any have the information by they work in this
> plataform or make changes, so i need makes this adds at they exist.

The FreeBSD Handbook includes a section on configuring ftpd. 
There's also a manual for ftpd itself (see 
http://www.freebsd.org/cgi/man.cgi?query=ftpd).
Is that what you're looking for? 

Normally, an FTP client can use any directory ("folder") on the server
if it's logging in as a normal user, or any directory under the home
directory if it's logging in as an "anonymous" user. These details are
covered in the ftpd manual page. You shouldn't have any trouble creating
such a directory with no spaces in its name.

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

Re: The logo at boot (Nakatomi Socrates BSD 9.2)

[Lowell Gilbert]

Patrick Dung  writes:

> Do you know what is this logo means, or the story behind it?
> I thought the BSD daemon (logo) has been around for many years in the past.

It's a movie reference ("Die Hard").

The Beastie logo is still there, in the /boot directory, if you want it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Network startup with age Ethernet device

[Lowell Gilbert]

Olivier Nicole  writes:

> I want to set-up a small server from an Asus P5L-MX motherboard.
>
> It has an onboard gigabit Ethrnet that works with the driver age. 
>
> Problem is that at boot, I experience the interface to go up and down a
> couple of times, and it is usually down when Apache try to start, so
> Apache would not start (nor ntpd).
>
> I resolved to add a 5 seconds sleep in /etc/rc.d/netif but there may be
> a more elegant way to solve that.

Have you tried using netwait? 
I think that would involve putting enable_netwait in rc.conf, and
configuring an address for it to check; probably the gateway would be
good enough.

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

Re: Potential Vulnerabilities list on US Cert

[Lowell Gilbert]

Jerry  writes:

> I usually check the US Cert listing every week to see if anything
> interesting is listed. 
>
> I discovered that there are two listings for FreeBSD:
>
> 1) http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-3077
>
> 2) http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-5209
>
> I just thought that users should be aware of this.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Potential Vulnerabilities list on US Cert

[Lowell Gilbert]

These are the sctp vulnerabilitiese from a week or two back.

Anyone following the Security Advisories can safely ignore these; they
were issued after the relevant advisories and patches, and consist of
nothing but pointers to the previous information.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Saving scanned document

[Lowell Gilbert]

Jerry  writes:

> On Tue, 23 Jul 2013 15:50:00 -0400
> Lowell Gilbert articulated:
>
>> Jerry  writes:
>> 
>> > Does anyone know of a way of getting the scanner to "see" the
>> > FreeBSD machine and saving a file to it?
>> 
>> I'm not sure I correctly understand your intention, but maybe Samba is
>> what you're looking for?
>
> Samba is working fine and all of the other computers on the network
> can see each other and the printer/scanner. The problem is that the
> scanner does not see the FreeBSD machine.

I'm going to make some guesses here, because your information is still
sketchy. Specifically, I'm assuming that you have Samba running on the
FreeBSD machine, and that the other (Windows) computers can write files
to the Samba shares on the FreeBSD machine, but that some kind of GUI
comes up when you scan, and offers Windows machines as possible
destination, but doesn't offer the FreeBSD machine.

Assuming all of that is correct, this is a Samba-tuning question, and
you may need a Samba expert. But first you can check whether the
machines agree on the master browser, and whether there's an Active
Directory lookup occurring in each (Windows machine vs. printer-scanner)
case. Are these hosts all on the same IP subnet?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Saving scanned document

[Lowell Gilbert]

Jerry  writes:

> Does anyone know of a way of getting the scanner to "see" the FreeBSD
> machine and saving a file to it?

I'm not sure I correctly understand your intention, but maybe Samba is
what you're looking for?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: chrome does not refresh screen content

[Lowell Gilbert]

CeDeROM  writes:

>>> Do you have kern.ipc.shm_allow_removed set?
>>> http://svnweb.freebsd.org/ports/head/www/chromium/pkg-message?revision=318200
>>
>> Thank you George! That was not set on my system, will try and let you
>> know the results!

That's in the pkg message.

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

Re: A very 'trivial' question about /root

[Lowell Gilbert]

Polytropon  writes:

> On Fri, 28 Jun 2013 15:25:44 +0200, Julian H. Stacey wrote:
>> ( I'd guess OpenBSD might go for a tighter /root though, as they're
>>   supposedly keen on security. )
>
> Currently I've got no OpenBSD installation at hand to verify,
> but I _assume_ they still have the same defaults as FreeBSD
> regarding permissions of /root.

That's correct.

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

Re: A very 'trivial' question about /root

[Lowell Gilbert]

ASV  writes:

> This is a very 'trivial' question but it's bugging me since quite a
> while now so I gotta ask.
>
> There's any reason (and should be a fairly good one) why the /root
> directory permissions by default are set to 755 (for sure on releases
> 8.0/8.1/9.0/9.1)

By default, there's nothing secret in there, so 755 makes sense to me.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: FreeBSD maximum password length

[Lowell Gilbert]

takCoder  writes:

> As i googled it,  there is no maximum limitations for users' password
> length by default.. But we may use *pam_passwdqc* module with *max* option
> to check it when required.
>
> And i've heard that no-maximum-limits for passwords length is only possible
> when we keep them in encrypted form not as plain text, which i think is
> matched with FreeBSD behavior.

Is plain-text passwords even a supported behaviour? I didn't think it was.

> Am i right? Is that all about maximum password length in FreeBSD? Did i
> miss something??

_PASSWORD_LEN is the defined limit. It's 128 characters by default but
could be changed at compile time. There may be other limits, such as in
various versions of NIS.

> Thank you for all your helps and ideas :)

I'm not sure I understand what you're doing, so I don't have any real
advice, but I don't see why 128 characters would be that hard to deal
with. 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: buildworld selectively?

[Lowell Gilbert]

Walter Hurry  writes:

> Ah, src.conf. That's what I missed!. Thank you so much Gary, and sorry if 
> it was a silly question.

Bear in mind that you're only going to be able to shave a small fraction
off the build time. by excluding parts of the build. The 'games' section
in particular has almost nothing in it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: USB can't mount msdosfs drive

[Lowell Gilbert]

"Joseph Mays"  writes:

>> If you do a ls /dev/da* What does it show.
>
> root@warehouse:/root # ls -la /dev/da*
> crw-r-  1 root  operator0, 123 Jun  4 17:08 /dev/da0
> crw-r-  1 root  operator0, 124 Jun  4 17:08 /dev/da0s1
> crw-r-  1 root  operator0, 131 Jun  4 17:08 /dev/da1
> crw-r-  1 root  operator0, 132 Jun  4 17:08 /dev/da1s1
> crw-r-  1 root  operator0, 138 Jun  4 17:08 /dev/da2
> crw-r-  1 root  operator0, 108 Jun  5 15:11 /dev/da2s1
> crw-r-  1 root  operator0, 154 Jun  4 17:08 /dev/da3
> crw-r-  1 root  operator0, 155 Jun  4 17:08 /dev/da3s1
> crw-r-  1 root  operator0, 152 Jun  4 12:08 /dev/da3s2

Just checking the obvious: you're sure this particular disk is showing
up as da2, right?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Any arp table size limitations?

[Lowell Gilbert]

Peter Andreev  writes:

> We are connecting to an IXP, they have tested our FreeBSD 9.1 server and
> said we can store only about 600 MACs simultaneously. So I'd like to ask if
> there is any arp table size limitations and if so, how we can increase the
> limit?

I looked at the code and there don't seem to be any arbitrary
limits. The code isn't optimized for really large numbers of entries,
but 600 isn't what I'd consider large in this context.

I ran a simple shell script and had no problems entering many thousands
of static ARP entries, so my interpretation from reading the code isn't
horribly wrong. I think you need to find out what kind of problems they
ran into at 600 entries. 

As a (maybe-irrelevant) side point, I don't know what you mean by IXP,
since in my background the term means "Internet eXchange Point," and
isn't likely to get anywhere close to 600 ARP entries on a single
subnet. 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: looking for command to display default route ip address

[Lowell Gilbert]

Joe  writes:

> Hello list
>
> How do I find the ip address of the default route?

The next-hop address, or the local address? 
The former can be easily parsed out of the netstat(1) output,
the latter isn't necessarily unique.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Compiling a lean kernel of 9.1 p3

[Lowell Gilbert]

Tommy Pham  writes:

> On Wed, May 15, 2013 at 10:43 AM, Tommy Pham  wrote:
>
>> Hi everyone,
>>
>> I installed 9.1 from DVD with src only and did 'freebsd-update fetch
>> install'.  Then I proceed to compile the lean kernel.  I'm unable to
>> compile a lean (no SCSI, RAID, sound, USB, Firewire, NICs) kernel of 9.1 p3
>> and without lib32 support.  I only needed SATA disk and em NIC support.
>>  The kernel compiled without errors.  However, on boot, it freezes after
>> the menu screen.  My make.conf only have added (from default
>> /usr/share/examples/etc):
>>
>> KERNCONF=custom
>> CPUTYPE=?opteron
>>
>> I have no problem booting from GENERIC built kernel and buildworld with
>> that make.conf.   Could someone please tell me how can I troubleshoot this?
>>
>> TIA,
>> Tommy
>>
>
> Hi again,
>
> I said that wrong... I meant that I was able to compile OK but unable to
> boot with a lean kernel.  I was able to boot buildworld and buildkernel of
> GENERIC.

The way to do this is to use a binary search. Start with a working
(GENERIC) kernel, then add half your changes in. If it fails, then you
know the problem is in the set of changes that you included. If it
works, the problem is in the set of changes you didn't include. It's a
little more complicated because there may well be a dependency, where
two options need to both be included or left out, but I'm sure you get
the idea.

Alternatively, you could include kernel debugging and see where the CPU
is executing after the hang. But this requires more programming knowledge.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Disable FIFO on UART

[Lowell Gilbert]

Miguel Barbosa Gonçalves  writes:

> Back in FreeBSD 7 there was a flag to disable the FIFO on the sio
[...]
> Now with FreeBSD 8 which uses the UART device driver there's no option for 
> that.
>
> I am looking to reduce the jitter I am getting on the serial port when
> connecting a GPS to the server.
>
> Can anyone help?

It looks do-able, although the interface is a bit more abstract and
covers a wider variety of hardware. You would probably need to contact
whoever's working on that driver these days.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: 9.1 Postfix problem

[Lowell Gilbert]

Paul Kraus  writes:

>   That was exactly the problem. I knew it was in the
> installation configuration *somewhere*, but I just could not find
> it. Thanks.
>
>   Should I report this as a bug in the postfix port ?

No need. Looks like sahil@ has already fixed it.

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

Re: Procmail Decoding Mime Messages

[Lowell Gilbert]

Polytropon  writes:

> On Wed, 24 Apr 2013 16:07:35 -0500, Martin McCormick wrote:
>>  Is there a filter that one can run in procmail in which
>> base64 encoded data go in and text comes out so one can allow
>> procmailrc to do its work?
>> [...]
>>  Is there anything which will take a raw email message
>> and spit out linear strings which can be processed like normal
>> text?
>
> I think this is possible with uudecode, in this case b64decode.
> See "man uuencode" for more information.

uuencode predates MIME. Although there are MIME types defined for it,
the base-system tools don't handle the MIME headers or section marking. 

For this purpose, a MIME-aware tool (such as ripmime, or metamail, or
mmencode) will be much more useful as part of an automated filtering
system.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Diskless question

[Lowell Gilbert]

Arthur Chance  writes:

> On 04/24/13 14:07, Lowell Gilbert wrote:
>
> No, that's from /etc/passwd which never shows any real password
> information. The true password field is in /etc/master.passwd and I'm
> not going to ask anyone to show that here. However, the OP should
> check it's got a valid looking field value rather than just a '*'

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

Re: Diskless question

[Lowell Gilbert]

Bernt Hansson  writes:

> 2013-04-24 12:30, Arthur Chance skrev:
>> On 04/24/13 09:18, Bernt Hansson wrote:
>>> Hello list!
>>>
>>> I have set up a diskless machine with 8.3-stable and i as a user can log
>>> in, but when I try to log in as root it won't work. How to resolv that
>>> issue. I have tried with and without password but the computer said no.
>>
>> How did it say no? What does the entry for root in /etc/passwd say?
>
> $su
> Sorry
>
> root:*:0:0:Charlie &:/root:/bin/csh
   ^
  / \

Root has no valid password. 

You'll need to go into single-user mode and either give it one or
install sudo and add your regular user to the sudoers file.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: restore /usr dump on two hard disk parallel y

[Lowell Gilbert]

s m  writes:

> i'm trying to restore DUMP file for partition /usr on tow hard disk
> parallel y. these two hard are connected to my system (i have freebsd8.2).
> i use  restore command and it uses /tmp directory to restore dump. in
> restoring dump process, two hard disks try to use /tmp directory of my
> system. therefore conflict happened and restore command return error.
> i try to use TMPDIR and define another tmp directory for one of my hard
> disk but it does not identify it and use my system tmp directory yet.
> please let me know if using TMPDIR is a good idea and how i can use it. if
> not, how i can restore /usr dump file on two hard disk parallel y?

What do you want to do exactly? 

Do you want both disks together to be your new /usr/partition? In that
case, you want to set up some kind of RAID system with the two
disks. Start with the GEOM section in the handbook.

Do you want to end up with two partitions, each holding part of what the
/usr backup contains?  If that's what you're after, then the best
approach is probably to pick one subdirectory of /usr (/usr/local would
be an obvious choice) and restore everything *but* that to one of your
disks, then mount the other disk on the subdirectory and restore the
rest onto there. 

If your problem is just that the two restore operations are stepping on
each other's temporary files, then TMPDIR *should* take care of
that. You could show us more detail of how you run the restore
operations, or just run them one at a time instead of in parallel. 

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

Re: 9.1 Postfix problem

[Lowell Gilbert]

Paul Kraus  writes:

>   When building postfix under 91. I am running into an odd
> problem. I use the INST_BASE option, which seems to cause the problem
> (it worked fine with 9.0). The 'make' goes fine, but the 'make
> install' fails when trying to install the startup script to
> /usr/etc/rc.d instead of /etc/rc.d. It works fine if INST-BASE is
> disabled. I looked through the Makefile but could not suss out how
> that difference in configuration was actually causing the problem.
>
>   Has anyone else run into this problem and what was the fix (or did you 
> just install into /usr/local) ?

I use /usr/local, but this seems to be a typo in the last checkin, 
which changed the internal names of the port options to our brave new
naming scheme. 

If you look in the Makefile clause for installing to base, renaming the
option itself went correctly, but both halves of the '.if' now invoke
USE_RC_SUBR. That's correct for PREFIX, but for installing into base
should be USE_RCORDER instead.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: none

[Lowell Gilbert]

Jerry  writes:

> On Fri, 12 Apr 2013 14:07:30 -0400
> Lowell Gilbert articulated:

No, I didn't. It was part of an attachment in my message.

>> You'll need to run -CURRENT instead of 9.1, and all the caveats that
>> apply.  You'll also need the special HAL that hasn't yet been commited
>> to -CURRENT.  There are instructions on the freebsd-wireless mailing
>> list.  I'm using that exact card right now.
>
> Really off-topic, but HAL is now deprecated on many modern systems. Why
> is FreeBSD continuing to use it? It is being replaced by "udev". You
> would think that FreeBSD-10 would be a perfect time to put HAL to bed
> and take a more modern approach.

udev is tightly tied to the Linux kernel. I understand why you would
refer to Linux as "many modern systems," but it's really not available
on anything non-Linux, and it's so tightly tied to the Linux kernel
device implementation that there's no reasonable way it could be. 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: none

[Lowell Gilbert]

 writes:

> Good afternoon, dear FreeBSD enthusiasts.  Is there anyone who has
> attempted to install a TP-LINK TL-WDN4800 p.c.i.-express wireless
> network interface card?  I am using FreeBSD 9.1 on a Hewlett-Packard
> xw4400 workstation.  The card works perfectly under Windows XP.
> However, it seems that the FreeBSD operating system does not even
> recognize the existence of the device; at least, I cannot find any
> mention of it in the dmesg.boot file.  Any and all comments or
> suggestions will be appreciated.  Also, many thanks to those of you
> who have responded to my previous inquiries.  Yours truly, Newby Lee
>
> P.S.  I failed to mention that the integrated circuit is an Atheros AR9380.

When you asked this yesterday, you got the following response:
--- Begin Message ---
[1. text/plain]

You'll need to run -CURRENT instead of 9.1, and all the caveats that
apply.  You'll also need the special HAL that hasn't yet been commited
to -CURRENT.  There are instructions on the freebsd-wireless mailing
list.  I'm using that exact card right now.

Run `pciconf -lv` and you should see it, but there's no driver in 9.1.

On 4/10/2013 3:39 PM, leeoliveshackelf...@surewest.net wrote:
> Good afternoon, dear FreeBSd enthusiasts.  Is there anyone who has
> attempted to install a TP-LINK TL-WDN4800 p.c.i.-express wireless
> network interface card?  I am using FreeBSD 9.1 on a Hewlett-Packard
> xw4400 workstation.  The card works perfectly under Windows XP.
> However, it seems that the FreeBSD operating system does not even
> recognize the existence of the device; at least, I cannot find any
> mention of it in the dmesg.boot file.  Any and all comments or
> suggestions will be appreciated.  Also, many thanks to those of you
> who have responded to my previous inquiries.  Yours truly, Newby Lee
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>

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

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

Re: Youtube & Flash Videos broken?

[Lowell Gilbert]

Harald Weis  writes:

> On Sun, Apr 07, 2013 at 12:09:32AM +0200, Polytropon wrote:
>  
>  > If it's just about YouTube video, why not use youtube-dl and
>  > mplayer? I haven't tested it for those particular two videos,
>  > but it tends to work for everything. :-)
>  
> Can you please help me how to find the right URLs for youtube-dl ?
>
> For example on
> http://www.youtube.com/user/ConcertosLive/videos
>
> When I copy URLs with mouse in opera I always get
> "youtube-dl: No match."
>
> (opera and flash work fine for playing and also for downloading the
> the ogg file)
>
> I definitely prefer the command line tool.
> Getting rid of flash would be a tremendous relief.

Right-click on one of the video icons, select "copy link address" and
the cut buffer will contain the URL. Depending on your shell you may
need to protect some of the characters from being interpreted.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Problem making software distros

[Lowell Gilbert]

"Don O'Neil"  writes:

> I've got an older FreeBSD 6.1 install that will no longer allow me to build
> any software distributions. Any time I try to do a 'configure', the
> configure seems to run fine, then I get a "config.status: error: cannot find
> input file:". This has happened on several packages from several different
> sources.
>
>  
>
> Any ideas as to what could be causing this? Is one of my binaries make
> corrupted possibly?

Unlikely to be a corrupted binary. Much more likely to be that configure
scripts are trying to use a file as input for their testing, and not
finding it. Tracking down *what* file they want shouldn't be too much
effort. If it turns out to be, you can always update to something recent
enough to be supported, but that's probably unnecessary for this problem.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Proper way to update ports with svn

[Lowell Gilbert]

Andre Goree  writes:

> I seem to have to run 'make index' in /usr/ports after I've run 'svn up
> /usr/ports' in order to see which ports need to be updated using
> 'portversion'.  This doesn't seem correct...and if so portsnap would
> seem like a much better tool.  Perhaps I should be running 'make
> fetchindex' instead?  I'm sure I've read about the correct way to do so,
> but it doesn't appear to be here:
> https://wiki.freebsd.org/PortsSubversionPrimer

Subversion is not relevant; it has not changed the use of the
index file. 'portversion' is part of the portupgrade port, and
requires not just an index but its own database version of the
index file. Building your own index will be slightly more
accurate for what is actually on your box, but fetching it will
be much faster and nearly always accurate enough.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: any 9.1-RELEASE-p1 to 10.0-CURRENT howtos?

[Lowell Gilbert]

Antonio Olivares  writes:

> On one of my machines I cannot get it to update ports, most fail with
> gettext.  I tried some options like disabling Native Language Support
> in binutils, but it still fails.  I deleted all the ports and am
> looking at starting from scratch again, but this time move to CLANG
> and build world and install world and not USE gcc and GNU anymore (on
> the machine which gettext fails).  Is there a nice howto as to how to
> do this?
> How can it be done in easy steps and then try to track current?

Current isn't necessary, although it often has slightly newer versions
of the related tools. Clang will work fine on recent 9.x (I don't know
when it was imported, so it may need something more recent than
9.1). Furthermore, it will support building the world and ports, as
detailed in:
https://wiki.freebsd.org/BuildingFreeBSDWithClang

> I am aware that I would be on my own if I track current, but I want to
> test many programs to see if they would build without GCC and with
> CLANG only and report back to the developers and let them know of
> issues.

You are not entirely on your own with current, but you are expected to
more of the heavy lifting when a problem comes up that doesn't happen
for other people.

You actually have a number of choices that should work for you. You can
run current, which probably won't be very difficult (but nobody's going
to guarantee that). You can run RELENG_9 using clang as the default
compiler. Or you could use a jail to build with clang when the host
system builds with gcc. And I've most likely overlooked other
possibilities. 

If you are really starting from scratch on a particular machine, then a
clean install is worth considering; it guarantees that you're not
bringing along the effects of mistakes made previously on the system. If
the system is also needed stable for other purposes, then doing your
experiments in a jail may be your easiest path (a jail may even be
overkill; a chroot will handle it for some purposes). 

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

Re: freebsd-hack...@freebsd.org

[Lowell Gilbert]

budsz  writes:

> I want ask about error in `dmesg` output "remove Bump sched buckets to
> 64 (was 0)"
> in FreeBSD 8.3 STABLE version. Where's the code lines should be remove 
> (safety)?

That message isn't in RELENG_9, so I can't give you details. It's
probably resizing a dummynet queue, so it's likely to be in one of the c
files in /usr/src/sys/netpfil/ipfw/. Removing the print statment is
*probably* safe, but will leave you with less information if something
actually goes wrong with allocating buckets the next time you add a new
queue. 

Or you could update to something more recent, where that specific
message isn't present at all.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Crash when trying to rsync to external NTFS-formatted HD

[Lowell Gilbert]

Leslie Jensen  writes:

> I'm trying the following on my 9.1-RELEASE #0 system:
>
> Mounting the external HD
> ntfs-3g /dev/da0s1 /mnt/backup/
>
> And doing
> rsync -av /home/les /mnt/backup/BSD_backup/
>
>
> I get "Building incremental file list" for about one minute then my
> system freezes and reboots.
>
> I'm aware that NTFS might be the culprit. I have chosen it for
> convenience and the possibility to move my data to machines without
> FreeBSD.
>
> Manually copying of files one by one works.

Yes, it definitely sounds like fuse is corrupting something in the
kernel. Could be tricky to debug, and forcing a kernel dump would be the
first step.

The traditional most-portable way of moving files is to tar(1) onto a
raw device rather than having any filesystem at all. 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: stupid portmaster question

[Lowell Gilbert]

Aryeh Friedman  writes:

> How do I tell portmaster -ad to ignore certain ports because they are
> broken such as editors/libreoffice is currently marked as (I am sure this
> will change soon)

Your direct question was already answered, but note that libreoffice is
not broken overall, just with certain options that probably won't affect
its operation for you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Client Authentication

[Lowell Gilbert]

Doug Hardie  writes:

> That is an interesting idea, but unfortunately our users tend to
> travel a lot and need to be able to access mail from anywhere.  Also,
> static IPs can get quite expensive from some ISPs.  Our users are
> pretty much on fixed incomes and any expense is a hardship for them.

I've been thinking about setting up certificates for pretty much the
same reason, but I haven't gotten around to it yet. My standing
impression is that the setup is mostly specific to the mail server,
which in my case is currently dovecot. 

Regardless of what else you do, there are some defensive things you
could do to take some of the pressure off. They won't be a solution, but
they might make your life easier while you work on a solution. Port
knocking would make it harder for the attackers to get through to try
passwords, and it's fairly easy to install on any particular type of
client. With the variety of clients you have to deal with, the
cumulative effort may be overwhelming, but it's at least worth a
thought. Another thing to try would be temporarily blocking any IP
address that tries several different user names in a short period of
time. Again, these kinds of things won't solve your problem, but they
may reduce the intensity of the attack.

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

Re: No sound with Thinkpad X60

[Lowell Gilbert]

Jerry  writes:

> On Fri, 22 Mar 2013 06:28:57 +0100
> Bernt Hansson articulated:
>
>> 2013-03-22 00:42, Peter Harrison skrev:
>> 
>> Put this in your /boot/loader.conf and report back.
>> 
>> hw.snd.default_unit="0"
>> 
>> Test with other nubers if 0 do not work.
>
> Using an nVidia card, I had to do the following:
>
> /etc/sysctl.conf
>   hw.snd.default_unit=4
>
> Rebooted and the sound worked. I never found any truly accurate
> information on it, it was basically just a trail and error experiment.
> And YES, it sucks that in all to many cases, sound doesn't "just work".

You don't actually need to reboot for each trial. Running sysctl(8) from
the command line will do. And /dev/sndstat would probably tell you the
right value to try. These things are covered in the Handbook..
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: w and who don't list users in FreeBSD 9.0 and 9.1

[Lowell Gilbert]

Istvan Gabor  writes:

> 2. I found that users are reported if they are logged in on terminal session 
> or through ssh.
> User who is logged in through KDM3 into KDE3 session is not shown.
> Does this change the above diagnosis? Can it be something else, maybe?

Well, if they don't start a login shell, they're not going to show up as
logged in. Most terminal programs have an option to start them as login
shells, but I don't know KDE well enough to know what the normal
practice there would be.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Problem with news/pan

[Lowell Gilbert]

Walter Hurry  writes:

> This port (pan-0.139_1) will again not compile on 9.1-RELEASE (amd64).

When did you last try it? 

It was last updated Saturday, and it builds fine for me.

If it's still failing, post the error messages.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Can an ISO file be mounted from /etc/fstab at boot?

[Lowell Gilbert]

Oscar Hodgson  writes:

> I'm pretty sure the answer is "no, just write a local rc script to do
> that", but thought I'd check.
>
> Can't see any hint of that capability in the handbook or fstab(5).
>
> Really just looking for a single point of management for file systems 

I don't see a way offhand. You need to do the mdconfig before you can
mount, and I don't think that can be done inside of fstab. 

I think that adding such a capability to mount(8) as a program option
would be a fairly minor hack.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Can't fetch boost-jam

[Lowell Gilbert]

Open Slate  writes:

> For several days I have not been able to update my ports due to fetch
> errors. Right now the first port portupgrade wants to update is
> devel/boost-jam. Here is the tail of the output of make issued in
> /usr/ports/devel/boost-jam:

You seem to have overridden a master site variable; downloading it from
sourceforge (as the port does by default) works fine.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: configure recursively and build question

[Lowell Gilbert]

Istvan Gabor  writes:

> 2013. március 12. 21:17 napon Lowell Gilbert 
>  írta:
>> 
>> Second, config-recursive only does the configuration of the port
>> options.
>
> Then I misunderstood the handbook, chich says:
>
> "To avoid this when there are many dependencies, first run make 
> config-recursive
> to do the configuration in one batch."
>
> I understood this as the configuration is done on all the dependencies as 
> well.

You understood the handbook correctly. My comment was poorly worded and
unnecessary (I was actually making the same point as in #4.

The word "options" can mean slightly different things. The port's
framework may define options, which the port will require you to choose
among before building its software. The program being built may
*additionally* require user input for building, and the port framework
(in particular, "make config") can't store those choices. This is
unusual, but some common ports do it (for example, ghostscript is one).

> The handbook also writes:
>
> "Tip: When using config-recursive, the list of ports to configure are 
> gathered by the
> all-depends-list make(1) target. It is often recommended to run make 
> config-recursive
> until all dependent ports options have been defined, and ports options 
> dialog(1) screens
> no longer appear, to be certain all ports options have been configured as 
> intended."
>
> Does this mean if I run config-recursive several times in a raw, all the 
> dependencies will
> be configured?

This is a slightly different issue. Changing a port's options may change
its dependencies, so another round of config-recursive  might be needed
to config the new dependencies.

> ...
>
>> Fourth (and, you'll be glad to hear, finally) some ports are interactive
>> for reasons beyond options. See the manual for ports(7), noting the
>> environment variables INTERACTIVE and BATCH.
>
> I will look at this.
>
>> > Second, after I've done a configure-recursive, how can I start it over 
>> > from scratch in case
>> > I want to change some config option? If I reissue make configure-recursive,
>> > I get only no configuration needed messages.
>> 
>> If you really want to start from scratch, you can use
>> "rmconfig-recursive" on the dependent port.
>
> Yes I meant only the given port and its dependencies, not the all ports.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: configure recursively and build question

[Lowell Gilbert]

Istvan Gabor  writes:

> As there are no compiled FreeBSD 9.1 packages for pkg_tools I decided to 
> build them.
> Last I started to build kde3. First I issued make configure-recursive in
> /usr/ports/x11/kde3, then make install clean, and left the computer for 
> overnight to work.
> I expected a successful build by the morning but instead I found a screen 
> requiring some
> config options (for apache). I selected the options and the build went on.
> But later other config windows came up, so far for mysqlclient, sane-backends,
> tk, tcl, libxine and sdl. So my question are:
>
> What is configure-recursive good for then? I thought it is for preventing 
> interactions
> during the build process. Ho can I really configure everything in one step 
> and leave
> the computer alone?

First of all, I think you mean config-recursive. 

Second, config-recursive only does the configuration of the port
options.

Third, handling of ports options has recently been changed to a new
system.  See ; intended
for porters but revealing much internal workings. There may be some bugs
(I think I've noticed a few but haven't looked much into it.  You might
want to ask the ports list about that.

Fourth (and, you'll be glad to hear, finally) some ports are interactive
for reasons beyond options. See the manual for ports(7), noting the
environment variables INTERACTIVE and BATCH.

> Second, after I've done a configure-recursive, how can I start it over from 
> scratch in case
> I want to change some config option? If I reissue make configure-recursive,
> I get only no configuration needed messages.

If you really want to start from scratch, you can use
"rmconfig-recursive" on the dependent port. Or to start *all* ports from
scratch, remove the contents of /var/db/ports/.

But generally you won't want to do that. What you really want is most
likely to be for one particular port, or for its full tree of
dependencies. In the first case, go to that port's directory and just do
a "make config" there. In the second case, go to that port's directory
and use "make showconfig-recursive" to figure out which ports actually
need to be changed.

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

Re: iconv issue (Re: Pan-0.139 won't compile)

[Lowell Gilbert]

And it's already been fixed.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: iconv issue (Re: Pan-0.139 won't compile)

[Lowell Gilbert]

Lowell Gilbert  writes:

> I'll put in a PR, because I won't have a chance to look more at this
> today. 

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

iconv issue (Re: Pan-0.139 won't compile)

[Lowell Gilbert]

Walter Hurry  writes:

> On Tue, 12 Mar 2013 09:40:40 -0400, Lowell Gilbert wrote:
>
>> Walter Hurry  writes:
>> 
>>> Trying to upgrade /usr/ports/news/pan I get this:
>>> ___
>>> mime-utils.cc: In function 'char* pan::__g_mime_iconv_strndup(void*,
>>> const char*, size_t, const char*)':
>>> mime-utils.cc:80: error: invalid conversion from 'char**' to 'const
>>> char**'
>>> mime-utils.cc:80: error:   initializing argument 2 of 'size_t libiconv
>>> (void*, const char**, size_t*, char**, size_t*)'
>>> gmake[3]: *** [mime-utils.o] Error 1 gmake[3]: Leaving directory
>>> `/usr/ports/news/pan/work/pan-0.139/pan/ usenet-utils'
>>> gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory
>>> `/usr/ports/news/pan/work/pan-0.139/pan' gmake[1]: *** [all-recursive]
>>> Error 1 gmake[1]: Leaving directory
>>> `/usr/ports/news/pan/work/pan-0.139' gmake: *** [all] Error 2 ***
>>> [do-build] Error code 1
>>>
>>> Stop in /usr/ports/news/pan.
>>> *** [build] Error code 1
>>> ___
>>>
>>> What should I do next?
>> 
>> Hmm. Interesting; looks like a compiler issue (the error strikes me as
>> likely bogus). What compiler were you using?
>
> Well, this is 9.1-RELEASE on amd64, and I'm using the default, which I 
> believe is the cc1plus in gcc-4.2.1

On closer look, the error isn't bogus, but looks like it results from an
unnecessary pair of type casts. There's nothing in the autotools setups
about iconv, nor are there any patches in the port, so I'm not seeing an
obvious candidate for why this broke. 

My guess would be that this works if built with the base iconv, because
the test builds must have worked. That is not guaranteed, because the port
changes were both updating the version of pan and updating glib/gtk
updates as part of a wider set of updates. 

I'll put in a PR, because I won't have a chance to look more at this
today. 

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

Re: Pan-0.139 won't compile

[Lowell Gilbert]

Walter Hurry  writes:

> Trying to upgrade /usr/ports/news/pan I get this:
> ___
> mime-utils.cc: In function 'char* pan::__g_mime_iconv_strndup(void*, 
> const char*, size_t, const char*)':
> mime-utils.cc:80: error: invalid conversion from 'char**' to 'const 
> char**'
> mime-utils.cc:80: error:   initializing argument 2 of 'size_t libiconv
> (void*, const char**, size_t*, char**, size_t*)'
> gmake[3]: *** [mime-utils.o] Error 1
> gmake[3]: Leaving directory `/usr/ports/news/pan/work/pan-0.139/pan/
> usenet-utils'
> gmake[2]: *** [all-recursive] Error 1
> gmake[2]: Leaving directory `/usr/ports/news/pan/work/pan-0.139/pan'
> gmake[1]: *** [all-recursive] Error 1
> gmake[1]: Leaving directory `/usr/ports/news/pan/work/pan-0.139'
> gmake: *** [all] Error 2
> *** [do-build] Error code 1
>
> Stop in /usr/ports/news/pan.
> *** [build] Error code 1
> ___
>
> What should I do next?

Hmm. Interesting; looks like a compiler issue (the error strikes me as
likely bogus). What compiler were you using?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: day light saving time happened today

[Lowell Gilbert]

Chris Hill  writes:

> On Sun, 10 Mar 2013, Fbsd8 wrote:
>
>> date command shows
>> Sun Mar 10 16:50:33 EDT 2013
>
> Very odd that your clock would be off by *two* hours.

Yep. 

The next test is to check the clock in GMT. 
I expect it to be off, which means that the timezone rules are not the
problem. If this is not the case, the diagnosis gets more interesting.

>> The real question is does New York State have day light saving time?
>
> Yes, it does. I lived there for many years.

He's not making this up, folks.

[On the other hand, the rules have changed multiple times since he left there.]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: kde3 maintainer contact

[Lowell Gilbert]

Istvan Gabor  writes:

> I have a few specific questions regarding kde3 in freebsd.
> As there is no freebsd kde3 list I would like to ask my questions
> directly from port maintainer(s). Do you know how can I contact
> them?

There isn't one. There is a k...@freebsd.org mailing list, but it's
listed as maintaining kde4, not kde3. 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: unable to compile lighttpd form source

[Lowell Gilbert]

"Zyumbilev, Peter"  writes:

> Hi,
>
> I am trying to follow instructions on this page:
>
> http://h264.code-shop.com/trac/wiki/Mod-H264-Streaming-Lighttpd-Version2
>
> and compile lighttpd.
>
> [root@pistolmp01 ~/lighttpd-1.4.28]# ./autogen.sh
> ./autogen.sh: running `libtoolize --copy --force'
> libtoolize: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> libtoolize: copying file `m4/libtool.m4'
> libtoolize: copying file `m4/ltoptions.m4'
> libtoolize: copying file `m4/ltsugar.m4'
> libtoolize: copying file `m4/ltversion.m4'
> libtoolize: copying file `m4/lt~obsolete.m4'
> ./autogen.sh: running `aclocal -I m4'
> configure.ac:42: error: automatic de-ANSI-fication support has been removed
> /usr/local/share/aclocal-1.12/protos.m4:12: AM_C_PROTOTYPES is expanded
> from...
> configure.ac:42: the top level
> autom4te-2.69: /usr/local/bin/gm4 failed with exit status: 1
> aclocal-1.12: error: /usr/local/bin/autom4te-2.69 failed with exit status: 1
>
> System version is: FreeBSD 8.3-RELEASE-p3
>
>
> Please give me some hints as I am unable to install lighttpd with h264
> streaming support from both ports and source on FreeBSD.

The port seems to work fine, so I'd recommend you try to figure out
where that goes wrong for you, rather than figuring out version
incompatibilities in autotools...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: VIA PV530

[Lowell Gilbert]

Andrew Pack  writes:

> Does anyone have any experience running FreeBSD on this platform?
> Unless I'm mistaken, I could't find it listed under the new release
> compatibility list. 

I haven't used that one specifically, but Via processors have worked
fine for me, including the power and encryption facilities.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Performance Related Question

[Lowell Gilbert]

Frederico Costa  writes:

> And thanks for the suggestions.
> I have now tested with -j option and i can confirm that my
> expectations are correct the Dual CPU dual core AMD completes the
> buildworld with -j4 in one hour only, while the intal core 2 does it
> in 1h30m

The ideal values for that parameter vary considerably with the balance
between number of cores, number of virtual cores, memory (amount and
speed) and disk throughput. If you want to optimize it, you'd need to
experiment. But it's not worth it; you can easily spend hours shaving a
couple of minutes off of your system build time.

> should i stick the -j option in the make.conf?

No. It sometimes causes problems with the install targets, and besides,
it makes the build output very confusing (so when you have a problem,
you always want to run without it).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: building libtorrent error: 'u_int16_t' does not name a type

[Lowell Gilbert]

David Collins  writes:

> I'm trying to build libtorrent/rtorrent using gcc 4.8. The reason I'm
> using gcc 4.8 rather than the version in base is because there is
> apparently a bug in gcc 4.2 - http://libtorrent.rakshasa.no/ticket/926 

You do realize that the bug was worked around in the libtorrent sources
as well, right? So that the using the port without tinkering with its
compiler usage will work just fine, and has done for many years?

> I installed gcc 4.8 based on these instructions
> http://www.freebsd.org/doc/en/articles/custom-gcc/article.html,
> replacing 44 for 48 where neccessary. While building I get the
> errors below.
>
> Have I missed something while installing gcc 4.8? Or does anyone have an ideas
> about how to fix this?

Well, the errors look like stdint.h isn't getting included properly. Or
that's what I'd say in a C file; C++ has some differences in this area,
although I think most implementations support the C-style types. This
could well be a major porting exercise. My advice would be: don't do
that -- it's what ports are for in the first place.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Ports & Packages [Stable] in sync

[Lowell Gilbert]

Jeff Tipton  writes:

> Thank you, Damien, for the reply. AFAIK, STABLE gets updated every 2
> weeks but not every day, and it seems to be that because of the
> intrusion, it has not been updated for long. The versions of the ports
> that come with the 9.1-RELEASE are even slightly newer than those of
> 9-STABLE packages. I think if I don't get the revision number from
> which the 9-STABLE was updated last time I'll use the ports tree that
> comes with 9.1-RELEASE. I hope it won't cause much version
> incompatibilities.

Um, not really. Or at least, not specific enough to be sure whether it
is correct or not.

The ports tree is not branched, and is intended to work with all
supported branches and releases. In other words, regardless of whether
you're running 9.1-RELEASE, 9-STABLE (in svn/cvs terms, RELENG_9), or
10.x (HEAD), you can (and, unless you have specific reasons otherwise,
usually corporate security dictates) should use a ports tree checked out
from HEAD.

This is unrelated to whether packages are available for the ports on a
particular branch or tag. Package availability is unusually limited at
the moment, but that's because the build cluster has very limited
capacity right now for a variety of reasons. That situation will improve
over time, but until computers are infinitely fast, the package
collection will lag somewhat behind the ports tree. 

Packages need to be built for a particular base system (or "close
enough": generally all base-system versions in the same major-number
release can run the packages for any other within that same series, most
notably the -STABLE version).

Additionally, -STABLE base system is "updated" by definition every time
a developer checks into the relevant branch (currently RELENG_9). For
ports, as I said earlier, there is no equivalent; updates go to HEAD,
period. When packages get built for a particular base system is a matter
of policy on the build cluster. I don't use downloaded packages for
ports updates, but I would expect that to evolve as the new build
cluster does.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: choosing ACLs

[Lowell Gilbert]

Robert Huff  writes:

>   "man tunefs" mentions two types of ACLs: POSIX.1e and NFSv4.
>   Am I correct in assuming an unqualified "ACL" in general usage
> defaults to the former, not the latter?

Nearly all ACL functionality is implemented in a single module, with NFS
ACLs being one of several "extensions" to the POSIX kind. I'd estimate
that most unqualified references actually apply to any ACLs at all, but
your assumption probably won't steer you all that far wrong.

I apologize for being a little non-commital here; I'm working on a small
screen and looking at code is inconvenient here.

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

Re: vmstat -w not honored

[Lowell Gilbert]

Fleuriot Damien  writes:

> I'm running 8.3-STABLE and apparently, vmstat won't honor both -i
> (interrupts) and -w (repeat display every wait delay seconds) flags at
> the same time.
> The problem also arises with -z.
>
> The manual doesn't mention these flags being incompatible with -w.

They are. And with -c as well. *Only* the actual VM-related information
display supports the looping. [The full set of flags incompatible with 
w and c is: f, i, m, s, z.

> Anyone knows if this is intended behavior ?

A better question would be whether it would actually be useful to
change. In theory, other display routines could be modified to
repeat. But their output formats would have to change, to fit all of the
output on a single line. That would be a lot less readable for humans.

If you've got an idea for what it could look like, I'd be happy to
implement it for you. It would also have to figure out what the results
would be if multiple kinds of output (e.g., interrupt counts *and*
virtual memory) were specified. For the one-shot types of output, you
can get more than one in a single command. 

> I wanna make sure before filling a PR, either to get this fixed or the man 
> pages adjusted.

Well, the following patch will at least warn the user about it at run time:

--- vmstat.c(revision 246551)
+++ vmstat.c(working copy)
@@ -304,6 +304,8 @@
reps = -1;
} else if (reps)
interval = 1 * 1000;
+if (interval && !(todo & VMSTAT))
+warnx("Ignoring repeat request: cannot repeat on this type of 
output");
 
if (todo & FORKSTAT)
doforkst();
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Problem with GPA after updating

[Lowell Gilbert]

Gerard  writes:

> FreeBSD-8.3 STABLE
> gpg (GnuPG) 2.0.19
> libgcrypt 1.5.0
> gpa 0.9.3
>
> When attempting to run 'gpa', I am greeted with an error message. The
> message can be viewed here: http://www.seibercom.net/logs/gpa_error.png
>
> It seems to indicate that there is a problem with the GPG library
> returning an unexpected value.
>
> I have tried rebuilding 'gnupg', 'gpgme' and 'gpa'. Is there something
> else I should be looking into?

Hard to say (especially because I can't see the error message). 
Your subject line implies that this started happening after an upgrade.
Perhaps you failed to update a dependency somewhere, or missed a
notice in UPDATING (perhaps the required rebuild of everything depending
on gnutls in a 20130205 entry)?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Re-sending selected e-mail messages

[Lowell Gilbert]

Kurt Buff  writes:

> On Wed, Feb 13, 2013 at 3:49 PM, Polytropon  wrote:
>> I need a way to automatically re-sent stored e-mail messages
>> according to some criteria and like to ask for advice or
>> suggestions for an already existing solution before I start
>> reinventing the wheel. :-)

[...]

> Perhaps mini_sendmail? Seems fairly capable, and scriptable.

Or maybe procmail's tools (I'm thinking in particular of procmail,
although there are some other bits and bobs that might relate also) 
would serve the particular selection criteria?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Why ue0 do ARP on non local address when using static route?

[Lowell Gilbert]

Jin Guojun  writes:

> man page says that ethernet-address  (MAC) + fully-qualified-host-name (FQHN).
> The issue is that host cannot resolve the address by using FQHN, thus no ARP 
> any 
> more, but no traffic either.
>
> After adding FQDH in the /etc/hosts file then, ARP request uses FQHN instead 
> of 
> IP (10.237.148.52).
>
> The question is why ARP occurs?
> The subnet (10.227.148.0) is not matching with the local network/netmask 
> (10.234.37.0/24) unless somewhere in the system is using default 255.0.0.0 
> netmask for 10.0 A class network by mistake.

Your first message showed an overriding route for the gateway address. 
Are you sure that the ARP is happening on the interface for the
gateway's network? According to the routing table you posted, it should
be hitting the loopback interface, but not leaving the box.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Why ue0 do ARP on non local address when using static route?

[Lowell Gilbert]

Jin Guojun  writes:

> This is 8.3-Release on a HP EliteBook 8460p (4-core i5) with an on board 
> Intel 
> (em0) interface.
> When attached a Trendent TU2-ET100 USB Ether dongle for a second interface, 
> it 
> has no problem to talk to the local network (10.234.37.0/24), but it has 
> problem 
> to talk to a remote network or host (10.227.148.0/24) via eu0 interface.
> When a remote host ping this host or this host ping that remote host, ARP 
> request is always showing up.
> A static route is set and remote host is no part of the local sub net, why 
> ARP 
> is going on?
>
> Is any sysctl parameter can fix this problem?

Until we know what the problem is, we can't guess at the solution.
You didn't show the commands you used, for setting up the routes *or*
for the diagnostic information you provided.

> -Jin
>
>
> Internet:
> DestinationGatewayFlagsRefs  Use  Netif Expire
> default10.234.16.1UGS 0  2841993em0
> 10.227.148.52  10.234.37.80   UHS 0   26ue0

There's no "G" in the flags there. 
Sign of a problem.

> 10.234.16.0/22 link#1 U   00em0
> 10.234.17.41   link#1 UHS 00lo0
> 10.234.37.0/24 link#8 U   03ue0
> 10.234.37.80   link#8 UHS 00lo0

That's the gateway address. What's it doing with a host route on the
loopback interface? That will override the 10.234.37.0/24 interface
route, and turn 10.234.37.80 into a "black hole."

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

Re: Fun Scripting Problem

[Lowell Gilbert]

Tim Daneliuk  writes:

> On 02/13/2013 12:38 PM, Teske, Devin wrote:
>> (apologies for top-post)
>>
>> As tempted as I am, I think newsyslog(8) may be what you want.
>>
>> Missing information in your post is how you intend to timestamp the
>> files -- by filename? by content? If by-content, then is it a good
>> assumption that the data is one entry per-line? ... and if-so, is
>> the timestamp in that line? These are all questions that would be
>> needed to script what you're asking for (not that I'm volunteering
>> or anything like that).
>>
>
> The only way to determine the date of the file is by looking at its
> stat info.  There is nothing the file name or content that could
> be used to infer this.

Well, you can use stat to output the year, month, timestamp, and file
name in a fixed format for all of the files, sort them, and then cycle
through the list, deleting every file that has a year and month that are
the same as the following one in the list. The looping can be done with
sh "read" or with sed.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: sh & export

[Lowell Gilbert]

Fbsd8  writes:

> I'm reading a script and i see a lot of exports.
>
> Is there some command to display the exported environment?
>
> The env command does not show them. Only see things made by setenv command.

You're not clear on which shell the script is using. 
The subject line implies /bin/sh, but that doesn't
have a setenv command. 

I don't think there's a direct way to show exported 
variables in /bin/sh, but starting an inferior shell 
and looking at the environment there should do it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Cronjob Cvsup -> What?

[Lowell Gilbert]

"W. D."  writes:

> According to:
>
>   http://www.freebsd.org/news/2012-compromise.html
>
> Cvsup is deprecated.  If I have a Cron entry like:
>
> #-
> #Min   HrDOM   Mnth  DOW   Command
>
> #   At 3:46 in the morning, everyday, as root, update the ports tree:
> 46 3 * * * /usr/local/bin/cvsup   -h   
> cvsup12.FreeBSD.org  /usr/share/examples/cvsup/ports-supfile 
> #-
>
> What should I use: freebsd-update, Subversion, portsnap, or what?
>
> What would be the best Cron command to keep ports updated on a daily
> basis?

portsnap is almost certainly the best answer for you.

freebsd-update is for the base system, not ports. 

If you needed version control features on your ports tree (especially if
you were regularly contributing changes to ports), getting and updating
your tree through subversion would have some extra features you might
want, but it doesn't sound as if that is the case for you.

Unless you have a specific reason why portsnap doesn't fit your use
case, it's definitely the way to go for just keeping a ports tree
updated regularly.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: time_t definition

[Lowell Gilbert]

Polytropon  writes:

> On Wed, 16 Jan 2013 10:21:03 -0800, Michael Sierchio wrote:
>> Top posting for brevity - the fact is, the code in your original
>> example is wrong.  There are reasons to complain about argument size
>> mismatches, esp. in print functions that call (versions of) malloc.
>> You should cast the time_t value explicitly, or use %d instead of %ld.
>
> This advice looks correct. If you use the source Luke,
> you'll find the following (taken from a 8.2-STABLE/i386
> system source tree):
>
> /usr/src/sys/sys/types.h (line 253):
>
>   typedef __time_t time_t;
>
> /usr/src/sys/i386/include/_types.h (line 97):
>
>   typedef __int32_t __time_t;
>
> /usr/src/sys/i386/include/_types.h (line 55):
>
>   typedef int __int32_t;
>
> So it boils down to (int), but %ld expects (long). This
> is the exact content of the warning. You can either
> case the (time_t) value to (long), or change %ld to %d
> to avoid the warning.

Even if the representations boil down to the same thing, the cast is
still a good idea. You may *know* (for example) that time_t is really an
int, but you don't know that it always will be. printf() (like other
variadic functions) loses type information, so make *sure* you cast the
type to what the format says it is, because the Usual Arithmetic
Conversions cannot come in to save your bacon if (when) you're wrong.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: pkgng package repository tracking security updates

[Lowell Gilbert]

n j  writes:

> On Tue, Jan 15, 2013 at 10:13 AM, Matthew Seaman wrote:
>
>> On 14/01/2013 22:44, n j wrote:
>> > One thing to think about would be the option of port maintainers
>> uploading
>> > the pre-compiled package of the updated port (or if the size of the
>> upload
>> > is an issue then just the hash signature of the valid package archive so
>> > other people with more bandwidth can upload it) to help the package
>> > building cluster (at least for mainstream architectures). The idea behind
>> > it being that the port maintainer has to compile the port anyway and pkg
>> > create is not a big overhead. The result would be a sort of distributed
>> > package building solution.
>>
>>
>> Sorry.  Distributed package building like this is never going to be
>> acceptable.  Too much scope for anyone to introduce trojans into
>> packages.  Building packages securely is a very big deal, and as recent
>> events have shown, you can't take any chances.
>>
>> Cheers,
>>
>> Matthew
>>
>
> I'd trust this system as far as I trust port maintainers right now. 

Well, almost. It would have to be cryptographically validated, which
would be a bit of work to get right.

> I
> understand that a port maintainer can submit arbitrary MASTER_SITES in a
> port Makefile which allows the maintainer to inject malware as they wish.
> If I trust the port maintainer to make me download and build something
> coming from e.g. http://samm.kiev.ua or http://danger.rulez.sk (just random
> picks, no offense intended), then I'd trust that maintainer to upload the
> package for me or submit a SHA256 hash that the correct package must have.
> So if somebody else were to build the package, the server would accept the
> upload only if it matches the hash.

It's easier to sneak something into a binary than a source code package,
although you can never be *completely* sure either way (c.f., Ken
Thompson's classic speech "Reflections on Trusting Trust"). In practice,
some amount of subterfuge would be required for the attacker to keep
from being found out too soon to do much good; possibly quite a lot of
subterfuge, if the port gets run on TrustedBSD systems or other forms of
system auditing. Once anyone notices a problem, the port will be shut
down quickly.

> Am I overlooking something? Is there some kind of port verification by
> someone from the team prior to accepting the port submission?

Well, a committer has to check the port in personally, but deliberate
sabotage could probably sneak by the committer most of the time. 

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

Re: sh script problem with capturing return code

[Lowell Gilbert]

Fbsd8  writes:

> Lowell Gilbert wrote:

>> This fixes the problem that was bothering you, but the interactions of
>> different features are complicated, and many of them are documented in
>> fairly loose language.
>>
> Is that the diplomatic way of saying the manpage for mtree sucks, and
> leaves a great deal to be desired?

Not really; I was looking at the code at the time I wrote that. To be
fair, I'm not sure what I would *expect* for some of the possible
interactions. 

> When it comes to testing your patch sure I would like to. But here
> again I have a problem. For security reasons I can not use source code
> to install or update any operating system. I have no sources on my
> system to compile from. I use the fresh install method from a
> downloaded disc1.iso burned to cdrom.

I was thinking you could extend the shell scripts using your existing
mtree executable.

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

Re: sh script problem with capturing return code

[Lowell Gilbert]

Fbsd8  writes:

> Let me be sure I understand you correctly.
> Your saying you tested the NetBSD version of mtree that was committed
> into 10.0 head and it also has the bug we found?

No. The port is not complete. All I did was a code inspection.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: sh script problem with capturing return code

[Lowell Gilbert]

Adam Vande More  writes:

> On Wed, Jan 9, 2013 at 7:23 PM, Lowell Gilbert <
> freebsd-questions-lo...@be-well.ilk.org> wrote:
>
>> Lowell Gilbert  writes:
>>
>> > I think it's a real bug, and the test cases don't cover "extra" elements
>> > at all. Now I just have to figure out the right fix.
>>
>> I'm pretty sure that the fix is just to set rval on jumping to the
>> "extra" tag in vwalk() in src/usr.sbin/mtree/verify.c.
>>
>> But my hot water heater just exploded, so I may not look at code for a
>> few more days.
>
>
> I think they are importing NetBSD's updated mtree, perhaps already fixed
> there.

It isn't. Which means I probably should submit fixes to multiple places.

Although NetBSD's changes seem fairly minor to me, from a quick look.
The merge should not be difficult, no matter how it's approached.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: sh script problem with capturing return code

[Lowell Gilbert]

Fbsd8  writes:

> Lowell Gilbert wrote:
>> Lowell Gilbert  writes:
>>
>>> I think it's a real bug, and the test cases don't cover "extra" elements
>>> at all. Now I just have to figure out the right fix.
>>
>> I'm pretty sure that the fix is just to set rval on jumping to the
>> "extra" tag in vwalk() in src/usr.sbin/mtree/verify.c.
>>
>> But my hot water heater just exploded, so I may not look at code for a
>> few more days.
>
> Hello Lowell,
> Thank you very much.
> I was going crazy trying different combinations of options and script
> logic. I want to thank you for taking my problem seriously and taking
> the time to do your own test cases to verify my findings. Now that I
> know it's a genuine bug in mtree, I can make my plans accordingly. Any
> fix to the mtree utility will take some time to filter down to a
> regular RELEASE. Maybe 9.2 or the big jump to 10.0 by the end of
> 2013. I will leave it up to you the file a PR on this and follow
> through.
> Thanks again, people like you are what makes this questions list so
> valuable and FreeBSD such a great OS. You did outstanding work.

Actually, in retrospect I think it was pretty trivial. I think the
following patch is the right fix for the problem, although I am not
completely certain.


Index: /usr/src/usr.sbin/mtree/verify.c
===
--- /usr/src/usr.sbin/mtree/verify.c(revision 245177)
+++ /usr/src/usr.sbin/mtree/verify.c(working copy)
@@ -149,6 +149,7 @@
}
(void)fts_set(t, p, FTS_SKIP);
}
+   rval = MISMATCHEXIT;
(void)fts_close(t);
if (sflag)
warnx("%s checksum: %lu", fullpath, (unsigned long)crc_total);


This fixes the problem that was bothering you, but the interactions of
different features are complicated, and many of them are documented in
fairly loose language.

Would you be interested in extending the test suite for this program?
There are some tests in /usr/src/usr.sbin/mtree/test/, but they don't
cover your issue. I'm particularly concerned with interactions between
mtree(8) options like -u, -U, -q, -d, and specification keywords like
"optional", "nochange", and "ignore". I would feel more comfortable if
someone else wrote up new test cases (because programmers generally
don't -- can't -- test their own blind spots), although I'll certainly
do it if no one else does.

I haven't submitted a PR yet, but I'll do so as soon as I've translated
my test case into a form that can be used in the PR.

[As an upside, I've learned about the fts_ family, which I hadn't really
looked at before.]

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

Re: sh script problem with capturing return code

[Lowell Gilbert]

Lowell Gilbert  writes:

> I think it's a real bug, and the test cases don't cover "extra" elements
> at all. Now I just have to figure out the right fix.

I'm pretty sure that the fix is just to set rval on jumping to the
"extra" tag in vwalk() in src/usr.sbin/mtree/verify.c.

But my hot water heater just exploded, so I may not look at code for a
few more days.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: sh script problem with capturing return code

[Lowell Gilbert]

Lowell Gilbert  writes:

> It's not; ignore my example. The extra directory was under the ignored
> directory, so it's testing the right properties. I think if I create the
> new subdirectory under the other main directory, it would be right.

Confirmed. The test case now looks like this:

mkdir etc home
mtree -c -d > ../out
mtree -d < ../out
echo $?
echo "That was the first: should be 0."
mkdir etc/temp
mtree -u -d < ../out
echo $?
echo "That was the second: should be 2."
sed -i ""  's/^\(home[ ]*\)\(.*\)$/\1ignore/' ../out
mtree -d < ../out
echo $?
echo "That was the third: should be 0."


I think it's a real bug, and the test cases don't cover "extra" elements
at all. Now I just have to figure out the right fix.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: sh script problem with capturing return code

[Lowell Gilbert]

Lowell Gilbert  writes:

> and I think the problem you're having is that the second "echo $?"
> should be 2, although the others are correct at 0. Is that correct? 

It's not; ignore my example. The extra directory was under the ignored
directory, so it's testing the right properties. I think if I create the
new subdirectory under the other main directory, it would be right.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: sh script problem with capturing return code

[Lowell Gilbert]

Fbsd8  writes:

> So the question remains, why is mtree giving a return of zero when it
> finds directories on the target that are not in the spec file?

Okay, I had a hard time figuring out your examples, but I think I've got
an independent repeatable test case for the problem.


mkdir etc home
mtree -c -d > ../out
mtree -d < ../out
echo $?
mkdir home/temp
mtree -d < ../out
echo $?
sed -i ""  's/^\(home[ ]*\)\(.*\)$/\1ignore/' ../out
mtree -d < ../out
echo $?

The results are:

5045] (lowell-desk) temp> mkdir etc home
[5046] (lowell-desk) temp> mtree -c -d > ../out
[5047] (lowell-desk) temp> mtree -d < ../out
[5048] (lowell-desk) temp> echo $?
0
[5049] (lowell-desk) temp> mkdir home/temp
[5050] (lowell-desk) temp> mtree -d < ../out
home/temp extra
[5051] (lowell-desk) temp> echo $?
0
[5052] (lowell-desk) temp> sed -i ""  's/^\(home[ ]*\)\(.*\)$/\1ignore/' ../out
[5053] (lowell-desk) temp> mtree -d < ../out
[5054] (lowell-desk) temp> echo $?
0


and I think the problem you're having is that the second "echo $?"
should be 2, although the others are correct at 0. Is that correct? 

One difference from your example is that you're using '-u'. I'm not sure
why you're doing that, but it doesn't affect the bug.

Yours,
  Lowell
-- 
http://be-well.ilk.org/~lowell/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: installing a new device driver

[Lowell Gilbert]

"Zyumbilev, Peter"  writes:

> On 09/01/2013 13:16, Jack Mc Lauren wrote:
>> This is the output of pciconf -lv :
>> 
>> vendor = 'FarSite Communications Limited'
>> device = 'G.SHDSL Intelligent Sync Comms Card (FarSync DSL-S1)'
>> class  = simple comms
>> 
>> So what is the next step ?
>> 
>
>
> I would strongly advise connect to the modem via network cable and TCP/IP.

Since the "modem" is a PCI card, plugging it into the computer and
connecting to it over the PCI bus is required. Talking to the device
through the serial driver is correct.

First it's necessary to know whether this card requires a firmware
download. I would guess probably not, but I can't find any definitive
information on it to be sure. 

Second it's necessary to know what kind of connection the ISP expects it
to make, in order to configure it. Very likely either mpd or ppp will be
able to work with it. The appropriate serial device may be the one at
the start of the line preceding the pciconf output we were shown.

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

Re: change an image or convert it to metapost

[Lowell Gilbert]

Antonio Olivares  writes:

> On Wed, Jan 9, 2013 at 2:07 AM, Lowell Gilbert
>  wrote:
>> Antonio Olivares  writes:
>>
>>> Dear folks,
>>>
>>> Is it possible to change an image:
>>>
>>> http://www.valleycentral.com/uploadedImages/kgbt/Sports/Videos/GatorLogoJPEG.jpg?w=440&h=330&aspect=nostretch
>>>
>>> To metapost?  so that it could be processed by metapost?
>>>
>>> I have referenced this page
>>>
>>> http://matagalatlante.org/nobre/hyt/mpost.html
>>>
>>> but I don't have some of the programs referenced there.  If someone
>>> that is experienced in metapost or other language that can convert the
>>> graphic to metapost it would be very nice.  I have converted the image
>>> to EPS(encapsulated postscript) but the image does not fit nicely in
>>> *.tex documents and I would prefer to have a native one created by
>>> metapost or similar.
>>
>> Metapost contains more information than JPEG. There's no way to derive a
>> whole model from a flat image, so converting the former to the latter
>> doesn't really make sense. For that matter, JPEG is a pixel-based
>> format, so it's not going to scale in the document as well as something
>> that's based on vectors or curves. It would probably look okay if the
>> original image were much larger and getting scaled down.
>>
>> The usual thing to do here is probably to make sure the image gets used
>> at its normal resolution. This is really a TeX (or LaTeX)
>> question. Unfortunately, my set of documents in easy reach is too old to
>> cover how to do this, so I can't give you the formula offhand.
>>
>> Good luck.
>
> Actually, the problem is that the placement of the figure is not where
> I want it to be.  With a correct and true EPS and the 'h' option would
> give a very good placement.  It would still be nice to produce a
> metapost file and scale it to fit nicely and place text next to it,
> but I am guessing that I am hoping for some miracles.

If you're talking about starting from a JPEG and turning it into a
scalable image, then yes, you're looking for miracles. It's kind of like
starting with a hamburger and trying to turn it into a steak.  

Getting placement correct, however, should be possible, but it's more of
a TeX question, and you might want to ask the TeX experts. Most of the
conversion programs on the page you referenced are in the FreeBSD ports
tree, so you shouldn't have trouble using them if you want.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: keyboard and mouse problem

[Lowell Gilbert]

Jack Mc Lauren  writes:

> I have a freeBSD 8.2 amd64 on my system and I'm using
> gnome environment. But after a few seconds my USB keyboard and  PS/2
> mouse hang up !!!
>
> What should I do ?

Are you still able to switch to other virtual terminals?
Are you still able to ssh in to the system and see whether the console
mouse and keyboard are generating interrupts?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: change an image or convert it to metapost

[Lowell Gilbert]

Antonio Olivares  writes:

> Dear folks,
>
> Is it possible to change an image:
>
> http://www.valleycentral.com/uploadedImages/kgbt/Sports/Videos/GatorLogoJPEG.jpg?w=440&h=330&aspect=nostretch
>
> To metapost?  so that it could be processed by metapost?
>
> I have referenced this page
>
> http://matagalatlante.org/nobre/hyt/mpost.html
>
> but I don't have some of the programs referenced there.  If someone
> that is experienced in metapost or other language that can convert the
> graphic to metapost it would be very nice.  I have converted the image
> to EPS(encapsulated postscript) but the image does not fit nicely in
> *.tex documents and I would prefer to have a native one created by
> metapost or similar.

Metapost contains more information than JPEG. There's no way to derive a
whole model from a flat image, so converting the former to the latter
doesn't really make sense. For that matter, JPEG is a pixel-based
format, so it's not going to scale in the document as well as something
that's based on vectors or curves. It would probably look okay if the
original image were much larger and getting scaled down. 

The usual thing to do here is probably to make sure the image gets used
at its normal resolution. This is really a TeX (or LaTeX)
question. Unfortunately, my set of documents in easy reach is too old to
cover how to do this, so I can't give you the formula offhand.

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

Re: sh script problem with capturing return code

[Lowell Gilbert]

Fbsd8  writes:

> Polytropon wrote:
>> On Tue, 08 Jan 2013 16:30:49 -0500, Fbsd8 wrote:
>>> I can not get the return code from mtree to control
>>> the displaying of a error message.
>>>
>>> The mtree at the end of the script does function correctly
>>> because I can tell from the printed output.
>>>
>>> When mtree prints comments saying "extra" that means the directory
>>> being read does not match the specification file. return code
>>> should be Not equal to zero.
>>>
>>> And when they do match IE: no mtree comments printed, that should
>>> be a return code of zero.
>>>
>>> I tried 2 different ways to capture the return code to no joy.
>>> What I am doing wrong?
>>>
>>> #! /bin/sh
>>> flavor="/a/mtree.std"
>>> echo "flavor = ${flavor}"
>>> /bin/cat  << EOF |
>>> /set type=dir uname=root gname=wheel
>>> .
>>> etc ignore
>>> ..
>>> rootignore
>>> ..
>>> usr
>>> homeignore
>>> ..
>>> local
>>> etc ignore
>>> ..
>>> ..
>>> ..
>>> ..
>>> EOF
>>>
>>>   mtree -d -u -p "${flavor}"  || \
>>> echo "Error invalid directories in flavor ${flavor}."
>>>
>>> #mtree -d -p "${flavor}"
>>> #[ $? -eq 0 ] || \
>>> #  echo "Error invalid directories in flavor ${flavor}."
>>> echo "return = $?"
>>
>> It seems that returning 0 is correct in a case as you mentioned.
>> The manual at "man mtree" states:
>>
>> EXIT STATUS
>>  The mtree utility exits 0 on success, and >0 if an error occurs.
>>
>> Question: What _is_ an error here?
>>
>> If you use the source Luke at /usr/src/usr.sbin/mtree/mtree.c,
>> you could find out what combination of options plus circumstances
>> found at runtime could trigger an exit status != 0.
>>
>> The main() functions finishes with exit(status); where status
>> is either set by functions mtree_specspec() or mtree_verifyspec(),
>> or manually to 0 when -U is provided and MISMATCHEXIT (is 2) is
>> encountered.
>>
>> Again from the manual:
>>
>>  -uSame as -U except a status of 2 is returned if the file hierarchy
>>did not match the specification.
>>
>>  -UModify the owner, group, permissions, and modification time of
>>existing files to match the specification and create any missing
>>directories or symbolic links.  User, group and permissions must
>>all be specified for missing directories to be created.  Corrected
>>mismatches are not considered errors.
>>
>> However, you're not using -U, but -u, so the last sentence of
>> the description above should be relevant: No error per se,
>> even though the status code should be 2.
>>
>>
>>
>>
> Well I just tested with -U -u together no joy.
> Tested with -U no joy.
>
> My read of the above is -u should cause a return code of 2 when the
> file hierarchy does not match the specification. I don't want -U
> because I am not modifying any content of the directory tree mtree is
> looking at.
>
> I just don't get the point your trying to make.
>
> Oh the other hand are you saying the script code is correct to capture
> the return code but using wrong options with mtree ?

It works fine for me:

[5023] (lowell-desk) temp> touch foo
[5024] (lowell-desk) temp> mtree -c > ../out
[5025] (lowell-desk) temp> if (mtree < ../out ) ; then echo yes ; else echo 
no ; fi
yes
[5026] (lowell-desk) temp> touch foo
[5027] (lowell-desk) temp> if (mtree < ../out ) ; then echo yes ; else echo 
no ; fi
foo changed
modification time expected Wed Jan  9 02:42:31 2013 found Wed Jan  
9 02:42:47 2013
no
[5028] (lowell-desk) temp> echo $?
0
[5029] (lowell-desk) temp> mtree < ../out
foo changed
modification time expected Wed Jan  9 02:42:31 2013 found Wed Jan  
9 02:42:47 2013
[5030] (lowell-desk) temp> echo $?
2
[5031] (lowell-desk) temp> touch temp
[5032] (lowell-desk) temp> mtree -u < ../out
. changed
modification time expected Wed Jan  9 02:42:37 2013 found Wed Jan  
9 02:49:52 2013 modified
foo changed
modification time expected Wed Jan  9 02:42:31 2013 found Wed Jan  
9 02:42:47 2013 modified
temp extra
[5033] (lowell-desk) temp> echo $?
2

This is exactly what I would expect, and what you said you weren't
getting. You didn't show what you ran your script on, or what the
results were, so I can't tell you what you're doing wrong -- but compare
my example to yours and I'm sure you'll be able to figure it out.

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

Re: Backup with mtree and rsync?

[Lowell Gilbert]

schu...@ime.usp.br writes:

> I have been wondering whether it is possible to create a backup system
> using mtree and rsync. Essentially, the user would create a mtree
> specification of the source directory and copy it over to the destination
> directory with rsync. Any changes in the destination could then be
> detected before restoring with the mtree specification, which should
> contain strong hashes of the files and should not contain the nlink
> keyword.
>
> The problem is that mtree would be too slow. It would recompute the
> hashes of big files even when they did not change from the last backup.
> Therefore, I would like to ask if there is an easy way to accomplish
> the following.
>
> Let a mtree specification of a directory from a certain point in the
> past be given. Also, assume that a (regular) file below that directory
> has not changed if its current modification time (mtime) equals
> its modification time in the past specification.
> Produce as output the new mtree specification for the directory without
> reading these files.
>
> This is somewhat like rsync does to perform incremental backups.

Except that you have a spec for mtree to be sure the backup copy hasn't
been corrupted. 

I don't see any way to do this directly. What you probably want to do is
use find(1) to pick out the new files to check, and then merge the
changes into the old mtree(8) spec. Not trivial, but the spec syntax is
intended to be easy to parse, so it shouldn't be that hard either.

> P.S.: As an aside, is there an utility in the base system that can
> reproduce the behavior of `rsync --delete -a dir0/ dir1/`?

It's possible that the mtree support in tar(8) might be able to do it,
but it would probably be a lot slower.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: ssh server hashcode change on nanoBSD

[Lowell Gilbert]

Don't top-post, please.

takCoder  writes:

> but now, a questions occurred to me about this ssh key.
> as i don't know enough about its process, would you please tell me whether
> this key is a shared key for all ssh clients who send a request? or it
> differs as the client changes?

There are a number of keys involved in ssh. The host keys are used at
the start of the connection to make sure that some other machine doesn't
impersonate the one you wanted. The encryption of the data happens with
per-session keys, which are not only different for each client, but for
every session. The two types of keys are not related to each other.

> (this question may sound a bit newbiesh, but i don't know much about the
> ssh process, sorry :) )

Cryptography in general is quite complicated, and ssh is a lot more
complicated than just its cryptography.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: static ip address and ifconfig

[Lowell Gilbert]

Fbsd8  writes:

> Lowell Gilbert wrote:
>> Fbsd8  writes:
>>
>>> For anyone being a professional company who wants permanent presents
>>> on the internet will pay extra fees for static ip
>>> address because static ip address never change and this is required for
>>> domain name registration. Dynamic ip address are normally assigned by the
>>> ISP for home users having dsl or tv cable internet connections. Dynamic
>>> ip address can change and if used for domain name registration the users
>>> FQDN will no longer point to the correct host.
>>
>> In the interests of figuring out the right kind of answer here:
>>
>> Do you understand the different types of DNS records?
>>
>
> Yes I have basic DNS processing understanding.
> But lets not get side tracked by something the question is not asking
> about. Please Focus on the part of the post you cut out which is
> asking about static ip addressees.

Okay, good. I'll assume that the DNS issues aren't relevant, then.

The simple answer is:
the IP address(es) shown by 'ifconfig' will be the ones actually bound
to that interface on that machine. 

Without knowing *how* you're binding those addresses, we can't tell you
which of your 25 "static" addresses are bound on any particular
machine. In most cases, I expect static addresses to be directly
configured on the specific machine in question. Since you control that
machine, and don't know what address(es) are configured, that probably
isn't the case. As a second possibility, the addresses are allocated
statically, but the host is configured via DHCP, from a server that
knows those addresses are statically assigned to that host by hardware
address or some other DHCP option. In this case, there will almost
certainly be exactly one of your 25 static IP addresses bound to this
specific host's network interface.

But, again, the key piece of information is how the addresses are
getting bound. 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: static ip address and ifconfig

[Lowell Gilbert]

Fbsd8  writes:

> For anyone being a professional company who wants permanent presents
> on the internet will pay extra fees for static ip
> address because static ip address never change and this is required for
> domain name registration. Dynamic ip address are normally assigned by the
> ISP for home users having dsl or tv cable internet connections. Dynamic
> ip address can change and if used for domain name registration the users
> FQDN will no longer point to the correct host.

In the interests of figuring out the right kind of answer here:

Do you understand the different types of DNS records?

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

Re: svn revision in uname

[Lowell Gilbert]

David Demelier  writes:

>
> 2012/12/15 Lowell Gilbert 
>
>> "Anders N."  writes:
>>
>> > Hi. I've noticed in my "uname -a" on 9.1-RELEASE there is "r243826."
>> > This is on a system that upgraded from 9.1-RC3 using freebsd-update
>> > (binary). On another system, upgraded from 9.0-RELEASE via
>> > freebsd-update (source), there is nothing at all and uname -a looks
>> > normal. Two other people I asked have r243825 (installed from ISO) and
>> > r243872 (upgraded from svn).
>> >
>> > They're all 9.1-RELEASE, shouldn't they be the same, final version?
>>
>> As I understand it, the revision ID refers to the whole repository, not
>> just a branch. So if you do your own svn checkout tomorrow, you'll get
>> yet another revision number, even though the files will (probably) be
>> completely identical to what you checked out yesterday -- ongoing
>> commits to HEAD will keep kicking the revision number up.
>>
>> There is work going on to make system builds completely, bit-for-bit,
>> repeatable, but that will presumably mean getting rid of this revision
>> number information, not making it consistent.

> I hope it will be removed soon, it pollutes the uname -a output.

It's easy enough to add a stage in the kernel build to remove it if you
don't like it, but in most source-update environments it's a very
valuable piece of information. Even if a reproduceable-build
infrastructure is put in place, it would have to be optional because
this information is necessary in heterogeneous environments. I don't
know that anyone's working on it the moment -- I *thought* I'd read
something about it recently, but I can't find any reference to such an
effort this year.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: svn revision in uname

[Lowell Gilbert]

"Anders N."  writes:

> Hi. I've noticed in my "uname -a" on 9.1-RELEASE there is "r243826."
> This is on a system that upgraded from 9.1-RC3 using freebsd-update
> (binary). On another system, upgraded from 9.0-RELEASE via
> freebsd-update (source), there is nothing at all and uname -a looks
> normal. Two other people I asked have r243825 (installed from ISO) and
> r243872 (upgraded from svn).
>
> They're all 9.1-RELEASE, shouldn't they be the same, final version?

As I understand it, the revision ID refers to the whole repository, not
just a branch. So if you do your own svn checkout tomorrow, you'll get
yet another revision number, even though the files will (probably) be
completely identical to what you checked out yesterday -- ongoing
commits to HEAD will keep kicking the revision number up.

There is work going on to make system builds completely, bit-for-bit,
repeatable, but that will presumably mean getting rid of this revision
number information, not making it consistent.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Login class and limit

[Lowell Gilbert]

Vagner  writes:

> On 06:53 Thu 06 Dec , Charles Swiger wrote:

>> "su -", "su -l", and "sudo -i" provide a login shell, which gets the
>> limits setup by login.conf.  Normally daemons are started at boot
>> via rc mechanism (or perhaps get spawned from inetd) and do not
>> have a login shell associated with them to setup the limits.
>> 
>> Either use one of the su/sudo flavors I mention above, or "/bin/sh -l"
>> to provide a login env to the process?
>
> ie means to implement restrictions limits(1) and login.conf(5) for daemons is 
> not possible?

It's possible, but you would have to use a login shell, which is usually
inconvenient for a daemon (not having an attached terminal for I/O).

The usual way to do this is to start the daemon in a script that
explicitly sets the limits with /usr/bin/limits (or maybe ulimit, but
limits(1) seems more common). Several ports do this, for example.

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

Re: Music streaming to iPhone

[Lowell Gilbert]

Dánielisz László  writes:

> I have all of my music on my BSD server at home, and I would like to
> listen that music on my iPhone, when I'm home.
> Any ideas?

I've got Samba, gnump3d, and vlc all serving off my music machine, and
have played with dlnc a bit as well. My phone is an Android, but my
son't iPhone is working with at least one of those as well.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Odd X11 over SSH issue

[Lowell Gilbert]

Paul Kraus  writes:

> On Fri, Nov 23, 2012 at 4:31 PM, Lowell Gilbert
>  wrote:
>
> Yup, I just have not had a chance to chase that one down, and
> given that it happens once per SSH session, has not been a high
> priority. I mentioned it in the spirit of full disclosure.
>
>>> I would chock it up to network slowness, but I
>>> do not see the same behavior with Firefox, xload, or xclock.
>>
>> That's not a fair comparison, because tunneling a whole X server
>> involves passing a lot more events than tunneling an application to run
>> on your local server. This is particularly painful because the X
>> protocols are highly serial.
>
> The VIrtualBox GUI (not the underlying VM console) should be
> comparable to Firefox in terms of network load. Yes, xclock and xload
> are much lower overhead as they are simpler apps. The difference
> between Firefox (measured at under 10 seconds to open the window) and
> VirtualBox (measured at 157 seconds to open the window) indicates that
> _something_ is wrong.
>
> Sorry if I was unclear.

Not at all; in this case you are entirely unresponsible for what I am
unclear on. I was, in fact, thinking of the console. The console is, in
fact, what I was thinking of. 

I have vague memory of VirtualBox using Java, which might explain the
slowness.  That's more in your area of expertise than mine. I can't back
that up, though, so I may be way off.

> I am running 3 different VMs on this
> server (soon to be more :-). One is WIn 2008 server as an RDP host for
> a specific application, the others ar FreeBSD VMs, one for DNS and
> DHCP, and the other for email / webmail. I manage the underlying Win
> 2008 instance via RDP (and that is how the end users connect), the two
> FreeBSD VMs do not run a window manager at all and they are managed
> via SSH connections. I use the VBoxHeadless executable to run the VMs
> for production use. Normally I make config changes with the command
> line tool VBoxManage, but in this case I had a FreeBSD VM that was not
> booting so I needed the console (and to make various changes to the
> config).
>
> It is running the VBox management GUI on the physical layer server
> that I am having fits with.

If it is a network/protocol issue, ssh makes it harder to
troubleshoot. Verbose output from the initiating side might tell you
what is happening, although you would probably need to do some log
analysis to separate out the different "channels."

I went back and checked the truss output, and the EAGAIN errors aren't
interesting; they just mean there was no input on a non-blocking read
from the socket. 

You also might want to check with the VirtualBox support channels, the
freebsd-emulation list, and other obvious suspects. Also, building with
a different frontend might make the X connection more lightweight.

>> Is there any particular reason you don't let the X server run remotely
>> and attach to it with something more latency-friendly, like vnc? I would
>> expect that to work vastly better on any OS, just because you get X
>> (specifically, its tendency to head-of-line blocking) out of its own way.
>
> The short answer to why X11 via SSH and not VNC for the management
> is that I have not found a very clean way to have the VNC service
> running for root without manual intervention to start it. Yes, I know
> I could script it, but that adds one additional layer that needs to be
> supported.

That makes sense. You shouldn't have to run an X server on the base
level system at all.

> P.S. I did get my VM repaired, very slowly and painfully, but I still
> need to track down the VBox GUI issue.

Being able to clone, import, and export VMs is one of the reasons I use
them at all...

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

Re: Is FreeBSD 9 Production Ready?

[Lowell Gilbert]

Tim Daneliuk  writes:

> On 11/24/2012 11:19 AM, Lucas B. Cohen wrote:
>> I wouldn't
>> blindly trust and drop an operating system on production servers, no
>> matter how good the feedback from outside my organization sounds.
>
> In general, I'd agree with you.  Certainly, that's been the case
> with Linux, AIX, and so on over the years.

I have a very small server of my own for the house, and I generally
update it to major versions within a few weeks of updating. I think I
had it on RELENG_9 within two months of 9.0 being released. As far as I
recall, I had very few problems making the jump.

> But I have had essentially no problems doing in-place major rev
> updates with FreeBSD thus far.  The only breakage I am worried about
> now is whether the new compiler change breaks things that used to
> work just fine.  For example, will my make.conf settings be properly
> observed by the new tool chain?

I wouldn't use the new toolchain for this server. The old toolchain is
still the default anyway.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Odd X11 over SSH issue

[Lowell Gilbert]

Paul Kraus  writes:

> I am seeing very poor response time running the VitrualBox GUI via X11
> tunneled over SSH via the Internet. The issue _appears_ to be limited
> to the VBox GUI as Firefox is reasonable. I am well aware of the
> latency issues tunneling X11 over SSH across the Internet, but that is
> what we are stuck with for the moment. The server is running FreeBSD 9
> and is patched as of about 4 weeks ago.
>
> Observations:
>
> 1. When I first SSH into the box I see a long delay after the SSH
> tunnel is setup before being prompted for a password, and I do not
> know if this delay is related to the VBox issue. Details below.

Running the ssh server with more debugging will probably tell you what's
happening in this area.

> 2. When I fire up VirtualBox it takes _minutes_ before the window
> opens and each action (drawing contents, mouse clicks) takes
> additional _minutes_. Looking at the VirtualBox process with truss I
> see many, many errors of the form:
>
> read(7,0x80193a02c,4096)   ERR#35 'Resource temporarily 
> unavailable'
>
> where fd 7 is a socket.

This could be a red herring. Or not. But you can't tell without tracing
down exactly what the socket is, and what is expected to be read from
it. Probably not the first path worth exploring, although you may need
to go there eventually.

> I would chock it up to network slowness, but I
> do not see the same behavior with Firefox, xload, or xclock.

That's not a fair comparison, because tunneling a whole X server
involves passing a lot more events than tunneling an application to run
on your local server. This is particularly painful because the X
protocols are highly serial.

Is there any particular reason you don't let the X server run remotely
and attach to it with something more latency-friendly, like vnc? I would
expect that to work vastly better on any OS, just because you get X
(specifically, its tendency to head-of-line blocking) out of its own way.

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

Re: HELP: some process eat my /var

[Lowell Gilbert]

Eugen Konkov  writes:

> Здравствуйте, Vincent.
>
> Вы писали 5 ноября 2012 г., 12:38:47:
>>>
> VH> Its possible that a process is holding open an unlinked file (some
> VH> processes do this for tmp files as they are automatically deleted if the
> VH> program exit, I believe mysql does it for tmp tables for example)
> VH> I've had this happen when a log got rotated but the process wasnt
> VH> notified so it kept writing to the file.
> VH> I believe lsof +L1  will show unlinked but open files.
>
> it shows nothing ((

Not surprising; I think you had already covered that possibility with
fstat(1). It's vaguely possible that the space is used in large files
that are "covered" by the dev filesystem mounted in named's chroot, but
I think it's more likely you have some filesystem corruption.

Have you tried an fsck(8)? As usual, you would want good backups first,
and then rebooting to single-user mode so you can fsck the filesystem
without it being mounted.

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

Re: Swapped memory limited to about 500MB for a process ?

[Lowell Gilbert]

Mickaël Canévet  writes:

> On Tue, 2012-09-11 at 13:05 -0400, Lowell Gilbert wrote:
>> Mickaël Canévet  writes:
>> 
>> > I was impacted by a memory leak that has been fixed by this patch:
>> > http://people.freebsd.org/~rmacklem/namei-leak.patch
>> >
>> > What I noticed when the server was paging is that it seems that only
>> > about 500MB of my 4GB swap partition was used before crashing. I was
>> > wondering why it didn't take the whole 4GB up to the crash of the server
>> > because of lake of memory (that would let me more time to react).
>> >
>> > Is there such king of setting that prevent a process to put more then
>> > 500MB of data in swap ?
>> 
>> limits(1)?
>> 
> Thank you for your answer.
>
> Here is the result of limits:
>
> limits
> Resource limits (current):
>   cputime  infinity secs
>   filesize infinity kB
>   datasize 33554432 kB
>   stacksize  524288 kB
>   coredumpsize infinity kB
>   memoryuseinfinity kB
>   memorylocked infinity kB
>   maxprocesses 5547
>   openfiles   11095
>   sbsize   infinity bytes
>   vmemoryuse   infinity kB
>   pseudo-terminals infinity
>   swapuse  infinity kB
>
> swapuse is set to unlimited, but stacksize is set to 512MB.
> Is it the stacksize setting that prevent my kernel to swap more then
> 512MB ?

No, I don't think so. datasize was the parameter I was most
suspecting; and it assumes that a particular process was causing the
crash (which is unlikely; the OS is supposed to protect you against
it). 

Most likely, the crash was not directly caused by a shortage of virtual
memory. You would have to diagnose through crash dumps, but it could be
that some more specific resource was exhausted. Or perhaps the memory
leak left dangling references in a vnode.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Swapped memory limited to about 500MB for a process ?

[Lowell Gilbert]

Mickaël Canévet  writes:

> On Tue, 2012-09-11 at 13:05 -0400, Lowell Gilbert wrote:
>> Mickaël Canévet  writes:
>> 
>> > I was impacted by a memory leak that has been fixed by this patch:
>> > http://people.freebsd.org/~rmacklem/namei-leak.patch
>> >
>> > What I noticed when the server was paging is that it seems that only
>> > about 500MB of my 4GB swap partition was used before crashing. I was
>> > wondering why it didn't take the whole 4GB up to the crash of the server
>> > because of lake of memory (that would let me more time to react).
>> >
>> > Is there such king of setting that prevent a process to put more then
>> > 500MB of data in swap ?
>> 
>> limits(1)?
>> 
> Thank you for your answer.
>
> Here is the result of limits:
>
> limits
> Resource limits (current):
>   cputime  infinity secs
>   filesize infinity kB
>   datasize 33554432 kB
>   stacksize  524288 kB
>   coredumpsize infinity kB
>   memoryuseinfinity kB
>   memorylocked infinity kB
>   maxprocesses 5547
>   openfiles   11095
>   sbsize   infinity bytes
>   vmemoryuse   infinity kB
>   pseudo-terminals infinity
>   swapuse  infinity kB
>
> swapuse is set to unlimited, but stacksize is set to 512MB.
> Is it the stacksize setting that prevent my kernel to swap more then
> 512MB ?

No, I don't think so. datasize was the parameter I was most
suspecting; and it assumes that a particular process was causing the
crash (which is unlikely; the OS is supposed to protect you against
it). 

Most likely, the crash was not directly caused by a shortage of virtual
memory. You would have to diagnose through crash dumps, but it could be
that some more specific resource was exhausted. Or perhaps the memory
leak left dangling references in a vnode.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: cksum entire dir??

[Lowell Gilbert]

Paul Kraus  writes:

> On Tue, Sep 11, 2012 at 9:18 PM,   wrote:
>
>> It's a real shame Unix doesn't have a really good tool for comparing
>> two directory trees. You can use 'diff -r' (even on binaries), but that
>> fails if you have devices, named pipes, or named sockets in the
>> filesystem. And diff or cksum don't tell you if symlinks are different.
>> Plus you may care about file ownership, and that's where the stat
>> command comes in handy.
>
> Solaris and a least a few versions of Linux have a "dircmp" command
> that is in reality a wrapper for diff that handles special files. The
> problem with it is that it tends to be slow (I had to validate
> millions of files).

It's not clear what the danger profile is supposed to be here; dircmp
(and recursing 'diff' applications) can handle many cases, but mtree(8)
(with appropriate options) covers more pathological problems. Even so,
analysis of changes in file nodes like named sockets will usually
require some understanding of the application.

I suspect that either a recursive diff or an mtree specification is a
good solution for the original poster's problem, but we don't have
enough information to be more sure than that.

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

Re: Swapped memory limited to about 500MB for a process ?

[Lowell Gilbert]

Mickaël Canévet  writes:

> I was impacted by a memory leak that has been fixed by this patch:
> http://people.freebsd.org/~rmacklem/namei-leak.patch
>
> What I noticed when the server was paging is that it seems that only
> about 500MB of my 4GB swap partition was used before crashing. I was
> wondering why it didn't take the whole 4GB up to the crash of the server
> because of lake of memory (that would let me more time to react).
>
> Is there such king of setting that prevent a process to put more then
> 500MB of data in swap ?

limits(1)?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Firefox install problem

[Lowell Gilbert]

Mario Lobo  writes:

> 2012/9/4 Warren Block 
>
>> On Tue, 4 Sep 2012, Waitman Gobble wrote:
>>
>>  On Sep 4, 2012 7:03 PM, "Mario Lobo"  wrote:
>>>

 All I've done was "csup -L 2 ports-supfile" with ports-www in it.
 Then cd /usr/ports/www/firefox; make with default options.

 As for my /etc/make.conf

 CPUTYPE?=nocona
 OVERRIDE_LINUX_BASE_PORT=f10
 OVERRIDE_LINUX_NONBASE_PORTS=f10
 WITH_KDE4=yes
 WITH_CUPS=yes
 WITH_ICONS=KDE4
 WITHOUT_GNOME=yes
 PYTHON_DEFAULT_VERSION=python2.7
 PERL_VERSION=5.10.4

 If it is its fault, it will be the first time in around 3,5 years.

>>>
>>> did you _only_  csup www in ports? ill have to check but im not sure
>>> libvpx
>>> is in www... im not in a place to check at this exact second but my memory
>>> is that is providing webm support so probably in audio or multimedia
>>>
>>
>> multimedia/libvpx would not have been updated.  Selectively updating ports
>> is not supported.  Symlinking libraries to missing versions is often a
>> source of mysterious problems later.
>>
>
>
> I had run csup with ports-multimedia since the first libvpx error came up!.
> Libvpx was already up to date by the way, and correctly installed. So i did
> not Symlink a library to any "missing version".

But not necessarily the version that your other ports had been tested
against. This can lead to mysterious problems, as you may have noticed.

> "Selectively updating ports is not supported".  Then I must wonder why do
> we have the option to put "ports-{$port}" inside the supfile, and not a
> mandatory ports-all.

Sometimes, for some purposes, it works, and keeping it around helps some
experts (especially porters). But "not supported" means "please
don't ask us to help you use it." That is, you should update the whole
port tree and update all dependent ports before reporting a problem.

Here is what you should do:

  (1) Update your ports tree. You can use any method to do this
  (e.g. cvs, cvsup, subversion, portsnap), but update the whole tree
  at the same time.

  (2) If step (1) did not update your INDEX file, update it
  now. Possible methods include "make fetch" and "make index". I you
  use portupgrade, "portsdb -Uu" is the best way.

  (3) cd /usr/ports && make clean
  Kind of overkill in most cases, but when your port tree is
  building in bogus directories for no apparent reason, overkill may
  save your butt.
  
  (4) Upgrade all of the ports that firefox depends on (and the ones
  they depend on). Tools like portmaster or portupgrade make this
  much easier.

  (5) Rebuild the vpx port, even if it's already up to date.

  (6) Then rebuild the firefox port.

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

Re: asking for help about "acpi_tz0: _CRT value is absurd, ignored (256.0C) "

[Lowell Gilbert]

Warren Block  writes:

> On Tue, 4 Sep 2012, Lowell Gilbert wrote:
>
>> "chiehhan"  writes:
>>
>>> To whom may concern,
>>>
>>> I am a greenhorn in the field of freebsd.And when I install
>>> Freebsd9.0 on my laptop HP NX6330,a control spam "acpi_tz0: _CRT
>>> value is absurd, ignored (256.0C)"occurs.
>>>
>>> I learned some reference about sysctl and revised the configure file 
>>> sysctl.conf,adding two lines below into sysctl.conf:
>>> hw.acpi.thermal.user_override=1
>>> hw.acpi.thermal.tz0._CRT=110.0C
>>> but the control spam remains.
>>>
>>> I read the source code about acpi_thermal.c,but still have no idea
>>> about how to solve this problem.I am a little desperated and turn
>>> freebsd-questions@freebsd.org for help.Would you please send me a
>>> solution?
>>
>> A solution to what problem? The "ignored" message isn't a problem on its
>> own; do you think it causing some other trouble that you didn't describe?
>
> I have a similar HP system.  That message is logged a couple of times
> a minute, hiding other messages in the logs and making them roll over
> quickly.  That particular system is a Pentium D which wasn't really
> worth much effort, but it would still be nice to see this annoyance
> fixed.

Yes, I would agree that a repeated message is much more of an annoyance
than having it just happen once at boot time. With a Pentium D, there
probably isn't a core temperature monitor at all (I *think* that's true
for all of them, but it's definitely true for some), so you just want to
turn the messages off.

Unfortunately, I can't browse sources now, but I think that what happens
might be controlled by events going through devd. If that's correct, you
should be able to add an event rule to drop events related to your
non-existant thermistor (or delete one that already exists). You also
might be able to change the polling period for the thermal device.

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

Re: Firefox install problem

[Lowell Gilbert]

Mario Lobo  writes:

> env:
> FBSD 8.3-STABLE AMD64
> Firefox 15 port
>
> The problem seems to be with the porting itself.
>
> The first problem showed up during configure. Libvpx could not be found and
> configure stops.
> After examining Config.Log, I found  a compiler switch like this:
>
> -L/usr/local/lib/nss
>
> I made a symlink there to libvpx.so and the port compiled without errors.

That's an incredibly ugly solution; if the vpx port were installed
correctly, it would have been detected, so you're probably just hiding a
real problem.

> Then after issuing a make install, this comes up everytime:
>
> [Snip]
> a ./searchplugins/yahoo.xml
> a ./dictionaries/en-US.aff
> a ./dictionaries/en-US.dic
> a ./defaults/pref
> a ./defaults/pref/channel-prefs.js
> a ./chrome/icons
> a ./chrome/icons/default
> a ./chrome/icons/default/default16.png
> a ./chrome/icons/default/default32.png
> a ./chrome/icons/default/default48.png
> /usr/ports/www/firefox/work/mozilla-release/config/nsinstall -D
> /usr/ports/www/firefox/work/fake/bin
> rm -f -f /usr/ports/www/firefox/work/fake/bin/firefox
> ln -s /usr/ports/www/firefox/work/fake/lib/firefox/firefox
> /usr/ports/www/firefox/work/fake/bin
> gmake[1]: Leaving directory
> `/usr/ports/www/firefox/work/mozilla-release/browser/installer'
> echo 'share/applications/firefox.desktop' >>
> /usr/ports/www/firefox/work/plist_files
> echo "@dirrmtry share/applications" >>
> /usr/ports/www/firefox/work/plist_dirs
> echo 'share/pixmaps/firefox.png' >> /usr/ports/www/firefox/work/plist_files
> /bin/mkdir -p /usr/ports/www/firefox/work/fake/libdata
> /bin/mv -f /usr/ports/www/firefox/work/fake/lib/pkgconfig
> /usr/ports/www/firefox/work/fake/libdata/ || true
> mv: rename /usr/ports/www/firefox/work/fake/lib/pkgconfig to
> /usr/ports/www/firefox/work/fake/libdata/pkgconfig: No such file or
> directory
> /bin/rm -f /usr/ports/www/firefox/work/fake/lib/pkgconfig
> cd: can't cd to /usr/ports/www/firefox/work/fake/include
> *** Error code 2
>
> Stop in /usr/ports/www/firefox.
> *** Error code 1
>
> Stop in /usr/ports/www/firefox.
>
> All the fixes I googled that could relate to this, date back to 2005 the
> latest,, and none of them helped.
>
> I've been trying to fix this for 2 days now and I'm not getting anywhere so
> I can only hope someone can shed a light on this problem here on the list..
>
> My sincere thanks to whoever points me a direction.

You've done something really weird (in particular, the "work/fake"
directory would not exist or be referenced in a normal ports
installation). Try emptying your /etc/make.conf and starting from
scratch.

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

Re: asking for help about "acpi_tz0: _CRT value is absurd, ignored (256.0C) "

[Lowell Gilbert]

"chiehhan"  writes:

> To whom may concern,
>
> I am a greenhorn in the field of freebsd.And when I install Freebsd9.0 on my 
> laptop HP NX6330,a control spam "acpi_tz0: _CRT value is absurd, ignored 
> (256.0C)"occurs.
>
> I learned some reference about sysctl and revised the configure file 
> sysctl.conf,adding two lines below into sysctl.conf:
> hw.acpi.thermal.user_override=1 
> hw.acpi.thermal.tz0._CRT=110.0C 
> but the control spam remains.
>
> I read the source code about acpi_thermal.c,but still have no idea about how 
> to solve this problem.I am a little desperated and turn 
> freebsd-questions@freebsd.org for help.Would you please send me a solution? 

A solution to what problem? The "ignored" message isn't a problem on its
own; do you think it causing some other trouble that you didn't describe?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"