Re: Why is this architecture dependent?
James Howard wrote: > We know I ask dumb questions a lot, but this one may not be so dumb. A > friend of mine was joking about having a device called /dev/foo which > would be like /dev/zero, except it would spit out the word "foo" over and > over again. Well, we laughed about it, but today, I implemented > it. (This was cool since this was the first time I've ever hacked the > kernel and it worked right...) [...] You are right and work is under way to break out this functionality in a MI driver. Search the mailing list archives for details. A first attempt can be found at: http://jeroen.vangelderen.org/FreeBSD/misc_device/ MarkM will soon import a variant of this with his excellent Yarrow work. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why is this architecture dependent?
James Howard wrote: > > In message <[EMAIL PROTECTED]>, "Jeroen C. van Gelderen" write > s: > > You are right and work is under way to break out this functionality in > > a MI driver. Search the mailing list archives for details. A first > > attempt can be found at: > > > > http://jeroen.vangelderen.org/FreeBSD/misc_device/ > > > > MarkM will soon import a variant of this with his excellent Yarrow > > work. > > Ahh, excellent. I was hoping to see something like this. > > Will random and urandom also end up therE? Broken out into their own device, yes. As a bonus we'll provide a better PRNG construct named Yarrow. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How many files can I put in one diretory?
"Nicole Harrington." wrote: > > On 23-Jun-00 Daniel O'Connor wrote: > > > > On 23-Jun-00 Nicole Harrington. wrote: > >> > Yeah.. This is why databases where invented :) > >> Hey I agree... However even if the html was databased.. (working on that > >> now) > >> the custom graphics cannot be. (yet) > > > > Hmm.. can't you do binary blobs in a DB and change the image URL's to be cgi > > requests? > > > > I dunno.. whats a "binary Blob"? Pleonasm? :-) BLOB = Binary Large OBject. >From the TransBase SQL Reference Manual: "TransBase does not interpret the contents of a BLOB. Each field of type BLOB either contains the NULL value or a BLOB object. The only operations on BLOBs are creation, insertion, update of a BLOB, testing a BLOB on being the NULL value, extracting a BLOB via the field name in the SELECT clause, extracting a subrange of a BLOB (i.e. an adjacent byte range of a BLOB), and extracting the size of a BLOB." Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mbuf re-write(s), v 0.1
Alfred Perlstein wrote: > > * David Greenman <[EMAIL PROTECTED]> [000703 01:32] wrote: > > .. response to mbuf rewrite > > >I'm not trying to 'frown upon evolution', unless the particular form of > > evolution is to make the software worse than it was. I *can* be convinced > > that your proposed changes are a good thing and I'm asking you to step up > > to the plate and prove it. > > I agree, we can not afford to sacrifice performance for memory > footprint any longer, Nobody talks about *sacrificing* performance here if I'm interpreting Bosko's mail correctly. > it's just not realistic. If a subsystem > needs X amount of memory at some point in time it will need it > again. Uh? If the peak is reached only ever so often I'd rather see the memory reclaimed so that it can be used for something else. (If it doesn't affect performance too much that is.) In fact, the whole design of the FreeBSD VM system responds dynamically to the load imposed thereby rendering you claim invalid for at least one subsystems. > Sacrificing performance to fix the small occurances where > this is not the case is not worth it, the general case will always > be there and will be more important. You seem to imply that you have proof that Bosko's patches will negatively affect the general case I assume? Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sources for null device!!!
Mohana Krishna Penumetcha wrote: > > hi, > > where can i find the sources corresponding to /dev/null?? cd /sys && find . -name null* && use common sense -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anyone try the new dual-head G-400 drivers?
thomas r stromberg wrote: > >We're looking at buying some workstations for our network admins >here, and dual head is a plus. We were looking at buying them from >hardware.bsdi.com, and then today on Slashdot I saw: > >- >Matrox has released a beta driver for their G200/G400/G450 which >includes support for DualHead and QuadHead (up to 4 monitors), Flat >Panel and TV out. This driver is a beta. You can get it here and I >mirrored it here. You'll need XFree 4.0.1 in order to use this >driver. Please follow the readme file carefully! (the readme file >from Matrox's FTP needs to be converted dos2unix). Note: you cannot >use the 3D hardware acceleration on the 2nd monitor (yet). >- > >And of course, I was instantly happy when I saw this.. > >Has anyone tried these drivers yet in FreeBSD? They look to be the >OS-independant XFree86 4.0.1 modules (nothing funky like the NVIDIA >ones). They come with some source code, but it appears to be >wrappers around a missing HAL (?) library, though I could be wrong. > >Please forward any successes/failures to the list. I have a G400Max (32MB) running dual head on 1600x1200. I've lost my display once after exiting X but a remote login and reboot did work. No crashes or lockups (knock on wood). [...] Section "Device" Identifier "Matrox Millennium G400 32MB 1" Driver "mga" BusID "PCI:1:0:0" Screen 0 EndSection Section "Device" Identifier "Matrox Millennium G400 32MB 2" Driver "mga" BusID "PCI:1:0:0" Screen 1 EndSection Section "Screen" Identifier "Screen 1" Device "Matrox Millennium G400 32MB 1" Monitor "Vision Master Pro 510" DefaultDepth 24 Subsection "Display" Depth 24 Modes "1600x1200" ViewPort0 0 EndSubsection EndSection Section "ServerLayout" Identifier "Simple Layout" Screen "Screen 1" RightOf "Screen 2" Screen "Screen 2" InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" EndSection [...] [...] FreeBSD 4.1-STABLE #0: Fri Aug 11 18:58:57 AST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GROLSCH Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbff real memory = 335532032 (327668K bytes) avail memory = 322437120 (314880K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 11 IOAPIC #0 intpin 19 -> irq 10 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc03a9000. Preloaded elf module "procfs.ko" at 0xc03a909c. Preloaded elf module "vinum.ko" at 0xc03a913c. Preloaded elf module "if_fxp.ko" at 0xc03a91dc. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 10 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0xe800-0xe80f at device 4.3 on pci0 ahc0: port 0xd000-0xd0ff mem 0xe000 -0xefff irq 10 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: port 0xb800-0xb83f mem 0xdf00-0xdf0f ,0xdf80-0xdf800fff irq 10 at device 9.0 on pci0 fxp0: Ethernet address 00:90:27:88:f0:64 pcm0: port 0xb400-0xb43f irq 11 at device 12.0 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> [...] -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anyone try the new dual-head G-400 drivers?
"Alexander N. Kabaev" wrote: > > This driver will not run on FreeBSD most likely. It seems like the driver needs > Linux framebuffer device to run. Fortunately this doesn't seem to be the case. Works like a charm... Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FYI: RSA Donated to the public domain
Warner Losh wrote: > > In message <[EMAIL PROTECTED]> Warner Losh writes: > : RSA Security Releases RSA Encryption Algorithm into Public Domain > > Note that other information at the site says that RSAREF isn't > released into the public domain. Its use is still governed by > copyright law, so we'll have to use the international version of > RSAREF if we want to get RSA into -current. RSAREF was only neccessary whilst the patent was enforced. Now that RSA is released[1] we can use the OpenSSL RSA implementation which is better. [1] The press release talk about RSADSI "waiving its rights to enforce the RSA patent for any development activities" This is very cunning as the patent never actually covered development. Instead it covers usage and sales of products incorporating RSA, both of which are not explicitly allowed for in the press release. Better be careful, better get written approval! Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FYI: RSA Donated to the public domain
Mike Silbersack wrote: > > On Wed, 6 Sep 2000, Jeroen C. van Gelderen wrote: > > > [1] The press release talk about RSADSI "waiving its > > rights to enforce the RSA patent for any development > > activities" > > > > This is very cunning as the patent never actually > > covered development. Instead it covers usage and > > sales of products incorporating RSA, both of which > > are not explicitly allowed for in the press release. > > Better be careful, better get written approval! > > All of the pages they've put up on their website seems to disagree with > what you've just said. I just pointed out that the press release (from which I quoted) doesn't state that use/selling of RSA is allowed now. It seems that the FAQ allows for use and sale. Which document prevails is up in lawyer land... > I think you're confusing use of RSA and use of > RSAREF/BSAFE, Nope, the press release explicitly (see quote above) talks about the patent (which covers the algorithm, not RSAREF) and I was pointing out just that. > which they're still maintaining control over (as Warner > said.) Which is not an issue as we don't need RSAREF, not even an international version of RSAREF :-) > Somehow I rather doubt they're trying to trick people into using RSA for > the next week, and then going on a mass lawsuit spree. You may very well be right but in case you are not, it would be rather nasty if we got harassed, right? RSADSI has not been nice about their IP in the past couple of years and I have no reason to believe they will be now. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: zero copy TCP
"Jin Guojun (DSD staff)" wrote: > > I heard that zero copy TCP is already in FreeBSD, isn't it? > I could not find any information in searching the entire website. > Before I am going to spend some silly time working on it, > I would like to know what is the status for "ZERO COPY TCP" in > FreeBSD right now. > If it already exists, how can I enable it (for 1500 MTU, not Jumbo Frame)? > or someone is still working on it. http://people.freebsd.org/~ken/ http://people.freebsd.org/~ken/zero_copy/ -Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Should jail treat ip-number?
Poul-Henning Kamp wrote: > >-Jail(2) specify "ip_number" and/or "ip6_number" into the kernel. > > Well, I guess we want it to be "and", right ? Will people want to > bind both a IPv4 and IPv6 address (does it make sense to do so ?) > or will people only need to bind one of them ? What about multiple IPv6 or IPv4 addresses per jail? It might be a good idea while Inoue-san is at it. Or is this an incredibly stupid question? Cheers, Jeroen -- Jeroen C. van Gelderen - [EMAIL PROTECTED] Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Should jail treat ip-number?
Yoshinobu Inoue wrote: > If explicit needs for "multiple addrs per address family" are > not clear now, I would like to try to implement just adding > ip6_number member for this time. I think sockaddrs are better because it allows you to change to multiple IP-support without changing the interface again. Or you can add IPX (whatever) support without disturbing existing applications... I'd say (but I'm not a real hacker) make jail accept a list of sockaddrs and -for now- disallow anything except a single IPv4 and a single IPv6 address in that list. I'm now pretty sure multiple IPs per jail is a good idea, but you can easily defer implementation to some point in the future... Cheers, Jeroen -- Jeroen C. van Gelderen - [EMAIL PROTECTED] Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Needed: suid library calls (was Re: cvs commit: src/crypto/openssh sshd_config)
Matthew Dillon wrote: > > :"Jeroen C. van Gelderen" wrote: > : > :> [...] > :> > :> Since user authentication is needed by more than one program it > :> should live in it's own process. Right now there is code > :> duplication and it is impossible to change the authentication > :> policy without messing with sshd. > :> > : > :What we _really_ need is some mechanism to recognize the difference > :between a user program and a system library, with an eye towards > :granting privileges to trusted libraries without letting those privileges > :leak past the library in question. > > Oh god, its MULTICS! Run! Run! Run for the hills! Hold on! I only spoke the first part, mind your quoting pleaz! Cheers, Jeroen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.0 - Isa devices not being probed
Dennis wrote: > > At 07:30 PM 5/27/00 -0400, Jeroen C. van Gelderen wrote: > >Dennis wrote: > >> > >> At 09:54 AM 5/27/00 +0200, John Hay wrote: > >> >> In message <[EMAIL PROTECTED]> Dennis writes: > >> >> : My 4.0 system doesnt probe ISA devices on my system. > >> >> : > >> >> : Whats the trick? Is there a config requirement with old-style drivers? > >> >> > >> >> They probe great for me. what, specifically, isn't probing? > >> > > >> >He is probably talking about their own driver. In that case you have to > >> >add it to /sys/i386/isa/isa_compat.* or bite the bullet and new-busify > >> >it. > >> > >> YesWhose brainstorm was it to use the new convoluted bus nonsense in > >> FreeBSD 4.0? Clearly someone who never wrote a driver with a complex > >> controller with indexed memory mapped registers.Whats next, assembler > drivers? > > > >Uhm, the very fact that you are too simple-minded to understand the > >new, flexible, structured, high-performance bus architecture is sad. > >That you take it out on the people reading -current is beyond sad. > >If you can't behave like an adult shut up and go away. > > I understand it, and I think it sucks. The world is going to object > oriented languages to make programming complex tasks easier , and freebsd > is going in the other direction. Dennis: you just posted a private email to a public mailing list: From:"Jeroen C. van Gelderen" <[EMAIL PROTECTED]> Time:Sat 19:30 Subject: Re: 4.0 - Isa devices not being probed To: Dennis <[EMAIL PROTECTED]> 'Nuff said. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kerneld for FreeBSD
Mike Smith wrote: [...] > This is, IMO, a good idea. I certainly don't want some smartass daemon > unloading a module just because it thinks it should. 8) You can always patch kldunload and have cron periodically execute a kldunload --unused-modules Or? Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kerneld for FreeBSD
Mike Smith wrote: > > > Mike Smith wrote: > > [...] > > > This is, IMO, a good idea. I certainly don't want some smartass daemon > > > unloading a module just because it thinks it should. 8) > > > > You can always patch kldunload and have cron periodically execute a > > kldunload --unused-modules > > Or? > > I have no faith at all any metric other than one determined by the module > itself to indicate "unuse", Did I suggest kldunload --unused-modules -f ? I didn't think so. > and if a module wants to unload itself due to > "unuse", it can already do so. You wouldn't have control over that process if the modules decides for itself. It's a sysadmin decision to unload modules, not the module's decision. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ [EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kerneld for FreeBSD
Mike Smith wrote:
>
> > > and if a module wants to unload itself due to
> > > "unuse", it can already do so.
> >
> > You wouldn't have control over that process if the modules decides
> > for itself. It's a sysadmin decision to unload modules, not the
> > module's decision.
>
> So why introduce a third party? ("kerneld") If the admin wants to
> remove a module, great.
That was the point I was trying to make. If the admin wants to
remove modules manually he can do so. If he wants to have it
happen periodically he can set up a cron job to do it. You would
just need to add an option to kldunload that unloads all unused
modules. You didn't read very well, I never promoted "kerneld".
This last comment referred to
> and if a module wants to unload itself due to
> "unuse", it can already do so.
because modules should not unload themselves, it's up to the
admin to decide.
Cheers,
Jeroen
--
Jeroen C. van Gelderen o _ _ _
[EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_)
_< \_ _>(_) (_)/<_\_| \ _|/' \/
(_)>(_) (_)(_) (_)(_)' _\o_
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
