Re: scsi tape driver wants an update
Matthew Jacob wrote: This is a harmless message for the moment. I took a look at the new make_dev stuff- it's more than a no-brainer to add because there's a lot of stuff about supported device nodes, etc... I'll try and get back to this after FreeBSDcon. Funny, phk's comments led me to believe it's actually easier to use make_dev() (!= makedev(), btw -- maybe you looked up the wrong one?). And, talking about phk, it is also my impression that it is his intent to push these changes as fast as he can. He gets strange at this time of the year, y'know... I think Jordan once posted an interesting explanation for this phenomenum. :-) -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: scsi tape driver wants an update
In message [EMAIL PROTECTED], "Daniel C. Sobral" writes: Matthew Jacob wrote: This is a harmless message for the moment. I took a look at the new make_dev stuff- it's more than a no-brainer to add because there's a lot of stuff about supported device nodes, etc... I'll try and get back to this after FreeBSDcon. Funny, phk's comments led me to believe it's actually easier to use make_dev() (!= makedev(), btw -- maybe you looked up the wrong one?). And, talking about phk, it is also my impression that it is his intent to push these changes as fast as he can. He gets strange at this time of the year, y'know... I think Jordan once posted an interesting explanation for this phenomenum. :-) "This time of the year" == "This time in the release cycle" If we want to have a somewhat clean line before 4.0 now is the time to push it through, not after the code freeze. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: scsi tape driver wants an update
"This time of the year" == "This time in the release cycle" If we want to have a somewhat clean line before 4.0 now is the time to push it through, not after the code freeze. And could you mention when the code freeze might be so that some of us could plan our work? Perhaps I've missed something, but I hadn't heard when the freeze would be. I have a *lot* of things to consider changing before it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: scsi tape driver wants an update
In message [EMAIL PROTECTED], Matthew Jacob writes: "This time of the year" == "This time in the release cycle" If we want to have a somewhat clean line before 4.0 now is the time to push it through, not after the code freeze. And could you mention when the code freeze might be so that some of us could plan our work? Perhaps I've missed something, but I hadn't heard when the freeze would be. I have a *lot* of things to consider changing before it. I have no idea when the code freeze happens, neither has anybody else. Looking at my complete collection of FreeBSD CDs on the shelf here I would put my money (but not too much) on january 2000. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: scsi tape driver wants an update
On Tue, 12 Oct 1999, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Matthew Jacob writes: "This time of the year" == "This time in the release cycle" If we want to have a somewhat clean line before 4.0 now is the time to push it through, not after the code freeze. And could you mention when the code freeze might be so that some of us could plan our work? Perhaps I've missed something, but I hadn't heard when the freeze would be. I have a *lot* of things to consider changing before it. I have no idea when the code freeze happens, neither has anybody else. Looking at my complete collection of FreeBSD CDs on the shelf here I would put my money (but not too much) on january 2000. Well, you scared me with the "not after the code freeze" statement. I would like the work I do for FreeBSD 4.0 not to be as incomplete as it was for FreeBSD 3.0, so making plans as to when new feature freeze is would be a "good thing (tm)". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: scsi tape driver wants an update
In message [EMAIL PROTECTED], Matthew Jacob writes: And could you mention when the code freeze might be so that some of us could plan our work? Perhaps I've missed something, but I hadn't heard when the freeze would be. I have a *lot* of things to consider changing before it. I have no idea when the code freeze happens, neither has anybody else. Looking at my complete collection of FreeBSD CDs on the shelf here I would put my money (but not too much) on january 2000. Well, you scared me with the "not after the code freeze" statement. I would like the work I do for FreeBSD 4.0 not to be as incomplete as it was for FreeBSD 3.0, so making plans as to when new feature freeze is would be a "good thing (tm)". I'd say try to have the boat rocking done by dec 1st, but that is merely a guess. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: scsi tape driver wants an update
This is a harmless message for the moment. I took a look at the new make_dev stuff- it's more than a no-brainer to add because there's a lot of stuff about supported device nodes, etc... I'll try and get back to this after FreeBSDcon. On Sun, 10 Oct 1999, Andy Farkas wrote: Just a reminder I guess, # uname -v FreeBSD 4.0-CURRENT #0: Sun Oct 10 16:16:34 EST 1999 # mt retension console emits (in bright white): WARNING: driver sa should register devices with make_dev() (dev_t = "#sa/1") -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
scsi tape driver wants an update
Just a reminder I guess, # uname -v FreeBSD 4.0-CURRENT #0: Sun Oct 10 16:16:34 EST 1999 # mt retension console emits (in bright white): WARNING: driver sa should register devices with make_dev() (dev_t = "#sa/1") -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: scsi tape driver wants an update
Huh? I'll check it out.. On Sun, 10 Oct 1999, Andy Farkas wrote: Just a reminder I guess, # uname -v FreeBSD 4.0-CURRENT #0: Sun Oct 10 16:16:34 EST 1999 # mt retension console emits (in bright white): WARNING: driver sa should register devices with make_dev() (dev_t = "#sa/1") -- :{ [EMAIL PROTECTED] Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message