cvsup to RELENG_4 = 5.0-CURRENT?

[Andy]

I just cvsup'd from my freshly installed 4.0 system, using the following
supfile, and now that I reboot, and do a uname -a; I find I am in
5.0-CURRENT?  

supfile is:
# Defaults that apply to all the collections
*default host=cvsup5.FreeBSD.org
*default base=/usr
*default prefix=/usr
# The following line is for 4-stable.  If you want 3.x-stable, change
# "RELENG_4" to "RELENG_3".
*default release=cvs tag=RELENG_4
*default delete use-rel-suffix
*default release=cvs tag=.
*default compress
src-all
cvs-crypto
ports-all

My uname -a output is:

FreeBSD phreakr.lewman.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Wed Mar
22 23:44:39 EST 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/PHREAKR  i386


Did I miss something?


-- 

|  Andy   | e-mail  |  web   |
| | [EMAIL PROTECTED] | www.lewman.com |

Worst Month of the Year:
February.  February has only 28 days in it, which means that if
you rent an apartment, you are paying for three full days you don't
get.  Try to avoid Februarys whenever possible.
-- Steve Rubenstein


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: cvsup to RELENG_4 = 5.0-CURRENT?

[Andy]

[EMAIL PROTECTED] wrote:

> > *default release=cvs tag=RELENG_4
> > *default delete use-rel-suffix
> > *default release=cvs tag=.
> 
> Notice your mistake?

Apparently, yes I did miss something.  Jeez, I need sleep.  Duh. 
Thanks, and sorry to bother everyone with that.  :P

-- 

|  Andy   | e-mail  |  web   |
| | [EMAIL PROTECTED] | www.lewman.com |

Bore, n.:
A guy who wraps up a two-minute idea in a two-hour vocabulary.
-- Walter Winchell


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: Aureal Vortex2 (Mx300) driver?

[Andy]

On Fri, 14 Apr 2000 [EMAIL PROTECTED] wrote:

>   Just a doubt?
>   Is there anyone working on a Aureal Vortex 2 driver?
>   I mean, a not kernel-panic version?

I think the issue may be that Aureal won't release their chip
specs without paying some exhorbitant fee.  I spoke with various people in
their company about getting an SDK, or even just documentation as to how
the chips work.  For a fee of around $US20k, they'd be happy to send them
to me.  On top of which, I couldn't release the source, nor the
specs.  The company appears to be in disarray in general.  I remember
reading something about their executive team leaving all at once.

Anyway, from my perspective I don't think Aureal will open the
specs soon.  


-- 

|  Andy   | e-mail  |  web   |
| | [EMAIL PROTECTED] | www.lewman.com |

Tell me, O Octopus, I begs,
Is those things arms, or is they legs?
I marvel at thee, Octopus;
If I were thou, I'd call me us.
-- Ogden Nash



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: FreeBSD 3.5 now available . . . . .

[Andy]

On Fri, 30 Jun 2000, Doug Barton wrote:

> > And honestly, I don't have the time to debug
> > it.  It didn't work, I went back to what worked.  Is that so bad?
> 
>   Nope, it's your life, spend the time whatever way feels right to you.
> However, I think most of us would appreciate it if you don't "knock"
> something you're not willing to put even the smallest amount of effort
> into improving. 

I was going to let this go, but not now.  My opinion is just one
data point on a whole range of points about stability.  Just because I
don't take the time to re-submit the same PR doesn't mean I don't
help.  I've offered to help with many things in the FreeBSD community,
they just aren't code related.  My coding skills aren't on par with
anything written for FreeBSD today.  I volunteered to call Aureal to get
sound drivers, and offered Cameron Grant any sound board he wanted, if it
would help him develop drivers for it.  I called Aureal, and some of the
other sound chip vendors, to get an SDK that an open source OS could
use.  I don't have US$10,000 to volunteer to a project so they can get an
SDK, sorry.
I've learned my lesson, any digression from the norm in BSD land
is just bad.  God forbid someone raise a flag that everything isn't as
smooth as is believed.  Next time, I'll just keep my mouth shut.  Jeez.

-- 

|  Andy   | e-mail  |  web   |
| | [EMAIL PROTECTED] | www.lewman.com |

In Corning, Iowa, it's a misdemeanor for a man to ask his wife to ride
in any motor vehicle.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: Hardware Info

[Andy]

On Fri, 14 Jul 2000, Vivek Khera wrote:

> >> Is there a way to get a map of the ports, irq, dma in use on a FreeBSD
> >> system? Maybe information similar to what one sees in Windows device
> >> manager.
> 
> A>Does "vmstat -i" provide the detail for which you seek?
> 
> That doesn't list ports and DMA.  Try "cat /var/run/dmesg.boot" and
> read through it.

He mentioned "in use".  Is there a way to get similar output to
vmstat -i for ports and dma?

-- 

|  Andy   | e-mail  |  web   |
| | [EMAIL PROTECTED] | www.lewman.com |

The human mind ordinarily operates at only ten percent of its capacity
-- the rest is overhead for the operating system.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: csup not updating all files

[Andy Farkas]

On Wed, Feb 9, 2011 at 7:31 AM, John Baldwin  wrote:

> On Tuesday, February 08, 2011 2:39:49 pm Richard Kuhns wrote:
>
>> Sorry to followup on my own post, but I figured out what was going on. It
>> appears to be a problem with csup.
>>
>> I've been using csup to maintain 2 CVS Repositories, one at home and one at 
>> work.
>>
>> The last couple of times I've run csup there were lots of 'checksum 
>> mismatches',
>> so csup said it would download the entire file. I was watching it this 
>> morning
>
> Hmm, I noticed this recently as well, but wasn't sure if anyone else had seen
> this.

The 'checksum mismatches' are especially annoying when a new tag is applied
to the tree. Practically the entire src repo is downloaded again :(

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

Intel c602 chipset support?

[Andy Dills]

Hi there,

Does anybody know if there are plans to support the Intel c602 chipset any 
time soon?

Thanks,
Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

FreeBSD 8.3-R sysinstall does not "see" disks that are recognized during boot

[Andy Dills]

I've got a new supermicro server I'm trying to get FreeBSD on. It uses the 
Intel c602 chipset, and it's my understanding that support for that 
chipset (c60X) was recently added via the isci driver. Ok, great, that 
explains why 8.2-R and 9.0-R didn't see the drives.

So, I grabbed the memstick image of 8.3-RELEASE that is on the ftp server, 
booted it up, and sure enough, as the dmesg scrolls I see it now properly 
recognizes da0 and da1, as it should (the memstick is da2). It sees the 
disks fine at this point, everything looks good.

However, once the system finishes booting and loads into sysinstall, and I 
go to partition the drives, I get "No disks found! Please verify that your 
disk controller is being properly loaded at boot time".

Any suggestions for avenues to troubleshoot this?  I have pictures to 
document if it helps.

Seems very odd. I confirmed the behavior with the SATA set to IDE, AHCI, 
and RAID modes. (The drives were recognized as da0 and da1 during bootup 
in all three modes, but not by sysinstall.)

Thanks,
Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

RE: FreeBSD 8.3-R sysinstall does not "see" disks that are recognized during boot

[Andy Dills]

On Wed, 18 Apr 2012, Harris, James R wrote:
> 
> Andy and I worked this out offline - workaround was to go to 
> Options|Re-scan which caused the devices to show up in the sysinstall 
> menu.  I'm adding details here for future reference.
> 
> 1) C60x chipsets have the 6 traditional SATA ports, plus 4 or 8 SAS 
> ports.  Only the latter are controlled by the isci(4) driver.
> 2) The IDE/AHCI/RAID modes apply only to the traditional SATA ports.
> 3) In Andy's case, going to Options|Re-scan Devices caused the disks to 
> show up.  This problem seems to be system or platform-dependent, as I 
> was not able to reproduce with 8.3 memstick image on my C600 systems.
> 4) There was a problem with initial device scan using isci(4) on 
> 7-STABLE, which necessitated r233371.  This was MFC'd back to 8-STABLE, 
> but after 8.3 was released.  I'm fairly convinced this is the root cause 
> of Andy's problem, but don't have any easy way to verify.

First, I want to thank James and the other responders for help getting me 
squared away.

Something that may be of specific use for others (James has covered the 
most relevant points...at blazing speed, what an asset to the community), 
is that the isci support in 8.3-R will now enable FreeBSD compatibility 
with most of the new Supermicro server platforms. 

And a new lesson was learnedfirst thing to try when sysinstall fails 
to recognize hardware is to re-scan devices. Never needed that across 
thousands of installs (dating to 2.2.8), and didn't even know it existed.

Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Intel c602 chipset support?

[Andy Dills]

On Thu, 19 Apr 2012, G??t Andr??s wrote:

> Hi,
> 
> Could you try FreeBSD it on a machine with a chipset like this?

8.3-RELEASE is the first version (outside of -CURRENT) to support the 
Intel c60X chips.

So, yes, FreeBSD does support the chipset now. Works great, I only had a 
small problem with sysinstall needing to re-scan devices to see the 
drives (but that's a sysinstall bug, see the other thread for details).

Thanks,
Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 7 installs where FreeBSD 8 wont due to CD

[Andy Farkas]

On Wed, Dec 8, 2010 at 7:17 PM, Bruce Cran  wrote:
> On Wed, 08 Dec 2010 01:00:34 -0800
> per...@pluto.rain.com wrote:
>
>> Go into Fixit# and examine /dev and/or the dmesg.
>
> The problem is there's no "ls" in FixIt mode so you need to use
> "echo *" to see what files are present.

Why is this so?

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

Re: FreeBSD 7 installs where FreeBSD 8 wont due to CD

[Andy Farkas]

> So since "ls" wasn't required it wasn't included.

I just booted an old 6.1-RELEASE CD and selected Fixit mode...

ls -lF works as expected!

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

Re: PPP doesn't set the correct interface in 7-STABLE

[Andy Dills]

On Wed, 6 Aug 2008, Mike Tancsa wrote:

> At 10:16 AM 8/6/2008, Andy Dills wrote:
> 
> > I'm trying to setup pptpd to enable VPN connections. This worked well in
> > all versions of FreeBSD prior to 7.
> 
> I would turf pptpd and look at mpd51 from the ports. It is far, far better
> maintained and is quite solid as an LNS as well as PPTP termination server.

Yep, it looks like this is definitely the best solution, for a number of 
reasons.

Thanks for the pointer.

Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: rdump stuck in sbwait state (RELENG_7)

[Andy Kosela]

I'm pretty sure it's caused by FreeBSD.  It can very well be related to
PR 117603, a real nasty dump(8) bug that was introduced in 7.0 on SMP
systems.  But it should have been patched back in March by this:

jeff 2008-03-13 00:46:12 UTC

FreeBSD src repository

Modified files:
sys/kern subr_sleepqueue.c
Log:
PR 117603
- Close a sleepqueue signal race by interlocking with the per-process
spinlock. This was mistakenly omitted from the thread_lock patch and
has been a race since.

MFC After: 1 week
PR: bin/117603
Reported by: Danny Braniss 

Revision Changes Path
1.48 +5 -2 src/sys/kern/subr_sleepqueue.c

So I'm real surprised it shows up again. We got a pretty large backup
environment with dump(8) being a critical element of it.  I just hope
the problem will be resolved before 7.1-RELEASE hit the streets.

Terry, please file a bug report on this and get in touch with iedowse@
who was implementing the aforementioned patch.

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

Re: strange abort with kcheckpass

[Andy Fawcett]

On Tuesday 12 January 2010 17:49:25 Damian Weber wrote:
> Hi, all,
> 
> I've got a strange SIGABRT issue with kcheckpass.
> Of course, kcheckpass is not contained in the base
> system, yet I write to this list since the base system
> could be able to help with tracking this down.
> (kcheckpass is called from a screen locker which fails
> to operate properly as a consequence of the SIGABRT.)
> 
> Normal behaviour:
> (for example with wrong password)
> $ kcheckpass
> Password:
> Authentication failure
> 
> Strange behaviour here (called mybox below):
> $ kcheckpass
> Abort trap: 6
> 
> I've recompiled the kcheckpass part of the kdebase3
> port with option -g.
> Starting with debugger even doesn't let me reach a
> breakpoint at main(), because the SIGABRT happens
> earlier.
> 
> # pwd
> /usr/ports/x11/kdebase3/work/kdebase-3.5.10/kcheckpass
> 
> # ldd ./kcheckpass
> ./kcheckpass:
> libkdefakes.so.6 => /usr/local/lib/libkdefakes.so.6 (0x68193000)
> libpam.so.4 => /usr/lib/libpam.so.4 (0x68195000)
> libjpeg.so.10 => /usr/local/lib/libjpeg.so.10 (0x6819c000)
> libthr.so.3 => /lib/libthr.so.3 (0x681d)
> libc.so.7 => /lib/libc.so.7 (0x6808)
> 
> # gdb ./kcheckpass
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
>  are welcome to change it and/or distribute copies of it under certain
>  conditions. Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-marcel-freebsd"...
> (gdb) b main
> Breakpoint 1 at 0x1470: file kcheckpass.c, line 297.
> (gdb) r
> Starting program:
>  /usr/ports/x11/kdebase3/work/kdebase-3.5.10/kcheckpass/kcheckpass
> 
> Program terminated with signal SIGABRT, Aborted.
> The program no longer exists.
> You can't do that without a process to debug.
> (gdb) q
> 
> $ uname -a
> FreeBSD mybox 7.2-STABLE FreeBSD 7.2-STABLE #18: Mon Dec 14 00:39:13 CET
>  2009 mybox  i386 $ ls -ld /var/db/pkg/kdebase*
> drwxr-xr-x  2 root  wheel  512 Jan 11 18:35 /var/db/pkg/kdebase-3.5.10_4/
> drwxr-xr-x  2 root  wheel  512 Jan 11 18:35
>  /var/db/pkg/kdebase-kompmgr-3.5.10_1/
> 
> Any ideas what's the cause or what I should try next to see where this
> abort comes from?
> 
> Thanks,
> 
>Damian

try debugging kcheckpass --nofork, as it will prevent the process forking off 
into the background.

A.

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

MFC of "Large set of CAM improvements" breaks I/O to Adaptec 29160 SCSI controller

[Andy Farkas]

Hi, firstly:

RELENG_8 csup'd with date=2010.02.14.00.00 works perfectly for days.

RELENG_8 csup'd with date=2010.02.15.00.00 dead-locks the disk I/O
subsystem. Network still operational but anything needing disk hangs.
Power-cycle required.

kernel config is GENERIC with KDB, DDB and BREAK_TO_DEBUGGER options added.

hardware:
ahc0:  port 0x4000-0x40ff mem
0xefa0-0xefa00fff irq 16 at device 0.0 on pci10
ahc0: [ITHREAD]
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

da0:  Fixed Direct Access SCSI-3 device
da1:  Fixed Direct Access SCSI-3 device


The dead-lock can happen at any time, but I can provoke it by running
a bonnie++ disk test. It happens doing rm -rf /usr/obj/usr and it has
happened doing a make installworld. It can survive a make buildworld
(the system runs normally until it decides to dead-lock).

The box (HP ProLiant ML 110) has 2 scsi disks and 4 sata disks. The
2010.02.15 kernel will run perfectly for days on the SATA disks. *Only*
when the scsi disks are accessed will the system dead-lock. Note that
the SATA disks do not work either if the system has dead-locked.

I can provide more details and a vmcore.0 if anyone is interested.

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

Re: MFC of "Large set of CAM improvements" breaks I/O to Adaptec 29160 SCSI controller

[Andy Farkas]

On Fri, Apr 30, 2010 at 4:42 AM, Pete French
 wrote:
>
> I've copied in the original poster of the problem to see how he is
> doing, but as far as I am concerned the problem has gone away. Certainly
> the things I was doing before to triger it no longer do so. Of course
> in the normal state of things it was rarely locking up (every few days)
> so I can't be sure just on a few hurs testing. But my initial impression
> is that this fixes it. Good work!
>

Confirming patch fixes problem. Thanks Alexander, good pick-up on finding
the missing bit of code!

bootverbose  <--  /me smacks forehead with palm of hand

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

Why doesn't this startup script execute on boot?

[Andy Dills]

I'm working on getting p0f integrated with amavisd-new. Everything is 
great, with the exception that I can't get the neccessary commands to 
execute on boot.

I started with rc.local and that didn't work. So I made this simple script 
in /usr/local/etc/rc.d/p0f:

---

#!/bin/sh

# PROVIDE: p0f
# REQUIRE: LOGIN
# BEFORE:  securelevel
# KEYWORD: shutdown


. "/etc/rc.subr"

name="p0f"
rcvar=`set_rcvar`

command="/usr/local/bin/p0f"
command_args="-l 'tcp dst port 25' 2>&1 | /usr/local/bin/p0f-analyzer.pl 2345 &"
pidfile="/var/run/$name.pid"

# read configuration and set defaults
load_rc_config "$name"
: ${p0f_enable="NO"}

run_rc_command "$1"

---


It does not execute on boot (yes, it's executable). It executes just fine 
by hand.

I'm assuming it has something to do with redirecting stdout and stderr to 
another script which is then shoved into the background? 

How do I work around this?

(BTW, FreeBSD 8.0-STABLE #2: Wed May 12 13:28:18 EDT 2010)

Thanks,
Andy


---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Why doesn't this startup script execute on boot?

[Andy Dills]

On Wed, 12 May 2010, Chuck Swiger wrote:

> Hi--
> 
> On May 12, 2010, at 4:46 PM, Andy Dills wrote:
> > I'm working on getting p0f integrated with amavisd-new. Everything is 
> > great, with the exception that I can't get the neccessary commands to 
> > execute on boot.
> 
> The amavid-p0fanalyzer script should have been installed if you used the port:

Well, isn't that convenient!

I decided after I had installed amavisd to add on the p0f support, I 
didn't realize there was an option to install that via port...I had just 
gone in and installed the p0f port by itself. But looking at the options 
for the amavisd-new, there it is indeed.

Thanks for your help.

Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

INET6 required for SCTP in 7.0?

[Andy Dills]

Hi there,

I'm not interested in enabling support for IPv6 for now. 

When I remove INET6 from the kernel configuration, I cannot compile the 
kernel without disabling SCTP. With fresh 7.0-STABLE source, here's the 
error output (INET6 disabled, but SCTP enabled):

uipc_syscalls.o(.text+0x3c1): In function `sctp_generic_recvmsg':
/usr/src/sys/kern/uipc_syscalls.c:2608: undefined reference to 
`sctp_sorecvmsg'
uipc_syscalls.o(.text+0x21a2): In function `sctp_generic_sendmsg_iov':
/usr/src/sys/kern/uipc_syscalls.c:2486: undefined reference to 
`sctp_lower_sosend'
uipc_syscalls.o(.text+0x249d): In function `sctp_generic_sendmsg':
/usr/src/sys/kern/uipc_syscalls.c:2379: undefined reference to 
`sctp_lower_sosend'
uipc_syscalls.o(.text+0x266c): In function `sctp_peeloff':
/usr/src/sys/kern/uipc_syscalls.c:2246: undefined reference to 
`sctp_can_peel_off'
uipc_syscalls.o(.text+0x28e6):/usr/src/sys/kern/uipc_syscalls.c:2287: 
undefined reference to `sctp_do_peeloff'
rtsock.o(.text+0xb7d): In function `rt_newaddrmsg':
/usr/src/sys/net/rtsock.c:897: undefined reference to `sctp_addr_change'
in_proto.o(.data+0xa8): undefined reference to `sctp_input'
in_proto.o(.data+0xb0): undefined reference to `sctp_ctlinput'
in_proto.o(.data+0xb4): undefined reference to `sctp_ctloutput'
in_proto.o(.data+0xbc): undefined reference to `sctp_init'
in_proto.o(.data+0xc8): undefined reference to `sctp_drain'
in_proto.o(.data+0xcc): undefined reference to `sctp_usrreqs'
in_proto.o(.data+0xdc): undefined reference to `sctp_input'
in_proto.o(.data+0xe4): undefined reference to `sctp_ctlinput'
in_proto.o(.data+0xe8): undefined reference to `sctp_ctloutput'
in_proto.o(.data+0xfc): undefined reference to `sctp_drain'
in_proto.o(.data+0x100): undefined reference to `sctp_usrreqs'
in_proto.o(.data+0x110): undefined reference to `sctp_input'
in_proto.o(.data+0x118): undefined reference to `sctp_ctlinput'
in_proto.o(.data+0x11c): undefined reference to `sctp_ctloutput'
in_proto.o(.data+0x130): undefined reference to `sctp_drain'
in_proto.o(.data+0x134): undefined reference to `sctp_usrreqs'



Is this intended and/or a known issue?

Thanks,
Andy


---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What's new on the 127.0.0/24 block in 7?

[Andy Dills]

On Mon, 3 Mar 2008, Chris H. wrote:

> Greetings,
> I'm having some difficulty working with anything past 127.0.0.1.
> It seems impossible to use (create) any addresses on the "loopback"
> past 127.0.0.1.
> More specifically; I installed rbldnsd from ports, and it worked quite
> well on a 6.x install. However, attempting the same config/install on
> a 7-RC3 install yields the inability to bind/create 127.0.0.2, or
> 127.0.0.3 for rbldnsd to answer on - all queries are refused. The
> same pinging/digging, etc.
> 
> The 2 servers have /exactly/ the same net setups, and DNS/rbldnsd
> configs. Yet no joy on the RELENG_7 box. So it /appears/ something
> in this area has changed since 6. But I'm unable to discover any
> info on it.
> 
> Thank you for all your time and consideration.

What subnet mask did you use when creating the 127.0.0.2 (etc) interfaces 
on lo0?

On 7.0-R, I just ifconfig'ed 127.0.0.2 as an alias to lo0 with a subnet 
mask of 255.255.255.255, and I was able to bind/listen/accept on it with 
no problem.

Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What's new on the 127.0.0/24 block in 7?

[Andy Dills]

On Mon, 3 Mar 2008, Chris H. wrote:

> > Are you sure it's a /24 you are talking about? My 7.0 disks install
> > 127.0.0.1/8 here.
> 
> Really? Where did you get the install disc? Mine clearly doesn't. :(
> All I am provided is 127.0.0.1 - not 127.0.0.2,3...

127.0.0.1/8 just means 127.0.0.1 with a netmask of 255.0.0.0. It doesn't 
imply a default behavior of binding to any other address than 127.0.0.1.

But I'm still really confused what you're trying to do...

See, the idea of returning multiple 127.0.0.X addressess within RBL is to 
convey different information while using a single zone. 

In the beginning, the RBLs would just reply with 127.0.0.1 and use 
different zones to imply different contexts...now you use a single zone 
with different 127.0.0.X addresses to convey the same information.

But...you don't actually do anything with that resolution beyond determine 
if a given record is listed or not. You don't actually need to configure 
or use the various 127.0.0.X addresses that might get returned.

On the other hand, if you're using multiple rbldnsd instances, one per 
zone... hile it's a pain you can indeed configured rbldns to serve 
multiple zones. Or just bind the additional loopback instances 


BTW, /etc/netstart is a nice shortcut to avoid fatfingering an ifconfig. 

Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What's new on the 127.0.0/24 block in 7?

[Andy Dills]

Just to provide a little information in case there is still confusion...


On Tue, 4 Mar 2008, Chris H. wrote:

> Quoting Greg Black <[EMAIL PROTECTED]>:
> 
> > On 2008-03-04, Chris H. wrote:
> > 
> > > Yes, adding an entry in /etc/rc.conf that provides 254 IP's now
> > > reveals:
> > > lo0: flags=8049 metric 0 mtu 16384
> > >inet6 ::1 prefixlen 128inet6 fe80::1%lo0 prefixlen 64
> > > scopeid 0x3inet 127.0.0.1 netmask 0xff00
> > > 
> > > as opposed to: 0x.
> > 
> > If you think the above shows evidence of providing 254 IP addresses,
> > it's really time either to catch up on some sleep or learn how these
> > things work.
> 
> Quite so. That was my point; adding netmask 255.255.255.0
> (0xff00) gave me 254 addresses. While the netmask
> 0x provides 1.

At the risk of being pedantic, I'm afraid that isn't true. If adding 
netmask 255.255.255.0 provided 255 addresses, adding the (default in every 
version of FreeBSD I'm aware of) netmask of 255.0.0.0 would provide 
255x255x255 addresses. That said, there is no way to ifconfig multiple 
addresses with a single address entry.

The netmask of an IP bound to an interface determines the scope of the 
logical network that can be reached through the given interface, not a 
range of addresses bound to the interface. So, 127.0.0.1 with a mask of 
255.255.255.0 means 127.0.0.0-255 would be reachable via lo0, whereas 
127.0.0.1 with a mask of 255.0.0.0 means 127.0-255.0-255.0-255 would 
be reachable via lo0.

In neither case would 127.0.0.2 be bound to lo0 implicitly, you would need 
to explicitly ifconfig them as aliases for them to be bound to lo0.

No worries regardless, netmasks are a common source of misunderstanding 
and confusion. In a routing context, the subnet mask does indeed affect 
every address within the subnet, however when binding addresses to an 
interface, the subnet mask merely controls which addresses are reachable 
locally on layer 2.

Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: INET6 required for SCTP in 7.0?

[Andy Dills]

On Wed, 5 Mar 2008, Mark Andrews wrote:

>   It would be better to remove the option all together.  IPv6
>   is no longer a protocol under development.  There is no
>   need to make it optional any more.  Having it there really
>   sends the wrong signal.

With all due respect, let's face a couple of facts.

IPv4 is going to be the primary protocol for several years to come. There
are a few critical reasons, and few people like to point out just how
naked the emperor is:

- Providing IPv6 currently (and for the forseeable future) provides no
return on investment (ROI). Service Providers can't make more money with
IPv6, businesses do not get any sort of competitive or perceived advantage
from deploying IPv6, and end users certainly don't want to deal with it.

- To route IPv6 with the same features and packet forwarding rate as with 
IPv4, nearly every network will be forced to purchase expensive router 
upgrades with no other real benefit beyond IPv6 connectivity (which again 
provides no ROI to justify the capex). Nobody is going to do forklift 
upgrades just for IPv6, but as routers get normally upgraded IPv6 
functionality will indeed slowly expand.

- IPv6 provides almost no technological upgrades beyond additional address
space. DHCP addressed the auto configuration feature, VPNs addressed
IPsec.

- IPv4 address spaces will eventually transition to a market commodity
model, providing a financial incentive that will encourage significant   
optimization and provide motive for providers to audit their allocations,
and for businesses to part with IP space that they no longer properly 
utilize. The cost of acquiring IPv4 space will be less than the cost of
upgrading to IPv6.

Therefore, given a lack of ROI or sufficient technological motivation, and
given the significant potential for optimization of existing IPv4 space   
both via technology and financial incentive, I see a minimum of five years
before IPv6 is common. 

In the meantime, I'd like to only enable IPv6 on IPv6 enabled networks.

Andy
   

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: INET6 required for SCTP in 7.0?

[Andy Dills]

On Wed, 5 Mar 2008, Pete French wrote:

> O.K., have snipped all the above IPv4 stuff, which actually seems quite
> reaosnable (though appears to foorget about STF), but this line...
> 
> > In the meantime, I'd like to only enable IPv6 on IPv6 enabled networks.
> 
> ...I fail to see how not wanting to enable it leads to you wanting
> to remove it from the kernel entirely ? That is the bit I don't understand
> about all of this discussion. Theres probably hundereds of bits in the kernel
> you havent enabled and don't use, why specificly do you want an option
> to take IPV6 out ?
> 
> I am genuinely piuzzled - why isn't "ipv6_enabled="NO" sufficient ? That's
> what I do on IPv4 networks and it works fine for me.

That's actually a good point. I've had a hard time shedding my "trim 
everything I don't use out of the kernel" mentality over the years.

Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: INET6 required for SCTP in 7.0?

[Andy Dills]

;   My ISP doesn't support IPv6 yet though I know that have
>   IPv6 netbocks for themselves now if not for the customers
>   at this stage.

Oh, they have them for the customers. They just don't want to upgrade 
their routers.

>   There is a reasonable chance that this mail will leave here
>   over IPv6 for some of the recipients.  It will almost
>   certainly travel over IPv6 for at least one hop.

s/IPv6/uucp/ ;)

Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: list spam

[Andy Greenwood]

Chris H. wrote:

Quoting Stephen Montgomery-Smith <[EMAIL PROTECTED]>:


Mike Lempriere wrote:
I've had it with the list spam -- is the any possibility of 
moderating this list, or changing it to must-be-subscriber-to-post?





I have the opposite experience.  I am amazed at how little spam this 
list gets.  So far today, only one piece of spam - from the ports list.


I'd have to agree. I'm subscribed to several of the FBSD lists. Yet
in any 30 day period, the most I've received is less than 4. I'd
have to say, that's a pretty good ratio. :)

--Chris H


Same here.




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]"








___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Current status of support for high end SAN hardware

[Andy Kosela]

Hi all,
What is the current status of support for high end SAN hardware in FreeBSD?
I'm especially interested in support for HP EVA/XP disk arrays, Qlogic
HBAs, multipathing.
How FreeBSD compares in this environment to RHEL 5?

-- 
Andy Kosela
ora et labora
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

console access

[Andy Kosela]

--On June 7, 2008 2:16:26 PM -0700 Jo Rhett 
wrote:

> On Jun 5, 2008, at 11:35 AM, Paul Schmehl wrote:
>> It's not quite that simple.  To do that, I have to block out time to
>> drive 45 miles during my supposed "off" hours and do the upgrade
>> there.  Because, if it breaks networking and I'm at home, the server
>> will be down for at least an hour until I can drive to the hosting
>> company, get access to the server and restore the old kernel.
>
> Paul, you should arrange with your colocation provider to get an out of
> band serial connection to the system, and configure the console to go to
> the serial port.  We provide that for free at $EMPLOYER and most other
> places I know of do it for free or nominal charge.
>

or if your colocation provider is using any modern server hardware
(HP, Dell, IBM) and I bet
they do, they should give you lights-out access (HP's ILO2, Dell's
DRAC). Then you can even
remotely mount iso images from your laptop at home directly on the
server (very handy sometimes).

-- 
Andy Kosela
ora et labora
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3

[Andy Kosela]

ernel, userland and any third party application they support. They backport
all security and bug fixes to the "so called" stable release during those seven
years. That is a long time in the open source world, as in the general
computing world. They can do this because they have resources for
that - they are operating as a commercial company.

In FreeBSD even if you upgraded cleanly base system (this is very easy
and fast now with freebsd-update(8)) there is always problem with ports.
I'm perfectly aware that developers are more focused on the base system
and ports are served on "as is" basis but most of the production systems
deployed worldwide are using ports and depends on them most of their time.
I also understand ports team in saying that there is no resources to have
many branches of ports tree at the same time, but this little example will
show that in the long term sometimes things are not working very smoothly
for people who are running mission critical systems. Let's say some
hypothetical 6.x-RELEASE comes out in January. The Apache port is
freezed at hypothetical 2.0.40 version. Now in April someone discloses
some very critical security flaw which affects all versions of Apache prior
to 2.0.43. Now what you can do? You can update your Apache port to
2.0.43 fixing a security hole. But at the same time you don't know the
upstream team changed dramatically some internal things in code, added
tons of new features and at the same time introduced a ton of new bugs
and possibly new security flaws which will be founded at a later time.
Those changes in code can also very well break your applications which
depended on the specific code in 2.0.40 version. So you are left with
headaches and backup tapes (of course you would first test the upgrade
process on the test machines). But my issue here is that ports really do
not offer real stability for mission critical systems who often depends for
years on specific versions of particular software (like banks). Red Hat in
that case backports new security patches to those old stable versions and
it seems it is some solution for such businesses. Of course I know there is
no resources for creating supported -SECURITY branch of ports tree which
would backport those patches.

FreeBSD has always been known for its legendary stability and mature
code base which is why many commercial companies depend on it every
day. "The anomaly" as someone said of long term support for 4.x releases
only helped to see FreeBSD as more stable and viable solution than Linux by
many businesses. Mission critical systems needs long term support (read: at
least backporting security patches) and stable systems that can run for years
without interruption. When it comes to stability vs development maybe there is
time to rethink FreeBSD overall strategy and goals. Major companies using
FreeBSD in their infrastructure like Yahoo! or Juniper Networks would
definetly benefit from such moves focused on long term support of stable
releases. I honestly think it is in their interest to support, even financially

-- 
Andy Kosela
ora et labora
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Current status of support for high end SAN hardware

[Andy Kosela]

On Mon, Jun 9, 2008 at 12:36 PM, Russell Vincent <[EMAIL PROTECTED]> wrote:
>
> The FreeBSD support for multipath/SAN is fairly poor. It's fiddly
> to get to work and boot times are a little variable (into the
> minutes) as it tries to discover the devices.  Once it is configured
> and booted, it just works as long as things don't go wrong.  SAN
> outages cause the machine to hang up until the issue is resolved
> (in which case it just seems to continue) or it doesn't recover at
> all and requires a reboot.  Note that I don't spend a significant
> amount of time on this, so it may be that I could do things a little
> better.  I have also not tested the failover stuff very well (I
> only upgraded this machine to 7-STABLE fairly recently).  Disk
> access seems to be restricted to a single path at a time.  Problem
> solving is very tricky as there is very little information to trace
> which path/disk refers to which fabric/storage device/LUN.
>

Russell,
Thank you for your insights. It's good to see you have no problems
with isp(4) and Qlogic HBAs. Though I'm concerned about
multipathing. We run 6.x-RELEASE releases so it seems we have
to upgrade to 7.0-RELEASE to achieve that goal. gmultipath(8)
code is fairly new so I suppose it's not that mature yet as in
Linux. Unfortunately it is only an active/passive approach with
no load balancing (the active path is active until a BIO request is
failed with EIO or ENXIO)

Good support for high end SAN environment is essential in
todays data centers, as most servers are connected to storage
using FC based storage area network. I hope things will improve
as 7.x-STABLE will be polished over time.

Mark, I completely agree with you that ZFS is much better than
Ext3+LVM2. Ext3 is still lacking internal snapshoting capability,
so it's even inferior to UFS2. As a matter of fact I'm watching
Oracle's btrfs development as it seems it will change many
things on Linux filesystems scene. Though I still fear ZFS on
FreeBSD is not as yet mature to the point of using it in a mission
critical 24x7 production environments. But it's definetly something
to watch out for.

-- 
Andy Kosela
ora et labora
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: CLARITY re: challenge: end of life for 6.2 is premature withbuggy 6.3

[Andy Kosela]

Robert,
Thank you for your insights. I think that this agreement between users and
developers does occur. The proper balance between rapid development vs
long term stability is the platform through which such agreement can be
achieved. It's up to the Core Team to reasonably steer the Project in such a
way as to achieve the greatest results.

FreeBSD has always been focused on creating simple, stable and reliable
operating system for system administrators and let's keep it that way. Longer
term support for -RELEASE gives many companies a stable platform to
develop and maintain their infrastructure. I think 5 years support for major
FreeBSD release (like major 6 or 7) would be really perfect for many of us.

On Wed, Jun 11, 2008 at 1:26 PM, Marian Hettwer <[EMAIL PROTECTED]> wrote:
> But there is a way around. As soon as you have several FreeBSD boxes, I'd
> advise you to install your own FreeBSD box for packages building.
> So if you need to update your php installations, go to your build box
> (which has the very same versions of programs installed as your production
> boxes), update your ports tree and do a "make package" of your new php
> port.
> If the new php package works fine on your build box, roll it out via
> "pkg_add -r $NEWPHPTHINGY" and off you go.

I think Anton raised a valid and reasonable point here by analyzing my
previous statements. Every data center environment test the upgrade process
before deploying it on production machines, but my point circulated around
the whole different theme.

Backporting
Backporting security and bug fixes to *STABLE* versions of ports would
definetly render the whole ports framework infrastructure more solid
and trustworthy for organizations that need mission critical stable and
reliable environment to work in. Creating -SECURITY branch of ports tree
with support *just* for common server applications like apache, postfix,
mysql or vsftpd (definetly not for all available ports) would very well
encourage more companies now stuck with the only alternative
(redhat/centos or debian) to trust this ports tree branch in deploying
their applications which very often needs specific versions of the
software to run properly. Right now it's sometimes very risky to jump
to the latest available upstream version as it very often breaks
compatibility with older versions.

I've been toying with the idea to create such -SECURITY branch, at
least just for ports I use extensively. I'm not aware of no such
project (open source, commercial) that is doing that. I'm curious
how many people out there would be also interested in such an idea.

> If you take a close look onto how the debian project is backporting
> security fixes you would probably agree that pretty often it's more
> desireable to jump to a newer version of that software than instead just
> security fixing it.
> Examples needed?
> MySQL 4.1.11 was the "stable" MySQL 4.1 in Debian Sarge. Of course it got
> security fixed, but not bugfixed. You get a secure version of MySQL 4.1 in
> Debian but not a stable one, because important bugfixes are missing.
> I'd rather upgrade to the latest MySQL 4.1.xx instead.
> And of course, do your testing before jumping version numbers.

Redhat/CentOS is more reliable here as backports involves both security
and bug fixes, plus even new hardware enhancements.

-- 
Andy Kosela
ora et labora
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

CLARITY re: challenge: end of life for 6.2 is premature withbuggy 6.3

[Andy Kosela]

On Wed, Jun 11 2008, Robert Watson wrote:

On Wed, 11 Jun 2008, Paul Schmehl wrote:
>> From a security standport, backporting fixes to previous versions of ports
>> creates a difficulty.  It's much harder to tell, for example, if a RedHat
>> "port" is vulnerable or not, because RedHat uses their own proprietary
>> versioning system to define "where" a particular "port" is at.
>>
>> So, while your system might *say* it's running php version 5.2, it's really
>> *not* vulnerable because in RedHatese it's version 5.2.1.6.92000.p-2.1 (I'm
>> just making that up.)
>>
>> If this idea ever gets off the ground, I *hope* the folks involved with find
>> a rational, logical way to define the versioning so that it's not
>> hieroglyphics to the average person.

Egyptian hieroglyphics was a very noble system the secret of which was,
in the days of old, in the possession only of the Hierogrammatists, or
initiated
Egyptian priests. Many occult alphabets and ciphers derived its origin from
egyptian sacred ciphers, as also everything we know as cryptography today.
I guess our english alphabet would be equally strange and uknown to them.
But reading widely available documentation on Redhat's versioning system
would definetly help in understanding its details.

Everything after second - (dash) like in ftp-0.17-33 is Redhat's release
version. In this case this is thirty third release or patch. It is similar to
FreeBSD's naming convention.
You can check changelog and see what has changed since release 1
by issuing:
$ rpm -q --changelog 

So the system is very clear and precise, just like FreeBSD system.
The only difference is that upstream version of the package changes
a lot more often than on redhat/centos.

> We already do this for some
>ports, in that the people involved in adapting and maintaining some of the
>larger/more critical parts, such as X.org, KDE, Gnome, and quite a few others,
>spend vast amounts of time ensuring that things work well, but largely without
>the help of revision control in the ports tree.  I'm not proposing we
>incorporate X.org into CVS (SVN?) or the like, but perhaps there is a way we
>could better present the choices reflected there.  That doesn't help users of
>random tiny software packages, and I'm not sure anything can, but perhaps we
>can provide a smoother incremental maintenance path for some key packages.

I think that most system administrators who maintain many FreeBSD servers in
data center environments do not really care about "X.org, KDE, Gnome" and
other desktop applications having those -SECURITY patches backported.
The real concern here is about common server applications. I think that
cutting edge users who run FreeBSD on their workstations are perfectly
aware that things can sometimes break, and to a degree they accept that
risk. But system administrators running mission critical nonstop systems 24/7
cannot accept such risk with the server ports they are using. So if anything
can be improved in ease of upgrading, backporting etc. this is the main
area to investigate, so as to make FreeBSD the most stable and reliable
Unix operating system out there.

-- 
Andy Kosela
ora et labora
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

tracking -stable in the enterprise

[Andy Kosela]

On Jun 25, 2008, at 3:46 AM, Peter Wemm wrote:
>I think we still have FreeBSD-3.x machines in production. I know we
>have FreeBSD-4.3.  99.9% of security issues don't affect us.  We have
>our own package system built on top of FreeBSD's pkg_add format and
>have the ability to push packages to machines.  If circumstances
>warrant it, we can push a fix for something.  It'll either push a new
>binary or be a source patch that is compiled directly on the machines
>in question.   The machines run a custom software stack.  More often
>we push fixes for driver or performance fixes or things like timezone
>updates.

Ports infrastructure do not support such old FreeBSD versions, so how
do you deal with that? Do you maintain your own CVS branches of
selected packages and backports necessary security patches? I guess it
demands considerable effort to compile the latest apache on FreeBSD
3.x or 4.x.

-- 
Andy Kosela
ora et labora
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

PPP doesn't set the correct interface in 7-STABLE

[Andy Dills]

I'm trying to setup pptpd to enable VPN connections. This worked well in 
all versions of FreeBSD prior to 7.

Now, however, the interface in the routing table is incorrectly set to 
that of the ethernet card, rather than the appropriate tun interface.

There is a months-old bug report detailing this:

http://www.freebsd.org/cgi/query-pr.cgi?pr=122068&cat=

He mentions two workarounds:

there are two way to fix it.
1. use differenet subnet for vpn. Don't use the same subnet for vpn 
routing. user-ppp will set the correct routing table.
2. downgrade to FreeBSD 6.2

#2 isn't really an option, and #1 isn't clear to me. I tried a couple of 
different configurations and the interface never seems to get set 
correctly.


Suggestions?

Thanks,
Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Deprecating base system ftpd?

[Andy Farkas]

I think this is an excellent start. My shopping list includes:

- remove ftp(1)
- remove ftpd(8)
- remove telnet(1)
- remove telnetd(8)
- remove ftp:// and http:// from libfetch. This is 2021 and we should all
use https://.
- replace DNS lookups with DoH and/or DoT. Why let your ISP see your DNS
traffic?



I wonder how many people use YP/NIS (man 8 yp)?


It's a nifty concept; I played around with it last century...

I believe there is still an open PR in bugzilla I created (can't find it

right now, used a diffent email address back then, although same

username).


Removing it from base (if it should be done at all) looks very complicated

and therefore creating a port equally so.


I know this topic (removing ftpd) is closed, so perhaps this should be

a new one (removing YP/NIS)?  ie. no development on yp has been

done for over a decade.


My view: remove neither


-andyf


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

SVN seeds [was: FreeBSD 9.1-RC1 Available...]

[Andy Farkas]

On 24/08/12 08:14, Peter Wemm wrote:

Back when I did the first mirror for making a seed, ...


If you have a complete CVS mirror repo (I'm using cvsup-mirror from ports),
can you make your own seeds using cvs2svn to create local read-only SVN
repos, then begin using svnsync from the master/mirror SVN servers?

I'm looking to avoid downloading what I believe will be large seed files.

I guess you'd need to convert src, ports, docs, www as different SVN repos?

Are there any docs on how it was done for FreeBSD?

-andyf

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

FreeBSD history

[Andy Farkas]

On 16/06/13 20:30, Jeremy Chadwick wrote:
> * Output from: strings /boot/kernel/kernel | egrep ^option Thanks.

I stumbled across this one about a week ago:

 strings /boot/kernel/kernel | head -1

and was wondering about the history of where it came from / what it means.

I can see it was added to Makefile.i386 in September 1998 but the commit 
comment mentions the defunct alpha port and searching SVN for things in 
the Attic is a PITA.


Also, according to 
http://svnweb.freebsd.org/base?view=revision&revision=1 FreeBSD is 20 
years old!


Is not a celebration / announcement warranted?

-andyf

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

Re: Why are cardbus drivers cbb(4) and pccard(4) still included in GENERIC?

[Andy Farkas]

There's still plenty of laptops that would be crippled if these were removed.



Indeed:

dc0:  port 0x1000-0x10ff mem 
0x8800-0x880003ff irq 11 at device 0.0 on cardbus1


-andyf

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

Re: Rescuing a GPT ZFS boot setup

[Andy Moran]

On Sep 19, 2013, at 6:58 AM, Volodymyr Kostyrko  wrote:

> 19.09.2013 16:43, Andrew Moran wrote:
>> Alas, that did not work. But it does look to be BIOS related.
>> 
>> I think this new system has a UEFI bios.
>> 
>> I just read from https://wiki.freebsd.org/UEFI:
>>  * Partitions not seen. When using GPT, FreeBSD will create a protective 
>> MBR. This MBR has one partition entry covering the whole disk. FreeBSD marks 
>> this partition active. This causes at least some UEFI implementations to 
>> ignore the GPT. To fix this the partition needs to be marked inactive.
>>  * Filesystem not seen. FreeBSD's FAT32 code appears to sometimes create 
>> filesystems that the UEFI code can't properly read. If the filesystem is 
>> small enough, use FAT16 or FAT12 instead.
>> 
>> I think this may be my issue.  But 9.1 LiveCD does boot and I can see the 
>> data once booted, so there must be a way to fix the boot loader on the drive 
>> to work.
> 
> Good catch. The fix landed in stable not so long ago 
> (http://svnweb.freebsd.org/base?view=revision&revision=255017) so you 
> wouldn't find it in 9.2 either. Can you try this:
> 
>   gpart unset -a active ada0


It says 'active' is an invalid attribute.  This matches what gpart mangpage 
says under ATTRIBUTES .. it doesn't list 'active' as an attribute for the GPT 
partition scheme (but it does for other schemes).I did try to unset 
'bootme' but that did not help either.  

Do I need the newer version of gpart to be able to unset or set it?



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

Re: Rescuing a GPT ZFS boot setup

[Andy Moran]

On Sep 19, 2013, at 9:28 AM, John-Mark Gurney  wrote:

> Andy Moran wrote this message on Thu, Sep 19, 2013 at 08:12 -0700:
>> 
>> On Sep 19, 2013, at 6:58 AM, Volodymyr Kostyrko  wrote:
>> 
>>> 19.09.2013 16:43, Andrew Moran wrote:
>>>> Alas, that did not work. But it does look to be BIOS related.
>>>> 
>>>> I think this new system has a UEFI bios.
>>>> 
>>>> I just read from https://wiki.freebsd.org/UEFI:
>>>>* Partitions not seen. When using GPT, FreeBSD will create a protective 
>>>> MBR. This MBR has one partition entry covering the whole disk. FreeBSD 
>>>> marks this partition active. This causes at least some UEFI 
>>>> implementations to ignore the GPT. To fix this the partition needs to be 
>>>> marked inactive.
>>>>* Filesystem not seen. FreeBSD's FAT32 code appears to sometimes create 
>>>> filesystems that the UEFI code can't properly read. If the filesystem is 
>>>> small enough, use FAT16 or FAT12 instead.
>>>> 
>>>> I think this may be my issue.  But 9.1 LiveCD does boot and I can see the 
>>>> data once booted, so there must be a way to fix the boot loader on the 
>>>> drive to work.
>>> 
>>> Good catch. The fix landed in stable not so long ago 
>>> (http://svnweb.freebsd.org/base?view=revision&revision=255017) so you 
>>> wouldn't find it in 9.2 either. Can you try this:
>>> 
>>> gpart unset -a active ada0
>> 
>> 
>> It says 'active' is an invalid attribute.  This matches what gpart mangpage 
>> says under ATTRIBUTES .. it doesn't list 'active' as an attribute for the 
>> GPT partition scheme (but it does for other schemes).I did try to unset 
>> 'bootme' but that did not help either.  
>> 
>> Do I need the newer version of gpart to be able to unset or set it?
> 
> You could try the new 10-ALPHA1 LiveCD to unset it..
> 
> -- 

WIth the 10-ALPHA2 LiveCD, I get:

gpart: attrib 'active': Device not configured

I can set/unset the bootme attribute and I can do:  gpart bootcode -b 
/boot/pmbr -p /boot/gptzfsboot -i ada0 
But neither seems to get me out of my jam -- the UEFI doesn't seem to see it as 
a bootable disk.

:(

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

Re: Rescuing a GPT ZFS boot setup

[Andy Moran]

Another thought:  since the LiveCDs can see my ZFS root pool, would it be 
possible to create a CD or memstick image just for the boot loader that then 
boots the OS of the hard drive?  

--Andy


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

Re: Rescuing a GPT ZFS boot setup

[Andy Moran]

On Sep 19, 2013, at 8:16 PM, "Andrey V. Elsukov"  wrote:

> On 20.09.2013 06:34, Andy Moran wrote:
>> WIth the 10-ALPHA2 LiveCD, I get:
>> 
>> gpart: attrib 'active': Device not configured
>> 
> 
> GPT partitions don't have active attribute. You should omit -i argument.
> Just run `gpart unset -a active ada0`.
> 
> -- 
> WBR, Andrey V. Elsukov
> 
> -- 
> WBR, Andrey V. Elsukov


That ran without errors.. but sadly did not solve my problem of the UEFI not 
recognizing it as a bootable disk. I think the problem is my particular 
UEFI doesn't recognize GPT drives that don't have an EFI partition on them. 

So I gave up.  My server has been down for too long.   I took half the zfs 
mirror, created it with a MBR partition and installed FreeBSD 9.2 on it, and my 
UEFI can boot it in legacy mode.   From there I can mount the other half of the 
mirror and copy files off.   A painful process but at least I have a way 
forward.   

Thanks for the suggestions.  

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

vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]

[Andy Farkas]

On 2020-03-09 04:15, bugzilla-nore...@freebsd.org wrote:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235564

--- Comment #8 from commit-h...@freebsd.org ---
A commit references this bug:

Author: emaste
Date: Sun Mar  8 18:14:45 UTC 2020
New revision: 358758
URL: https://svnweb.freebsd.org/changeset/base/358758

Log:
   MFC r355585: remove nonexistent from-* entries from vt INDEX.keymaps



Is anyone actually working on the vt(4) driver?  Will it ever

become feature-parity with the old sc(4) driver?


I've noticed some weird things happening on my console recently...

like psychedelicly-colour-coded kernel messages.. far out, man.


Just wondering,


-andyf


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

Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]

[Andy Farkas]

On 2020-03-10 01:04, Konstantin Belousov wrote:

Take a look at r334530.



"or the user really hates this feature and can't wait to turn it off"



Excellently explained by Bruce as usual:


"Revision 314641 - (view) (download) (annotate) - [select for diffs]
Modified Sat Mar 4 06:19:12 2017 UTC (3 years ago) by bde
File length: 107771 byte(s)
Diff to previous 312910
Colorize syscons kernel console output according to a table indexed
by the CPU number.

This was originally for debugging near-deadlock conditions where
multiple CPUs either deadlock or scramble each other's output trying
to report the problem, but I found it interesting and sometimes
useful for ordinary kernel messages.  Ordinary kernel messages
shouldn't be interleaved, but if they are then the colorization
makes them readable even if the interleaving is for every character
(provided the CPU printing each message doesn't change).

The default colors are 8-15 starting at 15 (bright white on black)
for CPU 0 and repeating every 8 CPUs.  This works best with 8 CPUs.
Non-bright colors and nonzero background colors need special
configuration to avoid unreadable and ugly combinations so are not
configured by default.  The next bright color after 15 is 8 (bright
black = dark gray) is not very readable but is the only other color
used with 2 CPUs.  After that the next bright color is 9 (bright
blue) which is not much brighter than bright black, but is used with
3+ CPUs.  Other bright colors are brighter.

Colorization is configured by default so that it gets tested.  It can
only be turned off by configuring SC_KERNEL_CONS_ATTR to anything other
than FG_WHITE.  After booting, all colors can be changed using the
syscons.kattr sysctl.  This is a SYSCTL_OPAQUE, and no utility is
provided to change it (sysctl only displays it).

The default colors work in all VGA modes that I could test.  In 2-color
graphics modes, all 8 bright colors are displayed as bright white, so
the colorization has no effect, but anything with a nonzero background
gives white on white unless the foreground is zero.  I don't have an
mono or VGA grayscale hardware to test on.  Support for mono mode seems
to have never worked right in syscons (I think bright white gives white
underline with either bold or bright), but VGA grayscale should work
better than 2-color graphics."



RIP


https://photos.app.goo.gl/YiVmFtWiK8Niy3Fw6


-andyf


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

Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]

[Andy Farkas]

On 2020-03-11 02:19, Ed Maste wrote:

So to confirm, your issue is with sc(4), not vt(4)? 



I don't actually have an issue with either. although:


"After booting, all colors can be changed using the
syscons.kattr sysctl."


% sysctl -a | grep syscons
hw.syscons.sc_no_suspend_vtswitch: 0
hw.syscons.kbd_debug: 1
hw.syscons.kbd_reboot: 1
hw.syscons.bell: 1
hw.syscons.saver.keybonly: 0

%


Also, both sc and vt are compiled into GENERIC.

Is it just a matter of putting "syscons=[sc|vt]" in loader.conf

to select whatever driver?


FreeBSD drunkfish.andyit.com.au 12.1-STABLE FreeBSD 12.1-STABLE #1 
r358253: Sun Feb 23 15:02:00 AEST 2020



-andyf


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

assfail

[Andy Farkas]

My normally very reliable PC now panics in 'assfail+0x1d'


Any idea why (or what!) this is?


Imge of panic screen: https://imgur.com/1vRpkgW


-andyf


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

Re: assfail

[Andy Farkas]

On 1/09/2020 12:38 pm, Eugene Grosbein wrote:

You should describe your system: OS version and disk/file system setup, 



It says it right there: FBSD 10.3-RELEASE-p6

Boots from a Samsung SSD 840EVO.



because the screenshot shows ZFS-related assertion failure after GELI 
initialization,
so your setup seems to be non-trivial.



Setup is bog-standard. In what way could it be otherwise?



Perhaps, your system experienced unclean reboot before this problem?
Maybe you'll need to use "zpool import -F" or even
"zpool import -F -X" for "extreem rewind" (-X is not documented).



Pretty sure no unclean reboots.. although as I said, it's been giving me 
problems lately,


Will try 'zpool import -F'


Will let you know...


-andyf


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

Re: assfail

[Andy Farkas]

On 1/09/2020 3:37 pm, Kurt Jaeger wrote:


Can you check smart values ?
smartctl -a /dev/ada0



No. Kernel does not boot so cannot get a sh prompt.


Just still wondering what 'assfail' could be.


Use the source, Luke!


-andyf


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

Re: assfail

[Andy Farkas]

On 1/09/2020 6:25 pm, Jamie Landeg-Jones wrote:

Don't google it!! 



Luckily I only use DuckDuckGo


-andyf


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

Re: [OT] Which one is best MTA for me?

[Andy Greenwood]

Patrick M. Hausen wrote:

Hi!

  

Recently I am considering to move to another MTA. At one time I was
wondering what mail server big ISP are running. I can't decide postfix
or qmail. 


Which one is best MTA for me?



Sendmail? It's the best MTA for me ;-)

Maybe your question could be answered in a more helpful way,
if you stated

- which MTA you are currently using
- what you don't like about it, so you want to switch
  


I agree. we can't determine what's best for you unless you tell us what 
you're lacking. the way you phrased your question, you'll just get a 
list of what other people like, which may or may not be well suited for 
your application.

We are an ISP and we run Sendmail. Works great. I don't like
qmail, because for me it's architecture is even more arcane
than Sendmail's. And it doesn't log all information Sendmail
does - which is important for us when tracing "lost" mails.
(remote MTA queue ID, for example)
  


I work at an ISP and we use sendmail here as well. I use postfix at 
home. Both work quite well.

I hear lots of good things about postfix, but switch for
the sake of switching? I already have enough work ;-)

Kind regards,
Patrick M. Hausen
Leiter Netzwerke und Sicherheit
  


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Poll: FreeBSD userbase in 2016

[Andy Farkas]

On 27/02/2016 13:09, Lucius Rizzo wrote:

I am wondering who else (these days) uses FreeBSD commercially and/or any major 
names to understand current userbase. Is there any data on this?



The FreeBSD web site (https://www.freebsd.org/) has a link on
the home page:

"... the platform of choice for many of the busiest web sites ..."

Try clicking on it.

-andyf

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

Re: Jenkins build is still unstable: FreeBSD_stable_10 #208

[Andy Farkas]

On 11/04/2016 06:28, jenkins-ad...@freebsd.org wrote:

See 




Anybody?

-andyf

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

Reproducible panic - Going nowhere without my init!

[Andy Farkas]

Is it just me or

Step 1: boot
Step 2: login as root
Step 3: type "w" *
Step 4: type "shutdown now; logout"
Step 5: press  at the 'Enter full pathname of shell or RETURN for
/bin/sh:' prompt
Step 6: type "reboot"
Step 7: get a Panic: "Going nowhere without my init!"

* The panic will not happen if you skip step 3.

The panic will not happen if you type "sync; sync; sync" after step 5.

The panic will not happen if you wait (an unknown amount of) some time
after step 5.

# uname -a
FreeBSD deepthink 11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #6 r306656: Tue
Oct  4 09:03:05 AEST 2016 root@deepthink:/usr/obj/usr/src/sys/GENERIC  amd64

-andyf

ps. apologies, forced to send from a gmail account.
reply-to: an...@andyit.com.au
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Reproducible panic - Going nowhere without my init!

[Andy Farkas]

On 05/10/2016 18:43, Konstantin Belousov wrote:

> Apply the following patch.  I am interested if anything additional appear
> on the console.  Screenshot is good enough.

Patch applied. Panic (easlily!) reproduced. No additional output.

Screenshot:  http://imgur.com/KOOBysH

I guess init is dying before it gets there.

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

Re: Reproducible panic - Going nowhere without my init!

[Andy Farkas]

On 05/10/2016 23:36, Konstantin Belousov wrote:

> Please try this variation, I want to see if the error code changed.

Afraid not. Still signal 0, exit 0.

Screenshot:  http://imgur.com/AU6weU0

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

Re: Reproducible panic - Going nowhere without my init!

[Andy Farkas]

Reverted your patch then changed line 1011 of init.c to _exit(97):

--- init.c-orig 2016-10-05 18:52:24.02291 +1000
+++ init.c 2016-10-06 17:02:33.714624000 +1000
@@ -1008,7 +1008,7 @@
  */
  warning("single user shell terminated.");
  sleep(STALL_TIMEOUT);
- _exit(0);
+ _exit(97);
  } else {
  warning("single user shell terminated, restarting");
  return (state_func_t) single_user;

...and got a panic that showed "exit 97":  http://imgur.com/xonPwxR

I think that kern_reboot() is not being called somehow.
kern_reboot() is the only place rebooting = 1; is executed.

"init died (signal 0, exit 97)
panic: Going nowhere without my init!"

can only happen if rebooting = 0 in kern_exit.c exit1().

Another tell that kern_reboot() has not been called is "cpuid = 3"
because the first thing kern_reboot() does is bind to CPU 0.

Why is kern_reboot() being skipped? I have no idea.

Anything more I can do to help?  Do you want a core dump?

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

Re: Reproducible panic - Going nowhere without my init!

[Andy Farkas]

With your latest patch applied, I ran through my procedure more
than a dozen times and no panics!

Any explanation why sleep(STALL_TIMEOUT) as apposed to a
bunch of sleep(1)'s tickles the panic?

Also, it is definitely not sleeping for 30 seconds. I guess some
event interrupts the sleep loop?

Thanks heaps for your time and effort,

-andyf

%%%
Please try the following patch.

diff --git a/sbin/init/init.c b/sbin/init/init.c
index bda86b5..25ac2bd 100644
--- a/sbin/init/init.c
+++ b/sbin/init/init.c
@@ -870,6 +870,7 @@ single_user(void)
  sigset_t mask;
  const char *shell;
  char *argv[2];
+ struct timeval tv, tn;
 #ifdef SECURE
  struct ttyent *typ;
  struct passwd *pp;
@@ -884,8 +885,13 @@ single_user(void)
  if (Reboot) {
  /* Instead of going single user, let's reboot the machine */
  sync();
- reboot(howto);
- _exit(0);
+ if (reboot(howto) == -1) {
+ emergency("reboot(%#x) failed, %s", howto,
+strerror(errno));
+ _exit(1); /* panic and reboot */
+ }
+ warning("reboot(%#x) returned", howto);
+ _exit(0); /* panic as well */
  }

  shell = get_shell();
@@ -1002,7 +1008,14 @@ single_user(void)
  *  reboot(8) killed shell?
  */
  warning("single user shell terminated.");
- sleep(STALL_TIMEOUT);
+ gettimeofday(&tv, NULL);
+ tn = tv;
+ tv.tv_sec += STALL_TIMEOUT;
+ while (tv.tv_sec > tn.tv_sec || (tv.tv_sec ==
+tn.tv_sec && tv.tv_usec > tn.tv_usec)) {
+ sleep(1);
+ gettimeofday(&tn, NULL);
+ }
  _exit(0);
  } else {
  warning("single user shell terminated, restarting");
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: my build time impact of clang 5.0

[Andy Farkas]

On 03/10/2017 06:18, Dan Mack wrote:


My scripts are pretty coarse grained so I only have timings at the macro
build steps so far (buildworld, buildkernel, installkernel, and
installworld)  I'm going to update them so I can a little more
granularity; should be easy to get timings wrapped around the big
sections, for example:

  >>> World build started on Mon Oct  2 07:49:56 CDT 2017
  >>> Rebuilding the temporary build tree
  >>> stage 1.1: legacy release compatibility shims
  >>> stage 1.2: bootstrap tools
  >>> stage 2.1: cleaning up the object tree
  >>> stage 2.2: rebuilding the object tree
  >>> stage 2.3: build tools
  >>> stage 3: cross tools
  >>> stage 3.1: recording compiler metadata
  >>> stage 4.1: building includes
  >>> stage 4.2: building libraries
  >>> stage 4.3: building everything
  >>> stage 5.1: building lib32 shim libraries
  >>> World build completed on Mon Oct  2 12:30:02 CDT 2017

Dan



Perhaps you could hack src/tools/tools/whereintheworld/whereintheworld.pl

-andyf

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

Re: upgrading from 10.0 to 10.3 problem

[Andy Firman]

On Tue, Aug 23, 2016 at 1:47 PM, Peter Lai  wrote:

> > Hello. I tried to upgrade from 10.0-RELEASE: # freebsd-update -r
> 10.3-RELEASE upgrade
> > ...
> > # freebsd-update install
> > ...
> > # reboot
> > ...
> > # freebsd-update install
> > Installing updates...Segmentation fault (core dumped)
> > Segmentation fault (core dumped)
> > Segmentation fault (core dumped)
> > Segmentation fault (core dumped)
> > Segmentation fault (core dumped)
> > Segmentation fault (core dumped)
> > Segmentation fault (core dumped)
> > Segmentation fault (core dumped) Now I have:
> > # freebsd-version -ku
> > 10.3-RELEASE-p4
> > 10.0-RELEASE It's not looking good. How to fix? PS. In /var/log/messages
> I see "(gunzip), uid 0: exited on signal 11"
> > And yes:
> > # gunzip
> > Segmentation fault (core dumped)
>
> Hi Sergey:
>
> I ran into this problem the week before you did:
> https://lists.freebsd.org/pipermail/freebsd-stable/2016-July/085115.html
> Because just about all of the binaries were trashed (including /lib,
> /[s]bin, /usr/lib, /usr/[s]bin files were truncated to 0), I had to
> /rescue/nc > base.txz (where I fetched base.txz from the ftp site in
> the 10.3-RELEASE distribution), then /rescue/tar -zxvf base.txz into a
> directory, then tar | tar each of /lib and so on to get my binaries
> back (apparently /rescue does not have a statically compiled cpio).
>
> After sending the above to the mailing list I went ahead and replaced
> the kernel that the broken freebsd-update install installed with the
> one from 10.3-RELEASE (from the distribution base.txz:boot/kernel),
> which made the system entirely binary 10.3-RELEASE then I was able to
> freebsd-update to FreeBSD-10.3-RELEASE-p6 with no problems. Note that
> the initial freebsd-update from 10.0 also severely trashed my /etc, I
> had to restore master.passwd and friends! (many of /etc files were
> also truncated to 0), even though the merge process seemed to complete
> ok before the broken freebsd-update install.
> ___
>
>

I just experienced the same thing. Sent this to freebsd-questions last
night, no response yet, so thought I would also try here on this thread.
Here is my disaster from last night:


*Following this guide:*

https://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html


# uname -a

FreeBSD 10.0-RELEASE-p9 FreeBSD 10.0-RELEASE-p9 #0: Mon Sep 15 14:35:52 UTC
2014 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64

*Run this command:*

# freebsd-update -r 10.4-RELEASE upgrade

# freebsd-update install

reboot


*Success...system came back up as 10.4*

# uname -a
FreeBSD 10.4-RELEASE-p3 FreeBSD 10.4-RELEASE-p3 #0: Tue Nov 14 09:43:55 UTC
2017 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64

*Run this command one more time per the guide above:*

# freebsd-update install
Installing updates...Segmentation fault (core dumped)
Segmentation fault (core dumped)
Segmentation fault (core dumped)
Segmentation fault (core dumped)
Segmentation fault (core dumped)


*System is totally down and had to recover from snaphot*


*What on earth happened here?*
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Writing application

[Andy Greenwood]

cd /usr/ports/www/apache13 && make install clean

should install apache and all it's dependancies for you. As for
writing your applications, I can't even begin to help without more
info. Perhaps you should search for information on your programming
language of choice. You can write your application in any folder you
want, but a likely place might be either your home directory or a
subdirectory of your apache's document root (depending on the
application's...uh...application) which defaults to
/usr/local/www/data-dist/

On 7/10/06, Mihir Sanghavi <[EMAIL PROTECTED]> wrote:

Hi,
 I have installed freeBSD 5.5 and am connected to the net now. I would like
to install apache and devlop some application from there. How should i start
writing my application, execute it. I even make to figure out what folder to
write application and how to deal with it. Thank you

--
What we see depends mainly on what we look for.
-MIHIR
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

device carp / freebsd-update

[Andy Hilker]

Hi,

we are currently migrating our hosts to 6.1-RELEASE with official
binaries (from CD). This is because we want to make use of
freebsd-update binary patches.

Our problem is that GENERIC kernel does not contain "device carp".
Is there any posibility to use carp without "device carp" in GENERIC
e.g. with /boot/loader.conf like other pseudo devices?

Any idea?

bye,
Andy

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: device carp / freebsd-update

[Andy Hilker]

Hi Max,

You (Max Laier) wrote:
> On Monday 21 August 2006 15:53, Andy Hilker wrote:
> > we are currently migrating our hosts to 6.1-RELEASE with official
> > binaries (from CD). This is because we want to make use of
> > freebsd-update binary patches.
> >
> > Our problem is that GENERIC kernel does not contain "device carp".
> > Is there any posibility to use carp without "device carp" in GENERIC
> > e.g. with /boot/loader.conf like other pseudo devices?
> 
> No, there is no such possibility.  The reason for this, is that carp(4) 
> has to register a protocol which cannot be (easily) done on-the-fly.  
> Since you should have a fail-over running it shouldn't be a problem to 
> build a carp enabled backup while the failover host takes care of the 
> service, however.

The problem is: we have to use a custom kernel, but currently we
try to use freebsd-update, which is not useable with custom kernels.


> As a fallback there is a userland implementaion of carp (google "ucarp"), 
> but I am not sure what the status of that is or if it works with the 
> in-kernel version.

We tested it already. It seems to work fine with 2 ucarp nodes, but
fyi ucarp and kernel carp does not work together (i did not found
out why). So we will test the ucarp more deeply and maybe switch
our carp system to ucarp :(

Maybe in future we can try to built our own binary diffs for
freebsd-update. Then we can make use of custom compiled worlds+kernels.
But this needs a "freebsd-update-built-server" and more custom work
on our side.

bye,
Andy



pgpMgFeIlrwvi.pgp
Description: PGP signature

Re: device carp / freebsd-update

[Andy Hilker]

You (Gavin Atkinson) wrote:
[...]
> I don't suppose there's any chance you know if ucarp works with
> 6.1-RELEASE and IPv6?  This is the one thing stopping me moving my
> machines to 6.1-RELEASE.
> 
> If you don't know, then you've given me yet another thing to add to my
> todo list!

No, sorry, I have not tested it. But maybe the kernel carp?

bye,
Andy

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

misc/amanda-server: amfetchdump segmentation fault

[Andy Hilker]

Hi,
 
Since 2.5.1p1,1 the amfetchdump utility does not work anymore:

-- snap --
$ amfetchdump -a -c CONFIG HOST da0s1e 20061108 1
Scanning /home/amanda/hold...
1 tape(s) needed for restoration
sh: segmentation fault (core dumped)  amfetchdump -a -c CONFIG HOST da0s1e 
20061108 1  
-- snap --

With strings on the .core file I have found:
Shared object "nss_dns.so.1" not found, required by "amfetchdump"
This "nss_dns.so.1" seems to be related to FreeBSD specific patches
which other ports needed in the past... (google result). But I am
not sure if this is the reason for the segmentation fault.

Is there anybody out where amfetchdump works in 2.5.1p1,1? 
Or any other idea? I can supply more information as needed.

Regards,
Andy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Portupgrade script.

[Andy Smith]

On Tue, Nov 09, 2004 at 10:39:02AM +, Yann Golanski wrote:
> Would people be kind enough to have a look at the following script and
> tell me what horrors/faux pas/stupid things I have done?  
> 
> The script is an almost automated way to upgrade all your ports to the
> latest version. 

Without looking further I'd say this is a bad idea because sometimes
an upgrade to a port radically changes its functionality or does
something else inconvenient.  For example, upgrading
databases/mysql*-server will shut down a running mysql server.

You need to be manually reading /usr/ports/UPDATING before each
update.

What I tend to do is automate the cvsup and then email a report of
what could be upgraded.  The actual upgrades are done
semi-automatically with a portupgrade -arR after checking it isn't
going to do anything untoward.


pgpfi57nXivU5.pgp
Description: PGP signature

Re: FreeBSD mysql and threading

[Andy Smith]

On Sun, Dec 05, 2004 at 10:44:15AM -0700, Scott Long wrote:
> The good news is that default option of using KSE (i.e.
> libpthread) system scope threads performs about as well as
> Linuxthreads, on an SMP system.

On a single processor 5.x system, is it still advised to use
linuxthreads with the MySQL 4.1.x port?


pgpUzTY0R0o98.pgp
Description: PGP signature

Re: Qt33 Build Problem

[Andy Fawcett]

On Monday 17 January 2005 22:23, Tom Huppi wrote:
> I worked at re-building Qt33 for quite some time, but
> 'libqt-mt.so' still retains a reference to 'libc_r'.  If there are
> any common reasons why this may be, I'de be interested to know of
> them.

Make sure you rebuild devel/qmake before building qt

This is because it is the config defined by qmake 
(actually /usr/local/share/qt/mkspecs/freebsd-g++/qmake.conf) that defines 
what thread library to use in building qt.

A.
-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Can't kldload pf

[Andy Firman]

On Fri, Mar 11, 2005 at 09:34:00AM +1030, Daniel O'Connor wrote:
> On Fri, 11 Mar 2005 08:33, [EMAIL PROTECTED] wrote:
> > On Thu, Mar 10, 2005 at 07:13:51PM +0100, Max Laier wrote:
> > > On Thursday 10 March 2005 18:52, [EMAIL PROTECTED] wrote:
> > > > on RELENG_5, cvsupped March 9th, I can't kldload pf:
> > > >
> > > > fw# kldload pf
> > > > kldload: can't load pf: No such file or directory
> > >
> > > You don't have "options INET6" in your kernel config, but the pf module
> > > assumes that it is there.  You can either built pf into the kernel (since
> > > you are building a custom kernel anyway), rebuild the module without that
> > > assumption (see the module's Makefile) or you can reenable "options
> > > INET6" in the kernel.
> >
> > Yes, INET6 is needed indeed. That was the catch! Adding "options INET6"
> > solved the problem.
> >
> > > The ENOENT error returned from kldload is a bit misleading, though.
> >
> > Ugh... yes ;). Perhaps that should be documented in pf(4)?
> 
> It's not pf per se..
> If you ran dmesg after your kldload attempts you'd see the kernel linker 
> complaining about being unable to resolve some IPv6 related symbols.
> 
> Other possibility is to do..
> cd /usr/src/sys/modules/pf
> make NO_INET6= install
> 
> and load it again.



H...interesting!!Would this for for /usr/src/sys/modules/ipfilter ?

I am having this problem:
http://www.freebsd.org/cgi/query-pr.cgi?pr=70401

That seems almost too easy.  :-)

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Can't kldload pf

[Andy Firman]

On Tue, Mar 15, 2005 at 10:54:44AM +1030, Daniel O'Connor wrote:
> On Tue, 15 Mar 2005 07:46, Andy Firman wrote:
> > H...interesting!!Would this for for /usr/src/sys/modules/ipfilter ?
> >
> > I am having this problem:
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=70401
> 
> Yes, that module makefile honours the NO_INET6 flag too.
> You might want to put it in /etc/make.conf.

That works.  I was able to build and load the module with no reboot.
So for the OP, this should apply to you with pf instead of ipfilter.
Here are some notes from doing this on my test system:

-
Found a solution to my problem.  One must add an entry to /etc/make.conf
and then you can rebuild the module, load it, and get the firewall going
with no reboot.  Below is a summary of doing this with my TEST kernel
having the INET6 option commented out.

su-3.00# kldload -v ipl
kldload: can't load ipl.ko: No such file or directory

su-3.00# uname -a
FreeBSD localhost 5.3-STABLE FreeBSD 5.3-STABLE #0: Mon Mar 14 16:08:45 EST 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST  i386

must add NOINET6=YES to /etc/make.conf before you make the new module.

su-3.00# cd /usr/src/sys/modules/ipfilter/

su-3.00# make

su-3.00# make install

su-3.00# kldload -v ipl

Nothing returned to therefore loaded properly...!

su-3.00# kldstat
Id Refs AddressSize Name
 16 0xc040 59f308   kernel
 21 0xc15fb000 17000linux.ko
 31 0xc167 16000ipl.ko

su-3.00# ipfstat -in
empty list for ipfilter(in)

su-3.00# ipfstat -on
empty list for ipfilter(out)

su-3.00# ipf -Fa -f /etc/ipf.rules

This locks up your session. Must login again and start new session.
Success upon new login in which the rules are working!!!

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Qt applications hang

[Andy Fawcett]

On Sunday 20 March 2005 09:26, Francois Tigeot wrote:
> On Sat, Mar 19, 2005 at 05:47:01PM -0800, David Wolfskill wrote:
> > There's a recent entry in /usr/ports/UPDATING that may be relevant.
>
> Thanks, but I fail to see what is relevant in this case.
>
> I suspected at one time the system compiler to be busted, but I recompiled
> everything with -O -pipe and the problem remains.
>
> Cc to -amd64 to see if there may be something architecture specific.
>
> [For the record, every QT application hang immediately when some menu
> options are selected. The system is 5.4-PRERELEASE/amd64]

I have 5.4-PRE on my work amd64 box (kernel/world built a few days ago) and 
I'm running KDE from ports in it without apparent problems.

A.
-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Possibility for FreeBSD 4.11 Extended Support

[Andy Dills]

On Fri, 29 Dec 2006, Wilko Bulte wrote:

> On Fri, Dec 29, 2006 at 08:45:03AM +0800, lveax wrote..
> > seems there are many machines at freebsd.org network are still using
> > 4-STABLE now.
> 
> There is a mix of versions in use, upgrading is done at the discretion
> of the admins team that controls the FreeBSD.org server farm.  That in
> turn is dependent on the amount of time admins have available etc etc.
> 
> So what is the problem?

Indeed...I still run and admin a large number of 4-STABLE servers, and 
even as I'm currently in the process of deploying 6-STABLE on my own 
servers, I still regularly deploy 4-STABLE for customers of mine.

There's a lot to be said for the "why fix what isn't broken" train of 
thought. I bet there are still a decent number of 2.2.8 boxes floating 
around...perhaps there's even more to be said for version maturity in 
general. 

I was hoping to wait for 6.4-R before jumping to the 6 line, but 6.2 is 
looking pretty solid for my purposes, so it seems like a great time to 
start migrating. I'm curious if anybody else is planning to migrate a 
large number of 4-STABLE boxes to 6-STABLE as of 6.2-R.  

Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: install on usb hdd

[Andy Greenwood]

On 2/10/07, Zoran Kolic <[EMAIL PROTECTED]> wrote:

Howdy!
I tried to install 6.2 amd64 on external usb hdd, but with no result.
It is 2.5 WD and enclosure with two usb connectors for power. The box
is not visible from bios at all, even when I use powered usb hub. Is
it possible to install on external device like this? Product is from
canyon. Should I buy another enclosure or look for internal 3.5 drive?
Note: neither bios nor installation cd see the external drive. What
could I do to have it working?


IIRC, you can only install to drives that the bios can see. You could
try finding a computer whose bios can see the drive and installing
from there. As long as you don't touch the internal drives on that
machine, everything *should* be safe. YMMV



 Zoran


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"




--
--
I'm nerdy in the extreme and whiter than sour cream
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: install on usb hdd

[Andy Greenwood]

On 2/12/07, Zoran Kolic <[EMAIL PROTECTED]> wrote:

Maybe stupid question, but should I, for any reason, partition usb
hdd first and then try to see it in bios and try to install on it?


I doubt that should be necessary. Have you checked to see if there are
any updates for your BIOS? If so, try installing those and seeing if
that will allow the BIOS to see the drive.


Never crossed my mind, but...
Looks obvious to me that this combination should work with no hitch.

   Zoran


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"




--
--
I'm nerdy in the extreme and whiter than sour cream
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Recent libxine update seems to cause ICE on 6-STABLE/amd64

[Andy Fawcett]

On Thursday, libxine was updated in the ports collection to version 1.1.4

Unfortunately, this seems to cause some kind of compiler-suite error on 
6.2-STABLE/amd64.

dsputil.c:3826: error: unrecognizable insn:
(insn 62 10 12 0 (set (reg:SI 0 ax [61])
(subreg:SI (plus:DI (subreg:DI (reg:SI 7 sp) 0)
(const_int -4 [0xfffc])) 0)) -1 (nil)
(nil))
dsputil.c:3826: internal compiler error: in extract_insn, at recog.c:2083
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
gmake[5]: *** [dsputil.lo] Error 1
gmake[5]: Leaving directory 
`/usr/ports/multimedia/libxine/work/xine-lib-1.1.4/src/libffmpeg/libavcodec'

Please see PR ports/109213 (raised by another person) for slightly more 
context to the error. It's bitten two of us so far, apparently in identical 
way.

I'm not sure this should be a ports PR, maybe it should go to the compiler 
suite?

Andy

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Recent libxine update seems to cause ICE on 6-STABLE/amd64

[Andy Fawcett]

On Sunday 18 February 2007 11:04, Jack L. wrote:
> It fails to compile with the gcc version that comes with FreeBSD 6 and
> 7, but it compiles fine on gcc 4.1 when I tried. It's probably a
> compiler bug that's been fixed on the 4.x series.

Yes, I agree it builds fine on 6.2/amd64 when gcc 4.1 is used. I guess a 
simple fix for the port would be to update the USE_GCC version to a value 
known to work (4.1 and 4.2 from ports are ok, no idea about 4.0).

Hopefully someone more familiar with the compiler suites would be able to fix 
the system compilers.

Andy


> On 2/17/07, Andy Fawcett <[EMAIL PROTECTED]> wrote:
> > On Thursday, libxine was updated in the ports collection to version 1.1.4
> >
> > Unfortunately, this seems to cause some kind of compiler-suite error on
> > 6.2-STABLE/amd64.
> >
> > dsputil.c:3826: error: unrecognizable insn:
> > (insn 62 10 12 0 (set (reg:SI 0 ax [61])
> > (subreg:SI (plus:DI (subreg:DI (reg:SI 7 sp) 0)
> > (const_int -4 [0xfffc])) 0)) -1 (nil)
> > (nil))
> > dsputil.c:3826: internal compiler error: in extract_insn, at recog.c:2083
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See http://gcc.gnu.org/bugs.html> for instructions.
> > gmake[5]: *** [dsputil.lo] Error 1
> > gmake[5]: Leaving directory
> > `/usr/ports/multimedia/libxine/work/xine-lib-1.1.4/src/libffmpeg/libavcod
> >ec'
> >
> > Please see PR ports/109213 (raised by another person) for slightly more
> > context to the error. It's bitten two of us so far, apparently in
> > identical way.
> >
> > I'm not sure this should be a ports PR, maybe it should go to the
> > compiler suite?
> >
> > Andy
> >
> > --
> > Andy Fawcett | [EMAIL PROTECTED]
> >
> >  | [EMAIL PROTECTED]
> >
> > "In an open world without walls and fences,  | [EMAIL PROTECTED]
> >   we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
> > ___
> > freebsd-ports@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Recent libxine update seems to cause ICE on 6-STABLE/amd64

[Andy Fawcett]

On Sunday 18 February 2007 16:32, Ariff Abdullah wrote:
> On Sun, 18 Feb 2007 14:28:54 +0200
>
> Andy Fawcett <[EMAIL PROTECTED]> wrote:
> > On Sunday 18 February 2007 11:04, Jack L. wrote:
> > > It fails to compile with the gcc version that comes with FreeBSD 6
> > > and 7, but it compiles fine on gcc 4.1 when I tried. It's probably
> > > a compiler bug that's been fixed on the 4.x series.
> >
> > Yes, I agree it builds fine on 6.2/amd64 when gcc 4.1 is used. I
> > guess a  simple fix for the port would be to update the USE_GCC
> > version to a value  known to work (4.1 and 4.2 from ports are ok, no
> > idea about 4.0).
> >
> > Hopefully someone more familiar with the compiler suites would be
> > able to fix  the system compilers.
>
> How about using default compiler + this patch:
>
> http://people.freebsd.org/~ariff/ports/multimedia_libxine/patch-xzz

This patch allows libxine to build on my system.

Thanks,

Andy

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: new compiler error, kdepim-3.5.6_3

[Andy Fawcett]

On Sunday 06 May 2007 15:51:45 [EMAIL PROTECTED] wrote:
> I'm running KDE-3.5.6 on FreeBSD 6.2-STABLE #2: Fri May  4 19:12:15
> EDT 2007, and CVSup'd ports this morning (05/06/2007)
>
> When running "portupgrade -a", the following error (see below) occurs
> after the build of kdepim3 runs for just over an an hour
> (kdepim-3.5.6_3) (machine info: Athlon XP2000, 512MB RAM - for the
> curious:)
>
> How to fix? We really don't want to force this, do we?:o)
>
> Byron
>
>
> Stop in /usr/ports/deskutils/kdepim3.
> ** Command failed [exit code 1]: /usr/bin/script -qa
> /tmp/portupgrade.91306.7 env UPGRADE_TOOL=portupgrade
> UPGRADE_PORT=kdepim-3.5.6_2 UPGRADE_PORT_VER=3.5.6_2 make
> ** Fix the problem and try again.
> --->  Skipping 'x11/kde3' (kde-3.5.6) because a requisite package
> 'kdepim-3.5.6_2' (deskutils/kdepim3) failed (specify -k to force)
> [Updating the pkgdb  in /var/db/pkg ... - 194
> packages found (-0 +1) . done]
> ** Listing the failed packages (*:skipped / !:failed)
> ! deskutils/kdepim3 (kdepim-3.5.6_2)(new compiler error)
> * x11/kde3 (kde-3.5.6)

Unfortunately, you've not pasted the important part, which is the part that 
actually shows the error in kdepim3. This would have come just before 
the "Stop in /usr/ports/deskutils/kdepim3." message above.

The part you pasted just shows it failed, but not the failure itself.

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: atapicam cd error

[Andy Fawcett]

On Thursday 24 May 2007 21:48:04 JoaoBR wrote:
> On Thursday 24 May 2007 15:15:51 you wrote:
> > On Wed, 23 May 2007 17:40:25 -0300
> >
> > [EMAIL PROTECTED] ~> uname -a
> > FreeBSD asus64.konav201.local 6.2-STABLE FreeBSD 6.2-STABLE #1: Tue Apr
> > 17 17:38:20 HST 2007
> > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  amd64
> >
> > [EMAIL PROTECTED] ~> dmesg | grep acd
> > acd0: DMA limited to UDMA33, device found non-ATA66 cable
> > acd0: DVDR  at ata1-master UDMA33
> > acd1: DVDROM  at ata1-slave UDMA33
> > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
> > acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
> > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
> > acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
> > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00
> > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00
> > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00
> > acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x0
> >
> > K3B works fine after build kernel/world on above date.
>
> Hi
> so you are suggesting a rollback? I compiled on may 21st and 23rd  and as
> Joe Altman confirmed too it's not working anymore on amd64 ... on i386 it's
> ok, may be this is a good moment then to change my backup strategy and use
> usb mem chips and kick atapicam out of the kernel

ping# uname -a
FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May 23 
15:19:22 EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING  
amd64

(compiled from sources updated immediately before the build started, no later 
than 10.00 UTC on 23.5.2007)

k3b is working absolutely fine on this box, I just managed to burn a CD 
followed by a DVD.


A.
-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: atapicam cd error

[Andy Fawcett]

On Friday 25 May 2007 00:46:09 JoaoBR wrote:
> On Thursday 24 May 2007 17:19:00 Andy Fawcett wrote:
> > ping# uname -a
> > FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May
> > 23 15:19:22 EEST 2007
> > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING amd64
> >
> > (compiled from sources updated immediately before the build started, no
> > later than 10.00 UTC on 23.5.2007)
> >
> > k3b is working absolutely fine on this box, I just managed to burn a CD
> > followed by a DVD.
>
> so that is funny now
> so i tried and indeed I can write an iso with cdrecord
>
> which is your k3b version? I have k3b 1.0_2

Same here.

A.

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD/i386 6-stable + 4 GB RAM

[Andy Hilker]

Hi,

You (Gerhard Schmidt) wrote:
> > The base install, running GENERIC will only use 3GB.  I believe you 
> > would either need to use the PAE kernel option, or use the 64bit version 
> > of FreeBSD on a corresponding 64bit hardware.
> 
> I Have a i386 server running with 4Gig of ram without PAE. It's running 
> with 5-STABLE. Has this changed in 6.0. 

No. It depends on your hardware how much memory is really available.
But there is no limit at 3GB in general. 

Do you use special options (KVA space etc.) in kernel-config
or make.conf to have a stable system?

bye,
Andy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

(no subject)

[Andy Jema]

Hello!

I gave a new try to 6.1-BETA4 on my Blade 150 recently but
there are some errors still spitting out during an 
installation:


acd0: TIMEOUT - READ_BIG retrying (1 retry left)
Interrupt storm detected on "vec1996:"; throttling interrupt 
source

acd0: TIMEOUT - READ_BIG retrying (1 retry left)

hw.ata.atapi_dma to 0
dmesg:
Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard
Copyright 1998-2002 Sun Microsystems, Inc.  All rights 
reserved.

OpenBoot 4.6, 512 MB memory installed, Serial #53155393.
Ethernet address 0:3:ba:2b:16:41, Host ID: 832b1641.



Rebooting with command: boot cdrom
Boot device: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:f  File 
and args:
 

FreeBSD/sparc64 boot block

   Boot path:   /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:f
   Boot loader: /boot/loader
Consoles: Open Firmware console
Boot path set to /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:a

FreeBSD/sparc64 bootstrap loader, Revision 1.0
([EMAIL PROTECTED], Thu Mar 16 00:29:29 UTC 2006)
bootpath="/[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:a"
Loading /boot/defaults/loader.conf
/boot/kernel/kernel data=0x490f08+0x5bbb8 
syms=[0x8+0x63960+0x8+0x5396f]

/
Hit [Enter] to boot immediately, or any other key for command 
prompt.

Booting [/boot/kernel/kernel]...
nothing to autoload yet.
jumping to kernel entry at 0xc006.
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 
1993, 1994
The Regents of the University of California. All 
rights reserved.

FreeBSD 6.1-BETA4 #0: Thu Mar 16 15:20:20 UTC 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Timecounter "tick" frequency 65000 Hz quality 1000
real memory  = 536870912 (512 MB)
avail memory = 506642432 (483 MB)
cpu0: Sun Microsystems UltraSparc-IIe Processor (650.00 MHz 
CPU)

nexus0: 
pcib0:  on nexus0
pcib0: Hummingbird compatible, impl 0, version 0, ign 0x7c0, 
bus A

pcib0: [FAST]
pcib0: [FAST]
pcib0: [GIANT-LOCKED]
pcib0: [GIANT-LOCKED]
pcib0 dvma: DVMA map: 0xc000 to 0xc3ff
pci0:  on pcib0
ebus0:  mem 
0xf000-0xf0ff,0xf100-0xf17f at device 12.0 on 
pci0

ebus0: : incomplete
ebus0:  addr 0-0xf (no driver attached)
eeprom0:  addr 0x1-0x11fff on ebus0
eeprom0: model mk48t59
eeprom0: hostid 832b1641
isab0:  at device 7.0 on pci0
isa0:  on isab0
gem0:  mem 0x40-0x41 
at device 12.1 on pci0

miibus0:  on gem0
ukphy0:  on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
gem0: 2kB RX FIFO, 2kB TX FIFO
gem0: Ethernet address: 00:03:ba:2b:16:41
fwohci0:  mem 0x42-0x4207ff,0x422000-0x4227ff 
at device 12.2 on pci0

fwohci0: OHCI version 1.0 (ROM=0)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:03:ba:ff:fe:2b:16:41
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0:  on fwohci0
sbp0:  on firewire0
fwe0:  on firewire0
if_fwe0: Fake Ethernet address: 02:03:ba:2b:16:41
fwe0: Ethernet address: 02:03:ba:2b:16:41
fwe0: if_start running deferred for Giant
fwohci0: Initiate bus reset
fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
ohci0:  mem 0x200-0x2007fff at 
device 12.3 on pci0

ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0:  on ohci0
usb0: USB revision 1.0
uhub0: (0x108e) OHCI root hub, class 9/0, rev 1.00/1.00, addr 
1

uhub0: 4 ports with 4 removable, self powered
pci0:  at device 3.0 (no driver 
attached)

pci0:  at device 8.0 (no driver attached)
atapci0:  port 
0xa00-0xa07,0xa18-0xa1b,0xa10-0xa17,0xa08-0xa0b,0xa20-0xa2f at 
device 13.0 on pci0
atapci0: using PIO transfers above 137GB as workaround for 
48bit DMA access bug, expect reduced performance

ata2:  on atapci0
ata3:  on atapci0
pcib1:  at device 5.0 on pci0
pci1:  on pcib1
machfb0:  port 0xb00-0xbff mem 
0x300-0x3ff,0x426000-0x426fff at device 19.0 on pci0
machfb0: 16 MB aperture at 0xd5d14000, 1 KB registers at 
0x037ffc00
machfb0: 8188 KB SDRAM 114.992 MHz, maximum RAMDAC clock 230 
MHz, DSP

machfb0: resolution 1152x900 at 8 bpp
syscons0:  on nexus0
syscons0: Unknown <16 virtual consoles, flags=0x100>
uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 43 on 
isa0

uart0: console (9600,n,8,1)
uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 43 on 
isa0

Timecounters tick every 1.000 msec
md0: Preloaded image  4194304 bytes at 
0xc05a3da0
ad0: 38166MB  at ata2-master 
UDMA66
acd0: CDRW  at ata2-slave 
UDMA66

Trying to mount root from ufs:/dev/md0
/stand/sysinstall running as init on serial console

Setting hw.ata.atapi_dma to 0 gives no luck :(

Sincerely yours,
Andy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: a place for configuration files

[Andy Newman]

Gary Kline wrote:
>   but the /usr/local directory paradigm is a Berkeley thing.
>   It probably began with the 4.X distribution

It's in a 3BSD tree I have lying around. Dated 1980.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Suggestions for Adaptec SAS AIC9410

[Andy Dills]

I'm trying to get a Supermicro 6024H-32R setup with 6.1, but I'm 
discovering that the Adaptec SAS AIC9410 controller isn't yet supported. 

I see one brief thread about it on this mailing list back in March, but no 
further mention or conclusive details. There was talk of MFCing the mpt 
driver...is anybody using this in production?  

I'd prefer to use FreeBSD, but I'm guessing I'm going to need to do SuSE 
for this box, which Adaptec provides drivers for.

Thanks,
Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Suggestions for Adaptec SAS AIC9410

[Andy Dills]

On Fri, 9 Jun 2006, Scott Long wrote:

> Doug White wrote:
> > On Mon, 5 Jun 2006, Andy Dills wrote:
> > 
> > > 
> > > I'm trying to get a Supermicro 6024H-32R setup with 6.1, but I'm
> > > discovering that the Adaptec SAS AIC9410 controller isn't yet supported.
> > > 
> > > I see one brief thread about it on this mailing list back in March, but no
> > > further mention or conclusive details. There was talk of MFCing the mpt
> > > driver...is anybody using this in production?
> > 
> > 
> > Can you get a pciconf -lv off this system? It might just be a case of
> > needing to add an ID to an existing driver (aac?).
> > 
> 
> No, the 9410 is a SAS HBA chip.  It's actually meant to be used just in
> Adaptec HostRAID (software RAID) mode, but writing a standalone driver
> is possible, albeit fairly difficult and time consuming.

Being completely ignorant of the deep internals of the FreeBSD kernel, the 
GEOM layer, etc., how difficult is it to take the existing linux drivers 
that Adaptec distributes and port them to FreeeBSD?

I ask out of curiousity, not implying that it isn't difficult and time 
consuming.

Thanks,
Andy

---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Lifetime of FreeBSD branches

[Andy Fawcett]

On Friday 27 May 2005 23:22, Matthias Buelow wrote:
> Scott Long wrote:
> > Yeah, and what I'm trying to do is smooth the bumps for the long
> > term. The 4.x->5.x transition was simply a gigantic mess for users,
> > and it was largely a function of it being 4+ years in the making.
>
> It still _is_ a gigantic mess.  My hosted 5.3-stable server
> just crapped itself for the second time this year, for no apparent
> reason.  I suggest  reestablishing 4.x as the "production" tree and
> continuing to maintain it for a while, including making releases, and
> regressing 5.x to what it is and probably will be for quite a while:
> "experimental".

And to counter your rant, I've been using 5.x since 5.0-DP1 on a range 
of hardware (mostly i386 in quite different setups, and more recently 
amd64 too) with virtually no problems.

On the other hand, 4.x (I think it was 4.9, but I really cannot remember 
for sure) crapped all over one box so hard I refuse to ever use it 
again.

A.

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Old messages

[Andy Gilligan]

Ok, is it just me or did anyone else receive a bunch of mails to -stable
from about 6-7 months ago?

-Andy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

5.4-p3 and bind9: isc_mutex_init failed in new_adbfind / exited on signal 11

[Andy Hilker]

Hi,

after upgrading to 5.4-p3 I have problems with bind 9. After a few
days it exits on signal 11. I am using an SMP kernel.  I have found
some other people describing the same problem, without a solution. 
On 5.3 I did not experience such things, bind runs stable.  Just
want to confirm this issue to whom it may concern.

If someone needs more info to debug or have hints/workarounds,
please answer.

named[721]: /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/adb.c:1439: 
unexpected error:
named[721]: isc_mutex_init failed in new_adbfind()
pid 721 (named), uid 53: exited on signal 11

bye,
Andy

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4-p3 and bind9: isc_mutex_init failed in new_adbfind / exited on signal 11

[Andy Hilker]

Hi,

You (Mark Andrews) wrote:
>   FreeBSD's pthread_mutex_init() (isc_mutext_init()) can fail
>   if there is no memory.  On most other OS this is not the case.
>   
>   The callers to isc_mutext_init() assume that a failure is due
>   to a double initialision and as a result log a error message
>   when it fails.  Memory allocation failures on the other hand
>   are not logged.

Thanks for your reply.
I think I have found the "reason". I have configured datasize value
lower than max-cache-size. Obviously this makes no sense.
Now I am waiting if it runs stable again.

bye,
Andy

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: x for users slow

[Andy Sparrow]

> On Monday 01 August 2005 17:34, Eriq wrote:
> > after all of this, I notice that it takes a user about a minute after
> > 'startx' to get into X. Yes I know, but I still like the colors :)
> > anyway this doesn't happen when I logon as root and start X. Blackbox is
> > the WM hope this helps.
> 
> At a wild guess I would say your DNS is broken.

Umm, yup, maybe.

There might be another phenomena, however. I resisted moving my laptop 
from XFree86 to XOrg until it became too much of a pain staying back. I 
only switched when VMware broke for me and I needed to try OpenOffice.

When I finally moved to Xorg (and rebuilt all my ports with portupgrade 
for good measure), the first thing I noticed was that it took almost a 
couple of minutes[0] on my laptop (1GHz PIII) for 'wdm' to display the 
login window and overlay the background over the grey weave. The hdd LED 
was lit solidly the entire time.

IIRC, the same machine (actually, it had a slower CPU then) with XFree86 
took maybe 10-15 seconds when I typed 'wdm&&exit' at a root prompt.

This is with 4.1[01]-STABLE, the built-in graphics are ATI Rage Mobility 
(Mach64), not exactly bleeding edge (and fairly well supported).

Other than that idiosyncracy, (and some infrequent odd effects with 
either xine or mplayer that can be cleared by re-starting the X server, 
at least some of which also happened with XFree68 and are probably due 
to the player apps), the Xorg server seems to work just fine. It does 
seem to behave somewhat differently to XFree86 on startup, however.

If all he's noticing is a slow X startup with the Xorg server, thats an 
 from me. I can't comment if starting it as a user is even slower, 
because I almost never use 'startx', I always run a display manager and 
log into that.

Cheers,

AS

[0] OK, I haven't actually timed it, but it's at least a minute, 
probably longer and it's 100% consistant.



pgpKpKAgF3LYF.pgp
Description: PGP signature

rc-ng problem with [procname] (e.g. kernel threaded procs)

[Andy Hilker]

Hi,

i think I have found a problem with rc-ng scripts and procnames
including brackets (e.g. kernel threaded, like mysqld).

Brackets [] are ignored, process will not be found and is regarded
as "not running". This breaks stop+status functions of rcng. The
following patch allows brackets in variable procname rc-ng scripts.
Maybe someone can review and fix this issue.

It was relevant for me when using [mysqld].

bye,
Andy


# $FreeBSD: src/etc/rc.subr,v 1.31.2.1 2005/01/17 11:51:00 keramida Exp $
--- rc.subr Thu Aug 11 15:18:52 2005
+++ /etc/rc.subrThu Aug 11 15:14:06 2005
@@ -267,7 +267,7 @@
_procnamebn=${_procname##*/}
_fp_args='_arg0 _argv'
_fp_match='case "$_arg0" in
-   $_procname|$_procnamebn|${_procnamebn}:|"(${_procnamebn})")'
+   
"$_procname"|$_procnamebn|${_procnamebn}:|"(${_procnamebn})")'
fi
 
_proccheck='

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: rc-ng problem with [procname] (e.g. kernel threaded procs)

[Andy Hilker]

Hmh, no one interested in this issue? Or am i wrong with this issue?

You (Andy Hilker) wrote:
> Hi,
> 
> i think I have found a problem with rc-ng scripts and procnames
> including brackets (e.g. kernel threaded, like mysqld).
> 
> Brackets [] are ignored, process will not be found and is regarded
> as "not running". This breaks stop+status functions of rcng. The
> following patch allows brackets in variable procname rc-ng scripts.
> Maybe someone can review and fix this issue.
> 
> It was relevant for me when using [mysqld].
> 
> bye,
> Andy
> 
> 
> # $FreeBSD: src/etc/rc.subr,v 1.31.2.1 2005/01/17 11:51:00 keramida Exp $
> --- rc.subr Thu Aug 11 15:18:52 2005
> +++ /etc/rc.subrThu Aug 11 15:14:06 2005
> @@ -267,7 +267,7 @@
> _procnamebn=${_procname##*/}
> _fp_args='_arg0 _argv'
> _fp_match='case "$_arg0" in
> -   
> $_procname|$_procnamebn|${_procnamebn}:|"(${_procnamebn})")'
> +   
> "$_procname"|$_procnamebn|${_procnamebn}:|"(${_procnamebn})")'
> fi
>  
> _proccheck='
> 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: rc-ng problem with [procname] (e.g. kernel threaded procs)

[Andy Hilker]

You (Jilles Tjoelker) wrote:
> On Tue, Aug 16, 2005 at 07:24:41PM +0200, Andy Hilker wrote:
> > Hmh, no one interested in this issue? Or am i wrong with this issue?
> 
> Apparently noone is interested.
> 
> Be sure to file a PR if you haven't done so yet.

Done. Some other guy has reported this as a PR, too and attached a
better patch than mine.

bye,
Andy

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

USB Card Reader Permissions

[Andy Fraser]

Hi,

I was wondering if someone could tell me how to set the permissions for a USB 
card reader when it's plugged in? I've been Googling for hours and found 
nothing concrete so far although I'll keep looking.

So far I have this situation:
I plug in the card reader and device nodes are created 
(e.g. /dev/da0s1, /dev/da1s1 etc). I can mount this as root and if I manually 
set the permissions I can mount it as my user too. What I can't work out is 
how to change the permissions when I plug it in so I can just use the reader 
as my user.

I've read the man pages for devfs, devfs.conf and devfs.rules. devfs.rules 
looks like what I need but I can't work out what I actually need to do or how 
to test a rule without rebooting.

I'm using FreeBSD 6.0-STABLE.

Thanks in advance to anyone who can help.

-- 
Andy.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: USB Card Reader Permissions

[Andy Fraser]

On Tuesday 08 Nov 2005 10:11 pm, Daniel O'Connor wrote:
> > I was wondering if someone could tell me how to set the permissions for a
> > USB card reader when it's plugged in? I've been Googling for hours and
> > found nothing concrete so far although I'll keep looking.
>
> devfs.conf can do it.

I thought that was only for devices that exist at boot? I have my DVD burner 
set up in devfs.conf so I can use it as my user (reading and burning with 
some other tweaks[1]).

> > So far I have this situation:
> > I plug in the card reader and device nodes are created
> > (e.g. /dev/da0s1, /dev/da1s1 etc). I can mount this as root and if I
> > manually set the permissions I can mount it as my user too. What I can't
> > work out is how to change the permissions when I plug it in so I can just
> > use the reader as my user.
>
> [inchoate 8:36] ~ >cat /etc/devfs.rules
> [root=100]
>
> add path 'da*' group operator mode 660

I already had something like this...

> And in rc.conf..
> devfs_system_ruleset="root"

...and this turned out to be the missing piece in the jigsaw.

> > I've read the man pages for devfs, devfs.conf and devfs.rules.
> > devfs.rules looks like what I need but I can't work out what I actually
> > need to do or how to test a rule without rebooting.
>
> It isn't very obvious :(
> You can test your changes by doing..
> /etc/rc.d/devfs restart

I'd been trying that. It turns out I had completely missed the rc.conf line 
above so obviously restarting devfs had no effect.

Many thanks Daniel. It's working just how I want it now. :-)

[1] One of the reasons I first tried FreeBSD as a desktop OS was because it 
has better support for CD/DVD burning as a user than Linux does (I still 
can't get burning working reliably with Gentoo but FreeBSD works flawlessly). 
And the sound system is much better but that's another story. :-)

-- 
Andy.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: USB Card Reader Permissions

[Andy Fraser]

On Wednesday 09 Nov 2005 12:22 am, Daniel O'Connor wrote:
> > I thought that was only for devices that exist at boot? I have my DVD
> > burner set up in devfs.conf so I can use it as my user (reading and
> > burning with some other tweaks[1]).
>
> Nope, it's applied to all devices as they are created as well as
> pre-existing ones.

Ah, cool. :-)

> > ...and this turned out to be the missing piece in the jigsaw.
>
> Yeah it took me a while to find out you needed that too :)

:-)

> > [1] One of the reasons I first tried FreeBSD as a desktop OS was because
> > it has better support for CD/DVD burning as a user than Linux does (I
> > still can't get burning working reliably with Gentoo but FreeBSD works
> > flawlessly). And the sound system is much better but that's another
> > story.
> >
> > :-)
>
> Weird, I would expect it to be largely the same.

I don't want to say too much, it being OT and all, but a change in Linux 2.6.8 
has meant that I have to run my burning software as root to get a reliable 
burn. I've yet to find a solution to that problem.

> PS another way to do this would be to create a devd file which does the
> chmod's for this particular device (instead of blindly changing all da
> devices).

I have things working, I'm happy. :-)

I'll look at other options and better set ups when I have either the need or 
the time. :-)

-- 
Andy.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: xorg-clients conflicts with xterm (patch)

[Andy Fraser]

On Wednesday 16 Nov 2005 3:26 am, James Long wrote:
> After hours of head-banging over the past couple of days,
> I have finally succeeded in installing EITHER
> xorg-clients-6.8.2_1 OR xterm-206_1.  Previously,
> installing either port told me that it conflicted
> with the other, in spite of having cvsupped my
> ports tree twice to ensure I was getting the most
> recent version of the ports, hopefully including a
> fix to the chicken-and-egg problem noted in
> /usr/ports/UPDATING

I had a similar problem. xterm-206_1 conflicted with xorg-clients-6.8.2_1. 
portmanager suggested removing xorg-clients after which xterm installed but 
xorg-clients wouldn't build anymore[1]. Some Googling suggested that the 
nVidia driver port (I don't know whether you're using this or not) replaced 
glx.h causing the xorg-clients to fail (unchecked) and reinstalling 
xorg-libraries would fix it. This worked for me.

I'm not sure whether you're having the same problem or not but I thought I'd 
mention this just in case.

[1] I also had this problem with 5.4-STABLE but to get around it there I 
installed a binary package to save time.

-- 
Andy Fraser.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: xorg-clients conflicts with xterm (patch)

[Andy Fawcett]

On Wednesday 16 November 2005 23:26, Dejan Lesjak wrote:
> On Wednesday 16 of November 2005 04:26, James Long wrote:
> > After hours of head-banging over the past couple of days,
> > I have finally succeeded in installing EITHER
> > xorg-clients-6.8.2_1 OR xterm-206_1.  Previously,
> > installing either port told me that it conflicted
> > with the other, in spite of having cvsupped my
> > ports tree twice to ensure I was getting the most
> > recent version of the ports, hopefully including a
> > fix to the chicken-and-egg problem noted in
> > /usr/ports/UPDATING
>
> x11/xorg-clients port does not conflict with any version of xterm.
> Where do you see that?

For an interesting variation, I have a totally up to date ports tree, 
with the latest versions of xterm and xorg-clients already installed:

xterm-206_1 Terminal emulator for the X Window System
xorg-clients-6.8.2_1 X client programs and related files from X.Org

then, portupgrade -fp xterm xorg-clients
...
===>  Installing for xterm-206_1

===>  xterm-206_1 conflicts with installed package(s):
  xorg-clients-6.8.2

  They install files into the same place.
  Please remove them first with pkg_delete(1).
*** Error code 1

Again, please note that xterm conflicts with the version of the clients 
it is supposed to work with. This is repeatable on 2 systems I have 
tried so far, 5.4-RELEASE/i386 and 6.0-STABLE/amd64.

A.

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: xorg-clients conflicts with xterm (patch)

[Andy Fawcett]

Argh! Correction below.

On Thursday 17 November 2005 00:02, Andy Fawcett wrote:
> On Wednesday 16 November 2005 23:26, Dejan Lesjak wrote:
> > On Wednesday 16 of November 2005 04:26, James Long wrote:
> > > After hours of head-banging over the past couple of days,
> > > I have finally succeeded in installing EITHER
> > > xorg-clients-6.8.2_1 OR xterm-206_1.  Previously,
> > > installing either port told me that it conflicted
> > > with the other, in spite of having cvsupped my
> > > ports tree twice to ensure I was getting the most
> > > recent version of the ports, hopefully including a
> > > fix to the chicken-and-egg problem noted in
> > > /usr/ports/UPDATING
> >
> > x11/xorg-clients port does not conflict with any version of xterm.
> > Where do you see that?
>
> For an interesting variation, I have a totally up to date ports tree,
> with the latest versions of xterm and xorg-clients already installed:
>
> xterm-206_1 Terminal emulator for the X Window System
> xorg-clients-6.8.2_1 X client programs and related files from X.Org
>
> then, portupgrade -fp xterm xorg-clients
> ...
> ===>  Installing for xterm-206_1
>
> ===>  xterm-206_1 conflicts with installed package(s):
>   xorg-clients-6.8.2
>
>   They install files into the same place.
>   Please remove them first with pkg_delete(1).
> *** Error code 1
>
> Again, please note that xterm conflicts with the version of the
> clients it is supposed to work with.

this should read "shows a conflict with a version of the port that is 
not installed".

> This is repeatable on 2 systems 
> I have tried so far, 5.4-RELEASE/i386 and 6.0-STABLE/amd64.
>
> A.

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Andy Fawcett]

On Tuesday 06 December 2005 23:46, Kris Kennaway wrote:
> On Tue, Dec 06, 2005 at 02:36:05PM -0700, secmgr wrote:
> > >Update to 5.4 before trying to update to 6.0.
> > >
> > >Kris
> >
> > So is there any supported direct 5.3->6.0 upgrade path, or is a
> > stop in 5.4 ville manditory now.?
>
> I tried to say that you have to update to 5.4 before you can update
> to 6.0, i.e. updates from older versions are not supported.  It may
> be easier to do a binary upgrade (i.e. download release media and use
> the upgrade option).

At least with a vanilla install of 5.3, I had no problem going directly 
to 6.0.

This was an extremely basic install, and I only did it because I lost my 
6.0-R cd :)

A.

-- 
Andy Fawcett | [EMAIL PROTECTED]
 | [EMAIL PROTECTED]
"In an open world without walls and fences,  | [EMAIL PROTECTED]
  we wouldn't need Windows and Gates."  -- anon  | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"