Re: stray irq 7
On Thu, Jan 18, 2001 at 10:38:31PM +, Josef Karthauser wrote: At the risk of being dragged into this, I've see this kind of behaviour on RELENG_3 also in the past. I have vague memories of it in 386BSD. It's really nothing new at all. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Sitting on hands (no longer Re: FreeBSD vs Linux, Solaris, and NT)
On Thu, Dec 21, 2000 at 11:53:50AM -0600, Peter Seebach wrote: In message [EMAIL PROTECTED], "SteveB" writes: In the open source world is there a official QA process or group. Is there a FreeBSD test suite that releases go through. QA is unglamorous work, but needs to be done. I don't know about the "official" process, but I will tell you that I'd rather have my life depend on FreeBSD-current than on Windows NT, despite the "QA cycle". There are many ways to do effective QA. Yup. I think the important point here is that the formal QA cycle is a means to an end, but it's not the only way to achieve that end. I get concerned that those who point to a lack of a QA cycle in open source software are missing the point entirely: They're focussing on the 'process' they're familiar with so much that they don't seem to acknowledge that alternative approaches can demonstrate similar results. At the end of the day, the track record of major open-source projects speaks for itself: Yes, there are bugs, but there are bugs in commercial software which is shaped and bounded by QA procedures as well. Overall, though, I'd hazard a guess that open-source software is generally more reliable (it is in my experience, anyway). - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Streams support.
On Mon, Nov 06, 2000 at 12:52:55PM -0800, Julian Elischer wrote: Riaz Khan wrote: I just need a clarification regarding streams support. Does FreeBSD provides support for streams programming. - i don't think so. I need info regarding how the network stack is implemented in FreeBSD. hope its very similar to linux architecture. there is some streams supprt as part of the SYSV emulation. I have no idea how complete it is or if it can be used natively. Don't even think about it :-) It's an evil hack. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.1 make world and cvsup release field
On Mon, Sep 18, 2000 at 02:45:06PM -0400, Christopher Stein wrote: On Mon, 18 Sep 2000, Kris Kennaway wrote: See the /usr/src/UPDATING file after updating your source and be sure to follow the directions precisely. Every message I see in the archives on these points is very simple: "See /usr/src/UPDATING" It's more like, "See /usr/src/UPDATING after updating your source." Unfortunately, my system has no /usr/src/UPDATING. If you had updated your source, you would have /usr/src/UPDATING. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
GeForce 6600 driver
Nvidia have released source code for a linux kernel driver and an XFree86 module which provides 3D accelleration via OpenGL. Having just acquired one of these boards, I'm intersted in knowing whether anyone has been interested in porting that driver from Linux to FreeBSD. I believe the XFree86 module should work without modification (include file locations notwithstanding). The kernel module might require a bit of work, though. Has anyone already made any progress on this which I could build on? Or any useful contacts inside Nvidia who could help out? Thanks, - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Bridging problems.. (WaveLan related?)
On Sat, Jul 01, 2000 at 01:56:51AM -0500, Chris Csanady wrote: It never fails.. I always post stuff just minutes too soon. Anyways, it seems that the problem is with the WaveLan network. In ad-hoc, or infrastructure mode, the card can only send frames with its own mac address as the source. Apparrently, the card needs to be set up as an access point (or something) to do bridging. You can make it run as an access point... if and only if you're prepared to produce an 802.11 protocol suite to run in the FreeBSD kernel, because you won't be able to use the one in the card's firmware. Of course, if you want to do something as insane as that, I'm sure your efforts will be welcommed with open legs^H^H^H^Harms. Being able to replace an access point with a FreeBSD box which costs a third as much would be tres cool. This is particularly true in the case of the Aironet 802.11 gear, which has even worse restrictions wrt bridging and even more expensive access points. (FWIW: With the Aironet kit, when you place the card into "monitor mode" you can't transmit frames at all). - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ttys entry for palm pilot as dumb terminal
On Fri, Jun 23, 2000 at 03:34:06PM -0400, Brian Reichert wrote:
Anyway, the suggested entry in /etc/ttys:
ttyd0 "/usr/libexec/getty std.9600" dialup on secure
does not work for me at all, yet if I do this intead:
cuaa0 "/usr/libexec/getty std.9600" dialup on secure
I indeed get a login prompt, and I'm all set.
I know that one device is for initiating outgoing connections, and
the other for incoming connections, but I don't understand why the
lines provided in a stock install seem to have the sense reversed...
It's because the Palm's serial port only runs 3 wires, and doesn't
provided a DCD signal. Opens on ttyd0 block until DCD is asserted,
so you're screwed if you're on a Palm :-) Opens on cuaa0 succeed
straight away if the device is idle.
- mark
--
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
[Oz-ISP] FreeBSD and the forces of darkness. Real religious wars! (fwd)
This is a message which appeared on the aussie-isp mailing list earlier today. I thought people here might like it :-) Ross is a reliable source, so I doubt we can chalk this one up to "urban legend". - mark -- Forwarded message -- Date: Wed, 14 Jun 2000 15:45:51 +1000 (EST) From: Ross Wheeler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [Oz-ISP] FreeBSD and the forces of darkness. Real religious wars! I've got to tell someone about this I'm flabergasted! A client of a client had their internet gateway machine (a Linux box) hacked recently, and seriously compromised. Ok... totally screwed. So, much panic, waving of arms and gnashing of teeth, and it was a case of "drop everything and help" this poor school. The person who set up the original box is on the other side of the continent and seems to be not contactable, or something. Anyhow, we helped. KNOWING the box had been hacked and WOULD be under constant scrutiny, we suggested FreeBSD (now before we start any religious wars here, yes, a linux box MAY be as secure as a FreeBSD box, assuming both were set up by people familiar and competent with them both but we're a FreeBSD site and not expert with Linux! Plus, it was compromised as a Linux box, much better to change things a little while we're at it). So the box was completely re-built. They moved the goalposts a couple of times (changing how things needed to be set up AFTER it had been done, but hey...). and now that it's all going and working. they want to rip it out and put linux back on again. Why? Well I could start a guessing competition here. And you guys (and girls) are NOT allowed to kill yourselves laughing here... This is what the person actually typed: "I've just had a converstaion with (our Principal) about some of the changes. We've had to deal with some of the philosphical issues related to BSD. As you know BSD uses a 'devil' icon to portray the BSD symbol. Given we are a Christian school this is a significant concern for us. Even after reviewing the sites blurb about the origin of the symbol, we've come to the conclusion that it would not be appropriate for us to use the software." Can you believe it?! I tried to "inform" them about the "mascot" "some of our parents who are very technically savvy would not care about the disctinction. It is the subliminal message the icon represents..." And then the FreeBSD site itself fueled the fire: "Even the site talks about a deamon being 'unleashed' in you computer blah." So that's that. No further discussion would be entered into. They've made their decision. with a parting shot that: "what we need to concern ourselves with as a Christian school is the 'message' or 'image' that may unwittingly be portrayd." I tried an internal modem, [EMAIL PROTECTED] but it hurt when I walked. Mark Newton - Voice: +61-4-1620-2223 - Fax: +61-8-82231777 - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SVR4 Emulation [was Re: iBCS status?]
On Tue, Jun 13, 2000 at 11:45:28PM -0400, Matthew Emmerton wrote: Even more interesting is the SCO document on how ELFs are pseudo-branded. OpenServer 5: No brand, but have a 28-byte NOTE field. UnixWare 7: No brand, but have one of the flags set in the FLAG field. (I couldn't find anything more specific than this.) Ah, thanks for that - I'll note it away for not-too-distant future reference. The emulator structures at the moment look for the ELF interpreter and try to switch on that, but I think that'll bite us with SysVR4 because all the SysVR4 OSs will use the same ELF interpreter pathname, and because it doesn't work as a discriminator anyway (Solaris executables still need to be specifically branded, or you need to rely on kern.fallback_elf_brand). Additional discriminators like this (even if they're bodgy crap ones) are useful things to know about. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SVR4 Emulation [was Re: iBCS status?]
On Wed, Jun 07, 2000 at 09:46:26AM -0500, Dan Nelson wrote: It's hard because SCO doesn't document any of this. You have to root through headers trying to figure out what structures are used when. How do you think the rest of the emulator has been written? :-) Ok -- I envisaged that there'd be a difficulty with different SysV vendors who used different semantics for the same syscalls, or different syscall numbering schemes. "It could happen!" (and, as we can see, it probably has). To fix it in as painless a way as possible, I'm envisaging something along the lines of this: * The existing svr4 KLD module, which implements the guts of the emulator; and * Additional much, much smaller modules which implement the differences between the "base" svr4 and wierd oddball variants. The additional modules would be dependent on the base module. Each one would have its own syscall table, but most of the entries in it would point to symbols which are defined in the base module. Only the system calls which have totally different semantics would need to be defined separately. Of course, this also gives us a simple way to renumber syscalls. Each variant would have its own ELF brand to aid the selection of the correct API. The files used to implement this would be in subdirectories of src/sys/svr4 and src/sys/i386/svr4, each of which would contain a *_sysvec.c file, a syscalls.master file, and the support .h files needed to glue it all together. The result of running "make" in src/modules/svr4 would be a base KLD plus several smaller flavour- specific KLDs. Note that syscall numbering isn't the only thing I can see that'll be different between "flavours" of SysVR4. Things like ioctl() commands, signal numbers, and basically all the other things the emulator translates could exhibit minor differences between flavours, but the bulk of it should be the same from vendor to vendor. Comments? - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SVR4 Emulation [was Re: iBCS status?]
On Wed, Jun 07, 2000 at 10:24:15PM -0400, Matthew Emmerton wrote:
Each variant would have its own ELF brand to aid the selection of the
correct API.
Makes sense. On a related note, I'm curious to see how this will integrate
into existing non-kernel tools. For example, truss and brandelf) only
understand BSD and Linux ELF binaries, and will require modifications to
identify all the different brands.
brandelf will really understand any brand at all; We just add special
cases to suppress the need for -f for "known" brands. As it happens,
though, there's no reason why you can't run "brandelf -f -t BOGUS-BOGUS foo"
and have it put a BOGUS-BOGUS brand into an ELF object called foo.
What may compound the problem is if
multiple ELF formats use the same brand, or none at all (as is the case with
SCO ODT5 binaries.)
Well, yes, that's the thing - Branding is, AFAICT, specific to FreeBSD
and Linux ELF; All other OSs need either a heuristic to select the
appropriate emulator (for example, the pathname to the ELF interpreter in
the executable, which doesn't always work), or an explicit branding, or
an appropriate setting of the kern.fallback_elf_brand sysctl MIB variable.
- mark
--
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: iBCS status?
On Tue, Jun 06, 2000 at 01:25:53AM -0500, Dan Nelson wrote:
In the last episode (Jun 06), Mark Newton said:
On Tue, Jun 06, 2000 at 01:48:10AM -0400, Matthew Emmerton wrote:
I was recently playing around with iBCS support in FreeBSD
3.4/4.0, and noticed that there hasn't been much done since 96/97.
From what I can see now, FreeBSD can't run SCO OpenServer 5.0 ELF
binaries, which is a feature I need desperately -- Linux has this
functionality. If anyone is working on iBCS, let me know,
otherwise I'll start hacking away at the the emulation code to
allow SCO OSR5 ELF stuff.
SCO OpenServer doesn't use iBCS2, it's an SysVR4 ELF system. FreeBSD
has notional support for it under the svr4 emulator in 4.x and
-current, but hardly any testing has been done with SCO (I've been
using Solaris binaries and libraries).
I can say it pretty much doesn't work at all on SCO.
I'm not at all surprised :-) I've had some reports from people who say
they've had limited success, but since I don't have any SCO bits here
I haven't been running any SCO software.
There is
apparently quite a difference between Solaris and SCO SVR4; the first
thing I had to do was change the lseek() syscall to use 32-bit offsets
instead of 64-bit, for example.
Interesting - Solaris has two lseek syscalls, notionally "lseek" and
"lseek64". If SCO only has one, which is a 64 bit variant, could
you perhaps let me know what its syscall number is?
- mark
--
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: iBCS status?
On Tue, Jun 06, 2000 at 01:48:10AM -0400, Matthew Emmerton wrote: I was recently playing around with iBCS support in FreeBSD 3.4/4.0, and noticed that there hasn't been much done since 96/97. From what I can see now, FreeBSD can't run SCO OpenServer 5.0 ELF binaries, which is a feature I need desperately -- Linux has this functionality. If anyone is working on iBCS, let me know, otherwise I'll start hacking away at the the emulation code to allow SCO OSR5 ELF stuff. SCO OpenServer doesn't use iBCS2, it's an SysVR4 ELF system. FreeBSD has notional support for it under the svr4 emulator in 4.x and -current, but hardly any testing has been done with SCO (I've been using Solaris binaries and libraries). If you want to play with it and send patches, feel free to bounce them my way. See http://slash.dotat.org/~newton/freebsd-svr4/ for more info. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How to read a file from a device driver?
On Fri, Mar 17, 2000 at 11:00:08PM -0500, Gary T. Corcoran wrote: Can someone please tell me how I can read a file from a device driver in FreeBSD? I need to download 2 or 3 relatively-large code files to my device, choosing from amongst several different files depending on which mode I'm operating in. Therefore compiling-in the code is not a reasonable choice. Defer the initialization of the device until a user-mode process opens it and performs an ioctl() on it. The ioctl should take a (void *) to a buffer containing a structure which says how long the code is, followed by the code itself. That avoids the whole problem of reading a file from your driver, you can do it with a user-mode helper process. If you can either tell me how to be able to read a file from my driver, or point me to an example driver which does this, I would appreciate it. I think the Stallion serial port drivers do something kinda similar. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
WaveLAN/IEEE Turbo (Silver)
I'm trying to get a WaveLAN/IEEE Turbo (Silver) card working on a two month old -current system using the ISA bus card which comes with the PCMCIA WaveLAN unit. "pccardc dumpcis" says it wants IRQ 6, so I've made sure that that was included in the list of IRQs in pccard.conf. It's still unable to allocate I/O space, though: card insertion yields: pccard: card inserted, slot 0 wi0: No I/O space?! ... which is slightly demoralizing :-) The relevent bits of pccard.conf: io 0x240-0x3ff irq 3 5 6 10 11 13 15 memory 0xd4000 96k # Lucent WaveLAN/IEEE card "Lucent Technologies" "WaveLAN/IEEE" config 0x1 "wi0" ? insert echo WaveLAN/IEEE inserted insert /etc/pccard_ether $device remove echo WaveLAN/IEEE removed remove /sbin/ifconfig $device delete I'll attach the output of pccardc dumpcis. I saw something about this on -hackers or -current about two weeks ago, but I didn't have a WaveLAN card then, so it didn't occur to me to save it. I can't find any reference to it in the archives either, but I'm sure *someone* here knows an answer. I know the WaveLAN stuff is crap, and I'd rather be using Aironet at the moment (at least that works!), but we've thought it prudent to give the Lucent stuff a try (even if only to make sure our suppliers understand that we can change vendors easily, so they'd better give us a good price grin Cheers, - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: WaveLAN/IEEE Turbo (Silver)
On Thu, Mar 16, 2000 at 12:59:13AM +1030, Mark Newton wrote: I'll attach the output of pccardc dumpcis. Blurgh. Maybe I'll attach it this time. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: 00 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = 512b, 1 units Tuple #2, code = 0x17 (Attribute memory descriptor), length = 4 000: 67 5a 08 ff Attribute memory device information: Device number 1, type SRAM, WPS = OFF Speed = 5.0 x 100 ns, Memory block size = 512b, 2 units Tuple #3, code = 0x1d (Other conditions for attribute memory), length = 5 000: 01 67 5a 08 ff (MWAIT) Tuple #4, code = 0x15 (Version 1 info), length = 80 000: 05 00 4c 75 63 65 6e 74 20 54 65 63 68 6e 6f 6c 010: 6f 67 69 65 73 00 57 61 76 65 4c 41 4e 2f 49 45 020: 45 45 00 56 65 72 73 69 6f 6e 20 30 31 2e 30 31 030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff Version = 5.0, Manuf = [Lucent Technologies],card vers = [WaveLAN/IEEE] Addit. info = [Version 01.01],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[] Tuple #5, code = 0x20 (Manufacturer ID), length = 4 000: 56 01 02 00 PCMCIA ID = 0x156, OEM ID = 0x2 Tuple #6, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #7, code = 0x22 (Functional EXT), length = 2 000: 01 07 Modem interface capabilities: Tuple #8, code = 0x22 (Functional EXT), length = 5 000: 02 40 42 0f 00 Data modem services available: Tuple #9, code = 0x22 (Functional EXT), length = 5 000: 02 80 84 1e 00 Data modem services available: Tuple #10, code = 0x22 (Functional EXT), length = 5 000: 02 60 ec 53 00 Data modem services available: Tuple #11, code = 0x22 (Functional EXT), length = 5 000: 02 c0 d8 a7 00 Data modem services available: Tuple #12, code = 0x22 (Functional EXT), length = 2 000: 03 07 Tuple #13, code = 0x22 (Functional EXT), length = 8 000: 04 06 00 60 1d 1e ac 5c Voice services available: Tuple #14, code = 0x22 (Functional EXT), length = 2 000: 05 01 Modem interface capabilities: Tuple #15, code = 0x1a (Configuration map), length = 7 000: 03 01 e0 03 00 00 01 Reg len = 4, config register addr = 0x3e0, last config = 0x1 Registers: X--- Tuple #16, code = 0x1b (Configuration entry), length = 15 000: c1 01 19 76 c5 4b d5 19 36 36 05 46 7f ff ff Config index = 0x1(default) Interface byte = 0x1 (I/O) Vcc pwr: Minimum operating supply voltage: 4 x 1V, ext = 0x4b Maximum operating supply voltage: 5 x 1V, ext = 0x19 Max current average over 1 second: 3 x 100mA Max current average over 10 ms: 3 x 100mA Power down supply current: 1 x 10mA Card decodes 6 address lines, limited 8/16 Bit I/O IRQ modes: Pulse IRQ level = 6 Tuple #17, code = 0xff (Terminator), length = 0 2 slots found
Re: Vinum encapsulating existing partitions (was: Sysinstall 'A'uto partitioning)
On Tue, Mar 14, 2000 at 12:12:17PM -0800, Greg Lehey wrote: On Thursday, 9 March 2000 at 11:12:21 +1030, Mark Newton wrote: Another thing which would be useful is the ability to "vinum-ize" an existing filesystem without destroying it first. On Solaris and IRIX I can do that by creating a logical volume with a single plex which just happens to contain the same partition as the existing filesystem, thereby wrapping the filesystem in the logical volume. [ ... ] It's still on my wishlist, though I don't know if I have it on the web page (and since I'm on the road at the moment, I can't check). My main concern here is that I want to maintain the device name/drive ID independence (for those who may not know, you can take the disks of a Vinum array out, shuffle the device IDs and reboot, and it will still put the components together in the correct way). IRIX does accomplish this (Solaris ODS doesn't). There are certain features of the way it handles its disks which make that simpler, though: IRIX utilizes a reserved partition on every disk (partition 8) as a "volume header", which must start at sector 0 and can be arbitrarily sized. The volume header contains a disklabel (which starts at sector 0, so it overlays the disk's partition table) and zero or more additional files in a simple filesystem (not a filesystem as such; all files are contiguous, rammed together a-la a tar archive, simple enough for a first-stage bootloader to understand). The most common use for this filesystem is to contain the second-stage bootloader (aka /boot/loader on BSD), but there are other purposes for it as well. One of those purposes is to host XLV volume labels, which are replicated across all disks which participate in XLV volumes. Each XLV volume label contains a unique identifier for the spindle which contains it. That means that the "subdisk ID" equivalent, together with all the other info in the label, is held out-of-band, leaving the partition containing the XLV volume element as a repository for filesystem data and nothing else. The advantage of this approach is, of course, that an XLV volume can "wrap" a preexisting filesystem without destroying it. If I want to grow my /usr partition on dks0d1s6 by using a "spare" partition on dks1d2s0, I can do this: irix# xlv_make xlv_make volume usr usr xlv_make data usr.data xlv_make plex usr.data.0 xlv_make ve dks0d1s6 usr.data.0.0 xlv_make end Object specification completed xlv_make exit Save changes? [n] y irix# [ then modify fstab to mount /usr from /dev/xlv/usr instead of /dev/dsk/dks0d1s6 and reboot. Once I've done that, I'll never need to reboot to manage /usr again; I can perform operations like growing the filesystem onto additional volume elements without needing to unmount it (in fact, some operations will fail to work if the filesystem is unmounted) ] irix# xlv_make xlv_make ve foo dks1d2s0 foo xlv_make end Object specification completed xlv_make exit Save changes? [n] y irix# xlv_mgr xlv_mgr attach ve foo usr.data.0 VE foo attached to plex usr.data.0 xlv_mgr show -verbose all [ you'll see that "foo" has been renamed to "usr.data.0.1" ] xlv_mgr exit irix# xfs_growfs /usr [ /usr is "grown" online (i.e: you don't need to unmount it) ] The obvious way to do that is to say "there must be a Vinum partition on this physical drive, but the subdisk doesn't have to be on it". That could be a problem for existing disks. Thoughts? A variation might be, "There can be more than one Vinum partition on a physical drive, and Vinum metadata can be kept in a different one from Vinum data." Cheers, - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Sysinstall 'A'uto partitioning
On Wed, Mar 08, 2000 at 05:30:00PM -0700, Warner Losh wrote:
Having vinum support in sysinstall would cut into my consulting
business :-).
"Oh, sorry, let's not do that then!" :-)
Setting up a mirrored system is hard enough that people
are hiring consultants to do it.
Yes, I have to say that I've done a couple of these myself.
Another thing which would be useful is the ability to "vinum-ize"
an existing filesystem without destroying it first. On Solaris and
IRIX I can do that by creating a logical volume with a single plex
which just happens to contain the same partition as the existing
filesystem, thereby wrapping the filesystem in the logical volume.
I can then mount that logical volume; the entire process takes about
two minutes. Adding additional plexes to it to grow it or add redundancy
is then done in the same way that'd be done for any other logical
volume.
I'm not sure that you can do that with vinum, though. Greg and I talked
about it about six months ago as a nice thing to have, but there are,
of course, other priorities...
- mark
--
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Great American Gas Out
On Fri, Mar 03, 2000 at 09:56:08AM -0700, Wes Peters wrote:
"Koster, K.J." wrote:
Oh, those Americans. :-)
Let's see: $1 per gallon in the US. $1.2 per litre in the Netherlands,
times 4.5 (or thereabouts) is $5.4 per gallon in the Netherlands.
Everyone in the Netherlands drives cars; everyone thinks gas is expensive.
This means that the gas prices in the US can go up 440% and people will
still drive cars and buy gas (and complain about gas prices, of course).
First, this off-topic for -hackers, so I've directed replies to -chat
if you want to continue.
Sage advice :-)
Second, I know people that commute distances that would cross your
country. I suspect the average American uses a lot more gas than the
average Nederlander.
Bah. In Western Australia there's a sheep station called "Little Texas"
which just happens to have a land area larger than the state of Texas;
I live in Adelaide, so I have to go 600 km East or 3000 km West or 3000 km
North to find another population centre with more than 50,000 people;
the nearest interstate Capital city is 980 km away. Our cities are also
a hell of a lot more widely laid-out than yours: Adelaide, with a pop.
of 1.1 million, has the same surface area as New York City.
So let's accept that distances in the US are pissant little commuter hops,
shall we? :-)
Third, our gas prices here are held down by all sorts of weird
government intervention, bizarre market shenanigans, and a public that
doesn't understand that the price of gasoline has risen only 4x in the
same period that the price of cars has risen 10x. That's certainly
NOT a "natural occurence".
Our prices are held *up* by the fact that over 50% of them constitute
State and Federal taxes.
Fourth, I'm paying $1.48/gal right now, and I want the price to go
DOWN, not UP.
I'm paying A$0.83c/L right now, which is roughly A$3.73/gal, which is
roughly US$2.76. That means the US price of petroleum can rise by almost
100% and people still still drive the kind of distances which usually
constitute international travel.
- mark :-)
--
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
DLink DGE-500SX
We've been speaking with our local DLink salescritter about FreeBSD support (we couldn't help it - he coldcalled us with a visit yesterday and tried to demo a whole lot of gear which wouldn't work under FreeBSD :-) We suggested to him that the best way to get us interested would be to contribute some hardware to the FreeBSD project so that some drivers could be written. He called us back today and said he was interested in getting a DGE-500SX Gigabit ethernet card to someone like Bill Paul (Hi, Bill!) along with programming docs, in the hope that there's interest in making it work. So is there? :-) - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Building customized kernel without root passwd
On Mon, Feb 28, 2000 at 03:58:00PM -0500, Zhihui Zhang wrote: My professor plans to use FreeBSD for teaching purpose. We will allow students to build their kernel but do not want to give them root password. So it's better to find a way to let students build kernel under their own account, save the kernel on a floppy and then boot from the floppy. How is this going to buy you anything? Once they've done that, they'll have root on the floppy-booted system, and they'll be able to mount the system's hard disk and change the root password to anything they want. If your students have physical access to the console of a system, the system is not secure. Doubly so if they have access to removable media (like floppy disks). You'd be better off firewalling the lab on the assumption that they *will* have root, in an effort to constrain the damage they can do if they misbehave, then just give them the root password so they won't have to dick around with floppies anymore. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Eclipse/BSD
On Thu, Feb 10, 2000 at 11:48:59AM +1030, Daniel O'Connor wrote: On 10-Feb-00 Mark Newton wrote: Those clauses aren't enforcible - Yet. They will be when (if) the Digital Millenium Copyright Act passes. Has it been proposed yet? (For .au) Not for .au, no. Give us five years, though... the companies pushing the DMCA have a lot of cash... - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sppp behaviour
On Fri, Jan 07, 2000 at 04:33:39PM +0100, Christoph Kukulies wrote: What is the 'normal' behaviour for a rlogin (ssh) or telnet session when one is logging into an ISP who assigns dynamic addresses and the connection has an idle timer (inactivity) (that is, the connection is dropped after a certain time period). Same as on any other OS: You get a new IP address when you reestablish your connection to the ISP, so the hosts at the other ends of any active network connections you happened to have open when you dropped your link will be sending their ACKs and data to someone else (who will no doubt start sending RST's, clearing the connections altogether, if anyone is responding on your old address at all). I have the problem that with FreeBSDs isdn (i4b) my rlogin (ssh) sessions die (are rendered unusable - lock o' city) regularly when the idle timer drops the connection. A subsequent awaking of the connection results in a different IP address being assigned from the ISP. This is perfectly normal, and is why "dial on demand IP with an idle timeout" sucks ass. Strangely Netscape does not suffer from this phenomenon. That's because Netscape (and all other web browsers) create separate short-lived TCP connections for each URL they fetch, and when you leave it idle it doesn't maintain any open connections at all (usually; your Java applets will probably screw up if they expect to have persistent connections back to the host they were loaded from). - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Serial boot prompt messages and a modem
On Tue, Dec 21, 1999 at 05:38:35PM -0800, Mike Smith wrote:
Hmm, last time I checked, they were just 'serial ports'.
Nope. The significance is determined by the software, and you're stuck
with the fact that the first serial port is the console port. End of
story. (Note: if we don't make some assumption about which port will be
the console, how do you expect the software to work out which one it
"should" use?)
Insist that consoles be cabled-in with "real" cables, and use the first
port we find with DCD asserted as the console, falling back to COM1 if
we can't find any ports with DCD (indicating that someone has failed to
follow our cabling insistence)
- mark
--
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: anybody using tn-gw-nav to tunnel ssh through a proxy?
return(1);
kludgeraw = 1;
+ } else if (gimme8bit) {
+ syslog(LLEV, "RAW connection requested");
}
if((rfd = conn_server(av[1],port,0,buf)) 0) {
***
*** 768,774
return(2);
}
!
baddest(fd,dest)
int fd;
--- 779,793
return(2);
}
! static int
! cmd_rawconn(ac, av, cbuf)
! int ac;
! char*av[];
! char*cbuf;
! {
! gimme8bit = 1;
! return(cmd_connect(ac, av, cbuf));
! }
baddest(fd,dest)
int fd;
--
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: anybody using tn-gw-nav to tunnel ssh through a proxy?
On Thu, Dec 16, 1999 at 09:57:36PM -0700, John and Jennifer Reynolds wrote: tn-gw isn't 8-bit-clean; you'll need to patch it. Try something like this: it creates a new tn-gw- prompt command called "rawopen" which gives you an 8-bit-clean link to whatever host/port you specify. When you say 8-bit-clean, what exactly does that mean? Generally speaking it means that certain bytes don't get passed through correctly: You don't end up with a clear 8-bit-wide datapath between point A and point B unless you use special escaping mechanisms. Example: Some systems don't pass through the most-significant- bit of any data presented to them. So if you punch character code 283 (which is binary 100011011) in you'll get character code 27 (which is binary 11011) out. fwtk isn't quite like that, but it's similar: tn-gw tries to do options spoofing, because it thinks it understands more about things like telnet echo enabling than the server at the other end. So, if you pass character code 255 (which introduces a telnet option) into it from the server side, you get basically nothing popping out at the client side. Meanwhile, you can get telnet options arriving at the client side with no prompting from the server whatsoever if tn-gw happens to think it's a good idea. This doesn't bother telnet one iota (after all, the bogus options are intended to make telnet work better), but it knocks other application layer protocols for six. Solution: Disable the options spoofing which tn-gw tries to do, which is precisely what the patch I posted does. I'm wondering why this whole charade works for Linux clients and others (their Makefile also suggests people have compiled it for Sun, AIX, and the bastard of them all, HP-UX) but not FreeBSD. What do we do differently? shrug Incidentally, with my patch in place a whole raft of "punch this through the firewall" possiblities arrive. I wrote a proxy which went through a send-expect sequence to "plug-through" any arbitrary TCP port when I was forced to endure a tn-gw proxy with a previous employer; I can provide it (under a BSD-style license) if anyone is interested. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: umount -f causes page fault in kernel?
On Mon, Dec 13, 1999 at 04:27:48PM +0100, Gergely EGERVARY wrote: [ ... ] "Doctor, it hurts when I do this:" mount /cdrom cd /cdrom umount -f /cdrom cd .. will cause 100% reproduceable kernel panic (page fault) "So don't do that then!" I know forced umount is dangerous, but soo ... =P It's described as "dangerous" precisely because it causes a kernel panic. Why on earth would you want/need to do that anyway? - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: syncflood attack
On Wed, Dec 01, 1999 at 07:24:58PM -0800, PinkSmurf Mushroom wrote: AS I discovered today that my box was brought down by a heavy syncflood attack, connecting to multiple ports. In addition to that, the attacker even attack the ftpd with spoofed IPs, opening tons of connection. In result I've limited the total connection allowed at anyone time but I couldnt figure out how to stop syncflood. One usually stops it by staying away from the 3l33t hax0rz channels in IRC. - mark I tried an internal modem,[EMAIL PROTECTED] but it hurt when I walked. Mark Newton - Voice: +61-4-1620-2223 - Fax: +61-8-82231777 - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: HEADS UP: ES1371/1373 sound card support in -stable
Roger Hardiman wrote: This is because in 4.x-current, the PCM driver has been totally rewritten and so, the -stable driver and the -current driver are very very different. A commit to -current and an MFC are not applicable. That'd be an MTC rather than an MFC, wouldn't it? :-) - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (forw) Reversing 32Upgrade package
Ron 'The InSaNe One' Rosson wrote: Is there anyway to reverse 32upgrade package after it has been installed on a 2.2.8-STABLE system. This is on a production box and rebuilding is not an option I have time to explore. If it's a production system you will have had backups from immediately before your upgrade, and reversing the upgrade will be a simple matter of restoring your backups. Why do you want to reverse it anyway? - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Handling segV's
Dodge Ram wrote: Also, is there a list of reasons for a SIGSEGV ? Only one: "Your program is buggy" :-) - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Generating interrupts ?
Johan Kruger wrote: I want to read the the type of motherboard the system is running on, as well as the BIOS version string. With all due respect, part of the whole point of UNIX is that you don't need to care about that. Why not tell us what you're actually trying to achieve (instead of how you're trying to achieve it) and we'll be able to give you a different way of doing it which actually makes sense. - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Generating interrupts ?
Johan Kruger wrote: H, OK , well, i want to use the specific strings as part of the info with which i am going to encrypt the kernel. Don't ask why, i am not at liberty to say. Great. We get to deal with someone who wants assistance but is too concerned with intrigue to fully explain the problem domain. We shall press on. It sounds like you want a kernel that's only able to boot on a particular machine, and you figure that that information from the BIOS is the closest thing a PC has to a hostid. I assume you'll have a kernel with an unencrypted entrypoint which knows how to decrypt the rest. Don't worry , it'l work, i just need the info from the motherboard and bios rev Have a look at i386_vm86(2) and its associated kernel support in /sys/i386, or (perhaps a better idea) think about doing your decryption in the bootloader where you have full access to the BIOS. While you're reading through it all, always keep the fact that there's probably a better way at the forefront of your mind :-) - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
SMP motherboards
Has anyone had any problems running FreeBSD-SMP on Intel GX-chipset motherboards? Conversely, does anyone have any recommendations for other motherboards to buy? - mark To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Some more commentary and results on 'postmark' (fwd)
I forwarded Brad Knowles' comments about the PostMark benchmarking suite to a NetApp engineer I happen to have known since my teens. Selected portions of his comments are included below (with permission) for your entertainment and elucidation. - mark A NetApp person wrote: Brad Knowles wrote: Both the client and server systems were 90%+ *IDLE* during all tests. I/O bound is fun! :) The benchmark has a number of problems. The 'postmark' program isn't forking at all, so there is a serious bottleneck in the process itself, especially whenever a read is issued. It doesn't really give us an accurate representation of a multi-tasking load. Most NFS servers have a multitasking load so it isn't really a fair test. I don't think Jeff was really all that interested in accurate comparisons of multi-tasking NFS performance -- for that, we've got SPEC SFS, which has been the standard method of comparing NFS performance for more than a decade. The benchmark shows pretty clearly the inefficiency of large UFS directories. Putting 2 files in a single directory is not fun, and it seriously skews the test results considering what the benchmark is supposed to be testing. Jeff's favourite problem domain is mail services, which have traditionally been lots-of-small-files-in-a-directory stuff. His benchmark reflects that focus. Thankfully, you can tweak the options to make it reflect some (but not all) other problem domains. It seems pretty clear to me that this benchmark has been designed to show-off the netapp in the best possible light and its competitors in the worst possible light. Well, ok, that may be an overly-harsh assessment, but it is still true to some degree. Actually, it's not true to *any* degree, and I know because I talked to Jeff Katcher (and his boss at the time, Andy Watson) whilst he was developing it and writing the white paper. PostMark was written to shame Sun and HP into improving their single-task NFS CLIENT performance by showing them how much better FreeBSD and Linux performed. Pure and simple. Jeff stopped coding as soon as he had something which was vaguely tunable to reflect different application loads (you don't have to have a fixed ratio of files to transactions, guys) and which showed the kinds of performance problems we'd seen with real live applications and the latest revisions of the commercial NFS clients which, thanks to introduction of a few more internal abstraction layers, were considerably slower than their predecessors. The benchmark is seriously flawed. laughter To paraphrase a hundred posts in freebsd-security: don't complain unless you're willing to write the code that fixes the problem, or at least suggest implementable solutions to the author. I'm sure Jeff will be more than happy to revise the benchmark if time permits, and I'll be forwarding the posts to him so he's got some impetus. :) I tried an internal modem,[EMAIL PROTECTED] but it hurt when I walked. Mark Newton - Voice: +61-4-1620-2223 - Fax: +61-8-82231777 - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: what is devfs?
Julian Elischer wrote: On Mon, 20 Sep 1999, John-Mark Gurney wrote: one thing that HAS to happen is the fast that some devices CAN'T "appeare" until the devfsd says it can, unless we force a very restrictive permision on all devices (600 or something similar) otherwise we will have security wholes up the wazoo... don't forget about this... a devfsd daemon is definately the way to go... While I sharply disagree, with your assertion, I also point out that if you make such a all-singing-all-dancing devfsd, then you might as well get rid of devfs entirely, and just have devfsd make the devices using normal mknod commands. Hmm - rip out the whole devfs infrastructure and replace it with something which writes tuples of (operation, devname, major, minor) to a socket somewhere, where "operation" is "create", "delete", "online", "offline", etc. Why worry about the complexities of a vfs to handle /dev in the kernel when almost all of it can be done in userland? [ Heh. *now* there'll be some wailing and gnashing of teeth... :-) ] - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: what is devfs?
Matthew Jacob wrote: Hmm - rip out the whole devfs infrastructure and replace it with something which writes tuples of (operation, devname, major, minor) to a socket somewhere, where "operation" is "create", "delete", "online", "offline", etc. Why worry about the complexities of a vfs to handle /dev in the kernel when almost all of it can be done in userland? [ Heh. *now* there'll be some wailing and gnashing of teeth... :-) ] "booting"? Not needed - The devfs registration stubs are called during driver initialization which happens at boot time anyway; When the devfsd starts up and reads messages from its socket, it'd get a queue of device instances. I'm envisaging something like /dev/log here; When syslog opens it at boot time, it gets all the log messages that have appeared during initialization. - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: placement of vi in the filesystem
Ben Rosengart wrote: I'm sure this is old ground, but could anyone please tell me why vi is in /usr/bin instead of /bin? It would be nice to be able to edit files in /etc (especially the fstab) without /usr mounted on a vanilla install. /bin/ed - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: placement of vi in the filesystem
Ben Rosengart wrote: I'm sure this is old ground, but could anyone please tell me why vi is in /usr/bin instead of /bin? It would be nice to be able to edit files in /etc (especially the fstab) without /usr mounted on a vanilla install. /bin/ed - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: nobody knows the answer?
Alfred Perlstein wrote: I have sent this email a 2 days ago but nobody answered yet. Is there anybody who I can contact with about this? I need an answer because this is a serious problem for me. You may have a program that still has a reference to that file open. Nah, that'd still influence the display from "df". - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: nobody knows the answer?
Alfred Perlstein wrote: I have sent this email a 2 days ago but nobody answered yet. Is there anybody who I can contact with about this? I need an answer because this is a serious problem for me. You may have a program that still has a reference to that file open. Nah, that'd still influence the display from df. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Possibility of increasing default MAXPARTITIONS from 8 to 16
Matthew Dillon wrote: The question I am putting to the group is whether it is "time" for us, with today's large disks, to increase the system-compiled default from 8 to 16 partitions. Instead of a-h we would have a-p It makes sense; We wouldn't be the first to do it either (IRIX has supported 16 partitions per spindle for years). Have you made the change on your hackbox already to make sure it doesn't have any negative implications? - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Possibility of increasing default MAXPARTITIONS from 8 to 16
Andrzej Bialecki wrote: On Tue, 24 Aug 1999, Matthew Dillon wrote: I don't know about all of you, but for the last few years I've been running out of partitions! It's even worse with today's big disks. I know it's not the answer, it's just related question: do you know perhaps of any initiatives (except XFS) that could significantly shorten time it takes fsck to check big filesystems, let's say 64GB? As it is now, it's almost unbearable. I naively thought softupdates would (almost) eliminate the need to do fsck... The UFS checkpointing stuff Kirk is working on is supposed to be the magic bullet that fixes this. XFS will be kinda neat too. - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Possibility of increasing default MAXPARTITIONS from 8 to 16
Matthew Dillon wrote: The question I am putting to the group is whether it is time for us, with today's large disks, to increase the system-compiled default from 8 to 16 partitions. Instead of a-h we would have a-p It makes sense; We wouldn't be the first to do it either (IRIX has supported 16 partitions per spindle for years). Have you made the change on your hackbox already to make sure it doesn't have any negative implications? - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Possibility of increasing default MAXPARTITIONS from 8 to 16
Andrzej Bialecki wrote: On Tue, 24 Aug 1999, Matthew Dillon wrote: I don't know about all of you, but for the last few years I've been running out of partitions! It's even worse with today's big disks. I know it's not the answer, it's just related question: do you know perhaps of any initiatives (except XFS) that could significantly shorten time it takes fsck to check big filesystems, let's say 64GB? As it is now, it's almost unbearable. I naively thought softupdates would (almost) eliminate the need to do fsck... The UFS checkpointing stuff Kirk is working on is supposed to be the magic bullet that fixes this. XFS will be kinda neat too. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE
Alec Kalinin wrote: I think, mentioned below program probably show the bug in virtual memory subsystem in FreeBSD-3.2-RELEASE. After running this program, FreeBSD comes into "out of swap" state, then hungs. Well, yeah, that's becuase you're running it out of swap by trying to allocate a gigabyte of memory. Why i think this is bug? Because any user can hung FreeBSD, settings in /etc/login.conf can't help. Are you sure about that? Setting datasize limits will prevent malloc() from doing what you're trying to make it do. Are you sure you're setting your login.conf settings properly? - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: RE: Need some advice regarding portable user IDs
Daniel O'Connor wrote: On 18-Aug-99 Wilfredo Sanchez wrote: Joe doesn't use the shell. The Finder will do this for him; when you insert a floppy in Mac OS, it gets mounted and shows up on your desktop. This is the case with all media. Yes... Why is this a FreeBSD problem then? I would have thought it would be up to MacOS to do the UID remapping (I must be missing something) "Think Different": The MacOS is BSD. - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE
Alec Kalinin wrote: I think, mentioned below program probably show the bug in virtual memory subsystem in FreeBSD-3.2-RELEASE. After running this program, FreeBSD comes into out of swap state, then hungs. Well, yeah, that's becuase you're running it out of swap by trying to allocate a gigabyte of memory. Why i think this is bug? Because any user can hung FreeBSD, settings in /etc/login.conf can't help. Are you sure about that? Setting datasize limits will prevent malloc() from doing what you're trying to make it do. Are you sure you're setting your login.conf settings properly? - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE
Biju Susmer wrote: Well, yeah, that's becuase you're running it out of swap by trying to allocate a gigabyte of memory. but this is done in steps of 1MB. Once it reaches out of memory, malloc should return NULL. Since there is no checking for NULL in this code, it should hit a signal, isn't it? Why that is not happening? We only had this thread a week ago. Please consult the archives. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: RE: Need some advice regarding portable user IDs
Daniel O'Connor wrote: On 18-Aug-99 Wilfredo Sanchez wrote: Joe doesn't use the shell. The Finder will do this for him; when you insert a floppy in Mac OS, it gets mounted and shows up on your desktop. This is the case with all media. Yes... Why is this a FreeBSD problem then? I would have thought it would be up to MacOS to do the UID remapping (I must be missing something) Think Different: The MacOS is BSD. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Using legacy sysinstall to upgrade live system
dannyman wrote: The point of it is, it's easy enough to download the floppies, but it's really hard to boot a system off an .flp image. :p 1. boot single-user 2. dd if=/some/dir/boot.flp of=/dev/da0s1b 3. reboot 4. When boot1 gives you the 5-second paused baton, press any key 5. enter "da(0,b)" at the Boot: prompt Us FreeBSD people can pretend we can do miniroot installs too :-) [ admittedly, I haven't tried this since before the new boot blocks were committed, but it worked perfectly last year... ] - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Using legacy sysinstall to upgrade live system
dannyman wrote: The point of it is, it's easy enough to download the floppies, but it's really hard to boot a system off an .flp image. :p 1. boot single-user 2. dd if=/some/dir/boot.flp of=/dev/da0s1b 3. reboot 4. When boot1 gives you the 5-second paused baton, press any key 5. enter da(0,b) at the Boot: prompt Us FreeBSD people can pretend we can do miniroot installs too :-) [ admittedly, I haven't tried this since before the new boot blocks were committed, but it worked perfectly last year... ] - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: mmap bug
Arun Sharma wrote: The second alternative - to mark system daemons as special sounds much more attractive. Ok, now define the difference between "system daemons" and any other daemon (or, for that matter, any other process). - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mmap bug
Arun Sharma wrote: The second alternative - to mark system daemons as special sounds much more attractive. Ok, now define the difference between system daemons and any other daemon (or, for that matter, any other process). - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: freebsd-hackers-digest V4 #576
Stephen Hocking wrote: The recent chatter about allowing kldload to give modules arguments is very interesting, as it would allow one to specify port addresses and the like. Would it be useful to be able to be able to do something like this: kldload -t kernel_config /sys/i386/conf/YOURKERNELNAME ... and have drivers consult the information they find in there for config hints? If newbus knew how to reconstruct config_devtab at runtime by parsing a "kernel_config" module's "device" and "controller" lines, we'd get dynamic runtime reconfiguration for free. It could even defer the initial construction of config_devtab until boot-time if you used "options INCLUDE_CONFIG_FILE" to provide default configuration data... - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: freebsd-hackers-digest V4 #576
Stephen Hocking wrote: The recent chatter about allowing kldload to give modules arguments is very interesting, as it would allow one to specify port addresses and the like. Would it be useful to be able to be able to do something like this: kldload -t kernel_config /sys/i386/conf/YOURKERNELNAME ... and have drivers consult the information they find in there for config hints? If newbus knew how to reconstruct config_devtab at runtime by parsing a kernel_config module's device and controller lines, we'd get dynamic runtime reconfiguration for free. It could even defer the initial construction of config_devtab until boot-time if you used options INCLUDE_CONFIG_FILE to provide default configuration data... - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Filesystem question...
Ronald G. Minnich wrote: On Fri, 23 Jul 1999, Kris Kennaway wrote: On Thu, 22 Jul 1999, Ronald G. Minnich wrote: Are you saying that as an ordinary user I can mount something on top of /tmp, for example? If the vfs.usermount sysctl is 1, and you have appropriate access to the thing you're trying to mount (block device, etc). OK, so let's say it is 1. Let's say I have "appropriate access" to /tmp. I mount my own fs on /tmp. I now have read/write access to everything anyone writes to /tmp. "Appropriate access" includes the idea that you need to own the mountpoint directory. If you have a system that's so badly run that arbitrary users own /tmp, then I'd say user mounts are the least of your problems :-) Or, let's say I don't have "appropriate access" to /tmp. Pick some other place. I mount my file system there for my files. Now everyone who wants can look for these user mounts and walk them at will. My private stuff is quite public. Correct (unless you want your private stuff to be private, and chmod your mountpoint's parent directory accordingly). But thanks for the note. I just now realized that if I add a private name space to v9fs (which is easy), and then turn on user mounts, user processes can have private name spaces on freebsd! I can't wait to see the security problems that causes when setuid executables assume that they only need to be worrying about one filesystem namespace. :-) - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Filesystem question...
Ronald G. Minnich wrote: On Fri, 23 Jul 1999, Kris Kennaway wrote: On Thu, 22 Jul 1999, Ronald G. Minnich wrote: Are you saying that as an ordinary user I can mount something on top of /tmp, for example? If the vfs.usermount sysctl is 1, and you have appropriate access to the thing you're trying to mount (block device, etc). OK, so let's say it is 1. Let's say I have appropriate access to /tmp. I mount my own fs on /tmp. I now have read/write access to everything anyone writes to /tmp. Appropriate access includes the idea that you need to own the mountpoint directory. If you have a system that's so badly run that arbitrary users own /tmp, then I'd say user mounts are the least of your problems :-) Or, let's say I don't have appropriate access to /tmp. Pick some other place. I mount my file system there for my files. Now everyone who wants can look for these user mounts and walk them at will. My private stuff is quite public. Correct (unless you want your private stuff to be private, and chmod your mountpoint's parent directory accordingly). But thanks for the note. I just now realized that if I add a private name space to v9fs (which is easy), and then turn on user mounts, user processes can have private name spaces on freebsd! I can't wait to see the security problems that causes when setuid executables assume that they only need to be worrying about one filesystem namespace. :-) - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: matcd on an SB16
Mike Smith wrote: Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone have any estimate of the amount of effort that'd be required to fix it? It works for some definitions of work. Firstly, there are three different CDROM interfaces that can be hung off an SB16; one is the Matsushita drive, there's also a Mutsumi interface (I don't think we support it) and a Sony interface (also, I believe, unsupported). Ghods, you're going through some old mail! [ and how was DEFCON, btw? :-) ] FWIW, the guy I was talking about embarked on a network install from another machine with a CD-ROM drive and an NFS server; the network install failed for slightly related reasons, having to do with the idea the hardware in this box is generally crap. The disappointing thing is that Linux works on it, though :-/ - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Swap overcommit
[EMAIL PROTECTED] wrote: The semantics of malloc() have been defined since almost the dawn of time. From the current manpage: RETURN VALUES The malloc() and calloc() functions return a pointer to the allocated memory if successful; otherwise a NULL pointer is returned. Nowhere does it say that allocated memory might not exist. Nowhere does it say that I have to touch all the allocated pages to make sure they are really there. Nowhere does it say process death at some non-deterministic time in the future might be a side effect of calling malloc(). It's just using a different definition of "successful return of malloc()" to the one you're trying to use :-) - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Swap overcommit
lyn...@orthanc.ab.ca wrote: The semantics of malloc() have been defined since almost the dawn of time. From the current manpage: RETURN VALUES The malloc() and calloc() functions return a pointer to the allocated memory if successful; otherwise a NULL pointer is returned. Nowhere does it say that allocated memory might not exist. Nowhere does it say that I have to touch all the allocated pages to make sure they are really there. Nowhere does it say process death at some non-deterministic time in the future might be a side effect of calling malloc(). It's just using a different definition of successful return of malloc() to the one you're trying to use :-) - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: (forw)
Karl Pielorz wrote: Yes, a nice, effective - and simply way of replacing syscall's on FreeBSD... Some might say a little too 'simple'? Garbage. You can do this on any OS, whether it supports loadable modules or not, if you've managed to win sufficient privileges through some other means. FreeBSD (and other OSs with loadable module support) merely provides a well-defined API which, like almost every other well- defined API, can be abused by those who harbor ill-will. Making the interface "complicated" does absolutely nothing to stop script-kiddies: Once a complicated interface is in an exploit script, who cares how arcane it is? - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (forw)
Karl Pielorz wrote: Yes, a nice, effective - and simply way of replacing syscall's on FreeBSD... Some might say a little too 'simple'? Garbage. You can do this on any OS, whether it supports loadable modules or not, if you've managed to win sufficient privileges through some other means. FreeBSD (and other OSs with loadable module support) merely provides a well-defined API which, like almost every other well- defined API, can be abused by those who harbor ill-will. Making the interface complicated does absolutely nothing to stop script-kiddies: Once a complicated interface is in an exploit script, who cares how arcane it is? - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: need a better solution as callback
Geza Fodor wrote: i have a freebsd installed with internet connection on my desktop pc and on my laptop as well. because i am traveling a lot between two countries, i'd like to make followings. You should be able to write some scripts which do this; theoretically, the "some commands to my desktop pc" bit can be an invocation of a background script which time-delays then initiates a PPP connection. - mark - laptop dials to my desktop pc - laptop sends some command - desktop hangs up and dials to local isp - laptop dials also to a local isp - desktop sends a mail to me that means it is online (sends an ip address as well) - laptop logs in is it too much? any idea? Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
matcd on an SB16
I've been following a local Linux mailing list, and a couple of the
users there have been trying FreeBSD ('cos I'm giving a presentation on
it at a Linux user group meeting next month :-)
One of them has an SB16 with a CD-ROM drive. His attempts at installing
FreeBSD from that CD-ROM have met with abysmal failure:
$ Next came an install on my Pentium 60 (previously running Caldera-2.2)
$ - A total disaster no way despite 12 attempts to install, could I
$ get FreeBSD to actually initialise the sbpcd (freebsd calls it matcdc)
$ despite changing IO's, entering the manual configuration option etc
$ etc... it would not could not, find the cdrom so I had to abort the
$ install every time!!
Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone
have any estimate of the amount of effort that'd be required to fix it?
- mark
Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone
have any estimate of the amount of effort that'd be required to fix it?
- mark
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: need a better solution as callback
Geza Fodor wrote: i have a freebsd installed with internet connection on my desktop pc and on my laptop as well. because i am traveling a lot between two countries, i'd like to make followings. You should be able to write some scripts which do this; theoretically, the some commands to my desktop pc bit can be an invocation of a background script which time-delays then initiates a PPP connection. - mark - laptop dials to my desktop pc - laptop sends some command - desktop hangs up and dials to local isp - laptop dials also to a local isp - desktop sends a mail to me that means it is online (sends an ip address as well) - laptop logs in is it too much? any idea? Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
matcd on an SB16
I've been following a local Linux mailing list, and a couple of the
users there have been trying FreeBSD ('cos I'm giving a presentation on
it at a Linux user group meeting next month :-)
One of them has an SB16 with a CD-ROM drive. His attempts at installing
FreeBSD from that CD-ROM have met with abysmal failure:
$ Next came an install on my Pentium 60 (previously running Caldera-2.2)
$ - A total disaster no way despite 12 attempts to install, could I
$ get FreeBSD to actually initialise the sbpcd (freebsd calls it matcdc)
$ despite changing IO's, entering the manual configuration option etc
$ etc... it would not could not, find the cdrom so I had to abort the
$ install every time!!
Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone
have any estimate of the amount of effort that'd be required to fix it?
- mark
Is the matcd driver known to work on FreeBSD 3.2 ? If not, does anyone
have any estimate of the amount of effort that'd be required to fix it?
- mark
Mark Newton Email: new...@internode.com.au (W)
Network Engineer Email: new...@atdot.dotat.org (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
Network Man - Anagram of Mark Newton Mobile: +61-416-202-223
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: Microsoft performance (was: ...)
Karl Denninger wrote: I've found FreeBSD to outperform NT-anything in any task you throw at the machine from web service to Samba for file and print service for PCs running Windows. Granted. Perhaps we're seeing an artifact of NT's developers focussing on optimizing their system for good benchmark performance rather than good real-world performance. 'twill be interesting to see the offical report to find out where the various strengths and weaknesses really are. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: All this and documentation too? (was: cvs commit: src/sys/isa sio.c)
Hellmuth Michaelis wrote: And as to the author: Writing docu while you are implementing something might work in a commercial environment where you want to be able to market something before it's sell-by date, but for hobbiests who basically spend the odd evening doing something, it is too much hassle. In case FreeBSD wants to enter commercial environments, we have to behave like behaving in commercial environments. Ok, so let's follow Microsoft's industry-leading documentation standards. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
Greg Lehey wrote: Those of you who were at Usenix may have picked up a free copy of a UnixWare 7 CD-ROM from SCO. If so, be careful when installing it. SCO has been a real pain in the bum about partition tables for as long as I can remember. Don't even try installing it anywhere other than on your normal boot disk either. I've never had any luck getting SCO OpenServer onto a secondary disk of any kind. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Beware of UnixWare 7
Greg Lehey wrote: On Friday, 18 June 1999 at 18:44:50 +0930, Mark Newton wrote: SCO has been a real pain in the bum about partition tables for as long as I can remember. To be fair, this is UnixWare You mean UnixSwear, don't you? :-) - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [Call for review] init(8): new feature
Arun Sharma wrote: While we're on the init topic, is there any strong feeling here about BSD /etc/rc* scripts Vs SysV ? The nice thing about SysV initscripts is the ability to start and stop any service that I like. That's fine -- there are lots of ways to start and stop any service you like without involving SysV init. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [Call for review] init(8): new feature
Arun Sharma wrote: Mark Newton new...@internode.com.au writes: Arun Sharma wrote: While we're on the init topic, is there any strong feeling here about BSD /etc/rc* scripts Vs SysV ? The nice thing about SysV initscripts is the ability to start and stop any service that I like. That's fine -- there are lots of ways to start and stop any service you like without involving SysV init. Like sending a signal to the process providing the service ? The problem with that approach is, the signal you send and the clean up you do is non-standard for each service and having a standard interface: There are lots of ways to start and stop any service you like without relying on sending a signal to a process and without involving SysV init. This topic has been canvassed so many times by so many people that I can only suggest that you run off to the archives and read about it there. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [Call for review] init(8): new feature
Wayne Cuddy wrote: They SysV way is more elegant and less error prone for bad typist. ... and has absolutely no way of encoding interdependencies between services (or any concept of a service at all, other than as after-the-fact hacks). What happens to your NFS services when you do /etc/init.d/inetsvc stop; /etc/init.d/inetsvc start on a Sun? What *should* happen on a notebook computer when you start it without its pccard ethernet device plugged in? Should certain network services not be started at all, or should they be delayed until after PPP comes up? Isn't that a question that can only be answered by the individual service? (like, DHCP wouldn't need to start at all when PPP comes up, but your web server might need to be restarted to listen to a new IP address). Graphical tools can be used to interface with these quite easily. ... also true for any other well-designed interface. It also also easy to automate installations via installation mechanisms. Also true for any other well-designed interface. SysV's mechanism is not a well-designed interface. Sure, it has its strengths, and it makes certain tasks easy, but it's not the only answer that has strengths and simplicity. I don't think I agree that it is a bad idea because it is associated with SysV... Neither do I; that issue hasn't been broached in this discussion to date. I think it's a bad idea because it's an intrinsically bad idea. It seems to me that every time this issue comes up people say, We need something better than rc.local/rc.conf for boot-time configuration. SysV has certain attributes we don't have; so let's use SysV! It's like the politician's mantra: SOMETHING must be done! This random solution counts as `something', so let's implement this random solution. Let's not. Several people have given this matter serious thought and have come up with some excellent ideas, some of which have been implmenented as a test platform. Again I'd suggest that anyone interested in following this up consults the archives first, because the last thing we need is to have the mailing lists rehash the same ground *again* less than three months after the last time we rehashed it. [ a note to whoever it is that's replying to this message: you will no doubt delete this text in your reply, because it's stressing that you should CONSULT THE ARCHIVES. have you consulted them? if not, please, please, please exit your editor without saving your response, and consult them. thank you for your cooperation. normal service will resume shortly. ] - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: allocate file blocks contiguously
Zhihui Zhang wrote: My feeling is that if we allocate ALL the data blocks of a big file contiguously, this will lead to too much localization as described in the paper (or the book). However, this may be good for this big file if the system buffering capability and hardware allow it (at the cost of other files?) Maybe this is something we could get if XFS is ported: XFS's guaranteed rate I/O (partly) works by putting guaranteed-rate files on distinct positions on the disk, or different subvolumes in the case of GRIO on XLV logical volumes. So when preparing a filesystem you could build a logical volume out of twenty 9 Gbyte disks plus another five 9 Gbyte disks for guaranteed-rate files. [ in practice you'd probably be building such a filesystem for a specific application, though, so you'd probably really use 25 9 Gbyte disks for GRIO :-) ] You decide which subvolume a file is allocated to immediately after file creation: There's an ioctl() which can be used before the first write to a new file which sets the please make me fast flag. One thing that helps to make this possible is an I/O scheduler which supports prioritization. Hmm... - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: a two-level port system?
Alexander Langer wrote: Thus spake Mark Newton (new...@internode.com.au): but for most people who just want to build a handful of ports, browse the tree to see if there's anything cool they want, and then forget the ports tree 'til the next upgrade, it'll cut How do you want to find out if the port fits your needs without a DESCR file? /usr/ports/INDEX ? - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: a two-level port system?
Alexander Langer wrote: Thus spake Mark Newton (new...@internode.com.au): DESCR file? /usr/ports/INDEX ? Isn't the DESCR much more detailed than this INDEX file? (compare mail/mutt/pkg/DESCR and the INDEX file) Use INDEX to work out whether the package *might* be appropriate, and use something like make buildenv to grab the DESCR file (and everything else) if you think it's useful to do so. I think most novices probably don't even know the DESCR file exists anyway. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: a two-level port system?
Andrew Kenneth Milton wrote: How about optionally tarring the 'files' and 'patches' subdirs (into seperate tarfiles or as one tarfile) to be extracted when the port is needed. This would make cvsupping ports 'harder' I would imagine, although not impossible, given the .uu files I've seen for /compat stuff recently. More blue-sky stuff, but perhaps this one is easier to maintain on a long-term basis... We currently have /usr/ports/distfiles as a catch-all for, well, the distfiles. There's also /usr/ports/Mk for the makefile stubs. As such, they're a special cases, treated differently from all the other subdirs of /usr/ports. I propose another one, called something like /usr/ports/buildenv (for Build Environment). /usr/ports/buildenv would contain everything that the non-special-case /usr/ports directories currently contain, except the Makefiles. They'd continue to live in their present location. The way it'd work in real life is like this: In order to build a port you'd need /usr/ports/Mk and the subdirectory for the port you want to build (and its prerequisites); Type make install in /usr/ports/category/application as per usual. The bsd.ports.mk file would begin by checking for the existence of /usr/ports/buildenv/category/application. If it doesn't exist, go looking for it in /cdrom, or on ftp.freebsd.org. If it does exist, copy its contents into /usr/ports/category/application and continue the build in exactly the same way we do it today. The advantage of this approach is that you don't need to truck patches, package DESCR files, etc along with the ports tree distributed to end-users: All you need is a tree full of makefiles, everything else is grabbed on-demand. You still have the option of putting the whole damn thing on your system if you want, but for most people who just want to build a handful of ports, browse the tree to see if there's anything cool they want, and then forget the ports tree 'til the next upgrade, it'll cut down considerably on overhead. It'll cut down on the number of subdirectories in the ports tree by 66% at least. Ok, fire away -- tell me why it'll never work :-) - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: a two-level port system?
Mark Newton wrote: /usr/ports/buildenv would contain everything that the non-special-case /usr/ports directories currently contain, except the Makefiles. They'd continue to live in their present location. I thought of another advantage of this approach: You can upgrade existing ports on your system (but not add new ones) by doing an rm -rf /usr/ports/buildenv. Next time you build a port the latest version of the build environment, supplementary makefiles, patches, distfile locations, etc can be sucked over from ftp.freebsd.org - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Kernel config script
David Scheidt wrote: Linux is for people that hate Microsoft. FreeBSD is for people who love Unix. I like Linux is Luke Skywalker; FreeBSD is Yoda. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Source code of SGI XFS
Pavel Narozhniy wrote: Does anybody heard about SGI releasing XFS source code? Yup, they're doing it. I would guess that FreeBSD would need a fairly thorough revamp of its handling of kernel memory allocation before XFS would be fully usable, though: XFS buffer management is pretty full-on. The filesystem maintains its own pool of kernel buffers separate from the VM page cache which it uses for aggregating I/O transfers (so that if, say, you make 5 separate out-of-order I/Os which just happen to blanket a contiguous region of a disk object, XFS will collapse them into a single I/O; it'll also take small contiguous regions (extents) and remap them into the next-power-of-two extent size as they grow. I know I could probably see by looking at the source, but does FreeBSD still impose a 64k limit on physical I/O operations? That'll have to go too... - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 Network Man - Anagram of Mark Newton Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
