Re: Please remove Perl from ports

[Stephen Montgomery-Smith]

On 08/01/2013 10:31 AM, Chris H wrote:

 So, in the end; why did Perl have to be relocated? Is my only
 recourse at this point to
 # cd /
 # rm -rf .

When I get into this kind of bad situation, I usually do something
slightly less drastic:
# pkg_delete -a
# find -d /usr/local -type d -exec rmdir {} \;
This last command removes empty directories in /usr/local (it also
produces lots of error messages when it tries to remove non-empty
directories).  Then I look through the contents of /usr/local,
especially if there is anything in /usr/local/etc or /usr/local/libexec
where some of my manually changed configuration files reside.  And then
I delete any crud left over that I know I don't need.

After that, I rebuild all the ports from scratch.

Finally, I do understand why you feel the need to vent, and I don't want
to belittle your feelings of frustration.  But I do think everyone is
trying their best.  I like to tell people that running FreeBSD or Linux
is like owning a souped up sports car - usually it runs really well, but
it often needs a lot of attention.  (Windows is like driving a cheap car
that breaks down all the time, but engine is designed in such a way as
to be totally inaccessible with regards to repairs.  And Apple is like
driving a BMW - it mostly works well but you pay a lot for it.)

___
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: svn - but smaller?

[Stephen Montgomery-Smith]

On 02/24/2013 03:24 PM, Jeremy Chadwick wrote:
 On Sun, Feb 24, 2013 at 10:19:57AM -0700, Ian Lepore wrote:
 On Sat, 2013-02-23 at 22:31 -0800, Jeremy Chadwick wrote:

 Also, John, please consider using malloc(3) instead of heap-allocated
 buffers like file_buffer[6][] (196608 bytes) and command[] (32769
 bytes).  I'm referring to this: 

 Why?  I absolutely do not understand why people are always objecting to
 large stack-allocated arrays in userland code (sometimes with the
 definition of large being as small as 2k for some folks).
 
 This is incredibly off-topic, but I'll bite.
 
 I should not have said heap-allocated, I was actually referring to
 statically-allocated.
 
 The issues as I see them:


 
 2. If the length of the buffer exceeds the amount of stack space
 available at the time, the program will run but the behaviour is unknown
 (I know that on FreeBSD if it exceeds stacksize per resource limits,
 the program segfaults at runtime).  With malloc and friends you can
 gracefully handle allocation failures.

This actually happened to me.  The program mkctm used to allocate space
using alloca (which is the same as declaring it like char
file_buffer[big_no] if big_no could be variable).  But this is space on
the stack as opposed to the heap, and if you type the command limit
you will see that the stack size is typically much smaller than the heap
size.  And on 32 bit machines, the default value of stack size is rather
small.  Anyway, one day mkctm stopped working for me, and precisely for
this reason.  It took me a day to trace the fault, and I ended up
rewriting the code to use malloc instead.  (mkctm is a little known
program, whose code is included in the FreeBSD base, to create updates
for the CTM delivery method.)

Probably on 64 bit machines it is not such a big issue.  And on Linux, I
think it makes no difference at all, because on Linux all data is stored
on the heap.
___
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: svn - but smaller?

[Stephen Montgomery-Smith]

On 02/24/2013 05:43 PM, Ian Lepore wrote:
 On Sun, 2013-02-24 at 13:24 -0800, Jeremy Chadwick wrote:
 On Sun, Feb 24, 2013 at 10:19:57AM -0700, Ian Lepore wrote:
 On Sat, 2013-02-23 at 22:31 -0800, Jeremy Chadwick wrote:

 Also, John, please consider using malloc(3) instead of heap-allocated
 buffers like file_buffer[6][] (196608 bytes) and command[] (32769
 bytes).  I'm referring to this: 

 Why?  I absolutely do not understand why people are always objecting to
 large stack-allocated arrays in userland code (sometimes with the
 definition of large being as small as 2k for some folks).

 This is incredibly off-topic, but I'll bite.

 I should not have said heap-allocated, I was actually referring to
 statically-allocated.

 The issues as I see them:

 1. Such buffers exist during the entire program's lifetime even if they
 aren't actively used/needed by the program.  With malloc(3) and friends,
 you're allocating memory dynamically, and you can free(3) when done with
 it, rather than just having a gigantic portion of memory allocated
 sitting around potentially doing nothing.

 2. If the length of the buffer exceeds the amount of stack space
 available at the time, the program will run but the behaviour is unknown
 (I know that on FreeBSD if it exceeds stacksize per resource limits,
 the program segfaults at runtime).  With malloc and friends you can
 gracefully handle allocation failures.

 3. Statically-allocated buffers can't grow; meaning what you've
 requested size-wise is all you get.  Compare this to something that's
 dynamic -- think a linked list containing pointers to malloc'd memory,
 which can even be realloc(3)'d if needed.

 The definition of what's too large is up to the individual and the
 limits of the underlying application.  For some people, sure, anything
 larger than 2048 might warrant use of malloc.  I tend to use malloc for
 anything larger than 4096.  That magic number comes from some piece of
 information I was told long ago about what size pages malloc internally
 uses, but looking at the IMPLEMENTATION NOTES section in malloc(3) it
 appears to be a lot more complex than that.

 If you want me to break down #1 for you with some real-world output and
 a very small C program, showing you the effects on RES/RSS and SIZE/VIRT
 of static vs. dynamic allocation, just ask.

 
 Actually, after seeing that the userland limit for an unpriveleged user
 on freebsd is a mere 64k, I'd say the only valid reason to not allocate
 big things on the stack is because freebsd has completely broken
 defaults.  I see no reason why there should even be a distinction
 between stack size and memory use limits in general.  Pages are pages,
 it really doesn't matter what part of your virtual address space they
 live in.

I think that the stacksize and datasize cannot together add up to more
than 4G, or maybe it is only 2G, at least on a 32 bit machine.  This is
because (I think) they compete for virtual memory address space.  I
guess this wasn't a problem in the old days, when 4G of RAM was unthinkable.

Also, as I said in another thread, I think Linux doesn't make this
distinction.  So at least someone else out there agrees with you.


___
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: svn - but smaller?

[Stephen Montgomery-Smith]

On 01/28/2013 07:34 AM, Isaac (.ike) Levy wrote:
 On CTM,
 
 On Jan 27, 2013, at 10:54 PM, Stephen Montgomery-Smith wrote:
 On 01/27/2013 09:24 PM, Isaac (.ike) Levy wrote:
 On Jan 24, 2013, at 6:13 AM, Peter Jeremy wrote:
 On 2013-Jan-23 15:40:50 +0100, Oliver Brandmueller o...@e-gitt.net wrote:
 in ancient times there was cvsup.

 Thank you for adding the ctm bits in the page, I'm deeply intrigued by 
 possibly solving this problem with bits *already* in base?!!
 ...
 - does CTM go away with the CVS servers?
 - do CTM-compatable patch/delta files exist on project repos?
 - what is the cleanest path to using CTM? (e.g. is the patch you mention 
 required)
 ...
 Say I have a bare 9.1 install, no ports, haven't downloaded any base/src or 
 ports yet.
 How do I go about using ctm(1) to fetch REL or STABLE to /usr/src, command 
 by command?

 First, you don't need any patches to get started.

 Suppose you want to keep up with 9.x-stable.  Then you look at the ftp
 site ftp://ftp.freebsd.org/pub/FreeBSD/CTM/src-9/, look at the latest
 xEmpty file, and fetch it.  Then create an empty directory /usr/src, and
 then do
 cd /usr/src  ctm the-xEmpty-file-you-downloaded.
 No need to decompress the file first.
 Then fetch from the same web site all the files whose number is greater
 than the xEmpty file you downloaded and do
 cd /usr/src  ctm the-rest-of-the-files*

 Now in /usr/src, you will have a reasonably up to date version of
 9.x-stable.

 You can keep it up to date by getting more files, either from the ftp
 site, or by email, and doing again
 cd /usr/src  ctm the-rest-of-the-files*
 It will automatically ignore the files already applied.

 Similar instructions for all the other stable/currents and ports.  Main
 thing to remember - start with an empty directory.

 Also making local changes is not permitted.  If ctm tries to modify a
 file whose md5 checksum has changed, it will quit with an error message.
 (But it won't leave your system in an unusable state - if you put that
 file back to its original state, then ctm will work again.)

 Now, if you want something not offered by ctm (e.g. 8.2-release), then
 you need to use svn.  You can get svn via ctm.  But you (1) need to
 apply the patch, (2) install the svn port, and (3) install the xz port
 if your FreeBSD is really old.
 
 Thank you Stephen, ctm(1) is quite rad, but I see now how it doesn't really 
 replace the 'one-liner' pull of c[v]sup…
 
 I updated the wiki page with an example from your notes,
 https://wiki.freebsd.org/UsersFetchingSource
 
 --
 With that, 2 questions:
 
 - I'm wondering if there is a clean/reliable way to pull an index of the CTM 
 deltas?  (This is still very far from the one-liner c[v]sup had become, it 
 would be great to check for new delta files in a simple automated manner.)
 

Not sure what you mean.  You can do ctm -l file-name and it will tell
you what files are modified in that delta.  And for ports, you have the
usual make fetchindex.  But that is about it.

 - does CTM go away with the CVS servers, e.g. who/how is it supported 
 supported and maintained going foreword under SVN?
 

No.  CTM is now completely dependent on svn.  I create the CTM deltas on
a computer owned by the University of Missouri.

___
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: svn - but smaller?

[Stephen Montgomery-Smith]

On 01/28/13 08:17, Isaac (.ike) Levy wrote:

On CTM:

On Jan 28, 2013, at 9:09 AM, Stephen Montgomery-Smith wrote:

- I'm wondering if there is a clean/reliable way to pull an index of the CTM 
deltas?  (This is still very far from the one-liner c[v]sup had become, it 
would be great to check for new delta files in a simple automated manner.)



Not sure what you mean.  You can do ctm -l file-name and it will tell
you what files are modified in that delta.  And for ports, you have the
usual make fetchindex.  But that is about it.


I'm sorry I wasn't clear enough- I meant:
On the FTP server, is there an index of which CTM delta files are on the FTP 
server?  I'd like to automate fetching just the new deltas...

If there was perhaps 1 file with a consistent name, I could fetch that on a 
nightly basis and fetch the other CTM files.


I can easily put in something like this.  Maybe the output of ls in each 
directory?


If you have more ideas on this, sign up to the ctm-users mailing list, 
and we can discuss exactly what is wanted.






- does CTM go away with the CVS servers, e.g. who/how is it supported supported 
and maintained going foreword under SVN?



No.  CTM is now completely dependent on svn.  I create the CTM deltas on
a computer owned by the University of Missouri.


Cool.
Is there any redundancy for this process, for example, deltas being created out 
on the east/west mirrors?  Perhaps as an SVN post-commit hook?



No.  The deltas are created in one place.  And they are created every 16 
hours according to a rigid schedule.


___
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: svn - but smaller?

[Stephen Montgomery-Smith]

On 01/27/2013 09:24 PM, Isaac (.ike) Levy wrote:
 Hi Peter,
 
 On Jan 24, 2013, at 6:13 AM, Peter Jeremy wrote:
 
 On 2013-Jan-23 15:40:50 +0100, Oliver Brandmueller o...@e-gitt.net wrote:
 in ancient times there was cvsup. cvsup was a PITA if you wanted (or 
 needed) to install it via ports, the only reasonable way was to use 
 pkg_add for that if you didn't want to pollute your system with 
 otherwise unneeded software.

 There was also ctm(1).  ctm is small, BSD-licensed and has been part
 of FreeBSD forever (almost).  Thanks to stephen@, ctm deltas for
 various src trees, as well as the entire SVN repo are still available.
 c[v]sup can do things than aren't possible with ctm but I would expect
 that most people who currently use c[v]sup could readily migrate to
 using ctm.

 See http://www.freebsd.org/doc/handbook/ctm.html for details.

 Note that mirroring the actual SVN repo via ctm requires some patches.
 There is a README and patches in 
 ftp://ftp.freebsd.org/pub/FreeBSD/CTM/svn-cur/

 -- 
 Peter Jeremy
 
 Thank you for adding the ctm bits in the page, I'm deeply intrigued by 
 possibly solving this problem with bits *already* in base?!!
 
 https://wiki.freebsd.org/action/diff/UsersFetchingSource?action=diffrev1=6rev2=7
 
 However, even after reading the handbook page, I just don't quite understand 
 how to use it on a modern system.  (The handbook page isn't too helpful, nor 
 is the man page- perhaps I'm looking at it backwards)  Could you help clarify:
 
 - does CTM go away with the CVS servers?
 - do CTM-compatable patch/delta files exist on project repos?
 - what is the cleanest path to using CTM? (e.g. is the patch you mention 
 required)
 
 --
 Say I have a bare 9.1 install, no ports, haven't downloaded any base/src or 
 ports yet.
 How do I go about using ctm(1) to fetch REL or STABLE to /usr/src, command by 
 command?

First, you don't need any patches to get started.

Suppose you want to keep up with 9.x-stable.  Then you look at the ftp
site ftp://ftp.freebsd.org/pub/FreeBSD/CTM/src-9/, look at the latest
xEmpty file, and fetch it.  Then create an empty directory /usr/src, and
then do
cd /usr/src  ctm the-xEmpty-file-you-downloaded.
No need to decompress the file first.
Then fetch from the same web site all the files whose number is greater
than the xEmpty file you downloaded and do
cd /usr/src  ctm the-rest-of-the-files*

Now in /usr/src, you will have a reasonably up to date version of
9.x-stable.

You can keep it up to date by getting more files, either from the ftp
site, or by email, and doing again
cd /usr/src  ctm the-rest-of-the-files*
It will automatically ignore the files already applied.

Similar instructions for all the other stable/currents and ports.  Main
thing to remember - start with an empty directory.

Also making local changes is not permitted.  If ctm tries to modify a
file whose md5 checksum has changed, it will quit with an error message.
 (But it won't leave your system in an unusable state - if you put that
file back to its original state, then ctm will work again.)

Now, if you want something not offered by ctm (e.g. 8.2-release), then
you need to use svn.  You can get svn via ctm.  But you (1) need to
apply the patch, (2) install the svn port, and (3) install the xz port
if your FreeBSD is really old.


___
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: csup to svn for 8-stable

[Stephen Montgomery-Smith]

On 01/11/2013 04:51 PM, Brian W. wrote:
 When I tried the first time, it only grabbed a few folders, a second try
 got me a conflict message. I then just whacked /usr/src and did the svn co
 again, successfully.
 
 Brian

And when you want to update, you can just type
svn up /usr/src


 
 
 On Fri, Jan 11, 2013 at 2:48 PM, David Wolfskill da...@catwhisker.orgwrote:
 
 On Fri, Jan 11, 2013 at 02:45:10PM -0800, Brian W. wrote:
 I had an existing /usr/src/ tree from previous csup sessions. After a bit
 of reading, it looks like all I need to do are these two steps?

 pkg_add -r subversion
 svn co svn://svn.freebsd.org/base/stable/8 /usr/src

 Is it really that simple for a src update?

 Unless you have custom modifications in your source tree, I believe that
 you will find it simpler to remove it (or at least rename it) and use
 the above svn co to create a fresh new working copy.

 I have been using portsnap for years for ports, so I can continue to do
 that.

 That is my understanding, yes.

 ...

 Peace,
 david
 --
 David H. Wolfskill  da...@catwhisker.org
 Taliban: Evil men with guns afraid of truth from a 14-year old girl.

 See http://www.catwhisker.org/~david/publickey.gpg for my public key.

 ___
 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-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: Does / Is anyone maintaining CVS for FreeBSD?

[Stephen Montgomery-Smith]

On 01/03/2013 07:20 PM, Erich Dollansky wrote:

 So, why not wait until some more mirrors are available?
 
 One other problem people in 'developed' nations do not see exists. If -
 like me - you are located on a very remote location with a more or less
 random Internet connection, many servers become very impatient with the
 user and cut the connection as their values for time outs are simply
 too low.

There is a delivery method called CTM which originally meant CVSUP
through Mail.  It was originally meant for people with slow
connections, but now it is mainly used by a few people because they are
behind very strict firewalls that don't allow them access to the outside
world except email.

BUT for people who have bad internet connections, may I commend it as a
method of getting updates for FreeBSD.

I have recently upgraded it to include updates for the svn repositories.
 Yes, you will need to have a working svn on your system.  And you will
have to apply a patch to the existing ctm program to make it work (ctm
is in the base system).  But this has been working for several weeks
now, and I think it is getting to the point where it is stable.


___
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

Problems with cvs - docs and www

[Stephen Montgomery-Smith]

(Not sure if this is the right mailing list, but here goes.)

Last night I did a csup to retrieve the whole cvs repository.  I noticed
that huge numbers of files in doc and www have been deleted.  Is this
intentional, or is it the svn to cvs program not working properly?  And
if it is the latter, are there plans to restore it?

(No need to reply with change to svn - I am aware of that solution.
But I still want to know what happened to cvs.)
___
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: Problems with cvs - docs and www

[Stephen Montgomery-Smith]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/31/2012 11:58 AM, Glen Barber wrote:
 On Mon, Dec 31, 2012 at 11:49:06AM -0600, Stephen Montgomery-Smith
 wrote:
 (Not sure if this is the right mailing list, but here goes.)
 
 
 -doc@ is a better choice.

Thanks.  I thought of that moments after I sent my email.

 
 Last night I did a csup to retrieve the whole cvs repository.  I
 noticed that huge numbers of files in doc and www have been
 deleted.  Is this intentional, or is it the svn to cvs program
 not working properly?  And if it is the latter, are there plans
 to restore it?
 
 
 We are not exporting docs from SVN to CVS.  There are no plans to
 do so.

OK.  Actually that makes my life easier.  Thank you.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBAgAGBQJQ4dMOAAoJEC3xK9GaktgHSmsH/RJ4yXZdImTu6en1j47rM6y/
5epcnudi4snuE+GQQzAIhAz9y3HN6tDK178518pm0WGR8r21YujKkdTAvLqfEBwX
yVFkFzyBeowe+92cX5uW3UNuzWpyvtwObVR6ScECaf56X2S64LUkIR1hI+fLUzko
buhh4vH+PTzDoASTLxJPFdodNfU+eQHF61803+a8iypGTi6nUeVJSGzvOslWUaz6
UPH5FVCwYCjYxMwp/d4ZLg6kJ1QCJ30hrkwWp52SYVFu9xHAdvXGPzjwJWbd3kkM
rcFdSmTT2+TVTu9e+9+PyuYKSUvwYc37oX5LRjm0vi200tVhg6wskdKsyO2ov2A=
=o0L9
-END PGP SIGNATURE-
___
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: Does / Is anyone maintaining CVS for FreeBSD?

[Stephen Montgomery-Smith]

On 12/31/2012 03:40 PM, Alfred Perlstein wrote:
 On 12/31/12 12:40 PM, Chris H wrote:
 | I'm sorry, but the exporter scripts were always a stopgap.
 That's what I was afraid I would hear. Recently, I was informed by
 SF.NET,
 that my account would be upgraded, and all the projects I have, which all
 use CVS, would be upgraded to SVN (which renders them useless). When I
 asked why, they told me because CVS was so old. To which I stated:
 Indeed, CVS is _quite_ old, and so is TCP/IP. Yet no one can seem live
 without it.
 Sigh...
 IM(NS)HO; SVN is an inferior RCS created so Windows users wouldn't feel
 left out.
 Are there _any_ CVS servers/trunks/tree's left? If so, how _current_ are
 they?

 Thanks again for taking the time to reply, Chris.

 All the best.

 You still really haven't come forward with a concrete reason besides my
 workflow and my scripts.
 
 Svn is a *near* drop in replacement for CVS.
 
 If instead of complaining and taking up bandwidth on the lists about old
 tech, you instead asked about how to move your archaic setup forward
 then someone would likely step forward and lend you a hand.
 
 The project's goal is to support a large user base and the developers in
 a manner that works with our resources.  Supporting CVS (a 2nd gen VCS)
 while we have been on a 3rd gen (svn) and are finally looking into a 4th
 gen (git) is just unfair.
 
 If you took a few minutes you'd fine the svn command set intuitive and a
 simple switch over from CVS.

The reason I asked the original question about docs disappearing from
cvs is because I maintain the CTM delivery system.  I am in the process
of switching CTM from cvs to svn, and IM(NS)HO svn is much, much nicer
than cvs or cvsup.  I am really looking forward to not having to deal
with cvs any more.

Give svn a try.  My guess is that you will find it easier to work with
than you expect.

Stephen

___
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 You Using FreeBSD?

[Stephen Montgomery-Smith]

I use FreeBSD because it was the first Intel based unix I tried.  A 
friend of mine suggested I try FreeBSD instead of Linux.


More recently I have had to start using Linux because FreeBSD doesn't 
have very good laptop support.  (All I ask for is a way to configure the 
mouse pad so that I can switch off tap to click.)


My main application is to write my own mathematics code.  From time to 
time I try running it under both FreeBSD and Linux to see which is 
fastest.  It seems the two OS's take turns in which is fastest, 
depending upon which has had more recent development work done on it.


Another reason I am forced to use Linux is because I sometimes use 
Mathematica 8.  I haven't got this to work with Linux emulation under 
FreeBSD yet.


When I use Linux, I use Ubuntu.  I like very much how things just 
work.  For example, to use a flash drive, I just plug it in.  I am 
sure I could configure FreeBSD to do the same thing, but it just becomes 
easier to type mount_msdos /dev/da0s1 /tmp as root rather than climb 
the learning curve.


On the other hand Ubuntu recently switched their Window manager, and I 
hated it on their early versions.  They also offered gnome3, and it just 
wasn't working.  So I dare not go beyond Ubuntu 10.04, and I fear the 
day 10.04 becomes EOL.


Having started with FreeBSD before Linux, I feel I understand FreeBSD a 
lot better.


Stephen
___
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: Restricting users from certain privileges

[Stephen Montgomery-Smith]

On 04/28/2012 02:50 AM, Zenny wrote:

On Sat, Apr 28, 2012 at 9:38 AM, Daniel Branissda...@cs.huji.ac.il  wrote:


Hi:

I could not figure out how to restrict users or other users from certain
privileges to execute certain commands in FreeBSD/NanoBSD?

What I meant is I want to create a NanoBSD image in which there will be

an

additional user, say 'admin'. I need to give this new user (admin) some
privileges to run some root-can-only-execute commands, but not all (ACL
similar to the firmwares in adsl modems from ISPs).

I read Dru Lavingne's 'BSD Hacks' and Joseph Kong's 'Designing BSD
Rootkits' besides FreeBSD handbook, but I simply could not figure out.
Could anyone throw some light on this? Appreciate it!

Thanks!

/zenny


try sudo from ports, security/sudo

cheers,
danny



Thanks Daniel, but sudo gives all (not selective) root privileges to the
user (admin in my case). So this is not what I am trying to achieve in my
original post.


Try the security/super port.  It is easy to create very fine grained 
privileges to selected users.  (I am not saying that sudo cannot do 
this, but with super it is very easy.)


___
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: GENERIC make buildkernel error / fails - posix_fadvise

[Stephen Montgomery-Smith]

On 01/12/2012 09:11 PM, Garrett Cooper wrote:


+1. And it's faster yet when you can run parallel copies of rm on
different portions of the directory tree (e.g. xargs, find [..] -exec)
as rm is O(n).


I have always wondered about that!  I thought that the main bottleneck 
in rm -r might be deleting directories which are not in the disk 
cache, which then have to be copied from the disk.  Copying two 
different parts of the disk into cache - well it has to be done one at a 
time whether the jobs asking for the copy of the disk are going 
concurrently or consecutively.


And perhaps two instances of rm -r acting on different parts of the 
hard drive will cause disk thrashing, so that they might even slow each 
other down.


But this is all guess work on my part.

If I am wrong, and rm -r does work faster when working in parallel on 
different parts, then why doesn't someone write the rm command to fork 
copies of itself that work on different parts of large trees?


Stephen
___
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: Escaping from a jail with root privileges on the host

[Stephen Montgomery-Smith]

On 12/28/2011 02:58 AM, Marin Atanasov Nikolov wrote:

Hello,

Today I've managed to escape from a jail by accident and ended up with
root access to the host's filesystem.

Here's what I did:

  * Using ezjail for managing my jails
  * Verified in FreeBSD 9.0-BETA3 and 9.0-RC3
  * This works only when I use sudo, and cannot reproduce if I execute
everything as root

First, created a folder *inside* the jail and cd to it:

  host$ sudo ezjail-admin console jail-test

  jail-test# id
  uid=0(root) gid=0(wheel) groups=0(wheel),5(operator)

  jail-test# mkdir ~/jail-folder
  jail-test# cd ~/jail-folder

  jail-test# pwd
  /root/jail-folder

Then from the host machine I've moved this folder to the cwd.

host$ pwd
/usr/home/mra

host$ sudo mv /home/jails/jail-test/root/jail-folder .

And then here's where the jail ends up :)

  jail-test# pwd
  /usr/home/mra/jail-folder


From here on the Jail's root user has full root privileges to the

host's filesystem.

Not sure if it is sudo or jail issue, and would be nice if someone
with more experience can check this up :)

Regards,
Marin



This is rather fascinating.

I agree with the poster that the jail didn't really escape, but was 
sprung from the outside.


But more than that, I imagine it would be very hard to stop this without 
either completely rethinking how unix filesystems work, or adding 
significant overhead to the OS so that it checks every single mv 
command against all existing jails.


I think the warning in the man page 
http://svnweb.freebsd.org/base/head/usr.sbin/jail/jail.8?r1=221665r2=224286 
is a better way to go.


Stephen

___
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: FLAME - security advisories on the 23rd ? uncool idea is uncool

[Stephen Montgomery-Smith]

On 12/23/2011 10:07 AM, Damien Fleuriot wrote:

Hey up list,



Look, just a rant here.


Who in *HELL* thought it would be a cool idea to release no less than
FOUR security advisories today ?


After receiving the fifth security advisory in a few moments, you will 
get a Christmas message from the Security Advisory team, which will

both apologize and explain why these untimely advisories came today.

http://lists.freebsd.org/pipermail/freebsd-security-notifications/2011-December/thread.html

___
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: FLAME - security advisories on the 23rd ? uncool idea is uncool

[Stephen Montgomery-Smith]

On 12/23/2011 10:56 AM, Mike Tancsa wrote:


Also, the chroot issue has been public for some time along with sample
exploits. Same with BIND which was fixed some time ago.  Judgment call,
and I think they made the right call at least from my perspective.


It is this chroot issue that bothers me.  From my reading of the ftpd 
man page, if I have anonymous ftp to my server, it seems that I am using 
chroot with ftpd, and there is no way to stop this happening.


Am I correct, or have I missed something?  (I am hoping I missed something.)
___
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

Problems with cvs from cvs-repository

[Stephen Montgomery-Smith]

I see that a lot of RELENG_9 tags have been created in the last day or 
so.  So I thought I would get the sources in the following manner:


I downloaded the complete cvs repository using cvsup.  Then I ran the 
commands

env CVSROOT=/whereever-it-is/cvs cvs co -rRELENG_9 src
and nothing happened except the directory src was created.

However if I try cvsup with RELENG_9, it works just fine.

Is this something to do with svn to cvs conversion, and somehow 
something isn't set quite right?  Or did I completely mess up the commands?

___
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: Problems with cvs from cvs-repository

[Stephen Montgomery-Smith]

On 09/24/2011 03:08 PM, Stephen Montgomery-Smith wrote:

I see that a lot of RELENG_9 tags have been created in the last day or
so. So I thought I would get the sources in the following manner:

I downloaded the complete cvs repository using cvsup. Then I ran the
commands
env CVSROOT=/whereever-it-is/cvs cvs co -rRELENG_9 src
and nothing happened except the directory src was created.

However if I try cvsup with RELENG_9, it works just fine.

Is this something to do with svn to cvs conversion, and somehow
something isn't set quite right? Or did I completely mess up the commands?



Please completely ignore this message.  I was simply impatient and 
didn't let the command run for long enough to do anything.  Sorry for 
the noise.

___
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: Best way to switch from Linux to BSD

[Stephen Montgomery-Smith]

Jason Hsu wrote:

I've been trying to switch from Linux to BSD for my everyday computing (email, 
word processing, spreadsheets, etc.), but I couldn't get things to work 
properly.  I've been so spoiled by the quickness and user-friendliness of 
antiX/Swift Linux and Puppy Linux for so long.  I have a backlog of stuff to 
do, so I'm sticking to Linux for now as my main OS.  However, I might try BSD 
in VirtualBox and on my laptop.
   
I have to say that I am taking a bit of the opposite route.  I learned 
Unix on SunOS, and so when I tried i386 Unix's, FreeBSD wasn't that hard 
for me.  I have slowly learned quite a lot about its inner workings.  
From a system administrator's perspective, FreeBSD is pure delight.


But the desktop experience of Ubuntu is so easy, and it works so much 
out of the box that I am switching to Ubuntu for a lot of my everyday 
desktop needs.  So, for example, getting flash to work properly with 
firefox on amd64 is too much of a pain under FreeBSD.  And my new ASUS 
laptop has an elan touchpad, which Ubuntu could handle out of the box, 
but FreeBSD couldn't recognize its special features.


One place I do use my computer a lot is with floating point numerically 
intensive programming.  I find that FreeBSD and Unix take turns as to 
who does this the best.  As of today, FreeBSD is definitely winning.  So 
I will always keep both OS's on my computers.


Another thing I love about the ports system in FreeBSD is that you can 
compile the code yourself, switch on or off many of the features of that 
particular piece of software, but still have it play nice with the 
FreeBSD packaging system.  Maybe there is a similar thing I can do with 
Ubuntu, but I haven't figured it out yet.  And I'm not prepared to go 
another route like gentoo - what's the point when I already have FreeBSD.



___
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: Best way to switch from Linux to BSD

[Stephen Montgomery-Smith]

Michal Varga wrote:

On Tue, 2011-03-29 at 10:51 -0700, Matthew Fleming wrote:
   

On Tue, Mar 29, 2011 at 10:27 AM, Michal Vargavarga.mic...@gmail.com  wrote:
 

Here too. How is desktop support on FreeBSD lacking?
   

I realize a desktop means many things to many people, but the biggest
thing holding me back from using FreeBSD on a desktop is flash
support.  I spent a little time trying to follow online instructions
and I didn't get anything working.
 

Lack of Flash support - a proprietary closed exploit-ridden hellhole -
sorry, I mean - application - that's in no way tied to FreeBSD and
controlled by a legendarily uncompetent company that blantantly refuses
to release a FreeBSD version of this very fine and awesome rootkit (a
good decision that one can only support, so really, what's the issue) is
hardly something that could even remotely be FreeBSD's fault. I mean,
this is what we're talking about:

http://secunia.com/advisories/search/?search=adobe+flash

But even in a completely hypothetical scenario where Flash wouldn't be
the world's most famous never-ending exploit carnival in the entire
existence of the universe, how that makes FreeBSD less desktop friendly
or less desktop capable? Adobe decided to not release their software on
FreeBSD (again, thank you Adobe, that's a thousand less attack vectors
daily to worry about), but there is no issue with FreeBSD with regard to
that, isn't it? This isn't the case that FreeBSD broke the Flash (ok,
this isn't funny anymore), there was never any FreeBSD Flash in the
first place. So no FreeBSD issue exists, or at least I can't see it, or
maybe I simply don't get something here.

There is also no Microsoft Windows Management Console for FreeBSD, does
it make FreeBSD lacking, insufficient, or broken in some specific server
area?
   


1. Lack of good flash support is most definitely not FreeBSD's fault.  
But if you want easy to use flash support, you don't care who's fault it 
is, you just care where you can get it.
2. I have found i386 flash support works well on FreeBSD.  But on the 
amd64, my experience was that it was very flaky.  (But I do agree that 
Windows is also flaky.)
3. Whether or not the use wants the ability to install a proprietary 
closed exploit-ridden hellhole depends upon what they want.  If they 
want to go to movie web sites and view the latest trailers complete with 
all the flashy add ons, then FreeBSD is not the way to go.  Of course, 
if your idea of a good desktop experience is as a software development 
environment, or to write math papers in latex, or to check email with 
little to no risk of acquiring the latest virus, FreeBSD wins out hands 
down.


Stephen

___
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

Change in behavior to stat(1)

[Stephen Montgomery-Smith]

I had a little script that would remove broken links.  I used to do it 
like this:


if ! stat -L $link  /dev/null; then rm $link; fi

But recently (some time in February according to the CVS records) stat 
was changed so that stat -L would use lstat(2) if the link is broken.


So I had to change it to

if stat -L $link | awk '{print $3}' | grep l  /dev/null;
then rm $link; fi

but it is a lot less elegant.

What is the proper accepted way to remove broken links?

Stephen
___
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: Change in behavior to stat(1)

[Stephen Montgomery-Smith]

Jeremy Chadwick wrote:


Possibly you could use the example from the find(1) man page:

find -L /usr/ports/packages -type l -exec rm -- {} +
Delete all broken symbolic links in /usr/ports/packages.

(Note that the + on the end is not a typo, see the man page)


Brilliant!

Since this is *precisely* the purpose of my script, I think I will use 
this code instead,

___
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: ALPS GlidePoint not detected on dell inspiron

[Stephen Montgomery-Smith]

David DEMELIER wrote:

Hello,

A friend has a DELL Inspiron 1525 with an ALPS GlidePoint touchpad. We
have added hw.psm.synaptics_support=1 in his /boot/loader.conf but it
still detected as a standard ps2 mouse.

Looking at sys/dev/atkbdc/psm.c :
  461 { MOUSE_MODEL_GLIDEPOINT,   /* ALPS GlidePoint */
  462   0xc0, MOUSE_PS2_PACKETSIZE, enable_aglide },

I'm guessing if his touchpad has 0xc0 as model, how can I check this?

For the moment there is this in his dmesg:

psm0:PS/2 Mouse  irq 12 on atkbdc0

psm0: [GIANT-LOCKED]

psm0: [ITHREAD]

psm0: model GlidePoint, device ID 0

Cheers,


I had the same issues with an ALPS glidepoint on a Dell Inspiron 1525. 
I think it is different than a synaptics.  I don't know what problem you 
are trying to solve, but if you are trying to switch off the tapping 
the touchpad feature, I found an unusual solution two years ago: look 
at 
http://www.mavetju.org/mail/view_message.php?list=freebsd-mobileid=2760915

___
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: samba recplacement

[Stephen Montgomery-Smith]

Nenhum_de_Nos wrote:


On Sat, February 6, 2010 23:44, Eric wrote:

On 2/5/2010 9:22 PM, Nenhum_de_Nos wrote:

hail,

I've installed a recent 8-stable with gnome installed. I needed samba
and
noticed I have samba4-devel installed. but I can't manage to make it a
simple file server as I need. so how to change samba package at minimum
harm ?

do I need to reinstall all ? a simple make fetch in samba33 says I can't
as it conflicts with samba4 and some tbd-something (not in the machine
right now).

is there easy way ?

I'd really like to choose samba version ... I've found a thread in
gnome@
about this change (from late december). not a solution though.

thanks,

matheus


pretty sure samba 4 is not stable yet. i played with it and it didnt
work too well a few months ago. go back to the 3.x branch. thats easy to
config.


I think this way too, the problem is how to do it in the least painful
way. if I deinstall all samba stuff, gnome will fail to work ?

matheus


This is what I did:

go to /usr/ports/x11/gnome2; do make config; deselect the MAPI option.


___
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: samba recplacement

[Stephen Montgomery-Smith]

Nenhum_de_Nos wrote:


On Sun, February 7, 2010 00:43, Stephen Montgomery-Smith wrote:

Nenhum_de_Nos wrote:


On Sat, February 6, 2010 23:44, Eric wrote:

On 2/5/2010 9:22 PM, Nenhum_de_Nos wrote:

hail,

I've installed a recent 8-stable with gnome installed. I needed samba
and
noticed I have samba4-devel installed. but I can't manage to make it a
simple file server as I need. so how to change samba package at
minimum
harm ?

do I need to reinstall all ? a simple make fetch in samba33 says I
can't
as it conflicts with samba4 and some tbd-something (not in the machine
right now).

is there easy way ?

I'd really like to choose samba version ... I've found a thread in
gnome@
about this change (from late december). not a solution though.

thanks,

matheus


pretty sure samba 4 is not stable yet. i played with it and it didnt
work too well a few months ago. go back to the 3.x branch. thats easy
to
config.


I think this way too, the problem is how to do it in the least painful
way. if I deinstall all samba stuff, gnome will fail to work ?

matheus


This is what I did:

go to /usr/ports/x11/gnome2; do make config; deselect the MAPI option.


what I will loose in functionality ?


I don't know.  Some functions related to the mail client evolution.


I'd have to rebuild it all, right ?


I think if you just delete samba4-devel and its dependencies, then you 
can rebuild from there.




matheus



___
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: samba recplacement

[Stephen Montgomery-Smith]

Nenhum_de_Nos wrote:


On Sun, February 7, 2010 01:02, Stephen Montgomery-Smith wrote:

Nenhum_de_Nos wrote:


On Sun, February 7, 2010 00:43, Stephen Montgomery-Smith wrote:

Nenhum_de_Nos wrote:


On Sat, February 6, 2010 23:44, Eric wrote:

On 2/5/2010 9:22 PM, Nenhum_de_Nos wrote:

hail,

I've installed a recent 8-stable with gnome installed. I needed
samba
and
noticed I have samba4-devel installed. but I can't manage to make it
a
simple file server as I need. so how to change samba package at
minimum
harm ?

do I need to reinstall all ? a simple make fetch in samba33 says I
can't
as it conflicts with samba4 and some tbd-something (not in the
machine
right now).

is there easy way ?

I'd really like to choose samba version ... I've found a thread in
gnome@
about this change (from late december). not a solution though.

thanks,

matheus


pretty sure samba 4 is not stable yet. i played with it and it didnt
work too well a few months ago. go back to the 3.x branch. thats easy
to
config.


I think this way too, the problem is how to do it in the least painful
way. if I deinstall all samba stuff, gnome will fail to work ?

matheus


This is what I did:

go to /usr/ports/x11/gnome2; do make config; deselect the MAPI
option.


what I will loose in functionality ?


I don't know.  Some functions related to the mail client evolution.


if just evolution is affected, no problem for me.


I'd have to rebuild it all, right ?


I think if you just delete samba4-devel and its dependencies, then you
can rebuild from there.


yeah ... I'll need to rebuild ...

but I need samba3 for filesharing purposes :)


And you can install samba3 separately, just like I did.



___
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 Security Advisory FreeBSD-SA-10:01.bind

[Stephen Montgomery-Smith]

FreeBSD Security Advisories wrote:


I.   Background

BIND 9 is an implementation of the Domain Name System (DNS) protocols.
The named(8) daemon is an Internet Domain Name Server.

DNS Security Extensions (DNSSEC) provides data integrity, origin
authentication and authenticated denial of existence to resolvers.

II.  Problem Description

If a client requests DNSSEC records with the Checking Disabled (CD) flag
set, BIND may cache the unvalidated responses.  These responses may later
be returned to another client that has not set the CD flag.


How do I find out if my named server is using DNSSEC?  I am using the 
vanilla defaults with named on FreeBSD.


___
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: Signing Request

[Stephen Montgomery-Smith]

On Wed, 23 Sep 2009, Robert Noland wrote:


On Wed, 2009-09-23 at 11:40 -0400, J. Hellenthal wrote:

If you do not need to pgp/gpg sign email message to the lists please don't. I
know I probably don't have your pgp public key and a lot more users probably do
not either. Please use your best judgment.


http://www.freebsd.org/doc/pgpkeyring.txt

Frankly, I always sign messages, except that evolution / gpg support is
currently a bit broken...

robert.


Thank you and best regards.


I don't use PGP, but I don't see how it can affect me if someone else 
does.  I can still read the emails, so why should it bother me?


Stephen

___
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: Burning DVD with files4GB from console

[Stephen Montgomery-Smith]

David Kelly wrote:

On Thu, Dec 04, 2008 at 10:48:54AM +0100, Bartosz Stec wrote:
My backup script split filesystem dumps to files with size of 4,37 GB (4 
588 544 kB). It's just an optimal size to fill out DVDs. At this moment 
I have to burn them from windows via smb-link becuase I didn't manage to 
do this task from FreeBSD console due to 2GB/4GB filesize restrictions 
(growisofs).


Since when did FreeBSD (or growisofs) have a 2GB/4GB filesize limit? I
have burned 4.3GB DVDs several times.


I never had a problem writing huge files.  But I did have a problem 
subsequently reading it with Windows XP.  Maybe the file size 
restriction is a Windows thing.

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

Calling malloc from a signal handler

[Stephen Montgomery-Smith]

I notice that if you use malloc from within a signal handler on 
FreeBSD-6.x, that you can potentially trigger a recursive call error.


But this seems to have changed in FreeBSD-7.x.

Is it now permissible to call malloc from within a signal handler in 
FreeBSD-7.x?


If so, should the man page of sigaction(2) be upgraded to say this?

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

Re: Inspiron 1525 Hardware

[Stephen Montgomery-Smith]

Gavin Atkinson wrote:

On Thu, 2008-09-04 at 11:32 -0600, Dan Allen wrote:

On 4 Sep 2008, at 10:29 AM, Gavin Atkinson wrote:


This is supported by the iwn(4) driver in CURRENT, and it should be
quite easy to port the driver to 7-STABLE.  If you're interested in
reinstalling FreeBSD and testing a backported driver, I'm sure this  
can be sorted.
I am interested in doing this.  Please advise on how I can get these  
bits.


I've got hold of a laptop with the 4965 chipset in it, if nobody beats
me to it I'll have a go at backporting the driver.


I have a Dell Inspiron 1525 with the intel wireless ethernet.

The iwn driver in CURRENT works well.

The http://people.freebsd.org/~yongari/msk/msk.88E8040.patch patch for 
the 88E8040 simply doesn't work.  It is not because of lack of testing 
(which I have performed for Pyun who wrote the patch), but apparently 
because of lack of reliable documentation.  There is a driver for 
FreeBSD on the Marvell web site, which did work for me, but I am told it 
is unreliable.


I also have had a hard time getting the sound to work.  The oss port 
does work, but has a habit of freezing up.


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

Re: Inspiron 1525 Hardware

[Stephen Montgomery-Smith]

Carlos A. M. dos Santos wrote:


Did you try using Alexander Motin's new snd_hda patches? They are available at

 http://people.freebsd.org/~mav/



Thanks.  I hadn't tried them.  But they didn't work.  (I used the Sept 4 
patch on CURRENT.)


I could provide more diagnostics if anyone wants to work to make it work.

___
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

[Stephen Montgomery-Smith]

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.


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

Re: Scheduler in Various Docs

[Stephen Montgomery-Smith]

Jason C. Wells wrote:
The comments regarding SCHED_ULE and SCHED_4BSD are inconsistent with 
information found in the email archives.  LINT says ULE is experimental. 
The handbook doesn't mention ULE at all. The archives say ULE is the 
new recommended scheduler.


If ULE is in fact the current recommendation, then a few docs need to be 
updated.


To add to Jason's point - why does GENERIC still default to SCHED_4BSD? 
 Are there plans to change this before 7.0 is truly released?


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

Re: Scheduler in Various Docs

[Stephen Montgomery-Smith]

Jeremy Chadwick wrote:

On Sun, Jan 20, 2008 at 07:40:07PM +0100, TooMany Secrets wrote:

On 1/20/08, Stephen Montgomery-Smith [EMAIL PROTECTED] wrote:

Jason C. Wells wrote:

The comments regarding SCHED_ULE and SCHED_4BSD are inconsistent with
information found in the email archives.  LINT says ULE is experimental.
The handbook doesn't mention ULE at all. The archives say ULE is the
new recommended scheduler.

If ULE is in fact the current recommendation, then a few docs need to be
updated.

To add to Jason's point - why does GENERIC still default to SCHED_4BSD?
  Are there plans to change this before 7.0 is truly released?

Excuse me for my bad english...

This question was mentioned two or three months ago. The answer was
that in 7.1, after the ULE will be tested in 7.0, it will be the
defacto scheduler in FreeBSD. First, the scheduler need the best
benchark in the world; a few thousand users testing in real-life
situations on a daily basis.


This is correct.  There was a very large discussion on freebsd-current
(which would've been discussing 7.x at that point) about what scheduler
should be the default for RELENG_7 (4BSD or the new ULE (a.k.a.
SMP2)).  It was voted (note the quotes) that SCHED_4BSD should
remain the default until 7.1 was released, since if there turned out
to be a gigantic bug in the new scheduler, we wouldn't want people to
get bit by it (thus harming the stability reputation of -RELEASE and
-STABLE).  The 4BSD scheduler is still considered stable and has a
track record to prove it.

In a way, SCHED_ULE on 7.x is still considered experimental in the
sense that it needs lots of people testing it.  So far all the results
have been positive (unlike SCHED_ULE on 6.x and 5.x, which were very
broken -- hence the rewrite!).

If the OP wants to read the thread/discussion (it's long), I can dig up
a URL to it in the archives.


Thanks.  You both answered my question admirably.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: To 6.3 or to 7.0 that is the question?

[Stephen Montgomery-Smith]

Steven Hartland wrote:
With the announcement of 6.3 and with 7.0 looking like it wont be far 
behind I'd interested to hear what people thought of the relative

benefits of each where?

I know 7 has had a lot of work done on locking and ULE but are there
any other reasons to go for that instead of 6.3? Conversely are there
any reason which would point away from 7 such as stability issues?

   Regards
   Steve


I really like FreeBSD 7.x, except for one issue.  On my Dell Lattitude 
D800 laptop, xorg freezes the computer solid on starting or stopping. 
(But I guess I like the advantages of 7.x to the extent that I haven't 
gone back to 6.x).


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

FreeBSD 7.0 freezes with nvidia card

[Stephen Montgomery-Smith]

I have a Dell D800 Latitude laptop.  If I use FreeBSD 7.0, and xorg with 
the nv driver, when I exit X, sometimes it simply freezes.  I tried it 
with the vesa driver. and the problem didn't seem to happen, but the 
vesa driver is unable to get the 1680x1050 resolution of my monitor.


I sent a similar message a while back because I thought the ndis driver 
was also involved.  But I have since disabled ndis.  (However when ndis 
is on, the problem is worse.)


Any ideas?

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

Re: FreeBSD 7.0 freezes with nvidia card

[Stephen Montgomery-Smith]

David Booth wrote:

On Monday 24 December 2007, Stephen Montgomery-Smith wrote:

I have a Dell D800 Latitude laptop.  If I use FreeBSD 7.0, and xorg
with the nv driver, when I exit X, sometimes it simply freezes.  I
tried it with the vesa driver. and the problem didn't seem to
happen, but the vesa driver is unable to get the 1680x1050
resolution of my monitor.

I sent a similar message a while back because I thought the ndis
driver was also involved.  But I have since disabled ndis. 
(However when ndis is on, the problem is worse.)


Any ideas?

Stephen
___


Have you tried the Nvidia driver from ports/x11?  It works well for me 
on my Dell I8600.


That is what I was originally using.  But that also froze.  I switched 
to nv in hopes that the problem would go away.


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

Re: Some processes stay active after killing its PID

[Stephen Montgomery-Smith]

On Tue, 27 Nov 2007, Honza Holakovsky wrote:


Well, didn't know that, /bin/kill -9 wdfs_PID works, great

Thanks a lot, after your advice I read an article about csh built-in
commands, never heard of it from any fbsd handbook...


I am completely baffled why this worked.  Why would /bin/kill -9 work when 
the built in csh kill -9 wouldn't?


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

Re: Is it O.K. to use the 7.0 ports tree on 6.3 ?

[Stephen Montgomery-Smith]

Pete French wrote:

I have a set of machines running 7.0 and a set running 6.3 which I
would like to use the same ports on. I was under the impression that
there was only one ports tree, so is it safe to simply untar the
ports.tgz file from 7.0 on the 6.3 machines, rename INDEX-7 to INDEX-6
and install away, or are there more subtle differences to tran the unwary ?

cheers,

-pcf.


I think that they are the same, except INDEX-6 and INDEX-7 differ.  So 
do your tar-untaring, and then do make fetchindex on the 6.3 machine(s).

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

FBSD-7-B2 Freeze

[Stephen Montgomery-Smith]

I am experiencing fairly consistent system freezes which seem to 
coincide with using the ndis driver and nvidia driver at the same time. 
 I had worst problems using the nvidia binary driver, but I did also 
experience a freeze one time with the xorg nv driver, which I am now 
using.  Sometimes the wireless card works extremely slowly when I am 
using the nvidia driver.


I have a Dell Latitude D800.  I enclose dmesg.  Any advice on how to 
either further diagnose, or fix the problem will be welcome.


Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-BETA2 #0: Sat Nov 10 12:48:18 CST 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) M processor 1.70GHz (1698.56-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x6d6  Stepping = 6

Features=0xafe9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE
  Features2=0x180EST,TM2
real memory  = 536535040 (511 MB)
avail memory = 511066112 (487 MB)
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: DELL CPi R   on motherboard
acpi0: [ITHREAD]
acpi0: reservation of 0, 9fc00 (3) failed
acpi0: reservation of 10, 1fef (3) failed
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0
cpu0: ACPI CPU on acpi0
est0: Enhanced SpeedStep Frequency Control on cpu0
p4tcc0: CPU Frequency Thermal Control on cpu0
acpi_acad0: AC Adapter on acpi0
battery0: ACPI Control Method Battery on acpi0
battery1: ACPI Control Method Battery on acpi0
acpi_lid0: Control Method Lid Switch on acpi0
acpi_button0: Power Button on acpi0
acpi_button1: Sleep Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci_link1: BIOS IRQ 11 for 0.31.INTB is invalid
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
vgapci0: VGA-compatible display mem 
0xfc00-0xfcff,0xd000-0xdfff irq 11 at device 0.0 on pci1
uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xbf80-0xbf9f 
irq 11 at device 29.0 on pci0

uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xbf40-0xbf5f 
irq 11 at device 29.1 on pci0

uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1
uhub1: 2 ports with 2 removable, self powered
uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xbf20-0xbf3f 
irq 11 at device 29.2 on pci0

uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb2
uhub2: 2 ports with 2 removable, self powered
ehci0: Intel 82801DB/L/M (ICH4) USB 2.0 controller mem 
0xf4fffc00-0xf4ff irq 11 at device 29.7 on pci0

ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb3: EHCI version 1.0
usb3: companion controllers, 2 ports each: usb0 usb1 usb2
usb3: Intel 82801DB/L/M (ICH4) USB 2.0 controller on ehci0
usb3: USB revision 2.0
uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb3
uhub3: 6 ports with 6 removable, self powered
pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0
pci_link1: BIOS IRQ 11 for 2.3.INTA is invalid
pci2: ACPI PCI bus on pcib2
pci0:2:0:0: bad VPD cksum, remain 14
bge0: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x3001 
mem 0xfaff-0xfaff irq 11 at device 0.0 on pci2

miibus0: MII bus on bge0
brgphy0: BCM5705 10/100/1000baseTX PHY PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto

bge0: Ethernet address: 00:0f:1f:21:d5:92
bge0: [ITHREAD]
cbb0: TI7510 PCI-CardBus Bridge at device 1.0 on pci2
cardbus0: CardBus bus on cbb0
pccard0: 16-bit PCCard bus on cbb0
cbb0: [ITHREAD]
cbb1: TI7610 PCI-CardBus Bridge irq 11 at device 1.1 on pci2
cardbus1: CardBus bus on cbb1
pccard1: 16-bit PCCard bus on cbb1
cbb1: [ITHREAD]
fwohci0: 1394 Open Host Controller Interface mem 
0xfafef800-0xfafe,0xfafe8000-0xfafebfff irq 11 at device 1.2 on pci2

fwohci0: [FILTER]
fwohci0: OHCI version 1.10 (ROM=0)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 48:4f:c0:00:36:a9:44:a1
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: IEEE1394(FireWire) bus on fwohci0
fwe0: Ethernet over FireWire on firewire0
if_fwe0: Fake Ethernet address: 4a:4f:c0:a9:44:a1

Trouble running Mathematica

[Stephen Montgomery-Smith]

When I run Mathematica 5.2 on FreeBSD RELENG_7 I get the following message:

/usr/local/mma52/SystemFiles/Kernel/Binaries/Linux/MathKernel: error 
while loading shared libraries: /usr/lib/librt.so.1: ELF file OS ABI invalid


It worked fine on RELENG_6.  Furthermore Mathematica 5.0 seems to work 
fine on RELENG_7.


I have the usual set of linux emulation libraries installed (what is 
pulled in by building the acroread7 port.)


Any ideas?  I'm really not sure how to go about diagnosing this apart 
from running ldd, which doesn't seem to tell me much more.


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

Re: Trouble running Mathematica

[Stephen Montgomery-Smith]

On Sat, Nov 10, 2007 at 04:38:56PM +0100, Lothar Braun wrote:
 Stephen Montgomery-Smith wrote:
  When I run Mathematica 5.2 on FreeBSD RELENG_7 I get the following message:
  
  /usr/local/mma52/SystemFiles/Kernel/Binaries/Linux/MathKernel: error
  while loading shared libraries: /usr/lib/librt.so.1: ELF file OS ABI
  invalid
 
 I got a similar message, when i tried to run skype_devel. The solution
 was to run
 
 sysctl compat.linux.osrelease=2.4.20
 
 and put compat.linux.osrelease=2.4.20 into my /etc/sysctl.conf. This
 may help you, too.
 
 Regards,
   Lothar

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

Re: Trouble running Mathematica

[Stephen Montgomery-Smith]

On Sat, Nov 10, 2007 at 05:10:45PM +0100, Tijl Coosemans wrote:
 On Saturday 10 November 2007 16:16:40 Stephen Montgomery-Smith wrote:
  When I run Mathematica 5.2 on FreeBSD RELENG_7 I get the following
  message:
  
  /usr/local/mma52/SystemFiles/Kernel/Binaries/Linux/MathKernel: error
  while loading shared libraries: /usr/lib/librt.so.1: ELF file OS ABI
  invalid
 
 If you have linux_base-fc4, creating the following link should fix it:
 
 ln -s ../../lib/librt-2.3.6.so /compat/linux/usr/lib/librt.so.1
 
 This is something that should have been added to the linux_base-fc4
 package long time ago, but I guess it got lost. CC'ed to maintainer.
 The same error appears when you run /compat/linux/bin/ls.

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

Re: Missing libstdc++.so.6 for openoffice in stable

[Stephen Montgomery-Smith]

Brian Josefsen wrote:

Hello all

I installed the openoffice package 
ftp://ooopackages.good-day.net/pub/OpenOffice.org/FreeBSD/2.3.0/i386/FreeBSD6/OOo_2.3.0_FreeBSD62Intel_install_da.tbz 
yesterday, now when i try to execute openoffice.org-2.3.0 it complaints 
about libstdc++.so.6 is missing. As far as i remember libstdc++.so.6 is 
part of GCC 4.2 and therefore first availible in -current. Now, am i a 
moron and got everything wrong, or is this an error by whoever built 
this package?


I simply can't allow myself 2 days to build this one.

--
Best regards
Brian Josefsen


I had the same problem.  I fixed it by installing the gcc42 package.

It seems to me that openoffice should have gcc42 as a LIB_DEPENDS as 
well as a BUILD_DEPENDS.


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

Re: named.conf restored to hint zone for the root by default

[Stephen Montgomery-Smith]

Jo Rhett wrote:

On Aug 3, 2007, at 6:12 PM, John Merryweather Cooper wrote:

I would appreciate it if the personal attacks ceased.


There was no personal attack there.  I never called him names or made 
any remark about his lifestyle or anything else.  I did say that he 
isn't paying attention to the people who disagree with him, but that is 
an observable fact.



As an observer
with no ax to grind on this issue, it is apparent that slaving the root
zone is technically possible, but not necessarily good policy.


Actually, it has been argued/shown-by-those-who-would-know that while 
you can do it, it won't work in a stable manner once everyone starts 
doing it.  The protocol itself is not designed for many unknown 
associations, really.



It would
be nice if those arguing against slaving the root zone would articulate
the specific effects on top-tier servers and quantify them.


This has been done, both here and on the DNS Operations list where this 
is actually topical.  Repeatedly.  This topic is dead, horse beaten to 
crap, except that Doug Barton really loves this idea and won't listen to 
why it won't work, and why it shouldn't be done, and why he shouldn't 
have done it that way.   He just keeps coming back and saying now lets 
talk about this some more...


As another person with no ax to grind, my sense is that this was a 
professional albeit heated discussion.  Briefly, it seems to me that 
Doug introduced changes with no prior discussion - this was his only 
real fault, and for this he has appropriately apologized.


The result of the heated discussion was that the slave zone thingy was 
turned into an option rather than the default.  As far as I am 
concerned, this is an entirely satisfactory resolution, and shows that 
the discussions had their desired effect.  That the discussions became a 
little heated merely shows that we are human beings.  The main thing is 
that everyone was upfront and honest about their agendas, and that the 
matter was resolved in the appropriate technical manner.


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

Re: Bug in less version 406.

[Stephen Montgomery-Smith]

David Wolfskill wrote:

On Thu, Aug 02, 2007 at 12:14:37PM -0500, Ted Hatfield wrote:

Can someone verify this bug for me please and suggest a fix.

Error description:

Using less -E or more to display a file that is less than a full page, 
while then displaying a nonexistent file causes a segmentation fault.


I was able to recrerate the symptoms using more, but not less -E.


For example on a newly built system you can

less -E /etc/group bogusfile


This will display the file ending with

/etc/group (file 1 of 2) (END) - Next: bogusfile

when you press space or return it gives

Segmentation fault: 11


I did:

g1-18(6.2-S)[1] cd /tmp
g1-18(6.2-S)[2] head /etc/group group
g1-18(6.2-S)[3] less -E group fubar

and didn't see a problem

Using more(1), I got:

g1-18(6.2-S)[5] more group fubar
# $FreeBSD: src/etc/group,v 1.32.2.1 2006/03/06 22:23:10 rwatson Exp $
#
wheel:*:0:root,david
daemon:*:1:
kmem:*:2:
sys:*:3:
tty:*:4:
operator:*:5:root
mail:*:6:
bin:*:7:
Segmentation fault (core dumped)
g1-18(6.2-S)[6] 


For me this is one of those intermittent faults.  Sometimes it 
segfaults, and sometimes it doesn't.


Stephen

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

thread error in pthread [was Re: [Bsd-sharp-list] Problem with x11-toolkits/gnome-sharp20 port]

[Stephen Montgomery-Smith]

Tom McLaughlin wrote:

On Fri, 2007-07-27 at 21:25 -0500, Stephen Montgomery-Smith wrote:


.Email deleted as it is irrelevant


Please include the FreeBSD version when reporting a problem. :)  This is
a -CURRENT issue only due to libthr.  A fix is here but has not been
committed to libthr:

http://lists.freebsd.org/pipermail/freebsd-current/2007-July/075454.html


Exactly the same error also appears in 
lib/libpthread/thread/thr_private.h, and in stable.


If it would help, I can submit a PR.

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

Re: updating xorg-libraries 7.2 to 7.2.1

[Stephen Montgomery-Smith]

Matthew Seaman wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Josh Paetzel wrote:

Shaun Branden wrote:



xorg 7.2 was installed on this system from scratch, ie no ports to start
with.



For right now if you want portupgrade to do anything with xorg you
need to export XORG_UPGRADE


Creating the /usr/X11R6 - /usr/local symlink is necessary, even on a
system with xorg 7.2 installed from scratch.  The presence of that
symlink will stop the xorg-libraries port whinging at you.  


There are a couple of other bits that need twiddling in the default
system, and a very handy way of getting them all to happen is by 
running mergebase.sh.  On a completely virgin newly instaleld system,

with /usr/ports populated, but no ports yet installed you may need
to:

mkdir /usr/X11R6

to give that script something to chew on, and then just:

sh /usr/ports/Tools/scripts/mergebase.sh

before proceeding to install whatever ports you want.

Cheers,

Matthew


My experience is that simply having the symlink /usr/X11R6-/usr/local 
is totally sufficient.


However it seems to me that what the port building procedure should now 
do is the following:


* if /usr/X11R6 exists as a directory, it should issue an error message 
like it does now.


* if /usr/X11R6 doesn't yet exist, silently create the symlink.

This will mirror how it used to behave, in that if /usr/local or 
/usr/X11R6 did not exist, they would be created as needed.


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

Re: updating xorg-libraries 7.2 to 7.2.1

[Stephen Montgomery-Smith]

On Sun, 27 May 2007, Matthew Seaman wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Stephen Montgomery-Smith wrote:

Matthew Seaman wrote:



Josh Paetzel wrote:

Shaun Branden wrote:



xorg 7.2 was installed on this system from scratch, ie no ports to
start
with.

sh /usr/ports/Tools/scripts/mergebase.sh

before proceeding to install whatever ports you want.



My experience is that simply having the symlink /usr/X11R6-/usr/local
is totally sufficient.

However it seems to me that what the port building procedure should now
do is the following:

* if /usr/X11R6 exists as a directory, it should issue an error message
like it does now.

* if /usr/X11R6 doesn't yet exist, silently create the symlink.

This will mirror how it used to behave, in that if /usr/local or
/usr/X11R6 did not exist, they would be created as needed.


Oh, agreed to that.  However, there are still more changes needed
beyond that:

Stopping the system running periodic jobs from /usr/X11R6/etc/periodic

Stopping the system running startup scripts from /usr/X11R6/etc/rc.d

Stopping the system searching for manpages from /usr/X11R6/man

The last is fairly trivial, but realise that the first two mean that
with the /usr/X11R6 - /usr/local link in place all
/usr/local/etc/periodic jobs would get run twice, and even more
importantly all /usr/local/etc/rc.d/ startup scripts would also run
twice.

Until there are new system releases incorporating the necessary changes
in /etc/defaults/rc.conf and /etc/defaults/periodic.conf it will be
necessary to override some of the default settings.  In /etc/rc.conf:

  local_startup=/usr/local/etc/rc.d

In /etc/periodic.conf:

  local_periodic=/usr/local/etc/periodic

and for completeness sake, comment out the 'X11R6' lines in
/etc/manpath.conf


I think that the easiest way (i.e. least disruption) is to add to each of 
the X11R6 scripts a test at their beginning to see if X11R6 is a symlink 
to /usr/local, and have the scripts do nothing if this is the case.  This 
way people who haven't yet switched to xorg-7.2 will not be disadvantaged 
in any way.  (I don't think simply testing to see if X11R6 is a symlink by 
itself will be sufficient because I bet that some people already have 
symlinks like X11R6-X11 or such like.)


Also, the last change you propose vis a vis man pages, is that actually 
necessary - I would have thought that the overhead in searching both local 
and X11R6 would be fairly negligable.


Stephen

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

Re: Don't buy AMD products (was Re: Xorg and ATI card query.)

[Stephen Montgomery-Smith]

Scott Long wrote:


Stephen Montgomery-Smith wrote:


Sean Bryant wrote:


Andrew Reilly wrote:


On Tue, 13 Mar 2007 14:17:00 -0800 (PST)
Doug Ambrisko [EMAIL PROTECTED] wrote:
 


One thing that is a plus with nv is that X has some support for it,
whereas, the newer ati cards have no support :-(  I was a fan of 
ati since it was easier to get support.  Now I'm starting to lean 
towards Nvidia :-(





Does anyone know if there are *any* contemporary graphics cards
that have 3D acceleration supported by some flavour of
open-source x.org?  Doesn't have to be a super-fast 'leet gamer
system to be better than a non-accelerated frame buffer.

Matrox used to have a reputation for goodness (I used to have a
G400 or the like), but it's been a long time...

(I'm currently using a lowish-end NVidia card under the x.org nv
driver, but it has issues (of which no 3D accel is but one...)

Cheers,

  




Try the 'vesa' xorg driver. It may not be fancy or all that 
accelerated but it works quite well. I have an nvidia card and 
cannot get it to work for the life of me. the drive attached, but 
nothing happens after that. It might be the fact that I have a PCI 
express card. But the vesa driver is working just fine for me.




I had a PCI-X nvidia card 



PCI-X?  Or PCI Express?  PCI-X is not the same thing.



It isn't?  I guess this shows my ignorance!  Well, I think it is the PCI 
express - the one that is supposed to be super fast, and replace AGP.


Stephen

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

Re: Don't buy AMD products (was Re: Xorg and ATI card query.)

[Stephen Montgomery-Smith]

On Tue, 13 Mar 2007, Doug Ambrisko wrote:


Kip Macy writes:
| Please be very careful. The only real alternative (Intel comes and
| goes) is Nvidia whose driver is binary-only for i386 (no amd64
| support) and has a history for being notoriously buggy. I only buy ATI
| because of the problems I keep seeing people have with the Nvidia
| driver. I have a friend who has basically abandoned his dual-head
| Nvidia card due to recurring issues.

One thing that is a plus with nv is that X has some support for it,
whereas, the newer ati cards have no support :-(  I was a fan of ati
since it was easier to get support.  Now I'm starting to lean towards
Nvidia :-(


I used to find nvidia drivers very buggy, but the recent drivers have 
greatly impressed me.


Stephen

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

ncurses

[Stephen Montgomery-Smith]

In the cvs repository, there has appeared src/lib/ncurses, which seems 
to be a copy of lib/libncurses.  Is this meant to be?



--

Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: (Seemingly) Spontaneous rebooting

[Stephen Montgomery-Smith]

Joe Holden wrote:

Ma wrote:

I have almost the same reboots on my server. :( And it may reboot 
serval times a day. I'd like to know how to get crash dumps? What is 
added in your rc.conf?


--
Ma Jie


Hi, I used the rc.conf values as set out in rc,conf(5)

[EMAIL PROTECTED] grep crash /etc/defaults/rc.conf
dumpdev=NO# Device to crashdump to (device name, AUTO, or 
NO).

dumpdir=/var/crash# Directory where crash dumps are to be stored

I set dumpdev to my swap partition, although nothing got dumped, 
although I did upgrade it to -CURRENT as i'd exhausted everything else, 
and its not crashed since, not wishing to flame/troll/whatever, but 6.x 
seems to have a fair few issues.



I posted a dump of a crash I had with a recent RELENG_6 computer a few 
weeks ago.  It was one of those fairly useless dumps where the program 
counter seems to be completely meaningless.


I also had similar behavior about a year ago, which seemed to be 
produced by a bug that is now fixed.  (That one I could make it happen 
at will by running a multithreaded program on a 4 processor system, and 
top -s0 at the same time.)  I do recall the nature of the crash is 
that sometimes it produced dumps, and sometimes it didn't.  And when it 
did they were useless.


The crash seemed always to be with a page fault.  I experienced it on 
two computers, both with SMP.


Anyway, what I am saying is that all these people might be seeing a 
genuine problem that by its very nature does not produce meaningful dumps.


If this problem is real, perhaps one solution is to put out release 6.2 
fairly soon, then lots of people will try it and experience this 
problem.  Then you guys will have lots of evidence to work with.  Then 
when you fix it, put out release 6.3 much sooner than otherwise 
anticipated.  (I should add that my wife accuses me of having humor that 
is too dry.)


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

RELENG_6 panic

[Stephen Montgomery-Smith]

I thought I would add another panic report.  This seemed to coincide 
with an upgrade I made today.  So if it is a software problem it 
happened between Nov 21 and Dec 5.  It happened on two computers that I 
upgraded, so I suspect its not a hardware problem.  One of the computers 
had crash dumps switched on.  The panic happened right after I issued a 
reboot.  The crash dump doesn't look very useful, but here it is anyway.


Script started on Wed Dec  6 21:23:26 2006
hub2# cd /usr/obj-old/usr/src/sys/HUB2/

hub2# kgdb kernel.debug /var/crash/vmcore.197

[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: 
Undefined symbol ps_pglobal_lookup]
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.

Unread portion of the kernel message buffer:
118Dec  6 19:49:28 hub2 syslogd: exiting on signal 15


Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 07
fault virtual address   = 0x4
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc06a50de
stack pointer   = 0x28:0xecfc9acc
frame pointer   = 0x28:0xecfc9ad4
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 18221 (sshd)
trap number = 12
panic: page fault
cpuid = 3
Uptime: 22h22m38s
Dumping 3071 MB (2 chunks)
  chunk 0: 1MB (158 pages) ... ok
  chunk 1: 3071MB (786126 pages) 3055 3039 3023 3007 2991 2975 2959 2943 2927 
2911 2895 2879 2863 2847 2831 2815 2799 2783 2767 2751 2735 2719 2703 2687 2671 
2655 2639 2623 2607 2591 2575 2559 2543 2527 2511 2495 2479 2463 2447 2431 2415 
2399 2383 2367 2351 2335 2319 2303 2287 2271 2255 2239 2223 2207 2191 2175 2159 
2143 2127 2111 2095 2079 2063 2047 2031 2015 1999 1983 1967 1951 1935 1919 1903 
1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 
1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 
1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 
1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 
831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 
511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 
191 175 159 143 127 111 95 79 63 47 31 15

#0  doadump () at pcpu.h:165
warning: Source file is more recent than executable.

165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) backtrace
#0  doadump () at pcpu.h:165
#1  0xc067470e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2  0xc0674a35 in panic (fmt=0xc08be305 %s) at 
/usr/src/sys/kern/kern_shutdown.c:565
#3  0xc086885c in trap_fatal (frame=0xecfc9a8c, eva=4) at 
/usr/src/sys/i386/i386/trap.c:837
#4  0xc086859b in trap_pfault (frame=0xecfc9a8c, usermode=0, eva=4) at 
/usr/src/sys/i386/i386/trap.c:745
#5  0xc08681d5 in trap (frame=
  {tf_fs = -1064501240, tf_es = 40, tf_ds = -1063583704, tf_edi = 
-930277248, tf_esi = -930277248, tf_ebp = -318989612, tf_isp = -318989640, 
tf_ebx = -932463616, tf_edx = -1063572696, tf_ecx = -914699648, tf_eax = 0, 
tf_trapno = 12, tf_err = 0, tf_eip = -1066774306, tf_cs = 32, tf_eflags = 
66182, tf_esp = -932463616, tf_ss = -930277248}) at 
/usr/src/sys/i386/i386/trap.c:435
#6  0xc085432a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7  0xc06a50de in ttymodem (tp=0xc86bbc00, flag=-1063572696) at 
/usr/src/sys/kern/tty.c:1666
#8  0xc06a98f6 in ptcclose (dev=0x0, flags=7, fmt=8192, td=0xc97aca80) at 
linedisc.h:136
#9  0xc064a2d7 in giant_close (dev=0xcd891200, fflag=7, devtype=8192, 
td=0xc97aca80) at /usr/src/sys/kern/kern_conf.c:284
#10 0xc06274a6 in devfs_close (ap=0xecfc9b7c) at 
/usr/src/sys/fs/devfs/devfs_vnops.c:357
#11 0xc087a050 in VOP_CLOSE_APV (vop=0x0, a=0xc09b2b28) at vnode_if.c:426
#12 0xc06da572 in vn_close (vp=0xc88d1880, flags=7, file_cred=0x0, 
td=0xc97aca80) at vnode_if.h:227
#13 0xc06db4e2 in vn_closefile (fp=0xcd896558, td=0xc97aca80) at 
/usr/src/sys/kern/vfs_vnops.c:867
#14 0xc06274e7 in devfs_close_f (fp=0xcd896558, td=0xc97aca80) at 
/usr/src/sys/fs/devfs/devfs_vnops.c:369
#15 0xc0654550 in fdrop_locked (fp=0xcd896558, td=0xc97aca80) at file.h:295
#16 0xc065449d in fdrop (fp=0xcd896558, td=0xc97aca80) at 
/usr/src/sys/kern/kern_descrip.c:2134
#17 0xc0652a3b in closef (fp=0xcd896558, td=0xc97aca80) at 
/usr/src/sys/kern/kern_descrip.c:1954
#18 0xc064fb99 in close (td=0xc97aca80, uap=0x0) at 
/usr/src/sys/kern/kern_descrip.c:1012
#19 0xc0868ba3 in syscall (frame=
  {tf_fs = -2009726917, tf_es = 

Panic

[Stephen Montgomery-Smith]

I just had a kernel panic.  This happened seconds after I started a 
reboot using alt-ctl-del, at about the time just after it it said it was 
writing the entropy file.


Here is the kernel config file, the results of the dump, and dmesg.  Do 
you want anything else?  I hope this info helps.


include GENERIC
ident HUB2
nooption INET6
options SMP
device  atapicam
makeoptions DEBUG=-g


hub2# cd /usr/obj/usr/src/sys/HUB2/
hub2# kgdb kernel.debug /var/crash/vmcore.196
[GDB will not be able to debug user-mode threads: 
/usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup]

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.

Unread portion of the kernel message buffer:
118.
118.


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x24
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc06acdc8
stack pointer   = 0x28:0xeadd7ae0
frame pointer   = 0x28:0xeadd7c68
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 479 (mountd)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 17h48m47s
Dumping 3071 MB (2 chunks)
  chunk 0: 1MB (158 pages) ... ok
  chunk 1: 3071MB (786126 pages) 3055 3039 3023 3007 2991 2975 2959 
2943 2927 2911 2895 2879 2863 2847 2831 2815 2799 2783 2767 2751 2735 
2719 2703 2687 2671 2655 2639 2623 2607 2591 2575 2559 2543 2527 2511 
2495 2479 2463 2447 2431 2415 2399 2383 2367 2351 2335 2319 2303 2287 
2271 2255 2239 2223 2207 2191 2175 2159 2143 2127 2111 2095 2079 2063 
2047 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 
1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 
1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 
1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 
1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 
911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 
623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 
335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 
31 15


#0  doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) list 0xc06acdc8
Function 0xc06acdc8 not defined.
(kgdb) list *0xc06acdc8
0xc06acdc8 is in unp_connect (/usr/src/sys/kern/uipc_usrreq.c:992).
987 goto bad2;
988 }
989 unp = sotounpcb(so);
990 unp2 = sotounpcb(so2);
991 unp3 = sotounpcb(so3);
992 if (unp2-unp_addr != NULL) {
993 bcopy(unp2-unp_addr, sa, 
unp2-unp_addr-sun_len);

994 unp3-unp_addr = (struct sockaddr_un *) sa;
995 sa = NULL;
996 }
(kgdb) backtrace
#0  doadump () at pcpu.h:165
#1  0xc0668736 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2  0xc0668a5d in panic (fmt=0xc08ae2d2 %s)
at /usr/src/sys/kern/kern_shutdown.c:565
#3  0xc085895c in trap_fatal (frame=0xeadd7aa0, eva=36)
at /usr/src/sys/i386/i386/trap.c:836
#4  0xc085869b in trap_pfault (frame=0xeadd7aa0, usermode=0, eva=36)
at /usr/src/sys/i386/i386/trap.c:744
#5  0xc08582d5 in trap (frame=
  {tf_fs = -814350328, tf_es = -354615256, tf_ds = -1066794968, 
tf_edi = 0, tf_esi = -926606416, tf_ebp = -354583448, tf_isp = 
-354583860, tf_ebx = -928231144, tf_edx = -927683016, tf_ecx = 4, tf_eax 
= -814325048, tf_trapno = 12, tf_err = 0, tf_eip = -1066742328, tf_cs = 
32, tf_eflags = 66178, tf_esp = -926077568, tf_ss = -927683016}) at 
/usr/src/sys/i386/i386/trap.c:434

#6  0xc08452ea in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7  0xc06acdc8 in unp_connect (so=0xc8cc1858, nam=0xcef36b60, td=0xc883f480)
at /usr/src/sys/kern/uipc_usrreq.c:991
#8  0xc06ab308 in uipc_connect (so=0xc8cc1858, nam=0xcef36b60, 
td=0xc883f480)

at /usr/src/sys/kern/uipc_usrreq.c:232
#9  0xc06a295e in soconnect (so=0xc8cc1858, nam=0xcef36b60, td=0xc883f480)
at /usr/src/sys/kern/uipc_socket.c:558
#10 0xc06a82c8 in kern_connect (td=0xc883f480, fd=3, sa=0xcef36b60)
at /usr/src/sys/kern/uipc_syscalls.c:536
---Type return to continue, or q return to quit---
#11 0xc06a822f in connect (td=0xc883f480, uap=0xeadd7d04)
at /usr/src/sys/kern/uipc_syscalls.c:505
#12 0xc0858ca3 in syscall (frame=
  {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 1, tf_esi = 
134598656, tf_ebp 

Re: MySQL and default memory limits (mysqld: Out of memory)

[Stephen Montgomery-Smith]

Mike Jakubik wrote:

Mathieu Arnold wrote:


+-Le 09/07/2006 14:25 -0700, Darren Pilgrim a dit :
| Mathieu Arnold wrote:
| [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't
| appear in sysctl.
| | Gotta love namespace collisions.

Well, in fact, most of the tunables do have a read only sysctl so that
people don't have to search the code for the value it has/takes :-)
Not this one though :-)
  



Exactly, its nice being able to see the current values. How else can i 
see what the values are set to?


The commands limit and limits (one of them is a csh only command) will 
tell you (although they might be set lower for a particular user via 
/etc/login.conf, or for a particular process, but that's unlikely).


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

Re: Still getting 'calcru: runtime went backwards'

[Stephen Montgomery-Smith]

Mike Jakubik wrote:

John Baldwin wrote:

That is partly because when you run top it queries the resource usage 
of the various processes via fill_kinfo_proc().  When you don't run 
top, no one is asking for the resource usage numbers, so the kernel 
doesn't waste time calculating them.


  



Right, also running ps has the same effect. But why do these messages 
occur?


In both cases your errors are for a long-running kernel process that's 
been up since boot.  What's the uptime on your box?


  



Not sure what the uptime was, this box is not in production yet so i 
shut it off regularly. I would guess under an hour.


I used to be able to get these predictably on FreeBSD 5, except then it 
could actually cause a panic.  If you run top -s 0 (as root) you can 
get these errors arriving at a spectacular rate.



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

dmesg seg faults

[Stephen Montgomery-Smith]

My video card spits out rather weird messages to the kernel message 
buffer.  This is only an annoyance, except it causes dmesg to seg fault. 
 I have some very simple possible fixes at

http://www.freebsd.org/cgi/query-pr.cgi?pr=93841

It is nothing crucial but it would be nice if a fix was submitted soonish.

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

Re: freeBSD 5.5 Prerelease ( 5.4 stable )

[Stephen Montgomery-Smith]

Jon Holstrom wrote:

any one know the date to get 5.4 stable ?
i am not able to find the date to CVsup 5.4 stable
as 5.5 is vary slow  is to buggy



You might try stable-6.x, which in my opinion is really fine.  My sense 
is that it actually runs a little faster than 5.x.






- Original Message - From: Jon Holstrom [EMAIL PROTECTED]
To: freebsd-stable@freebsd.org
Sent: Sunday, February 05, 2006 5:04 PM
Subject: freeBSD 5.5 Prerelease ( 5.4 stable )


Hello Group

CVSuped a 5.4 release box 2 days ago ( was going for 5-stable )
CVS server gave me 5.5 prerelease
two days later everything is 100 % installed

had to run pkg_deinstall on gnome-2-10
after running portupgrade to install gnome-2.12


run down on PC i worked with

Compaq 5003US PIII 866 , 370 pingrid
384 megs of ram ( 1 stick of PC 133, 256 RAM, 1 stick of PC 133, 128 RAM )
40 gig Maxtor ATA 100
onboard Intel 810 chipset
3Com networkcard


___
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]




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

Re: Problem with memory stick

[Stephen Montgomery-Smith]

Giorgos Kapetanakis wrote:

On Sat, February 4, 2006 3:45 am, Stephen Montgomery-Smith wrote:


I have a Crucial 1GB USB 2.0 Gizmo memory stick.  It does work, but not
without its problems.

When I insert it into the USB port, the kernel spits out a large number
of bad looking messages - I'll copy them below.  /dev/da0 is created,
but no /dev/da0s1 is created.  If I then do mount_msdos /dev/da0 /mnt
it gives an appropriate error message, but then /dev/da0s1 is
mysteriously created.  At this point mount_msdos /dev/da0s1 /mnt works
just right, and it is ready to use.

I just get the feeling that it is not quite working how it should be.  I
am using a fairly recent RELENG_6 (maybe two weeks old).



Check your kernel, maybe you are using the ehci driver for USB 2.0
support, which is under development and buggy. Also take a look at
ehci(4).


I was.  But when I added nodevice ehci to my kernel, the memory stick
still malfunctioned in exactly the same way.

Here is my kernel and dmesg.

include GENERIC
ident   LAPTOP2
nooption INET6
device  atapicam
nodeviceehci


Copyright (c) 1992-2005 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.0-STABLE #1: Sat Feb  4 11:51:18 CST 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP2
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) M processor 1.70GHz (1698.56-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x6d6  Stepping = 6

Features=0xafe9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE
  Features2=0x180EST,TM2
real memory  = 536535040 (511 MB)
avail memory = 511483904 (487 MB)
npx0: [FAST]
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: DELL CPi R   on motherboard
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0
cpu0: ACPI CPU on acpi0
acpi_throttle0: ACPI CPU Throttling on cpu0
acpi_acad0: AC Adapter on acpi0
battery0: ACPI Control Method Battery on acpi0
battery1: ACPI Control Method Battery on acpi0
acpi_lid0: Control Method Lid Switch on acpi0
acpi_button0: Power Button on acpi0
acpi_button1: Sleep Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci_link1: BIOS IRQ 11 for 0.31.INTB is invalid
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
nvidia0: GeForce FX Go5200 mem
0xfc00-0xfcff,0xd000-0xdfff irq 11 at device 0.0 on pci1
nvidia0: [GIANT-LOCKED]
uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xbf80-0xbf9f
irq 11 at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xbf40-0xbf5f
irq 11 at device 29.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xbf20-0xbf3f
irq 11 at device 29.2 on pci0
uhci2: [GIANT-LOCKED]
usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
pci0: serial bus, USB at device 29.7 (no driver attached)
pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0
pci_link1: BIOS IRQ 11 for 2.3.INTA is invalid
pci2: ACPI PCI bus on pcib2
bge0: Broadcom BCM5705M Gigabit Ethernet, ASIC rev. 0x3001 mem
0xfaff-0xfaff irq 11 at device 0.0 on pci2
miibus0: MII bus on bge0
brgphy0: BCM5705 10/100/1000baseTX PHY on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,
1000baseTX-FDX, auto
bge0: Ethernet address: 00:0f:1f:21:d5:92
cbb0: PCI-CardBus Bridge at device 1.0 on pci2
cardbus0: CardBus bus on cbb0
pccard0: 16-bit PCCard bus on cbb0
cbb1: PCI-CardBus Bridge irq 11 at device 1.1 on pci2
cardbus1: CardBus bus on cbb1
pccard1: 16-bit PCCard bus on cbb1
fwohci0: 1394 Open Host Controller Interface mem
0xfafef800-0xfafe,0xfafe8000-0xfafebfff irq 11 at device 1.2 on pci2
fwohci0: OHCI version 1.10 (ROM=0)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 48:4f:c0:00:36:a9:44:a1
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: IEEE1394(FireWire) bus on fwohci0
fwe0: Ethernet over FireWire on firewire0
if_fwe0: Fake Ethernet address: 4a:4f:c0:a9:44:a1
fwe0: Ethernet address: 4a:4f:c0:a9:44:a1
fwe0: if_start running deferred for Giant
sbp0: SBP-2/SCSI over FireWire on firewire0
fwohci0: Initiate bus reset
fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
firewire0: 1

Problem with memory stick

[Stephen Montgomery-Smith]

I have a Crucial 1GB USB 2.0 Gizmo memory stick.  It does work, but not 
without its problems.


When I insert it into the USB port, the kernel spits out a large number 
of bad looking messages - I'll copy them below.  /dev/da0 is created, 
but no /dev/da0s1 is created.  If I then do mount_msdos /dev/da0 /mnt 
it gives an appropriate error message, but then /dev/da0s1 is 
mysteriously created.  At this point mount_msdos /dev/da0s1 /mnt works 
just right, and it is ready to use.


I just get the feeling that it is not quite working how it should be.  I 
am using a fairly recent RELENG_6 (maybe two weeks old).


Here are the messages from dmesg.

umass0: USB Flash Disk, rev 2.00/2.00, addr 2
da0 at umass-sim0 bus 0 target 0 lun 0
da0: CRUCIAL USB Flash Disk 2.00 Removable Direct Access SCSI-2 device
da0: 40.000MB/s transfers
da0: Attempt to query device size failed: UNIT ATTENTION, Not ready to 
ready change,

(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retries Exhausted
Opened disk da0 - 6
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retries Exhausted
Opened disk da0 - 6
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition

Re: X.org 6.9 doesn't work with NVidia 7800 GTX (fwd)

[Stephen Montgomery-Smith]

Mike O'Brien wrote:

I sent this to freebsd-x11 and didn't hear a peep back,
so I'm widening the net.

I'm running FreeBSD 6-STABLE, cvsupped as of last night.  I upgraded
the ports collection to X.org 6.9 at the same time.  Under the X
that ships with 6-RELEASE, in the ISO image, and under X.org 6.9,
the symptoms are the same.

The hardware is an Athlon 4400+ CPU on an Asus motherboard and an
NVIDIA 7800 GTX video card.

I'm not running the NVidia FreeBSD driver (yet), preferring to see
the VESA work first before stirring the pot.  If I run X -probeonly,
I get a message that module fbdev cannot be found.  This message
is, however, almost unreadable because the probing of the video
card causes the console contrast to drop almost to zero.  The room
has to be almost pitch-black before the remaining dim text can be
read.  I have to reboot the machine to make the console brightness
and contrast normal again.

Any takers on either of these problems?

Mike O'Brien


It might be worth trying the nvidia drivers even if VESA isn't working. 
 My personal experience with the very recent FreeBSD nvidia drivers is 
that they are awesome.


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

Re: compat 5x libraries missnig after restart

[Stephen Montgomery-Smith]

Ion-Mihai Tetcu wrote:

On Tue, 27 Dec 2005 11:25:39 -0600
Stephen Montgomery-Smith [EMAIL PROTECTED] wrote:



Doug Barton wrote:


Add the following to /etc/rc.conf.local:

compat5x_enable=yes

And it would probably help if you watched the messages printed to
the console as the system boots.


And you should also have read the message that came when you
installed the port - you know, the one that immediately scrolled off
the top of the screen.  And you should also have checked
ports/UPDATING - oops, scratch that last piece of advice.

Seriously, I consider my self lucky, not superior, that I caught this 
change and didn't face the same problems as the OP. 



You mean you've read those mails with [HEADS-UP] pre-pended to
subj. line ?


The only HEADS-UP message I saw was Proposed patch to update 
misc/compat5x to rc.d-style boot script.  This message had neither a 
HEADS-UP prepended to it, nor did the content have any explicit 
meantion of compat-xx_enable=YES.




I hope you guys fix this feature before RELEASE-6.1, otherwise the
mailing lists are going to be full of this issue.


There's nothing to fix and yes, it's a feature (which will be probably
referenced in the release notes).


Having it referenced in the release notes is going to help.

But why not put
compat_xx_enable=YES

in /etc/defaults/rc.conf?

Also, how about explaining this in pkg_descr as well?

I do agree with many posters that it is somewhat counterintuitive to 
need to put something in /etc/rc.conf in order to get these compatxx 
ports to work.  (And personally don't see a reason for it - why would 
anyone install these ports if they didn't intend for them to be 
enabled.)  I can see why those very much immersed in FreeBSD think this 
is a good idea (perhaps for consistencies sake).  But I also think that 
the way it is now, it is going to trip up a lot of the more naive 
FreeBSD users.  At the very least it needs to be documented in as many 
places as possible.


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

Re: compat 5x libraries missnig after restart

[Stephen Montgomery-Smith]

Doug Barton wrote:

Add the following to /etc/rc.conf.local:

compat5x_enable=yes

And it would probably help if you watched the messages printed to the
console as the system boots.


And you should also have read the message that came when you installed 
the port - you know, the one that immediately scrolled off the top of 
the screen.  And you should also have checked ports/UPDATING - oops, 
scratch that last piece of advice.


Seriously, I consider my self lucky, not superior, that I caught this 
change and didn't face the same problems as the OP.  I hope you guys fix 
this feature before RELEASE-6.1, otherwise the mailing lists are going 
to be full of this issue.


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

Re: Copying kernel and OS

[Stephen Montgomery-Smith]

Jack Raats wrote:

I've two machines running FreeBSD 6.0-STABLE.
One very fast machine and one very very slow machine. On the fast 
machine I can compile a new kernel and OS very quickly and easily.
Is it possible to transfer the compile world and kernel to the slow 
machine. If yes whart directories etc... do i have to transfer.


Jack


I do something like this.  I build on the fast machine, and then use NFS 
to allow the slow machine to access /usr/src and /usr/obj.  I have found 
that it is important to preserve the names of the directories, so that 
they are also called /usr/src and /usr/obj on the slow machine.  Then I 
just do mergemaster, make installworld, make installkernel (in the 
appropriate order) on the slow machine, and it works like a charm.


The entries in fstab are like this:
hub2:/usr/obj/usr/objnfs rw,bg,noauto0   0
hub2:/usr/src/usr/srcnfs rw,bg,noauto0   0
where hub2 is the name of the fast machine.

In /etc/exports on hub2 I have something like this
/usr -maproot=root -alldirs -network 10.0.0.0 -mask 255.255.255.0
(here 10.0.0.0 is the IP addresses of my LAN)

and in /etc/rc.conf on hub2 I have some lines like
nfs_server_enable=YES
rpcbind_enable=YES

Then on the slow machine I simply type
mount /usr/src
mount /usr/obj

--

Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FreeBSD unstable on Dell 1750 using SMP?

[Stephen Montgomery-Smith]

Dan Charrois wrote:

It actually may be a comfort, since perhaps HTT is related to the  
culprit.  Since the last crash, about a month ago, I disabled HTT,  both 
in the kernel as well in the BIOS.  So as far as I know, it's  
completely been disabled (and the boot messages and top only show 2  
CPUs).  And I haven't had the system go down for nearly a month now.


I don't know if it is related, but I used to have random reboots on a 
dual Xeon system with HTT enabled.  It happened when I ran a CPU 
intensive threaded program at the same time as top - running top -s0 
(which you have to do as root) could usually kill the machine in seconds 
if not minutes.


All I can tell you is that with FreeBSD 6.0 the problem disappeared.

Well not totally - I still get a bunch of harmless calcru negative 
messages, although I don't know if it is actually related to the boot 
problems I used to have with FreeBSD 5.4, because I get the calcru 
backwards messages even with HTT disabled.


Anyway, if you are in the mood to try it out, you might like to try 
re-enabling HTT, starting up whatever process you usually use (I'm 
guessing it is MySQL), and then run top -s0.  If you get a crash soon 
after that, you have the same problem I had.


Let me also add that these crashes usually did not trigger a crash dump 
(I had dumpon set), and when it did the resulting dump looked rather 
corrupted.


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

Jerky keyboard and mouse

[Stephen Montgomery-Smith]

I recently upgraded from stable-6 of Nov 4 to stable-6 of today on my 
Dell Latitude D800 Laptop, and suddenly the response of the touchpad 
mouse and keyboard was bery bad.  In particular, when I type about 1 in 
10 key presses simply do not register.  I ended up going back to the Nov 
4 stable-6, which fixed the problem.


Any ideas?  I am happy to provide any details you may need.

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

kernel: calcru: runtime went backwards

[Stephen Montgomery-Smith]

This is on a recent FreeBSD-6.0 stable SMP machine.

As root, run top -s0.  Then, at the same time run this program:

#include pthread.h
#define D (110)
void *thread(void *n) {
  int i;
  double array[D];
  for (i=0;iD;i++) array[i] = i;
}
int main() {
  void *i;
  pthread_t tid;
  while (1) {
pthread_create(tid,NULL,thread,i);
pthread_join(tid,i);
  }
}

Let this program run for about a minute.  Then kill this program.

At this point, I sometimes get some calcru messages from the kernel.

(This is not a contrived situation - this happens much more frequently 
than this sample program when I run programs with threaded fftw3 calls - 
I suspect that it throws off the cpu times shown by top.)


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

three button mouse issues

[Stephen Montgomery-Smith]

My laptop has two mice - the touchpad and a usb mouse.

I would like the touchpad moused to run with the -3 flag and the usb 
moused to run without -3.  But I can only get neither or both to run 
with -3 by the appropriate settings in /etc/rc.conf.


Any ideas?  (Apart from manually killing and restarting one of the 
moused processes?)


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

Re: Atheros (ath0) no RX traffic

[Stephen Montgomery-Smith]

Richard Arends wrote:

Hello,

Today I upgraded my laptop from 5-STABLE to 6-STABLE. After the
upgrade, my wireless is not working anymore.


You are doing better than me.  I try this:
ifconfig ath0 wepkey 12345
and get
ifconfig: SIOCS80211: Invalid argument

(Actually maybe that is happening to you as well, but since you are 
setting ifconfig_ath0 from within rc.conf, you might be missing this 
error message as it flies by in your start up.)


I get this error on other wireless cards as well.

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

Re: Atheros (ath0) no RX traffic

[Stephen Montgomery-Smith]

Николай Мирин wrote:
If you do not build kernel modules there are several things to include 
in 6.0 kernel when
you migrate from 5.4. The reason for the error in your case is probably 
missing wlan_wep device.


#5.4
device  wlan# 802.11 support
device  ath
device  ath_hal

#6.0
device  wlan# 802.11 support
device  wlan_wep
device  ath
device  ath_hal
device  ath_rate_onoe




And actually, I had to change rc.conf line for my ath card a little bit.
For some reason in 6.0 it doesn't work without wepkey number specified.

in 5.4 it was:
ifconfig_ath0=inet 192.168.0.99 ssid MirinNET channel 1 wep wepkey 
0x0 authmode open


in 6.0 it became
ifconfig_ath0=inet 192.168.0.99 ssid MirinNET channel 1 wep wepkey 
0x authmode open weptxkey 1



-Nikolay


Thank you.  That fixed it.

Stephen

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

Re: kernel: calcru: runtime went backwards

[Stephen Montgomery-Smith]

Giovanni P. Tirloni wrote:


Try this,

 http://www.freebsd.org/doc/en/books/faq/book.html#CALCRU-NEGATIVE


Thank you.  I must admit that I missed this.  Unfortunately all the 
suggestions in this FAQ seem to be out of date - none of the suggested 
sysctls or kernel config options seem to apply to FreeBSD 6.


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

Well done with FreeBSD 6.0

[Stephen Montgomery-Smith]

I just upgraded from FreeBSD-5.4 to FreeBSD-6.0 stable.  It really went 
very smoothly.  Well done to all concerned.


A few things that could make it a little easier:

1.  I have a habit of doing the mergemaster stuff in a slightly 
different order.  Any chance of updating pwd_mkdb and cap_mkdb in 
FreeBSD-5.4 to the FreeBSD-6 version?


2.  In UPDATING, remind people to switch off the nvidia_load stuff in 
/boot/loader.conf (and any other exernally created modules), before 
first rebooting to the new kernel.


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

DMA errors

[Stephen Montgomery-Smith]

I found these messages on my computer, which is running a very recent 
RELENG_5.  Is this bad?  Does it indicate that the disk is failing?


Nov  3 07:35:48 cauchy kernel: ad4: FAILURE - READ_DMA
status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=145908831
Nov  3 07:35:51 cauchy kernel: ad4: FAILURE - READ_DMA
status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=145908863
Nov  3 07:35:55 cauchy kernel: ad4: FAILURE - READ_DMA
status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=145908895
Nov  3 07:35:59 cauchy kernel: ad4: FAILURE - READ_DMA
status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=145908895

--

Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen

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

Problem with thernet card and dhclient

[Stephen Montgomery-Smith]

My computer running a very recent FreeBSD release 5 is connected to the 
internet with 3Com 3c980C Fast Etherlink XL to a cable modem connected 
to Mediacom.  I connect with the command dhclient xl0.


The problem I have is that every so often the mediacom connection goes 
down, and when it comes up again, the computer seems unable to connect 
with the outside world.  Yet if I do killall dhclient;dhclient xl0 it 
happily connects sufficiently well to get itself an IP address from the 
mediacom dhcp server, but it does not seem able to pass any other kind 
of internet info, e.g. ping, nameserver, ssh, etc.


However rebooting the computer completely solves the problem.

It is as if the IP software gets stuck in some weird mode, and seems 
unable to get out of it.


Anyone got any ideas?  I'll provide more details about the system if 
that will help.


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

Re: Xorg monopolizes CPU after switching away with KVM

[Stephen Montgomery-Smith]

Darren David wrote:

Hi all-


So I've just encountered a new issue ( for me ) with Xorg, and i'm 
having a heck of a time tracking down the source and/or the actual 
nature of the issue. When i switch to another computer using my KVM, 
Xorg immediately begins to monopolize the CPU, heading up to 95% 
utilization. When i switch back to my machine, my USB keyboard works, 
but by USB mouse is unfunctioning. I have to force quit Xorg and restart 
to restore peace to the land.


Now, this didn't exist on 5.3. I'm running FreeBSD 5.4-STABLE, and 
xorg-6.8.2 and gnome2-2.10.1 from ports. I get no info in the logs 
either. I've searched the archives on this, but it's difficult to figure 
out exactly /what/ to search on to match this problem. No love on the 
xorg list either.


Any thoughts are greatly appreciated.


Regards,
darren david


It sounds like the symptoms I had when I tried to run an nvidia card on 
my Tyan motherboard with the nvidia drivers.  (And I waited for hours to 
see if it would stop.)  I bet that it is something that the video card 
is doing, maybe it is trying probe your CRT to see what kind it is, or 
something like that.


(This is all pure speculation on my part, so I don't know.)


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

Re: Problems with PCI-express video card

[Stephen Montgomery-Smith]

Stephen Montgomery-Smith wrote:
I have a nvidia PCI-express 6600 video card on an Intel SE7525GP2 
motherboard.  I am running a fairly recent version of RELENG_5.


I am having great difficulty getting the video card to work.  On an 
older version of Xorg it would try to use the vesa driver.  It did put 
up some video, but it was illegible.


Just in case anyone else had this problem - intel just announced an 
update version of the BIOS for this motherboard.  Now the video card 
works wonderfully with the nvidia drivers.


Best, Stephen

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

How to set polling for printer upon startup

[Stephen Montgomery-Smith]

My printer doesn't work very well unless I type
lpcontrol -p
What is the correct way to make this happen when the computer first 
boots up - is there some setting in device.hints or something I can put 
in the kernel config so that it defaults to this?


Thanks, Stephen

--

Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen
___
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 not running HTT

[Stephen Montgomery-Smith]

Steven Hartland wrote:

Have a read /usr/src/UPDATING it explains.



It should be in /usr/src/UPDATING, but I don't see it there myself.

I got bitten by the same problem.  The other guy who gave
ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-05:09.htt.asc
provided the right answer, but it should be also mentioned in UPDATING.




I have several boxes that I have upgraded from 5.3 to 5.4 and has stopped
using the HTT virtal CPU's. This have been going on for a while. the
oldest is dated 20050519 and the latest is yesterday.

Is there something that I have missed? Been using same configs for 5.3
without any problems.






This e.mail is private and confidential between Multiplay (UK) Ltd. and 
the person or entity to whom it is addressed. In the event of 
misdirection, the recipient is prohibited from using, copying, printing 
or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission 
please telephone (023) 8024 3137

or return the E.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]




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

releng 5 panic (again)

[Stephen Montgomery-Smith]

Please help me!

I know that I am getting few responses to my emails - I am guessing that 
my situation is difficult.  If you could offer any ideas how to help 
with further diagnostics.


I am regularly getting panics with instruction pointer equal to 
0xc0611c69.  I am not able to get any dumps - the dumpon directive is 
simply ignored.


(I did get one dump (for some reason), but that was with a kernel that 
was not made with config -g, and new kernels made afterwards seem 
significantly different, despite having exactly the same size.)


The code at this instruction pointer is

(kgdb) list *0xc0611c69
0xc0611c69 is in fill_kinfo_thread (../../../kern/kern_proc.c:748).
743 }
744
745 kg = td-td_ksegrp;
746
747 /* things in the KSE GROUP */
748 kp-ki_estcpu = kg-kg_estcpu;
749 kp-ki_slptime = kg-kg_slptime;
750 kp-ki_pri.pri_user = kg-kg_user_pri;
751 kp-ki_pri.pri_class = kg-kg_pri_class;
752

so I'm guessing that kp is not correct.

Because of the consistency of the instruction pointer value from panic 
to panic, I really am thinking that this is not a hardware issue.


I will try any reasonable test you guys have for me.  Right now I am 
switching off HTT to see if that is the issue.  This is a dual Xeon system.


I am willing to provide a copy of the program that I'm guessing is 
causing the problem.  It is a multithreaded program that is very CPU 
instensive, although most of the inners of the code are from the fftw3 port.


One interesting thing about this program is that when I run it, top says 
that about 45% CPU is being used (which with 4 logical CPU's means that 
almost 2 CPU's are being used), but that actual program is registered at 
running with about 80% CPU time (which I am guessing means 0.8 of one 
CPU is being used).  It seems to me that there is some disparity in the 
accounting.


Maybe it is a problem with the math/fftw3 code.  But is still shouldn't 
causes crashes.


Please help me.  I am sure that this is a difficult problem, but I just 
don't know how to provide you any further decent diagnostic information.


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

Re: releng 5 panic (again)

[Stephen Montgomery-Smith]

Mike Tancsa wrote:

At 04:03 PM 25/05/2005, Stephen Montgomery-Smith wrote:

I will try any reasonable test you guys have for me.  Right now I am 
switching off HTT to see if that is the issue.  This is a dual Xeon 
system.



The SCHED_4BSD doesnt do anything with HTT and in fact might hurt 
performance. If you are using ULE, there are several known bugs and its 
not recommended that you use it.  So in short, turn off HTT in your BIOS 
on RELENG_5.




I am using the 4BSD scheduler, but I am really seeing some advantage 
with it.  When it is switched off, multiply running programs really do 
seem to run a little slower.


But I'll switch off HTT for now.

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

panic on RELENG_5

[Stephen Montgomery-Smith]

I have a dual Xeon with HTT enabled.  Many months ago I had frequent 
problems with panics, which since dissappeared, until very recently. 
Now after dong a very recent upgrade of RELENG_5, the problem is back 
again.  For whatever reason, I could not get savecore to work with my 
twe raid 0 had drives.  So I put in another hard drive, just for getting 
dumps, and now I actually have a dump!!!.


I did a config -g after the fact - I hope that is OK.

Here is what I got.  Can you guys get anything out of this?

hub2# kgdb kernel.debug /var/crash/vmcore.84
[GDB will not be able to debug user-mode threads: 
/usr/lib/libthread_db.so: Unde

fined symbol ps_pglobal_lookup]
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.
#0  0xc0617b0e in doadump ()
(kgdb) backtrace
#0  0xc0617b0e in doadump ()
#1  0xc0618187 in boot ()
#2  0xc06184ad in panic ()
#3  0xc07a9310 in trap_fatal ()
#4  0xc07a8a89 in trap ()
#5  0xc079679a in calltrap ()
#6  0xe92a0018 in ?? ()
#7  0xc0600010 in exit1 ()
#8  0xc0612151 in sysctl_out_proc ()
#9  0xc06128f0 in sysctl_kern_proc ()
#10 0xc06202b7 in sysctl_root ()
#11 0xc06204a4 in userland_sysctl ()
#12 0xc0620355 in __sysctl ()
#13 0xc07a964b in syscall ()
#14 0xc07967ef in Xint0x80_syscall ()
#15 0x0805002f in ?? ()
#16 0x281a002f in ?? ()
#17 0xbfbf002f in ?? ()
#18 0x0003 in ?? ()
#19 0xbfbfe9cc in ?? ()
#20 0xbfbfe998 in ?? ()
#21 0xe92add64 in ?? ()
#22 0x281a3f2c in ?? ()
---Type return to continue, or q return to quit---
#23 0x080e in ?? ()
#24 0xbfbfea00 in ?? ()
#25 0x00ca in ?? ()
#26 0x0016 in ?? ()
#27 0x0002 in ?? ()
#28 0x28129d2f in ?? ()
#29 0x001f in ?? ()
#30 0x0296 in ?? ()
#31 0xbfbfe95c in ?? ()
#32 0x002f in ?? ()
#33 0x in ?? ()
#34 0x in ?? ()
#35 0x in ?? ()
#36 0x in ?? ()
#37 0x5e79 in ?? ()
#38 0xc72b654c in ?? ()
#39 0xc459f000 in ?? ()
#40 0xe92adaa8 in ?? ()
#41 0xe92ada90 in ?? ()
#42 0xc38a0480 in ?? ()
#43 0xc0628803 in sched_switch ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic on RELENG_5

[Stephen Montgomery-Smith]

Kris Kennaway wrote:



Something is still wrong, because no source code references are listed
here (i.e. this is what you'd get if you ran gdb on kernel, not
kernel.dump).



I think that it was because I did the config -g after the fact.  Now I 
get something like this.  I hope that this is useful.


(By after the fact I mean - I did a config -g HUB2 with the destdir 
the same as the destdir that I had used to make the original kernel.  I 
hoped to save some time on the resulting make depend  make.  But it 
looks like it simply did not make a lot of the labels.  This is still an 
after the fact kernel creation, except I used a brand new destdir.  If 
this isn't right, I can install this new kernel and wait for yet another 
panic.)



Script started on Tue May 24 15:54:07 2005
hub2# kgdb kernel.debug /var/crash/vmcore.84
[GDB will not be able to debug user-mode threads: 
/usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup]

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.
#0  doadump () at pcpu.h:160
160 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) backtrace
#0  doadump () at pcpu.h:160
#1  0xc0618187 in boot (howto=260) at ../../../kern/kern_shutdown.c:410
#2  0xc06184ad in panic (fmt=0xc07f1834 %s) at 
../../../kern/kern_shutdown.c:566
#3  0xc07a9310 in trap_fatal (frame=0xe92ad884, eva=44) at 
../../../i386/i386/trap.c:817

#4  0xc07a8a89 in trap (frame=
  {tf_fs = -383123432, tf_es = -1067450352, tf_ds = -383123440, 
tf_edi = -1003533220, tf_esi = -383067908, tf_ebp = -383067932, tf_isp = 
-383067984, tf_ebx = 4, tf_edx = 0, tf_ecx = -953280640, tf_eax = 6, 
tf_trapno = 12, tf_err = 0, tf_eip = -1067377559, tf_cs = 8, tf_eflags = 
65559, tf_esp = 327361, tf_ss = 0}) at ../../../i386/i386/trap.c:255

#5  0xc079679a in calltrap () at ../../../i386/i386/exception.s:140
#6  0xe92a0018 in ?? ()
#7  0xc0600010 in exit1 (td=0xc72e1780, rv=0) at 
../../../kern/kern_exit.c:189
#8  0xc0612151 in sysctl_out_proc (p=0xc42f4c5c, req=0xe92adc08, 
flags=0) at ../../../kern/kern_proc.c:887
#9  0xc06128f0 in sysctl_kern_proc (oidp=0x0, arg1=0x0, arg2=0, 
req=0xe92adc08) at ../../../kern/kern_proc.c:1076
#10 0xc06202b7 in sysctl_root (oidp=0x0, arg1=0x0, arg2=0, 
req=0xe92adc08) at ../../../kern/kern_sysctl.c:1225
#11 0xc06204a4 in userland_sysctl (td=0x0, name=0xe92adc74, namelen=3, 
old=0xe92adc08, oldlenp=0xbfbfe9cc, inkernel=0, new=0x0, newlen=0, 
retval=0xe92adc70) at ../../../kern/kern_sysctl.c:1322
#12 0xc0620355 in __sysctl (td=0xc459f000, uap=0xe92add04) at 
../../../kern/kern_sysctl.c:1259

#13 0xc07a964b in syscall (frame=
  {tf_fs = 134545455, tf_es = 672792623, tf_ds = -1078001617, 
tf_edi = 3, tf_esi = -1077941812, tf_ebp = -1077941864, tf_isp = 
-383066780, tf_ebx = 672808748, tf_edx = 135135232, tf_ecx = 
-1077941760, tf_eax = 202, tf_trapno = 22, tf_err = 2, tf_eip = 
672308527, tf_cs = 31, tf_eflags = 662, tf_esp = -1077941924, tf_ss = 
47}) at ../../../i386/i386/trap.c:1009

#14 0xc07967ef in Xint0x80_syscall () at ../../../i386/i386/exception.s:201
#15 0x0805002f in ?? ()
#16 0x281a002f in ?? ()
#17 0xbfbf002f in ?? ()
#18 0x0003 in ?? ()
#19 0xbfbfe9cc in ?? ()
#20 0xbfbfe998 in ?? ()
---Type return to continue, or q return to quit---
#21 0xe92add64 in ?? ()
#22 0x281a3f2c in ?? ()
#23 0x080e in ?? ()
#24 0xbfbfea00 in ?? ()
#25 0x00ca in ?? ()
#26 0x0016 in ?? ()
#27 0x0002 in ?? ()
#28 0x28129d2f in ?? ()
#29 0x001f in ?? ()
#30 0x0296 in ?? ()
#31 0xbfbfe95c in ?? ()
#32 0x002f in ?? ()
#33 0x in ?? ()
#34 0x in ?? ()
#35 0x in ?? ()
#36 0x in ?? ()
#37 0x5e79 in ?? ()
#38 0xc72b654c in ?? ()
#39 0xc459f000 in ?? ()
#40 0xe92adaa8 in ?? ()
#41 0xe92ada90 in ?? ()
#42 0xc38a0480 in ?? ()
#43 0xc0628803 in sched_switch (td=0xbfbfe9cc, newtd=0x281a3f2c, 
flags=Cannot access memory at address 0xbfbfe9a8

) at ../../../kern/sched_4bsd.c:881
Previous frame inner to this frame (corrupt stack?)
(kgdb) quit
hub2# ^Dexit

Script done on Tue May 24 15:54:23 2005
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

ep/X11 problems

[Stephen Montgomery-Smith]

I have a Dell Inspiron 7500 on which I have put FreeBSD Release 5.4.
The 3Com Megahertz 574B pccard ethernet card works well with the ep 
driver, except that after I run X11, it simply stops working.

I am guessing that it is an interupt conflict.  I have tried everything 
I can think of so that sp0 is not irq 11, most notably putting
hints.ep.0.irq=10
in /boot/loader.conf, but it just doesn't work - the irq for ep0 is 
still 11.

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

Re: ep/X11 problems

[Stephen Montgomery-Smith]

Stephen Montgomery-Smith wrote:
I have a Dell Inspiron 7500 on which I have put FreeBSD Release 5.4.
The 3Com Megahertz 574B pccard ethernet card works well with the ep 
driver, except that after I run X11, it simply stops working.

I am guessing that it is an interupt conflict.  I have tried everything 
I can think of so that sp0 is not irq 11, most notably putting
hints.ep.0.irq=10
in /boot/loader.conf, but it just doesn't work - the irq for ep0 is 
still 11.

Oops - I was supposed to put it in /boot/device.hints.  But it still 
didn't work.

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

Problems with PCI-express video card

[Stephen Montgomery-Smith]

I have a nvidia PCI-express 6600 video card on an Intel SE7525GP2 
motherboard.  I am running a fairly recent version of RELENG_5.

I am having great difficulty getting the video card to work.  On an 
older version of Xorg it would try to use the vesa driver.  It did put 
up some video, but it was illegible.

The most recent version of Xorg tries to use the nv driver.  I have also 
tried out the very recent nvidia driver that just came out on the nvidia 
website a few days ago.  In these cases startx simply doesn't work, and 
I get the error messages:

(EE) NVIDIA(0): No valid FB address in PCI config space
I might add that when the nvidia.ko is loading, it puts out messages 
like this:

pci3: ACPI PCI bus on pcib3
nvidia0: GeForce 6600 mem 
0xdd00-0xddff,0xf000-0x,0xd8
00-0xdbff at device 0.0 on pci3
nvidia0: NVRM: NVIDIA MEM resource alloc failed.
nvidia0: NVRM: NVIDIA driver alloc failed.
device_attach: nvidia0 attach returned 6

I have tried also messing with the AGP settings to no avail, but I guess 
that is irrelevant anyway (is AGP totally unrelated to PCI-express?)

I don't know if this is a video card issue, or a motherboard issue, or 
what.  It works beautifully with Windows XP.  I might try it out with 
Linux also, but I haven't got that far yet.

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

Re: Panic - cannot get a dump

[Stephen Montgomery-Smith]

Bob Johnson wrote:
Any chance your RAID array is built from two-year-old Western Digital 
drives?  Your problem sounds a lot like the one discussed here:
http://adam.kungfoohampster.com/lists/freebsd-questions/msg18877.shtml

The message above doesn't mention it, but the WD KB article also 
includes a fix for drives on 3Ware controllers.

Probably this is not the problem.  I have Seagate drives, and the 
symptoms seem to be different - I have a panic, not a freeze.

Although I am having problems with the disk when I reboot.  The program 
I am running outputs a data.check file every second or so, so that 
when the program is restarted it can pick up where it left.  The code to 
do this is something like
  check_point = open(data.check-tmp,O_WRONLY|O_TRUNC|O_CREAT,0644);
  write(check_point,lots-of-stuff);
  close(check_point);
  rename(data.check-tmp,data.check);
What I find is that after the panic the file data.check is several 
days old.  I am guessing it is because the IDE Seagate disk has some 
cache that it doesn't write back to the disk - probably it is the 
directory itself which is not properly updated.  It is a bit annoying, 
but I can live with this.  But maybe this indicates something more sinister.


I have put in another IDE disk whose only purpose is to be the disk to 
dump to.  Hopefully I will be able to catch a good dump on that.

--
Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Panic - cannot get a dump

[Stephen Montgomery-Smith]

(This is a follow up to earlier messages I sent to freebsd-smp because 
then I thought it was an smp issue - now I am not so sure.)

I have been experiencing some panics on my dual processor Xeon system. 
It can take up to a few days for a panic to happen, and it seems to 
happen under heavy loads.

I have set the dumpdev variable in rc.conf as the instructions say, and 
indeed a reboot -d does actually generate a good dump.  But for some 
reason this particular panic refuses to create any dump at all.

The instruction pointer is at 0xc060b885, and:
nm -n /boot/kernel/kernel | grep c060b
c060b09c t pgadjustjobc
c060b128 T fixjobc
c060b240 t orphanpg
c060b390 T fill_kinfo_proc
c060b3a4 T fill_kinfo_thread
c060bbbc T pstats_alloc
c060bbd8 T pstats_fork
c060bc08 T pstats_free
c060bc1c T zpfind
c060bc98 t sysctl_out_proc
c060bf20 t sysctl_kern_proc
I am using a recent version of RELENG_5 (last make world was about March 4).
The disk is a RAID 0 twe0: 3ware Storage Controller. Driver version 
1.50.01.002

I am not suspecting hardware problems, because of the consistency of the 
value of the instruction pointer when the crash occurs.

I am now going to try the system with HTT disabled.  Maybe it will crash 
likewise if I wait long enough.

Here is my config file
include GENERIC
ident HUB2
nooption INET6
options SMP
device atapicam
and dmesg:
Copyright (c) 1992-2005 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 5.4-PRERELEASE #1: Fri Mar  4 19:15:30 CST 2005
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/HUB2
ACPI APIC Table: A M I  OEMAPIC 
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 3.40GHz (3391.52-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0xf41  Stepping = 1
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
  Hyperthreading: 2 logical CPUs
real memory  = 3221020672 (3071 MB)
avail memory = 3150659584 (3004 MB)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  6
 cpu3 (AP): APIC ID:  7
ioapic0 Version 2.0 irqs 0-23 on motherboard
ioapic1 Version 2.0 irqs 24-47 on motherboard
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: A M I OEMRSDT on motherboard
acpi0: Power Button (fixed)
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0
cpu0: ACPI CPU on acpi0
acpi_throttle0: ACPI CPU Throttling on cpu0
cpu1: ACPI CPU on acpi0
cpu2: ACPI CPU on acpi0
cpu3: ACPI CPU on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pci0: unknown at device 0.1 (no driver attached)
pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0
pci1: ACPI PCI bus on pcib1
pcib2: ACPI PCI-PCI bridge at device 3.0 on pci0
pci2: ACPI PCI bus on pcib2
pcib3: ACPI PCI-PCI bridge at device 4.0 on pci0
pci3: ACPI PCI bus on pcib3
pci3: display, VGA at device 0.0 (no driver attached)
pcib4: ACPI PCI-PCI bridge at device 28.0 on pci0
pci4: ACPI PCI bus on pcib4
em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 
0xdc00-0xdc3f mem 0xdeec-0xdeed,0xdeee-0xdeef irq 24 at 
device 2.0 on pci4
em0: Ethernet address: 00:0e:0c:63:34:14
em0:  Speed:N/A  Duplex:N/A
twe0: 3ware Storage Controller. Driver version 1.50.01.002 port 
0xd880-0xd88f mem 0xde00-0xde7f irq 25 at device 3.0 on pci4
twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048
uhci0: UHCI (generic) USB controller port 0xc880-0xc89f irq 16 at 
device 29.0 on pci0
usb0: UHCI (generic) USB controller on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: UHCI (generic) USB controller port 0xcc00-0xcc1f irq 19 at 
device 29.1 on pci0
usb1: UHCI (generic) USB controller on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
pci0: base peripheral at device 29.4 (no driver attached)
pci0: base peripheral, interrupt controller at device 29.5 (no driver 
attached)
pci0: serial bus, USB at device 29.7 (no driver attached)
pcib5: ACPI PCI-PCI bridge at device 30.0 on pci0
pci5: ACPI PCI bus on pcib5
em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 
0xec00-0xec3f mem 0xdefa-0xdefb irq 16 at device 3.0 on pci5
em1: Ethernet address: 00:0e:0c:3d:e1:6f
em1:  Speed:N/A  Duplex:N/A
pci5: multimedia, audio at device 4.0 (no driver attached)
isab0: PCI-ISA bridge at device 31.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel 6300ESB UDMA100 controller port 
0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
pci0: serial bus, SMBus at device 31.3 (no 

Re: 5.2 - 5.3 without single mode?

[Stephen Montgomery-Smith]

M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
dima [EMAIL PROTECTED] writes:
:  Is it possible to cvsup from 5.2 to 5.3 without booting in single mode?
:  I have a remote machine and want update it, but it is no console access,
:  only SSH.
: You don't actually need to reboot in single-user mode. Just make sure your 
users wouldn't use the server hard during the
: # mergemaster -p
: # make installworld
: # mergemaster
: cycle. You can basically disable all the services but sshd for that task  
enable them again after the second reboot.
While you don't NEED to go into single user (I do the above all the
time), you are setting yourself up to get screwed the first time that
a new, common system call is introudced...
So if there is a new common system call introduced, will it arrive with 
a nice entry in UPDATING plus a HEADS UP?

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

Beastie

[Stephen Montgomery-Smith]

It is with a little intrepidation that I ask this question, because I 
sense that what I am about to ask might push some buttons, or perhaps 
bring back some unpleasant memories of those who have asked what I am 
going to ask in a less tactful manner.

I find that the beastie that appears at boot time with FreeBSD 5.3 
mildly bothers me.  It is possible for me to edit boot/beastie.4th, but 
this gets put back each time I do make installworld.

Would it be possible to add a variable show_beastie to be put in 
/boot/loader.conf, which would default to YES, but users could add in 
show_beastie=NO if they didn't want it, but only want the menu.

I am sure that this is a sensitive subject with you guys, because I know 
that you have no intention of associating FreeBSD with satanism or 
anything like that.  It is not my intention to apply any kind of label 
of evil to you guys, indeed I find FreeBSD to be a very fine operating 
system, and I use it all the time.  But the symbol which is commonly 
associated with the devil does cause me some discomfort, and for 
example, if I were to install some kind of server for my church, I think 
that it would bother them as well.

I know that the the symbol of the beastie is strongly associated with 
FreeBSD, and that it would be grossly unfair for me to ask for it to be 
removed just because of my personal discomfort.

That is why I am proposing the solution above.  I think that it would be 
easy to implement by anyone who knows Forth (presuming that the 
loader.conf variables are known to the beastie.4th program), and that 
this would not interfere at all with those who don't mind or enjoy the 
beastie, but it would also help people like me in an unobtrusive manner.

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

Re: Beastie

[Stephen Montgomery-Smith]

Jon Noack wrote:
Throw 'beastie_disable=YES' into /boot/loader.conf.
Jon

Thanks guys - I really appreciate you having done this.
Stephen
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

/dev/fd/3

[Stephen Montgomery-Smith]

I have a program that needs to write to file descriptor 3 via /dev/fd/3. 
 But FreeBSD-5.3 doesn't let me do that, since only fd/0-2 exist.  How 
do I do this?  man fd didn't help me.

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

Re: /dev/fd/3

[Stephen Montgomery-Smith]

Robert Watson wrote:
On Sun, 24 Oct 2004, Stephen Montgomery-Smith wrote:

I have a program that needs to write to file descriptor 3 via /dev/fd/3. 
 But FreeBSD-5.3 doesn't let me do that, since only fd/0-2 exist.  How
do I do this?  man fd didn't help me. 

You can mount fdescfs on top of /dev/fd using the following command as
root:
mount -t fdescfs fdescfs /dev/fd
Thanks - it works.
How about adding fdescfs(5) to the SEE ALSO section of man fd?
Stephen
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Error in make buildworld

[Stephen Montgomery-Smith]

I have recent sources (the most recent CTM delta).  I do make -j4
buildworld
on three different computers.  It works on two of them, but on one of
them (the fastest), I get:

=== usr.sbin/i4b/ispppcontrol
rm -f .depend
mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include 
/usr/src/usr.sbin/i4b/ispppcontrol/ispppcontrol.c
cd /usr/src/usr.sbin/i4b/ispppcontrol; make _EXTRADEPEND
echo ispppcontrol: /usr/obj/usr/src/i386/usr/lib/libc.a   .depend
=== usr.sbin/i4b/man
=== usr.sbin/boot0cfg
rm -f .depend
mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include 
/usr/src/usr.sbin/boot0cfg/boot0cfg.c
cd /usr/src/usr.sbin/boot0cfg; make _EXTRADEPEND
echo boot0cfg: /usr/obj/usr/src/i386/usr/lib/libc.a   .depend
1 error
*** Error code 2
1 error
*** Error code 2
1 error

I didn't get this problem when I removed the -j4.  This computer had a
hard drive failure a few months ago, and the replacement drive is
exceedingly fast.  So maybe this computer is too fast for -j4 to
work.  As computers get faster and faster, maybe more and more people
will have this problem.

-- 
Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen

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

Re: linux-base 6.2 vs linux-base 7

[Stephen Montgomery-Smith]

Bruce Burden wrote:
 
 I think Netscape 4 is compiled with the Linux 6 libraries.
 I installed Linux base 7 on a clean system, and Netscape install
 went out and tried to install Linux base 6. It could not find a
 particular library, which was there, just under a different name.
 Linux 7 has a bad habit of naming everything *.2.2.2.*, I noticed.
 
 I couldn't find the libstd++, I believe it was, that Netscape
 complained about on startup, and I didn't wnat to dig through
 meaningless RPM's to find _the_ library, so I finally wiped Linux
 base 7 and installed Linux base 6.
 

You can fix this as follows.  Start netscape - see that it has an error
message about not finding
libstd++
where  is something.  Look in /compat/linux/usr/lib.  There you see
libstd++
So do
ln -s libstd++ libstd++
and netscape should work.

Also, make sure you run a very recent version of FreeBSD stable - there
is a problem in linux emulation in older versions.

-- 
Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen

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

Re: mergemaster goes postal

[Stephen Montgomery-Smith]

Kris Kennaway wrote:
 
 On Thu, Sep 20, 2001 at 12:17:58PM +0100, j mckitrick wrote:
  On Wed, Sep 19, 2001 at 09:41:28PM -0700, Randy Bush wrote:
  | happened on three separate systems cvsupped this afternoon
  |
  | *** You installed a new /dev/MAKEDEV script, so make sure that you run
  | 'cd /dev  /bin/sh MAKEDEV all' to rebuild your devices
  |
  | Would you like to run it now? y or n [n] y
  | Running cd /dev  /bin/sh MAKEDEV all
  |
  | MAKEDEV: arith: syntax error: à   {
  |
  | bad node: mknod i4bteld1
 
  Check the archives for the past few days.  This has been asked several times
  in the last week or two.
 
  You'll either need to change the MAKEDEV script or change your CPUTYPE.
 
 What does CPUTYPE have to do with a shell script?
 

I think the bug is in sh.

-- 
Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen

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

Printer problems

[Stephen Montgomery-Smith]

I have a HP Deskjet 932C.  I was having problems with printing out large
douments - right in the middle of the print job the job would stop.  lpq
would complain that the printer was offline.  The only fix I found was
to reboot the computer.

I fixed the problem by switching to using polling mode (using
lptcontrol).

Is this a known bug with the lpt drivers?


-- 
Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen

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

Re: XFree86-4.1.0_4 still broken?

[Stephen Montgomery-Smith]

I had problems building Mesa3 with XFree86-4.1.0.  I did discover a
work around which I posted as a PR:

http://www.freebsd.org/cgi/query-pr.cgi?pr=28228

This is the process I used to make Mesa3.  The resulting binaries and
libraries seemed to work fine.

cd /usr/ports/graphics/Mesa3
make
cd work/Mesa-3.4.2/src-glu
make
cd ../../..
make




Mike Bristow wrote:
 
 On Thu, Jun 14, 2001 at 12:58:27PM -0400, a clever sheep wrote:
  On Thu, Jun 14, 2001 at 11:28:45AM -0400, Kenneth Mays wrote:
  
   Successful install notes on using these applications on v4.3-R
   1. XFree86 v4.1.x
   2. Gnome 1.4.x
   3. KDE 2.1.x
   4. Netscape v4.77, 6.1
 
  am i just missing something here?
 
  cd /usr/ports/x11/XFree86-4/ ; make install
  cd ../gnome ; make install
 
 Did you have Mesa3 installed before you did this?
 
 It seems to me that:
 
 gnome depends on x11/xscreensaver
 
 xscreensaver depends on graphics/gle
 
 gle needs libglut which is in graphcis/Mesa3, but if you have
 XFREE86_VERSION=4 set the gle port doesn't try and make it.
 
 If I try and build Mesa3 by hand, it bombs out.
 
 It used to be (with earlier versions of XFree86-4) that Mesa would
 build correctly if you wanted libglut.  So if you had Mesa3 build
 from the times when you had XFree86-4.0.1, and then you installed
 XFree86-4.1, then your build of gnome might work, while mine
 wouldn't.
 
 I've stuck script(1-- 
Stephen Montgomery-Smith
[EMAIL PROTECTED]
http://www.math.missouri.edu/~stephen

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