RE: Manual mount root issue
My FreeBSD 5.2.1 server had a 4.5 GB HDD. I decided to upgrade it with a larger drive. I installed a new drive on the second IDE channel which made it ad2, of course, my original drive was ad0. I created a partition, boot loader and matching slices on the new drive. Then I copied the old drive to the new drive. Once finished, I removed the original drive and installed the new one on the primary channel. When I booted up everything appeared normal, but when the system starts to mount / it gives no error or warning and just drops to a Manual mount root specification prompt. If type ufs:ad0s1a it boots up and everything is perfect. This is the same slice / was on the old drive as well. I have tried the following with no success: Checked /etc/fstab boot0cfg -v -B ad0 bsdlabel -B ad0s1 tried booting from a cd, going into post install config, fdisk, and set the partition as bootable, it already was. Since upgrading the hard disk, I have upgraded the system to 5.5 and then to 6.2. This system has been working great for over a week now, just have this boot problem. -- Here is my fstab: /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 -- Output from bsdlabel # bsdlabel ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 585018626 10485764.2BSD 2048 16384 28552 b: 10485760 swap c: 5860672020unused0 0 # raw part, don't edit -- Output from boot0cfg # boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 1023:254:63 63586067202 version=1.0 drive=0x80 mask=0xf ticks=182 options=nopacket,update,nosetdrv default_selection=F1 (Slice 1) Thanks, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ACPI causing trouble for X in 5.2
Trey Sizemore wrote: Jaroslaw Nozderko wrote: OS: FreeBSD 5.2-RC2 (MAC - biba,mls) Hi, I have problem with X on 5.2-RC2. Sometimes the whole system hangs when I start X by startx or 'setpmac mls/equal startx' (with MAC policies loaded). In about 30% of attempts it hangs on XFree startup messages and hard reset is required. The problem occurs a little bit too often for some unrelated accident and it doesn't occur at all on 5.1-RELEASE (the same hardware and configuration). Does anyone have similar problem ? Regards, Jarek Yes, see my post from earlier today called Can't shutdown, logout, or restart cleanly. I have not run 5.1-RELEASE before, so I can't say if it didn't happen there, but it definitely happens with 5.2-CURRENT. I'm at my wit's end trying to find out why! Per a post I received on bsdforums.com, try booting up with ACPI turned off. This can be done in 5.1 and later by choosing option 2 in the boot menu (Boot FreeBSD with ACPI disabled). Once I did this, it worked like a champ. I'm not sure why earlier versions may not have been affected by this or if it only affects certain hardware. Let me know if this worked for you. I have the same problem on two builds of 5.2, one is a Sony Vaio PCG-F360 Laptop (PII 400MHz) and the other is a newer P4 system with Asus mother board. Both worked fine with 5.1 and both broke with 5.2. I was able to work around this problem by booting up with ACPI disabled. Is there a known issue with ACPI that is being worked on for 5.2 or did someone already submit a bug report? Thanks, David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI causing trouble for X in 5.2
Robert Watson wrote: On Fri, 16 Jan 2004, David Cramblett wrote: I have problem with X on 5.2-RC2. Sometimes the whole system hangs when I start X by startx or 'setpmac mls/equal startx' (with MAC policies loaded). In about 30% of attempts it hangs on XFree startup messages and hard reset is required. The problem occurs a little bit too often for some unrelated accident and it doesn't occur at all on 5.1-RELEASE (the same hardware and configuration). Does anyone have similar problem ? Yes, see my post from earlier today called Can't shutdown, logout, or restart cleanly. I have not run 5.1-RELEASE before, so I can't say if it didn't happen there, but it definitely happens with 5.2-CURRENT. I'm at my wit's end trying to find out why! Per a post I received on bsdforums.com, try booting up with ACPI turned off. This can be done in 5.1 and later by choosing option 2 in the boot menu (Boot FreeBSD with ACPI disabled). Once I did this, it worked like a champ. I'm not sure why earlier versions may not have been affected by this or if it only affects certain hardware. Let me know if this worked for you. I have the same problem on two builds of 5.2, one is a Sony Vaio PCG-F360 Laptop (PII 400MHz) and the other is a newer P4 system with Asus mother board. Both worked fine with 5.1 and both broke with 5.2. I was able to work around this problem by booting up with ACPI disabled. Is there a known issue with ACPI that is being worked on for 5.2 or did someone already submit a bug report? Thanks, David I was seeing this on my Dell Latitude notebook from a couple of years ago (C600). I found that the problem went away when I switched off either ACPI or device apic, so it looks like it's basically an interrupt problem of some sort. I'm running with the r128 kernel module for DRI, and John Baldwin suggested that it might be part of the problem. I've also been experiencing continuing ATA problems, so it may well be that a combination of ACPI and apic changes has resulted in improper handling/routing/... of interrupts on the box. You might want to check and see if there are any BIOS upgrades available for your system -- as ACPI support evolves, older systems with more questionable ACPI sometimes work less well. A number of vendors have released BIOS updates to address this. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Senior Research Scientist, McAfee Research Seems kinda strange that it would work fine in 5.1 and then break in 5.2, if it were hardware/bios related. Keep in mind, one of my systems is less than a year old P4 system (you seem to just be referencing my older laptop), so were not just talking about old pre-ACPI hardware/bios either. I may be wrong, but it seems something has changed for ACPI between 5.1 and 5.2, either in the FreeBSD implementation or in the specification that would require a BIOS update on my newer hardware and make the older hardware need it disabled. -- David Cramblett Multnomah Education Service District phn 503-257-1535 fax 503-257-1538 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: audigy support
http://www.opensound.com David Martynas P wrote: Maybe has somebody idea : how to support the audigy sound card on FreeBSD 4.7 ? __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: audigy support
how can one extract the gziped patch from that second link? Orion Hodson wrote: There are currently two patches for the Audigy sound cards. http://chibis.persons.gfk.ru/audigy and: http://www.freebsd.org/cgi/getmsg.cgi?fetch=664373+686499+/usr/local/www/db/tex t/2003/freebsd-hackers/20030216.freebsd-hackers+raw Each patch has it's merits. The author of the latter, Orlando Bassotto, is in the process of merging the two at present and we hope to have Audigy support in the tree within a short time frame. Making these patches work on a 4.7 box probably isn't that hard if you really want it now. Regards - Orion To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: gif tunnels?
I have a similar configuration, what are your internal router/firewall ip's? From your diagram, I would think something like 10.1.0.1 and 10.2.0.1 ?? so where you have: # ifconfig gif0 inet 10.255.255.1 10.255.255.2 netmask 255.255.255.252 My config would have: # ifconfig gif0 10.1.0.1 10.2.0.1 netmask 0x Hope that helps, I run VPN tunnels to two separate boxes with similar configurations, forming kinda of a triangle VPN if you will. David Aaron Burke wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Krassimir Slavchev Sent: Friday, February 21, 2003 12:21 AM To: [EMAIL PROTECTED] Subject: gif tunnels? Hello All, I have: Private Net 1 Firewall 1Firewall 2 Private Net 2 --- --- | 10.1.0.0/24 || FBSD 4.7 |--//--| FBSD 4.7 || 10.2.0.0/24 | --- --- |__tunnel__| I want to configure tunnel between Private Net 1 and Private Net 2 and can not get tunnel to work when Public IP of Firewall 1 and Firewall 2 are from same subnet. If public IPs of my firewalls are from different subnets all works fine. On Firewall 1 I do: # ifconfig gif0 create # gifconfig gif0 x.y.z.1 x.y.z.2 # ifconfig gif0 inet 10.255.255.1 10.255.255.2 netmask 255.255.255.252 # route add -net 10.2.0.0/24 10.255.255.2 On Firewall 2 I do: # ifconfig gif0 create # gifconfig gif0 x.y.z.2 x.y.z.1 # ifconfig gif0 inet 10.255.255.2 10.255.255.1 netmask 255.255.255.252 # route add -net 10.1.0.0/24 10.255.255.1 Is there any way to get this to work? You may want to check out http://www.nullplusone.com/vpn .It describes a slightly different situation. Here there is a link from the 192.168.0.0/24 to 10.1.1.0/24. Thanks in advance Hope this site is some help To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- David Cramblett To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: from GNOME to KDE
if you have KDE installed, try the program switchdesk on Linux. Gary D Kline wrote: A friend set up GNOME on a Redhat system that I successfully networked to my three BSD servers. How do I switch to KDE from Gnome? Also, I would like to set up a similar KDE account here formy seven-year-old. She likes unix better than her windows computer---can't imagine whre she gets her biases :-| Anyway, I would like to set up/switch to KDE on both platforms. I'd be much obliged for any clues! tia, gary -- David Cramblett To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: FreeBSD 4.7-REL-p3 and an IPsec connection to Linksys BEFVP41
Just a quick note, what Linksys box do you have? Are you sure it supports IPsec? I have seen many that support IPsec pass through, but I have not seen any that support IPsec. George Hartzell wrote: Thanks for the response! I'll dig a bit more and either report success or come back with more data. Lars Eggert writes: [...] All three aproaches above can be made to work, as explained by the tutorials you cite. The question is, which one is supported by your Linksys box? *That* is the 64-million dollar question. I'll keep at it. g. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Help Building Mozilla
Hello, I am trying to add spell checking support to mozilla. I have download the spell checker from cvs. First I tried adding the src and patching the port directly, of course it wiped that out when I started the port install again. So I downloaded the src for 1.2.1 from mozilla and added the spell checker source and patched that code. I tried to build it and just can't seem to find any instructions for building mozilla from source. The best I have found is running the configure script and then running gmake or make (different instructions) -f client.mk build. However that is not working, getting Missing operator errors. There are really no instructions for building Mozilla from src on the Mozilla site, other than there auto installers for Linux, etc.. Seems like if the process is so convoluted hat they would have some instructions. Is there a way to pull down the src, modify it and then build it using the freebsd ports? Thanks for your help. David -- David Cramblett Axis Integrated 503-730-6201 -- David Cramblett Axis Integrated 503-730-6201 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Restricting some user only to internal email
I believe postfix, and probably other MTA's, can support user based relaying. However it would also be easy to setup two mail server's. One that only relayed mail internally and one that relayed mail externally as well, if you budget supports two mail servers that is. Then just set the smtp server appropriately for each of the mail clients. David BSD Freak wrote: Hi all, I need to be able to restrict certain users only to be able to email within the company, while other need to be be able to send email both internally and externally? Any ideas would be greatly apprciated -Thanks in advance. - NEW to mBox, receive faxes to any email address! Find out more http://www.mbox.com.au/fax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- David Cramblett Axis Integrated 503-730-6201 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Saga continues:Make Buildworld fails 4.5-R - 4.7 R
I have had problems with make world related to bad/incompatible memory, any chance this is a problem for you? David Lowell Gilbert wrote: Blake Swensen [EMAIL PROTECTED] writes: Just for giggles I cvsup'ed the RELENG_4_5 sources (yes, I removed the /usr/obj/* files) and did a 'make buildworld' on those... I the build crashed with: [snip] /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/../libio/fstream.cc: In method `fstream::fstream(int)': /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/../libio/fstream.cc:110: Internal compiler error. /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/../libio/fstream.cc:110: Please submit a full bug report. /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/../libio/fstream.cc:110: See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. *** Error code 1 Stop in /usr/src/gnu/lib/libstdc++. *** Error code 1 [snip] Okay, this is pretty wacky. Are you sure you're getting the system compiler? Have you, perhaps, installed another one (e.g., from ports)? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Xine failing to Compile on 5.0 release
Any one got an idea on this:
/usr/include/sys/ipc.h:80: syntax error before ushort
main.c: In function `parse_visual':
main.c:274: warning: implicit declaration of function `strcasecmp'
main.c: In function `xrm_parse':
main.c:341: warning: implicit declaration of function `gethostname'
main.c: In function `load_audio_out_driver':
main.c:686: warning: implicit declaration of function `strncasecmp'
gmake[4]: *** [main.o] Error 1
gmake[4]: Leaving directory
`/usr/ports/graphics/xine/work/xine-ui-0.9.18/src/xi
tk'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory
`/usr/ports/graphics/xine/work/xine-ui-0.9.18/src/xi
tk'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/usr/ports/graphics/xine/work/xine-ui-0.9.18/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/graphics/xine/work/xine-ui-0.9.18'
gmake: *** [all] Error 2
*** Error code 2
Stop in /usr/ports/graphics/xine
*** snippet from ipc.h around line 80
/*
* XXX almost all members have wrong types.
*/
struct ipc_perm {
ushort cuid; /* creator user id */
ushort cgid; /* creator group id */
ushort uid; /* user id */
ushort gid; /* group id */
ushort mode; /* r/w permission */
ushort seq; /* sequence # (to generate unique msg/sem/shm id) */
key_t key; /* user specified msg/sem/shm key */
};
Thanks,
David
--
David Cramblett
Axis Integrated
503-730-6201
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: cvsup done, now what]
You need to build and install the source. There is a really good doc on this in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html It is not to tough, good luck. David Darryl Hoar wrote: Greetings. I downloaded the ISO image for 4.7-release and burned it to a cd. I installed this on a server of mine. I then copied /usr/share/examples/cvsup/stable-supfile to /etc. Edited stable-supfile to my desires. then I cvsup /etc/stable-supfile this completed. What do I need to do next to be running stable (instead of release) ? thanks, Darryl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- David Cramblett Network and Information Services Multnomah Education Service District phn: 503-257-1535 fax: 503-257-1538 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: IPFW, natd, redirect_address help needed
Do you have gateway_enable=YES in your firewall? Can you get packets through both directions just fine with the firewall set to OPEN? David Terrac Skiens wrote: Hi there, I have been trying to set up an embedded system from soekris, running a small version of freebsd on it's internal compact flash hard disk. The machine is built, I have remote access to it and I intend to use it as a firewall + nat appliance. Directing traffic from machines internally to external IP addresses. I have gotten everything running, however my test for the machines behind the new firewall keep failing. I can ping the firewall itself, but not anything past it. The pings just dissapear. From the firewall I can ping anythign by either hostname or IP. What I have not figured out is why my machines behind the firewall cannot ping out past the firewall, or get any other traffic out either. my ipfw list is: --- 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 00400 deny ip from any to 172.16.0.0/12 via sis0 00500 deny ip from any to 192.168.0.0/16 via sis0 00600 deny ip from any to 0.0.0.0/8 via sis0 00700 deny ip from any to 169.254.0.0/16 via sis0 00800 deny ip from any to 192.0.2.0/24 via sis0 00900 deny ip from any to 224.0.0.0/4 via sis0 01000 deny ip from any to 240.0.0.0/4 via sis0 01100 divert 8668 ip from any to any via sis0 01200 deny ip from 172.16.0.0/12 to any via sis0 01300 deny ip from 192.168.0.0/16 to any via sis0 01400 deny ip from 0.0.0.0/8 to any via sis0 01500 deny ip from 169.254.0.0/16 to any via sis0 01600 deny ip from 192.0.2.0/24 to any via sis0 01700 deny ip from 224.0.0.0/4 to any via sis0 01800 deny ip from 240.0.0.0/4 to any via sis0 01900 allow tcp from any to any established 02000 allow ip from any to any frag 1 deny log logamount 100 tcp from any to any in recv sis0 setup 10100 allow tcp from any to any setup 10200 allow udp from any to any 53 keep-state out xmit sis0 10300 allow udp from any to any 53 keep-state in recv sis0 10400 allow udp from any to any 123 keep-state out xmit sis0 10500 allow udp from any to any 123 keep-state in recv sis1 10600 allow tcp from any to any 53 keep-state out xmit sis0 10700 allow tcp from any to any 53 keep-state in recv sis1 10800 allow tcp from any to any 25 keep-state out xmit sis0 10900 allow tcp from any to any 25 keep-state in recv sis1 11000 allow tcp from any to any 22 keep-state out xmit sis0 11100 allow tcp from any to any 22 keep-state in recv sis1 11200 allow udp from me to any 67 keep-state out xmit sis0 11300 allow icmp from any to any 65535 deny ip from any to any and my netstat -rn is: --- Routing table: -- DestinationGatewayFlags Netif Use default66.180.229.177 UGScsis02 10.1.1.0/24link#2 UC sis10 xxx.xxx.xxx.xxxlink#1 UC sis00 - network xxx.xxx.xxx.xxxlink#1 UHLWsis00 - gateway 127.0.0.1 127.0.0.1 UH lo0 0 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- David Cramblett Network and Information Services Multnomah Education Service District phn: 503-257-1535 fax: 503-257-1538 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: IPFW, natd, redirect_address help needed
well you could simply do an ipfw flush and then use ipfw command line to add back the rule for the loopback device and the natd divert line (looks like your using natd?), then do a: ipfw add pass all from any to any and make sure that you can send and recive traffic in both directions without any deny firewall rules in place. If you want to test with the current rules in place, you may want to add a line to log all connections, if you have the disk space for it and then tail -f your security log and see what packets are getting denied/accepted and why. David Terrac Skiens wrote: since this is a super small distribution I do not have the default open, closed, and client firewall configs. The set I am using is based on the client one though, however I adjusted it to allow traffic from the inside to the outside on specific ports and hopefully keep-state to let the returning packets back in. Thats right isn't it? -terrac On Tue, 5 Nov 2002, David Cramblett wrote: Do you have gateway_enable=YES in your firewall? Can you get packets through both directions just fine with the firewall set to OPEN? David Terrac Skiens wrote: Hi there, I have been trying to set up an embedded system from soekris, running a small version of freebsd on it's internal compact flash hard disk. The machine is built, I have remote access to it and I intend to use it as a firewall + nat appliance. Directing traffic from machines internally to external IP addresses. I have gotten everything running, however my test for the machines behind the new firewall keep failing. I can ping the firewall itself, but not anything past it. The pings just dissapear. From the firewall I can ping anythign by either hostname or IP. What I have not figured out is why my machines behind the firewall cannot ping out past the firewall, or get any other traffic out either. my ipfw list is: --- 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 00400 deny ip from any to 172.16.0.0/12 via sis0 00500 deny ip from any to 192.168.0.0/16 via sis0 00600 deny ip from any to 0.0.0.0/8 via sis0 00700 deny ip from any to 169.254.0.0/16 via sis0 00800 deny ip from any to 192.0.2.0/24 via sis0 00900 deny ip from any to 224.0.0.0/4 via sis0 01000 deny ip from any to 240.0.0.0/4 via sis0 01100 divert 8668 ip from any to any via sis0 01200 deny ip from 172.16.0.0/12 to any via sis0 01300 deny ip from 192.168.0.0/16 to any via sis0 01400 deny ip from 0.0.0.0/8 to any via sis0 01500 deny ip from 169.254.0.0/16 to any via sis0 01600 deny ip from 192.0.2.0/24 to any via sis0 01700 deny ip from 224.0.0.0/4 to any via sis0 01800 deny ip from 240.0.0.0/4 to any via sis0 01900 allow tcp from any to any established 02000 allow ip from any to any frag 1 deny log logamount 100 tcp from any to any in recv sis0 setup 10100 allow tcp from any to any setup 10200 allow udp from any to any 53 keep-state out xmit sis0 10300 allow udp from any to any 53 keep-state in recv sis0 10400 allow udp from any to any 123 keep-state out xmit sis0 10500 allow udp from any to any 123 keep-state in recv sis1 10600 allow tcp from any to any 53 keep-state out xmit sis0 10700 allow tcp from any to any 53 keep-state in recv sis1 10800 allow tcp from any to any 25 keep-state out xmit sis0 10900 allow tcp from any to any 25 keep-state in recv sis1 11000 allow tcp from any to any 22 keep-state out xmit sis0 11100 allow tcp from any to any 22 keep-state in recv sis1 11200 allow udp from me to any 67 keep-state out xmit sis0 11300 allow icmp from any to any 65535 deny ip from any to any and my netstat -rn is: --- Routing table: -- DestinationGatewayFlags Netif Use default66.180.229.177 UGScsis02 10.1.1.0/24link#2 UC sis10 xxx.xxx.xxx.xxxlink#1 UC sis00 - network xxx.xxx.xxx.xxxlink#1 UHLWsis00 - gateway 127.0.0.1 127.0.0.1 UH lo0 0 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
