Install bug - 4.9 stable - post install circular reboot
I can confirm an issue posted Dec 3rd, freebsd-stable maillist, titled 4.9 install buglet. I experience this bug running the install (various configurations) 100% of the time. After install, after system reboot, the boot loader comes up with F1: FreeBSD, and reboots continually forever. To test, I made 3 installs without issue using 4.8. So first, I'd like to confirm the bug report, and ask the following. In his buglet post, Ian noted the following work around. Work around. Force write in label screen (or rewrite MBR and label post reboot) Looking at fdisk, and the label utility I see nothing option along these lines. Could someone explain to me what/how to do this? Has anyone else seen this apparently prevalent issue? Is a fix likely, or do these kind of things just slip by? I did not expect this from a 'stable' release. Unfortunately, I'm making my second attempt at evaluating FreeBSD (last time I used an active box - and got frustrated with bad ports, MySQL/BSD issues, and needed to get the box online, so I installed something that worked). I'm interested in BSD's lean-ness, and other aspects, as opposed to other nix'es. Needless to say, testing again using 4.9 this time hasn't been very impressive. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPSec Tunnel w/Racoon between BSD boxes - linksys routers
Thanks for the replies from both of you. The AH point is a good one... specifically the thing I'll need to know. I notified the other party and as soon as I get him off his duff we'll give it a try. Colin Watson wrote: As I understand it, traffic over an IPSEC link flows over standard ports - it's just encapsulated in an ESP packet (or just has data encrpyted if it's transport mode). Port 500 is used for the IKE daemon to negotiate the connection with the other point. The Kame URL: http://www.kame.net/racoon/ under the 'How can I play' heading has a number of tutorials varying in depth. I hope that helps Colin. - Original Message - From: Kevin Berrien [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 11:26 PM Subject: Re: IPSec Tunnel w/Racoon between BSD boxes - linksys routers To answer my own question, looks as if 7000, 7002, 500. Or just 500? Kevin Berrien wrote: I'm looking for tunnel between two 4.8-stable boxes using IPSEC/Racoon. However, both boxes are protected by Linksys cable/router's. Thus, the BSD boxes are behind the routers. I took a general gandor through the docs, websites... through which ports would this traffic flow.. and is this fairly possible? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
IPSec Tunnel w/Racoon between BSD boxes - linksys routers
I'm looking for tunnel between two 4.8-stable boxes using IPSEC/Racoon. However, both boxes are protected by Linksys cable/router's. Thus, the BSD boxes are behind the routers. I took a general gandor through the docs, websites... through which ports would this traffic flow.. and is this fairly possible? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPSec Tunnel w/Racoon between BSD boxes - linksys routers
To answer my own question, looks as if 7000, 7002, 500. Or just 500? Kevin Berrien wrote: I'm looking for tunnel between two 4.8-stable boxes using IPSEC/Racoon. However, both boxes are protected by Linksys cable/router's. Thus, the BSD boxes are behind the routers. I took a general gandor through the docs, websites... through which ports would this traffic flow.. and is this fairly possible? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HP or Compaq servers.
The real key is, getting BSD popular/requested enough that it's tested/supported officially by HP et. al! That would be good to have a webpage with server configurations that run under FreeBSD. Don't you think so? Keeping the list of supported individual components up-to-date is a significant challenge. Trying to keep a list of complete system configurations available is exponentially more difficult, but you're welcome to try. You first might want to compute the number of permutations from choosing, say, 6 components per system out of 1000 components. I hope everyone will help to keep this list up to date. I hope you too. Components are listed in supported hardware but I will ask people to send me the updates. I will do it as soon as I get my new servers done. gregory ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't get splash scr working - arg
Excellent, Either the defaults file or adding the vesa_load did the trick. Trouble is, kernel boots so fast I get like 3 seconds on the screen ha!. Was more a desire to get working what I could not, than anything else. Thanks! Supote Leelasupphakorn wrote: According to the comment in file /boot/defaults/loader.conf, the file /boot/defaults/loader.conf must be untouched but edit whatever you want in /boot/loader.conf instead. I recommend you should restore the original version of /boot/defaults/loader.conf first, append vesa_load=YES line in your /boot/loader.conf and use only 320*200 size of images (according to 'man splash') such as -- /boot/loader.conf userconfig_script_load=YES vesa_load=YES splash_bmp_load=YES bitmap_load=YES bitmap_name=your_splash_file_with_full_path After done, it must be work for you. Cheer, ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 4.8-RELEASE mutt color (color)
Speaking of color. Does anyone have a good tutorial/script to add color in bash as one finds in the newer linux distributions? Kyle Jamieson wrote: I'm running 4.8-RELEASE; relatively new to FreeBSD. I get color in vim and ls, but not mutt. How can I get color in mutt? - yes, I've tried setting TERM=xterm-color; no change. - yes, I've installed ncurses; no change. - yes, I realize this may be a mutt-specific q, but I'm asking for help here. Thanks for any help you can give. __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i want to switch from windows to freebsd, please help me.
I second on 4.8-stable. Been playing for FreeBSD for about a month now, but before I had a lot of hassles with 5, 5.1. I got the experience I expected using 4.8. I'd recommed FreeBSD 4.8 to you, since 5.1 has still some issues. Here is how to get FreeBSD: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't get splash scr working - arg
4.8 has the following /boot/loader.conf /boot/defaults/loader.conf I edited both, and configured both individually.. with no success. :::sample from /boot/loader.conf userconfig_script_load=YES splash_bmp_load=YES bitmap_load=YES bitmap_name=splash.bmp :::sample from /boot/defaults/loader.conf loader_conf_files=/boot/device.hints /boot/loader.conf /boot/loader.conf.local /boot/nextboot.conf verbose_loading=NO# Set to YES for verbose loader output ## ### Splash screen configuration ## splash_bmp_load=YES# Set this to YES for bmp splash screen! splash_pcx_load=NO# Set this to YES for pcx splash screen! vesa_load=NO# Set this to YES to load the vesa module bitmap_load=YES# Set this to YES if you want splash bitmap_name=/boot/splash.bmp# Set this to the name of the bmp or pcx file bitmap_type=splash_image_data Like I said, tried every combination, the stuff off that well know splash website (refers to 3.2) and some of the oddities with 5.0 (placement of bitmap file). Anyone have any suggestion? Install is stock 4.8-Stable except for a slimmed down kernel I compiled. I'm not aware of any kernel option related to the slash. Also, is there a way I can get a verbose logging of the boot process so I can track this down. Not that it's a big deal, but when I dig into a new OS like this, if I can't do it - I make my self succeed in order to learn the os better, or toss it aside as non-mature. Supote Leelasupphakorn wrote: Hi, Have you edited /boot/loader.conf (see loader.conf(5)) and include the following lines: splash_bmp_load=YES bitmap_load=YES bitmap_name=mysplash.bmp for more information refer to 'man splash' GoodLuck, ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Can't get splash scr working - arg
As I've been playing with FreeBSD 4.8 stable on a test box, I came across the splash screen feature after building my own kernel. Figured I'd give it a try for the heck of it. Anyways, I've had no success! I've followed the various (not always identical) tutorials on www.baldwin.cx/splash/, free-bsd.org the manual page. Other than my kernel my install is stock 4.8. I'm I missing something obvious? Anyone know if a better tutorial? Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't get splash scr working - arg
No luck with the link, or placing the splash file in the other dirs. I did find my splash was a bit off on the res, but using a 320x200x8 replacement, and playing around a bit didn't help. I get no flicker or anything that would indicate it's even suggesting of trying a graphics mode. As for dmesg, I get no messages regarding the splash modules or anything. This is using dmesg , or w/ -a as I'm familiar with it. If this doesn't work, please send as the output of the relevant dmesg lines, i.e. the beginning, where the kernel modules are preloaded and some message about the splash module should appear. Ciao Siegbert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: smbd errors - bind fialed on port
Hum, I've never had to define that before on any linux config. I'll give it a try. tnx Derrick Ryalls wrote: [2003/06/18 16:12:08, 0] smbd/server.c:main(791) smbd version 2.2.8a started. Copyright Andrew Tridgell and the Samba Team 1992-2002 [2003/06/18 16:12:08, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use Thoughts? I know its not the install, but why/what could be bound to port 139?? ___ check your smb.conf file and look for the line similar to this: interfaces = 192.168.0.1/24 the ip listed should be the interface's ip. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
