StarOffice 5.1 (Sun version) on 3.3-STABLE
Hi, I am attempting to install the Sun version of StarOffice 5.1 (for Linux) on my FreeBSD 3.3-STABLE (CVSup'ed on the 18-SEP-1999) SMP box. The "net" install worked fine (into /usr/local/Office51). The problem happens when running the per-user setup. It gets about 99% into the setup and then hangs. As far as I can tell it isn't an X11 problem, my home directory is NFS mounted of a 2.2.8-STABLE box but the problem still exists with a local home directory (so it isn't an NFS or locking issue - a long shot anyway). I get a ton of kernel messages such as: /kernel: shared address space fork attempted: pid: 281 /kernel: cmd setup.bin pid 281 tried to use non-present sched_yield last message repeated 1926 times Has anyone seen this and more importantly does anyone have any ideas on how to work around this. It all seemed to be going so well - I thought one I got the "net" setup to work the user side of things would be trivial :-) So close and yet so far! Many thanks, Shaun. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
StarOffice 5.1 (Sun version) on 3.3-STABLE
Hi, I am attempting to install the Sun version of StarOffice 5.1 (for Linux) on my FreeBSD 3.3-STABLE (CVSup'ed on the 18-SEP-1999) SMP box. The "net" install worked fine (into /usr/local/Office51). The problem happens when running the per-user setup. It gets about 99% into the setup and then hangs. As far as I can tell it isn't an X11 problem, my home directory is NFS mounted of a 2.2.8-STABLE box but the problem still exists with a local home directory (so it isn't an NFS or locking issue - a long shot anyway). I get a ton of kernel messages such as: /kernel: shared address space fork attempted: pid: 281 /kernel: cmd setup.bin pid 281 tried to use non-present sched_yield last message repeated 1926 times Has anyone seen this and more importantly does anyone have any ideas on how to work around this. It all seemed to be going so well - I thought one I got the "net" setup to work the user side of things would be trivial :-) So close and yet so far! Many thanks, Shaun. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Acenic driver questions
Question about the acenic driver. In if_ti.c, there's ti_mem which is currently used to load the firmware onto the card. What I'm trying to do is to use take advantage of the window base/window from the registers on the tigon and write to a particular segment of the memory. From what I've seen so far, it looks like I should be able to do this using ti_mem to do this but my experimentations don't seem to be working. I know that Linux acenic driver has patches available for using the window/winbase to read the nic's tracing ring buffer so I'm thinking that I should be on the right track. Does anyone have any experience/suggestions? Thanks! Amy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Acenic driver questions
> On Wed, Apr 04, 2001 at 09:48:24 -0400, Amy Fong wrote: > > Question about the acenic driver. In if_ti.c, there's ti_mem > > which is currently used to load the firmware onto the card. What > > I'm trying to do is to use take advantage of the window base/window > > from the registers on the tigon and write to a particular segment of > > the memory. From what I've seen so far, it looks like I should be > > able to do this using ti_mem to do this but my experimentations > > don't seem to be working. I know that Linux acenic driver has > > patches available for using the window/winbase to read the nic's > > tracing ring buffer so I'm thinking that I should be on the right > > track. > > > > Does anyone have any experience/suggestions? > > Look at the Tigon driver diffs in this patch set: > > http://people.FreeBSD.org/~ken/zero_copy/zero_copy.diffs.20010124 > > In particular, look at the ti_copy_mem() function. > > Ken > -- > Kenneth Merry > [EMAIL PROTECTED] > Thanks! I should be kicking myself right now. I looked at the zero copy code a few months back and totally forgot about it. While I'm wasting bandwidth, I've got another question. I've noticed that if I use up too much stack space, the freebsd kernel (4.2) seems to crash very easily. Specially, if I create an array of size N within a function, once the function gets invoked, my machine just reboots. How do I find out how much stack space I've got? I'm assuming that it _is_ a stack issue. :) Amy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
stack/memory usage in kernel related question
Query: I've noticed that if I use up too much stack space, the freebsd kernel (4.2) seems to crash very easily. Specially, if I create an array of size N within a function, once the function gets invoked, my machine just reboots. How do I find out how much stack space I've got? I'm assuming that it _is_ a stack issue. :) Thanks, Amy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
NIS client (ypbind) "feature" on FreeBSD 3.2-STABLE
Hi, This is long but I wanted to provide as much information as possible. There appears to be an interesting "feature" with NIS client support under FreeBSD 3.2-STABLE (as at Tuesday 24 August). This was a new installation onto a Dell Precision 410-MT (single 400MHz CPU, single SCSI disk, on-board fast ethernet) into an existing environment (the first FreeBSD host in this environment which has mainly Suns, a few Alpha and SGIs and an increasing number of Linux boxes). The machine is part of a group that does telecommunications and networking research - they already have Suns and Linux boxes. Essentially the install went smoothly direct from the 3.2 CDs, and subsequent post-installation configuration involved making a custom kernel, setting up NIS client support, configuring AMD, installing some key packages (e.g. "ssh") and installing and configuring an Efficient ATM card (using HARP included in the release). No real problems with any of this. NIS client support uses "ypbind" in broadcast mode - the NIS master server is a SunOS 4.1.3_U1B machine and three other NIS slave servers are all running Solaris 2.6. This environment has served the site well for a number of years and is VERY stable. We make extensive use of various NIS maps including the automounter for home directories. What appears to happen with the FreeBSD host is that after a reboot, it correctly binds to one of the NIS servers BUT whenever, for whatever reason, it is forced to re-bind it ends up never re-binding, creates something like 600kbit/s of broadcast traffic across our LAN and forces the "rpcbind/portmap" and "ypserv" process on the NIS servers to become CPU bound - it appears to also cause problems for some other broadcast-type applications such as DHCP. Interestingly, the broadcast traffic slowly decreases but probably only by say 100kbit/s in a period of more that 12 hours. Some info: FreeBSD host: % ypwhich ypwhich: can't yp_bind: reason: Domain not bound USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 147 44.7 1.5 1288 924 ?? Rs Tue08PM 394:11.05 ypbind root 132 1.6 0.9 820 576 ?? Ss Tue08PM 23:43.76 syslogd daemon 143 1.1 1.0 836 600 ?? Ss Tue08PM 22:50.86 /usr/sbin/portmap NIS master (SunOS 4.1.3_U1B): USER PID %CPU %MEM SZ RSS TT STAT START TIME COMMAND root60 34.0 0.3 68 236 ? R20:27 280:09 portmap root65 33.6 0.4 172 388 ? R20:27 280:06 ypserv NIS slave (Solaris 2.6): ~~~ USER PID %CPU %MEM SZ RSS TT SSTART TIME COMMAND root 221 17.6 0.3 2264 1216 ?R Jul 29 386:43 rpcbind root 234 4.4 0.3 2368 1400 ?S Jul 29 474:11 ypserv In addition, from "syslog" on the FreeBSD host (the broadcast problem started at around 16:41 so the earlier messages may not be significant): Aug 26 05:19:24 rational xntpd[139]: time reset (step) 0.370413 s Aug 26 14:25:03 rational portmap[3024]: connect from 130.155.194.226 to callit(ypserv): request not forwarded Aug 26 14:25:03 rational portmap[3025]: connect from 130.155.194.226 to callit(ypserv): request not forwarded ... Aug 26 16:41:15 rational ypbind[147]: NIS server [130.155.194.25] for domain "rp .csiro.au" not responding Aug 26 16:41:21 rational last message repeated 2684 times Aug 26 16:41:21 rational /kernel: xl0: command never completed! Aug 26 16:41:21 rational ypbind[147]: NIS server [130.155.194.25] for domain "rp.csiro.au" not responding Aug 26 16:41:21 rational last message repeated 68 times Aug 26 16:41:21 rational /kernel: xl0: command never completed! Aug 26 16:41:21 rational ypbind[147]: NIS server [130.155.194.25] for domain "rp.csiro.au" not responding Aug 26 16:41:21 rational /kernel: xl0: command never completed! Aug 26 16:41:21 rational last message repeated 3 times Aug 26 16:41:21 rational ypbind[147]: NIS server [130.155.194.25] for domain "rp.csiro.au" not responding Aug 26 16:41:52 rational last message repeated 13943 times I thought it was interesting to see the messages from the "xl0" driver - this machine has an on-board 3Com ethernet (as do most newish Dell's) and is connected to a 10mbit/s hub: xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x00 int a irq 14 on pci0.17.0 xl0: Ethernet address: 00:c0:4f:68:e1:6a xl0: autoneg complete, link status good (half-duplex, 10Mbps) The problem is repeatable and as a test I tried to force the host to bind to particular servers using the "-S" option. It works after a reboot but no subsequently with similar problems on the NIS servers. I didn't see the "xl0" messages in this case though: Aug 28 13:08:48 rational ypbind[147]: NIS server [130.155.194.25] for domain "rp.csiro.au" not responding Aug 28 13:09:19 rational last message repeated 14143 times Aug 28 13:11:20 rational last message repeated 55641 times Aug 28 13:21:21 rat
VMWare and SCSI CD-ROMs
Hi, I just installed the "vmware2" port on my freshly CVSup'ed and rebuilt 4.3-RC system. The port installed fine and it appears to startup just fine. My system has a SCSI CD-ROM drive and SCSI CD-RW, both of which work just fine under FreeBSD. VMWare doesn't seem to be able to access the CD-ROM drive, with the device entry changed to /dev/cd0c. I haven't investigated any other "features" like networking although I expect that will work fine. Does anyone have a SCSI CD-ROM drive accessible from within a VMWare virtual machine? There didn't seem any mention of this at http://www.mindspring.com/~vsilyaev/vmware/, I sort of need this so I can easily install the guest OS. Many thanks, Shaun. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Promise ATA100 controller: disk not recognised
Hi, Season's greetings to everyone from a rather warm Sydney, Australia! This evening, I installed a new Promise UltraATA 100 TX2 controller which is correctly recognised at boot time. To this controller I connected a new IBN 60 GB disk (Model: IC35L060AVER07-0). This disk is found and recognised by the Promise controller probe at system startup at Ultra DMA 5 so I believe that the cabling is correct. The problem is that although FreeBSD finds a device present, it does not identify the drive. The output from a "boot -v" is below in case that helps. My entire system was rebuilt from a "cvsup" on December 25 and the system is working fine otherwise it seems. Any advice or thoughts are appreciated - it could be something obvious but as it is after midnight here I am needing sleep! Thanks in advance. Best regards, Shaun. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Promise ATA100 controller: disk not recognised
Hi again, As you can now see I must be needing sleep as I stupidly forgot the output from the "boot -v" - apologies! Thanks, Shaun. >Season's greetings to everyone from a rather warm Sydney, Australia! > >This evening, I installed a new Promise UltraATA 100 TX2 controller which is >correctly recognised at boot time. To this controller I connected a new IBN >60 GB disk (Model: IC35L060AVER07-0). This disk is found and recognised by >the Promise controller probe at system startup at Ultra DMA 5 so I believe >that the cabling is correct. > >The problem is that although FreeBSD finds a device present, it does not >identify the drive. The output from a "boot -v" is below in case that >helps. My entire system was rebuilt from a "cvsup" on December 25 and the >system is working fine otherwise it seems. > >Any advice or thoughts are appreciated - it could be something obvious but as >it is after midnight here I am needing sleep! > >Thanks in advance. > >Best regards, Shaun. --- Copyright (c) 1992-2001 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.5-PRERELEASE #0: Wed Dec 26 21:45:29 EST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/EXPLORER Calibrating clock(s) ... TSC clock: 334084474 Hz, i8254 clock: 1193159 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbff real memory = 268423168 (262132K bytes) Physical memory chunk(s): 0x1000 - 0x0009dfff, 643072 bytes (157 pages) 0x00426000 - 0x0fff4fff, 264040448 bytes (64463 pages) avail memory = 257118208 (251092K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 11 IOAPIC #0 intpin 17 -> irq 10 IOAPIC #0 intpin 19 -> irq 9 SMP: CPU0 apic_initialize(): lint0: 0x0700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 bios32: Found BIOS32 Service Directory header at 0xc00f9e20 bios32: Entry = 0xf0530 (c00f0530) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x730 pnpbios: Found PnP BIOS data at 0xc00fd2d0 pnpbios: Entry = f:d300 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: 000f8110 Preloaded elf kernel "kernel" at 0xc03fc000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x0400 TPR: 0x0010 SVR: 0x01ff pci_open(1):mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) Using $PIR table, 7 entries at 0xc00f0d20 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[10]: type 1, range 32, base e400, size 26 found-> vendor=0x8086, dev=0x7191, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[20]: type 1, range 32, base d800, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=d, irq=9 map[20]: type 1, range 32, base d400, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[90]: type 1, range 32, base e800, size 4 found-> vendor=0x9005, dev=0x001f, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base d000, size 8 map[14]: type 1, range 64, base df00, size 12 found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base e100, size 12 map[14]: type 1, range 32, base b800, size 5 map[18]: type 1, range 32, base de80, size 20 found-> vendor=0x105a, dev=0x4d68, revid=0x02 class=01-80-85, hdrtype=0x00, mfdev=0
NIS client (ypbind) "feature" on FreeBSD 3.2-STABLE
Hi, This is long but I wanted to provide as much information as possible. There appears to be an interesting "feature" with NIS client support under FreeBSD 3.2-STABLE (as at Tuesday 24 August). This was a new installation onto a Dell Precision 410-MT (single 400MHz CPU, single SCSI disk, on-board fast ethernet) into an existing environment (the first FreeBSD host in this environment which has mainly Suns, a few Alpha and SGIs and an increasing number of Linux boxes). The machine is part of a group that does telecommunications and networking research - they already have Suns and Linux boxes. Essentially the install went smoothly direct from the 3.2 CDs, and subsequent post-installation configuration involved making a custom kernel, setting up NIS client support, configuring AMD, installing some key packages (e.g. "ssh") and installing and configuring an Efficient ATM card (using HARP included in the release). No real problems with any of this. NIS client support uses "ypbind" in broadcast mode - the NIS master server is a SunOS 4.1.3_U1B machine and three other NIS slave servers are all running Solaris 2.6. This environment has served the site well for a number of years and is VERY stable. We make extensive use of various NIS maps including the automounter for home directories. What appears to happen with the FreeBSD host is that after a reboot, it correctly binds to one of the NIS servers BUT whenever, for whatever reason, it is forced to re-bind it ends up never re-binding, creates something like 600kbit/s of broadcast traffic across our LAN and forces the "rpcbind/portmap" and "ypserv" process on the NIS servers to become CPU bound - it appears to also cause problems for some other broadcast-type applications such as DHCP. Interestingly, the broadcast traffic slowly decreases but probably only by say 100kbit/s in a period of more that 12 hours. Some info: FreeBSD host: % ypwhich ypwhich: can't yp_bind: reason: Domain not bound USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 147 44.7 1.5 1288 924 ?? Rs Tue08PM 394:11.05 ypbind root 132 1.6 0.9 820 576 ?? Ss Tue08PM 23:43.76 syslogd daemon 143 1.1 1.0 836 600 ?? Ss Tue08PM 22:50.86 /usr/sbin/portmap NIS master (SunOS 4.1.3_U1B): USER PID %CPU %MEM SZ RSS TT STAT START TIME COMMAND root60 34.0 0.3 68 236 ? R20:27 280:09 portmap root65 33.6 0.4 172 388 ? R20:27 280:06 ypserv NIS slave (Solaris 2.6): ~~~ USER PID %CPU %MEM SZ RSS TT SSTART TIME COMMAND root 221 17.6 0.3 2264 1216 ?R Jul 29 386:43 rpcbind root 234 4.4 0.3 2368 1400 ?S Jul 29 474:11 ypserv In addition, from "syslog" on the FreeBSD host (the broadcast problem started at around 16:41 so the earlier messages may not be significant): Aug 26 05:19:24 rational xntpd[139]: time reset (step) 0.370413 s Aug 26 14:25:03 rational portmap[3024]: connect from 130.155.194.226 to callit(ypserv): request not forwarded Aug 26 14:25:03 rational portmap[3025]: connect from 130.155.194.226 to callit(ypserv): request not forwarded ... Aug 26 16:41:15 rational ypbind[147]: NIS server [130.155.194.25] for domain "rp .csiro.au" not responding Aug 26 16:41:21 rational last message repeated 2684 times Aug 26 16:41:21 rational /kernel: xl0: command never completed! Aug 26 16:41:21 rational ypbind[147]: NIS server [130.155.194.25] for domain "rp.csiro.au" not responding Aug 26 16:41:21 rational last message repeated 68 times Aug 26 16:41:21 rational /kernel: xl0: command never completed! Aug 26 16:41:21 rational ypbind[147]: NIS server [130.155.194.25] for domain "rp.csiro.au" not responding Aug 26 16:41:21 rational /kernel: xl0: command never completed! Aug 26 16:41:21 rational last message repeated 3 times Aug 26 16:41:21 rational ypbind[147]: NIS server [130.155.194.25] for domain "rp.csiro.au" not responding Aug 26 16:41:52 rational last message repeated 13943 times I thought it was interesting to see the messages from the "xl0" driver - this machine has an on-board 3Com ethernet (as do most newish Dell's) and is connected to a 10mbit/s hub: xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x00 int a irq 14 on pci0.17.0 xl0: Ethernet address: 00:c0:4f:68:e1:6a xl0: autoneg complete, link status good (half-duplex, 10Mbps) The problem is repeatable and as a test I tried to force the host to bind to particular servers using the "-S" option. It works after a reboot but no subsequently with similar problems on the NIS servers. I didn't see the "xl0" messages in this case though: Aug 28 13:08:48 rational ypbind[147]: NIS server [130.155.194.25] for domain "rp.csiro.au" not responding Aug 28 13:09:19 rational last message repeated 14143 times Aug 28 13:11:20 rational last message repeated 55641 times Aug 28 13:21:21 rat
Re: CCD questions
In message <[EMAIL PROTECTED]> you write: >On 28 Oct, Wes Peters wrote: >> "Stephen J. Roznowski" wrote: >>> >>> I'm looking at the tutorial on building CCDs at >> >> Why? Do you have a compelling reason not to use Vinum volume manager? > >No, but why should I use Vinum over CCD? (All I want to do is create >some larger disks). > >I just did a search on www.freebsd.org, and all I could find about Vinum >seems to imply that the software isn't ready for prime time. Also, a >quick scan of the vinum(4) man page doesn't lead to a lot of confidence >since a large portion of the page is devoted to "DEBUGGING PROBLEMS WITH >VINUM" including kernel panics > >Is Vinum ready for prime time? Vinum is included in the 3.3-RELEASE which suggests there must be a very high level of confidence in its stability and functionality. I would guess that while Vinum is being actively maintained by Greg et al., ccd is showing its age and is probably not being as actively maintained. Vinum has been around for q good amount of time - I heard Greg talk about is in September 1998 at a conference. For some fun, I recently (four weeks ago) decided to stripe and concatenate a couple of filesystems across two 4GB SCSI disks. I was so confident I moved my home directory off my older 2.2.8-STABLE box onto one of these vinum devices and whilst one user probably doesn't hit things hard I have seen no problems. Having had considerable experience with Sun's DiskSuite on Solaris boxes I didn't have much of a problem in getting things going (it was even easier than I thought). There is some excellent info on Greg's WWW site: http://www.lemis.com/vinum.html which may help you get going. Note that the RAID-5 functionality is now also present. Regards, Shaun. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CD-RW long filenames/rw filesystem.
>A couple weeks ago I got a CD-RW drive, and decided to try it out under >all the different OS's I use. In FreeBSD, the only way (it seems) to use >it, is grab a bunch of stuff you want to backup/record and use mkisofs and >cdrecord to dump it onto a CD. Everything I read seemed to indicate that >this method limits you to the 8.3 filename format of iso9660 and all >Rockridge does is add file/group permissions and ownership. is there any >CD recording utilities/formats that can do long filenames (hopefully with >Unix permissions)? This is not correct. The initial ISO9660 standard did specify the 8.3 format but there are now extensions that do what you describe. Recent versions of "mkisofs" support RockRidge (long filename under UNIX support) and Joliet (MS long filename support) so you are not restricted to the 8.3 format. I wrote a couple of CDs the other day under FreeBSD (3.4-STABLE) using "mkisofs" with RockRidge support and the long filenames work fine. As this was data from a UNIX system I wasn't concerned with Windows support. > Next question. Under Windows, there was a program called Adaptec >Direct CD that pretty much allowed you to treat a CD-RW disc as "a really >big floppy disk" (I think that was from the docs). You can save a file to >the CD-RW and then delete it later if you want to. Would it be possible, >or even feasible, to implement something like this in FreeBSD? The is called "packet writing" and the drive has to support it as well as software. I haven't seen any Unix tools to date (although I haven't done a comprehensive search) that supports this. Shaun. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CD-RW long filenames/rw filesystem.
>"Shaun Amy, CSIRO TIP/ATNF" wrote: >> >A couple weeks ago I got a CD-RW drive, and decided to try it out under >> >all the different OS's I use. In FreeBSD, the only way (it seems) to use >> >it, is grab a bunch of stuff you want to backup/record and use mkisofs and >> >cdrecord to dump it onto a CD. Everything I read seemed to indicate that >> >this method limits you to the 8.3 filename format of iso9660 and all >> >Rockridge does is add file/group permissions and ownership. is there any >> >CD recording utilities/formats that can do long filenames (hopefully with >> >Unix permissions)? >> >> This is not correct. The initial ISO9660 standard did specify the 8.3 forma >t >> but there are now extensions that do what you describe. Recent versions of >> "mkisofs" support RockRidge (long filename under UNIX support) and Joliet >> (MS long filename support) so you are not restricted to the 8.3 format. I >> wrote a couple of CDs the other day under FreeBSD (3.4-STABLE) using >> "mkisofs" with RockRidge support and the long filenames work fine. As this >> was data from a UNIX system I wasn't concerned with Windows support. > >Not quite. According to mkisofs(1): > > -l Allow full 32 character filenames. Normally the > ISO9660 filename will be in an 8.3 format which is > compatible with MS-DOS, even though the ISO9660 > standard allows filenames of up to 32 characters. > If you use this option, the disc may be difficult > to use on a MS-DOS system, but this comes in handy > on some other systems (such as the Amiga). Use > with caution. > >It's depressing to see just how long the legacy of MS-DOS persists. :-( >The ISO9660 format supports 32 chars, but since nearly everything uses 8.3 >to be readable by MSCDEX and windoze, the 32 character names are rarely >implemented or well tested. Ah, I was thinking along the lines of: -J Generate Joliet directory records in addition to regular iso9660 file names. This is primarily use- ful when the discs are to be used on Windows-NT or Windows-95 machines.The Joliet filenames are specified in Unicode and each path component can be up to 64 Unicode characters long. and -R Generate SUSP and RR records using the Rock Ridge protocol to further describe the files on the iso9660 filesystem. -r This is like the -R option, but file ownership and modes are set to more useful values. The uid and gid are set to zero, because they are usually only useful on the author's system, and not useful to the client. All the file read bits are set true, so that files and directories are globally readable on the client. If any execute bit is set for a file, set all of the execute bits, so that executa- bles are globally executable on the client. If any search bit is set for a directory, set all of the search bits, so that directories are globally searchable on the client. All write bits are cleared, because the CD-Rom will be mounted read- only in any case. If any of the special mode bits are set, clear them, because file locks are not useful on a read-only file system, and set-id bits are not desirable for uid 0 or gid 0. This is from the man page for 1.12b5 of "mkisofs", which does have a rather large number of options :-) So you may well be correct Peter and probably have a lot more experience than I do with this having only had a CD-R/CD-RW for a bit over a week on my home systems although we have had them for some time at work. Regards, Shaun. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
4.0-RELEASE, PCMCIA, DHCP and IP
Hi, If the subject line hasn't put you off then no doubt after reading this you will think I am crazy in a fairly standard configuration almost works but for the networking... Basically I am trying to install 4.0-RELEASE (off a CD I burnt from the ISO image whilst I wait for the WC CD kit) on a Dell Latitude CPi laptop (which has run FreeBSD 2.2.x and FreeBSD 3.2 in the past). I boot off floppy, do the install of the CD and everything works just fine, including finding the PCMCIA ethernet card (3Com 3C589B which I know works with FreeBSD) and using DHCP to get the correct network parameters over the network. The only problem is (and this sounds silly) is that with the PCMCIA card configured with DHCP addresses it won't pass any IP traffic, even a ping to another machine on the same subnet fails (so it isn't a routing issue). I have done a few installs to try different things and even configuring the IP address manually late in the sysinstall phase still exhibits the same problem. The interface config looks just fine (even after installation using the shell on vty4) but it won't pass IP traffic from what I can tell. I know the card is OK, the cable is OK, the hub/switch is OK as I can boot Win2K and it gets its address from DHCP and works fine. I think I understand networking and do a fair bit of Unix administration so I don't think/hope it is something I have overlooked but... Sorry that there isn't much to go on, but I am out of ideas at the moment and am wondering if anyone has seen something similar? Many thanks, Shaun. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
