Re: Where to start for someone new to kernel coding
On Wed, Oct 06, 2004 at 09:33:50PM +0200, John Oxley wrote: I want to extend the disk quota system: - Implement a user space daemon to control it. - Pass control from the kernel to the user space daemon. [skipped] Is this at all possible, and if so, where should I start looking for coding with the kernel. Quota checks are implemented in chk*() functions from the sys/ufs/ufs/ufs_quota.c file. If you want to implement your idea as a replacement of existing QUOTA, then you need to modify this file and probably some others. It is also possible to change addresses of these functions, but this is a hack. Another way is using stackable VFS or MAC framework. In these approaches your module will have control before actual FS code is called. And a module can decide what to do: use already loaded own quota policy in the kernel or send a message to a process, which will decide what to do and send a reply back to your module. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sudden Reboots
On Monday 04 October 2004 04:04 pm, Jim Durham wrote: On Monday 04 October 2004 03:06 pm, Doug Russell wrote: On Mon, 4 Oct 2004, Jim Durham wrote: The reboots started out happening at 5.15 pm or so. I had them unplug the server completely from AC and restart it and now it's happening withing a few minutes of 12:40pm every day. The 'last' command output is the only thing showing anything log-wise. Look at this: reboot ~ Mon Oct 4 12:33 reboot ~ Sun Oct 3 12:37 reboot ~ Sat Oct 2 12:42 reboot ~ Fri Oct 1 12:45 That is strange What is that machine doing at that time? Does it start a backup job, or any kind of maintenance at that time? Anything at all? I'd monitor what the heck the machine is doing to some remote machine and see what goes on when it dies. Later... Doug Well... I'm trying to do too many things at the same time and not thinking. I thought about it and also ran 'last -f /var/log/wmtp.1' and found the whole sequence...and added my recent reboot info to the top and here is what I got. reboot ~ Mon Oct 4 14:54 reboot ~ Mon Oct 4 12:33 reboot ~ Sun Oct 3 12:37 reboot ~ Sat Oct 2 12:42 reboot ~ Fri Oct 1 12:45 reboot ~ Thu Sep 30 12:33 reboot ~ Thu Sep 30 08:54 reboot ~ Wed Sep 29 08:41 reboot ~ Tue Sep 28 17:20 reboot ~ Mon Sep 27 17:28 reboot ~ Sun Sep 26 17:28 reboot ~ Sat Sep 25 17:37 reboot ~ Fri Sep 24 17:38 reboot ~ Thu Sep 23 17:42 reboot ~ Wed Sep 22 17:50 reboot ~ Tue Sep 21 17:52 reboot ~ Mon Sep 20 17:57 reboot ~ Sun Sep 19 17:57 reboot ~ Sat Sep 18 17:56 Now, the machine was powered down on Sept 17 because of an all-day power failure. It started doing this on the 18th ,starting at 5:56pm and working earlier until Sept 29, when I upgraded from 4.9 to 4.10 p3. Then it started rebooting at 8:45 aprox and I had the customer shut down the machine completely on the 30th and remove the AC from the rear connector and wait a few minutes and bring it back up. That's when it started rebooting at 12:30 or so. Googling for Freebsd reboots at same time every day will produce hits on people with the same problem so this is not just me. I checked crontab, etc and there's nothing coinciding and also, apparently every time you reboot the machine, the cycle changes, so how can it be an external event? Boy...I'm confused... 8-) There was one Google posting that maintained that this one guy fixed it by removing IPV6 from the kernel. I'm trying this at the moment. Of course, I had to reboot to change the kernel, so the times will probably change if it keeps rebooting. It also just hit me that the time doesn't change much if the machine reboots itself, but changes if you upgrade or do a controlled reboot. Wow... This is a followup posting on the above problem.. After removing IPV6 from the kernel and recompiling ,(note that I had recompiled the kernel earlier during this troubleshooting series with no effect) , the problem has gone away. The machine has been up for over 2 days with no reboots. So, to recap: Machine reboots at aprox 23hrs 57 minutes of uptime at ~12:30pm.. Upgraded to latest 4.10p3 sources. Still reboots at 23hrs 57mins, but at different time of day, ~8:15am. Unplugged machine totally from AC and restarted. Still reboots at 23:57 intervals, but time is now changed again, ~2:55pm. Recompiled kernel, removing IPV6. Problem stops. Up now for over 2 days for first time in weeks. Note1: The 23:57 is the usual interval. Sometimes it varied by a few minutes. Note2: 'healthd' showed normal operation of Power Supply with no log entries. Note3: The IPV6 idea was gleaned from a Google search of earlier postings on same problem. Note4: Another posting claimed a cure of this problem by changing network card. Observation: When the machine reboots itself, the time of the reboots seems to stay very close to 23:57 intervals. When you reboot on command, the interval stays the same, but the time of day changes, and does not coincide with the commanded reboot time. I have no conclusion about this. Thanks to all who made suggestions. -Jim Durham ___ [EMAIL
Re: Sudden Reboots
Can this be some kind of misbehaved hardware watchdog (say, built into motherboard or network card)? So, to recap: Machine reboots at aprox 23hrs 57 minutes of uptime at ~12:30pm.. Upgraded to latest 4.10p3 sources. Still reboots at 23hrs 57mins, but at different time of day, ~8:15am. Unplugged machine totally from AC and restarted. Still reboots at 23:57 intervals, but time is now changed again, ~2:55pm. Recompiled kernel, removing IPV6. Problem stops. Up now for over 2 days for first time in weeks. Note1: The 23:57 is the usual interval. Sometimes it varied by a few minutes. Note2: 'healthd' showed normal operation of Power Supply with no log entries. Note3: The IPV6 idea was gleaned from a Google search of earlier postings on same problem. Note4: Another posting claimed a cure of this problem by changing network card. Observation: When the machine reboots itself, the time of the reboots seems to stay very close to 23:57 intervals. When you reboot on command, the interval stays the same, but the time of day changes, and does not coincide with the commanded reboot time. I have no conclusion about this. Thanks to all who made suggestions. -Jim Durham ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
fsck: How to reduce memory usage - to avoid out of swap on boot ?
On 4.10-RELEASE with real memory = 10485760 (10240K bytes) big disc partition:disklabel ad0s1 sectors/unit: 160071597 #size offsetfstype [fsize bsize bps/cpg] h: 156613309 34582884.2BSD 2048 1638489 # (Cyl. 215*- 9963*) On a dirty reboot, fsck hangs single user saying: out of swap space. This on an embedded headless host, delivered to remote sites. Plugging in a monitor card is problematic, so it needs to come up multi user net reachable. Options: - Split the partition in several. - Ugly, Maybe I could remerge them with ccd or vinum?] not tried those before, but still an ugly solution. - More memory: Mainboard has 2M just 1 slot, currently with an 8M RAM, but I'm looking for a 16M slice will see if mboard accepts it if fsck considers that enough. ( After forcing it multiuser I saw: # UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND # 0 455 419 113 42 0 7064 1820 - R+p12:42.52 fsck -y /usr1 for comparison on another 4.10-RELEASE box with an 18G drive it grew to # 0 625 553 0 -6 0 7580 7448 physst DL+ p00:12.50 fsck -y /usr3 (Could man fsck document roughly how much ram needed for what size disc ? ) - Add ,noato to /etc/fstab manually fsck mount /usr1 from rc.local (I imagine swapinfo by then reports more swap available) - ugly. I think Ive tried that before somewhere else recently, (on 5-current admittedly) I recall no clean bit caused a hang, even thouth ,noauto - /usr/src/sbin/fsck/fsck.h, maybe I could eg halve one or both of these: #define MAXBUFSPACE 40*1024 /* maximum space to allocate to buffers */ #define INOBUFSIZE 56*1024 /* size of buffer to read inodes in pass1 */ I quickly paged through all of /usr/src/sbin/fsck/ but didnt see much else likely. Any suggestion what to hack ? Must be some define type `take so much RAM' lines in there :-) PS I think it's pass1 that's running out of swap, but maybe pass2, I can't check till backup complete. Ideas ? - Julian Stacey. Unix,C,Net Sys. Eng. Consultant, Munich. http://berklix.com Mail Ascii; Html deleted as Spam. Ihr Rauch = mein allergischer Kopfschmerz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: syslog() reentrant when compiling with -pthread?
On 2004-10-07 07:20, Marc Balmer [EMAIL PROTECTED] wrote: 1) openlog() must be called before any threads that use syslog() are started. 2) The first argument to openlog() must not be NULL. 3) The %m Format String must not be used in syslog() calls. Can (3) this be solved by changing all the calls to strerror() with equivalent calls to strerror_r() in the syslog() implementation? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: attaching ugen(4) on multi interface USB devices
Bernd Walter writes: On Wed, Oct 06, 2004 at 03:30:05PM +0300, Niki Denev wrote: Hello everyone!, The last 1-2 days i've been trying to make some userspace OBEX utilities to work with a USB based Nokia GSM phone and doing this i discovered something that confuses me a little: The phone in question is Nokia 6230 and it has an USB interface. The phone has 11 interface descriptors, 2 of them are used for the Modem and CM over data. Judging from the windows drivers it seems that four of the other interfaces are OBEX compatible. But if i kldload umodem and plug the phone it detects only one ucom(4). and if i plug the phone without any u* modules loaded the kernel attaches ugen0 only. From what i understand it attaches the ugen0 using the info in the first interface descriptor in the device. Wouldn't it be more usefull for the kernel to attach ugen for every unknown interface in a device. For example when attaching the phone with umodem loaded, i will get the ucom(4) device and the other unrecognised interfaces will show up as ugens ? What do you think about that? ugen attaches to the whole device and supporting all interfaces in one driver instance. thanks, i saw this in the ugen(4) manpage. it seems that i haven't noticed it before :( If you already an interface driver atatched then ugen fails to attach the whole device. well, i think that this can be a problem sometimes. actually i don't need kernel driver for obex devices, because everyting can and will be probably better done in the userland via ugen. but this means that the phone modem and obex interfaces can't be used together. why not having a ugen(4) for every USB device? even it is supported? it probably won't harm anyone, but will make possible accessing parts of the device that are otherwise hidden. 11 interface descriptors sounds unlikely to be correct - it's more likely that some of them are alternative configurations and a device or interface can only be in a single configuration at a given time. You can switch between alternative configurations via ugen. It seems that this is the way that the CDC WMC (wireless mobile communication) devices are made. At least that is what i understand when reading some of the specifications published at usb.org I don't know about OBEX, but why don't you just create an interface class driver that attaches to OBEX interfaces - writing USB drivers is not very difficult if you know USB and a few kernel basics. I've done some testing in this area and i've made a driver based on ucom/umodem that attaches to OBEX devices. (only attaches at the moment). And here i discovered that usbdevs can't show more than 4 interfaces on USB device. I tracked down this to USB_MAX_DEVNAMES=4. Is there a reason for this to be set this low? P.S.: anyone know some good way to list the attached usb devices beyond usbdevs? It seems that the information that can be gathered from usbdevs is very limited. For example 'lsusb' in linux can show much more info. What do you think about that too? I like usbctl from NetBSDs usbutils. An older port draft is available under: http://www.cosmo-project.de/~bernd/usbutil.tgz It will also show you the interface configurations with all alternatives. usbctl and friends are nice! :) i would love to see them in freebsd by default :) P.S.:yesterday i have managed to panic my 6.0-current kernel with usbctl, but i'm not sure if this is related to changes that i have done. i will cvsup to clean any problems in my source/rebuild and then report if there are problems. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] thanks! --niki pgpxGEIXLkMwb.pgp Description: PGP signature
Re: attaching ugen(4) on multi interface USB devices
On Thu, Oct 07, 2004 at 04:22:12PM +0300, Niki Denev wrote: Bernd Walter writes: On Wed, Oct 06, 2004 at 03:30:05PM +0300, Niki Denev wrote: If you already an interface driver atatched then ugen fails to attach the whole device. well, i think that this can be a problem sometimes. Yes - this is very often a problem :( actually i don't need kernel driver for obex devices, because everyting can and will be probably better done in the userland via ugen. but this means that the phone modem and obex interfaces can't be used together. Exactly that's the reason why you want a obex kernel driver. That doesn't mean it has to provide more functionality then ugen and you can still do the processing in userland. why not having a ugen(4) for every USB device? even it is supported? it probably won't harm anyone, but will make possible accessing parts of the device that are otherwise hidden. It can harm. Say you have other drivers attached and ugen switches the configuration of the device/interface that the other driver(s) uses. Many safety checks need to added to ugen for this. Copy the ugen driver to uobex, swtich it to be an interface level driver and strip the functionality down to what you really need. 11 interface descriptors sounds unlikely to be correct - it's more likely that some of them are alternative configurations and a device or interface can only be in a single configuration at a given time. You can switch between alternative configurations via ugen. It seems that this is the way that the CDC WMC (wireless mobile communication) devices are made. At least that is what i understand when reading some of the specifications published at usb.org Well - as I already wrote - I know almost nothing about this type of devices, but it still sound unlikely to be correct to what I know about USB - that doesn't mean it can't be correct. I don't know about OBEX, but why don't you just create an interface class driver that attaches to OBEX interfaces - writing USB drivers is not very difficult if you know USB and a few kernel basics. I've done some testing in this area and i've made a driver based on ucom/umodem that attaches to OBEX devices. (only attaches at the moment). And here i discovered that usbdevs can't show more than 4 interfaces on USB device. I tracked down this to USB_MAX_DEVNAMES=4. Is there a reason for this to be set this low? As I already wrote - 11 interfaces is very unusual and therfor you usually don't have that many drivers attached as well. Raise the limit if you need - or better make it a kernel tunable and document that your OBEX driver needs at least 11. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing from kernel
Søren Schmidt wrote: Roman Kurakin wrote: Hi, I have some problems with printing from kernel. At first I think that my problems was cause I use printf, but changed all of them to log cause it safe to use from interrupt handlers. The situation become better but I still observe system lockup in case I output some debug information from my driver. Yes its a known problem, if you output enough from the kernel the console will eventually lockup, its been so for ages, and I dont think anyone really have been looking into it. I didn't saw it before, only now after moving from Giant, but probably some system changes affect this. Hm. may be I need to try some old versions to check for this. I'll try to dig this. This was the only eye in kernel I use for ages. rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing from kernel
Don Lewis wrote: On 7 Oct, Roman Kurakin wrote: Hi, I have some problems with printing from kernel. At first I think that my problems was cause I use printf, but changed all of them to log cause it safe to use from interrupt handlers. The situation become better but I still observe system lockup in case I output some debug information from my driver. Also I have some problems with system console via com port. Instead of messages from kernel I see the first letter of the month name. This is a bug in syslogd related to non-blocking I/O that bde and I discussed quite a while back, though we never figured out a proper fix. I recently made the interesting discovery that the same problem isn't present on sparc64. I think it'll start working again if you restart syslogd. From my observation I didn't came to conclusion that this could be due to syslog, but I'll check this. Could anybody comment my observation? Does anybody saw anything like this? Oh, I forget to say I observe that with both Current and Releng5, SMP. Also I can't trigger NMI so I can't see the point of lockup. I generally use printf for this sort of thing, and I was going to suggest that you take a look at the KTR stuff, but that won't help if the machine totally locks up so that you can't get to the KTR buffer. I think you'll have trouble getting close to the bug if you use log because of the log latency from the generation of the message, passing it through syslogd, and back to the kernel to be printed. I'll try to think up how to see where I have my problems. If you plan to work on this problems we could join our efforts, rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing from kernel
Greg 'groggy' Lehey wrote: On Thursday, 7 October 2004 at 0:31:33 +0400, Roman Kurakin wrote: Hi, I have some problems with printing from kernel. At first I think that my problems was cause I use printf, but changed all of them to log cause it safe to use from interrupt handlers. The situation become better but I still observe system lockup in case I output some debug information from my driver. About the only thing I can think is that you're doing this in some area where it's unsafe to print, probably holding a lock that's needed in the print routines. I have the same idea but I cant't get which one. Also I have some problems with system console via com port. Instead of messages from kernel I see the first letter of the month name. Could anybody comment my observation? Without more detail, it's impossible to help. Does anybody saw anything like this? No. printf() is widely used in the kernel. I know. But it seems that log is more safer ... Oh, I forget to say I observe that with both Current and Releng5, SMP. Also I can't trigger NMI so I can't see the point of lockup. Take a look at your code and check what locks you're holding. Also, if this is only for debugging, you should be using the kernel debugger. It is used not only for debugging by myself, part of this output is my eye on users side. But for now, most of output is locking debugging. rik Greg -- See complete headers for address and phone numbers. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
BTX scripting help
Hi Folks, I'm trying to automate a sequence of BTX commands and I'm hitting some snags. I've got some minor forth experience, but it isn't enough. My machine uses the standard bootloader and doesn't present a menu for the user. By default, the machine boots a standard kernel and fs-image file and everything is happy. Sometimes, though, I want my users to be able to boot an alternate kernel and fs-image. To do this, what they do now is: - wait for the default kernel to start loading - hit the space bar - BTX breaks out and gives them a prompt - they type four commands: - unload - load /kernel - load -t md_image /altfs-image - boot I'd like to replace those four commands with one command to make things nicer for them. So I tried to define the obvious forth word: : altboot unload load /kernel load -t md_image /altfs-image boot ; which fails to compile because /kernel isn't a word. These all compile, but reboot when invoked : altboot unload s /kernel load ; \ reboots the box : altboot unload load s /kernel ; \ reboots the box : altboot unload . /kernel load ; \ reboots the box : altboot unload load . /kernel ; \ reboots the box I'm stumped. Any suggestions? Kelly ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BTX scripting help
On Thu, Oct 07, 2004 at 11:00:06AM -0700, Kelly Hall wrote: Hi Folks, I'm trying to automate a sequence of BTX commands and I'm hitting some snags. I've got some minor forth experience, but it isn't enough. My machine uses the standard bootloader and doesn't present a menu for the user. By default, the machine boots a standard kernel and fs-image file and everything is happy. Sometimes, though, I want my users to be able to boot an alternate kernel and fs-image. To do this, what they do now is: - wait for the default kernel to start loading - hit the space bar - BTX breaks out and gives them a prompt - they type four commands: - unload - load /kernel - load -t md_image /altfs-image - boot I'd like to replace those four commands with one command to make things nicer for them. So I tried to define the obvious forth word: : altboot unload load /kernel load -t md_image /altfs-image boot ; which fails to compile because /kernel isn't a word. These all compile, but reboot when invoked : altboot unload s /kernel load ; \ reboots the box : altboot unload load s /kernel ; \ reboots the box : altboot unload . /kernel load ; \ reboots the box : altboot unload load . /kernel ; \ reboots the box I'm stumped. Any suggestions? Read the loader(8) manpage, it says: BUILTIN COMMANDS Loader's builtin commands take its parameters from the command line. Presently, the only way to call them from a script is by using evaluate on a string. : OK : altboot : s unload evaluate : s load /boot/kernel/kernel evaluate : s lsmod evaluate : ; : OK altboot : /boot/kernel/kernel data=0x5ce910+0x488e0 syms=[0x8+0x69798+0x8+0x56466] : 0xfc30: /boot/kernel/kernel (elf kernel, 0x6d6e00) : modules: splash.1 nfsserver.1 nfs4.1 nfs.1 if_gif.1 if_faith.1 ether.1 sysvshm.1 sysvsem.1 sysvmsg.1 cd9660.1 isa.1 pseudofs.1 procfs.1 msdosfs.1 usb.1 random.1 ppbus.1 pci.1 null.1 mpt.1 miibus.1 mem.1 ispfw.0 isp.1 sbp.1 fwe.1 firewire.1 ahc.1 ahc_pci.1 ahc_isa.1 ahc_eisa.1 cam.1 Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpTs6CKWCUlb.pgp Description: PGP signature
bay area hacker needed
Hello list, I have tried and done everything to have this remote debugging working, with no success. Any BSD hacker in the bay area that know how to do this, shoot me an email. I will come meet you with a monetary donation if you can make this work. Thank you, Jerry. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hacking SCO....
Well, I eventually got this SCO system working. But today, some errors appeared: 505k:unrecover error reading SCSI disk on 0 Dev 1/42 cha = 0 id = 0 1 on = 0 Block 6578 medium error unrecovered read error HTFS i/o failure occurred while trying to upgrade 1 node 26302 on HTFS. Dev hd 1/42 Error log over flow block 6578 medium error unrecovered read error . Do these sound likes hardware errors for the drive or the adaptec card itself? The drive is brand new (well, its actually a replacement from acer with a date code on it from 1998 so it has been sitting in a box for awhile). However, the card is very old too. Any ideas? -john On Sep 27, 2004, at 7:24 PM, Julian H. Stacey wrote: John Von Essen wrote: Unfortunately, I have inherited a Intel P200 with SCO OpenServer 5.0.4 with a 4Gb SCSI drive. Condolences ! SCO is Horrible to work on, a waste of time, erase ASAP ! SCO is of no help, they cant provide replacement boot floppy, only sell me complete distribution version 5.0.7 for $100. Any ideas on how I should go about this. All I need to do is get that data from the tape onto the disk and I should good to go. SCO is of no help, they cant provide replacement boot floppy, only sell me complete distribution version 5.0.7 for $100. SCO used to give away licences free for 5.0.4 /or 5.0.5 for restricted use. One could legally download cdrom images burn them. Good denough to rescue data then erase SCO install BSD If you can't rescue the data while running FreeBSD, either: Non Commercial solution: Look around find someone near who has a 5.0.4 or 5 cdrom, (maybe even SCO site somewhere) get a copy, (cdrom contains floppy images too I recall), rescue data, delete SCO very quickly from your machine, (before you discover the pain of running SCO, ( if you really must run SCO then Do get their Skunkware CDROM too (yes that's it's real name! it's full of FSF/GNU stuff free makes using SCO rather less unpleasant (not unpleasant, just rather less). Commercial solution. Pay the $100, if its for a commercial job it's cheap. No point quibbling. SCO used to cost about 2000 German Deutschmarks, for end users, ( was the Unix I found most crippled. BSD is cheaper, but if it's for business, it's their legal right, cheap enough. There's SCO forums somewhere, but probably the wrong route. Their manuals used to just present work-rounds for obsolete old software everyone else wasn't using anymore eg at one stage they were SVR3 all other vendors were SVR4 based. Last time I was contracted to work on SCO, I just kept tossing more modern source eg X11R6 lesstif GNU src/ on top of the base obsolete SCO, till obsolete SCO libraries no longer broke my project. Reading SCO manuals was a waste of time, better to just to rip it out replace it with better software, either per utility that annoys, or per whole OS. - Julian Stacey. Unix,C,Net Sys. Eng. Consultant, Munich. http://berklix.com Mail in Ascii, Html dumped as Spam. Ihr Rauch = mein allergischer Kopfschmerz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hacking SCO....
Well, I eventually got this SCO system working. But today, some errors appeared: 505k:unrecover error reading SCSI disk on 0 Dev 1/42 cha = 0 id = 0 1 on = 0 Block 6578 medium error unrecovered read error HTFS i/o failure occurred while trying to upgrade 1 node 26302 on HTFS. Dev hd 1/42 Error log over flow block 6578 medium error unrecovered read error . Do these sound likes hardware errors for the drive or the adaptec card itself? The drive is brand new (well, its actually a replacement from acer with a date code on it from 1998 so it has been sitting in a box for awhile). However, the card is very old too. Any ideas? -john medium error unrecorvered read error really sounds like a phsycial medium (drive) error. If the controller was flaky, you'd get bus retries and stuff. -- Matt Emmerton ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hacking SCO....
On Thu, 7 Oct 2004, John Von Essen wrote: Well, I eventually got this SCO system working. But today, some errors appeared: 505k:unrecover error reading SCSI disk on 0 Dev 1/42 cha = 0 id = 0 1 on = 0 Block 6578 medium error unrecovered read error HTFS i/o failure occurred while trying to upgrade 1 node 26302 on HTFS. Dev hd 1/42 Error log over flow block 6578 medium error unrecovered read error . Do these sound likes hardware errors for the drive or the adaptec card Drive errors. Did you do a new low-level format before you put it in service? sformat is your friend. I do the full 14 pattern tests before I put a SCSI disk in service. Later.. Doug ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
