Error handling for src/usr.sbin/pccard/pccardc/*
This is a patch for better (I think) error handling for pccardc.
(obtained from PAO3)
Please review.
--
Jun Kuriyama // kuriy...@sky.rim.or.jp
// kuriy...@freebsd.orgIndex: pccardc/dumpcis.c
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardc/dumpcis.c,v
retrieving revision 1.10
diff -u -r1.10 dumpcis.c
--- dumpcis.c 1999/02/05 16:00:15 1.10
+++ dumpcis.c 1999/02/13 04:33:28
@@ -43,7 +43,7 @@
int nocards;
-void
+static void
scan(slot)
int slot;
{
@@ -57,7 +57,8 @@
if (fd 0)
return;
nocards++;
- ioctl(fd, PIOCGSTATE, st);
+ if (ioctl(fd, PIOCGSTATE, st))
+ err(1, ioctl (PIOCGSTATE));
if (st.state == filled) {
cp = readcis(fd);
if (cp) {
Index: pccardc/enabler.c
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardc/enabler.c,v
retrieving revision 1.11
diff -u -r1.11 enabler.c
--- enabler.c 1999/02/05 16:00:15 1.11
+++ enabler.c 1999/02/13 03:50:51
@@ -126,7 +126,7 @@
err(1, set I/O context);
}
if (ioctl(fd, PIOCSDRV, drv))
- warn(set driver);
+ err(1, set driver);
close(fd);
return 0;
}
@@ -138,9 +138,9 @@
usage(msg)
char *msg;
{
- warnx(enabler: %s, msg);
+ fprintf(stderr, enabler: %s\n, msg);
fprintf(stderr,
-usage: pccardc enabler slot driver [-m addr size] [-a iobase] [-i irq]\n);
+Usage: enabler slot driver [-m addr size] [-a iobase] [-i irq]\n);
fprintf(stderr,
-m card addr size : card address (hex), host address (hex) size
(Kb)\n);
fprintf(stderr,
Index: pccardc/pccardc.c
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardc/pccardc.c,v
retrieving revision 1.7
diff -u -r1.7 pccardc.c
--- pccardc.c 1998/02/26 14:36:01 1.7
+++ pccardc.c 1999/02/13 03:51:35
@@ -84,10 +84,11 @@
{
int i;
- fprintf(stderr, usage: pccardc subcommand arg ...\n);
- fprintf(stderr, subcommands:\n);
+ fprintf(stderr, Usage:\n);
+ fprintf(stderr, \t%s subcommand arg ...\n, argv[0]);
+ fprintf(stderr, Subcommands:\n);
for (i = 0; subcommands[i].name; i++)
- fprintf(stderr, \t%s\n\t\t%s\n,
+ fprintf(stderr, \t%s\t: %s\n,
subcommands[i].name, subcommands[i].help);
return 1;
}
Index: pccardc/pccardmem.c
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardc/pccardmem.c,v
retrieving revision 1.10
diff -u -r1.10 pccardmem.c
--- pccardmem.c 1999/02/05 16:00:15 1.10
+++ pccardmem.c 1999/02/13 04:02:59
@@ -37,13 +37,6 @@
#include pccard/cardinfo.h
-static void
-usage()
-{
- fprintf(stderr, usage: pccardc pccardmem [memory-address]\n);
- exit(1);
-}
-
int
pccardmem_main(argc, argv)
int argc;
@@ -54,7 +47,8 @@
int fd;
if (argc 2)
- usage();
+ errx(1, Usage: %s pccardmem [ memory-address ], argv[0]);
+
sprintf(name, CARD_DEVICE, 0);
fd = open(name, O_RDONLY);
if (fd 0)
@@ -64,8 +58,8 @@
errx(1, arg error);
}
if (ioctl(fd, PIOCRWMEM, addr))
- warn(ioctl);
+ err(1, ioctl (PIOCRWMEM));
else
printf(PCCARD Memory address set to 0x%x\n, addr);
- exit(0);
+ return 0;
}
Index: pccardc/rdattr.c
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardc/rdattr.c,v
retrieving revision 1.4
diff -u -r1.4 rdattr.c
--- rdattr.c1998/02/27 08:00:18 1.4
+++ rdattr.c1999/02/13 04:06:35
@@ -24,11 +24,13 @@
* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/
+#include err.h
#include stdio.h
#include stdlib.h
#include unistd.h
#include fcntl.h
#include sys/ioctl.h
+
#include pccard/cardinfo.h
int
@@ -41,37 +43,31 @@
u_char *buf;
int fd;
off_t offs;
+
+ if (argc != 4)
+ errx(1, Usage: %s rdattr slot offs length, argv[0]);
- if (argc != 4) {
- fprintf(stderr, usage: %s rdattr slot offs length\n, argv[0]);
- exit(1);
- }
sprintf(name, CARD_DEVICE, atoi(argv[1]));
fd = open(name, O_RDONLY);
- if (fd 0) {
- perror(name);
- exit(1);
- }
+ if (fd 0)
+ err(1, %s, name);
+
reg = MDF_ATTR;
- if (ioctl(fd, PIOCRWFLAG, reg)) {
- perror(ioctl (PIOCRWFLAG));
- exit(1);
- }
+ if (ioctl(fd, PIOCRWFLAG, reg))
+ err(1, ioctl (PIOCRWFLAG));
+
if (sscanf(argv[2], %x, reg) !=
Re: Error handling for src/usr.sbin/pccard/pccardc/*
This is a patch for better (I think) error handling for pccardc.
(obtained from PAO3)
Please review.
Some of it I like, and others I don't.
@@ -138,9 +138,9 @@
usage(msg)
char *msg;
{
- warnx(enabler: %s, msg);
+ fprintf(stderr, enabler: %s\n, msg);
fprintf(stderr,
-usage: pccardc enabler slot driver [-m addr size] [-a iobase] [-i irq]\n);
+Usage: enabler slot driver [-m addr size] [-a iobase] [-i irq]\n);
The usage really is 'pccardc enabled', not 'enabler', so this should
stay, or at least converted to use argv[0] to be consistent with
the other changes.
Index: pccardc/pccardc.c
===
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardc/pccardc.c,v
retrieving revision 1.7
diff -u -r1.7 pccardc.c
--- pccardc.c 1998/02/26 14:36:01 1.7
+++ pccardc.c 1999/02/13 03:51:35
@@ -84,10 +84,11 @@
{
int i;
- fprintf(stderr, usage: pccardc subcommand arg ...\n);
- fprintf(stderr, subcommands:\n);
+ fprintf(stderr, Usage:\n);
+ fprintf(stderr, \t%s subcommand arg ...\n, argv[0]);
+ fprintf(stderr, Subcommands:\n);
for (i = 0; subcommands[i].name; i++)
- fprintf(stderr, \t%s\n\t\t%s\n,
+ fprintf(stderr, \t%s\t: %s\n,
subcommands[i].name, subcommands[i].help);
However, I'm not sure why we are changing the output. It seems
gratiutious.
-static void
-usage()
-{
- fprintf(stderr, usage: pccardc pccardmem [memory-address]\n);
- exit(1);
-}
-
int
pccardmem_main(argc, argv)
int argc;
@@ -54,7 +47,8 @@
int fd;
if (argc 2)
- usage();
+ errx(1, Usage: %s pccardmem [ memory-address ], argv[0]);
+
Again, we use warn one place, and then err. Any chance of keeping it
consistent in all places.
Nate
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Aladdin chipset SMBus support available!
Hi folks, I've just committed the alpm(4) driver to -current: the Aladdin SMBus driver. With an onboard system management chip (lm7x or w87381), it offers monitoring capabilities to recent Acer based motherboards like the ASUS P5AB. Example program to fetch temperature or voltages is available at http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ There's also an example program to fetch SDRAM info over the smbus. You may also want to know what smbus(4) is: http://www.freebsd.org/~nsouch/iicbus.html Feedbacks are wellcome. Nicholas. PS: A driver is also available for the Intel PIIX4, see intpm(4). -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
lpt0
Recently I noticed that lpt0 has been replaced by the ppbus stuff, in LINT. The problem is, I can't find any example as to how to set it up for a plain, vanilla printer ppbus has so many more capabilities than lp, I think it's embarrassed about it's dowdy origins. I don't know what controller to use (ppbus0 or maybe ppc0?) and the old device, lpt0, doesn't even exist in LINT anymore. I tried picking up the lines for ppbus0 and nlpt, which I guessed might be right, from LINT, and dropping them into my config file. They compile fine, but nothing is probed (my dmesg shows no printer) and I can't print. What's the right setup for a plain, ordinary IRQ 7 printer port? Please, don't answer if you're going to talk about connecting some parallel interfaced thing like a zip drive. I can't seem to find any docs on this, nor any mail messages (nothing in UPDATING either). There is much discussion about things like zip drive connecting, though ... +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: inetd problem
On 8 Jan 1999, Dag-Erling Smorgrav wrote: Can anyone tell me if the inetd realloc (and other) problems have been fixed yet? Searching Deja News shows conflicting reports. I checked the current diffs, and built version 1.46 - is this a safe version to use? It's been running on my local workstation for a few days now, but it really doesn't have any load on it. I'd like to copy it up to our webservers, but thought I would ask first. If you mean the dying daemons problem, it has probably been fixed in version 1.105 of src/sys/vm/swap_pager.c. No. People are constantly confused over this issue. There is (was) a bug in inetd related to the way it handles signals, which caused it to output junk pointer: too low to make sense (or sometimes too high to make sense) when under heavy load. It is not the same bug as the dying daemons bug. There have been two attemps to fix the inetd bug: one by Matt Dillon in rev. 1.42 and 1.43, and one by me (based on patches submitted by Graham Wheeler) in rev. 1.44 and 1.45. I haven't heard any complaints about the inetd bug lately, so I'll tentatively postulate that I succeeded. Did someone bring it back? Telnet output: Escape character is '^]'. inetd in realloc(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too low to make sense. Connection closed by foreign host. That's to a freshly rebooted machine (with 16 MB memory, 96 MB swap) that was doing a `make buildworld' when the X server on another machine that displayed the xterm with an rsh session to it. Since ssh ain't aware of Kerberos I'll have to attach a console to look into this further. Running 3.1-BETA, cvsup'ed Feb 10, world and kernel. Sorry, no kernel debugger :( but I'd appreciate it if someone would point me to documentation outlining how to configure the port speed in boot0/ boot1, and what option to set to still allow unattended reboots after a crash. -- Niels. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lpt0
You need: controller ppbus0 # The ppbus system device nlpt0 at ppbus? # The printer driver And finally the parallel port chipset interface, controller ppc0at isa? port? tty irq 7 drq 3 See ppbus(4) and/or http://www.freebsd.org/~nsouch/ppbus.html for more info about the ppbus architecture. On Sat, Feb 13, 1999 at 01:11:25PM -0500, Chuck Robey wrote: Recently I noticed that lpt0 has been replaced by the ppbus stuff, in LINT. The problem is, I can't find any example as to how to set it up for a plain, vanilla printer ppbus has so many more capabilities than lp, I think it's embarrassed about it's dowdy origins. I don't know what controller to use (ppbus0 or maybe ppc0?) and the old device, lpt0, doesn't even exist in LINT anymore. I tried picking up the lines for ppbus0 and nlpt, which I guessed might be right, from LINT, and dropping them into my config file. They compile fine, but nothing is probed (my dmesg shows no printer) and I can't print. What's the right setup for a plain, ordinary IRQ 7 printer port? Please, don't answer if you're going to talk about connecting some parallel interfaced thing like a zip drive. I can't seem to find any docs on this, nor any mail messages (nothing in UPDATING either). There is much discussion about things like zip drive connecting, though ... +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lpt0
On Sat, 13 Feb 1999, Chuck Robey wrote: Recently I noticed that lpt0 has been replaced by the ppbus stuff, in LINT. The problem is, I can't find any example as to how to set it up for a plain, vanilla printer ppbus has so many more capabilities than lp, I think it's embarrassed about it's dowdy origins. I don't know what controller to use (ppbus0 or maybe ppc0?) and the old device, lpt0, doesn't even exist in LINT anymore. I tried picking up the lines for ppbus0 and nlpt, which I guessed might be right, from LINT, and dropping them into my config file. They compile fine, but nothing is probed (my dmesg shows no printer) and I can't print. What's the right setup for a plain, ordinary IRQ 7 printer port? Please, don't answer if you're going to talk about connecting some parallel interfaced thing like a zip drive. I can't seem to find any docs on this, nor any mail messages (nothing in UPDATING either). There is much discussion about things like zip drive connecting, though ... The following works great for me: controller ppbus0 device nlpt0 at ppbus? device plip0 at ppbus? device ppi0at ppbus? device pps0at ppbus? controller ppc0at isa? port ? tty irq 7 +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lpt0
Nicolas Souchu nso...@teaser.fr writes: controllerppbus0 # The ppbus system devicenlpt0 at ppbus? # The printer driver OBTW, when are you planning to rename nlpt0 to lpt0? DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: inetd problem
: dying daemons bug. There have been two attemps to fix the inetd bug: : one by Matt Dillon in rev. 1.42 and 1.43, and one by me (based on : patches submitted by Graham Wheeler) in rev. 1.44 and 1.45. I haven't : heard any complaints about the inetd bug lately, so I'll tentatively : postulate that I succeeded. : :Did someone bring it back? Telnet output: : :Escape character is '^]'. :inetd in realloc(): warning: junk pointer, too low to make sense. :inetd in free(): warning: junk pointer, too low to make sense. :Connection closed by foreign host. : :That's to a freshly rebooted machine (with 16 MB memory, 96 MB swap) that :was doing a `make buildworld' when the X server on another machine that :displayed the xterm with an rsh session to it. Since ssh ain't aware of :Kerberos I'll have to attach a console to look into this further. Running :3.1-BETA, cvsup'ed Feb 10, world and kernel. : :Sorry, no kernel debugger :( but I'd appreciate it if someone would point :me to documentation outlining how to configure the port speed in boot0/ : -- Niels. Please do the following: uname -a strings /usr/sbin/inetd | fgrep Id -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
support for 3Com 3C575 network controller?
Is anyone out there successfully using a 3Com 3C375 network controller in there laptop? I got a new Dell Inspiron 7000 that came with one of these jewels and I haven't been able to find the trick to make it work. Here are some specifics. If you need more info please let me know. - The model number of the card is 3CCFE575BT-D. - I'm running 4.0-CURRENT up-to-date as of this morning. - 'pccardc rdattr 0 0 1' returns nothing but 0xFF. - 'pccardc dumpcis' doesn't show any info for the card. - The card is in slot0. - I have a Viking 56K modem in slot1 which I'm using right now to type this message. I had to add an entry to /etc/pccard.conf to get it to work. I'm assuming since the modem works I've at least got things setup correctly for pccardd. - When I fire up pccardd it complains about not having an entry for (), which I assume is related to the fact that dumpcis and rdattr don't return anything meaningful. Any help would be greatly appreciated. Thanks. Steve To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
CDR says: Attempt to query device size failed...
I've been getting the following message, usually within a minute or so after booting. It shows up only once, and doesn't seem to interfere with normal operation of the CDR: (cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc0:0:5:0): NOT READY asc:4,0 (cd1:ahc0:0:5:0): Logical unit not ready, cause not reportable cd1 at ahc0 bus 0 target 5 lun 0 cd1: PHILIPS CDD2600 1.06 Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable This is not a new error. It has been happening for several months now, but I never got around to reporting this. Any idea what the problem is? Thanks, Ben To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CDR says: Attempt to query device size failed...
On Sat, Feb 13, 1999 at 10:44:24PM +0100, Ben Stuyts wrote: I've been getting the following message, usually within a minute or so after booting. It shows up only once, and doesn't seem to interfere with normal operation of the CDR: (cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc0:0:5:0): NOT READY asc:4,0 (cd1:ahc0:0:5:0): Logical unit not ready, cause not reportable cd1 at ahc0 bus 0 target 5 lun 0 cd1: PHILIPS CDD2600 1.06 Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable Is the drive empty? It seems to me it's complaining because you don't have a disk in. -- ++ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| |lcrem...@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CDR says: Attempt to query device size failed...
Ben Stuyts wrote... I've been getting the following message, usually within a minute or so after booting. It shows up only once, and doesn't seem to interfere with normal operation of the CDR: (cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc0:0:5:0): NOT READY asc:4,0 (cd1:ahc0:0:5:0): Logical unit not ready, cause not reportable cd1 at ahc0 bus 0 target 5 lun 0 cd1: PHILIPS CDD2600 1.06 Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable This is not a new error. It has been happening for several months now, but I never got around to reporting this. Any idea what the problem is? It probably just means your drive doesn't have a CD in it. I've seen similar reports for other Philips and HP CD-R drives. In fact, that's why 0x04-type errors are acceptable for the CD driver's attach routine. It used to be that if it got an error back, the CD driver would only continue to attach if that error was a medium not present error. Because of those Philips and HP drives, though, the CD driver will attach even if the error is a not ready type error. Did you boot with -v? You probably shouldn't be getting the large error message above, just the condensed error message from the CD driver if you're not booting with -v. Ken -- Kenneth Merry k...@plutotech.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Aladdin chipset SMBus support available!
On Sat, 13 Feb 1999, Nicolas Souchu wrote: Hi folks, I've just committed the alpm(4) driver to -current: the Aladdin SMBus driver. Great, my newest mobo is an AcerLabs. With an onboard system management chip (lm7x or w87381), it offers monitoring capabilities to recent Acer based motherboards like the ASUS P5AB. I'm using a matsonic. Example program to fetch temperature or voltages is available at http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ There's also an example program to fetch SDRAM info over the smbus. I tried them, and there's the problem: all the ioctl()s they perform return EINTR! Has this driver been tested on many motherboards? Why should I expect an EINTR? Just wondering :) You may also want to know what smbus(4) is: http://www.freebsd.org/~nsouch/iicbus.html Feedbacks are wellcome. Nicholas. PS: A driver is also available for the Intel PIIX4, see intpm(4). -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CDR says: Attempt to query device size failed...
On Sat, 13 Feb 1999, Chris D. Faulhaber wrote: cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable There is no CD in the drive, which makes the device 'not ready' and therefore unable to query device size. If you put a CD in the drive and reboot, you shouldn't get this error. Correct. I forgot to mention in my original post that I also have another cdrom player in my system, and it doesn't generate this error. (cd0: MATSHITA CD-ROM CR-506 8S05 Removable CD-ROM SCSI-2 device) That's why I thought it was odd. Thanks for the reply! Ben To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CDR says: Attempt to query device size failed...
On Sat, 13 Feb 1999, Chris D. Faulhaber wrote: Interesting, this happens to both my CDR and regular CD: cd0 at ahc0 bus 0 target 3 lun 0 cd0: MATSHITA CD-ROM CR-508 XS03 Removable CD-ROM SCSI-2 device cd0: 10.0MB/s transfers (10.0MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 5 lun 0 cd1: PHILIPS CDD2600 1.07 Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable It may simply be the way the different devices report that the device is not ready/no medium present in the sense data... ...if no one else has any good ideas, I may just get a trace of the bus this evening and see exactly what is being reported (and when). Thanks, just let me know if I can do anything to help. I've just remade world and kernel, and here's the latest data from both my drives I get with boot -v: (cd0:ahc0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ahc0:0:4:0): NOT READY asc:3a,0 (cd0:ahc0:0:4:0): Medium not present cd0 at ahc0 bus 0 target 4 lun 0 cd0: MATSHITA CD-ROM CR-506 8S05 Removable CD-ROM SCSI-2 device cd0: 10.0MB/s transfers (10.0MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present ... (cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc0:0:5:0): NOT READY asc:4,0 (cd1:ahc0:0:5:0): Logical unit not ready, cause not reportable cd1 at ahc0 bus 0 target 5 lun 0 cd1: PHILIPS CDD2600 1.06 Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable From this you can see that both drives report differently that the tray is empty. Medium not present sounds less of a problem than ... cause not reportable. Also, cd0 status is shown immediately on booting, while cd1 status takes about a minute or so to appear. Ben To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lpt0
On 13 Feb 1999, Dag-Erling Smorgrav wrote: Nicolas Souchu nso...@teaser.fr writes: controller ppbus0 # The ppbus system device nlpt0 at ppbus? # The printer driver OBTW, when are you planning to rename nlpt0 to lpt0? Hopefully before 3.1 goes out...it would be a bummer to have one release with a different name than the rest; it confuses documentation that tries to cover multiple versions. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CDR says: Attempt to query device size failed...
On Sat, 13 Feb 1999, Kenneth D. Merry wrote: (cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc0:0:5:0): NOT READY asc:4,0 (cd1:ahc0:0:5:0): Logical unit not ready, cause not reportable cd1 at ahc0 bus 0 target 5 lun 0 cd1: PHILIPS CDD2600 1.06 Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable It probably just means your drive doesn't have a CD in it. I've seen similar reports for other Philips and HP CD-R drives. In fact, that's why 0x04-type errors are acceptable for the CD driver's attach routine. It used to be that if it got an error back, the CD driver would only continue to attach if that error was a medium not present error. Because of those Philips and HP drives, though, the CD driver will attach even if the error is a not ready type error. Makes sense. I forgot to mention in my original post that I also have another cdrom player in my system, and it doesn't generate this error. (cd0: MATSHITA CD-ROM CR-506 8S05 Removable CD-ROM SCSI-2 device) That's why I thought it was odd. Did you boot with -v? You probably shouldn't be getting the large error message above, just the condensed error message from the CD driver if you're not booting with -v. Yes, I did boot with -v. I though it would be useful to give some more info about what the driver returned. If I boot w/o -v, I just get the last three or four lines of the message. Thanks for the reply! Ben To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
sysinstall rc.conf
I just installed a 4.0-SNAP on my laptop (replacing the old 2.2.7 installation), and I must say once I stopped doing stupid things the install went nicely. But I noticed after I rebooted that 'myname.my.domain' didn't write out any of the config information to rc.conf (which, of course, doesn't exist). Is this known/planned/expected? This is the 02/12 SNAP. --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/~fullermd | * fulle...@futuresouth.com fulle...@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | The only reason I'm burning my candle at both ends, | *is because I haven't figured out how to light the* | middle yet | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: CDR says: Attempt to query device size failed...
On 13-Feb-99 Ben Stuyts wrote: I've been getting the following message, usually within a minute or so after booting. It shows up only once, and doesn't seem to interfere with normal operation of the CDR: (cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc0:0:5:0): NOT READY asc:4,0 (cd1:ahc0:0:5:0): Logical unit not ready, cause not reportable cd1 at ahc0 bus 0 target 5 lun 0 cd1: PHILIPS CDD2600 1.06 Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable This is not a new error. It has been happening for several months now, but I never got around to reporting this. Any idea what the problem is? There is no CD in the drive, which makes the device 'not ready' and therefore unable to query device size. If you put a CD in the drive and reboot, you shouldn't get this error. Thanks, Ben - Chris To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CDR says: Attempt to query device size failed...
On 13-Feb-99 Ben Stuyts wrote: On Sat, 13 Feb 1999, Chris D. Faulhaber wrote: cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable There is no CD in the drive, which makes the device 'not ready' and therefore unable to query device size. If you put a CD in the drive and reboot, you shouldn't get this error. Correct. I forgot to mention in my original post that I also have another cdrom player in my system, and it doesn't generate this error. (cd0: MATSHITA CD-ROM CR-506 8S05 Removable CD-ROM SCSI-2 device) That's why I thought it was odd. Thanks for the reply! Ben Interesting, this happens to both my CDR and regular CD: cd0 at ahc0 bus 0 target 3 lun 0 cd0: MATSHITA CD-ROM CR-508 XS03 Removable CD-ROM SCSI-2 device cd0: 10.0MB/s transfers (10.0MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 5 lun 0 cd1: PHILIPS CDD2600 1.07 Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable It may simply be the way the different devices report that the device is not ready/no medium present in the sense data... ...if no one else has any good ideas, I may just get a trace of the bus this evening and see exactly what is being reported (and when). - Chris To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
New print interface
I have to add an addendum here, to my previous question about the new config file setup for a simple printer. I was looking forward to seeing the probing come back to my dmesg, when I finally got it right, but seeing this: Feb 13 14:02:01 picnic /kernel: ppc0 at 0x378 irq 7 on isa Feb 13 14:02:01 picnic /kernel: ppc0: SMC FDC37C665GT chipset (EPP/PS2/NIBBLE) in COMPATIBLE mode Feb 13 14:02:01 picnic /kernel: ppb0: IEEE1284 device found /NIBBLE/ECP Feb 13 14:02:01 picnic /kernel: Probing for PnP devices on ppbus0: Feb 13 14:02:01 picnic /kernel: ppbus0: HEWLETT-PACKARD DESKJET 690C MLC,PCL,PML Feb 13 14:02:01 picnic /kernel: nlpt0: generic printer on ppbus 0 Feb 13 14:02:01 picnic /kernel: nlpt0: Interrupt-driven port I *never* expected to see the PNP functions actually pick up the name of my printer. I was economically bushwacked by the Windows corps into buying the 693C (the version with the Windows software floppies tacked on) so I was actually pleased that it ID'd the printer as the more generic 690C (sans the Windows extortia). Very nice. The mistake I'd made earlier was in not knowing that the config needed all 3 lines, not just some subset of 2 of them as I'd guessed. Great job, Nicolas! +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: sysinstall rc.conf
Today Matthew D. Fuller wrote: I just installed a 4.0-SNAP on my laptop (replacing the old 2.2.7 installation), and I must say once I stopped doing stupid things the install went nicely. But I noticed after I rebooted that 'myname.my.domain' didn't write out any of the config information to rc.conf (which, of course, doesn't exist). Is this known/planned/expected? This is the 02/12 SNAP. I think it's a feature. RELENG_3, as of this morning, does the same thing for a new install, except that the file exists but is empty except for the ...just the overrides... header. For an `upgrade' install it copies _all_ of the old rc.conf values into the new one, advertising them as just the overrides. -- Jack O'NeillSystems Administrator / Systems Analyst j...@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger j...@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages /dev/null -- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
lpt0 Not Found
I changed to the new nlpt. No luck. It appears that the parallel port is not found. I am running SMP-current, as of this afternoon. From uname -a: ... FreeBSD 4.0-CURRENT #0: Sat Feb 13 16:11:56 PST 1999 In my config, I changed to include ppbus0, nlpt0, and ppc0, exactly as in LINT: snip # Parallel-Port Bus # nlpt Parallel Printer controller ppbus0 # devicelpt0at isa? port? tty irq 7 vector lptintr controller ppc0at isa? disable port ? tty irq 7 device nlpt0 at ppbus? snip tomdean == dmesg == Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Feb 13 16:11:56 PST 1999 tomd...@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter i8254 frequency 1193025 Hz CPU: Pentium/P54C (586-class CPU) Origin = GenuineIntel Id = 0x525 Stepping=5 Features=0x3bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC real memory = 100663296 (98304K bytes) avail memory = 95055872 (92828K bytes) Programming 16 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec0 Preloaded elf kernel kernel at 0xf02b. Probing for devices on PCI bus 0: chip0: Intel 82434NX (Neptune) PCI cache memory controller rev 0x11 on pci0.0.0 ncr0: ncr 53c810 fast10 scsi rev 0x02 int a irq 11 on pci0.1.0 chip1: Intel 82378IB PCI to ISA bridge rev 0x88 on pci0.2.0 vga0: Matrox MGA 2064W graphics accelerator rev 0x01 int a irq 9 on pci0.6.0 de0: Digital 21041 Ethernet rev 0x11 int a irq 10 on pci0.8.0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface stray irq 7 Intel Pentium detected, installing workaround for F00F bug APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 de0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen Waiting 5 seconds for SCSI devices to settle (probe3:ncr0:0:3:0): COMMAND FAILED (6 ff) @0xf09dc000. (probe2:ncr0:0:2:0): COMMAND FAILED (6 ff) @0xf09dc600. (probe1:ncr0:0:1:0): COMMAND FAILED (6 ff) @0xf09dcc00. (probe0:ncr0:0:0:0): COMMAND FAILED (6 ff) @0xf09ba200. SMP: AP CPU #1 Launched! da0 at ncr0 bus 0 target 0 lun 0 da0: QUANTUM FIREBALL1080S 1Q09 Fixed Direct Access SCSI-2 device da0: 10.0MB/s transfers (10.0MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) da2 at ncr0 bus 0 target 2 lun 0 da2: QUANTUM EMPIRE_1080S 1240 Fixed Direct Access SCSI-2 device da2: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da2: 1029MB (2109376 512 byte sectors: 255H 63S/T 131C) da1 at ncr0 bus 0 target 1 lun 0 da1: QUANTUM FIREBALL ST3.2S 0F0C Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da1: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) changing root device to da1s1a cd0 at ncr0 bus 0 target 5 lun 0 cd0: TOSHIBA CD-ROM XM-5401TA 3605 Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present (da1:ncr0:0:1:0): tagged openings now 8 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: inetd problem
According to Matthew Dillon: strings /usr/sbin/inetd | fgrep Id ident(1) is your friend :-) /usr/sbin/inetd: $Id: inetd.c,v 1.46 1999/01/05 11:56:35 danny Exp $ -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: sysinstall rc.conf
On Sat, Feb 13, 1999 at 10:19:27PM -0500, a little birdie told me that jack remarked I think it's a feature. RELENG_3, as of this morning, does the same thing for a new install, except that the file exists but is empty except for the ...just the overrides... header. For an `upgrade' install it copies _all_ of the old rc.conf values into the new one, advertising them as just the overrides. It's always (in the past) saved the host/network config I setup during the installation (FTP), so I'd boot up afterwards and not have to reset the host name, network interfaces, default router, etc etc etc. Had me panicing for about 20 seconds trying to figure out what I messed up, until I realized that /etc/rc.conf was empty. It's the anti-POLA! ;) --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/~fullermd | * fulle...@futuresouth.com fulle...@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | The only reason I'm burning my candle at both ends, | *is because I haven't figured out how to light the* | middle yet | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lpt0 Not Found -- FOUND IT
I found my problem. I did a cut-paste from LINT. # Parallel-Port Bus # nlpt Parallel Printer controller ppbus0 # devicelpt0at isa? port? tty irq 7 vector lptintr device nlpt0 at ppbus? controller ppc0at isa? disable port ? tty irq 7 ^^^ | Should LINT be changed? Most machines using this will have printers. tomdean To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lpt0
FWIW, I would also like to see this happen. On 13 Feb 1999, Dag-Erling Smorgrav wrote: Nicolas Souchu nso...@teaser.fr writes: controllerppbus0 # The ppbus system devicenlpt0 at ppbus? # The printer driver OBTW, when are you planning to rename nlpt0 to lpt0? Hopefully before 3.1 goes out...it would be a bummer to have one release with a different name than the rest; it confuses documentation that tries to cover multiple versions. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: was: some woes about rc.conf.site
On Tue, Feb 09, 1999 at 06:40:58PM -0500, Christopher Masto wrote: mergemaster Yes, I have. It doesn't make much of a dent in the real problem, which is separating diffs like: variations on a theme deleted Good point. I adopted the rc.local solution some time ago, which simplified matters a lot for me. As yet, I've not been caught out by a new or changed default in rc.conf. -- Adrian Wontroba To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: sysinstall rc.conf
Hmmm. No, that's not what's expected. I've got a test release rolling on my own machine right now and will install my spam box with it once it finishes. The intention is definitely for the changes (and only those) to be written out to /etc/rc.conf. - Jordan I just installed a 4.0-SNAP on my laptop (replacing the old 2.2.7 installation), and I must say once I stopped doing stupid things the install went nicely. But I noticed after I rebooted that 'myname.my.domain' didn't write out any of the config information to rc.conf (which, of course, doesn't exist). Is this known/planned/expected? This is the 02/12 SNAP. --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/~fullermd | * fulle...@futuresouth.com fulle...@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | The only reason I'm burning my candle at both ends, | *is because I haven't figured out how to light the* | middle yet | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CDR says: Attempt to query device size failed...
Ben Stuyts wrote... On Sat, 13 Feb 1999, Chris D. Faulhaber wrote: Interesting, this happens to both my CDR and regular CD: cd0 at ahc0 bus 0 target 3 lun 0 cd0: MATSHITA CD-ROM CR-508 XS03 Removable CD-ROM SCSI-2 device cd0: 10.0MB/s transfers (10.0MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 5 lun 0 cd1: PHILIPS CDD2600 1.07 Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable It may simply be the way the different devices report that the device is not ready/no medium present in the sense data... ...if no one else has any good ideas, I may just get a trace of the bus this evening and see exactly what is being reported (and when). Thanks, just let me know if I can do anything to help. I've just remade world and kernel, and here's the latest data from both my drives I get with boot -v: There's really nothing to look into or trace. This is a well known problem with Philips/HP CD-R's. They bogusly report logical unit not ready when no CD is in the drive. Most CDROM drives report medium not present. i.e., this is all normal, your drives aren't broken. (cd0:ahc0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ahc0:0:4:0): NOT READY asc:3a,0 (cd0:ahc0:0:4:0): Medium not present cd0 at ahc0 bus 0 target 4 lun 0 cd0: MATSHITA CD-ROM CR-506 8S05 Removable CD-ROM SCSI-2 device cd0: 10.0MB/s transfers (10.0MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present ... (cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc0:0:5:0): NOT READY asc:4,0 (cd1:ahc0:0:5:0): Logical unit not ready, cause not reportable cd1 at ahc0 bus 0 target 5 lun 0 cd1: PHILIPS CDD2600 1.06 Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable From this you can see that both drives report differently that the tray is empty. Medium not present sounds less of a problem than ... cause not reportable. Also, cd0 status is shown immediately on booting, while cd1 status takes about a minute or so to appear. The fact that the Philips/HP CD-R's take a long time to report the fact that they have no media is also known. For some reason, it takes the drives up to 20 seconds to respond to a read capacity when they're empty. We then retry the read command, which takes up to another 20 seconds. If you want the probe message to appear quicker, leave a CD in the drive. Ken -- Kenneth Merry k...@plutotech.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: sysinstall rc.conf
I think it's a feature. RELENG_3, as of this morning, does the same thing for a new install, except that the file exists but is empty except for the ...just the overrides... header. For an `upgrade' install it copies _all_ of the old rc.conf values into the new one, advertising them as just the overrides. Erm. Neither of these behaviors are intended, if that's what's going on. Like I said, I'm waiting for my own release build to finish right now and will happily fix this if I can reproduce it. It should write only the customized variables in either the install or upgrade case. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: sysinstall rc.conf
Today Jordan K. Hubbard wrote: Erm. Neither of these behaviors are intended, if that's what's going on. Like I said, I'm waiting for my own release build to finish right now and will happily fix this if I can reproduce it. It should write only the customized variables in either the install or upgrade case. I'll watch for commit messages. I've got 3 pre-/etc/default 3.x boxen I can upgrade and two junk drives where I can test fresh installs. -- Jack O'NeillSystems Administrator / Systems Analyst j...@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger j...@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages /dev/null -- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: sysinstall rc.conf
until I realized that /etc/rc.conf was empty. It's the anti-POLA! ;) That's POMA :) - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Q) FreeBSD development load map
Could anyone point me where FreeBSD development load map if such one exists? Is threaded kenel implemented with 4.[0,1,2] ? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: sysinstall rc.conf
On Sat, 13 Feb 1999, Jordan K. Hubbard wrote: until I realized that /etc/rc.conf was empty. It's the anti-POLA! ;) That's POMA :) Could somebody tell me the meaning of those acronyms? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
