DOS-style Console Type for IPMI remote console
Hi! I've got a nifty new server board with an IPMI card. The console-redirection over LAN is supposed to work for anything that uses DOS-style video modes or characters, i.e. no graphics mode. In fact it works for the BIOS/boot*/loader and first kernel messages up to the point where the Timecounter i8254 frequency 1193182 Hz quality 0 line is printed out. Then the management software tells me that the system entered graphics mode, which it can't forward. Now, does anybode have an idea how to tell FreeBSD not to switch any graphics mode, i.e. keep that stupid plain printout of characters as the loader does? I would be very nice to do single-user mode installs that way. I've tried sc/vga with various options, but they don't help, I can't get further as the above timecounter line (I assume that's when the vga driver registers and tries to detect the vga). I'm currently using these options: options VGA_NO_FONT_LOADING # don't save/load font options VGA_NO_MODE_CHANGE # don't change video modes options VGA_SLOW_IOACCESS options SC_NO_FONT_LOADING none of them helps. When using pcvt, the boot messages scroll a bit futher, including the avail memory messages, but then stop, with the same message about graphics mode as above. Any workarounds? Anybody using IPMI console redirection over LAN and had success? Thanks Ciao Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
loader tunables for modules
Hi! How would one give flags to kernel modules? I.e. a kernel module I wrote starts a kernel thread. It should be controlable what kernel thread it starts depending on a sysctl. Of course the sysctl isn't available before the module is loaded. So is there a way to pass a kernel module options to the load-handler, as it is the case for the linux modprobe? For statically drivers in the kernel this can be done by a r/o loader tunable, but I really want to have a module. Thanks for any pointers Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader tunables for modules
Also sprach Lara Harti Brandt ([EMAIL PROTECTED]): It turns out that kenv is just handy for this. I use it to pass debugging information and configuration info to the ATM drivers. And you can set kenv entries from the loader and the shell. Great, exactly what I was looking for. Thanks a lot. Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
mysql endless loops
Hi! A known bug with MySQL 3.x is that it sometimes enters a 100% cpu usage loop if you stress it too much (I can repeat this every 2-3 weeks). I just attached a ktrace, and it shows this: 57486 mysqld CALL poll(0x8382000,0x4,0xb8c) 57486 mysqld RET poll 1 57486 mysqld CALL gettimeofday(0x283fddec,0) 57486 mysqld RET gettimeofday 0 57486 mysqld CALL poll(0x8382000,0x4,0xb8c) 57486 mysqld RET poll 1 57486 mysqld CALL gettimeofday(0x283fddec,0) 57486 mysqld RET gettimeofday 0 57486 mysqld CALL poll(0x8382000,0x4,0xb8c) 57486 mysqld RET poll 1 57486 mysqld CALL gettimeofday(0x283fddec,0) 57486 mysqld RET gettimeofday 0 57486 mysqld CALL poll(0x8382000,0x4,0xb8c) 57486 mysqld RET poll 1 57486 mysqld CALL gettimeofday(0x283fddec,0) 57486 mysqld RET gettimeofday 0 57486 mysqld CALL poll(0x8382000,0x4,0xb8c) 57486 mysqld RET poll 1 57486 mysqld CALL gettimeofday(0x283fddec,0) 57486 mysqld RET gettimeofday 0 57486 mysqld CALL poll(0x8382000,0x4,0xb8c) 57486 mysqld RET poll 1 57486 mysqld CALL gettimeofday(0x283fddec,0) 57486 mysqld RET gettimeofday 0 57486 mysqld CALL poll(0x8382000,0x4,0xb8c) 57486 mysqld RET poll 1 57486 mysqld CALL gettimeofday(0x283fddec,0) 57486 mysqld RET gettimeofday 0 57486 mysqld CALL poll(0x8382000,0x4,0xb8c) 57486 mysqld RET poll 1 57486 mysqld CALL gettimeofday(0x283fddec,0) 57486 mysqld RET gettimeofday 0 57486 mysqld CALL poll(0x8382000,0x4,0xb8c) 57486 mysqld RET poll 1 57486 mysqld CALL gettimeofday(0x283fddec,0) 57486 mysqld RET gettimeofday 0 57486 mysqld CALL poll(0x8382000,0x4,0xb8c) 57486 mysqld RET poll 1 ... (approx. 80 MB of these lines, then I killed the process). It seem the thread handling is broken for mysql (this gettimeofday happens in the while (select_thread_in_use) in mysqld.cc I believe. Anyways, I'm going to try mysql 4.0 now, maybe someone can use the information above. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: panic: icmp_error: bad length
JFYI, the patch Ian recently MFCed does fix the problem here on our 4.7 box. Thanks Ian :-) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: ecc on i386
Thus spake Peter Wemm ([EMAIL PROTECTED]): Our NMI / ECC handling really really sucks in FreeBSD. Consider: [...] Is there any effort to fix this stuff? Considering FreeBSD is still known as one of the best server platforms, this is more important than a multi-threaded kernel or similar stuff, IMO. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Version of XFree86 in FreeBSD Release 4.4
Thus spake Robert Withrow ([EMAIL PROTECTED]): I know it is slimy, but couldn't there be a dummy port just called XFree86 that is what most other ports depend on? The minority of ports that actually care what version of X is installed could always use the version-specific names... Would be nice if we had a package system that lets you just install - let me call them - features, such as a XFree86 feature, other ports could depend on. Multiple packages could supply this feature then and ports could also say if they depend on a specific version. Alex, hiding in a dark corner. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Version of XFree86 in FreeBSD Release 4.4
Thus spake Rasputin ([EMAIL PROTECTED]): Isn't this what XFREE86_VERSION does? Nope, this is a build-time option. I can't remember a commit to the pkg tools that check for XFREE86_VERSION. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Version of XFree86 in FreeBSD Release 4.4
Thus spake Daniel O'Connor ([EMAIL PROTECTED]): Yes, I suspect the answer is along the lines of 'yes that's coming' :) :-) The previous suggestion (have a generic XFree86 port) is a) hacky, but b) workable in the current package framework I suspect.. Yes, would be a nice workaround. I don't use packages, though :) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: local changes to CVS tree
Also sprach Bernd Walter ([EMAIL PROTECTED]): How do people fix stuff in their local CVS tree and sync other FreeBSD changes with that? It's a CVSup FAQ: http://www.polstra.com/projects/freeware/CVSup/faq.html#canilocal Great, thanks. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
local changes to CVS tree
Thus spake Kris Kennaway ([EMAIL PROTECTED]): On Wed, Sep 05, 2001 at 09:52:34AM +0300, Giorgos Keramidas wrote: I have it fixed now in my local CVS tree. Hopefully Kris will commit something to fix it soon :-) I'm just curious: How do people fix stuff in their local CVS tree and sync other FreeBSD changes with that? I mean I have much stuff, which gets M file in the next cvs update, but I'd really like to cvs commit them to my local /home/ncvs, but cvsup will overwrite these changes. Thanks Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: local changes to CVS tree
Thus spake Peter Pentchev ([EMAIL PROTECTED]): One way that (I think it was) Sheldon pointed out to me a few months ago would be keeping your own CVS repository and vendor-importing the FreeBSD source on a regular basis. The regular vendor-import is quite time-consuming though :( That sucks. From what I've heart about the Sparc64 development on freefall, perforce seems to be able to do such stuff automatically, right? Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: NETBIOS Browsing?
Thus spake Conrad Minshall ([EMAIL PROTECTED]): Does anyone know of any code which would help in browsing a Windows Network Neighbourhood? Something which would make broadcasts to find all the netbios name servers, and then query them to discover more. Code from Samba's nmblookup would be fine but it is GPL. xsmbrowser is a GREAT tools, which is even better than Microsofts Network Neighbourhood. I use it to browser our LAN with 200+ PCs and it's very comfortable (and has less bugs than M$' crap) You can find it in the ports collection. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: NETBIOS Browsing?
Ouch, I should actually read more carefully what you were asking, sorry. I guess smbfs doesn't help you here (don't know if it actually browses, but at least it's SMB stuff) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: PANIC - 4.3-STABLE, suspecting ata controller
Thus spake Bill Moran ([EMAIL PROTECTED]): http://www.prioritydesigns.com/crashdata/ contains the files. I've put a dmesg.out (obvious) as well as the kernel.0, vmcore.0 and kernel.debug there, if anyone would like to run it through gdb themselves (***WARNING*** vmcore.0 is 128M) (NOTE, the web server does not allow directory listings, you'll have to access the files directly) So ... I'm looking for any possible help in straightening this out. Advice on how to run gdb more effectively is welcome, as well as anyone Hi! In the handbook there is a chapter about how to debug kernels. If you correctly load the symbols-file (kernel.debug), you should be able to backtrace and the code resulting the panic occurs (usually *g*). That's a good start to paste here. Thanks Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: [PATCH] Limited BPF to the specified program
The options should be a sysctl, since dhclient might move from inode to inode and I don't want to recompile a kernel everytime. Also, that should be a list of filesystem:inode pairs, imho, for multiple programs. OTOH, I don't know if that makes sense, since superuser still can compile a new kernel or set the sysctl. Sounds like a neat idea if it actually works, though. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: newbussifying drivers
Thus spake j mckitrick ([EMAIL PROTECTED]):
| It's pretty rare to need to bit-bang to find a device these days anyway;
| you should probably be looking for PnP data or similar. This is what
| hints are (basically) - manually-supplied PnP data.
How would you recommending fixing this, taken from the ex driver?
for (ioport = 0x200; ioport 0x3a0; ioport += 0x10) {
This is exactly what Mike meant:
You manually set the correct I/O port in the hints file and then you
don't have to check for each port between 0x200 and 0x3a0.
Just bus_alloc_resource once and test for the card.
Alex
--
cat: /home/alex/.sig: No such file or directory
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: general speed differences between 4.1.1-RELEASE and 4.3-RELEASE
Thus spake Ed Hudson ([EMAIL PROTECTED]): for my money, hw.ata.wc=1 soft updates OFF is a better performing choice than hw.ata.wc=0 and soft updates ON. (soft updates are great, but i really dislike the performance stalls that it (or async mode) engenders with big copies/etc for other processes). Well, that must be decided on situtation by situation. Most people read a much bigger amount of data than they actually write, and the small amount of data they write is then (almost!) guaranteed to be consistent. For webservers, were only few changes to the static pages are made, this mode is the correct behaviour, for newsservers it's probably not. The way it's done at the moment is ok, IMO. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: softc with resource sharing
Thus spake j mckitrick ([EMAIL PROTECTED]): Any devices using the ppbus will end up sharing the hardware port. If i want to access this resource info, should i store it in my local driver's softc structure, or extract it from the parent device (ppbus)? What about bus_alloc_resource()? Or is ppbus special? (Not that I know of). Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Device driver questions
Thus spake SJ ([EMAIL PROTECTED]): Hi! 1. ioconf.c contains struct config_resource and config_device definitions for declarations in config file. But I noticed that for some devices e.g. device atadisk device atapicd ... the corresponding lines in ioconf.c are missing?? I think it's because ata is a self-identifying bus. Not sure, though. Are any PCI-only devices listed? 3. File naming question: whats the reasoning behind having bus.h and bus_private.hwhats the significance of private here. drivers include bus.h, kernel does also include bus_private.h 4. concept behind having devclasses...I know that devclasses for a particular bus holds devices and device drivers for that bus. But then whats the need for defining a devclass for each driver we write ? Because you can hold multpiple devices that are enumerated, e.g. xl0, xl1, ... The devclass is unique for each driver, but not for different busses. You can have ed0 on ISA and ed1 on PCI for example, using the same devclass. If ISA and PCI subdrivers are using a different devclass, the enumeration breaks. 5. Any poniters to literature which explains the design philosophy and code specific help for device drivers in freebsd - I am referring to files kern/subr_bus.c, bus.h, bus_private.h, isa/* etc. Use the source, luke :-) Seriously, subr_bus.c is quite nice to read if you read it togethers with, say, sys/pci/pci.c. That makes the concept quite clear. The developer's handbook might be worth reading for you, also there are some tutorials on the website which explain a little. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: removing inb()/outb() from devices
Thus spake j mckitrick ([EMAIL PROTECTED]): I'd like to finalize the newbus work by changing inb()/outb() calls to bus_space_write calls. Is there a device where this has been partially done already? I'd like to see the old and new styles, then i would fix the It has been done to sys/dev/ed/ about half a year ago. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com]
Thus spake Matt Dillon ([EMAIL PROTECTED]): Helicopter? Pah! I know for a fact that Jordan was bribed with a brand spanking new hovermobile by the afformentioned aliens! (which, oddly enough looks somewhat like a DeLorean with a MrCoffee bolted to the back, hrm). I always thought sheep drive Vespas. :) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: device driver dev. book
Thus spake Leif Neland ([EMAIL PROTECTED]): Just to get the facts clear: Do you ever intend to write a book? A "Developers Handbook", which will also cover device driver and kernel module programming is in work under the leadership of Jeroen Ruigrok van der Werven [EMAIL PROTECTED]. Once it has more content I can imagine a print version of this. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: device driver dev. book
Thus spake Jerry Toung ([EMAIL PROTECTED]): Does anyone of you know about a book that would deal specifically with FreeBSD device drivers dev.? If yes let me know. Not books, but there are some tutorials/manpages available. See: http://www.FreeBSD.org/tutorials/ and section 9 of the manual pages. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: good book or other source about socket programming
Thus spake Marco van de Voort ([EMAIL PROTECTED]): I'm searching for a good book (or site/tutorial) about Unix socket programming, preferably FreeBSD specific. Socket programming shouldn't be FreeBSD specific. Unix Network Programming Vol.1 by W. Richard Stevens is a good choice. After that you probably want to read some kqueue documents, which is FreeBSD specific, but shall be quite fast (faster than select/poll) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: good book or other source about socket programming
Thus spake Brian Reichert ([EMAIL PROTECTED]): Other than the manpage, what documents about kqueue are there? I read this: http://www.flugsvamp.com/~jlemon/fbsd/internals.txt http://people.freebsd.org/~jlemon/ has a slideshow on kqueue. http://www.flugsvamp.com/~jlemon/fbsd/ has also some small examples. I also once had a simple kqueue echo server, but I deleted it :-) You can probably find its location in the mailing list archives. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: An example script for creating a bootable floppy
Thus spake Dan Langille ([EMAIL PROTECTED]): I get a root mount failed, then a panic, but at least it's a kernel. If I make any more progress, I'll le you know. Did you strip it? I have way smaller kernels here, which have much more options. Btw: Just gzip the file and call it /kernel.gz on the floppy, the loader can handle this. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel programming
Thus spake Yonny Cardenas B. ([EMAIL PROTECTED]): Is there anybody knows some reference (URL), tools or some help to programming and debugging in the kernel FreeBSD? Try http://www.freebsd.org/tutorials/ Andrew W. Reiter has written a nice kernel mod tutorial. There recently (last week or something) was a thread here or on another mailinglist on how to debug kernel moduls, which is a little bit tricky. Just search the archives. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel programming
Thus spake Dag-Erling Smorgrav ([EMAIL PROTECTED]): There recently (last week or something) was a thread here or on another mailinglist on how to debug kernel moduls, which is a little bit tricky. It's also documented in the handbook. Well, actually debugging modules is a little bit more tricky than debugging kernels with statically linked drivers. This is what I meant. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
What must be provided by an init for ncurses?
Hello!
Libh uses TVision which uses ncurses.
I have written a *simple* init which opens /dev/ttyv0.
printf() and alikes work, but ncurses does not ("Error opening
terminal").
I wonder if anyoen can tell me what my simple init must provide as
well to make ncurses running.
I have a /etc/termcap installed as well, but this is not enough.
Any hints?
Thanks
Alex
--
cat: /home/alex/.sig: No such file or directory
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
(fwd) libh disk editor
Hi! I'm forwarding this here for those of you who might have missed it on cvs-all/committers. This is libh's version of the disk-editor. Note that it is alpha-software, so be careful with use. Some dialogs (e.g. the "About"-dialog) just don't work, but you will notice this. At least, it is a nice example of what libh is able to do. - Forwarded message from Alexander Langer [EMAIL PROTECTED] ----- From: Alexander Langer [EMAIL PROTECTED] Subject: libh disk editor To: Dag-Erling Smorgrav [EMAIL PROTECTED] Cc: Alfred Perlstein [EMAIL PROTECTED], Valentin Nechayev [EMAIL PROTECTED], John Baldwin [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Sat, 20 Jan 2001 00:03:26 +0100 Thus spake Dag-Erling Smorgrav ([EMAIL PROTECTED]): I didn't try to edit a disk with it (because I lack a test-disk), but I might try. Hey, I have disks. How do I obtain / build the code? Ok. I've statically linked a tcl interpreter with the libs. Note: -current's Disk_Names() from libdisk finds only ad0 here, though I have ad0 and ad2, so this is not a bug of libh :-) The files are on http://people.freebsd.org/~alex/libh/tclh.static.gz http://people.freebsd.org/~alex/libh/disk.tcl I'm actually rewriting disk.tcl, since some stuff in the User-Interface API changed. Alex -- cat: /home/alex/.sig: No such file or directory - End forwarded message - -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: stupid CVS question
Thus spake Peter Pentchev ([EMAIL PROTECTED]): Never mind, I found the -N option by reading the source. Why oh why is it not documented in the CVS info page :( document it :-) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How to make a PCI network device loadable module?
Thus spake Daniel O'Connor ([EMAIL PROTECTED]): I don't think you need anything special for your device to be a KLD.. I maintain a simple character device which didn't need anything special, but network devices may be different. Most of the drivers in the tree either exist as module already or need only little patches to work as module. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: syslogd patch
Thus spake Eric Melville ([EMAIL PROTECTED]):
Should I send-pr this thing too, or is just sending it to -hackers enough?
To -audit, in general.
if (flags ISKERNEL) {
- snprintf(buf, sizeof(buf), "%s: %s", bootfile, msg);
+ /* ignore path to kernel */
+ bflen = strlen(bootfile);
+ bfshort = bootfile;
+ while(bflen--)
+ if(*(bootfile+bflen) == '/')
+ {
+ bfshort = bootfile+bflen+1;
+ break;
+ }
+ snprintf(buf, sizeof(buf), "%s: %s", bfshort, msg);
Why don't you just use basename(3)?
Alex
--
cat: /home/alex/.sig: No such file or directory
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: sys/disklabel.h in C++ files
Thus spake Warner Losh ([EMAIL PROTECTED]): No need for Hope to Spring. As near as I can tell, I've fixed it. Yes, thanks. Now the disk-library of libh builds again. Thanks! Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
sys/disklabel.h in C++ files
Hi!
I have a question:
How do you include sys/disklabel.h in C++ files?
alex:~ $ cat test.cc
#include sys/disklabel.h
alex:~ $ cat test2.cc
extern "C" {
#include sys/disklabel.h
}
alex:~ $ make test.o
c++ -O -pipe -c test.cc
In file included from test.cc:1:
/usr/include/sys/disklabel.h:182: `lp' was not declared in this scope
/usr/include/sys/disklabel.h:183: syntax error before `*'
*** Error code 1
Stop in /usr/home/alex.
alex:~ $ make test2.o
c++ -O -pipe -c test2.cc
In file included from test2.cc:2:
/usr/include/sys/disklabel.h:182: `lp' was not declared in this scope
/usr/include/sys/disklabel.h:183: syntax error before `*'
/usr/include/sys/disklabel.h:188: `lp' was not declared in this scope
/usr/include/sys/disklabel.h:189: `lp' was not declared in this scope
/usr/include/sys/disklabel.h:189: `lp' was not declared in this scope
/usr/include/sys/disklabel.h:190: syntax error before `while'
*** Error code 1
Stop in /usr/home/alex.
alex:~ $
Is there a gcc option?
Or does this just not work?
I mean, it worked before PHK made dkcksum() an __inline function.
Thanks
Alex
--
cat: /home/alex/.sig: No such file or directory
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Silent FreeBSD
Thus spake Renaud Waldura ([EMAIL PROTECTED]): I've got that FreeBSD gateway in a corner at my house, it works fine dandy but the constant noise (whirring fans, hard drives) gets on my nerves. What solutions have people explored to quiet down a computer system? (actual experience will be preferred over wild speculations). I'm already aware of PicoBSD, but I need more storage than just a floppy. Has anybody experimented with RAM cards? How about noise-proof enclosures? A friend of mine has a Dual PII 400 box in the cellar which is his workstation. Then he has bought a K6-2 500 and is using it at 200 MHz, so it doesn't need a fan. The power supply fan is silent enough. Since this K6-2 box netboots and mounts his root via Full-Duplex Fast-Ethernet from the Workstation, where all processes are started as well, he has a silent, but fast workstation. And, btw, he is watching TV via fxtv over the network w/o any problems (AND can work in the meanwhile) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
kvtop() on alpha question
Hello! I have a question: How can the if_ed driver work on FreeBSD/Alpha, if it uses kvtop(), but kvtop() is only defined in sys/i386/i386/vm_machdep.c? I'm very confused, and I wonder if someone can enlighten me, please. Thanks Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: int80h.org
Thus spake G. Adam Stanislav ([EMAIL PROTECTED]): swap space and memory even on a tiny little file. I have 8 Meg of RAM and successfully run Photoshop, CorelDraw and other huge programs. Yet, a simple file conversion program runs out of memory? Besides, it claims CHAPTER is not permitted in a book. Weird. Maybe something is wrong and creates an infinite loop in the jade program. Would you share the .sgml file with us? We maybe could also solve the problem why CHAPTER isn't allowed. Thanks IA Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Need some help developing my ethernet driver.
Thus spake Rink Springer ([EMAIL PROTECTED]): One final problem here now... how can I determine which I/O address FreeBSD is willing me to probe for the device? I cannot find it in any of the existing drivers... anyone? This is done automatically. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD 4.x/3.x kld device driver
Thus spake Willem van Engen ([EMAIL PROTECTED]): I'd also like to use it on FreeBSD 3.x. When compiling gigadrive there, the file device_if.h can't be found. Any ideas to solve this? This is code that is only working in FreeBSD 4.0 or greater. You really should update if you develop drivers. It's also much easier with the new driver-interface in 4.0 and above. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [book] how compatible are FreeBSD and Advanced Programming in the UNIX ...?
Thus spake John Lispton ([EMAIL PROTECTED]): programming described in the book? Or can I rest assured that the book contents apply well to FreeBSD? Yes, the book explains everything on 4.3BSD, so everything applies to FreeBSD as well. Of course, FreeBSD (and the other BSD's, too) have had some improvements on various points in the meanwhile. However, since Stevens covers most things related to the Posix and other standards, you can expect everything in the book to work. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How to make *real* random bits.
Thus spake Poul-Henning Kamp ([EMAIL PROTECTED]): between events. Because of this your T3 value can be considered the T1 value for the next random bit you generate. No it cannot. If you did that then the probability would skew from bit to bit. If the (t3-t2) was large bit N == 1 and the probability of bit N+1 == 0 is .5 then. Yes, but you can use the 3rd bit as bit 1 for the next step. With 15 events, that gives 7 bits/second: bit 1: 3 1 (is event 3 of the last bit) bit 2: 2 1st bit 3: 3 1 bit 4: 2 2nd bit 5: 3 1 bit 6: 2 3rd bit 7: 3 1 bit 8: 2 4th bit 9: 3 1 bit 10: 2 5th bit 11: 3 1 bit 12: 2 6th bit 13: 3 1 bit 14: 2 7th bit 15: 3 1 (is event 1 for the next bit) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
type of _BSD_TIME_T_ in machine/ansi.h
Hello!
Currently, I see the following:
root@parca /sys $ grep _BSD_TIME_T {alpha,i386}/include/ansi.h
alpha/include/ansi.h:#define_BSD_TIME_T_int /* time() */
i386/include/ansi.h:#define _BSD_TIME_T_long /* time()... */
I wonder if we want to change that to __int32_t in both files?
Additionally, I have the following patch, which is needed
at the moment to suppress warnings (on alpha):
Index: kern_shutdown.c
===
RCS file: /usr/home/ncvs/src/sys/kern/kern_shutdown.c,v
retrieving revision 1.76
diff -u -r1.76 kern_shutdown.c
--- kern_shutdown.c 2000/07/04 11:25:22 1.76
+++ kern_shutdown.c 2000/07/23 18:20:22
@@ -175,21 +175,37 @@
printf("Uptime: ");
f = 0;
if (ts.tv_sec = 86400) {
+#ifdef __alpha__
+ printf("%dd", ts.tv_sec / 86400);
+#else
printf("%ldd", ts.tv_sec / 86400);
+#endif
ts.tv_sec %= 86400;
f = 1;
}
if (f || ts.tv_sec = 3600) {
+#ifdef __alpha__
+ printf("%dh", ts.tv_sec / 3600);
+#else
printf("%ldh", ts.tv_sec / 3600);
+#endif
ts.tv_sec %= 3600;
f = 1;
}
if (f || ts.tv_sec = 60) {
+#ifdef __alpha__
+ printf("%dm", ts.tv_sec / 60);
+#else
printf("%ldm", ts.tv_sec / 60);
+#endif
ts.tv_sec %= 60;
f = 1;
}
+#ifdef __alpha__
+ printf("%ds\n", ts.tv_sec);
+#else
printf("%lds\n", ts.tv_sec);
+#endif
}
/*
--
cat: /home/alex/.sig: No such file or directory
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: /etc/security - /etc/periodic/security ?
Thus spake James Howard ([EMAIL PROTECTED]): fairings? Why does it matter what color the bikeshed is? What does What is this thing with the bikesheds??? It appears on every place I am, on IRC, now here. As a non-native English-speaker, I'd like to know what's up with the poor bikesheds. The poor ones :-( Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption)
Thus spake Bill Fumerola ([EMAIL PROTECTED]): PS. No, it's not something stupid like file flags or something. No, it was something even stupider. Completely ignore this. Oh, come on now, tell us the details! :-) It involves this running in another window: [hawk-billf] $ while `true`; do make clean; sleep 5; make; sleep 5; done BWAHAAHAHAAHAH! coool :-) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
removal of kvtop() on i386
Hello! I recently wanted to port the if_ed driver to alpha. FreeBSD/alpha still misses kvtop(), so I implemented it. However, bde told me, that the whole function kvtop() is wrong, since "0" is a legitimate physical address and therefore the panic is misplaced. That means, kvtop() is obsolete. Before I continue porting the driver, I'd like to have this issue resolved. Please take a look at this (kinda old) patch: - Remove pmap_kextract from pmap.h for alpha and add it to pmap.c - remove pmap_kextract from vm_machdep.c for i386 and add it to pmap.c - change all kvtop() to pmap_kextract() in the src. http://people.freebsd.org/~alex/remove-kvtop.diff I received no further comments about this patch from bde, and dillon didn't answer to an email concerning this. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: why isnt there a ext2fs.ko ?
Thus spake James Howard ([EMAIL PROTECTED]): day or so and I will update it work with a newer FreeBSD. On this topic, how would anyone feel about importing NetBSD's GPL-clean ext2fs source? Cool! Is it stable? What is better than w/ our ext2fs stuff? Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Documentation selection in sysinstall
Thus spake Jordan K. Hubbard ([EMAIL PROTECTED]): What happened to the plans to move to the TurboVision library? We're still working on it. Yes, someone should encourage John Baldwin to fix that. For example by promising some cakes or something :) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anybody working on FreeBSD BIOS?
Thus spake Stefan Molnar ([EMAIL PROTECTED]): is already supported. ( On some high end machines serial console works in the prom as well). Also on low-end machines... Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NVIDIA Drivers for XF4
Thus spake Trent Nelson ([EMAIL PROTECTED]): What's porting going to involve? I can't see porting the kernel module being *too* difficult (I'd love to start on something after exams) - but I don't know how the Linux object files for the XFree86 interface are going to be dealt with (Linux developer port?). If I understood dfr correctly (I've not taken a look at this yet), the new AGP driver in -current does similar things and works for two chipsets already (can't recall which, read cvs-all). However, porting the nvidia driver shouldn't be the problem. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
sigaction.2 manpage: mcontext_t or ucontext_t?
Hello! docs/17863 claims: The description of the third argument to signal handlers if SA_SIGINFO is supplied is wrong. It's a ucontext_t, not an mcontext_t. It wants to change: The context argument to a POSIX SA_SIGINFO handler points to an - instance of mcontext_t. to The context argument to a POSIX SA_SIGINFO handler points to an + instance of ucontext_t. I myself think - from reading source - that this is true, but I'm not quite sure. I want someone who has clue to verify this :) Thanks in advance! Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: review request: truncate(1)
Thus spake Johan Karlsson ([EMAIL PROTECTED]): However, the man page does not mention that one have to also specify the wanted size of the file. Oooops :-) *correcting* Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Unexpected reboot.
This to make the memory settings more conservative. I had that too earlier, and after I changed that the machine became much more stable: 5:01pm up 62 days, 20:10, 4 users, load averages: 2.31, 2.12, 1.86 (nfs-buildworld/ports server) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: review request: truncate(1)
Thus spake Johan Karlsson ([EMAIL PROTECTED]): Please sort the options in getopt and in the switch-statement. see style(9) for more style info. Please also use -Wall when compiling to catch all warnings True - forget about that. What about the other things, I mean non-stylistic but functional/technical stuff? Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: newbus code
Thus spake J McKitrick ([EMAIL PROTECTED]): Is there a document anywhere that explains the newbus function calls? I've written a few and am writing some. Most don't have manual pages. A good start are the NetBSD manual pages, most stuff is the same. times, and definitions are scattered all over. I hate to say it, but it makes me appreciate M$ browse function under visual C++. BAH! ;) Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: further question to bus_alloc_resource
Thus spake Sergey Babkin ([EMAIL PROTECTED]): the old version somehow wedges the system. And upgrading drivers on a running production system is not something I personally would do. This is a dangerous operation and if it would cause any problems Heh. Of course. But also the bktr-driver, the newbus stuff is completely borked. I can't unload the module, as I'd like to. (work in progress...) Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: bktr, unknown PCI device?
Thus spake Wilko Bulte ([EMAIL PROTECTED]): I just upgraded one of my boxes to 4.0-stable. Now I seem to have a 'unknown card' on the PCI, seems related to the bktr. I remember That is the Radio-chip of your TV-card: bktr0: BrookTree 878 mem 0xe700-0xe7000fff irq 7 at device 10.0 on pci0: unknown card (vendor=0x109e, dev=0x0878) at 10.1 irq 7 ^ I have this, too. Alex PS: The Alpine works fine, I'm recompiling kernel for ed0 at the moment :-) -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: further question to bus_alloc_resource
Thus spake Sergey Babkin ([EMAIL PROTECTED]): compiled in the kernel (as opposed to being loaded as a module) then it never gets unloaded. And many drivers were written before the loadable modules appeared. Yes. But what about the others. /sys/dev/aha/aha_mca.c for example - it is part of module (aha), allocs resources, but never releases them. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: further question to bus_alloc_resource
Thus spake Warner Losh ([EMAIL PROTECTED]): : Strange. Enlighten me, please. .-9 If you don't have a detach routine, you can't unload the driver. How does one unload aha.ko then (for the aha_mca.c cards)? That needs to be fixed. Shall I? Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: further question to bus_alloc_resource
Thus spake Doug Rabson ([EMAIL PROTECTED]): There is really no need. The mcclock driver can't be detached since its required for normal system functioning (its the main clock source). OK. I agree. It was just the first driver I got, so far only an example (bad one). What about aha? Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: request for review: bus_alloc_resource(9)
Thus spake Matthew N. Dodd ([EMAIL PROTECTED]): is just a range; start and length, and a type. The 'rid' has nothing to do with offsets into a memory/port resource. Hmm. When I wrote Doug Rabson about newbus months ago, he gave me that part of code: rid = 0x10; /* offset of pci mapping register - check your docs */ res = bus_alloc_resource(dev, SYS_RES_IOPORTS, rid, 0, ~0, 1, RF_ACTIVE); st = rman_get_bustag(res); sh = rman_get_bushandle(res); This "offset of the pci mapping register" is quite confusing for me then. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: request for review: bus_alloc_resource(9)
Thus spake Matthew N. Dodd ([EMAIL PROTECTED]): Think of an 'rid' as in index into an array of like resources. A resource is just a range; start and length, and a type. The 'rid' has nothing to do with offsets into a memory/port resource. Ah, yes. That is probably why resource_list_alloc(rl, dev, child, type, rid, ... is called for the pci-version of bus_alloc_resource :-) (sys/pci/pci.c) Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: request for review: bus_alloc_resource(9)
Thus spake Mike Smith ([EMAIL PROTECTED]): Not at all; in the PCI context, that's what the rid is. As has been said several times now, the meaning of the rid is _bus_specific_. Ah, I wrote that before reading the next mails, stupid me. Well, thanks for all your comments. I'll add/merge the information you gave me in the evening. Thanks! Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: request for review: bus_alloc_resource(9)
Second, reworked version now available. http://big.endian.de/FreeBSD/bus_alloc_resource.9 In my eyes, it's quite correct now and is worth a PR/commit. I'll send a PR if I get your ok. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
new bus_release_resource(9)
Hello! I just finnished bus_release_resource.9. The technical part should be correct, since I could not do things wrong. Maybe you want to review it anyways. http://big.endian.de/FreeBSD/bus_release_resource.9 Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
further question to bus_alloc_resource
Hello! See sys/alpha/isa/mcclock_isa.c: It has attach (which allocs resource), but not detach. Also, it doesn't save the rid in the softc. I wonder, if the generic detach function is capable to clean up the resource without knowing the rid, or if this is a bug. If so, I'm going to write patches. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: further question to bus_alloc_resource
Thus spake Alexander Langer ([EMAIL PROTECTED]): If so, I'm going to write patches. ... for almost every driver in the tree. Hmm. EITHER almost all people never unloaded their driver, or I still understood wide parts wrong. I grepped through /sys now and only 10% of the drivers save the rid. Strange. Enlighten me, please. .-9 Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
request for review: bus_alloc_resource(9)
Hello! I've written bus_alloc_resource(9). I need one with _experience_ on newbus to review it. http://big.endian.de/FreeBSD/bus_alloc_resource.9 Thanks! Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: newbus documentation
To follow up myself, I got the first important comments from Matthew N. Dodd, which I will merge this evening. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: newbus documentation
Second revision is online at http://big.endian.de/misc/newbus-intro.txt The led-driver is still in the tar.gz I posted yesterday, but this tar.gz still has version 1. Please, guys. READ IT! COMMENTS! Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
newbus documentation
Hello! I've started a newbus introduction. It covers most aspects of a newbus driver, based on Warner Losh's led-driver. I've added interrupts- and ioctl-handlers. The whole thing "behing" newbus is a little bit vague. Please review my documentation and give me hints for improvements. I'd like to see that introduction in the official docs some time, since I've heard from several people that the bad thing with newbus is its lack of documentation. ftp://big.endian.de/pub/FreeBSD/newbus-intro.tar.gz Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: controlled panic - kernel-module
Thus spake Sheldon Hearn ([EMAIL PROTECTED]): Only if someone sent in a patch. *nudge* It's on my TODO list now :-) Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ILOVEYOU
Thus spake Dag-Erling Smorgrav ([EMAIL PROTECTED]): Nope, ILOVEYOU is a real virus. ...but it does not wipe your hard disk, no matter what the warning message said. It does wipe all jpeg and mp3 files though... Smartass! ;-) Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ILOVEYOU
Thus spake Matthew Dillon ([EMAIL PROTECTED]): The 'virus' is the warning message itself, silly! Nope, ILOVEYOU is a real virus. It's quite funny. Here in Germany even the radio reported about it, it seems to have crashed MANY companies and governmental institutions. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ILOVEYOU
Thus spake Marc Nicholas ([EMAIL PROTECTED]): Pine is my friend ;-) Mutt =) Nicole Sent via XFmail (becouse I still want my GUI) Did you try Mutt? It has a nice GUI :-) Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GPS heads up
Thus spake Matthew Dillon ([EMAIL PROTECTED]): satellites sitting thousands of miles away in the sky. It's even more impressive to see the government do something right for a change! It's much more idiotic that the government prevented it before. That just means that military use is even better already, i.e. I just imagine they are at 1m or less already. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GPS heads up
Thus spake Poul-Henning Kamp ([EMAIL PROTECTED]): not supposed to know about how it works) which gives them an even more interesting and powerful DOS on the GPS system. I doesn't quite work by postal code, but it comes *very* close. what is a DOS?-) That just means that military use is even better already, i.e. I just imagine they are at 1m or less already. Not quite, the military system is only better because it has two frequencies, and that doesn't improve things *that* much. That's the official version :) Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GPS heads up
Thus spake Poul-Henning Kamp ([EMAIL PROTECTED]): not supposed to know about how it works) which gives them an even more interesting and powerful DOS on the GPS system. I doesn't quite work by postal code, but it comes *very* close. what is a DOS?-) Denial Of Service. Oh. DOS you mean :-) Well, that sounds bad. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GPS heads up
Thus spake Brooks Davis ([EMAIL PROTECTED]): feature. He mounts them on buildings around SoCal with dataloggers to determine building movement due to earthquakes and general plate movement. 2-3 mm is exact enough for this? Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GPS heads up
Thus spake David Holloway ([EMAIL PROTECTED]): You are associating one persons accuracy numbers with someone elses experiments. Ah. So what are the prof's accuracy numbers? Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: JetDirect 500X and FreeBSD
Thus spake Andrew MacIntyre ([EMAIL PROTECTED]): they weren't particularly reliable, particularly when multiple jobs were queued simultaneously. I hope their more recent stuff is better behaved. It is now. A further thing is: If your LaserJet doesn't understand PostScript, you have to use apsfilter. I do it this way here at home, the Windows-boxes use the JetDirect directly (the Windows software is REALLY nice!) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Big ATA problems
Thus spake Brian Fundakowski Feldman ([EMAIL PROTECTED]): You don't have any modules preloaded in /boot/loader.conf, do you? That's That's right. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Big ATA problems
Thus spake Soren Schmidt ([EMAIL PROTECTED]): You don't have any modules preloaded in /boot/loader.conf, do you? That's That's right. I think I lost track here, do you still have problems with the latest ata in 4.0 or -current ??? Not me, but I don't preload any modules in /boot/loader.conf Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: custom release
How much disk space is it necessary to have the entire CVS repository ? Actually almost exactly: /dev/ad0s3f992439 8482766476893%/usr/home/ncvs uhm, approx. 800 MB. The idea is to build a custom release. This takes some more, I believe at least 3 GB or such. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Big ATA problems
Thus spake Jason Allum ([EMAIL PROTECTED]): It seems Jose Gabriel Marcelino wrote: Well, rebuild the loader, that helped Bryan, apparently it has nothing to do with the ata driver i've had no troubles on my ata-based dell precision 410, running -current (circa -11pm last night). Yes, that's because you are using Windows, Windows it not affected by ATA. ;-) Seriously, I have no problems too: alex:~ $ uname -a ; ls -l /boot/loader FreeBSD cichlids.cichlids.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat Feb 19 09:56:01 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/cichlids i386 -r-xr-xr-x 1 root wheel 143360 10 Feb 22:58 /boot/loader* Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: moving CVS repository
Thus spake Nate Williams ([EMAIL PROTECTED]): Or even more paranoid and slightly shorter. ;) find /local2/CVSfoo -name Root -print | fgrep CVS | perl -pi -e 's#/local#/local2/#g;' Hehe, yes ;-) But, as bp mentioned already in IRC: find /path/to/checked/out/files/and/not/the/repository ;-) Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: moving CVS repository
Thus spake Boris Popov ([EMAIL PROTECTED]): This has the side-effect(?) that all sources checked out from the 'old' repository location have references to /local/CVSfoo whereas cvs update obviously wants to have the references to /local2/CVSfoo. The simplest way is to replace content of CVS/Root files. They contain full path to repository. Yes. Shell is your friend. find /local2/CVSfoo -name "Root" | xargs sh -c "mv $a $a.old ; sed -e 's:/local/:/local2/:g' $a.old $a rm $a.old" or something. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mktime(3) and strange struct tm entries
Thus spake Alexander Langer ([EMAIL PROTECTED]): set the tm-tm_mday = 31 (november has only 31 days) ^^ 30, of course Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mktime(3) and strange struct tm entries
Thus spake Thomas David Rivers ([EMAIL PROTECTED]): I believe this is correct behaviour. Ok. I got a further question: From ctime(3): til tm_mon and tm_year are determined. Mktime() returns the specified calendar time; if the calendar time cannot be represented, it returns -1; Which calendar time is meant? IMO November 31th is void and cannot be represented. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: vis(3), unvis(3), HTTP-URIs and libfetch
Thus spake Alexander Langer ([EMAIL PROTECTED]): int strunvisx(char *dst, const char *src, int flag); ok. I'll use a function like this. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PAPERSIZE in /etc/make.conf?
Thus spake Wilko Bulte ([EMAIL PROTECTED]): Read again. part of /etc/profile (or something similar) so that it can be picked up from a reliable place at runtime. - groff has the paper size set as compile time option. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PAPERSIZE in /etc/make.conf?
Thus spake Wilko Bulte (wi...@yedi.iaf.nl): Read again. part of /etc/profile (or something similar) so that it can be picked up from a reliable place at runtime. - groff has the paper size set as compile time option. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: a two-level port system?
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) Alex -- ** I doubt, therefore I might be. ** *** Send email to pgp-k...@cichlids.com to get PGP-Key *** To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: a two-level port system?
Thus spake Mark Newton (new...@internode.com.au): I think most novices probably don't even know the DESCR file exists anyway. Exactly, when I was new I used lynx and the included .html-files for each package to find out what it is. Ok. if you can remove the buildenv-stuff when the package is not that what you want, this might be ok. But you should then have a build-env-distfile dir, because I often reinstall a port after a while i've not used it, and so the distfiles often are still there. If you have no buildenv-distfile-directory, you need a connection to the internet to build it :( Alex -- ** I doubt, therefore I might be. ** *** Send email to pgp-k...@cichlids.com to get PGP-Key *** To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: a two-level port system?
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? I use them very often. So - include it. Alex -- ** I doubt, therefore I might be. ** *** Send email to pgp-k...@cichlids.com to get PGP-Key *** To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
