Re: Patch to modify default inetd.conf, have sysinstall prompt to edit , inetd.conf
->On Tue, 31 Jul 2001, Mike Porter wrote: > > >Actually, although I'm happy with the current default of enabling SSH for >now, if there isn't already a sysinstall post-install config twiddle for >SSH, we should probably add one. To be honest, a "default all off" >policy, with the opportunity to enable easily in sysinstall, might be >better than turning SSH on by default. Maybe we'll do that for >5.0-RELEASE :-). Yes thank you for clarifying. Although as I mentioned earlier, I managed to misread your post and thought you were toaling about ssh when you were talking about ftpd... > >This is true--however, the inetd.conf file doesn't lend itself to >automated management, as it doesn't have an inline "disabled" flag. To >disable a service, you comment it out, making it hard for a program to >distinguish things which are legitimately comments, and things that are >disabled services. In the long term, it would probably make sense to >develop some sort of administrative tool for inetd.conf: however, I >concluded that doing so prior to 4.4-RELEASE was unlikely, and opted for >this. In the future, if such a tool is developed, I'd be happy to slot it >in instead of invoking EDITOR on it :-). > This is an interesting point, though it could also be argued that if there is a prety tool to do it, many (most?) of the comments in the file are no longer needed. The flip side of this, of course is that then you are more or less forced into using the specialized editor, and there are those who would prefer not to (at least not all the time). JUst brainstorming herebut another potential advantage...such a program could invoke a boot time check of inetd.conf to a stored backup created on editing, which block stuff like the person who had the "dlip" line in his inetd.conf. I suppose the argument AGAINST that is that whoever put that line in his inetd.conf could as easily have access to the mythical-viinetd (to borrow from vipw), and this therefore doesn't add much in the way of *real* security. Well, I'm going to shut up now before I put my foot in my mouth again. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Boot oddness
So I installed FreeBSD to be duaql boot with WinME; WinME is on disk 1, a 30G drive, FreeBSD on 2, another 30G drive. All went well in install, but when I boot, I have problems. When I get to the promtp for loading an OS, I have the choices of F1 for the OS on the drive, GF5 to change drives. F5 works fine, but when I choose F1, the system freezes. To make it odder, if the default is to load an OS, if I wait without pressing F1, it .will. load the OS. Sadly, it has a habit of changing the default from F1 to F5, at which point I cannot load anything; I have to pop in my Install CD and make it boot the drive. How can I fix this? I would like the menu to work, but I would likely settle for making a floppy for FreeBSD that I can just pop in when I want to boot FreeBSD. Ideas? Jamie PS Sorry for typos, 5 second lag to my email box. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: upgrade
klein brock <[EMAIL PROTECTED]> types: > i want to upgrade my FreeBSD4.2-STABLE to > FreeBSD4.3-STABLE > > can anybody help me ? or give me some suggestion which > doc should i read ? If you're running 4.2-STABLE - and not -RELEASE - you're already most of the way there. Updating your source tree again, and reinstalling the world should do the trick. The handbook covers this at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html > and following. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
silly doc-bug to fix before release
I just noticed a thinko in make.conf(5) today. What ought to be FORCE_PKG_REGISTER is FORCE_PKG_RESIDENT. No biggie, obviously, but it seemed like a good thing to fix... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: upgrade
> i want to upgrade my FreeBSD4.2-STABLE to > FreeBSD4.3-STABLE > > can anybody help me ? or give me some suggestion which > doc should i read ? Take a look at my 'make world' cheat sheet at http://www.mostgraveconcern.com/freebsd/sheet.cgi?mw Have fun! --Dan -- Dan O'Connor On Matters of Most Grave Concern http://www.mostgraveconcern.com FreeBSD Cheat Sheets http://www.mostgraveconcern.com/freebsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
upgrade
i want to upgrade my FreeBSD4.2-STABLE to FreeBSD4.3-STABLE can anybody help me ? or give me some suggestion which doc should i read ? Thanks! __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: PERC 3 Dell 2500 and FreeBSD 4.3 stable
Thanks to everyone for their input. This morning I was able to configure the RAID 5 logical drive 3 x 36 gig drives for a 72 gig logical drive --67 gig and change actually, the hd overhead chewed up > 4 gig. The boot disks from the 7/21/01 snapshot from releng4.freebsd.org worked like a charm and, after cvsupping the sources (I know, a somewhat hazardous procedure in a code freeze), I was able to compile an SMP kernel that supported both the machine's processors. I installed and ran the dnetc client just so I could watch the CPU's switch back in forth in a top screen. :-) FreeBSD on this machine makes for one snappy server. Thanks again for all your help. Tim Kellers CPE/NJIT On Tue, 31 Jul 2001, Mike Smith wrote: > > Here is a summary of PERC hardware from Mike Smith who did most (all) > > of the driver work for them: > > The PERC, PERC 2/SC, PERC 2/DC and PERC 3/D* are AMI designs. > > > > The PERC 2/Si, PERC 2/Di, PERC 3/Si and PERC 2/QC are Adaptec designs. > > > > "PERC" means "this is a Dell-branded RAID controller". > > "2" and "3" refer to 40MHz vs 80MHz SCSI support. > > "S" "D" and "Q" are single, dual and quad channel designations. > > "i" means it's integrated onto the server motherboard. > > "C" means it's an addin card. > > "L" means it's the low-cost version. > > Just to amend this; the 3/DC is an AMI controller, but the 3/Di is an > Adaptec design. > > Another way of looking at it is that if it's an 'i', or a QC, it's an > Adaptec. Otherwise it's an AMI. Knowing Dell, though, this may change > again without too much notice. 8( > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] >V I C T O R Y N O T V E N G E A N C E > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Beware of WindRiver Systems!
Tony Landells wrote: > > Hi Gerd, > > Maybe I'm just lucky, but I haven't had any problem. My 4.3 CDs > arrived without any "intervention" on my part. Maybe a bit more > slowly than I might have liked, but I don't need them at the moment > so I don't really care. > > But then, they do say that Australia is "the lucky country" ;-) It must be "the lucky country" since I had no problems with my subscription ether... Besides it arriving 2 or 3 weeks late ofcouse :P To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: I am trying to contact webmaster for "www.bsdvault.net"
This has nothing to do with the FreeBSD project and should not be posted to its mailing lists. The web site www.bsdvault.net is a completely independent entity and you have violated the published mailing list charter for freebsd-stable by even posting your complaint here. Please see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL For full information on what constitutes valid material for the freebsd-stable mailing list. Whether the content originated here or not is also irrelevent since these are publically available mailing lists for which published fair-use guidelines apply. The project holds no responsibility for the content or redistribution of the contents of these lists and all usage of them as at "own risk", as described in the BSD license. This notice also constitutes your first official warning of a charter violation. Should you repeat this offense, you will be banned from all FreeBSD mailing lists in accordance with the charters. Thank you. - Jordan P.S. In case it's not clear, we're NOT going to be dragged into this and I am firmly invoking the mailing list charters to preempt any such thing. No further traffic to this list on this matter at all, please! From: "Monica Shin" <[EMAIL PROTECTED]> Subject: I am trying to contact webmaster for "www.bsdvault.net" Date: Wed, 01 Aug 2001 23:15:27 + > http://www.bsdvault.net/article.php?sid=298&mode=thread&order=0 > > He has asked me regarding the procedures of the law in dealing with such > matters and agreed to resolve this matter in peaceful manner should it be > possible. Should he pursue to go on with a law suit, he has all the rights > to ask for any damages to his honor that has occured or should occur in > whatever form should it be by email or any of the means; he has the rights > to restitution for any misuses and damages to his intellectual property (the > message is signed), the party in operation of www.bsdvault.net. To make it > even worse, he has the rights to ask for the shutdown of the To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Fat kernel, needs dieting (again :-)
'make release' as of Aug/01/2001 JST fails, since a kernel for kern.flp is a little bigger and doesn't fit to a 1.44MB floppy. % ls -lR total 1297 drwxr-xr-x 2 root wheel 512 Aug 2 06:11 boot -r-xr-xr-x 1 root wheel 1316804 Aug 2 06:11 kernel.gz ./boot: total 162 -r--r--r-- 1 root wheel 512 Aug 2 06:11 boot1 -r--r--r-- 1 root wheel7680 Aug 2 06:11 boot2 -r-xr-xr-x 1 root wheel 147456 Aug 2 06:11 loader -rw-r--r-- 1 root wheel 136 Aug 2 06:11 loader.rc % du -s . 1460. *** The other day a guy (sorry I forgot who) says that 1) /boot/boot1 and /boot/boot2 can be safely removed, since these are not used. It brings us about 8kbytes. 2) /boot/loader can be kgzip(1)ed. It brings us about (approx.) 60kbytes. Hack 1) is already committed into 5-current so it's safe to do. Hack 2) is not yet commited to any branches, but I've tested with recent 4-stable and 5-current and it works fine. -- - Makoto MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Beware of WindRiver Systems!
From: Tony Landells <[EMAIL PROTECTED]> Subject: Re: Beware of WindRiver Systems! Date: Thu, 02 Aug 2001 09:12:04 +1000 > But then, they do say that Australia is "the lucky country" ;-) Yeah, you got all the convicts. We got all the puritans. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: I am trying to contact webmaster for "www.bsdvault.net"
On Wed, 1 Aug 2001, Dave Uhring wrote: > On Wednesday 01 August 2001 18:15, Monica Shin wrote: > > I'm sorry if you are reading this. I'm a law student at University of > > Washington (Seattle, WA). This morning, Wednesday, August 1, 2001, a > > In most jurisdictions in the US it is illegal to represent another person's > interests in matters of law without having first been admitted to the bar > in one's state. I wouldn't worry too much about that - the IP address from the headers of the email she posted reverse resolves back to an address within Virginia Tech, VA anyway... gavin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: I am trying to contact webmaster for "www.bsdvault.net"
On Wednesday 01 August 2001 18:15, Monica Shin wrote: > I'm sorry if you are reading this. I'm a law student at University of > Washington (Seattle, WA). This morning, Wednesday, August 1, 2001, a > friend of mine contacted me regarding the posting of his "signed" email > that was, I believe, exchanged in freebsd-stable forum sometime ago, > without his written consent. As of now, I don't know the details of the > policy and rules one has to agree and sign before becoming a member to > the freebsd-stable list server but he is very upset and serious about > this matter. The link is given below. > > http://www.bsdvault.net/article.php?sid=298&mode=thread&order=0 > > He has asked me regarding the procedures of the law in dealing with such > matters and agreed to resolve this matter in peaceful manner should it be > possible. Should he pursue to go on with a law suit, he has all the > rights to ask for any damages to his honor that has occured or should > occur in whatever form should it be by email or any of the means; he has > the rights to restitution for any misuses and damages to his intellectual > property (the message is signed), the party in operation of > www.bsdvault.net. To make it even worse, he has the rights to ask for > the shutdown of the > www.bsdvault.net operation should the Defense loses the case. Whoever is > in charge of the operation of the website, www.bsdvault.net, should take > this matter seriously and take any means of actions necessary in timely > manner to prevent any unnecessary actions that may or may not follow from > taking. > > > Regards, > Monica Shin, > Wdenesday, August 1, 2001. > > Mr. Cho has resigned from freebsd-stable mailing list for this matter. > > In most jurisdictions in the US it is illegal to represent another person's interests in matters of law without having first been admitted to the bar in one's state. > _ > Get your FREE download of MSN Explorer at > http://explorer.msn.com/intl.asp > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: printcap question
Check this WWW: http://pdq.sourceforge.net/ Use the ports Luke /usr/ports/print/pdq Also this page is a great help with PDQ itself. http://www.linuxprinting.org/pdq-doc.html Specific info on network printing. http://www.linuxprinting.org/howto/network.html#NETWORKED-PRINTERS "Douglas G. Allen" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 08/01/2001 01:20 PM To: "FreeBSD Stable Listserv" <[EMAIL PROTECTED]> cc: Subject:printcap question In conjunction with my question in the hardware list about printer compatibility, I'm wondering if I've missed something somewhere in the documentation. Is there a setting that can go into the printcap entry for a printer that will allow you to print to a printer with a network card (EIO Card for HP printers) installed in it? I looked, but I didn't see anything that looked like it would be exactly what I was looking to do. Example: I have several HP printers with EIO cards in them. Each of them is set to a distinct IP address (a.b.c.d), with a mask (e.f.g.h), in the printer configuration. For the Windows printers, you create the IP port, assign the printer to it, then print to the IP address. I'd like to do something similar with a printcap entry and lpd and it would open up the number of printers one can easily use greatly. Thanks in advance for any information. Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
make world failure
Cvsup today: install -c -o root -g wheel -m 444 growfs.8.gz /usr/share/man/man8 ===> sbin/ifconfig install -c -s -o root -g wheel -m 555 ifconfig /sbin install -c -o root -g wheel -m 444 ifconfig.8.gz /usr/share/man/man8 ===> sbin/init install -c -s -o root -g wheel -m 500 -fschg -b -B.bak init /sbin *** Error code 64 Stop in /usr/src/sbin/init. *** Error code 1 Stop in /usr/src/sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Any advice highly appreciated. -Wash -- Odhiambo Washington Wananchi Online Ltd., [EMAIL PROTECTED] 1st Flr Loita Hse. Tel: 254 2 313985 Loita Street., Fax: 254 2 313922 PO Box 10286,00100-NAIROBI,KE. In activity we must find our joy as well as glory; and labor, like everything else that is good, is its own reward. -Edwin P. Whipple PGP signature
Re: installworld failure (install of sbin/init)
Shouldn't this mandate a UPDATING entry? Or is it already the case? ;) A Anders Andersson wrote: > On Wed, Aug 01, 2001 at 09:01:12PM +1000, Tony Maher wrote: > >>Just did buldworld, kernel, installworld cycle but there was one small >>problem in installworld >> >>o---o >>===> sbin/init >>install -c -s -o root -g wheel -m 500 -fschg -b -B.bak init /sbin >>install: illegal option -- b >>usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 >>file2 >> install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 >>... >> fileN directory >> install -d [-v] [-g group] [-m mode] [-o owner] directory ... >>*** Error code 64 >> >>Stop in /usr/src/sbin/init. >>o---o >> >>Checking CVS I thought maybe I had cvsupped and got the init Makefile >>change and not the changes to (x)install but this does not appear to be the >>case. A second cvsup after the install did not get anything for xinstall >>and the manpage for install shows the new -b and -B (as does runningthe new >>install). >> >>Does installworld use the old install? >> >>In any case removing the "-b -B.bak" in sbin/init/Makefile and reinstalling >>solved the problem for me. >> > > Or as I did, > > cd /usr/src/usr.bin/xinstall && make install > > and then installworld works. > > -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Patch to modify default inetd.conf, have sysinstall prompt to edit , inetd.conf
In message <[EMAIL PROTECTED] >, Robe rt Watson writes: > One of the observations that has been made fairly frequently to me is that > the current default inetd.conf puts many FreeBSD users at risk > unnecessarily, as many of them have moved to using SSH for remote access > needs. In particular in light of the recent ftpd and telnetd security > bugs, it seems like 4.4-RELEASE would be a good time to move to a more > conservative default of having both of these services disabled in the base > install, as both NetBSD and OpenBSD have moved to doing. I think that this is goodness. I have been an advocate of this (actually a less balanced approach -- of which I've seen the light and error of my thinking) for a long time. For that matter one of my biggest pet peeves about RH Linux is that by default it installs everything and enables everything. I think that the approach taken here is a balanced approach and is the correct approach. Services are not removed from the system entirely and can be enabled if needed. Regards, Phone: (250)387-8437 Cy SchubertFax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: [EMAIL PROTECTED] Open Systems Group, ITSD Ministry of Management Services Province of BC To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: PERC 3 Dell 2500 and FreeBSD 4.3 stable
Hi James and the others using Dell and FBSD, I have had terrible problems with the perc controllers from Dell that have been discussed before on this list. However we order our 2400's and 1400's from dell and add Adaptec's 2100S and 3200S controllers that Mike Smith added support for in 4.2 and the hardware RAID is the fastest reliable RAID we have ever seen. The only difficulty is find the "raidutil" and storage manager software for FreeBSD. They don't provide source, but with enough digging I found the executables. Haven't had much luck with storage manager but raidutil works just great from the command line. Here is a link for the products: http://www.adaptec.com/worldwide/product/prodtechindex.html?cat=/Techn ology/RAID Hope this helps others on Dell, it would be great to get Dell to offers these controllers instead of those crappy PERC controllers, but these I guess are too expensive??? Hope this helps other freebsd-stable users, Ken - Original Message - From: "James Satterfield" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 31, 2001 2:39 PM Subject: RE: PERC 3 Dell 2500 and FreeBSD 4.3 stable > # Begin rambling > The Perc 3QC is an AMI Enterprise 1600 card. I've got two of them. They both > suck. =) > I've done a LOT of disk IO benchmarking with the Perc 3Di and 3QC cards in > the last few months. Awful results. If anyone is interested, I could send > them some of my findings (and a few things Dell has said about the > performance). Basically, I ended up removing the QC cards, installing a few > 2 channel ultra160 cards, and running software raid because the hardware > solution was so poor. It was very nice of Dell to start including a branded > version of Veritas Volume Manager as their array management solution. > # End rambling > James > > -Original Message- > From: Mike Smith [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, July 31, 2001 1:08 AM > To: Kevin Oberman > Cc: Tim Kellers; [EMAIL PROTECTED] > Subject: Re: PERC 3 Dell 2500 and FreeBSD 4.3 stable > > > > Here is a summary of PERC hardware from Mike Smith who did most (all) > > of the driver work for them: > > The PERC, PERC 2/SC, PERC 2/DC and PERC 3/D* are AMI designs. > > > > The PERC 2/Si, PERC 2/Di, PERC 3/Si and PERC 2/QC are Adaptec designs. > > > > "PERC" means "this is a Dell-branded RAID controller". > > "2" and "3" refer to 40MHz vs 80MHz SCSI support. > > "S" "D" and "Q" are single, dual and quad channel designations. > > "i" means it's integrated onto the server motherboard. > > "C" means it's an addin card. > > "L" means it's the low-cost version. > > Just to amend this; the 3/DC is an AMI controller, but the 3/Di is an > Adaptec design. > > Another way of looking at it is that if it's an 'i', or a QC, it's an > Adaptec. Otherwise it's an AMI. Knowing Dell, though, this may change > again without too much notice. 8( > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] >V I C T O R Y N O T V E N G E A N C E > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Help with "rmuser"
Thus spake Odhiambo: > > After a cvsupping and doing complete update yesterday, I now have > > a very funny problem - I can't remove users! > > > > everest# rmuser test2 > > Matching password entry: > > test2:RUgtD0aLuma/E:5259:1004::0:0:Test Two:/home/test2:/nonexistent > > > > Is this the entry you wish to remove? y > > > > Remove user's home directory (/home/test2)? y > > > > Removing user's at jobs:Updating password file, > > /usr/sbin/rmuser: Error: Couldn't open file : > > No such file or directory > > > > Is there something wierd I might have done? Replied I: > I don't think so. It looks like some recent changes broke rmuser. > I'm looking into it. It looks like rmuser is indeed broken. I submitted a PR with the following patch, which works for me. As usual, there is no guarantee that this won't totally destroy your password database; use with *extreme* caution. http://www.slb.to/~lucas/patches/rmuser-200108011320.diff Apply the patch in /usr/src/usr.sbin/adduser. Lucas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: RELENG_4 installworld broken
On Wed, Aug 01, 2001 at 12:43:23PM +0200, Anders Andersson wrote: > Just cvsup'd and built world, > > make installworld... > > ===> sbin/init > install -c -s -o root -g wheel -m 500 -fschg -b -B.bak init /sbin Install the new "install" by hand, that does it. cd /usr/src/usr.bin/xinstall make install mv /usr/bin/install /usr/bin/install.old mv /usr/bin/xinstall /usr/bin/install Then try installworld again. -- Pierre Beyssac [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Watching DVD's in -stable
Joe Kelsey wrote: > > As far as I understand it, in order to get effective video display from > any of the "new" players, your video card must support the XVideo > extension. In XFree86 4.1, the ATI supports this, but I believe that > the MGA driver still does not, although I cannot find a specific > reference anymore to which drivers support Xv and which do not. Does > anyone have a reference to the Xv support by driver? I think the MGA driver supports Xv. At least when I turned on the Xv display it worked for a bit (although it crashed not too long afterward). This is on a G200 with the Matrox HAL driver under Xfree86 4.1.0. Actually, all three modes worked (to varying degrees) on my system: Ximages (I guess), Xv, and SDL. The SDL display had some weird issues with looking really blocky on the bottom 3/4 of the image. Subtitles don't work at all from what I can tell. I can turn them on (and if I watch the debug output I see that it found the subtitle track), but nothing is ever displayed. The display is unfortunatly jerky. The worst part is, my CPU isn't even pegged. From what I can tell, vlc reads off a block from the DVD, de-csses it, decodes it, sends it to the display plugin, THEN reads off the next block. My DVD doesn't seek (or transfer) fast enough for it to keep up[1]. If vlc kept some sort of buffer full of blocks, I bet it would be smooth on even fairly low end systems. [1] And this is a 16x DVD using UDMA33 transfers. -- \ |_ _|__ __|_ \ __| Jason Andresen[EMAIL PROTECTED] |\/ | ||/ _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: question on BSD tweaks (daemonnews article)
* j mckitrick <[EMAIL PROTECTED]> [010801 14:17]: > > In the article in Daemonnews on tuning a BSD box for high performance, there > were 2 miscellaneous tweaks mentioned. One was partition layout, and the > other was turning on 'noatime' for most of the partitions. > > What partition layout strategies are suggested for servers? For > workstations? > > I have noatime turned on for my root partition. What other partitions can > use this setting for servers? And for workstations? Does it have any > downside? I think 'man tuning' says that noatime can mess up applications that use the modification time in their logic. (I wouldn't put it on /var, but that's mainly superstition) -- Turnaucka's Law: The attention span of a computer is only as long as its electrical cord. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Strange diskless bahaviour since CVSupdate today
On Wed, Aug 01, 2001 at 01:27:59PM +0200, Hartmann, O. wrote: > The terminals are all DURON based diskless systems, booting via PXE > and isc-dhcp2. On of these termninals is my administration terminal - > and this on differs only in one point from the others: it is mentioned > separately in /etc/exports where I export the diskless filesystem due > to the fact all the other terminals belong to a netgroup 'xterms'. It might be worth checking the server log to see if mountd produced any errors. Also, see what "showmount -e server.host.name" says. > Luckily this one terminal boots perfectly and I can work, but all others > boot kernel and the freeze at the point when on screen appears > "additional TCP extensions", at this stage it should start XDM-chooser. Try pressing Control-T on the terminal and see what program is running. Also see what it is waiting on (That's the word in square brackets). David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
question on BSD tweaks (daemonnews article)
In the article in Daemonnews on tuning a BSD box for high performance, there were 2 miscellaneous tweaks mentioned. One was partition layout, and the other was turning on 'noatime' for most of the partitions. What partition layout strategies are suggested for servers? For workstations? I have noatime turned on for my root partition. What other partitions can use this setting for servers? And for workstations? Does it have any downside? jcm -- o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o | Jonathon McKitrick ~ | | "I prefer the term 'Artificial Person' myself." | o-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-o To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Disabling portmapper (was Re: Patch to modify default inetd.conf, have sysinstall prompt to edit , inetd.conf)
On Tue, 31 Jul 2001, Nate Williams wrote: > > One of the observations that has been made fairly frequently to me is that > > the current default inetd.conf puts many FreeBSD users at risk > > unnecessarily, as many of them have moved to using SSH for remote access > > needs. In particular in light of the recent ftpd and telnetd security > > bugs, it seems like 4.4-RELEASE would be a good time to move to a more > > conservative default of having both of these services disabled in the base > > install, as both NetBSD and OpenBSD have moved to doing. > > In the same vein, shouldn't we also have the portmapper 'disabled' out > of the box by default? I know we haven't (yet) had any remote exploits > like Linux, but it may only be a matter of time. > > Plus, the crap filling up the logs could be argued as a type of DoS. I'd be tempted to disable the portmapper (rpcbind in -CURRENT) by default, allowing it to either be manually enabled, or enabled by virtue of dependencies (something we already support). Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
