Hi,
Kai wrote:
> Another ™.02,
>
> Today I'm installing Freebsd 6 from a CD, and I'm having to jump through
> loops to get it up-to-date. Take for example FreeBSD-SA-06:03.cpio.
>
> First I need to install the sources for the complete OS, then run a patch on
> it, and all that for the installation
Kai <[EMAIL PROTECTED]> wrote
> Hello,
>
> Another ™.02,
>
> Today I'm installing Freebsd 6 from a CD, and I'm having to jump through
> loops to get it up-to-date. Take for example FreeBSD-SA-06:03.cpio.
>
> First I need to install the sources for the complete OS, then run a patch on
> it, and all
On Thu, 5 Jan 2006, Jo Rhett wrote:
>
> Look around. Every major commercial OS does it just fine. Most of the
> open source OSes do it just fine. Debian had probably the easiest to use
> system, and they've risen, owned the world and fallen all while FreeBSD has
> been debating this issue.
>
On 22. des. 2005, at 22.17, Jo Rhett wrote:
On Sat, Dec 17, 2005 at 06:19:25PM -0700, Scott Long wrote:
FreeBSD Update was written by, and is continuously maintained by the
actual FreeBSD Security Officer. It's as official as it gets. If
the only barrier to acceptance is that it's not distrib
On Thu, 12 Jan 2006 18:15, Jo Rhett wrote:
> Before we plan the invasion of Iraq, how about an agreement on what we're
> trying to accomplish? Like I said, this topic has always been killed
> because "non-newbies can run make buildworld". So if it's going to get
> shot down quickly then why bothe
On Thu, 12 Jan 2006 18:07, Jo Rhett wrote:
> On Fri, Jan 06, 2006 at 10:20:11PM +1030, Daniel O'Connor wrote:
> > I imagine there are a few committers interested, but I'd say you need to
> > ask the right way first..
>
> As in...?
I don't know any personally, but then again I only know about 3 com
Hej there,
Jo Rhett wrote:
> On Fri, Jan 06, 2006 at 01:27:18PM +0100, Marian Hettwer wrote:
>
>>I'm actually wondering how yahoo for instance handles this situation. To
>>my knowledge, they have several thousand of FreeBSD based servers.
>>Either they are all the same in regards to configuration
On Wed, 2006-Jan-11 23:22:53 -0800, Jo Rhett wrote:
>I am deliberately trolling: not to cause grief, but to see if there are any
>bites on the topic. So far it's just people insulting my intelligence and
>cut&pasting web pages to me.
Going out of your way to antagonize FreeBSD developers is not t
On Fri, Jan 06, 2006 at 01:27:18PM +0100, Marian Hettwer wrote:
> I'm actually wondering how yahoo for instance handles this situation. To
> my knowledge, they have several thousand of FreeBSD based servers.
> Either they are all the same in regards to configuration and version, or
> they have some
On Fri, Jan 06, 2006 at 10:20:11PM +1030, Daniel O'Connor wrote:
> I imagine there are a few committers interested, but I'd say you need to ask
> the right way first..
As in...?
But again, there are lots of people interested in this topic. Colin for
an obvious one. But if Colin can't convince
On Fri, Jan 06, 2006 at 01:16:36PM -0800, John-Mark Gurney wrote:
> You're trying to target to large of an audience... You need to get _A_
> committer interested in your work, and get HIM to guide you and commit
> your work...
DING! Now we are FINALLY understanding what my goal for this topic w
On Sat, Jan 07, 2006 at 06:44:36AM +1100, Peter Jeremy wrote:
> In general, volunteer projects have a surfeit of ideas and a shortage
> of real implementations. The Project is never going to agree to import
> an idea without some substance.
Always true, and I wouldn't expect less. But we've cov
> >On Thu, Jan 05, 2006 at 10:47:38AM +0100, Patrick M. Hausen wrote:
> >> While I agree with much of your reasoning, I know exactly zero
> >> people running a modified kernel of any version of Windows,
> >> Mac OS X or Solaris, to name just three commercial OS's.
> On Fri, 2006-Jan-06 02:34:40 -
Jo Rhett wrote this message on Fri, Jan 06, 2006 at 03:03 -0800:
> On Thu, Jan 05, 2006 at 10:41:47AM -0800, John-Mark Gurney wrote:
> > I believe core has a policy of never supporting vaporware... There is
> > always the chicken and egg problem with arguments like this... I'll
> > code this if y
On Fri, 2006-Jan-06 02:34:40 -0800, Jo Rhett wrote:
>On Thu, Jan 05, 2006 at 10:47:38AM +0100, Patrick M. Hausen wrote:
>> While I agree with much of your reasoning, I know exactly zero
>> people running a modified kernel of any version of Windows,
>> Mac OS X or Solaris, to name just three commerc
On Fri, 2006-Jan-06 03:03:18 -0800, Jo Rhett wrote:
>> Bottom line: Once code exists, then support can be talked about..
>
>This is bullhockey and you know it. Once the project is done, we'll
>authorize a budget for it? Once the season is over we'll know who should
>be on the starting team?
In
Hi there,
Jo Rhett wrote:
> On Fri, Jan 06, 2006 at 11:20:13AM +1030, Daniel O'Connor wrote:
>>
>>So, uhh, how would your magical binary upgrade system handle custom kernels?
>>Why would it be any different? You still haven't explained how this would
>>work..
>
>
> Versioning of the core packa
On Fri, 6 Jan 2006 21:53, Jo Rhett wrote:
> > you mean? Are you claiming someone from (or claiming to be from core)
> > said "Don't do this, we won't allow it"? If so, can you supply proof?
>
> I used to write a lot of patches to freebsd. I used to submit a lot of bug
> reports. I've found over t
> > I just know that core has either struck it down or been Silent.
On Thu, Jan 05, 2006 at 05:32:26PM -0600, Mark Linimon wrote:
> The latter is an entirely different case from the former, and you've been
> claiming core has done the former. This, and the above, tell me that
> you're not intere
On Fri, Jan 06, 2006 at 11:20:13AM +1030, Daniel O'Connor wrote:
> For NFS mount, read: any network file system. You can also use, say IPSEC to
> protect the NFS packets (although I'm not claiming it's a trivial thing to
> set up..)
IPsec is trivial compared to the amount of code and localized
On Thu, Jan 05, 2006 at 10:41:47AM -0800, John-Mark Gurney wrote:
> I believe core has a policy of never supporting vaporware... There is
> always the chicken and egg problem with arguments like this... I'll
> code this if you agree to support it and maintain it/I will agree to
> support it once
On Thu, Jan 05, 2006 at 10:40:56PM +1100, Peter Jeremy wrote:
> >No. I want a binary update mechanism. Obviously if we have local
> >configuration options we'll have to compile our own binaries. But doing
> >the work of tracking system updates currently requires us to build our own
> >patch trac
On Thu, Jan 05, 2006 at 01:26:12PM -0500, Ender wrote:
> I think what "integrated with the core OS" means from a user standpoint
> is: from a fresh minimum install of freebsd I can type
> "freebsd-update-whatever" and it will update my system.
Just "freebsd-update" ;-)
That works fairly well wi
On Thu, Jan 05, 2006 at 09:11:58PM +1030, Daniel O'Connor wrote:
> On Thu, 5 Jan 2006 20:02, Jo Rhett wrote:
> > On Fri, Dec 23, 2005 at 11:26:44AM +1030, Daniel O'Connor wrote:
> > > How do you expect these two to be handled in a binary upgrade?
> > > I can't see how it's possible..
> >
> > Look a
On Thu, Jan 05, 2006 at 10:47:38AM +0100, Patrick M. Hausen wrote:
> > > > 1. modified kernels are foobar
> > > > ..yet are practically mandatory on production systems
>
> > Look around. Every major commercial OS does it just fine.
>
> While I agree with much of your reasoning, I know exactly
ml> (And, as well, that you do not even understand the role the core plays
ml> in the project. Hint: it is not primarily technical in nature.)
For those curious to know how the project works, the following online
resources may help:
A project model for the FreeBSD Project
http://www.freebsd.
[cross post to -current removed]
On Thu, 5 Jan 2006 19:54, Jo Rhett wrote:
> On Fri, Dec 23, 2005 at 11:36:11AM +1030, Daniel O'Connor wrote:
> > On each 'client' PC..
> > NFS mount /usr/src and /usr/obj
> > installkernel
> > reboot
> > installworld
>
> Works fine on home computers behind firewall
> Jo Rhett wrote this message on Thu, Jan 05, 2006 at 01:24 -0800:
> Sorry. As said before, the topic is always struck down and nobody from
> core has ever stood up to say "we'll support this". I don't know whose on
> core this week, nor will I at any given time.
This information is publicly ava
Jo Rhett wrote this message on Thu, Jan 05, 2006 at 01:24 -0800:
> > You are putting words in the mouth of core@ -
>
> Sorry. As said before, the topic is always struck down and nobody from
> core has ever stood up to say "we'll support this". I don't know whose on
> core this week, nor will I
Daniel O'Connor wrote:
On Thu, 5 Jan 2006 20:02, Jo Rhett wrote:
On Fri, Dec 23, 2005 at 11:26:44AM +1030, Daniel O'Connor wrote:
How do you expect these two to be handled in a binary upgrade?
I can't see how it's possible..
Look around. Every major commercial OS does it just
On Thu, 2006-Jan-05 01:37:27 -0800, Jo Rhett wrote:
>No. I want a binary update mechanism. Obviously if we have local
>configuration options we'll have to compile our own binaries. But doing
>the work of tracking system updates currently requires us to build our own
>patch tracking mechanism, an
On Thu, 5 Jan 2006 20:02, Jo Rhett wrote:
> On Fri, Dec 23, 2005 at 11:26:44AM +1030, Daniel O'Connor wrote:
> > How do you expect these two to be handled in a binary upgrade?
> > I can't see how it's possible..
>
> Look around. Every major commercial OS does it just fine. Most of the
> open sour
Hello!
> > > 1. modified kernels are foobar
> > > ..yet are practically mandatory on production systems
> Look around. Every major commercial OS does it just fine.
While I agree with much of your reasoning, I know exactly zero
people running a modified kernel of any version of Windows,
Mac OS
> On Thu, 2005-Dec-22 13:17:30 -0800, Jo Rhett wrote:
> >But FreeBSD Update suffers from all of the same limitations that I've been
> >describing because of lack of integration with the Core OS.
> >
> >1. modified kernels are foobar
> > ..yet are practically mandatory on production systems
> >
> >
> On Fri, 23 Dec 2005 07:47, Jo Rhett wrote:
> > But FreeBSD Update suffers from all of the same limitations that I've been
> > describing because of lack of integration with the Core OS.
> >
> > 1. modified kernels are foobar
> > ..yet are practically mandatory on production systems
> >
> > 2. m
> Patrick M. Hausen, and lo! it spake thus:
> > Any suggestions for an alternative to NFS if your 'client' servers
> > are located "all over the world" and you want to installworld across
> > the Internet? I was planning to use NFS/TCP secured by IPSec
> > transport mode, but anything less complica
On Fri, Dec 23, 2005 at 11:36:11AM +1030, Daniel O'Connor wrote:
> On each 'client' PC..
> NFS mount /usr/src and /usr/obj
> installkernel
> reboot
> installworld
Works fine on home computers behind firewalls.
Useless on public servers that don't run RPC.
Useless on flash-based servers where min
> On Thu, Dec 22, 2005 at 01:09:04PM -0800 I heard the voice of
> Jo Rhett, and lo! it spake thus:
> >
> > No, you're missing the point. More core OS upgrades means less
> > incremental patches (which are easier to apply than a full update).
On Thu, Dec 22, 2005 at 09:08:13PM -0600, Matthew D.
On Thu, Dec 22, 2005 at 09:08:13PM -0600, Matthew D. Fuller wrote:
> Having done full OS upgrades a number of times, I can't remember the
> last time it took more than 5 or 10 minutes (during most of which the
When the servers are in 17 countries around the world, with no CD-ROM
access. You keep
On Fri, Dec 23, 2005 at 03:38:20PM +1100, Peter Jeremy wrote:
> I agree with Brooks. I don't recall ever seeing a message from -core
> (or anyone else talking on behalf of the Project) stating that code to
> make binary updates possible would not be integrated. For that matter,
> I don't recall e
On Fri, Dec 23, 2005 at 01:13:20PM -0600, Mark Linimon wrote:
> On Thu, Dec 22, 2005 at 01:10:19PM -0800, Jo Rhett wrote:
> > I and many others have offered to work on this. The core team has
> > repeatedly stated that they won't integrate the efforts
>
> Please provide hard evidence for this ass
On Sun, 25 Dec 2005 02:02, Brian Candler wrote:
> Linux has an extremely neat solution for this (sshfs) but I don't know of
> anything comparable in the BSD world. sshfs uses 'Fuse', a plug-in
> architecture which allows filesystems to run in userland. I believe it
> makes an sftp connection to the
On Fri, Dec 23, 2005 at 09:51:15AM +0100, Patrick M. Hausen wrote:
> Any suggestions for an alternative to NFS if your 'client' servers
> are located "all over the world" and you want to installworld across
> the Internet? I was planning to use NFS/TCP secured by IPSec transport
> mode, but anythin
On Thu, Dec 22, 2005 at 01:10:19PM -0800, Jo Rhett wrote:
> I and many others have offered to work on this. The core team has
> repeatedly stated that they won't integrate the efforts
Please provide hard evidence for this assertion. Merely repeating it will
not be sufficiently convincing. I wou
On Fri, 23 Dec 2005 21:10:19 +0530
Joseph Koshy <[EMAIL PROTECTED]> wrote:
> www.infrastructures.org
> www.isconf.org
and perhaps also http://www.cfengine.org/
and probably others.
IMHO, FreeBSD is a good os, with good options on configuration and
management.
It is not a systems management tool
phk> Bring to system administration what source code
phk> version control brought to programming.
www.infrastructures.org
www.isconf.org
--
FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
___
freebsd-stable@freebsd.org mailing list
http://lis
I have consistently ignored all emails in this thread because the
use of the word "demand" in the Subject.
Whenever people use words like "demand" or "somebody should" in
FreeBSD contexts, it indicates cluelessness to me.
Cluelessness about how the project works and cluenessness about
how thing
Brian Candler wrote:
> I think the real concern here is: for how long after RELEASE_X_Y are binary
> patches for it made available?
I build FreeBSD Update patches for all the branches supported by the
FreeBSD Security Team.
To answer a couple of other questions:
FreeBSD Update is something which
On Fri, 23 Dec 2005 19:26, Matthew D. Fuller wrote:
> > the Internet? I was planning to use NFS/TCP secured by IPSec
> > transport mode, but anything less complicated would be greatly
> > appreciated ;-)
>
> This is one of the situations where r{dist,sync}'ing out the binaries
> makes more sense th
On Thu, Dec 22, 2005 at 09:08:13PM -0600, Matthew D. Fuller wrote:
> > No, you're missing the point. More core OS upgrades means less
> > incremental patches (which are easier to apply than a full update).
>
> Right. I don't understand how B follows A here.
>
> These patches come from where? S
On Fri, Dec 23, 2005 at 09:51:15AM +0100 I heard the voice of
Patrick M. Hausen, and lo! it spake thus:
>
> Any suggestions for an alternative to NFS if your 'client' servers
> are located "all over the world" and you want to installworld across
> the Internet? I was planning to use NFS/TCP secure
Hi, Folks!
> On your central PC..
> buildworld once.
> builkernel once for each of the different kernels you are using.
>
> On each 'client' PC..
> NFS mount /usr/src and /usr/obj
> installkernel
> reboot
> installworld
Any suggestions for an alternative to NFS if your 'client' servers
are locat
On Thu, 2005-Dec-22 13:17:30 -0800, Jo Rhett wrote:
>But FreeBSD Update suffers from all of the same limitations that I've been
>describing because of lack of integration with the Core OS.
>
>1. modified kernels are foobar
> ..yet are practically mandatory on production systems
>
>2. modified sour
On Thu, 2005-Dec-22 13:10:19 -0800, Jo Rhett wrote:
>I and many others have offered to work on this. The core team has
>repeatedly stated that they won't integrate the efforts, which makes
>os-upgrade capability minimal and easily broken. (see current efforts)
On Thu, 2005-Dec-22 14:05:32 -0800,
On Thu, Dec 22, 2005 at 01:09:04PM -0800 I heard the voice of
Jo Rhett, and lo! it spake thus:
>
> No, you're missing the point. More core OS upgrades means less
> incremental patches (which are easier to apply than a full update).
Right. I don't understand how B follows A here.
These patches
On Fri, 23 Dec 2005 08:42, Jo Rhett wrote:
> > Using a build server as a testbed and to generate new packages or even a
> > new kernel + world will reduce the amount of work required, but FreeBSD
> > does require some level of administration and maintenance.
>
> We already have that. But again, I'
On Fri, 23 Dec 2005 07:47, Jo Rhett wrote:
> On Sat, Dec 17, 2005 at 06:19:25PM -0700, Scott Long wrote:
> > FreeBSD Update was written by, and is continuously maintained by the
> > actual FreeBSD Security Officer. It's as official as it gets. If
> > the only barrier to acceptance is that it's no
On Thu, Dec 22, 2005 at 04:45:09PM -0500, Chuck Swiger wrote:
> FreeBSD releases new .ISO images several times a year, but you've got the
> tools to make .ISO images of patch releases yourself, if you want to. I
> don't think that the FreeBSD project can shorten the release cycle below a
> mont
On Thu, Dec 22, 2005 at 01:30:41PM -0800, Brooks Davis wrote:
> This statement makes no sense. The core team wouldn't have much to
> do with this other than possibly being involved in making any service
> official. Also, approval is never given to include a non-existent
> feature. Easy, binary u
Jo Rhett wrote:
On Sat, Dec 17, 2005 at 06:55:03PM -0500, Chuck Swiger wrote:
YMMV. I burned a 6.0 release from the ISO image, and did a binary upgrade on an
IBM ThinkPad (T.34? maybe), which worked perfectly. All of the 5.x binaries,
including X11, KDE, printing, Mozilla, etc worked just fine
On Thu, Dec 22, 2005 at 01:10:19PM -0800, Jo Rhett wrote:
> On Sat, Dec 17, 2005 at 11:08:07PM +0100, Wilko Bulte wrote:
> > So, when will you fix it? Or hire someone to fix it? FreeBSD after
> > all is mostly a volunteer operation.
>
> I and many others have offered to work on this. The core
On Sat, Dec 17, 2005 at 06:19:25PM -0700, Scott Long wrote:
> FreeBSD Update was written by, and is continuously maintained by the
> actual FreeBSD Security Officer. It's as official as it gets. If
> the only barrier to acceptance is that it's not distributed from the
> FreeBSD.org domain, then a
On Sat, Dec 17, 2005 at 11:35:34PM +0100, K?vesd?n G?bor wrote:
> I agree. And after all, tracking a security branch isn't too difficult,
> but the most people think that they have to do a complete "make
> buildworld" after a security advisory, but this isn't true. For example
> there was that
On Sat, Dec 17, 2005 at 11:08:07PM +0100, Wilko Bulte wrote:
> So, when will you fix it? Or hire someone to fix it? FreeBSD after
> all is mostly a volunteer operation.
I and many others have offered to work on this. The core team has
repeatedly stated that they won't integrate the efforts, wh
> On Sat, Dec 17, 2005 at 02:00:21PM -0800 I heard the voice of
> Joe Rhett, and lo! it spake thus:
> >
> > Increasing the number of deployed systems out of date [...]
On Sat, Dec 17, 2005 at 08:37:25PM -0600, Matthew D. Fuller wrote:
> This doesn't make any sense. If you install a 6.0 system,
> On Sun, Dec 18, 2005 at 09:55:33AM +, Matthew Seaman wrote:
> > Doesn't creating a binary updates system that's going to be practical to use
> > require implementation of that old and exceedingly bikesheddable subject:
> > packaging
> > up the base system?
On Sun, Dec 18, 2005 at 12:13:09PM
On Sun, Dec 18, 2005 at 09:55:33AM +, Matthew Seaman wrote:
> Doesn't creating a binary updates system that's going to be practical to use
> require implementation of that old and exceedingly bikesheddable subject:
> packaging up the base system?
EXACTLY. That's why we need core team suppo
> > On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote:
> > > There will be three FreeBSD 6 releases in 2006.
> On Sat, Dec 17, 2005 at 02:00:21PM -0800, Joe Rhett wrote:
> > While this is nice, may I suggest that it is time to put aside/delay one
> > release cycle and come up with a binar
On Sat, Dec 17, 2005 at 06:55:03PM -0500, Chuck Swiger wrote:
> YMMV. I burned a 6.0 release from the ISO image, and did a binary upgrade on
> an
> IBM ThinkPad (T.34? maybe), which worked perfectly. All of the 5.x binaries,
> including X11, KDE, printing, Mozilla, etc worked just fine.
There a
As a FreeBSD-n00b with some 'friends' that know FreeBSD better/well I
can only say
Please add this kind of information to the Handbook
Any addition to the handbook on tracking down problems and smarter
ways to fix things would be greatly appreciated. I found myself
recompiling my kernel to test c
Kevin Oberman writes:
> [discussion of USB/Cx level interactions clipped out...]
>
> If you unload the drivers, you should be to lower levels. Take a look at
> sysctl hw.acpi.cpu for detail and to see how much time is spent in each
> sleep state.
>
> I assume that you can unload the driver
Kevin Oberman wrote:
Date: Sun, 18 Dec 2005 20:46:49 +0100
From: martinko <[EMAIL PROTECTED]>
Kevin Oberman wrote:
Date: Sat, 17 Dec 2005 18:14:01 +0100
From: martinko <[EMAIL PROTECTED]>
Kevin Oberman wrote:
Date: Fri, 16 Dec 2005 14:29:39 -0600
From: Craig Boston <[EMAIL
On Sun, Dec 18, 2005 at 12:44:06PM -0800, Doug Barton wrote:
> regression in this area in RELENG_6, it would be worth reporting to this
> list, hopefully with enough detail that a developer could help you
> troubleshoot the problem.
This problem already existed in 5.x, please have a look at ker
On Sun, Dec 18, 2005 at 12:06:12PM -0500, Kris Kennaway wrote:
> Well, no, the "sound system" is not broken, perhaps a driver just
In my case it is broken, I hear cracks and dropouts with my Soundblaster
Live card and the emu10k driver. It gets worse with higher loads and
uptime. I experienced th
On Sun, Dec 18, 2005 at 12:13:09PM -0500, Kris Kennaway wrote:
> > Doesn't creating a binary updates system that's going to be practical to use
> > require implementation of that old and exceedingly bikesheddable subject:
> > packaging
> > up the base system?
>
> No, after all the *existing* bina
On Dec 18, 2005, at 8:01 , Daniel O'Connor wrote:
On Mon, 19 Dec 2005 00:32, Uwe Laverenz wrote:
- wlan is broken, my Thinkpad keeps losing WPA-PSK connection very
often
(probably kern/88793).
"Works for me" (tm). Although I have an ath card. Perhaps you
should take it
up with the ipw
On Mon, 19 Dec 2005 00:32, Uwe Laverenz wrote:
> On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote:
> I don't know his exact problems either, but I could name you a few
> examples that currently reduce the fun of using FreeBSD:
If you're going to do this, please write a GOOD bug report
> Date: Sun, 18 Dec 2005 20:46:49 +0100
> From: martinko <[EMAIL PROTECTED]>
>
> Kevin Oberman wrote:
>
> >>Date: Sat, 17 Dec 2005 18:14:01 +0100
> >>From: martinko <[EMAIL PROTECTED]>
> >>
> >>Kevin Oberman wrote:
> >>
> >>
> Date: Fri, 16 Dec 2005 14:29:39 -0600
> From: Craig Boston
Uwe Laverenz wrote:
On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote:
It looks like in the course of writing your long email you forgot to
describe any of the problems you are having.
I don't know his exact problems either, but I could name you a few
examples that currently reduc
On Sunday 18 December 2005 20:46, martinko wrote:
> # sysctl hw.acpi.cpu
> hw.acpi.cpu.cx_supported: C1/1
> hw.acpi.cpu.cx_lowest: C1
> hw.acpi.cpu.cx_usage: 100.00%
>
> and, imho, cx_supported should list all available states, doesn't matter
> what is in rc.conf. (well, at least i reckon it's sup
Kevin Oberman wrote:
Date: Sat, 17 Dec 2005 18:14:01 +0100
From: martinko <[EMAIL PROTECTED]>
Kevin Oberman wrote:
Date: Fri, 16 Dec 2005 14:29:39 -0600
From: Craig Boston <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
-cpu0: on acpi0
+cpu0: on acpi0
Q: Guessing that's a for
Thanks to the email from some kind members here, it is likely that my
problems are not fatal, just temporarily blocking me. I plan to do
another attempt on Mt 6.0, with proper planning, base and upper camps,
and of course, porter support.
Thanks to those who wrote.
BillN
__
On Sun, Dec 18, 2005 at 09:55:33AM +, Matthew Seaman wrote:
> Chuck Swiger wrote:
>
> >Upgrading the ports from there was somewhat annoying, as this guy's
> >machine had
> >~400 or so, but deleting them all, and then using "pkg_add -r " works just
> >fine
> >if you want to grab the latest cu
On Sun, Dec 18, 2005 at 03:02:58PM +0100, Uwe Laverenz wrote:
> On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote:
>
> > It looks like in the course of writing your long email you forgot to
> > describe any of the problems you are having.
>
> I don't know his exact problems either, bu
On Sunday 18 December 2005 15:02, Uwe Laverenz wrote:
> On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote:
> > It looks like in the course of writing your long email you forgot to
> > describe any of the problems you are having.
>
> I don't know his exact problems either, but I could na
Uwe,
On Sun, 18 Dec 2005, Uwe Laverenz wrote:
> On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote:
>
> > It looks like in the course of writing your long email you forgot to
> > describe any of the problems you are having.
>
> I don't know his exact problems either, but I could name yo
On Sat, Dec 17, 2005 at 06:44:48PM -0500, Kris Kennaway wrote:
> It looks like in the course of writing your long email you forgot to
> describe any of the problems you are having.
I don't know his exact problems either, but I could name you a few
examples that currently reduce the fun of using F
Chuck Swiger wrote:
Upgrading the ports from there was somewhat annoying, as this guy's machine had
~400 or so, but deleting them all, and then using "pkg_add -r " works just fine
if you want to grab the latest current binaries. From there you can portupgrade
as usual.
Now, if you want to talk
Hi,
Scott Long wrote:
Peter Jeremy wrote:
I think FreeBSD Update shows the way forward but IMHO there needs to
be an "official" binary update tool accessible from www.freebsd.org.
FreeBSD Update was written by, and is continuously maintained by the
actual FreeBSD Security Officer. It's as
On Sat, Dec 17, 2005 at 02:00:21PM -0800 I heard the voice of
Joe Rhett, and lo! it spake thus:
>
> Increasing the number of deployed systems out of date [...]
This doesn't make any sense. If you install a 6.0 system, in 6 months
(assuming you installed it right when 6.0 was cut, for simplicity)
On Sat, 2005-Dec-17 18:19:25 -0700, Scott Long wrote:
>Peter Jeremy wrote:
>>I think FreeBSD Update shows the way forward but IMHO there needs to
>>be an "official" binary update tool accessible from www.freebsd.org.
>
>FreeBSD Update was written by, and is continuously maintained by the
>actual Fr
Peter Jeremy wrote:
On Sat, 2005-Dec-17 23:35:34 +0100, Kövesdán Gábor wrote:
I agree. And after all, tracking a security branch isn't too difficult,
...
# cd /usr/src
# patch < /path/to/patch
# cd /usr/src/gnu/usr.bin/cvs/cvsbug
# make obj && make depend && make && make install
# cd /usr/s
On Sunday 18 December 2005 01:13, Kevin Oberman wrote:
> > Date: Sat, 17 Dec 2005 18:14:01 +0100
> > From: martinko <[EMAIL PROTECTED]>
> >
> > Kevin Oberman wrote:
> > >>Date: Fri, 16 Dec 2005 14:29:39 -0600
> > >>From: Craig Boston <[EMAIL PROTECTED]>
> > >>Sender: [EMAIL PROTECTED]
> > >>
> > >>
> Date: Sat, 17 Dec 2005 18:14:01 +0100
> From: martinko <[EMAIL PROTECTED]>
>
> Kevin Oberman wrote:
> >>Date: Fri, 16 Dec 2005 14:29:39 -0600
> >>From: Craig Boston <[EMAIL PROTECTED]>
> >>Sender: [EMAIL PROTECTED]
> >>
> >>
> >>>-cpu0: on acpi0
> >>>+cpu0: on acpi0
> >>>
> >>>Q: Guessing that
> From: George Hartzell <[EMAIL PROTECTED]>
> Date: Fri, 16 Dec 2005 16:05:51 -0800
>
> Kevin Oberman writes:
> > [...]
> > No. There is no conflict between Cx states and EST. Cx states specifies
> > how deeply the CPU will sleep when idle. EST controls processor speed
> > and voltage. In most
Joe Rhett wrote:
> On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote:
>>There will be three FreeBSD 6 releases in 2006.
>
> While this is nice, may I suggest that it is time to put aside/delay one
> release cycle and come up with a binary update mechanism supported well by
> the OS? Incr
On Sat, Dec 17, 2005 at 02:00:21PM -0800, Joe Rhett wrote:
> On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote:
> > There will be three FreeBSD 6 releases in 2006.
>
> While this is nice, may I suggest that it is time to put aside/delay one
> release cycle and come up with a binary update
On Sat, Dec 17, 2005 at 10:23:05AM -0800, Bill Nicholls wrote:
> Let me add my voice to this discussion. I have been a happy user of
> FreeBSD from 4.0 thru 4.11, but have stumbled repeatedly on 5.x and now 6.0.
It looks like in the course of writing your long email you forgot to
describe any of
On Sat, 2005-Dec-17 23:35:34 +0100, Kövesdán Gábor wrote:
>I agree. And after all, tracking a security branch isn't too difficult,
...
># cd /usr/src
># patch < /path/to/patch
># cd /usr/src/gnu/usr.bin/cvs/cvsbug
># make obj && make depend && make && make install
># cd /usr/src/gnu/usr.bin/send-p
Bill Nicholls wrote:
> Let me add my voice to this discussion. I have been a happy user of
> FreeBSD from 4.0 thru 4.11, but have stumbled repeatedly on 5.x and now
> 6.0.
>
> For some reason, I can get these (5 & 6) installed, but not stable or
> running KDE, yet 4.11 runs solid for months. In ad
1 - 100 of 133 matches
Mail list logo
