Bartosz Fabianowski wrote:
the same device that FreeBSD used to identify as "IPOD" is now
identified as "Rockbox"
The Rockbox USB code keeps changing with each build - it used to
request power (using its own USB stack) until very recently for me,
but as of a couple of days ago, reboots into t
the same device that FreeBSD used to identify as "IPOD" is now
identified as "Rockbox"
The Rockbox USB code keeps changing with each build - it used to request
power (using its own USB stack) until very recently for me, but as of a
couple of days ago, reboots into the original firmware again.
Just wanted to correct an error in my original note; I intended to
suggest that a change in Rockbox had caused this problem, not rsync.
Bartosz picked up on that immediately. Regarding your note, I think
that the Rockbox USB stack may in fact be running by default in the
newest releases.
I think that this is related to some changes on the rsync end,
specifically their "New USB stack with limited capability".
The new USB stack is not enabled by default. Rockbox still reboots the
iPod into emergency disk mode when USB is plugged in, just like it
always did.
That said, Apple's
Hi all,
I'm running FreeBSD 7.0 on a home file server that holds, among a
bunch of other stuff, my music collection. I occasionally hook up my
iPod Video (5.5) to charge and to synchronize files using rsync; I've
got Rockbox (http://www.rockbox.org/) running on the iPod. For as long
as I
Hi all
I`ve tried to install FreeBSD 7 on Compaq Proliant ML330 G2 server, but
it won`t boot. FreeBSD boot0 beeps after pressing F1, or F2 (got 2
partitions) key. So i`ve installed grub on another machine, but than it
says "Error 5" only in Proliant, I don`t even get grub command prompt.
HDD
I believe I've found a bug in the libgcc or libstdc++ library (not sure
which one) packaged with the gcc43 port in fbsd7 on an Intel x86-64. A
program linked against those libraries aborts when an exception is thrown.
It does not abort if -lpthread is added to the link line, even though the
progra
On Fri, Apr 04, 2008 at 07:46:05PM +0200, Guido van Rooij wrote:
>I've got a amd64 system where I;m using powernow. I am using th i8254
>timecounter.
I'm using ACPI-fast on amd64 without problems. i8254 should not be
affected by PowerNow! but ACPI-fast should be listed as preferable.
Do you have
On 04/04/2008, John Baldwin <[EMAIL PROTECTED]> wrote:
> On Thursday 28 February 2008 05:56:32 pm pluknet wrote:
> > Hello,
> >
> > I've updated to the recent RELENG_7 as of 2008/02/28
> > to try the new kld-add feature in kgdb, among other things
> > (yes, i do debug kernel modules).
>
>
> Th
On Fri, Apr 04, 2008 at 07:46:05PM +0200, Guido van Rooij wrote:
> I've got a amd64 system where I;m using powernow. I am using th i8254
> timecounter. I keep getting time resets from ntp:
I don't think the i8254 should be effected by the i8254. Are there
any other choices listed under kern.timeco
I've got a amd64 system where I;m using powernow. I am using th i8254
timecounter. I keep getting time resets from ntp:
Apr 4 01:13:27 gvr ntpd[96120]: kernel time sync enabled 6001
Apr 4 01:30:21 gvr ntpd[96120]: kernel time sync enabled 2001
Apr 4 03:28:25 gvr ntpd[96120]: time reset -10.5876
On Fri, Apr 04, 2008 at 10:58:40AM +0200, Ivan Voras wrote:
> >> Signing binaries could be naturally tied in with securelevel, where some
> >> securelevel (1?) would mean kernel no longer accepts new keys.
> >
> > If you set the system immutable flag on the binaries, you cannot modify
> > them at
Ivan Voras-7 wrote:
>
> jbsnyder wrote:
>> Hi -
>>
>> I'm not yet filing a PR on this since I'm wondering if anyone else has
>> experienced this issue. I've got ZFS running on a raid-z with 4 disks,
>> C2Duo 2.33 Ghz, 64-bit FreeBSD 7 release, 4GB RAM. For the most part
>> this
>> has been wo
Maks Verver wrote:
> I recently encountered an error, where executing the ImageMagick
> "convert"
> tool as an unpriviliged user caused the system to hang.
>
> The error is similar to one reported in 2004:
>
I had exactly the same problem recently under FreeBSD-6.3. I don't know
if the problem
On Thu, 3 Apr 2008 20:37:44 -0300 Nenhum_de_Nos wrote:
> I'd like to run folding at home on FreeBSD (my OS of choice) and I
> have this problem of needing to run a amd64 binary. all I saw when
> emulating on freebsd was a 32 bits linux enviroment, and all I found
> about amd64 enviroment for amd64
Roland Smith wrote:
> On Thu, Apr 03, 2008 at 01:46:39PM +0200, Ivan Voras wrote:
>> Roland Smith wrote:
>>> On Wed, Apr 02, 2008 at 03:09:59PM -0400, Forrest Aldrich wrote:
Does FreeBSD have support for digitally signed binary checking, similar to
what Linux has with bsign and DigSig, w
16 matches
Mail list logo
