Hi,
> What about the SLUB/SLAB issue, is that solved?
I've not had time to revert that single bad commit yet and do a test - unless
the default m68k config gets changed to use SLAB it'll remain an issue.
I'll let you all know as soon as I have a solution, depend on that.
(And no, I'm not bac
On Wed, Mar 02, 2011 at 02:31:48AM +1100, Finn Thain wrote:
> At present, if MacOS is not in use, you can just use UTC. Whereas, the
> kernel would have to store the timezone in PRAM when it wrote to the RTC
> if were to depend on a valid timezone there. And I'm not sure that the
> kernel even
On Tue, 1 Mar 2011, Thorsten Glaser wrote:
> Geert Uytterhoeven dixit:
>
> >So can't you hack MacOS to consider the RTC in UTC, cfr. the unixclock
>
> If it’s true that the timezone is stored there as well
I'll assume for the moment that it is true (for System 7)...
> , this isn’t actually ne
Finn Thain dixit:
>Wow. That sucks rocks through a straw. I wonder if only ext4 has broken
>read-only mounts?
AFAIHH read-only mounts in Linux are only for data, not for
metadata (mika from Grml cursed a lot about it). The kernel
at least does journal replays for journalled filesystems that
are
On Mon, Feb 28, 2011 at 23:54, Scott Holder wrote:
> On 2/28/2011 5:45 PM, Thorsten Glaser wrote:
>>
>>
>> I think that distributions run hwclock, check filesystems,
>> then run hwclock again, even. But, see above, it may not
>> be enough. I seem to recall an answer from that discussion
>> simply
On Mon, 28 Feb 2011, Thorsten Glaser wrote:
> Geert Uytterhoeven dixit:
>
> > On Mon, Feb 28, 2011 at 04:34, Finn Thain
> > wrote:
> >
> > > It doesn't matter what the clock says if root is read-only.
>
> I think the problem is that the root filesystem is never really
> read-only because the
On 2/28/2011 5:45 PM, Thorsten Glaser wrote:
I think that distributions run hwclock, check filesystems,
then run hwclock again, even. But, see above, it may not
be enough. I seem to recall an answer from that discussion
simply saying to “fix your clock”, so, it may be the kernel
that needs to se
Geert Uytterhoeven dixit:
>On Mon, Feb 28, 2011 at 04:34, Finn Thain wrote:
>> It doesn't matter what the clock says if root is read-only.
I think the problem is that the root filesystem is never really
read-only because the kernel does journal replays and things
like that, too eatly (there was
On Mon, 28 Feb 2011, I wrote:
>
> On Mon, 28 Feb 2011, Michael Tomkins wrote:
>
> > >
> > > Doesn?t the kernel set the clock now, before that?
> >
> > Yes,
>
> Well, this won't work correctly unless your RTC is in UTC, and MacOS
> uses localtime not UTC.
I think you would run "hwclock --s
On Mon, 28 Feb 2011, Geert Uytterhoeven wrote:
> Isn't the check on the rootfs done _before_ hwclock runs?
I don't know how squeeze does things, but I hope to find out.
Finn
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact list
On Mon, Feb 28, 2011 at 04:34, Finn Thain wrote:
> On Mon, 28 Feb 2011, Thorsten Glaser wrote:
>> Finn Thain dixit:
>> >> > Doesn?t the kernel set the clock now, before that?
>> >>
>> >> Yes,
>> >
>> >Well, this won't work correctly unless your RTC is in UTC, and MacOS
>> >uses localtime not UTC.
On Mon, 28 Feb 2011, Thorsten Glaser wrote:
> Finn Thain dixit:
>
> >> > Doesn?t the kernel set the clock now, before that?
> >>
> >> Yes,
> >
> >Well, this won't work correctly unless your RTC is in UTC, and MacOS
> >uses localtime not UTC.
>
> Sucks?
I don't see the problem with localtime?
Finn Thain dixit:
>> > Doesn?t the kernel set the clock now, before that?
>>
>> Yes,
>
>Well, this won't work correctly unless your RTC is in UTC, and MacOS uses
>localtime not UTC.
Sucks…
>> but seems to have a out by -1 on the month. Date was set to ~28 Feb 8:50
FWIW this works fine on AR
On Mon, 28 Feb 2011, Michael Tomkins wrote:
>
> >
> > > be that debian is misconfigured (it thinks the hardware clock is in
> > > UTC but it is actually localtime. MacOS uses localtime so
> > > dual-booting means you have to tell Linux about this).
> >
> > I think the configuration for Linux
On 28/02/2011, at 1:38 AM, Thorsten Glaser wrote:
Finn Thain dixit:
On Sun, 27 Feb 2011, Michael Tomkins wrote:
Decided to compile the stable: 2.6.37.1 from kernel.org and it
compiled
straight out of a "make oldconfig ; make vmlinux modules
modules_install" using Thorsten's 2.6.32 .config
On Sun, 27 Feb 2011, Thorsten Glaser wrote:
> Doesn?t the kernel set the clock now, before [userland]?
Yes, it will if you configure the kernel at build time with
CONFIG_RTC_HCTOSYS and the appropriate CONFIG_RTC_HCTOSYS_DEVICE. This
device must use UTC and the relevant RTC driver must be buil
Finn Thain dixit:
>On Sun, 27 Feb 2011, Michael Tomkins wrote:
>
>> Decided to compile the stable: 2.6.37.1 from kernel.org and it compiled
>> straight out of a "make oldconfig ; make vmlinux modules
>> modules_install" using Thorsten's 2.6.32 .config! Although it did take 3
What about the SLU
Hi Michael,
On Sun, 27 Feb 2011, Michael Tomkins wrote:
> Decided to compile the stable: 2.6.37.1 from kernel.org and it compiled
> straight out of a "make oldconfig ; make vmlinux modules
> modules_install" using Thorsten's 2.6.32 .config! Although it did take 3
> days on a quadra 650/605/60
Decided to compile the stable: 2.6.37.1 from kernel.org and it
compiled straight out of a "make oldconfig ; make vmlinux modules
modules_install" using Thorsten's 2.6.32 .config! Although it did take
3 days on a quadra 650/605/605 cluster (so its mac only?). Kernel and
modules are here http
19 matches
Mail list logo
