rune questions
hi, I am working on additional documentation for locale part of the libc and have some questions. FreeBSD locale is based on rune-type files. By mklocle(1) descriptions all characters are dividing into few categories: . ALPHA - letters . CONTROL - control symbos . DIGIT - digits et cetera. But I don't see anywhere descirptions on PHONOGRAM and IDEOGRAM. Manpages shown that these categories were used by Japan locale only (again without any descriptions :-( ) Anybody can give me answer about that these categories means ? Or url/reference at least. -- /* Alexey Zelkin && [EMAIL PROTECTED]*/ /* Tavric National University && [EMAIL PROTECTED] */ /* http://www.ccssu.crimea.ua/~phantom && [EMAIL PROTECTED] */ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Implementing ioctl to set MAC address -- question.
I don't have the answer to this question, but I would be most interested in hearing how this project goes as I was thinking of doing the same thing. Steve >I'm trying to implement Bill Paul's "setmac" code in the > actual source code as a project (and will have it reviewed > before it's committed -- if I ever get that far!). However, I'm > getting stuck in that ether_ioctl is never getting the ioctl > request. I've added the case statement for "SIOCSIFMAC" > (probably to be renamed) to net/if.c and dev/ed/if_ed.c > (which is the card I'm using) as well as net/if_ethersubr.c. Are > there any other files that need to know about the ioctl or am I > going about this the wrong way entirely? > > -- > |Chris Costello <[EMAIL PROTECTED]> > |This BBS is ancient. Some say from the echocene. > `- > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: rune questions
Alexey Zelkin wrote: > > But I don't see anywhere descirptions on PHONOGRAM and IDEOGRAM. Manpages > shown that these categories were used by Japan locale only (again without any > descriptions :-( ) On a guess, it might distinguish between hiragana/katakana and kanji. The former are a syllabic "alphabets", while the later have "meaning" attached. Written japanese use all three. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "People call him Neutron Star, 'cuz he's so dense lights bends around him." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: journaling UFS and LFS
> There is a difference between a log-structured filesystem and a > journaling filesystem... And? > *Very* different from LFS. (What are features? "Has files and > directories"? Time-complexity? Implementation details? Buzzwords?) You know. Features. As in those things that people would like to see in such a file system. The features we would like to see have already been listed. Please see the archives if you want to know what was considered a "feature". Besides, VxFS has a closer feature set to what I would like to see. > This seems a bit hard to believe (must check freebsd-fs to see if > people are actually *seriously* considering LFS as a starting > point...). Some people would prefer to start from scratch. Others have suggested LFS as a starting point. Still others no longer care. -don <--- no longer cares Please stop copying me on these messages. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: rune questions
In message <[EMAIL PROTECTED]> Alexey Zelkin writes: : But I don't see anywhere descirptions on PHONOGRAM and IDEOGRAM. Manpages : shown that these categories were used by Japan locale only (again without any : descriptions :-( ) A PHONOGRAM is a symbol that stands for more than one sound without meaning. In Japanese the phonograms are the hiragana and katakana, which are used to spell out some words and endings phonetically. An IDEOGRAM conveys both the sound and the meaning of the word, or word fragment, which is called kanji. The Japanese language is nihongo (this is a romanization of the word, and variants may exist). Spelled out in hiragana, it looks like $B$K$[(B $B$s$4(B, but you are more likely to see its kanji of $B!VF|K\8l!W(B. I said word fragments above because the English language is eigo or $B!V1Q8l!W(B. Notice the common suffix -go, represented in hiragana as $B!V$4!W(B and as kanji$B!V8l!W(B. I'm sorry that I don't have a URL to support the above. It is a simplification of what is going on. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CCD questions
On Sun, 31 Oct 1999, Andre Albsmeier wrote: > > ccdconfig manufactures a disklabel when you create the stripe, so you > > don't need to adjust the disklabel. The subdisks must have disklabels, > > and you can't use the C partition since ccd only uses partitions of type > > 4.2BSD. > > Does that mean I should not use partition c as a 4.2BSD type? This is what > I am currently doing on all disks (ccd'ed or single) if the whole disk is > used as one big filesystem, e.g.: > #size offsetfstype [fsize bsize bps/cpg] > c: 4532264404.2BSD 1024 819216 # (Cyl.0 - 2810*) I've been admonished for using the c partition as a filesystem since it's somewhat magic. For regular disks the running recommendation is to make another partition (a or g or whatever) that is identical to the c partition information, and to newfs/mount that. I personally haven't run into problems but I've been warned that the c partition interface is subject to change. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CCD questions
On Sunday, 31 October 1999 at 19:53:51 +0100, Andre Albsmeier wrote: > On Fri, 29-Oct-1999 at 08:56:01 -0700, Doug White wrote: >> On Thu, 28 Oct 1999, Stephen J. Roznowski wrote: >> >>> I'm looking at the tutorial on building CCDs at >>> >>> http://www.freebsd.org/tutorials/formatting-media/x205.html >> >> I am the author of said document ;) >> >>> It seems that this page needs to be updated to include the FAQ >>> entry between the ccdconfig and newfs. [I don't remember the >>> error I had before I did the disklabel...] >>> >>> # ccdconfig ccd0 32 0 /dev/sd0c /dev/sd1c /dev/sd2c >>> > # disklabel ccd0 > /tmp/ccd.label > # disklabel -Rr ccd0 /tmp/ccd.label >>> >>> # newfs /dev/rccd0c >>> >>> Is this really the case? [If so, I'll send-pr a correction] >> >> ccdconfig manufactures a disklabel when you create the stripe, so you >> don't need to adjust the disklabel. The subdisks must have disklabels, >> and you can't use the C partition since ccd only uses partitions of type >> 4.2BSD. > > Does that mean I should not use partition c as a 4.2BSD type? Yes. > This is what I am currently doing on all disks (ccd'ed or single) if > the whole disk is used as one big filesystem, e.g.: > 3 partitions: > #size offsetfstype [fsize bsize bps/cpg] > c: 4532264404.2BSD 1024 819216 # (Cyl.0 - 2810*) > > > I didn't have any problems for the last 3 years but if someone tells me that this > is bad, danegerous or simply ugly, I will change that :-) It's bad, dangerous and ugly :-) Seriously, you can normally get by this way, but it's confusing things, and there's no guarantee that you won't run into trouble in the future. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CCD questions
On Saturday, 30 October 1999 at 6:14:32 +0200, [EMAIL PROTECTED] wrote: >> Because Vinum is being maintained, and because Vinum will allow you to >> stripe your disks instead of simple concatenate them, which will probably >> result in better I/O rates. > > Some simple measurements shows ccd to be slightly faster when striping > 11 disks, then running 130 threads reading 1MB blocks from random > sector-aligned positions in a 10 GB file. > > with Vinum: 70 MB/s(2 of the 11 subdisks shown in iostat output) > > > tty da5 da6 cpu > tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id >0 94 171.82 36 5.96 174.53 38 6.48 0 0 16 3 80 >0 35 173.90 36 6.13 174.79 36 6.10 0 0 9 3 88 >1 47 175.33 35 6.01 173.96 38 6.44 0 0 9 3 88 >1 378 175.69 38 6.53 170.85 38 6.28 0 0 9 3 88 >1 37 176.47 37 6.42 173.21 35 5.87 0 0 9 3 88 >0 36 176.05 39 6.72 172.27 35 5.87 0 0 9 3 87 >0 36 168.95 40 6.60 172.89 36 6.14 0 0 9 4 87 >0 36 169.44 39 6.42 171.73 38 6.30 0 0 8 4 88 >0 36 172.64 37 6.24 174.79 38 6.44 0 0 9 3 88 > > With ccd: 80 MB/s > > ttyccd1 cpu > tin tout KB/t tps MB/s us ni sy in id >0 39 204.46 408 81.56 0 0 5 1 94 >0 39 205.28 413 82.75 0 0 5 1 94 >0 39 204.91 438 87.72 0 0 7 1 92 >0 39 204.96 429 85.96 0 0 6 1 93 >0 39 205.13 439 87.85 0 0 6 1 93 >0 39 204.80 448 89.61 0 0 5 1 94 >0 39 204.77 428 85.66 0 0 5 1 94 >0 39 204.66 440 87.95 0 0 6 1 93 >0 39 205.58 421 84.61 0 0 5 1 94 What program did you use to get this information? I'm surprised by the size of the transfers, which is larger than MAXPHYS (128 kB, the largest physical transfer allowed). There's also a discrepancy between the transfer size for Vinum and ccd which almost exactly corresponds to the measured performance. It would be interesting to see the output of rawio (in the Ports Collection) on these two volumes. > ccd is also capable of striping disks with different sizes. Correct. That's one aspect I didn't consider worth doing in Vinum. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CCD questions
On Mon, 01-Nov-1999 at 08:36:35 -0800, Doug White wrote: > On Sun, 31 Oct 1999, Andre Albsmeier wrote: > > > > ccdconfig manufactures a disklabel when you create the stripe, so you > > > don't need to adjust the disklabel. The subdisks must have disklabels, > > > and you can't use the C partition since ccd only uses partitions of type > > > 4.2BSD. > > > > Does that mean I should not use partition c as a 4.2BSD type? This is what > > I am currently doing on all disks (ccd'ed or single) if the whole disk is > > used as one big filesystem, e.g.: > > > #size offsetfstype [fsize bsize bps/cpg] > > c: 4532264404.2BSD 1024 819216 # (Cyl.0 - 2810*) > > I've been admonished for using the c partition as a filesystem since it's > somewhat magic. For regular disks the running recommendation is to make > another partition (a or g or whatever) that is identical to the c > partition information, and to newfs/mount that. I personally haven't run > into problems but I've been warned that the c partition interface is > subject to change. OK, I see. So I am going to use the a partition in future and leave c unused. Thanks, -Andre To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CCD questions
On Mon, 01-Nov-1999 at 10:42:21 -0500, Greg Lehey wrote: > On Sunday, 31 October 1999 at 19:53:51 +0100, Andre Albsmeier wrote: > > On Fri, 29-Oct-1999 at 08:56:01 -0700, Doug White wrote: > >> On Thu, 28 Oct 1999, Stephen J. Roznowski wrote: > >> > >>> I'm looking at the tutorial on building CCDs at > >>> > >>> http://www.freebsd.org/tutorials/formatting-media/x205.html > >> > >> I am the author of said document ;) > >> > >>> It seems that this page needs to be updated to include the FAQ > >>> entry between the ccdconfig and newfs. [I don't remember the > >>> error I had before I did the disklabel...] > >>> > >>> # ccdconfig ccd0 32 0 /dev/sd0c /dev/sd1c /dev/sd2c > >>> > > # disklabel ccd0 > /tmp/ccd.label > > # disklabel -Rr ccd0 /tmp/ccd.label > >>> > >>> # newfs /dev/rccd0c > >>> > >>> Is this really the case? [If so, I'll send-pr a correction] > >> > >> ccdconfig manufactures a disklabel when you create the stripe, so you > >> don't need to adjust the disklabel. The subdisks must have disklabels, > >> and you can't use the C partition since ccd only uses partitions of type > >> 4.2BSD. > > > > Does that mean I should not use partition c as a 4.2BSD type? > > Yes. > > > This is what I am currently doing on all disks (ccd'ed or single) if > > the whole disk is used as one big filesystem, e.g.: > > > 3 partitions: > > #size offsetfstype [fsize bsize bps/cpg] > > c: 4532264404.2BSD 1024 819216 # (Cyl.0 - 2810*) > > > > > > I didn't have any problems for the last 3 years but if someone tells me that this > > is bad, danegerous or simply ugly, I will change that :-) > > It's bad, dangerous and ugly :-) OK, the author of vinum will know that :-) As I just said in another mail, I will use the a partition in future and leave c untouched... > > Seriously, you can normally get by this way, but it's confusing > things, and there's no guarantee that you won't run into trouble in > the future. Thanks, -Andre To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Search a symbol in the source tree
In message <[EMAIL PROTECTED]> Jacques Vidrine writes:
: > $find . -name "*.c" -print -exec "egrep" "-i" "idt" {} \; | less
: > Here , "idt" is a search string.
:
: That's because no one wants a separate invocation of egrep for
: every file!
find . -name \*.c | xargs egrep -i idt | less
is shorter to type and will generally fork only a couple of times for
the entire source tree.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
RE: BSD XFS Port & BSD VFS Rewrite
I spent an hour on the phone with SGI's lead FS scientist Dan Koren discussing the XFS situation, Margot Seltzer's LFS work, ships, sails, sealing wax... The code is not yet open. It is being "disencumbered" and retrofitted to the Linux kernel interfaces by a team of contractors and university people all under NDA. So we're on hold for the time being. Unless you want to sign an NDA and move to Iowa for a year or so. We BSDies really are going to have to come up with something in the way of a modern storage subsystem. > -Original Message- > From: Andrzej Bialecki [SMTP:[EMAIL PROTECTED]] > Sent: Saturday, October 30, 1999 10:56 AM > To: Alton, Matthew > Subject: Re: BSD XFS Port & BSD VFS Rewrite > > On Thu, 5 Aug 1999, Alton, Matthew wrote: > > > I am currently conducting a thorough study of the VFS subsystem > > in preparation for an all-out effort to port SGI's XFS filesystem to > > FreeBSD 4.x at such time as SGI gives up the code. Matt Dillon > > Is there anything that you might say on the progress status of this > project? Thanks! > > Andrzej Bialecki > > // <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com) > // --- > // -- FreeBSD: The Power to Serve. http://www.freebsd.org > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Problem: 3.3-STABLE floppies: ep0/zp0, laptop falls off net
In message <[EMAIL PROTECTED]> Chris Shenton writes: : Unfortunately, it thinks my 3com 3c589 PCMCIA card is an ep0 -- it : has no driver for the correct zp0 device. It is correct. That is the right device to use. zp0 is a kludge that will die in 4.0 if I have my way. : It is able to get its DHCP address and was briefly able to start : FTP retrieval from ftp.freebsd.org, but speed was about 1KB/second : on a 1.5Mbps DSL line. Subsequent attempts caused it to fail even : resolving other ftp*.freebsd.org names despite the fact that its : nameserver is on the same LAN. This is the classic "I didn't assign the right IRQ to the pccard" problem. : I'd imagine the 3c589 is a fairly popular card and if ep0 can't : drive it, then zp0 should certainly be included in the pccard : floppy distro. No. pccard floppy is doing the right thing. It is well known that the ep driver can drive the 3c589, since 1 of people are using it to do just that as well as myself :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Ethernet TAP device driver released
Hello All, It is time for new release :) The beta version of Ethernet TAP device driver for FreeBSD is released. I've written this device driver for VTUN (http://vtun.netpedia.net) software package. It is possible the coolest software to make tunnels over TCP/IP networks. For more details please see author's page. The TAP device driver is like TUN device driver, but it works with Ethernet packets. It allows to capture Ethernet packets and feed them to user space and vice versa. The driver can be found at http://vtun.netpedia.net/tun/tap-0.1-freebsd.tar.gz. I've tested it with VTUN on my FreeBSD 3.2-RELEASE. It seems to me it works just fine. I'd like to ask to help me in testing and give some feed back. Thank you very much, Best regards, eMax. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Ethernet TAP device driver released
> The beta version of Ethernet TAP device driver for FreeBSD is released. This looks like BPF, only much less smart. Why reinvent the wheel? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CCD questions
On Monday, 1 November 1999 at 17:49:29 +0100, Andre Albsmeier wrote: > On Mon, 01-Nov-1999 at 08:36:35 -0800, Doug White wrote: >> On Sun, 31 Oct 1999, Andre Albsmeier wrote: >> ccdconfig manufactures a disklabel when you create the stripe, so you don't need to adjust the disklabel. The subdisks must have disklabels, and you can't use the C partition since ccd only uses partitions of type 4.2BSD. >>> >>> Does that mean I should not use partition c as a 4.2BSD type? This is what >>> I am currently doing on all disks (ccd'ed or single) if the whole disk is >>> used as one big filesystem, e.g.: >> >>> #size offsetfstype [fsize bsize bps/cpg] >>> c: 4532264404.2BSD 1024 819216 # (Cyl.0 - 2810*) >> >> I've been admonished for using the c partition as a filesystem since it's >> somewhat magic. For regular disks the running recommendation is to make >> another partition (a or g or whatever) that is identical to the c >> partition information, and to newfs/mount that. I personally haven't run >> into problems but I've been warned that the c partition interface is >> subject to change. > > OK, I see. So I am going to use the a partition in future and leave > c unused. BTW, it's pretty trivial to change things. Run 'disklabel -e da0' (or whatever your drive is), duplicate the line and change to, say: c: 453226440unused 1024 819216 # (Cyl.0 - 2810*) e: 4532264404.2BSD 1024 819216 # (Cyl.0 - 2810*) Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CCD questions
:BTW, it's pretty trivial to change things. Run 'disklabel -e da0' (or :whatever your drive is), duplicate the line and change to, say: : : c: 453226440unused 1024 819216 # (Cyl.0 - 2810*) : e: 4532264404.2BSD 1024 819216 # (Cyl.0 - 2810*) : :Greg :-- CCD doesn't protect its own label area. It is safest to make your 'e' partition start at sector 16 and be 16 sectors smaller. e: 45322628 164.2BSD 1024 819216 # (Cyl.0 - 2810*) -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CCD questions
On Mon, 01-Nov-1999 at 10:15:01 -0800, Matthew Dillon wrote: > > :BTW, it's pretty trivial to change things. Run 'disklabel -e da0' (or > :whatever your drive is), duplicate the line and change to, say: > : > : c: 453226440unused 1024 819216 # (Cyl.0 - 2810*) > : e: 4532264404.2BSD 1024 819216 # (Cyl.0 - 2810*) > : > :Greg > :-- > > CCD doesn't protect its own label area. It is safest to make your 'e' > partition start at sector 16 and be 16 sectors smaller. > > e: 45322628 164.2BSD 1024 819216 # (Cyl.0 - 2810*) Ah, that's new to me. Thanks for the info. But anyway, I will switch to vinum as soon as I get a free saturday to copy all the GB's around :-) Thanks, -Andre > > > -Matt > Matthew Dillon > <[EMAIL PROTECTED]> -- "Amateurs like Linux, but professionals prefer FreeBSD." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Ethernet TAP device driver released
Hello Mike, It seems to me bfp can bind to EXISTING interface. I.e. you have to have phisical interface. (if I wrong, correct me :) This driver will create a VIRTUAL Ethernet interface "tapX" with random MAC address etc. You can attach bpf to this interface. In other words you can connect computer to Ethernet network without having Ethernet card. All you need is just ANY type of connection. I was using ppp to connect to remote server with VTUN and DID HAVE ETHERNET network. BTW, what the difference between TUN and BPF :-) Regards, eMax. > -Original Message- > From: Mike Smith [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 01, 1999 12:54 PM > To: Yevmenkin, Maksim N, CSCIO > Cc: [EMAIL PROTECTED] > Subject: Re: Ethernet TAP device driver released > > > > The beta version of Ethernet TAP device driver for FreeBSD > is released. > > This looks like BPF, only much less smart. Why reinvent the wheel? > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ > [EMAIL PROTECTED] > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
IDA driver issues upon installation. Probing devices hangs
I am trying to install the stable snapshot from 10301999 on a compaq proliant 4500 with a smart array controller. I recompile the installation kernel and dropped it on the disk. The newly compile kernel has the ida driver included (as the drives are on that controller). It finds the controller and the logical drives, but when the installation program starts, it hangs at Probing for devices. The ida driver also reports "irq with no handler" when the kernel finds the device (prior to the probing screen). I've tried moving irq's around and removing some other cards but nothing. If I boot without the ida driver, it works ifne except that I don't have any drives to install on. If you need any more information please let me know. Thanks! Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
docs/14112: replacement for diediedie() in docs
-hackers, Could someone take a look at docs/14112 please. The online kernel debugging section in the Handbook mentions calling diediedie() or boot() to reboot the system. According to the PR, these don't exist in 3.3-R, and I don't know what calls / actions should replace the existing text. Any help appreciated. Thanks, N -- A different "distribution" of Linux is really a different operating system. They just refuse to call it that because it's bad press. But that's what the shoe fits. -- Tom Christiansen, <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Ethernet TAP device driver released
On Mon, 1 Nov 1999, Mike Smith wrote: > > The beta version of Ethernet TAP device driver for FreeBSD is released. > > This looks like BPF, only much less smart. Why reinvent the wheel? May-be for the same reason the horse-power has been invented. ;-) Gérard. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NASM programs for freebsd
Ok, if i happen to remember correctly, assembly isn't so easy under freebsd or linux as it is under dos, mainly because we aren't in real time anymore..and the kernel prevents you from accessing the hardware so easily via assembly. You might wish to try using system calls.. example below.. section .text bits32 extern printf global main msg db 'Hello, World!',10,0 main: push dword msg call printf add esp,4 retn Hope this helps in any way possible.. :) -- Jonathan Towne [EMAIL PROTECTED][EMAIL PROTECTED] Systems Administratorhttp://massive.geek.edu/ -BEGIN GEEK CODE BLOCK- Version: 3.1 GU d- s: a--- C+++ UB P L- E--- W--- N++ o K w--- O-- M V- PS PE Y-- PGP- t+ 5 X+ R+ tv- b+ DI+ D++ G e- h-- r-- y --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: VTun...
Hi, [...] > I notice that you support traffic shaping. I was wondering > if you plan to > offer support for slower than 8KBytes / sec (64Kbits/s). Everything should be there ;) > What I'd like to be able to do, is create some tunnels to my > end points, > and then using the firewall / routing software, do policy > routing. (ie: > telnet goes over this tunnel, and is traffic shaped to > 1KByte/s, while web > traffic goes over another tunnel, and is allocated the > remainder of the > available bandwidth.) In this way, I'd be able to guarantee > a certain > amount of BW to core services such as telnet, without letting > things like > SMTP or web impact on services... Yes, you can do it. I think Max is going to release new version of VTUN very soon. Best regards, eMax. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Vinum or CCD? (was: CCD questions)
On Friday, 29 October 1999 at 12:05:30 -0600, Wes Peters wrote: > "Stephen J. Roznowski" wrote: >> >> On 28 Oct, Wes Peters wrote: >>> "Stephen J. Roznowski" wrote: I'm looking at the tutorial on building CCDs at >>> >>> Why? Do you have a compelling reason not to use Vinum volume manager? >> >> No, but why should I use Vinum over CCD? (All I want to do is create >> some larger disks). > > Because Vinum is being maintained, and because Vinum will allow you to > stripe your disks instead of simple concatenate them, which will probably > result in better I/O rates. In fact, CCD will stripe for you as well. In such configurations, there isn't much difference between CCD and Vinum performance. That changes a lot when you get to mirroring. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: gdb and kld symbols -- how to (and handbook is outdated)
On Friday, 29 October 1999 at 9:05:15 -0400, Robert Watson wrote:
>
> I've mostly debugged kernel modules running as lkm's, but decided to start
> up my debugger on code in a kld a couple of days, and needless to say the
> procedure is different :-). And unfortunately, also not documented in the
> handbook online, which still talks about lkms. Any suggestions? It is
> presumably still add-symbol-file, but with a different offset?
>
> Also, it might be desirable to either extend the handbook to also talk
> about klds, or to replace it with a kld page.
This questions qualifies as "in-depth technical", so I'm moving it to
-hackers. If you're not signed up there, you should be. I'm also
copying -committers because it's probably of interest there.
The object you need is in /modules. For example, to debug the Linux
kld, you need to load the symbols from /modules/linux.ko. That's the
easy part.
The difficult part is to find the base address. I have this in
/usr/src/sys/modules/vinum/.gdbinit.vinum.paths:
define asf
set $file = linker_files.tqh_first
set $found = 0
while ($found == 0)
if (*$file->filename == 'v')
set $found = 1
else
set $file = $file->link.tqe_next
end
end
shell /usr/bin/objdump --section-headers /modules/vinum.ko | grep ' .text' | awk
'{print "add-symbol-file /modules/vinum.ko \$file->address+0x" $4}' > .asf
source .asf
end
This goes through an internal kernel list and looks for a module name
which begins with 'v'; you'll need to change the first "if" statement
to something which uniquely matches your kld. The rest (modulo file
names, which I have omitted here) should stay the same. There's also
more information in vinum(4).
Greg
--
When replying to this message, please copy the original recipients.
For more information, see http://www.lemis.com/questions.html
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Vinum (was: CCD questions)
On Friday, 29 October 1999 at 8:56:01 -0700, Doug White wrote: > On Thu, 28 Oct 1999, Stephen J. Roznowski wrote: > >> I'm looking at the tutorial on building CCDs at >> >> http://www.freebsd.org/tutorials/formatting-media/x205.html > > I am the author of said document ;) > >> It seems that this page needs to be updated to include the FAQ >> entry between the ccdconfig and newfs. [I don't remember the >> error I had before I did the disklabel...] >> >> # ccdconfig ccd0 32 0 /dev/sd0c /dev/sd1c /dev/sd2c >> # disklabel ccd0 > /tmp/ccd.label # disklabel -Rr ccd0 /tmp/ccd.label >> >> # newfs /dev/rccd0c >> >> Is this really the case? [If so, I'll send-pr a correction] > > ccdconfig manufactures a disklabel when you create the stripe, so you > don't need to adjust the disklabel. The subdisks must have disklabels, > and you can't use the C partition since ccd only uses partitions of type > 4.2BSD. > >> Also, "newfs -v /dev/ccd0c" yields >> >> newfs: /dev/rccd0c: `c' partition is unavailable >> >> but "newfs /dev/ccd0c" works. Why is this? > > ccds are goofy. They're not real devices. If the tutorial says to newfs > rccd then that is a problem. I think you've missed a different point here. /dev/rccd0c *should* be correct; in 4.0-RELEASE there will be no block devices, so if it doesn't we need to do something quickly. The point here is that Stepen used the -v option for newfs, which tells newfs to ignore partition information. This is needed for Vinum, and hasn't been used for anything else. Stephen, what does 'newfs /dev/rccd0c' do? >> Finally, the CCD homepage at http://stampede.cs.berkeley.edu/ccd/ >> seems unavailable. Is this temporary or permanent? > > CCD is deprecated by vinum. I think that, as long as ccd is still available (and I don't see it going away soon), the docco should be available too. On Friday, 29 October 1999 at 22:28:00 +1000, Shaun Amy, CSIRO TIP/ATNF wrote: > In message <[EMAIL PROTECTED]> you write: >> On 28 Oct, Wes Peters wrote: >>> "Stephen J. Roznowski" wrote: I'm looking at the tutorial on building CCDs at >>> >>> Why? Do you have a compelling reason not to use Vinum volume manager? >> >> No, but why should I use Vinum over CCD? (All I want to do is create >> some larger disks). >> >> I just did a search on www.freebsd.org, and all I could find about Vinum >> seems to imply that the software isn't ready for prime time. Also, a >> quick scan of the vinum(4) man page doesn't lead to a lot of confidence >> since a large portion of the page is devoted to "DEBUGGING PROBLEMS WITH >> VINUM" including kernel panics You can get panics with ccd as well. Since Vinum is still being actively developed, there are parts which are not as stable as others. The CCD functionality has been stable for over 12 months. The known bugs files and DEBUGGING PROBLEMS section of vinum(4) are there to ensure that you don't have more problems than necessary. You shouldn't take them as an indication that you're going to have trouble. >> Is Vinum ready for prime time? > > Vinum is included in the 3.3-RELEASE which suggests there must be a very high > level of confidence in its stability and functionality. I would guess that > while Vinum is being actively maintained by Greg et al., ccd is showing its > age and is probably not being as actively maintained. Vinum has been around > for q good amount of time - I heard Greg talk about is in September 1998 at a > conference. > > For some fun, I recently (four weeks ago) decided to stripe and concatenate > a couple of filesystems across two 4GB SCSI disks. I was so confident I > moved my home directory off my older 2.2.8-STABLE box onto one of these vinum > devices and whilst one user probably doesn't hit things hard I have seen no > problems. > > Having had considerable experience with Sun's DiskSuite on Solaris boxes I > didn't have much of a problem in getting things going (it was even easier > than I thought). There is some excellent info on Greg's WWW site: > >http://www.lemis.com/vinum.html > > which may help you get going. Note that the RAID-5 functionality is now also > present. Note that RAID-5 functionality is one of the areas that I wouldn't recommend for prime time yet. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Ping - sized tests with 0% and 100% packet loss! Any ideas?
Hey guys, A wierd one. I'm trying to track down a packets size (I believe) problem on my network. During ping testing I've come across the following strange which I don't understand. Using various sized packets ($n) with: ping -f -c 300 -s $n localhost I'm getting results that I wouldn't expect: SizePacketLoss 1 14% 2-100% 11 100% 12 0% 13 100% 14 0% 15 100% etc. Anyone any idea what's going on? I've tcpdump/tcpshow'd the traffic and the packets are definitely going out, but no replies are coming back. For the size of 1 we only get 256 packets back and no more. I've scanned though the ping code, and everything's fine up to and including the return from 'sendto'. Does anyone know this part of the kernel? Joe -- Josef KarthauserFreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IDA driver issues upon installation. Probing devices hangs
None of the interested developers have access to one of these machines anymore; it's quite possible that things have been changed or broken to some degree of late. > I am trying to install the stable snapshot from 10301999 on a compaq > proliant 4500 with a smart array controller. I recompile the installation -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IDA driver issues upon installation. Probing devices hangs
> I've tried moving irq's around and removing some other cards but nothing. > If I boot without the ida driver, it works ifne except that I don't have > any drives to install on. Oops, I forgot to mention; you can't install onto an 'ida' drive; you need a system drive. You will want one anyway; swapping onto a RAID5 array is a pretty lame idea. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: semaphores/semget problem
Kent Boortz <[EMAIL PROTECTED]> wrote: > semget(IPC_PRIVATE, SEMMSL, IPC_EXCL | IPC_CREAT | 0600)) > > fails with the error "No space left on device". Since SEMMSL defaults to SEMMNS, this is guaranteed to fail if anything else is using semaphores. > I tried to > use a smaller value for SEMMSL but it did not help. I'm not sure what you mean by this. Did you re-define SEMMSL before your semget, or build a new kernel with a smaller SEMMSL? If you intend to make heavy use of semaphores, you might like to study PR kern/12014 as well. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IDA driver issues upon installation. Probing devices hangs
The array only contains two drives. Hmm.. the only other way is to use a drive on the embedded controller, which is a ncr (chipset 53C825) which isn't found by probing when the kernel loads. It's and embedded EISA compaq 32-bit Fast-Wide Scsi2-/e .. On Mon, 1 Nov 1999, Mike Smith wrote: > > I've tried moving irq's around and removing some other cards but nothing. > > If I boot without the ida driver, it works ifne except that I don't have > > any drives to install on. > > Oops, I forgot to mention; you can't install onto an 'ida' drive; you > need a system drive. You will want one anyway; swapping onto a RAID5 > array is a pretty lame idea. 8) > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Ping - sized tests with 0% and 100% packet loss! Any ideas?
At Tue, 2 Nov 1999 00:16:02 +, Josef Karthauser <[EMAIL PROTECTED]> wrote: >Anyone any idea what's going on? The problem doesn't exist in 2.2.5-RELEASE. I can't readily test anything other than that and -current at present. As far as I can determine, the problem with 1-byte packets is that the transmitted checksum is incorrect when the ICMP sequence number exceeds 255 - this suggests that the checksum missing the last byte of the sequence number. The problem is also on the transmit side. Studying the code in src/sys/netinet/ip_icmp.c:icmp_input() [which is reporting checksum errors] and icmp_send() [which inserts the checksum], it looks to me like the problem is: cvs diff: Diffing . Index: ip_icmp.c === RCS file: /home/CVSROOT/src/sys/netinet/ip_icmp.c,v retrieving revision 1.37 diff -u -r1.37 ip_icmp.c --- ip_icmp.c 1999/09/14 16:40:28 1.37 +++ ip_icmp.c 1999/11/02 01:45:34 @@ -685,7 +685,7 @@ m->m_len -= hlen; icp = mtod(m, struct icmp *); icp->icmp_cksum = 0; - icp->icmp_cksum = in_cksum(m, ip->ip_len - hlen); + icp->icmp_cksum = in_cksum(m, ip->ip_len); m->m_data -= hlen; m->m_len += hlen; m->m_pkthdr.rcvif = (struct ifnet *)0; though I can't confirm this immediately. (And I can't see why this would have worked at all). Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Secondary IDE cannot be detected
I am really sorry to post here a problem that's not related to hacking, but i have already sent many posts to [EMAIL PROTECTED] without a solution to my problem. I am trying to get my Secondary IDE detected, but FreeBSD DOES NOT detect it! This device is working well under another OS like Linux and Win98 (i have 3 OSes in my machine), so i believe there is no hardware problems. Any way here goes some important information about my system (only relevant part) Dmesg output: wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): < 34X CD-ROM/VER 1.D1>, removable, accel, dma, iordy acd0: drive speed 687 - 3781KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked wdc1 not found at 0x170 ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port Comment: It was no funny to see this on my screen, freebsd cannot even detect it, altough it's compiled into kernel, (wdc1 not found at 0x170). My kernel config file: (again, only relevant part) options "CMD640"# work around CMD640 chip deficiency controller wdc0at isa? port "IO_WD1" bio irq 14 diskwd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller wdc1at isa? port "IO_WD2" bio irq 15 #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC#Don't do it as an LKM device acd0#IDE CD-ROM device wfd0#IDE Floppy (e.g. LS-120) -- Message of the day: The trouble with doing something right the first time is that nobody appreciates how difficult it was. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Secondary IDE cannot be detected
On 02-Nov-99 Gustavo V G C Rios wrote: > I am trying to get my Secondary IDE detected, but FreeBSD DOES NOT > detect it! > This device is working well under another OS like Linux and Win98 (i > have 3 OSes in my machine), so i believe there is no hardware problems. Does it have a device on it? If not it won't show up. If it only has a slave on it, it won't be detected either - its supposed to have a master as well - or just a master (this might have changed recently though) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Secondary IDE cannot be detected
On 02-Nov-99 Gustavo V G C Rios wrote: > I am trying to get my Secondary IDE detected, but FreeBSD DOES NOT > detect it! > This device is working well under another OS like Linux and Win98 (i > have 3 OSes in my machine), so i believe there is no hardware problems. My fix to this, was to use the newer, experimental ATA drivers in -CURRENT by Soren Schmidt(spelling? sorry if i got it wrong), and the problem was solved on its own..though i should have read UPDATING, it'd have made my life a bit easier :P -- Jonathan Towne [EMAIL PROTECTED][EMAIL PROTECTED] Systems Administratorhttp://massive.geek.edu/ -BEGIN GEEK CODE BLOCK- Version: 3.1 GU d- s: a--- C+++ UB P L- E--- W--- N++ o K w--- O-- M V- PS PE Y-- PGP- t+ 5 X+ R+ tv- b+ DI+ D++ G e- h-- r-- y --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Ping - sized tests with 0% and 100% packet loss! Any ideas?
Josef Karthauser writes: > A wierd one. I'm trying to track down a packets size (I believe) problem > on my network. During ping testing I've come across the following strange > which I don't understand. > > Using various sized packets ($n) with: > ping -f -c 300 -s $n localhost > > I'm getting results that I wouldn't expect: > > SizePacketLoss > > 1 14% > 2-100% > 11 100% > 12 0% > 13 100% > 14 0% > 15 100% > etc. Happens to me to on -current, but not -stable. With -current's ping on stable it doesn't happen, and with -stable's ping on -current it still happens. Therefore it must be a kernel bug. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Ping - sized tests with 0% and 100% packet loss! Any ideas?
> Happens to me to on -current, but not -stable. With -current's > ping on stable it doesn't happen, and with -stable's ping on > -current it still happens. Therefore it must be a kernel bug. Can you recompile ping without -O (or -O0)? Tammy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Ping - sized tests with 0% and 100% packet loss! Any ideas?
> From: Peter Jeremy <[EMAIL PROTECTED]> > Date: 1999-11-01 17:49:29 -0800 > To: [EMAIL PROTECTED] > Subject: Re: Ping - sized tests with 0% and 100% packet loss! Any ideas? > Cc: [EMAIL PROTECTED] > X-Mailer: Mutt 1.0pre3i > Content-return: prohibited > Delivered-to: [EMAIL PROTECTED] > X-Loop: FreeBSD.ORG > > At Tue, 2 Nov 1999 00:16:02 +, Josef Karthauser <[EMAIL PROTECTED]> wrote: > >Anyone any idea what's going on? > > The problem doesn't exist in 2.2.5-RELEASE. I can't readily test > anything other than that and -current at present. FWIW, our kernel, based roughly on FreeBSD 3.2, has the same line as marked with "-", and I don't see the problem: # for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 > do > echo === $i === > ping -f -c 300 -s $i localhost > done| grep loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss 300 packets transmitted, 300 packets received, 0% packet loss Regards, Justin > As far as I can determine, the problem with 1-byte packets is that > the transmitted checksum is incorrect when the ICMP sequence number > exceeds 255 - this suggests that the checksum missing the last byte > of the sequence number. The problem is also on the transmit side. > > Studying the code in src/sys/netinet/ip_icmp.c:icmp_input() [which > is reporting checksum errors] and icmp_send() [which inserts the > checksum], it looks to me like the problem is: > > cvs diff: Diffing . > Index: ip_icmp.c > === > RCS file: /home/CVSROOT/src/sys/netinet/ip_icmp.c,v > retrieving revision 1.37 > diff -u -r1.37 ip_icmp.c > --- ip_icmp.c 1999/09/14 16:40:28 1.37 > +++ ip_icmp.c 1999/11/02 01:45:34 > @@ -685,7 +685,7 @@ > m->m_len -= hlen; > icp = mtod(m, struct icmp *); > icp->icmp_cksum = 0; > - icp->icmp_cksum = in_cksum(m, ip->ip_len - hlen); > + icp->icmp_cksum = in_cksum(m, ip->ip_len); > m->m_data -= hlen; > m->m_len += hlen; > m->m_pkthdr.rcvif = (struct ifnet *)0; > > though I can't confirm this immediately. (And I can't see why > this would have worked at all). > > Peter > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > > -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking| Men are from Earth. Apple Computer, Inc. | Women are from Earth. 2 Infinite Loop | Deal with it. Cupertino, CA 95014 | *-*---* To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Secondary IDE cannot be detected
On 02-Nov-99 Gustavo V G C Rios wrote: > I am really sorry to post here a problem that's not related to > hacking, > but i have already sent many posts to [EMAIL PROTECTED] without a > solution to my problem. > > I am trying to get my Secondary IDE detected, but FreeBSD DOES NOT > detect it! > This device is working well under another OS like Linux and Win98 (i > have 3 OSes in my machine), so i believe there is no hardware > problems. It doesn't detect it if you don't have anything plugged into it. Relax. Do you have a hard drive or CD-ROM plugged into the controller? --- John Baldwin <[EMAIL PROTECTED]> -- http://www.cslab.vt.edu/~jobaldwi/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Secondary IDE cannot be detected
Daniel O'Connor wrote: > > On 02-Nov-99 Gustavo V G C Rios wrote: > > I am trying to get my Secondary IDE detected, but FreeBSD DOES NOT > > detect it! > > This device is working well under another OS like Linux and Win98 (i > > have 3 OSes in my machine), so i believe there is no hardware problems. > > Does it have a device on it? If not it won't show up. > > If it only has a slave on it, it won't be detected either - its supposed to > have a master as well - or just a master (this might have changed recently > though) > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message I have a CDROM onto it! It's in the secondary slave, so i need to change it to the master. Thaaanks a lot for your time and cooperation! It's surprise that nobody at [EMAIL PROTECTED] knows about that! But nothing that [EMAIL PROTECTED] could not solve it, of course! Thank you guys! -- Message of the day: The trouble with doing something right the first time is that nobody appreciates how difficult it was. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Secondary IDE cannot be detected
Gustavo V G C Rios wrote: > I am trying to get my Secondary IDE detected, but FreeBSD DOES NOT > detect it! > > My kernel config file: (again, only relevant part) > > options "CMD640"# work around CMD640 chip deficiency > controller wdc0at isa? port "IO_WD1" bio irq 14 > diskwd0 at wdc0 drive 0 > #disk wd1 at wdc0 drive 1 > > controller wdc1at isa? port "IO_WD2" bio irq 15 > #disk wd2 at wdc1 drive 0 > #disk wd3 at wdc1 drive 1 Uncommenting wd2 and wd3 might help. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Netgear FA410 pccard ethernet?
Does anybody have a Netgear FA410 pccard ethernet adapter working with FreeBSD? I'm using version 3.2, installed from the distribution CD. -Guy Middleton To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD XFS Port & BSD VFS Rewrite
"Alton, Matthew" wrote: Hmm interesting... Guess I need to read the hackers list more often. So anybody interested in what is going on right now? Legal BS; The encumbrance work is progressing at an expected snails pace. The hardest question to answer at this point; What is encumbered and what isn't! It isn't even clear what constitutes encumbrance structures function names/api's. Short summary to all this nobody has any clear idea as to how long before the code can be released. I do have a bit of good news: if anybody is truly interested in helping out with the project they can sign an NDA through the company that sgi has contracted to work on the linux port. This is basically to protect SGI until the code has be officially clean and blessed. Contact me directly if you are interested [EMAIL PROTECTED] Where are we at with the linux port... Well we can mount file systems, df, ls, and read files (not a complete implementation) I am currently working on the write path, this one is much more complicated and will require addition work from other people to complete first. There are a lot and I mean a lot of issues involved with getting xfs to interface with the buffer/memory management system of an OS. IRIX pulls a lot of tricks with delayed allocation, holes, overlapping buffers, pining etc. etc. There is a lot of discussion amongst the linux people about how to proceed with upgrading linux's buffer/page code. I am currently trying to keep linux specific stuff out of the bowels of XFS. In fact one of our main goals is change a little XFS code as possible since all current improvements / bug fixes are being done on the IRIX code base. If people have ideas how how to keep this a "portable" file system let me know. It is easier for me to push things in certain directions now rather than later. > I spent an hour on the phone with SGI's lead FS scientist Dan Koren discussing > the XFS situation, Margot Seltzer's LFS work, ships, sails, sealing wax... The > code is not yet open. It is being "disencumbered" and retrofitted to the Linux > kernel interfaces by a team of contractors and university people all under NDA. > So we're on hold for the time being. Unless you want to sign an NDA and move to > Iowa for a year or so. > > > We BSDies really are going to have to come up with something in the way of a > modern storage subsystem. > > > -Original Message- > > From: Andrzej Bialecki [SMTP:[EMAIL PROTECTED]] > > Sent: Saturday, October 30, 1999 10:56 AM > > To: Alton, Matthew > > Subject: Re: BSD XFS Port & BSD VFS Rewrite > > > > On Thu, 5 Aug 1999, Alton, Matthew wrote: > > > > > I am currently conducting a thorough study of the VFS subsystem > > > in preparation for an all-out effort to port SGI's XFS filesystem to > > > FreeBSD 4.x at such time as SGI gives up the code. Matt Dillon > > > > Is there anything that you might say on the progress status of this > > project? Thanks! > > > > Andrzej Bialecki > > > > // <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com) > > // --- > > // -- FreeBSD: The Power to Serve. http://www.freebsd.org > > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Russell Cattelan [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
AMD PCnet-FAST+ ethernet chip.
Under 3.3R does anyone have this chip working? I get the following dmesg info: lnc1: rev 0x36 int a irq 10 on pci0.5.0 lnc1: PCnet-FAST+ address 00:d0:12:01:04:53 Interestingly no PHY information.. ifconfig says: # ifconfig lnc1 lnc1: flags=8843 mtu 1500 inet 207.76.205.82 netmask 0xff00 broadcast 207.76.205.255 ether 00:d0:12:01:04:53 however I get: # ping 207.76.205.22 PING 207.76.205.l22 (207.76.205.2n2): 56 data bytecs 1: Transmit underflow error -- Resetting lnc1: Transmit underflow error -- Resetting lnc1: Transmit underflow error -- Resetting lnc1: Transmit underflow error -- Resetting ^C --- 207.76.205.22 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss netstat -in shows: # netstat -in Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll lnc1 150000.d0.12.01.04.53 4809 0 17 4 0 lnc1 1500 207.76.205207.76.205.82 4809 0 17 4 0 The chip on the card is an AM79C972 and the PHY is (If the one with PHY written on it is the one), an Am79C873KC. The card has home-PNA on it as well so it's posible the PHY might belong to that. Looking at the AMD specs that must be the PHY. The "underflow" messages suggest a DMA/Data transfer problem, does anyone have any suggestions/experience? If I getthe time I'l hve a read of the driver too. julian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: RTLD_GLOBAL/RTLD_LOCAL dlopen mode flags
In article <[EMAIL PROTECTED]>, Max Khon <[EMAIL PROTECTED]> wrote: > Are there any plans to implement RTLD_GLOBAL/RTLD_LOCAL mode flags for > dlopen? RTLD_GLOBAL has been supported in -current since around the beginning of September. What is RTLD_LOCAL, and which OS supports it? I've never heard of that one. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Ping - sized tests with 0% and 100% packet loss! Any ideas?
On Tue, 02 Nov 1999 00:16:02 GMT, Josef Karthauser wrote: > A wierd one. I'm trying to track down a packets size (I believe) problem > on my network. During ping testing I've come across the following strange > which I don't understand. PR 13292 Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
