Bugs, lost and found

It looks like the PC Card problems mentioned earlier are really a problem with the DHCP client. David Rhodus is looking for someone to try a new import of the ISC DHCP code. (Updated – an import from FreeBSD-5 is happening instead, since that fixes some problems with the most recent ISC code.)

Galen Sampson found that using NFS without -maproot will cause file truncation; Matt Dillon has a temporary hack that will fix it, which will be committed by the end of the week if it works without trouble.

Matt Dillon disabled background bitmap writes, as it can apparently cause certain race conditions. He notes: “Eventually the problem background bitmap writes solved will be solved more generally by implementing page COWing durign [sic] device I/O to avoid stalls on pages undergoing write I/O.”

PCMCIA Problems

Emiel Kollof found that to get a PCMCIA network card going, you need to add these lines to /etc/rc.conf: (replace x’s with your static address, if applicable.)


removable_interfaces="<interface name>"
pccard_ifconfig="inet xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx"
or
pccard_ifconfig="DHCP"

Bootsplash

Emiel Kollof made a bootsplash screen at 800x600x8, available here. Download, ungzip to /boot, and put these lines in your loader.conf:


vesa_load="YES"
splash_bmp_load="YES"
bitmap_load="YES"
bitmap_name="dfly.bmp"

The screen, incidentally, looks just like the main site logo.

Even more replacement

The conversation about how to handle third-party utilities in the base system is continuing. Most everyone is coming around to the idea of variant symlinks – file links that use a variable to determine destination, with that variable value determined by the rc system.

Matt Dillon added to his earlier plan with a description of the framework for this variable data, using a system MTA as an example:
Continue reading “Even more replacement”

Code Cleaning continues

David P. Reese, Jr. has completed the 4th stage of his work separating syscalls. This patch splits getsockopt() and setsockopt(). It’s not yet committed as of this writing, but there are no objections yet. A side benefit of this work is that calls like stackgap_init() and stackgap_alloc() can be removed, as they copy data into an area of kernel memory that’s easily overwritten.

The aforementioned K&R -> ANSI cleanups have been committed – that’s about 160 files in bin and sbin that have been cleaned up.

ACPI already

David Rhodus kindly pointed out to me that I missed his commit of ACPI code from Intel, back on the 23rd.

It’s not installed by default. To use it, you’ll need to add ‘device acpica’ to your kernel config file.

Sendmail not sent yet

Timothy Cava brought up the topic of removing sendmail from the base system, and what would be needed to do so without breaking many, many things. Mike Porter pointed out that an rc.mail file should be able to control it. Jeremy Messenger added that this was talked about in an earlier thread revolving around Perl and other base components from FreeBSD. David Rhodus closed this discussion, somewhat, by saying a final DragonFly BSD packaging mechanism is necessary first.

Ways to use up RAM

Joe “Floid” Kanowitz brought up the idea of RAM being used as disk cache, to which a number of replies were made. I mentioned softupdate snapshots as a possible mechanism, which Sander Vesik corrected to say that it would be more like a “write through” union mount of a MFS and real filesystem.

Kip Macy pointed out that ‘tmpfs‘, on Solaris and Linux does something similar. BSD also has mfs, which requires that you allocate memory ahead of time. (Most commonly used to speed up buildwords in /usr/obj/ .)

The concept of journaling file systems that save the state of a file at given chronological points was brought up, and several people noted ‘Elephant‘. (Link from Hiten Pandya.)

Matt Dillon also wrote up several paragraphs on using RAM for storage, which are sufficiently technical that I’ll paste them in the extended link for this entry, rather then sum up.
Continue reading “Ways to use up RAM”