Re: Firewall or not ...
On Wed, 2005-09-21 at 19:20 +, Marcin Jessa wrote: > On Wed, 21 Sep 2005 21:05:36 +0200 > Kiffin Gish <[EMAIL PROTECTED]> wrote: > > > I have installed FreeBSD 5.4 on my Dell Inspiron 8200 using WiFi to > > access the Internet. > > > > My question is what are the pros and cons of running a firewall on my > > client, e.g. is it really necessary. > > > > I mean it's not like I am running Windows and have to bloat it with all > > McAfee, Zonealarm ad infinitum -- or do I? > > > > Thanks alot in advance. > I have a firewall set up on my laptop, as it is company policy. FreeBSD makes it fairly simple to set up and use with the options in /etc/rc.conf, and I rarely have any need to tweak it. I have a fairly lightly modified "CLIENT" type firewall. DHCP is an issue, but a quick script at boot can be used to grab the dynamic IP without too much trouble. Otherwise I really do not have performance issues, connectivity problems, etc, that are worth mentioning. I like to keep a decent eye on security, but to my knowledge I have never run into an occasion where someone has tried to hack me into my laptop through wireless or wired, in a way that would work. I have certainly seen attempted MS-Windows hacks, etc. But nothing that would actually effect FreeBSD. I keep the system fairly up to date, and rarely have any problems with security. (The problems I have had, a firewall would not fix anyway.) I highly suspect that I could stop using the firewall all together and it would not make that much of a difference.So do you need a firewall? Probably not. But since it is really not that hard to set up and manage on FreeBSD, I would advise anyone to use one if they can. -- Marius M. Rex Sr. System Admin. Community Connect Inc. [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dgen-sdl gives only blank sceen
Has anyone had luck with dgen-sdl? All I have ever gotten with it is a blank screen. I have tried it a number of times under several recent versions of FreeBSD, and it is always the same blank screen. A blank screen with no sound. (but sound is a secondary issue.) I have searched thr archives of questions and see no refernce to this problem. The port compiles fine, as far as I can tell. It seems to run fine when it is invoked, except for the blank screen. I can start it up or quit dgen without obvious error. I can press 'tab' to 'reset' the game, the function keys work, all with little text feedback from the otherwise blank screen. A ktrace of the process shows that dgen is indeed loading the ROM. (One of the ROMs that I have has a text intro, and that shows up just fine in the kdump. The process smoothly moves on beyond that. I think the ROM is loading fine.) Granted I only have tested dgen-sdl with a few ROMs, but since all of them give the same response, I believe that I simply have something misconfigured. Other sdl games work fine. I do not think it is a case of old packages, as I have a subscription to FreeBSD and often simply do a fresh install for major upgrades instead of just a buildworld. So more then once I have built the port from scratch with all current packages for a given branch. While I have had the same experience with various versions of FreeBSD and thus different port builds of dgen-sdl, but here is the current setup: # uname -a FreeBSD sutolux.ny.home 4.7-STABLE FreeBSD 4.7-STABLE #6: Fri Dec 20 13:00:45 EST 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/SUTOLUX i386 with: esound-0.2.29 libaudiofile-0.2.3 libiconv-1.8_2 gettext-0.11.5_1 gmake-3.80 imake-4.2.0_1 libgnugetopt-1.2 libtool-1.3.4_4 nasm-0.98.33,1 pkgconfig-0.13.0 sdl-1.2.4_1 Mesa-3.4.2_2 aalib-1.4.r5_1 svgalib-1.4.2_1 freetype2-2.1.2_1 expat-1.95.5 XFree86-libraries-4.2.1_4 dgen-sdl-1.22_1 cat /etc/X11/XF86Config Section "Module" Load"dbe" # Double buffer extension Option"omit xfree86-dga" # don't initialise the DGA extension EndSubSection Load"type1" Load"freetype" Load "glx" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "/usr/X11R6/lib/X11/fonts/local/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" FontPath "/usr/X11R6/share/AbiSuite/fonts" EndSection Section "ServerFlags" EndSection Section "InputDevice" Identifier "Keyboard1" Driver "Keyboard" Option "AutoRepeat" "500 30" Option "XkbRules" "xfree86" Option "XkbModel" "pc101" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol""auto" Option "Device" "/dev/sysmouse" Option "Emulate3Buttons" EndSection Section "Monitor" Identifier "laptopscreen" HorizSync 31.5 - 57.0 VertRefresh 50-70 EndSection Section "Device" Identifier "Standard VGA" VendorName "Unknown" BoardName "Unknown" Driver "vga" EndSection Section "Device" Identifier "builtin" Driver "neomagic" EndSection Section "Screen" Identifier "Screen 1" Device "builtin" Monitor "laptopscreen" DefaultDepth 24 Subsection "Display" Depth 8 Modes "640x480" "800x600" "1024x768" "1280x1024" ViewPort0 0 Virtual 1024 768 EndSubsection Subsection "Display" Depth 16 Modes "640x480" "800x600" "1024x768" "1280x1024" ViewPort0 0 Virtual 1280 1024 EndSubsection Subsection "Display" Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" ViewPort0 0 Virtual 1152 900 EndSubsection EndSection Section "ServerLayout" Screen "Screen 1" InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" EndSection - Marius M. Rex NeXT is most Goth of all computers. It's all black. It's obscure and arcane. It's obstinate, and at times annoying. Most of all, it's a fetish which one can only defend by resorting to emotional arguments because there is no rational basis for involvement with it any longer. (Not only that, but many no longer work, and occasionally smoke.) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
memory disks in 4.5-stable
I want to create a number of small RAM disks on some webservers so they can serve high traffic content directly off of RAMdisks instead of conventional disks or NFS. I first tested this out on my desktop machine 4-7 stable and everything worked just fine. I made 3 10Mb RAMdisks and mounted then just as planned. But once I hopped onto the production servers (4.5-Stable from eb 26, 2002 I believe) I seemed to be limited to using only one md device. Only md0 is reconized as valid, any device number above that fails to be recognized as a configured device. MAKEDEV will make the devices just fine, but disklabel refuses to deal with them. It fails like so: image1# cd /dev image1# ./MAKEDEV md1 image1# disklabel -r -w md1 auto disklabel: /dev/md1c: Device not configured /dev/md1c and all the associated devices seem to be present, but disklabel refuses to recogize them. Again, this worked fine on my 4.7 desktop, but following the same procedure on the servers at our data center, it fails every time. I thought that perhaps adding a number after md in the kernel would help so I did this and recompiled: pseudo-device md 3 # Memory disks But that had no effect at all. If this is a bug, I can not find reference to it. Is it a bug that I can patch? Is there a work around I can preform? I am reluctant to upgrade the servers unless I have to, as they are in production. Anyone have any suggestions or advice? Please cc: responces to me, as I am not a regular subscriber. - Marius M. Rex NeXT is most Goth of all computers. It's all black. It's obscure and arcane. It's obstinate, and at times annoying. Most of all, it's a fetish which one can only defend by resorting to emotional arguments because there is no rational basis for involvement with it any longer. (Not only that, but many no longer work, and occasionally smoke.) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
