REQ: Test /etc/rc clean-up
Hi folks,
I have a diff for src/etc/rc that I'd like to have had used on a few
machines before I commit it. I'm pretty sure I haven't made any mistakes
with my changes, but you can never be too careful, right?
The diff homogenizes the manner in which variables are tested and is
more careful about using variables in a manner that avoids potential
problems that are unlikely to occur. I see it as a mostly cosmetic, but
healthy change.
Ciao,
Sheldon.
Index: rc
===
RCS file: /home/ncvs/src/etc/rc,v
retrieving revision 1.193
diff -u -d -r1.193 rc
--- rc 1999/08/06 06:22:43 1.193
+++ rc 1999/08/17 15:36:04
@@ -45,15 +45,15 @@
ccdconfig -C
fi
-if [ X$start_vinum = XYES ]; then
+if [ X"${start_vinum}" = X"YES" ]; then
vinum start
-elif [ -n "$vinum_drives" ]; then
- vinum read $vinum_drives
+elif [ -n "${vinum_drives}" ]; then
+ vinum read ${vinum_drives}
fi
swapon -a
-if [ $1x = autobootx ]; then
+if [ X"$1" = X"autoboot" ]; then
echo Automatic reboot in progress...
fsck -p
case $? in
@@ -95,7 +95,7 @@
# diskless boot it does not have to be.
#
-if [ "X$root_rw_mount" != "XNO" ]; then
+if [ X"${root_rw_mount}" != X"NO" ]; then
mount -u -o rw /
fi
@@ -106,7 +106,7 @@
umount -a /dev/null 21
-if [ "X$early_nfs_mounts" != "XYES" ]; then
+if [ X"${early_nfs_mounts}" != X"YES" ]; then
mount -a -t nonfs
else
mount -a
@@ -119,9 +119,9 @@
# Run custom disk mounting function here
#
-if [ "X$diskless_mount" != "X" ]; then
- if [ -f $diskless_mount ]; then
- sh $diskless_mount
+if [ X"${diskless_mount}" != X"" ]; then
+ if [ -f ${diskless_mount} ]; then
+ sh ${diskless_mount}
fi
fi
@@ -148,9 +148,9 @@
fi
# Add additional swapfile, if configured.
-if [ "x$swapfile" != "xNO" -a -w "$swapfile" -a -b /dev/vn0b ]; then
- echo "Adding $swapfile as additional swap."
- vnconfig /dev/vn0b $swapfile swapon /dev/vn0b
+if [ X"${swapfile}" != X"NO" -a -w "${swapfile}" -a -b /dev/vn0b ]; then
+ echo "Adding ${swapfile} as additional swap."
+ vnconfig /dev/vn0b ${swapfile} swapon /dev/vn0b
fi
# set sysctl variables early as we can
@@ -195,7 +195,7 @@
#
# See also the example of another cleanup policy in /etc/periodic/daily.
#
-if [ "X${clear_tmp_enable}" = X"YES" ]; then
+if [ X"${clear_tmp_enable}" = X"YES" ]; then
echo clearing /tmp
# prune quickly with one rm, then use find to clean up /tmp/[lq]*
@@ -217,7 +217,7 @@
# start system logging and name service (named needs to start before syslogd
# if you don't have a /etc/resolv.conf)
#
-if [ "X${syslogd_enable}" = X"YES" ]; then
+if [ X"${syslogd_enable}" = X"YES" ]; then
# Transitional symlink (for the next couple of years :) until all
# binaries had a chance to move towards /var/run/log.
if [ ! -h /dev/log ] ; then
@@ -233,21 +233,21 @@
# enable dumpdev so that savecore can see it
# /var/crash should be a directory or a symbolic link
# to the crash directory if core dumps are to be saved.
-if [ "X${dumpdev}" != X"NO" -a -e ${dumpdev} -a -d /var/crash ]; then
+if [ X"${dumpdev}" != X"NO" -a -e ${dumpdev} -a -d /var/crash ]; then
dumpon ${dumpdev}
echo -n checking for core dump...
savecore /var/crash
fi
-if [ -n "$network_pass1_done" ]; then
+if [ -n "${network_pass1_done}" ]; then
network_pass2
fi
# Enable/Check the quotas (must be after ypbind if using NIS)
-if [ "X${enable_quotas}" = X"YES" ]; then
+if [ X"${enable_quotas}" = X"YES" ]; then
# Only check quotas if they have been previously enabled, and requested
-if [ "X${check_quotas}" = X"YES" ]; then
+if [ X"${check_quotas}" = X"YES" ]; then
echo -n 'checking quotas:'
quotacheck -a
echo ' done.'
@@ -258,7 +258,7 @@
echo ' done.'
fi
-if [ -n "$network_pass2_done" ]; then
+if [ -n "${network_pass2_done}" ]; then
network_pass3
fi
@@ -274,7 +274,7 @@
"password file may be incorrect -- /etc/ptmp exists"
fi
-if [ "X${accounting_enable}" = X"YES" -a -d /var/account ]; then
+if [ X"${accounting_enable}" = X"YES" -a -d /var/account ]; then
echo 'turning on accounting'
if [ ! -e /var/account/acct ]; then
touch /var/account/acct
@@ -287,7 +287,7 @@
if [ -x /sbin/ldconfig ]; then
if [ X"`/usr/bin/objformat`" = X"elf" ]; then
_LDC=/usr/lib
- for i in $ldconfig_paths; do
+ for i in ${ldconfig_paths}; do
if test -d $i; then
_LDC="${_LDC} $i"
fi
@@ -301,7 +301,7 @@
# Default the a.out ldconfig path.
: ${ldconfig_paths_aout=${ldconfig_paths}}
_LDC=/usr/lib/aout
- for i in $ldconfig_paths_aout; do
Re: The Matrix screensaver
What a ridiculous idea! I love it! Nick Hi, This is my poor attempt at reproducing the screens on the movie... Sure, there is much room for improvement, and the whole thing would look cool in VESA, if someone has more spare time... http://www.freebsd.org/~abial/matrix.tgz Unpack it in /sys/modules/syscons. Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- e-Mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
How To Burn CDs
This is a summary of the information that I gather over the last few days with respect to CD recorders. It appears that the preferred and better supported CD recorders are scsi . To shorten the gap what is needed is for ATAPI cd recorders to be integrated into CAM so that we may present a unified interface to both ATAPI and SCSI CD drives. Post on -hackers if you are interested in working on such a project. The rest of this document will deal with scsi cd recorders. Software Tools : cdrecord is used to burn the CDs . cdrecord http home: http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdr ecord.htm cdrecord supports CD-R, CD-RW and Audio CD (Red Book) formants. cdda2wav which is now bundled with cdrecord can extract audio CD tracks. cdrecord is part of the ports/sysutils collection. toshais another scsi tool to extract CD audio tracks and it is in the ports/audio directory . tosha is native program to FreeBSD. tosha was written by Oliver Fromme [EMAIL PROTECTED] cdd another native freebsd program to extract CD audio tracks was written by Charles Henrich and is part of the ports/audio collection. mkisofs is used to create an iso 9660 cd image. It is located in the ports/sysutils collection If one of the audio "rippers" does not work report the problem after first making sure that the program does indeed support your CD disk unit and then just try another one. For a list of "reported to work" drives that work with cdrecord + cdd2wav see: http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdw riters-1.8.html External vs. Internal I find that my YAMAHA CRW6416sz scsi cd recorder runs rather cool . Some members on the list have reported that at least early models of their CD-Recorders run hot so they preferred to have them external due to the heat problem and/or portability . A little bit on cdrecord. To determine which scsi recorder is installed in your system issue: cdrecorder -scanbus Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling scsibus0: 0) 'SEAGATE ' 'ST34501W' '0017' Disk 1) 'YAMAHA ' 'CRW6416S' '1.0b' Removable CD-ROM 2) * 3) 'SEAGATE ' 'ST15150W' '0023' Disk 4) * 5) * 6) * 7) * scsibus1: 100) * 101) * 102) * 103) * 104) * 105) 'UMAX' 'UMAX S-12 ' 'V2.0' Scanner 106) * 107) * So my Yamaha CD recorder is scsi bus 0 , scsi address 1, lun 0. I recommend sticking this information in /etc/default/record cat /etc/default/cdrecord CDR_DEVICE=1,0 What this means is that every time that cdrecord runs it gets is device info from /etc/default/cdrecord . If you feel somehow compel to always specify the scsi device in cdrecord, the syntax is: -dev=bus,scsi address, lun or -dev=scsi address, lun in my case is: -dev=1,0 (the default scsi bus is 0) I recommend for the first few times to use a CD-RW. They are more expensive than CD-R;however, for playing for the first time with your scsi cd recorder they can actually probably save you a lot of money. Now that you have all your hardware and software in place what can you do 8) To create an iso cd9660 with a CD-RW: mkisofs -R /mount/dir | cdrecord -blank=fast -v fs=6m speed=3 - mkisofs pipes an ISO 9660 cd image to cdrecord. cdrecord does the actual cd burning: -blank=fastfirst it does a quick blank -v verbose mode so you can see what is doing fs=6m forks a process and uses a 6MB buffer speed=3usually CD-RW can only be burned as fast as 4X you will have to experiment with your cd recorder to see what speed works best. Take a break pending upon the size of the image the process can take 1/2 hour to just a few minutes so kick back and relax. Here is session for creating audio cds. mkdir cdtracks cd cdtracks cddwa2wav -B This command generates tracks in the format of: audio_nn.wav where nn is a track number . audio in .wav format audio_nn.inf where nn is a track number . pregap info cdrecord -blank=fast -audio -useinfo audio*.wav -blank=fast blanks your CD-RW for CD-R don't include this command -audiosets audio cd recording -useinfo use the pregap info generated by cdd2wav *.inf files Issues: In the list there was an exchange of using the tool team for buffering vs cdrecord's own buffering scheme: "Another possibility, if you have the RAM, is to use the team(1) program
Re: Strange notebook boot misbehaviour.
Greg Lehey wrote: On Thursday, 19 August 1999 at 17:34:28 +0300, Maxim Sobolev wrote: I have a notebook (toshiba satellite pro 445) with WinNT and FreeBSD installed and discovered that when I'm booting FreeBSD directly from power-down state or rebooting after FreeBSD then it boots ok, but when I doing reboot from NT it hangs just before mounting / (probably "hang" is not quite correct term because it still responds to ctrl-alt-del). Any ideas of where I should look? Following is my dmesg (with hang point highlited): [snip] acd0: Medium: CD-ROM 120mm data disc loaded, unlocked changing root device to wd0s1a Card inserted, slot 1 ^ - Hangs after this message!!! On Thursday, 19 August 1999 at 14:55:15 -0500, Matt Crawford wrote: On the Sony 505 mailing list, this was noted and said to be due to Windows leaving the ethernet chip in some APM-related suspended state. Interesting. I see similar behaviour. It also happens in the opposite direction: if I reboot from FreeBSD and select Microsoft, Microsoft hangs during boot. Well, nice to hear that I'm not alone ;). But anyway does anyone have ideas on how track this down? -Max -- "We believe in the Power and the Might!" (Manowar, 1996) Maxim V. Sobolev, Financial Analyst, Vega International Capital Phone: +380-(44)-246-6396 Fax: +380-(44)-220-8715 E-mail: [EMAIL PROTECTED] ICQ: #42290709 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: How To Burn CDs
On 20-Aug-99 Amancio Hasty wrote: This is a summary of the information that I gather over the last few days with respect to CD recorders. It appears that the preferred and better supported CD recorders are scsi . To shorten the gap what is needed is for ATAPI cd recorders to be integrated into CAM so that we may present a unified interface to both ATAPI and SCSI CD drives. Post on -hackers if you are interested in working on such a project. The rest of this document will deal with scsi cd recorders. Software Tools : cdrecord is used to burn the CDs . cdrecord http home: http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cd r ecord.htm cdrecord supports CD-R, CD-RW and Audio CD (Red Book) formants. cdda2wav which is now bundled with cdrecord can extract audio CD tracks. cdrecord is part of the ports/sysutils collection. toshais another scsi tool to extract CD audio tracks and it is in the ports/audio directory . tosha is native program to FreeBSD. tosha was written by Oliver Fromme [EMAIL PROTECTED] cdd another native freebsd program to extract CD audio tracks was written by Charles Henrich and is part of the ports/audio collection. mkisofs is used to create an iso 9660 cd image. It is located in the ports/sysutils collection If one of the audio "rippers" does not work report the problem after first making sure that the program does indeed support your CD disk unit and then just try another one. For a list of "reported to work" drives that work with cdrecord + cdd2wav see: http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cd w riters-1.8.html External vs. Internal I find that my YAMAHA CRW6416sz scsi cd recorder runs rather cool . Some members on the list have reported that at least early models of their CD-Recorders run hot so they preferred to have them external due to the heat problem and/or portability . A little bit on cdrecord. To determine which scsi recorder is installed in your system issue: cdrecorder -scanbus Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling scsibus0: 0) 'SEAGATE ' 'ST34501W' '0017' Disk 1) 'YAMAHA ' 'CRW6416S' '1.0b' Removable CD-ROM 2) * 3) 'SEAGATE ' 'ST15150W' '0023' Disk 4) * 5) * 6) * 7) * scsibus1: 100) * 101) * 102) * 103) * 104) * 105) 'UMAX' 'UMAX S-12 ' 'V2.0' Scanner 106) * 107) * So my Yamaha CD recorder is scsi bus 0 , scsi address 1, lun 0. I recommend sticking this information in /etc/default/record cat /etc/default/cdrecord CDR_DEVICE=1,0 What this means is that every time that cdrecord runs it gets is device info from /etc/default/cdrecord . If you feel somehow compel to always specify the scsi device in cdrecord, the syntax is: -dev=bus,scsi address, lun or -dev=scsi address, lun in my case is: -dev=1,0 (the default scsi bus is 0) I recommend for the first few times to use a CD-RW. They are more expensive than CD-R;however, for playing for the first time with your scsi cd recorder they can actually probably save you a lot of money. Now that you have all your hardware and software in place what can you do 8) To create an iso cd9660 with a CD-RW: mkisofs -R /mount/dir | cdrecord -blank=fast -v fs=6m speed=3 - mkisofs pipes an ISO 9660 cd image to cdrecord. cdrecord does the actual cd burning: -blank=fastfirst it does a quick blank -v verbose mode so you can see what is doing fs=6m forks a process and uses a 6MB buffer speed=3usually CD-RW can only be burned as fast as 4X you will have to experiment with your cd recorder to see what speed works best. Take a break pending upon the size of the image the process can take 1/2 hour to just a few minutes so kick back and relax. Here is session for creating audio cds. mkdir cdtracks cd cdtracks cddwa2wav -B This command generates tracks in the format of: audio_nn.wav where nn is a track number . audio in .wav format audio_nn.inf where nn is a track number . pregap info cdrecord -blank=fast -audio -useinfo audio*.wav -blank=fast blanks your CD-RW for CD-R don't include this command -audiosets audio cd recording -useinfo use the pregap info generated by cdd2wav *.inf files Issues: In the list
Re: cc -O broken in -current for Alpha KLDs
Doug Rabson wrote: On Thu, 19 Aug 1999, Andrew Gallatin wrote: I do most of my development on alphas I just turned some local code into a loadable kernel module. It works fine when compiled into the kernel statically, but fails miserably when loaded into an alpha kernel as a module. This alpha is running -current from monday or so. After a day or so of debugging, I decided to run it on an x86 -- it ran just fine. I've narrowed the problem down to one involving optimization and have extracted a simple, reproducable test case. When the test module is loaded without optimization (CFLAGS += -g -O0), it prints the following (which is correct): It looks like we aren't handling the relocations correctly. When I get a chance, I will try to look at it. If you want to have another look, the code at fault is probably in alpha/alpha/elf_machdep.c and you can get a list of relocations in the module with 'objdump --dynamic-reloc foo.ko'. I thought of that before I went to sleep this morning too.. Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cc -O broken in -current for Alpha KLDs
Doug Rabson writes: On Thu, 19 Aug 1999, Andrew Gallatin wrote: I do most of my development on alphas I just turned some local code into a loadable kernel module. It works fine when compiled into the kernel statically, but fails miserably when loaded into an alpha kernel as a module. This alpha is running -current from monday or so. After a day or so of debugging, I decided to run it on an x86 -- it ran just fine. I've narrowed the problem down to one involving optimization and have extracted a simple, reproducable test case. When the test module is loaded without optimization (CFLAGS += -g -O0), it prints the following (which is correct): It looks like we aren't handling the relocations correctly. When I get a chance, I will try to look at it. If you want to have another look, the code at fault is probably in alpha/alpha/elf_machdep.c and you can get a list of relocations in the module with 'objdump --dynamic-reloc foo.ko'. Thanks for the pointer, it was right on the money. It turns out that at the default optimization level, the objdump output looks like this: ... 00010ea8 RELATIVE *ABS* 00010e80 GLOB_DAT Xmit_completes+0x0028 00010e88 GLOB_DAT Xmit_completes+0x0008 00010e90 GLOB_DAT Xmit_completes+0x0010 00010e98 GLOB_DAT Xmit_completes+0x0018 00010ea0 GLOB_DAT Xmit_completes 00010e70 JMP_SLOT printf ... I've just committed a patch to alpha/alpha/elf_machdep.c which takes into account the addends for objects of type R_ALPHA_GLOB_DAT. This fixes my problem. Should it be MFC'ed? Thanks again, Drew -- Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: [EMAIL PROTECTED] Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How To Burn CDs
On Fri, Aug 20, 1999 at 01:04:47PM +0200, Werner Griessl wrote: # # Don't forget cdrdao, it's able to read and burn "video(cdi)"-cd's. # Successfully done here with a philips cdr2600 burner for a philips cdi player. # It's also in ports. From what I recall, tosha's been able to deal with vcd's as well, it's just they usually start from track 2. # Werner -- -mishania To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ping/egcs
Hi,
I just came across the problem with ping and egcs. If you do
# ping -s 57 localhost
PING localhost (127.0.0.1): 57 data bytes
^C
--- localhost ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
if the data size is even number, it works OK. I think that
the problem is that EGCS generates bad code in in_cksum()
with -O.
Compiling with -O0 solves the problem as well as applying
following patch fixes it.
I wonder if how many problems like this go unnoticed
*** ping.c-org Fri Aug 20 09:38:33 1999
--- ping.c Fri Aug 20 09:39:08 1999
***
*** 944,949
--- 944,950
/* mop up an odd byte, if necessary */
if (nleft == 1) {
*(u_char *)(answer) = *(u_char *)w ;
+ *((u_char *)(answer)+1) = 0;
sum += answer;
}
Tammy
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
problem with vnconfig -s labels ...
Hi, trying to build picobsd on 19990816snap of -current, i am consistently hitting a problem, which is totally reproducible from the command line. The following sequence vnconfig -s labels -c /dev/rvn0 fs.PICOBSD disklabel -rw /dev/rvn0 fd1440 causes a panic with a page fault accessing a low address (presumably through a null pointer) in vnstrategy. fs.PICOBSD is a file filled with 0's with dd if=/dev/zero... and the problem appears to occur independently from the size of the file. can someone investigate this ? the code seems to work fine on 3.x cheers luigi ---+- Luigi RIZZO, [EMAIL PROTECTED] . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ First International Workshop on Networked Group Communication ---+- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem with vnconfig -s labels ...
On Fri, 20 Aug 1999, Luigi Rizzo wrote: Hi, trying to build picobsd on 19990816snap of -current, i am consistently hitting a problem, which is totally reproducible from the command line. The following sequence vnconfig -s labels -c /dev/rvn0 fs.PICOBSD disklabel -rw /dev/rvn0 fd1440 causes a panic with a page fault accessing a low address (presumably through a null pointer) in vnstrategy. fs.PICOBSD is a file filled with 0's with dd if=/dev/zero... and the problem appears to occur independently from the size of the file. can someone investigate this ? the code seems to work fine on 3.x Someone also sent me a report on that, so it's a real problem. I have a traceback, but without debugging symbols. Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem with vnconfig -s labels ...
can someone investigate this ? the code seems to work fine on 3.x Someone also sent me a report on that, so it's a real problem. I have a traceback, but without debugging symbols. it's so easy to reproduce that i hope the vm/vn gurus will not require too much effort to find the bug. in the meantime, what you suggest (for picobsd builds that is) ? use a real floppy ? cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
The Matrix screensaver, v.0.2
Hi, Due to unexpected demand (I did it mostly as a distraction from real work), I backported this screensaver to 3.2-RELEASE (don't know about STABLE), and corrected some inconsistencies. I added also binary versions to the archives. Both versions are available at: http://www.freebsd.org/~abial/matrix_3.2.tgz http://www.freebsd.org/~abial/matrix_4.0.tgz Have fun... Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem with vnconfig -s labels ...
Luigi, I've been seeing the same thing for about 6 weeks now :) I, too can reproduce the panic _at will_. If anyone's interested I've got a large selection of kernel cores to choose from :) ... Andrew. Some comments below ... On Fri, 20 Aug 1999, Luigi Rizzo wrote: Hi, trying to build picobsd on 19990816snap of -current, i am consistently hitting a problem, which is totally reproducible from the command line. The following sequence vnconfig -s labels -c /dev/rvn0 fs.PICOBSD disklabel -rw /dev/rvn0 fd1440 causes a panic with a page fault accessing a low address (presumably through a null pointer) in vnstrategy. Yeah, I instrumented my kernel - and it is NULL. I think it's dev_t related breakage but I have no proof :) . Also slices don't work. I try doing: vnconfig -e -s labels /dev/vn0 and then disklabel -rw vn0 auto and disklabel says '/dev/vn0c' not configured, or some such - it seems the mapping between /dev/vn0 /dev/vn0s1 (and friends) and /dev/vn0a /dev/vn0b (and friends) does not work _at all_. This has been the case since early July. fs.PICOBSD is a file filled with 0's with dd if=/dev/zero... and the problem appears to occur independently from the size of the file. Correct. Same here. can someone investigate this ? the code seems to work fine on 3.x As stated above it worked fine until sometime in July. A point that may be of interest - I've found panics are more likely to occur if the command pair is executed in a script vs. from the command line. This may suggest some sort of race is occurring. Hope some of this is helpful... :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem with vnconfig -s labels ...
Someone also sent me a report on that, so it's a real problem. I have a traceback, but without debugging symbols. Doh! Sorry about that :) I'll rebuild my kernel later today... Cheers, Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp and cdrom image
On Fri, 20 Aug 1999, Mete Balci wrote: I have some questions for distribution. I have started to download freebsd 3.2-current via ftp but it seems to be huge. I think it will be 2 CD. First, how do I have to split it to 2 CDs ? which dirs will going to first and which to second CD ? Second, I have seen there is an iso image file for rel. 4.0. So why is it just 1 CD ? I have experienced Linux for 3 years at an administration level but no idea about freebsd. Which type of download could you recommend to me ? I recommend you download FreeBSD 3.2-STABLE, not FreeBSD 4.0-CURRENT, which is the developer's version and for experienced hackers only (see http://www.freebsd.org/FAQ/FAQ7.html#7) For instructions on how to install FreeBSD-STABLE, please see http://www.freebsd.org/handbook/install.html. Note that 3.3 is coming out in a few weeks, but there aren't likely to be many differences between the current snapshot of 3.2-STABLE and 3.3-RELEASE (see http://www.freebsd.org/FAQ/FAQ8.html#8 for why). In general, be sure to always consult the FAQ, handbook, and mailing list archives with your problems before posting to a mailing list - chances are they have been answered (many times) before. Thanks and good luck! Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver
On Fri, 20 Aug 1999, Andrzej Bialecki wrote: Hi, This is my poor attempt at reproducing the screens on the movie... Sure, there is much room for improvement, and the whole thing would look cool in VESA, if someone has more spare time... http://www.freebsd.org/~abial/matrix.tgz Hey, where'd it go? Doug White Internet: [EMAIL PROTECTED]| FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite| www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gdb-4.17 in FreeBSD 4.0-CURRENT
I managed to build gdb-4.17 in FreeBSD 4.0, here's how to do it: 1) gdb-4.17/configure --host=i386-unknown-freebsdelf4.0 Have to specify the host explicitly, otherwise it doesn't realize it needs to use ELF. 2) in gdb-4.17/Makefile, add "-DSVR4_SHARED_LIBS" to definition of CFLAGS 3) in gdb-4.17/gdb/solib.c, add #include "elf/common.h" (after #include "elf/external.h") 4) in gdb-4.17/gdb/infptrace.c, add #define U_REGS_OFFSET 0x1fa8 I figured out this number the hard way by searching all the valid PT_READ_U addresses and comparing the results with PT_GETREGS - found locations where eip and esp values matched up. Doubtless there's a better way to get the right value. Then it should all build (and perhaps work). The same hacks probably apply to gdb-4.18 and gdb-current (but so far gdb-4.17 is the most useful version I've seen for debugging C++). Richard Cownie ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver
On Fri, 20 Aug 1999, Doug White wrote: On Fri, 20 Aug 1999, Andrzej Bialecki wrote: Hi, This is my poor attempt at reproducing the screens on the movie... Sure, there is much room for improvement, and the whole thing would look cool in VESA, if someone has more spare time... http://www.freebsd.org/~abial/matrix.tgz Hey, where'd it go? See my next announcement on -current. Or, see my page. Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
oh THAT screen... quite a giggle.. On Fri, 20 Aug 1999, Andrzej Bialecki wrote: Hi, Due to unexpected demand (I did it mostly as a distraction from real work), I backported this screensaver to 3.2-RELEASE (don't know about STABLE), and corrected some inconsistencies. I added also binary versions to the archives. Both versions are available at: http://www.freebsd.org/~abial/matrix_3.2.tgz http://www.freebsd.org/~abial/matrix_4.0.tgz Have fun... Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On Fri, 20 Aug 1999, Julian Elischer wrote: oh THAT screen... quite a giggle.. c'mon, you didn't expect me to put an intro scene from the movie, did you? Yeah, that's something - MPEG screensaver... only a few GB. I need to think about it. 8-)) Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On Fri, 20 Aug 1999, Andrzej Bialecki wrote: c'mon, you didn't expect me to put an intro scene from the movie, did you? Yeah, that's something - MPEG screensaver... only a few GB. I need to think about it. I wonder where in phk's rules for binary files in the tree that would fall. Just make sure to uuencode the mpeg first. : -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On Fri, 20 Aug 1999, Nick Hibma wrote: oh THAT screen... quite a giggle.. Have you seen the source ... very neat and short. Pitty that it consumes 2% intr time. Oh, there is still much room for improvement here... if there is any interest, that is. :-) Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On Fri, 20 Aug 1999, Andrzej Bialecki wrote: Hi, Due to unexpected demand (I did it mostly as a distraction from real work), I backported this screensaver to 3.2-RELEASE (don't know about STABLE), and corrected some inconsistencies. I added also binary versions to the archives. LOL! I love that! Good work. :) - kevin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
help! - strange vn behaviour
I'll cc: hackers and see if this rings a bell for anyone :| .. Andrew Btw, can you explain why this happens? $ partitionsize=256 $ sects=`/bin/expr $partitionsize '*' 64 '-' 1` $ vnconfig -e -s labels -S $partitionsize"m" /dev/vn0 $ disklabel -w -r vn0 auto disklabel: /dev/rvn0c: Device not configured $ disklabel vn0 disklabel: ioctl DIOCGDINFO: Inappropriate ioctl for device $ disklabel /dev/vn0 # /dev/vn0: type: unknown disk: amnesiac label: fictitious flags: bytes/sector: 4096 sectors/track: 32 tracks/cylinder: 8 sectors/cylinder: 256 cylinders: 256 sectors/unit: 65536 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c:655360unused0 0 # (Cyl. 0-255) - Now, if I do a - $ vnconfig -u /dev/vn0c echo "woohoo!" vnconfig: VNIOCDETACH: Device not configured $ vnconfig -u /dev/vn0 echo "woohoo!" woohoo! ... The vn device _is_ configured but not useable via /dev/vn0[abc..z] ?? Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
oh THAT screen... quite a giggle.. Have you seen the source ... very neat and short. Pitty that it consumes 2% intr time. Oh, there is still much room for improvement here... if there is any interest, that is. :-) Like rewriting the syscons driver again, to make your 10 line screensaver faster, yeah right. This ain't Linux. Nick -- e-Mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
Hi, On Fri, Aug 20, 1999 at 07:34:31PM +0200, Andrzej Bialecki wrote: Due to unexpected demand (I did it mostly as a distraction from real work), I backported this screensaver to 3.2-RELEASE (don't know about ... I saw the announcement for the first release, realised that it's only for -current; went home, tested it on my personal -current machine and instantly wondered how many messages about a port to -stable you might had got already. I decided to just let the others do the begging ;))) What a pity, that our servers are running on those smallish gray-scale 9" screens. And what a pity for 'Chuck' being banned from our consoles ...;) What about a xlock-more module? Thank's alot for the amusement ... -Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/: : PGP-Key:http://www.tse-online.de/~ab/public-key: : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On Fri, Aug 20, 1999 at 11:50:25PM +0200, Andreas Braukmann wrote: Hi, On Fri, Aug 20, 1999 at 07:34:31PM +0200, Andrzej Bialecki wrote: Due to unexpected demand (I did it mostly as a distraction from real work), I backported this screensaver to 3.2-RELEASE (don't know about ... I saw the announcement for the first release, realised that it's only for -current; went home, tested it on my personal -current machine and instantly wondered how many messages about a port to -stable you might had got already. I decided to just let the others do the begging ;))) What a pity, that our servers are running on those smallish gray-scale 9" screens. And what a pity for 'Chuck' being banned from our consoles ...;) What about a xlock-more module? Thank's alot for the amusement ... I haven't seen Andrzej's screensaver, but if it is about those green letters that fall from the top of the screen (aka the matrix) then xlock already includes a module for this... I'm using it on my laptop.. regards, -Oscar -- For PGP Public Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
user friendly creation of CDs (was: Re: patches for tosha?)
In article [EMAIL PROTECTED] you write: Hi, I am all set . cdrecord-1.8a22 includes cdda2wav as [EMAIL PROTECTED] pointed out and it does work with my Yamaha cd recorder . In summary using FreeBSD-current of about two weeks ago , I am now able to : 1. to burn iso 9660 with mkisofs + cdrecord 2. extract CD audio tracks with cdda2wav 3. Burn audio cds with cdrecord . No other external program is necessary to burn the Audio CD. A bit more work is needed to make the creation of CDs on FreeBSD user friendly and the responsibilty for that falls more on the authors of the CD tools. Re user friendly creation of CDs, have you tried the sysutils/gcombust port? works quite well for me... (using 3.2-stable.) Regards, -- Juergen Lock [EMAIL PROTECTED] (remove dot foo from address to reply) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: user friendly creation of CDs (was: Re: patches for tosha?)
Yes, I tried gcombust and opted for the command line approach gcombust looks great ;however, I expect for user firiendly land less knobs for instance: burn iso 9660 cd Select files or directories type of CD : CD-R , CD-RW then pull the appropiate information for buffering and optimal speed from a database. You need something special to burn your CD ? pull out the "expert" tab menus. If I showed gcombust to Bettina , she would snap you got to be kidding and I have to confess that she is right. She already ask me is the system ready for you and I had to respond sorry not quite there yet you will have to wait about a week and she responded thats not bad take your time . Sometimes being the hacker of the house is not an easy task 8) Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On Fri, Aug 20, 1999 at 04:11:42PM -0600, Oscar Bonilla wrote: I haven't seen Andrzej's screensaver, but if it is about those green letters that fall from the top of the screen (aka the matrix) then xlock already includes a module for this... I'm using it on my laptop.. I like Andrzej's module a _lot_ better than the xlock module. It looks (IMO) more like the screen from the movie and doesn't eat all of my CPU cycles. --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville [EMAIL PROTECTED] PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On Fri, 20 Aug 1999, Keith Stevenson wrote: On Fri, Aug 20, 1999 at 04:11:42PM -0600, Oscar Bonilla wrote: I haven't seen Andrzej's screensaver, but if it is about those green letters that fall from the top of the screen (aka the matrix) then xlock already includes a module for this... I'm using it on my laptop.. I like Andrzej's module a _lot_ better than the xlock module. It looks (IMO) more like the screen from the movie and doesn't eat all of my CPU cycles. --Keith Stevenson-- Agreed, my friends (who were much larger fans of the movie then I (they've seen it multiple times and I've only seen it once)) were shocked (actually outright amazed in awe) when I showed them it. Now all I have to do is find that perfect looking blond from reading the code... ;) - kevin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cc -O broken in -current for Alpha KLDs
In article [EMAIL PROTECTED], Andrew Gallatin [EMAIL PROTECTED] wrote: I've just committed a patch to alpha/alpha/elf_machdep.c which takes into account the addends for objects of type R_ALPHA_GLOB_DAT. This fixes my problem. Should it be MFC'ed? Nice work! It looks right to me, not to mention that it now agrees with what the dynamic linker does. I think you should definitely bring it into -stable. For good form you might want to give it another day or two in -current first. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem with vnconfig -s labels ...
Hi, I've found panics are more likely to occur if the command pair is executed in a script vs. from the command line. This may suggest some sort of race is occurring. no idea... i have always managed to panic the system even running the commands from the command line one at a time, so i don't think it is a race. I think i also got the paninc trying a disklabel when the "vn" device was not in the kernel, but this one i had no time to reproduce. cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem with vnconfig -s labels ...
On Sat, Aug 21, 1999 at 04:22:46AM +0200, Luigi Rizzo wrote: Hi, I've found panics are more likely to occur if the command pair is executed in a script vs. from the command line. This may suggest some sort of race is occurring. no idea... i have always managed to panic the system even running the commands from the command line one at a time, so i don't think it is a race. I think i also got the paninc trying a disklabel when the "vn" device was not in the kernel, but this one i had no time to reproduce. The problem is that disklabel executes code in subr_diskslice.c which does: dev1 = dkmodslice(dkmodpart(dev, RAW_PART), slice); The 'dev' structure has s_drv1 set correctly, but the 'dev1' entry has s_drv1 NULL. When vnstrategy() is called using dev1, vn = bp-b_dev-s_drv1 is NULL when it shouldn't be. The first time vn is referenced... fall down go boom. In my code (a bit similar to what picobsd is doing), I can open /dev/vn0, ioctl(fd,VNIOCATTACH,...), ioctl(fd,VNIOCUSET,...) and close without a problem. Execing '/sbin/disklabel -Brw /dev/rvn0 blah' causes the machine to panic. I've patched vnstrategy() to fail gracefully if bp-b_dev-s_drv1 is NULL, but I'm still looking for the place where the dev1 entry is supposed to be initialised. -- John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem with vnconfig -s labels ...
On Sat, Aug 21, 1999 at 07:30:46AM +0200, Poul-Henning Kamp wrote: but I'm still looking for the place where the dev1 entry is supposed to be initialised. In dkmodslice() (and friends). Hmmm, I know this is your code, but are you sure? 8-). My understanding of dkmodslice() and friends is that they manipulate dev_t entries, but don't actually initialise them. Since the subr_diskslice code takes a dev_t and goes off and accesses the raw partition entry, my guess is that vnopen() should check if the raw entry has been initialised, and if not do it, just like it does for the one you open. -- John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem with vnconfig -s labels ...
Hmmm, I know this is your code, but are you sure? 8-). My understanding of
dkmodslice() and friends is that they manipulate dev_t entries, but don't
actually initialise them. Since the subr_diskslice code takes a dev_t
dkmodslice() once just manipulated bits in dev_t scalars. Now that dev_t
is a pointer, dkmodslice() has to create something for the pointer to
point to. That something needs to be fully initialised and not created
more than once. The initialisation is apparently incomplete. Multiple
creation is avoided by searching the list of previously created entries.
Now I understand why my memory is filling up with unused dev_t
entries :-). subr_diskslice churns through a not insignificant part
of the per-drive minor number space (32 slices * 8 partitions * {raw,
buffered}), using dkmodslice to create new dev_t's.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: problem with vnconfig -s labels ...
In message [EMAIL PROTECTED], Bruce Evans writes:
Hmmm, I know this is your code, but are you sure? 8-). My understanding of
dkmodslice() and friends is that they manipulate dev_t entries, but don't
actually initialise them. Since the subr_diskslice code takes a dev_t
dkmodslice() once just manipulated bits in dev_t scalars. Now that dev_t
is a pointer, dkmodslice() has to create something for the pointer to
point to. That something needs to be fully initialised and not created
more than once. The initialisation is apparently incomplete. Multiple
creation is avoided by searching the list of previously created entries.
Now I understand why my memory is filling up with unused dev_t
entries :-). subr_diskslice churns through a not insignificant part
of the per-drive minor number space (32 slices * 8 partitions * {raw,
buffered}), using dkmodslice to create new dev_t's.
yes, this is the remaining sticky issue, and the only cure I know for
this and for the DEVFS issue is to relayer the slice/label processing
out of the device driver entirely. This is now almost possible to do.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
