Re: pw group add problem
"David W. Chapman Jr." <[EMAIL PROTECTED]> wrote:
> When I run the command in the topic I get the following error.
>
> pw: group update: Inappropriate ioctl for device
>
> This works in -stable
>
> I noticed this problem while testing postfix-current which runs
>
> /usr/sbin/pw groupadd ${group} -h - || exit
>
>
> from pkg-install and also gives the above error message.
This should be fixed in rev 1.10 of src/usr.sbin/pw/grupd.c.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Doug Ambrisko wrote: > Robert Watson writes: > | On Wed, 29 Aug 2001, Garrett Wollman wrote: > | > < sai d: > | > > - I pushed the power button, and my system shut down cleanly! > | > > | > > Yes. ACPI brings some useful new features. 8) > | > > | > FSVO ``useful''. It's a real PITA to have to physically unplug the > | > machine when the kernel is wedged rather than have the power button > | > turn off the power. (The machine in question does not have a reset > | > switch.) As a sometime developer, I may well have a reason to power > | > the system off without performing any kind of shutdown. > | > | Most systems with soft power will perform a hard powerdown if you hold > | down the power button for a sufficiently long period of time (10 - 20 > | seconds). > > Correct ... and unfortunately it's done in hardware so you can trap it :-( > In some applications you want to make it really hard for someone to be > able to turn it off when a "power off" is not equivalent to "pull the > plug" and the "pull the plug" is safer for the system due to power supply > design. Most systems have a 4-second override so that holding down the power button for 4 seconds forces it off. However, my vaio is not one of these. I've had the joy of having to unplug the power and then remove the battery to get out of an acpi wedge. Anyway, IMHO, this is the least of our problems. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
Robert Watson writes: | On Wed, 29 Aug 2001, Garrett Wollman wrote: | > < said: | > > - I pushed the power button, and my system shut down cleanly! | > | > > Yes. ACPI brings some useful new features. 8) | > | > FSVO ``useful''. It's a real PITA to have to physically unplug the | > machine when the kernel is wedged rather than have the power button | > turn off the power. (The machine in question does not have a reset | > switch.) As a sometime developer, I may well have a reason to power | > the system off without performing any kind of shutdown. | | Most systems with soft power will perform a hard powerdown if you hold | down the power button for a sufficiently long period of time (10 - 20 | seconds). Correct ... and unfortunately it's done in hardware so you can trap it :-( In some applications you want to make it really hard for someone to be able to turn it off when a "power off" is not equivalent to "pull the plug" and the "pull the plug" is safer for the system due to power supply design. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
On Wed, 29 Aug 2001, Garrett Wollman wrote: > < said: > > > - I pushed the power button, and my system shut down cleanly! > > > Yes. ACPI brings some useful new features. 8) > > FSVO ``useful''. It's a real PITA to have to physically unplug the > machine when the kernel is wedged rather than have the power button > turn off the power. (The machine in question does not have a reset > switch.) As a sometime developer, I may well have a reason to power > the system off without performing any kind of shutdown. Most systems with soft power will perform a hard powerdown if you hold down the power button for a sufficiently long period of time (10 - 20 seconds). Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
< said: > - I pushed the power button, and my system shut down cleanly! > Yes. ACPI brings some useful new features. 8) FSVO ``useful''. It's a real PITA to have to physically unplug the machine when the kernel is wedged rather than have the power button turn off the power. (The machine in question does not have a reset switch.) As a sometime developer, I may well have a reason to power the system off without performing any kind of shutdown. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: ACPI CHANGES AFFECTING MOST -CURRENT USERS
I have just committed some changes to the way that ACPI works in current. This has an impact on all -current users, so please take a few seconds to read this and feel free to ask questions. The loader now detects ACPI in your system, and loads the ACPI module if it is present. This has major ramifications for the device probe and attach phases of system initialisation. - Root PCI bridges are detected using ACPI. - PCI interrupt routing is now performed using ACPI. - The PnP BIOS is disabled and onboard peripherals are detected using ACPI, and attach to ACPI and not isa. - System-owned resources are detected and reserved by ACPI. - The default system timecounter will be the ACPI timer. There are other changes, these are just the really big ones. I'll try to answer some of the FAQs here, to keep the discussion focussed. Regards, Mike ACPI Integration Mini-FAQ - Who died and left you in charge? - Why are you making such major changes? ACPI is the direction that the Intel/PC architecture is taking. The dominant operating system family on this platform uses ACPI heavily and has done so for the last five years. We have to follow suit or fall badly behind. In addition, ACPI brings us functionality that we have not had in the past. Much discussion on ACPI has been had, and the current direction reflects such consensus as has been reached so far. - Help! ACPI crashes my system. You can disable ACPI by unsetting the 'acpi_load' variable in the loader (for temporary testing) or by setting hint.acpi.0.disable=1 in /boot/device.hints. If you find that you need to do this, please let the FreeBSD ACPI developers ([EMAIL PROTECTED]) know so that we can investigate the problem. - The ACPI module is huge! Do I have to use it? No, you don't. But you may lose functionality if you choose to disable it. The system's legacy probe mechanisms have not been affected by these changes, and we will continue to support legacy platforms for the forseeable future. - Where can I find more information on ACPI? The ACPI homepage is at http://www.teleport.com/~acpi The Intel ACPI Component Architecture homepage is at http://developer.intel.com/technology/iapc/acpi The acpi(4) manpage offers an overview of the debugging options for the Intel ACPI CA code (the core of the ACPI subsystem). An acpi(9) manpage is under development. - Can I compile ACPI into the kernel for debugging? Yes. See NOTES for details on this. Note that you must disable loading of the ACPI module to avoid confusing the kernel linker if you do this. - Is ACPI compatible with APM? No. You must disable APM if you are using ACPI. - Does this change make FreeBSD a "PnP OS"? Not entirely. You may still need to set BIOS "PnP OS" to "NO" in your BIOS setup. - Do I need to make any other BIOS adjustments? You should update your BIOS to the latest version available for your system. If your system has an option to enable ACPI, it should be enabled (typically under 'power management'). - Can ACPI damage my system? Under ACPI, the operating system is meant to be responsible for thermal management of the system. Our thermal management code has only been lightly tested, and many systems still ignore the OS and perform their own thermal management. You should monitor your system for any unexpected behaviour when using ACPI, not just overheating. - I pushed the power button, and my system shut down cleanly! Yes. ACPI brings some useful new features. 8) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pw group add problem
When I run the command in the topic I get the following error.
pw: group update: Inappropriate ioctl for device
This works in -stable
I noticed this problem while testing postfix-current which runs
/usr/sbin/pw groupadd ${group} -h - || exit
from pkg-install and also gives the above error message.
-
David W. Chapman Jr.
[EMAIL PROTECTED] Raintree Network Services, Inc.
[EMAIL PROTECTED] FreeBSD Committer
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: testing KSE
the crash I saw was on today's sources I think. That's why I'm asking for the same revision of the -current to be used.. My test box has no floppies... On Wed, 29 Aug 2001, David W. Chapman Jr. wrote: > On Wed, Aug 29, 2001 at 03:42:55PM -0700, Julian Elischer wrote: > > can you try the same with a "matching" -current? > > I heard that msdosfs is bombing there too. > > (just to confirm this.. if it works there but not with KSE > > then we have work to do :-) > > > > I'm just tuning into this thread a little late, so excuse the > ignorance that I show. I have no problems with msdosfs > > FreeBSD dwcjr.inethouston.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue > Aug 28 22: 23:07 GMT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DWCJR i386 > > -- > David W. Chapman Jr. > [EMAIL PROTECTED] Raintree Network Services, Inc. > [EMAIL PROTECTED] FreeBSD Committer > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: testing KSE
On Wed, Aug 29, 2001 at 03:42:55PM -0700, Julian Elischer wrote: > can you try the same with a "matching" -current? > I heard that msdosfs is bombing there too. > (just to confirm this.. if it works there but not with KSE > then we have work to do :-) > I'm just tuning into this thread a little late, so excuse the ignorance that I show. I have no problems with msdosfs FreeBSD dwcjr.inethouston.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Aug 28 22: 23:07 GMT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DWCJR i386 -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: testing KSE
can you try the same with a "matching" -current? I heard that msdosfs is bombing there too. (just to confirm this.. if it works there but not with KSE then we have work to do :-) On Wed, 29 Aug 2001, Carlo Dapor wrote: > The most recent diffs applied nicely. > The kernel built nicely, as well. > > But I could not mount an msdosfs partition, it bombed terribly. > I don't have any ouytput, though, sorry. > > Ciao, derweil, > -- > Carlo > > PS: Only two or three modules did not compile, ncp and smbfs(?) I think > > > After doing a single buildworld of a normal tree, > > The best thing you can do to test it is just use is as much as possible > > as a replacement for your normal kernel, so that > > we can try out as many 'paths' through the kernel as possible. > > Everyone does a few buildworlds so that's quite tested.. > > not a lot of Music gets played on it, or videos watched etc. > > (linux emulation for example) > > Try som ekernel modules after you have tried the same modules built in.. > > > > that sort of thing.. > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: testing KSE
The most recent diffs applied nicely. The kernel built nicely, as well. But I could not mount an msdosfs partition, it bombed terribly. I don't have any ouytput, though, sorry. Ciao, derweil, -- Carlo PS: Only two or three modules did not compile, ncp and smbfs(?) I think > After doing a single buildworld of a normal tree, > The best thing you can do to test it is just use is as much as possible > as a replacement for your normal kernel, so that > we can try out as many 'paths' through the kernel as possible. > Everyone does a few buildworlds so that's quite tested.. > not a lot of Music gets played on it, or videos watched etc. > (linux emulation for example) > Try som ekernel modules after you have tried the same modules built in.. > > that sort of thing.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: testing KSE
On Wed, 29 Aug 2001, David Wolfskill wrote: > OK; maybe I'm just not cut out to be trying to do this. > > The first time I tried the usual approach, my build machine locked up, > hard. (It was running the previous days' -CURRENT -- and I was able to > build today's -CURRENT on a copy of it). Once I got home, I found that > nothing would make the machine do anything except for a power cycle or a > reset. In particular, Ctl+Alt+Esc didn't do anything. > > I tried again, and sometime after I started it, I saw your message that > says "You need to do build the kernel outside of the tree you will > "make buildworld" in so that the build tree is untouched" And sure > enough, the 2nd attempt terminated: > After doing a single buildworld of a normal tree, The best thing you can do to test it is just use is as much as possible as a replacement for your normal kernel, so that we can try out as many 'paths' through the kernel as possible. Everyone does a few buildworlds so that's quite tested.. not a lot of Music gets played on it, or videos watched etc. (linux emulation for example) Try som ekernel modules after you have tried the same modules built in.. that sort of thing.. > > But I'm having no luck figuring out what you want folks to do, based on > your (quoted) comment. Here's what I usually do (within "script"): [...] > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current snd: where 'bass' and 'treble' gone?
I have plain SB Live! Value which works with pcm+emu10k1 modules long time ago. Today when I try I found that 'bass' and 'treble' options dissapearse from mixer capabilities, but some unknown and wrong options appearse instead, like 'video' (SB don't have video). I think something wrong with treating AC97 mixer capabilities in emu10k1 code. Fix this thing, please. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
18 Year Old Blonde Girl In Need Of Money
100% HARDCORE PORN AT HARDCORE SEX 5 out of 5 compulsive masturbators agree, this is the place to jerk-off! CLICK HERE FOR INSTANT ACCESS http://3322253298 Choose a FREE name and password, and then get ready to cum! 1+ free photos 1000's of free videos 100's of free live shows 100's of free voyeur cams 100's of downloadable videos Don't miss out on your TRIAL MEMBERSHIP http://3322253298 This email has been sent to you because someone at this e-mail address subscribed to this service. If you wish to remove yourself from this service please simply send a remove request to [EMAIL PROTECTED] with the e-mail address you wish to remove. All models are at least eighteen years of age. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Undeletable files
On Wed, Aug 29, 2001 at 07:19:11AM -0500, Jacques A. Vidrine wrote: > On Wed, Aug 29, 2001 at 02:09:35AM -0500, David W. Chapman Jr. wrote: > > I cannot seem to delete some files that fsck can't seem to fix. > > Use clri(8) to stomp the directory that is giving you problems, then > run fsck again. Repeat until the filesystem is clean. > Thanks, that seemed to do it. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Undeletable files
On Wed, Aug 29, 2001 at 02:09:35AM -0500, David W. Chapman Jr. wrote: > I cannot seem to delete some files that fsck can't seem to fix. Use clri(8) to stomp the directory that is giving you problems, then run fsck again. Repeat until the filesystem is clean. Then find your backup :-) Cheers, -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unknown PNP hardware
>> I once wrote the following patch to deal with this problem by
>> probing ISA devices in the following order.
>>
>> 1. sensitive ISA devices described in device.hints
>> 2. PnP BIOS ISA devices
>> 3. other ISA devices described in device.hints
>> 4. PnP ISA devices
>
>This order is still slightly wrong. You need to do:
>
> 0. Disable ALL PnP devices which can be disabled.
Ya, the patch disables PnP devices (if they can be disabled) before it
starts probing devices. It enables each PnP device only when it is
about to be probed...
> 1. PnP devices (of any kind) which cannot be disabled, or which only
>have a single configuration. These devices which cannot be disabled
>need a placeholder attached to them if a driver doesn't claim them,
>or some other mechanism so that their resources are never used.
> 2. Sensitive hinted ISA devices.
> 3. Other ISA devices.
> 4. Other PnP devices.
Ok, revised patch is attached.
Kazu
begin 666 isapnp.diff2.gz
M'XL(")RZC#L VES87!N<"YD:69F,@"]6%%SVD80?I9_Q2:=>L (D# 86VXR
MID :9HAQ@?BE[6B$.,R-A41/@L3327][=^].( %VF*039A#HM'N[M_OMMW?J
MA5/VV0$>>ZX?+1916/%/WGS_YV38'L&,!\R!:BS\:OM^)'_CI[B*MJI9>^;Z
M1+!$<+;FX0,(_(EY%()=J9V?3/EL!N45E 7=YMTLE\NY :-F67;5NJS:%EA-
MIV$Y=MV0LY1*I<.2M2NP+IQZW;&MDYL;*->;MGD%I7JS:38LN+DY@1,P9H*Q
M@C][,.&#.^Y^N"M>XW#)J)[A!<[@3D03!LMP"5-TW64"8Q!'*T%3S;B(DXH4K^*5
MSZ PB:)DS<0DBED1AXREX&$R*[RF!2[)%]>?\V J6.@ W5-0[\*[U+L_P]>X
M@)(QBP04.+P!ZQHX_ )AJH6WI5(1_J&YE8Z;@'R(PJG0'_POFL2($['R$QE<
M)0MG'/^@9*=[/Q[T1JV"5"&3)%_%53_R)8116,Z$K%*IJ 7*%;X:MWK]W]UW
MO>%H7#BE^/A=1'C!$(D"#@1PGV6X?D3 TQNG$#'B>''25[).C%,7\(W4VJ=9QTX-/ IH_E
MA' F HSLUO)&^?I9'9>%B7@BS=0!Z8%.K,*+%TY=+TD\?ZZ=P!6#I;Q/(1"S
MA#*,*(VUJR:*I%/*6C (TVT)8R]\@E7H!4'D>PF;9@"=1/#(V!(BRE*JE!;.
M3$0+6,6$6'R\J.CG,D_&J-\;C=UW@V&WU7Y?P/68( (3 AX^ID%3Z,%'Y;=H
M<3-J8(& X(1?]8Q/K_63?*RDPP6:%3TR%=A-+:D (/63IR7+#Y_BE/D1RX1_
M\6OK*-'P%_DCKW3!+Y(+1JY,(;AEGQ-9KHC<(-BMCV>I0BD?Y(NO3%E!XQ1:
MV"<5.(Y4:,(]8I$L>GENVC4H-#)XV"A*/
M$'H+!G/TV$3T,.!)IK8W1J8^B:6@.,2D&[#KU1,(=%)!?EXK;*9U($W"S[3R
MO-RNS>O=NCM43;M*VJ5,- @W@!DW7J[>ZW3I>^N;K&+W@85,<%^M466UL$5[
M,<-21W $G)[N^2TM?84U0*YDB_YWG,CB"10I;ID:V2);!>B$!G1*#R_K"K;P
M>$@I>VF6[ZV#PS5P=67:-M; !=: +6O@R.:6+P%0)2 ;T!F,MBTNK8!/6 [2
MLZE1!2B=\2[E876&"JL@P8!DX+18XE9S*L,Q$1'W)6YO?O6T.VT;UL?N@ZYOIVCL$+(+Q/A)L6=TI8!T9-1!J=LYJ&.0S9P
M![\2(71O!P@/5>#2W:N:=/>BN75WSTDTNO8"B?;CG-WQBYQ&;,6T3?4$G!7U
M;%_UMJ#<+6[]O6S6S":4KAJV>:G=5SQW/TT= Z!EE'=%A=5 C!
MWM[);_Z#3W[S9T]^S=S!KYEW?JV-=H$DCQVE0YSYQJ,OMY8QO':\!="?44?93P@H2)$+&\QJ)5S62K
MZT^PO#:Z>"NU?:SWB><_PFP5^G0H5'KKB$^-G+PG'JZ-K (.K!9(9HJWM\!7
M6KI42>/P'DG:^2(1\Q/6!,>3T>:LAAI%HU X<*HK0J8W\+4G8BEC(
M%P9X3>F-!3&C$HO$E ED)N*OP;#3';JCNV[[8[\U[MUW%4>DA^I?/X[<5J?C
MMM_W^IW"$D^NM).5$Y@R;[BM#7DB2>,HG=N/_;X)95L2&Y&"UI)DLJ$_FHY2
M+"E%HB8E%+UI!5D*GDCD6P*\\:-5J&^V:4?U]DY=\765OW=,[E
MC>(+VZ[6&F!=.O:Y3O:'GRX0W1T,"U[8V9V4'7"M(B1RJ5;C3J1
MF-UH:!8C\5:[W1V-!L-"C'M^#\^UVAG<"B;%'9$@>N#(,7B0A:U_AP33MFW"
MQCLE5LJ)*4B9H+PU(=>AR7$\GB)IDJI8>/&CJPB'B[_=)0NGF-L"D2'A4$M*
5;MS?B:<]-"&*0O'_ \7R/73%
end
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: old BSD/OS binary coredumps
On Wed, Aug 29, 2001 at 08:50:53AM +0200, Joerg Wunsch wrote: > After upgrading to current-2001-08-28, my old BSD/OS Netscape 3 binary > no longer works. It coredumps right away at startup, before opening > any window. (Running it as "netscape3 -help", where it only produces > a usage message, isn't affected.) > > Now the interesting part: i wanted to get an idea why this happened, > and ran it through ktrace. Voila, that still works! Likewise when > running through truss. I saw something like this some time ago, too. In my case it was because in kern_sysctl:ogetkerninfo(), in "case KINFO_BSDI_SYSINFO:", the variable "size" is not always given a value. Maybe the patch in http://www.FreeBSD.org/cgi/query-pr.cgi?pr=25476 fixes it for you, too? (Hm, now I think my patch could need a comment: "size" will only be returned if needed==0. There are two ways this can happen: 1) "case KINFO_BSDI_SYSINFO" has been executed: In this case, "size" will have been set to 0, too. "size" is of size_t, i.e. positive or 0.) 2) on of the other cases has been executed: they all set "size".) > Does anybody have an idea what might have changed, If it's what I suspect, just the random inital value of "size" changed... > and why's that odd behaviour with the syscall tracers? I'd like to know that, too. Bye, Philipp To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Junior Kernel Hacker task: Get rid of NCCD constant.
Poul-Henning Kamp wrote: > Assignment: > > There is no reason for the NCCD constant to exist anymore. > > The CCD driver already has cloning support but CCDs "softc" > structure is statically allocated for NCCD devices. > > Change the CCD driver to dynamically allocate memory as needed, > the MD driver can be used as example as the overall morphology > of the two drivers are the same. I'll do that. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/dev/cardbus cardbus.c cardbus_cis.c cardbus_cis.h cardbusvar.h src/sys/dev/pccard card_if.m pccard.c pccardvar.h src/sys/dev/pccbb pccbb.c pccbbvar.h src/sys/sys rman.h
In message <20010829115934.T594-10@nihil> Michael Reifenberger writes: : On Tue, 28 Aug 2001, Jonathan Chen wrote: : ... : > > The boot message is attached in boot.txt. : > > The backtrace is following tomorrow ( hopefully after building a new kernel) : > : > That won't be necessary. I now know what causes the panic. Actually, : > that's not really important. There's something strange going on with the : > second non-ep card insertion. Is this a memory card you're trying to use? : Yes. : It is either a SANDISK Smartmedia 64MB or a Apacer CF 64MB. : Both should attach to the ad driver... The ata driver hasn't been NEWCARDed yet. It needs to be updated. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/dev/cardbus cardbus.c cardbus_cis.ccardbus_cis.h cardbusvar.h src/sys/dev/pccard card_if.m pccard.c pccardvar.hsrc/sys/dev/pccbb pccbb.c pccbbvar.h src/sys/sys rman.h
On Tue, 28 Aug 2001, Jonathan Chen wrote: ... > > The boot message is attached in boot.txt. > > The backtrace is following tomorrow ( hopefully after building a new kernel) > > That won't be necessary. I now know what causes the panic. Actually, > that's not really important. There's something strange going on with the > second non-ep card insertion. Is this a memory card you're trying to use? Yes. It is either a SANDISK Smartmedia 64MB or a Apacer CF 64MB. Both should attach to the ad driver... Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: old BSD/OS binary coredumps
Joerg Wunsch wrote: > After upgrading to current-2001-08-28, my old BSD/OS Netscape 3 binary > no longer works. It coredumps right away at startup, before opening > any window. (Running it as "netscape3 -help", where it only produces > a usage message, isn't affected.) > > Now the interesting part: i wanted to get an idea why this happened, > and ran it through ktrace. Voila, that still works! Likewise when > running through truss. > > Does anybody have an idea what might have changed, and why's that odd > behaviour with the syscall tracers? That is certainly odd. Can you put a .tar.gz of whatever is needed to replicate it somewhere? eg: on http://freefall/~joerg/ ? What is the last -current kernel build date that it ran under? Have you removed COMPAT_43 by any chance? Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
