Re: How big a HD? (automatic settings)
After some advocacy effort, I convinced a friend to try FreeBSD and I handed him some old 3.4 CDs I had. He attempted to install it on a 600M HD with the surprise that the auto settings in sysinstall didn't leave him sufficient space on the /usr partition. He was somewhat surprised as the CD box actually suggested that much less space was required. He downloaded a 5.0 ISO and found the same problem. My question is; how much disk space is required to install FreeBSD nowadays?? This is a known problem. Unfortunately I don't think it will ever get fixed because it's an issue where everyone likes to fight about their way being best. I would expect the disk in question to be enough if the partitions were sized by hand after looking at an installed system. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: incorrect information in ata(4)?
kern.osrevision: 199506 staralfur% sysctl kern.osrevision kern.osrevision = 199506 staralfur% uname -v Darwin Kernel Version 5.3: Thu Jan 24 22:06:02 PST 2002; root:xnu/xnu-201.19.obj~1/RELEASE_PPC I couldn't tell you what it means, though. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: [OT] alarm() question
Uh, I'm not sure what to make of that mangling of my name. However, I think the pointer to Steven's book you provided may be the thing he needs. I certainly don't know what he needs based on his followup. I'm really sorry for messing up your name like that. I suppose your domain name was sticking in my head for some reason. I don't think I got the response that you are talking about, but from what he has sent me I think that Stevens will provide the answer. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: [OT] alarm() question
Why does the alarm go off but not interrupt the system call? bzzt() is executed, but the program doesn't print Done and exit for a minute plus. Pointers to FM to RT welcome. The system call is being interrupted, it just gets restarted right away by default. See Steven's UNIX Network Programming for a means of avoiding this behavior. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: [OT] alarm() question
The system call is being interrupted, it just gets restarted right away by default. See Steven's UNIX Network Programming for a means of avoiding this behavior. Of course, I'm completely wrong because we're not even talking about a system call here. Mike Mired already posted what you need. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: (no subject)
The concept that netgraph hooks are a leg up on say, ETs drivers that have integrated bandwidth management and prioritization, WAN bridging support, load balancing and a probably 25% performance advantage is a bit entertaining. Unless you need to do some convoluted encapsulation netgraph is, aside from being appallingly non-standard to anything else in the market, not much of an advantage, and its a poster child for the trade off of flexibility versus performance. Lets face it. If you were going to sit down and design an interface for frame relay, multi-protocol support, etc, you'd have to be smoking something pretty strong to come up with netgraph. But its free and there is source, so it must be great! Dennis, if you are going to continue trolling FreeBSD mailing lists from your AOL account, you should really consider choosing a name that does not coincide with what we already know or can easily find out about you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: (no subject)
Just for historical reasons I have a question... Is Dennis and Elder Troll or was he cast of the fire and brimstone of the BSDi dissolution? Dennis does something along the lines of building wan cards and selling them for a number of systems, including FreeBSD. The ironic part, of course, is that he likes to fight with the very people that are creating his market. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Recent changes to libdialog are weird
Recently, libdialog's use of tab, space and enter seems to have changed. Now, space and enter mean the same thing. Before, enter was a context-insensitive short-cut to the currently selected dialogue submit button. There's nothing context-insensitive about libdialog. Pressing enter does not submit the network interface configuration form. What many folks may not realize is that the new behaviour, while safer than what we had before, makes libdialog behave differently from at least Motif, Windows, JavaAWT, JavaSwing. It seems to me that in popular toolkits, one moves the curson over the desired component and presses a button. To do this with a keyboard, tab is used to move the cursor, and space is used to press a button. So what we have now is a libdialog that protects the finger-happy, while confounding those who expect pretty standard behaviour. What we have now, at best, is an interface that is usable by someone with no proir experiance. At worst, it is an archaic interface, but has behaviour that is documented on the very screen on which it is implemented (at least in the case of sysinstall), and thus is no worse than what we had before. I reckon if sysinstall needs to be weird, sysinstall should use its own weird version of libdialog and leave the distributed libdialog alone. This would be disasterous. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Recent changes to libdialog are weird
I agree with and like the new behaviour but I think it is still lacking in one aspect. When using a mouse to position your cursor it's very obvious where that cursor is and what it's pointing to. With lidialog it's hard to tell at just a glance where the cursor is because it's only a few characters wide even if the button it's on is wider, and it's a drab gray color. If the cursor were something brighter and unique it might make it easier to distinguish as the cursor and there for easier to understand. Red maybe? Anyone else think this is a good idea? That would be excellent. However, according to jkh there is no easy means of doing this, which leaves us with the option of changing the grey background around. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: cvs commit: src/gnu/lib/libdialog checklist.c menubox.c radiolist.c textbox.c tree.c yesno.c
I can't tell any more how many times this annoying libdialog has bitten me in this regard. Don't think you're the only one :) Even better - I take it sysinstall then uses 'sane' space/enter combo's also (it being a consumer of libdialog)? Yes, my big purpose here was to make sysinstall a little nicer. There may be plans to abandon it, but at very least the next few releases will be using it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: cvs commit: src/gnu/lib/libdialog checklist.c menubox.c radiolist.c textbox.c tree.c yesno.c
Modified files: gnu/lib/libdialogchecklist.c menubox.c radiolist.c textbox.c tree.c yesno.c Log: Improve the interface provided by libdialog. Move a cursor around over the components and trigger actions based on its position. This reduces the need to remember the functions of various keys, and makes the interface more consistant across library. This eliminates the problem where people would exit a menu when they really wanted to select an item (the space/enter confusion), amongst other things. I intend to MFC this sometime before 4.4-RELEASE, potentially along with some things people from mailing lists have submitted. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Status of dialog(1) and libdialog.
I'm working on some patches for dialog(1) and libdialog. Does FreeBSD team want to continue use of dialog(1) program and libdialog in future? I ask this question because I fix some problems I have with dialog(1) (really with libdialog) and I'm going to try to fix the same problems with all functions in libdialog, so I want to know if it will be interesting for FreeBSD. I saw some bug reports for dialog/libdialog, but didn't see good reactions on that PRs. I'm currently working on libdialog, hopefully making the interface a bit more sensible. I'd like to see what you're up too, hopefully we're not duplicating efforts. Currently the plan is to commit this stuff in a day or two. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: upgrading packages
Currently, upgrading packages is more painful than it should be. However, it would not take much work to make things significantly more friendly - 1. pkg_add - when a package is installed, it should check for an older version of itself, and if the new version provides everything from the old one, update the associated +REQUIRED_BY files 2. pkg_delete - when a package is deleted, it should check for a newer version of itself, and files that overlap between both versions should not be deleted Careful users can avoid the problems that these two changes fix, but there's really no reason to not make life simple for everyone. Comments? Takers? I'm a bit busy due to the finals that I've got looming on the horizon, but I'll eventually get to it if no one else does. Nevermind, it looks like pkg_update(1) does everything I want and more. I should probably read documentation more, and complain less. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: technical comparison
The proposed filesystem is most likely Reiserfs. This is a true journalling filesystem with a radically non-traditional layout. It is no problem to put millions of files in a single directory. (actually, the all-in-one approach performs better than a tree) XFS and JFS are similarly capable, but Reiserfs is well tested and part of the official Linux kernel. You can get the Reiserfs team to support you too, in case you want to bypass the normal filesystem interface for even better performance. It should be noted that simply because something is tested and a part of a release, it is not automatically wonderful. My last experiance with linux was in the 2.2 days, and ended with a lost root filesystem while attempting to access an msdosfs drive. From what I've read, mixing reiserfs and nfs is about as exciting as the stock market has been in the last few months. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
upgrading packages
Currently, upgrading packages is more painful than it should be. However, it would not take much work to make things significantly more friendly - 1. pkg_add - when a package is installed, it should check for an older version of itself, and if the new version provides everything from the old one, update the associated +REQUIRED_BY files 2. pkg_delete - when a package is deleted, it should check for a newer version of itself, and files that overlap between both versions should not be deleted Careful users can avoid the problems that these two changes fix, but there's really no reason to not make life simple for everyone. Comments? Takers? I'm a bit busy due to the finals that I've got looming on the horizon, but I'll eventually get to it if no one else does. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
syslogd patch
Printing out the whole path to the kernel all the time in syslog messages is
a bit redundant and ugly, especially seeing that it isn't done for any other
binaries.
Should I send-pr this thing too, or is just sending it to -hackers enough?
--- usr/src/usr.sbin/syslogd/syslogd.c.old Sat Jan 13 21:20:28 2001
+++ usr/src/usr.sbin/syslogd/syslogd.c Sat Jan 13 22:27:44 2001
@@ -734,8 +734,8 @@
int flags;
{
struct filed *f;
- int i, fac, msglen, omask, prilev;
- char *timestamp;
+ int i, fac, msglen, omask, prilev, bflen;
+ char *timestamp, *bfshort;
char prog[NAME_MAX+1];
char buf[MAXLINE+1];
@@ -784,7 +784,16 @@
/* add kernel prefix for kernel messages */
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);
msg = buf;
msglen = strlen(buf);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD in good standing in netcraft survey
No worries, you just forgot the 's' at the end ;) The site is still there, it's just "uptimes.net" not "uptime.net". Guys, sorry did not mean to spam, but there used to be a site called uptime.net (I'm pretty sure of it) It basically did what netcraft is doing, except it only kept the uptimes. They had some wonderful uptimes of several years. As far as I remember, NETBSD was 1st place and FreeBSD was in second. sorry about the spam, was not aware that the site has gone away. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Help
If there's any truth to this assumption, there's probably a much bigger problem at hand, such as all of their networking is borked. It's kind of hard to determine what's going on with such a general statement. Can you assist me with a Free BSD problem. One of my customers had a College kid mess with his Unix Kernal. Now they can no longer access thier E-mail ??? Could he have turned off Email somehow, when he messed around with the Unix kernal??? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
firewall help
i was told by a freebsd friend to ask you this question: can *bsd do kernel-space ip port forwarding? thanks. -E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
