Re: NIC 1 gigabit
On Wed, 23 Mar 2005 [EMAIL PROTECTED] wrote: Hi, I have trouble with my NIC. I'm using Server Mainboard Intel (I forgot the model), there is 2 NICs; the one is 100Mbps other is 1 gigabit. I use this for my web server with freeBSD 5.1-RELEASE. NIC 1 gigabit is not detected and recognised neither by freeBSD the other is fine and working. What should I do ? Should I recompile kernel ? And How ? Sorry, my English is bad. Thanks. Hope you can read english... http://www.freebsd.org/doc/ Have a read through the above thoroughly please. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: firewall
On 2005-03-23 07:41, [EMAIL PROTECTED] wrote: I just build a web server, with apache-2.xx w/ php and mysql-1.4xx. How to configure firewall in my web server ? - The FreeBSD Handbook has several sections devoted to firewalls and their configuration. - The archives of this mailing list have dozens of suggestions for firewall setups. - The articles at O'Reilly's OnLamp site have even more firewall setup examples. You can find a lot of material online. Just start looking at pages like: http://www.FreeBSD.org/docs.html http://lists.freebsd.org/pipermail/freebsd-questions/ http://www.onlamp.com/pub/ct/13 http://ezine.daemonnews.org/ Must I download kernel source and recompile ? Nope. If I must download kernel source, where I can found it ? The sources for the FreeBSD base system are in /usr/src. The kernel is under /usr/src/sys. The Handbook contains detailed instructions about rebuilding everything from source. I'm using freebsd 5.1-RELEASE. Thanks. That's a very old and experimental release of the 5.X branch. You should really consider upgrading to (or reinstalling with) a more recent 5.X release. 5.3-RELEASE is teh latest release that is available on the mirrors right now, and if you can wait a few days, 5.4-RELEASE is scheduled to be out sometime during the first days of April. - Giorgos ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
security or lack thereof
So, is it FreeBSD policy to ignore security bug reports? I sent the following bug report to [EMAIL PROTECTED] on Feb. 19th, 2005 and it still hasn't been acted on. This total lack of action on an extremely simple (and silly) three year old bug doesn't give one the warm fuzzies. Heck, it took 48 hours to get a response from a security officer, and another 24 hours to get something from the guilty developer. From: [EMAIL PROTECTED] (John Nemeth) Date: Sat, 19 Feb 2005 21:46:42 -0800 To: [EMAIL PROTECTED] Subject: rexecd root lockout I'm working on converting NetBSD's rexecd to use PAM and I was looking at FreeBSD's rexecd for ideas. In the process I noticed that FreeBSD's version of rexecd is supposed to disallow its use by uid 0. However, there is a bug in the PAM conversion of FreeBSD's rexecd.c that disables that feature. The change was made in revision 1.29 of rexecd on May 2, 2002. The problem is around line 192 and exists in the latest version. As far as I can tell the problem affects all FreeBSD 5.x releases. The problem is that the following line: if ((pwd-pw_uid == 0 no_uid_0) || *pwd-pw_passwd == '\0' || was changed to: if ((pwd = getpwnam(user)) == NULL || (pwd-pw_uid = 0 no_uid_0) || Note that the second version assigns 0 to pwd-pw_uid instead of comparing it thus forcing the uid 0 test to always fail. The fix is to change the second line to: if ((pwd = getpwnam(user)) == NULL || (pwd-pw_uid == 0 no_uid_0) || Note that I haven't tested any of this and found it by reading the code. The fix is also untested, but given the simplicity it should be fine. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ip_reass() - possibly incorrect goto
On Tue, 22 Mar 2005, 12:08-0800, [EMAIL PROTECTED] wrote:
Hi hackers, I am looking at the ip_reass() routine. In case of the
1st fragment we create the reassembly queue. After the queue has
been inserted in the hash bucket, the if () code does a goto
inserted. Should this be changed to goto done instead? Any code
that is executed for the 1st fragment, like frag per packet limiting
and complete reassembly are not valid. Am I mistaken?
Yep, it seems you are right. The second micro optimization - drop the
fragment early if maxfragsperpacket == 0.
Andre, Mike, what do you think?
Index: ip_input.c
===
RCS file: /home/ncvs/src/sys/netinet/ip_input.c,v
retrieving revision 1.299
diff -u -r1.299 ip_input.c
--- ip_input.c 16 Mar 2005 05:27:19 - 1.299
+++ ip_input.c 23 Mar 2005 13:12:00 -
@@ -801,8 +801,8 @@
u_int8_t ecn, ecn0;
u_short hash;
- /* If maxnipq is 0, never accept fragments. */
- if (maxnipq == 0) {
+ /* If maxnipq or maxfragsperpacket are 0, never accept fragments. */
+ if (maxnipq == 0 || maxfragsperpacket == 0) {
ipstat.ips_fragments++;
ipstat.ips_fragdropped++;
m_freem(m);
@@ -918,7 +918,7 @@
fp-ipq_dst = ip-ip_dst;
fp-ipq_frags = m;
m-m_nextpkt = NULL;
- goto inserted;
+ goto done;
} else {
fp-ipq_nfrags++;
#ifdef MAC
@@ -998,8 +998,6 @@
m_freem(q);
}
-inserted:
-
/*
* Check for complete reassembly and perform frag per packet
* limiting.
%%%
--
Maxim Konovalov
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: security or lack thereof
John Nemeth wrote: So, is it FreeBSD policy to ignore security bug reports? I sent the following bug report to [EMAIL PROTECTED] on Feb. 19th, 2005 and it still hasn't been acted on. This total lack of action on an extremely simple (and silly) three year old bug doesn't give one the warm fuzzies. Heck, it took 48 hours to get a response from a security officer, and another 24 hours to get something from the guilty developer. I'm a nobody as far as FreeBSD src trees, bugs, etc go, but I didn't see a PR in the bug reports database (link on the left of the main freebsd.org website). This is probably why it got shuffled into a crack somewhere, but take my bits with a grain of salt. If you haven't, please submit your patch via the bug system here: http://www.freebsd.org/send-pr.html Thanks for the bug find.. Eric -- Eric AndersonSr. Systems AdministratorCentaur Technology I have seen the future and it is just like the present, only longer. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: security or lack thereof
On 3/22/05 9:04 PM, John Nemeth wrote: So, is it FreeBSD policy to ignore security bug reports? I sent the following bug report to [EMAIL PROTECTED] on Feb. 19th, 2005 and it still hasn't been acted on. This total lack of action on an extremely simple (and silly) three year old bug doesn't give one the warm fuzzies. Heck, it took 48 hours to get a response from a security officer, and another 24 hours to get something from the guilty developer. Hi John, I'm sorry for the delay. I could give you a list of excuses, but suffice it to say that the simple (and silly) bug had lower priority than several other issues in our queue. We should have sent you a status update, though: that's my fault. Better late than never, I hope? Initially we believed the bug was more serious than you had reported, since it has an evil side-effect (sets pw_uid to 0). However, we discovered that due to a second bug the impact was limited. Saved by dumb luck (^_^). Anyway, as you might know, we are in a code freeze for 5.4. Coincidentally, just yesterday we asked the Release Engineering team for (and received) permission to apply a fix for 5.4-RELEASE. So you will see the issue addressed shortly. The correct fix is a bit more subtle than that suggested in your original message. I guess I should also mention that we've discussed removing rexec/rexecd entirely (for 6.x releases), since it has been deprecated for over 6 years, and the documentation has discouraged its use for over 11 years. Cheers, -- Jacques A Vidrine / NTT/Verio [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure
Thanks for the patch. This is the outcome: re_probe(): vid 10ec did 8169 hwrev 1000 Andrew - Original Message - From: [EMAIL PROTECTED] (Dag-Erling Smørgrav) Date: Tuesday, March 22, 2005 10:11 am Subject: Re: NIC detected, but won't DHCP or configure Daniel O'Connor [EMAIL PROTECTED] writes: On Tue, 22 Mar 2005 17:30, Andrew Robinson wrote: thanks for the suggestion! I tried that and it didn't seem to change anything: the relevant output of pciconf -lv is still Try if_rl.ko/rl0 No, if_rl will not attach to 8169 cards. Andrew, it seems you have a chip revision which isn't currently supported. Try applying the attached patch, and see if loading if_re.ko results in something like this: re_probe(): vid 10ec did 8169 hwrev 0080 the first two numbers should be exactly as shown, but the last number should be different; let me know what it is. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure
Can you give us the output of pciconf -r pci10:3:0 0:0xff ?
Certainly:
816910ec 02b7 0210
4001 b3004800
09001558
00dc 40200115
f7c20001
0003
Andrew
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: passwd permissions
On Sun, Mar 20, 2005 at 01:26:57PM -0600, H. S. typed: Hey, I'm using FreeBSD on various servers for many time now, and there is something that always bothered me. It is related to /etc/passwd and /etc/pwd.db permissions. I have custom (0640) permissions on these files. However, each time a user Be carefull not to get yourself a false sense of security. e.g. if your goal is to hide information about your users, there are many other ways to get the info without having to open /etc/passwd or /etc/pwd.db example: /usr/sbin/pw usershow -a Ruben [/ttyp0] username:/home/username$ ./pw usershow -a [/ttyp0] username:/home/username$ (no output) Since pw is not setuid, if it can't read any of the passwd files, it will not print the full userlist. I have very customized (and tested, over the years) permissions on the whole filesystem. That is why I wanted to find out why some permissions get back to system defaults whenever I install a port. The most proeminent cases are /usr/local/sbin/ (gets back to rwx rx rx) and /usr/local/www (rwx rx rx and chgrp wheel, I have a different group owning the directory). Any idea about what to fix in order to make the system stop resetting my permissions when I install ports ? Thanks! ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure
Andrew Robinson [EMAIL PROTECTED] writes:
re_probe(): vid 10ec did 8169 hwrev 1000
That's an 8169SB, which is supported in -CURRENT. Try the attached
patch. I'll try to get it merged before 5.4-RELEASE.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
Index: sys/pci/if_rlreg.h
===
RCS file: /home/ncvs/src/sys/pci/if_rlreg.h,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- sys/pci/if_rlreg.h 7 Jan 2005 02:29:18 - 1.49
+++ sys/pci/if_rlreg.h 22 Jan 2005 22:40:52 - 1.50
@@ -147,6 +147,7 @@
#define RL_HWREV_8169 0x
#define RL_HWREV_8169S 0x0400
+#define RL_HWREV_8169SB 0x1000
#define RL_HWREV_8110S 0x0080
#define RL_HWREV_8139 0x6000
#define RL_HWREV_8139A 0x7000
Index: sys/dev/re/if_re.c
===
RCS file: /home/ncvs/src/sys/dev/re/if_re.c,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- sys/dev/re/if_re.c 6 Jan 2005 01:43:10 - 1.38
+++ sys/dev/re/if_re.c 22 Jan 2005 22:40:53 - 1.39
@@ -166,6 +166,8 @@
RealTek 8169 Gigabit Ethernet },
{ RT_VENDORID, RT_DEVICEID_8169, RL_HWREV_8169S,
RealTek 8169S Single-chip Gigabit Ethernet },
+ { RT_VENDORID, RT_DEVICEID_8169, RL_HWREV_8169SB,
+ RealTek 8169SB Single-chip Gigabit Ethernet },
{ RT_VENDORID, RT_DEVICEID_8169, RL_HWREV_8110S,
RealTek 8110S Single-chip Gigabit Ethernet },
{ COREGA_VENDORID, COREGA_DEVICEID_CGLAPCIGT, RL_HWREV_8169S,
@@ -184,6 +186,7 @@
{ RL_HWREV_8139CPLUS, RL_8139CPLUS, C+},
{ RL_HWREV_8169, RL_8169, 8169},
{ RL_HWREV_8169S, RL_8169, 8169S},
+ { RL_HWREV_8169SB, RL_8169, 8169SB},
{ RL_HWREV_8110S, RL_8169, 8110S},
{ RL_HWREV_8100, RL_8139, 8100},
{ RL_HWREV_8101, RL_8139, 8101},
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ziatech 5503 watchdog driver
On Saturday 19 March 2005 04:04 am, Devon H. O'Dell wrote: On Sat, Mar 19, 2005 at 09:43:41AM +0100, Devon H. O'Dell wrote: On Sat, Mar 19, 2005 at 09:02:15AM +0100, Devon H. O'Dell wrote: On Fri, Mar 18, 2005 at 03:55:53PM -0700, Warner Losh wrote: I'm busy writing a Ziatech 5503 watchdog driver for FreeBSD (and porting all the watchdog stuff to DragonFly BSD) and Plan 9. For my driver, I have no way to identify that the system has the driver, so I wanted to make it conditional on Rather, I have no way to identify that the system has the device :). AHA! But I have finally found something that will make my life a little easier, I think. I just noticed a read only register with a default value of 0x80 and tested it. It returns 0x80. Is this enough to test on / probe for? --Devon Sorry, hate replying to myself. Turns out the value here is variable. Assuming I cannot find anything to identify the system, can I simply attach the driver if it is enabled in the configuration file? Yes. See the identify routines for things like apm and pmtimer for examples. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve = http://www.FreeBSD.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
running freebsd in qemu using the -nographic option ?
Hi all, I am running freebsd 5.3 under qemu (a fast IA32 emulator). My host system is linux. Everything works fine, but I want to get rid of this small non-scrollable window, not practical when gcc says I made many many errors :-)... Instead I want to get a console. In qemu's documentation it says : == `-nographic' Normally, QEMU uses SDL to display the VGA output. With this option, you can totally disable graphical output so that QEMU is a simple command line application. The emulated serial port is redirected on the console. Therefore, you can still use QEMU to debug a Linux kernel with a serial console. == So basically what I need is, some how, to tell the freebsd kernel to forward its output/input to a serial port. In linux this is done by supplying the parameter console=ttyS0. Is there something equivalent in FreeBSD ? Thanks for your help, Aziz ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ziatech 5503 watchdog driver
On Wed, Mar 23, 2005 at 02:24:54PM -0500, John Baldwin wrote: On Saturday 19 March 2005 04:04 am, Devon H. O'Dell wrote: On Sat, Mar 19, 2005 at 09:43:41AM +0100, Devon H. O'Dell wrote: Sorry, hate replying to myself. Turns out the value here is variable. Assuming I cannot find anything to identify the system, can I simply attach the driver if it is enabled in the configuration file? Yes. See the identify routines for things like apm and pmtimer for examples. Thanks, looks like I will have to do it this way. :) I'm going to have time for it this weekend, so it should be ready by Monday. --Devon -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve = http://www.FreeBSD.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] pgpKk4l3fEtf6.pgp Description: PGP signature
Re: running freebsd in qemu using the -nographic option ?
In the last episode (Mar 23), Aziz KEZZOU said: I am running freebsd 5.3 under qemu (a fast IA32 emulator). My host system is linux. Everything works fine, but I want to get rid of this small non-scrollable window, not practical when gcc says I made many many errors :-)... In FreeBSD, you can scroll vtys by hitting scroll-lock, then using the up/down/pgup/pgdn/home/end keys to view the scrollback. Hit scroll-lock again to go exit scrollback mode. You could also use screen or pipe your output to less. Instead I want to get a console. In qemu's documentation it says : == `-nographic' Normally, QEMU uses SDL to display the VGA output. With this option, you can totally disable graphical output so that QEMU is a simple command line application. The emulated serial port is redirected on the console. Therefore, you can still use QEMU to debug a Linux kernel with a serial console. == So basically what I need is, some how, to tell the freebsd kernel to forward its output/input to a serial port. In linux this is done by supplying the parameter console=ttyS0. Is there something equivalent in FreeBSD ? To boot using a serial console, add this to /boot/loader.conf: console=comconsole To enable a login prompt on the serial port after the system has come up, edit /etc/ttys and change the ttyd0 line from off to on. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: running freebsd in qemu using the -nographic option ?
Aziz KEZZOU wrote: Hi all, I am running freebsd 5.3 under qemu (a fast IA32 emulator). My host system is linux. Everything works fine, but I want to get rid of this small non-scrollable window, not practical when gcc says I made many many errors :-)... you can scroll it after hittong tthe scroll lock key Instead I want to get a console. In qemu's documentation it says : == `-nographic' Normally, QEMU uses SDL to display the VGA output. With this option, you can totally disable graphical output so that QEMU is a simple command line application. The emulated serial port is redirected on the console. Therefore, you can still use QEMU to debug a Linux kernel with a serial console. == So basically what I need is, some how, to tell the freebsd kernel to forward its output/input to a serial port. In linux this is done by supplying the parameter console=ttyS0. Is there something equivalent in FreeBSD ? in /boot/loader.conf add: console=comconsole that should do it.. Thanks for your help, Aziz ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
NIC detected, but won't DHCP or configure.
Interestingly, i encountered the very same behaviour as explained by
Andrew, with a side note: it works sometimes for me. Despite the fact
that my ethernet seems correctly handled (ifconfig shows the 're'
entry), almost all the time i boot on my notebook (D480V) the state of
the media is no carrier. So, all services which use the network fail
inevitably: dhcp, ntpdate and ntpd.
In order to be able to use the network, sometimes i just must wait some
dozens minutes... or totally reboot and wait some other dozens minutes.
I can't remember of one boot wich went without a hitch.
Here is some (useful?) information:
# uname -a
FreeBSD boboche.thilelli.net 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #1:
Tue Mar 22 20:04:20 CET 2005
root at boboche.thilelli.net:/usr/obj/usr/src/sys/BOBOCHE i386
# pciconf -lv
re0 at pci0:10:0: class=0x02 card=0x08001558 chip=0x816910ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8169 Gigabit Ethernet Adapter'
class= network
subclass = ethernet
= note: it seems that the chip revision, which is the same as Andrew,
is recognized here.
# pciconf -r pci0:10:0 0:0xff
816910ec 02b00017 0210 4004
2001 e8005000
08001558
00dc 40200113
f7c20001
# ifconfig re0
re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING
inet6 fe80::290:f5ff:fe28:cfa8%re0 prefixlen 64 scopeid 0x2
inet 192.168.1.20 netmask 0xff00 broadcast 192.168.1.255
ether 00:90:f5:28:cf:a8
media: Ethernet autoselect (100baseTX full-duplex)
status: active
= note: here is the status after waiting a long time or rebooting.
As for Andrew, it may be noted that i do not encountered this kind of
problem under GNU/Linux (i tested with two live CDs), NetBSD (1.6.2
through 2.0.2) and Windows Server 2003 Ent-Ed.
Because of this particular problem, i can't currently use this machine
in a usefull way, so any advice are welcome too ! :) It wants to say i
can test and apply patch(es) without problem, if any.
Could you try this patch:
http://lists.freebsd.org/pipermail/freebsd-stable/2005-March/013107.html
Ok, just tried it. As i can see there is some improvement here, along
with the following comments:
1/ When rebooting the system, the bad/old behaviour seems to happen
systematically;
2/ When powered-off then powered-on, the behaviour seems to be more
correct. Nevertheless, i encountered the old problem more than
*one* time... roughly ~40% to 50% :(
Just for information, i just build and install a -CURRENT FreeBSD system:
# uname -a
FreeBSD boboche.thilelli.net 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Wed Mar
23 22:24:26 CET 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/BOBOCHE i386
It doesn't work better (i saw the same _bad_ behaviour) but this time,
the kernel send more messages:
# dmesg | egrep ^re0:
re0: RealTek 8169S Single-chip Gigabit Ethernet port 0x2000-0x20ff mem
0xe8005000-0xe80050ff irq 19 at device 10.0 on pci0
re0: Ethernet address: 00:90:f5:28:cf:a8
re0: link state changed to UP
re0: link state changed to DOWN
re0: link state changed to UP
re0: link state changed to DOWN
re0: link state changed to UP
re0: link state changed to DOWN
re0: link state changed to UP
re0: link state changed to DOWN
re0: link state changed to UP
re0: link state changed to DOWN
re0: link state changed to UP
It seems to be the link which is the problem... but i'm not really sure
since this hardware works with other Unix-like systems and because i
encountered the same problem in another place (at work).
Any clue?
--
-jpeg.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd 5.3 hangs under heavy load????
Hi again, I have two Seagate SCSI drives 36GB and 8GB RAM and installed 5.3-REL with PAE and SMP support. Now the problem arises that the system hangs under heavy load and there are no error messages nothing. I have to hard boot it everytime it hangs. Then I tried with only SMP and the machine still hangs. I tried using New memory and a Maxtor 36Gb SCSI drive , still hangs but was up for longer perios 13hrs.. Any one know about this problem. Alos tried with 5.4-Prerelease same results. Any help would be great, Scott any help. Thanks Aman Rojer wrote: Amandeep Pannu wrote: Hi all, I have two Seagate SCSI drives 36GB and 8GB RAM and installed 5.3-REL with PAE and SMP support. Now the problem arises that the system hangs under heavy load and there are no error messages nothing. I have to hard boot it everytime it hangs. Roger Comments: PAE must have something to do with this. i have similar reports from fellow admins (they run large free mail service): machines with lots (4+ gigs) of memory, 5.3R, SMP and PAE enabled just refused to cooperate, freezing and crashing all the way under load. sadly, having no time to dive into gory details, they just installed Linux on those and all has been going well since that... the point is: PAE and large memory configurations in general need more testing. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel documentation and specification
Where can i find resources about the freebsd kernel? I read over the developers handbook, and the architecture handbook, and both provide very little information i need. Also if anyone can recommend irc channels to visit where developers are to be found. I visited #BsdCode of efnet, but it was keyed not too long ago. Some questions for instance are the use of sse, mmx, and fpu register and commands inside the kernel. How is the development organized. Is it just a jungle where people choose what they want to improve and expand in the kernel and then submit their code? What type of process scheduling the freebsd uses, interprocess communication and more.. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel documentation and specification
On Thu, Mar 24, 2005, klowd9 - wrote: Where can i find resources about the freebsd kernel? I read over the developers handbook, and the architecture handbook, and both provide very little information i need. Also if anyone can recommend irc channels to visit where developers are to be found. I visited #BsdCode of efnet, but it was keyed not too long ago. Some questions for instance are the use of sse, mmx, and fpu register and commands inside the kernel. How is the development organized. Is it just a jungle where people choose what they want to improve and expand in the kernel and then submit their code? What type of process scheduling the freebsd uses, interprocess communication and more.. Reading the CVS logs for the relevant files should give you ideas about who might be able to answer your questions. However, you shouldn't expect that people have time to answer lots of questions. Of course, it helps if your interest is in the context of contributing something back to the project. Kirk's book, ``The Design and Implementation of the FreeBSD Operating System'' probably contains the answers to basic questions about scheduling and IPC. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel documentation and specification
Reading the CVS logs for the relevant files should give you ideas about who might be able to answer your questions. However, you shouldn't expect that people have time to answer lots of questions. Of course, it helps if your interest is in the context of contributing something back to the project. Kirk's book, ``The Design and Implementation of the FreeBSD Operating System'' probably contains the answers to basic questions about scheduling and IPC. I considered purchasing that book, which is very very good imo, but a bit overpriced at $60.. Any other resources about kernel development, and to whom may i speak with to help me get started.. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel documentation and specification
klowd9 - wrote: Kirk's book, ``The Design and Implementation of the FreeBSD Operating System'' probably contains the answers to basic questions about scheduling and IPC. I considered purchasing that book, which is very very good imo, but a bit overpriced at $60.. Um, well, actually for a reference work, that's a reasonable price. You might be able to pick up a copy of the 4.4BSD demon book used, I guess. Any other resources about kernel development, and to whom may i speak with to help me get started.. If you're really serious, buy the book. Buy an intro Operating Systems book as well, Andrew Tannenbaum's is good but there are others. Grab the FreeBSD source and start reading. I started out in mainframes but when I decided I wanted to do Unix kernel programming, I took a UCLA Extension course, I bought the books that were available at the time (some fifteen years ago, now, ghods how time flies) and when it was finally available I got the 386bsd source, bought a 486 system, installed it, and started mucking about. I was fortunate enough to have access to some SVR4 experts around then, as well. But all this was _after_ six years of college and five or six years of a Real Job doing operating systems work. These days the resources are ridiculously plentiful. There are online resources galore, from OS class syllabi to a number of varieties of open-source Unix. As well as many more people who know something about it and are willing to answer reasonable, intelligent questions. But don't expect anyone to hold your hand and _don't_ expect anyone to do the work for you. If you really want to learn this stuff, you will have to invest a _lot_ of time and at least _some_ money. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel documentation and specification
On 2005-03-24, klowd9 - wrote: Reading the CVS logs for the relevant files should give you ideas about who might be able to answer your questions. However, you shouldn't expect that people have time to answer lots of questions. Of course, it helps if your interest is in the context of contributing something back to the project. Kirk's book, ``The Design and Implementation of the FreeBSD Operating System'' probably contains the answers to basic questions about scheduling and IPC. I considered purchasing that book, which is very very good imo, but a bit overpriced at $60.. If you're not prepared to invest that small amount in your learning, then you're not serious about it. Any other resources about kernel development, and to whom may i speak with to help me get started.. You don't need to speak -- as has already been pointed out, you need to read. Read the source code and the CVS logs; read the book; experiment a bit. Then, when you have a handle on things, maybe you might have some real questions to ask. Greg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel documentation and specification
From: Greg Black [EMAIL PROTECTED] To: klowd9 - [EMAIL PROTECTED] CC: freebsd-hackers@FreeBSD.org Subject: Re: Kernel documentation and specification Date: Thu, 24 Mar 2005 13:14:54 +1000 On 2005-03-24, klowd9 - wrote: Reading the CVS logs for the relevant files should give you ideas about who might be able to answer your questions. However, you shouldn't expect that people have time to answer lots of questions. Of course, it helps if your interest is in the context of contributing something back to the project. Kirk's book, ``The Design and Implementation of the FreeBSD Operating System'' probably contains the answers to basic questions about scheduling and IPC. I considered purchasing that book, which is very very good imo, but a bit overpriced at $60.. If you're not prepared to invest that small amount in your learning, then you're not serious about it. Any other resources about kernel development, and to whom may i speak with to help me get started.. You don't need to speak -- as has already been pointed out, you need to read. Read the source code and the CVS logs; read the book; experiment a bit. Then, when you have a handle on things, maybe you might have some real questions to ask. Greg First of all i am dead serious about learning. Secondly, where i come from, $60 is alot of money. And in the spirit of open source and free software, charging $60 for a book is ridiculous. I want to code free software and contribute to the open source community, must i be prepared to pay inorder to contribute? Why isnt a free copy of this book available online? The author obviously put alot of time and effort into making this excellent book, but so do thousands of other people writing code and papers every day, published freely on the internet, and they ask for nothing in return, besides perhaps, some gratitude Furthermore, you cannot speak with a book, and ask it questions, why some things happen a certain way. A good book will do its best to clerify everything, but it doesnt even come close to what an experienced person can help you understand in half that time. Your email contained absolutely no useful information or help, besides a bit condescending on your behalf. Thanks for wasting my time. And lastly, if i did have some 'real questions', im afraid you wouldnt be able to answer them. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
