Maximum code size and heep
I am running i386 FreeBSD-4.9. My hardware has 2GB of memory and 3GB swap. However, I have noticed that I cannot make a running code larger than about 500MB. If the code grows from the heep by mallocs larger than this I get coredumps. The coredumps are no larger than about 500MB. Is there a system limit on the size of the heep, or something that disallows running with more than 500MB total size? even though I have 2GB RAM. Ed Alley [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Trouble with atapicam and DVD+RW
Ed Alley wrote: Does FreeBSD support ATA DVD writers the same way that it supports CD writers? I have been to SOS's web page, and have looked at hardware support info, but have found no hint at whether ATA DVD writers are supported under FreeBSD. Vulpes Velox replied: Look for dvd+rw tools. Chuck Swiger replied: Yes-- consider using device atapicam + the sysutils/dvd+rw-tools port. Thank-you Vulpes and Chuck; the atapicam mechanism looks like a fine idea. However, I am having problems getting it to work for me... O.K. I am running FreeBSD 4.9. I built a new kernel with: device ata0at isa? port IO_WD1 irq 14 device ata1at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives #device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives device atapicam# CAM device device scbus # Needed for CAM device device pass# Needed to connect scsi to cam device cd # SCSI cd connected through CAM device options ATA_STATIC_ID # Static device numbering Some output from dmesg: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.9-RELEASE #0: Mon Mar 22 15:40:21 PST 2004 [EMAIL PROTECTED]:/usr/src/sys/compile/JORDAN.2 ... etc CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3192.02-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV, PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 1073168384 (1048016K bytes) avail memory = 1041809408 (1017392K bytes) Preloaded elf kernel kernel at 0xc0374000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled ...etc atapci0: Intel ICH5 ATA100 controller port 0xffa0-0xffaf,0x374-0x377,0x170-0x177, 0x3f4-0x3f7,0x1f0-0x1f7 mem 0xfebffc00-0xfebf irq 9 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 atapci1: Intel ICH5 SATA150 controller port 0xfea0-0xfeaf,0xfe30-0xfe33,0xfe20-0xfe27, 0xfe10-0xfe13,0xfe00-0xfe07 irq 9 at device 31.2 on pci0 ata2: at 0xfe00 on atapci1 ata3: at 0xfe20 on atapci1 ...etc ad0: 76293MB Maxtor 6Y080L0 [155009/16/63] at ata0-master UDMA33 ad1: 38166MB WDC WD400BB-75AUA1 [77545/16/63] at ata0-slave UDMA33 Mounting root from ufs:/dev/ad0s1a cd0 at ata1 bus 0 target 0 lun 0 cd0: HP CD-Writer+ 9500 1.0e Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ata1 bus 0 target 1 lun 0 cd1: _NEC DVD+RW ND-1100A 10FD Removable CD-ROM SCSI-0 device cd1: 16.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present em0: Link is up 100 Mbps Full Duplex cd9660: Joliet Extension (Level 1) cd9660: Joliet Extension (Level 1) cd9660: RockRidge Extension -- The cd1 is an _NEC DVD+RW ND-1100A. It is connected as a slave to the HP CD-Writer that is the master on the second IDE channel. I have installed growisofs and cdrtools. cdrecord version is 2.00.3. I can mount CDs on both cd0 and cd1. I can record CDs with cdrecord on cd0, BUT I cannot record DVDs on cd1. I am using Memorex DVD-Rs. Rated at 4.7GB on the label. When I execute growisofs with one of these DVD-Rs in it I get: growisofs -dvd-compat -Z /dev/cd1c=nycity.iso :-( unable to open(/dev/cd1c,O_RDONLY): Device not configured However, I can mount CDs on it. It looks as though growisofs thinks that the device is read-only. Any advice would be greatly appreciated; I was hoping to use this DVD setup as a back-up media as tapes are getting expensive. Ed Alley ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with atapicam and DVD+RW
Chuck Swiger wrote: #device atapicd ... Uncomment these, or at least the first one. :-) O.K. I'll try that when I can get the machine tonight. You might also be having some issues with SATA support under 4.9 with the ICH5 controller if you were using these rather than a normal ATA port; it might be the case that 5.2.x would work better for you. People are actively working to improve this area. I'll try it under 5.2.x also; but that will take until the weekend... Can you a burn a CD on cd1? What device are you using with cdrecord, via SCSI or are you specifying the device as ATAPI:...? I can burn CD's on cd1 using cdrecord without specifying the device as ATAPI, the command that I use is: cdrecord -v dev=1,1,0 nycity.iso The output of camcontrol devlist -v might also be interesting... Here is the output of camcontrol and also cdrecord will scan the scsi bus too... CAMCONTROL: camcontrol devlist -v scbus0 on ata0 bus 0: at scbus0 target -1 lun -1 () scbus1 on ata1 bus 0: HP CD-Writer+ 9500 1.0e at scbus1 target 0 lun 0 (pass0,cd0) _NEC DVD+RW ND-1100A 10FDat scbus1 target 1 lun 0 (pass1,cd1) at scbus1 target -1 lun -1 () scbus2 on ata2 bus 0: at scbus2 target -1 lun -1 () scbus3 on ata3 bus 0: at scbus3 target -1 lun -1 () scbus-1 on xpt0 bus 0: at scbus-1 target -1 lun -1 (xpt0) CDRECORD: cdrecord -scanbus Cdrecord 2.00.3 (i386-unknown-freebsd4.9) Copyright (C) 1995-2002 JF6rg Schilling Using libscg version 'schily-0.7' scsibus1: 1,0,0 100) 'HP ' 'CD-Writer+ 9500 ' '1.0e' Removable CD-ROM 1,1,0 101) '_NEC' 'DVD+RW ND-1100A ' '10FD' Removable CD-ROM 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * Ed ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with atapicam and DVD+RW
Andrew Gould wrote; The description of the DVD burner states DVD+RW. Are you sure it can burn DVD-R's? OOPS ;) Andrew also wrote: A couple of us have experienced difficulties with Memorex media. Consider testing another brand. I feel silly... Well, I went out to Office Max and bought a pack of HP dvd+rw DVDs, tried them out and the burner worked perfectly. I promptly burnt 3GB of back-up without a problem!!! Thanks for the hints. I'm new to DVDs and didn't realize that one DVD media is not necessarily the same as another; or the fact that the little - or + on the label means something important. (:-) Ed Alley ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
DVD R/W in FreeBSD?
Does FreeBSD support ATA DVD writers the same way that it supports CD writers? I have been to SOS's web page, and have looked at hardware support info, but have found no hint at whether ATA DVD writers are supported under FreeBSD. Any help would be greatly appreciated. Ed Alley ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File permissions suddenly change for /dev/null.
On Tue, 2 Sep 2003, Ed Alley wrote: I'm running FreeBSD-4.8. Sometimes the file permissions for /dev/null gets mysteriously changed by some unknown process to: crw--- 1 root wheel 2, 2 Sep 2 11:20 /dev/null On Tue, 2 Sep 2003, David Landgren wrote: ..., the moral of the story is, what have you installed recently? On Tue, 2 Sep 2003, Matthew Seaman wrote: ... It would have to be a root-owned process ... On Tue, 2 Sep 2003, Scott Kupferschmidt wrote: I had the same problem and still unable to figure it out.. I thankyou all for the above comments. They were helpful to me in finding the problem: When I thought about it for a time I realized that it happens on days that I was doing administrative work as ROOT! It was NETSCAPE! running under root. It turns out that I periodically tweak our router via Netscape. If I happen to be logged in as root on my FreeBSD terminal when I log into the router with Netscape, then after I'm finished with my work and close Netscape, I find that the permissions on /dev/null have been reset to: crw---. I'm running Netscape-4.76. I also have a late version of Mozilla installed which doesn't seem to mangle the file permissions on /dev/null the way Netscape does. I also don't need to be logged in as root when I run Netscape to tweak the router, it just happens that when I'm doing other administrative stuff I think to look at the router also. (:-) Ed Alley [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
File permissions suddenly change for /dev/null.
I'm running FreeBSD-4.8. Sometimes the file permissions for /dev/null get mysteriously changed by some unknown process to: crw--- 1 root wheel 2, 2 Sep 2 11:20 /dev/null This has a devastating effect on user processes that want to open /dev/null. Whenever my system starts acting funny, the first place I look is at the permissions for /dev/null. When I find them changed I go under root and execute: chmod 666 /dev/null to get things back to normal. Has anybody seen this before? Have I got a hidden umask set up wrong somewhere, or is one of my daemons the culprit? Or could it be happening during the time that I run as root doing system maintenance? Ed Alley ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[no subject]
On Tue, 2003-09-02 at 14:32, Ed Alley wrote: I'm running FreeBSD-4.8. Sometimes the file permissions for /dev/null get mysteriously changed by some unknown process to: crw--- 1 root wheel 2, 2 Sep 2 11:20 /dev/null On Tue, 2003-09-02 Adam McLaurin wrote: That's very strange indeed. Have you tried using chflags to prevent the permissions from being changed? This should do the trick, albeit a dirty hack. Sorry, I didn't mention that I tried setting flags on /dev/null: chflags schg /dev/null What happens is that sendmail complains that it can't open /dev/null. Hey! I just realized that this may be a clue! Does sendmail fiddle with /dev/null? What happens if sendmail tries to lock /dev/null after it opens it? Does schg prevent fcntl from locking /dev/null, if that is what sendmail uses? Ed Alley ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[no subject]
In addition to being a FreeBSD enthusiast, I am also a Minix enthusiast. I've learned a great deal about how UNIX works by hacking the Minix OS myself. A by-product of my hacks was the development of a FreeBSD kernel module that impliments the Minix Version 2 file system. The latest release that it runs on is FreeBSD 4.6.x. My question is whether the FreeBSD community is interested in such a module? If so, then how does one go about submitting a kernel module for evaluation and possible inclusion in the source? My impression is that the Minix fs is a little simplistic perhaps for inclusion in the FreeBSD source. If so, then is it possible to submit it as a port? I have never seen an example of a kernel module that was submitted as a port, however. Ed Alley To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Minix fs offered
Sorry about the re-posting; but the subject line was omitted in the last post. The previous post contained the following text without a subject line. In addition to being a FreeBSD enthusiast, I am also a Minix enthusiast. I've learned a great deal about how UNIX works by hacking the Minix OS myself. A by-product of my hacks was the development of a FreeBSD kernel module that impliments the Minix Version 2 file system. The latest release that it runs on is FreeBSD 4.6.x. My question is whether the FreeBSD community is interested in such a module? If so, then how does one go about submitting a kernel module for evaluation and possible inclusion in the source? My impression is that the Minix fs is a little simplistic perhaps for inclusion in the FreeBSD source. If so, then is it possible to submit it as a port? I have never seen an example of a kernel module that was submitted as a port, however. Ed Alley To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message