Suggestion on hardware ofr play with fxtv
Hello, I had keep reading the news on fxtv for a couple of monthes and want to play with it. However, I don't know which hardware should I to buy in order to start the games. Can anyone suggest me what to do ? Thanks. Clarence To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How to power off an ATX power supply machine on shutdown ?
Jose M. Alcaide wrote: Matthew Thyer wrote: Anyway, how do I power off a machine on shutdown ? I have apm in the kernel and it probes as apm v 1.2 but when the shutdown -p now command is run, the power is not turned off and I have to hold down the power button for 4 seconds to turn it off. Hows it done ? Do I have to run apmconf -e (The owner hasn't tried this yet) Yes. There is a knob in /etc/rc.conf (apm_enable) that forces this at startup. It doesn't work in all cases, though. It sure doesn't work on _my_ machine. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
how to install so5 for freebsd-current
Hello, I recently download so5 and encounter a problem when installing it. I was asked for the personal key from the product. Anyone know how to solve it. Thanks, Clarence To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: how to install so5 for freebsd-current
Go to www.stardivision.com and proceed with registration. ? Chan Yiu Wah wrote: Hello, I recently download so5 and encounter a problem when installing it.? I was asked for the personal key from the product.? Anyone know how to solve it. Thanks, Clarence To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How to power off an ATX power supply machine on shutdown ?
On 12 Feb, Daniel C. Sobral wrote: Do I have to run apmconf -e (The owner hasn't tried this yet) Yes. There is a knob in /etc/rc.conf (apm_enable) that forces this at startup. It doesn't work in all cases, though. It sure doesn't work on _my_ machine. Do you use the Power up at time/date feature of the BIOS? Bye, Alexander. -- Darth Vader sleeps with a Teddywookie. Fortune cookie http://netchild.home.pages.de/A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How to power off an ATX power supply machine on shutdown ?
Alexander Leidinger wrote: On 12 Feb, Daniel C. Sobral wrote: Do I have to run apmconf -e (The owner hasn't tried this yet) Yes. There is a knob in /etc/rc.conf (apm_enable) that forces this at startup. It doesn't work in all cases, though. It sure doesn't work on _my_ machine. Do you use the Power up at time/date feature of the BIOS? No. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Serious mbuf cluster leak..
Ouch. I can say that our implementation doesn't seem to suffer from this problem. Could be there's an issue in the use of PRUS_* v. the socket state we use. The code in my kernel looks like:
in sosend():
if (dontroute)
so->so_options |= SO_DONTROUTE;
if (resid > 0)
so->so_state |= SS_MORETOCOME;
s = splnet(); /* XXX */
error = (*so->so_proto->pr_usrreq)(so,
(flags MSG_OOB) ? PRU_SENDOOB : PRU_SEND,
top, addr, control);
splx(s);
if (dontroute)
so->so_options = ~SO_DONTROUTE;
so->so_state = ~SS_MORETOCOME;
and in tcp_output():
if (len) {
if (len == tp->t_maxseg)
goto send;
if (!(so->so_state SS_MORETOCOME)) {
if ((idle || tp->t_flags TF_NODELAY)
len + off >= so->so_snd.sb_cc)
goto send;
}
if (tp->t_force)
goto send;
We've subjected this to countless (well, some, I'm sure, can count them :-}) hours of thrashing for web server, file server, and other-server types of uses, and haven't seen any (reports of) leakage like this.
I'll look more closely at the results we see, to verify that we don't have a problem.
Regards,
Justin
From: Chris Csanady ccsan...@friley-185-205.res.iastate.edu>
Date: 1999-02-11 01:51:17 -0800
To:
Subject: Re: Serious mbuf cluster leak..
Cc:
In-reply-to: Your message of Wed, 10 Feb 1999 17:49:20 CST.19990210234920.2a1...@friley-185-205.res.iastate.edu>
X-Mailer: exmh version 2.0.2 2/24/98
X-Loop:
After a while, I have determined the cause of the leak to be the
following commit. Although, I can't seem to find any reason why
it would cause this behavior--reverting these files fixes it.
Any thoughts?
fenner 1999/01/20 09:32:01 PST
Modified files:
sys/kern uipc_socket.c
sys/netinet tcp_output.c tcp_usrreq.c tcp_var.h
sys/sys protosw.h
Log:
Add a flag, passed to pru_send routines, PRUS_MORETOCOME. This
flag means that there is more data to be put into the socket buffer.
Use it in TCP to reduce the interaction between mbuf sizes and the
Nagle algorithm.
Based on: Justin C. Walker jus...@apple.com>'s description of Apple's
fix for this problem.
Revision ChangesPath
1.50 +4 -2 src/sys/kern/uipc_socket.c
1.32 +3 -2 src/sys/netinet/tcp_output.c
1.40 +7 -2 src/sys/netinet/tcp_usrreq.c
1.49 +18 -17src/sys/netinet/tcp_var.h
1.26 +2 -1 src/sys/sys/protosw.h
>I have been seeing a nasty cluster leak in both 3.0 stable and 4.0
>current as of today. Until now, I thougt maybe it was something in
>my driver, athough after much careful looking over my code, it
>simply does not look possible. Also, I downgraded to current of
>Dec 12, and the problem dissappears.
>The odd thing is that the clusters that leak don't seem to be
>attached to mbufs. Or at least there is not a 1-1 ratio. Following
>is netstat output after a while of running netpipe in streaming
>mode. (NPtcp -s; see ftp://ftp.scl.ameslab.gov/pub/netpipe) Also,
>the leak only becomes apparent when the send write size is very
>large--several hundred K to several megabytes.
>Does anyone have any idea what this may be? I really am not sure
>where to look aside from trying prorgressively newer kernels. Also,
>I only have alphas to test on right now..
>puck:~> netstat -m
>211/416 mbufs in use:
>116 mbufs allocated to data
>95 mbufs allocated to packet headers
>1674/1688/2048 mbuf clusters in use (current/peak/max)
>3480 Kbytes allocated to network (97% in use)
>0 requests for memory denied
>0 requests for memory delayed
>0 calls to protocol drain routines
>Chris Csanady
>To Unsubscribe: send mail to majord...@freebsd.org
>with unsubscribe freebsd-net in the body of the message
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-net in the body of the message
To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Serious mbuf cluster leak..
On Thu, 11 Feb 1999 09:15:29 -0800 Justin C. Walker jus...@apple.com wrote: I can say that our implementation doesn't seem to = suffer from this problem. Could be there's an issue in the use of = PRUS_* v. the socket state we use. The code in my kernel looks like: The NetBSD code looks pretty much just like this, and also does not suffer from an mbuf cluster leak of any kind. -- Jason R. Thorpe thor...@nas.nasa.gov To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr
On Thu, Feb 11, 1999 at 10:24:51AM +0100, D. Rock wrote: Anyone with /usr/obj NFS mounted should have the same problems. I've just updated my firewall machine using NFSv3 hardmounted /usr/obj over a 10BaseT connection (slow!). Did a make installworld, and kernel rebuild over it last night with the latest cvsup.. NFS server was running 3.1-beta (2/10), and NFS client (firewall) was running 3.0-current (1/10). No problems at all.. I will try the termcap database test tonight.. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ #Anime Expo 1998 www.anime-expo.org/ # Redline Games www.redlinegames.com/ # Cal-Animage Epsilon www.best.com/~nugundam/epsilon/ # EX: The Online World of Anime Manga www.ex.org/ / To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Problem building world on current - into2html missing
=== lib/libcom_err === lib/libcom_err/doc info2html com_err.info info2html: not found *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Since when do we need a port installed to build the world? -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Serious mbuf cluster leak..
On Thu, 11 Feb 1999 09:15:29 -0800 Justin C. Walker jus...@apple.com wrote: I can say that our implementation doesn't seem to = suffer from this problem. Could be there's an issue in the use of = PRUS_* v. the socket state we use. The code in my kernel looks like: The NetBSD code looks pretty much just like this, and also does not suffer from an mbuf cluster leak of any kind. I'll take a look at the NetBSD code when I have a chance. Are you sure you just have not seen it though? I only see it over gigabit ethernet, and even then only when doing lots of large writes. Perhaps it is a timing issue? I am only pointing out what I see. It does not happen with source from before this change--so what else should I think? You are welcome to take a glance at my driver, although I don't think it is the problem. There are only 2 places where clusters are touched, and they never become seperate from the mbuf header. But I don't see any mbuf leak.. Chris To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
I may have missed this earlier in the thread, but has anyone given any consideration to upgrade installs? If an upgrade doesn't plant the new default files in /etc/default[s] after an upgrade, we now have two places and twice the files to compare on upgrade. As unorthodox as it sounds, if these defaults are meant to be unchanged, wouldn't a place like /boot/rc, or something similar, make sense? Upgrades get the new whistles, and administrators can fiddle files in /etc to their heart's content. -- Jay To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
mergemaster is your friend. On Fri, 12 Feb 1999, Jay Nelson wrote: I may have missed this earlier in the thread, but has anyone given any consideration to upgrade installs? If an upgrade doesn't plant the new default files in /etc/default[s] after an upgrade, we now have two places and twice the files to compare on upgrade. As unorthodox as it sounds, if these defaults are meant to be unchanged, wouldn't a place like /boot/rc, or something similar, make sense? Upgrades get the new whistles, and administrators can fiddle files in /etc to their heart's content. -- Jay To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: [Call for Review] new ioctl for src/sys/pccard/*
Nate Williams wrote: The changes to pccardd to support the new 'inactive' flag are still missing. We can power the slot on/off, but pccardd is unaware of these changes. Doesn't it need to be aware of the new 'power' state? Hmm. I looked pccard in PAO but it is complex in state treatment. I should make this more clearer. I'll continue to check PAO code so I will return this area after I check other area of PAO. At this time, I'll commit beep feature only. Right. Last I looked at PAO the pccard code had modifications all over the kernel. I think so, too. :-) -- Jun Kuriyama // kuriy...@sky.rim.or.jp // kuriy...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: [Call for Review] new ioctl for src/sys/pccard/*
On Sat, 13 Feb 1999, Jun Kuriyama wrote: Nate Williams wrote: The changes to pccardd to support the new 'inactive' flag are still missing. We can power the slot on/off, but pccardd is unaware of these changes. Doesn't it need to be aware of the new 'power' state? Hmm. I looked pccard in PAO but it is complex in state treatment. I should make this more clearer. I'll continue to check PAO code so I will return this area after I check other area of PAO. At this time, I'll commit beep feature only. Right. Last I looked at PAO the pccard code had modifications all over the kernel. I think so, too. :-) Pardon my naivite, but why iswas PAO not part of FreeBSD itself? -- Jun Kuriyama // kuriy...@sky.rim.or.jp // kuriy...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: StarOffice 5.0
According to William Woods: Is it correct to assume that StarOffice 5.0 works with current now? It does for me. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Lots of panic: vrele: negative ref cnt
: twice, so if you do this a few times you can panic a machine. I've : submitted a gnats report (kern/9970). : :I can confirm that this also halts my crashes with nmh's spost command. :I'll leave it up to an NFS guru to tell whether it's the *right* fix, :but it's certainly something that needs looking at, quickly. : :Thanks for your help. :-- :Dom Mitchell -- Palmer Harvey McLane -- Unix Systems Administrator This fix looks right. I've compared the NFS code to the UFS code as well as looked at the link() system call. The man page is wrong, and the NFS code is wrong. I'll commit a fix to -4.x and after getting the OK from Jordan, to -3.x too. It also appears that nfs_rename() is broken ( it leaves namei data sitting around, so no crash but...) And also possibly other nfs VOP calls -- I'll have to audit all of them. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
