Yoshinori K. Okuji wrote:
>Only if you prove that the current implementation does not work, I will
>consider it.
>
>I have already investigated how other systems deal with Gate A20. For example,
>Linux does not do such a thing, but nobody has reported that it does not
>work.
>
>
>
Ok. after a
On Sunday 14 August 2005 09:47, Vladimir Serbinenko wrote:
> >Do you mean 80386? Of course, no. I don't have such an old CPU.
> But some people use old PC like a home servers.
So?
> Perhaps if we read a huge block of memory it will do the trick?
Only if you prove that the current implementation
Yoshinori K. Okuji wrote:
>
>Do you mean 80386? Of course, no. I don't have such an old CPU.
>
>
>
But some people use old PC like a home servers. But 80386 I
suppose is not very used because it can't have more than a few
hundred Mb hard disk, which is important criteria for home server,
more im
On Thursday 11 August 2005 16:47, Vladimir Serbinenko wrote:
> Has anybody tested grub2 on i386 processor? Do you think that 2
> microseconds will
> invalidate the cache if processor is waiting?
Do you mean 80386? Of course, no. I don't have such an old CPU.
AFAIK, this problem may happen only in
Yoshinori K. Okuji wrote:
>
>Besides that, we must learn from the history. Many years ago, nobody could
>imagine that computers would have more than 1MB memory. So the braindead Gate
>A20 had to be invented. Likewise, nobody could imagine that hard disks would
>exceed 500MB. So LBA mode had to
On Thursday 11 August 2005 13:22, Marco Gerards wrote:
> > I also don't think we could find any file big enough to need 3 levels of
> > indirection.
>
> It can be a problem if someone uses the loopback command.
It's a good example.
Besides that, we must learn from the history. Many years ago, nob
Vincent Pelletier <[EMAIL PROTECTED]> writes:
> Marco Gerards wrote:
>> Can you tell me how to reproduce it?
>
> I had problems with one of those (damn, I can't remember now) on 720kB
> floppy (erm... not really important by itself, but couldn't it be a
> symptom of a deeper bug ?) but it was a wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Gerards wrote:
> Can you tell me how to reproduce it?
I had problems with one of those (damn, I can't remember now) on 720kB
floppy (erm... not really important by itself, but couldn't it be a
symptom of a deeper bug ?) but it was a while ago -
Vincent Pelletier <[EMAIL PROTECTED]> writes:
> Vladimir Serbinenko wrote:
>> Try to make an fsck on this partition and repair the errors if any.
>> If it doesn't work could you send the characteristics of your ext3 FS?
>> (like size)
>
> I'm quite sure there is a bug in ext fs handler (and probab
On Wednesday 10 August 2005 23:50, Vernon Mauery wrote:
> the CVS version gives me the "Welcome to GRUB!" banner and then an
> "unaligned pointer 0x7ff58". Instant death.
Hmmh, strange. I cannot reproduce it. Can you send the file config.log? This
might depend on the build environment.
Okuji
Yoshinori K. Okuji wrote:
> On Wednesday 10 August 2005 18:06, Vernon Mauery wrote:
>
>>I am seeing unaligned pointer messages when I use grub2 on /dev/hda2. If I
>>type 'root (hd0,2)', I get 'unaligned pointer 0x7ff94' and if I type
>>'insmod (hd0,2)/boot/grub/mulitboot.mod', I get 'unaligned po
On Wednesday 10 August 2005 18:06, Vernon Mauery wrote:
> I am seeing unaligned pointer messages when I use grub2 on /dev/hda2. If I
> type 'root (hd0,2)', I get 'unaligned pointer 0x7ff94' and if I type
> 'insmod (hd0,2)/boot/grub/mulitboot.mod', I get 'unaligned pointer
> 0x7ff64'.
Thank you fo
Vladimir Serbinenko wrote:
>
> Try to make an fsck on this partition and repair the errors if any.
> If it doesn't work could you send the characteristics of your ext3 FS?
> (like size)
fsck says the filesystem is clean.
bluecow:/home/vhmauery# fdisk -l
Disk /dev/hda: 80.0 GB, 80032038912 byte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir Serbinenko wrote:
> Try to make an fsck on this partition and repair the errors if any.
> If it doesn't work could you send the characteristics of your ext3 FS?
> (like size)
I'm quite sure there is a bug in ext fs handler (and probably fat),
Vernon Mauery wrote:
>Vincent Pelletier wrote:
>
>
>>Vernon Mauery wrote:
>>
>>
>>
I am seeing unaligned pointer messages when I use grub2 on /dev/hda2.
If I type 'root (hd0,2)', I get 'unaligned pointer 0x7ff94' and if I
type 'insmod (hd0,2)/boot/grub/mulitboot.mod', I get 'unal
Vincent Pelletier wrote:
> Vernon Mauery wrote:
>
>>>I am seeing unaligned pointer messages when I use grub2 on /dev/hda2.
>>>If I type 'root (hd0,2)', I get 'unaligned pointer 0x7ff94' and if I
>>>type 'insmod (hd0,2)/boot/grub/mulitboot.mod', I get 'unaligned
>>>pointer 0x7ff64'.
>
>
> Sounds
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vernon Mauery wrote:
> I am seeing unaligned pointer messages when I use grub2 on /dev/hda2.
> If I type 'root (hd0,2)', I get 'unaligned pointer 0x7ff94' and if I
> type 'insmod (hd0,2)/boot/grub/mulitboot.mod', I get 'unaligned
> pointer 0x7ff64'.
S
Yoshinori K. Okuji wrote:
> I'm happy to announce the release of GRUB 1.90. This is the first of
> our prereleases leading up to GRUB 2.0. We encourage you to try it, as
> we have done a significant amount of work towards GRUB 2. Note that this
> release is mainly for developers who are willing to
On Aug 9, 2005, at 1:42 PM, Yoshinori K. Okuji wrote:
On Tuesday 09 August 2005 15:43, Hollis Blanchard wrote:
You mentioned you wanted to release something "in the beginning of
August." There was no rush this weekend, and I think it would have
been
polite to give people time to fix the PPC b
"Yoshinori K. Okuji" <[EMAIL PROTECTED]> writes:
> As long as GRUB 2 is at a developmental phase, I'd like to keep the policy of
> making releases regularly, regardless of the status. That's because I know
> that releases can be extremely delayed, once I accept to put a delay.
Even when you car
"Yoshinori K. Okuji" <[EMAIL PROTECTED]> writes:
> On Tuesday 09 August 2005 16:21, Marco Gerards wrote:
>> Perhaps it is a good idea to send the announcement to info-gnu as
>> well, to attract more developers.
>
> I thought info-gnu is only for stable versions... Isn't it?
It is not for test rel
On Tuesday 09 August 2005 15:43, Hollis Blanchard wrote:
> You mentioned you wanted to release something "in the beginning of
> August." There was no rush this weekend, and I think it would have been
> polite to give people time to fix the PPC build before releasing.
I'm sorry, but I must insist m
On Tuesday 09 August 2005 16:21, Marco Gerards wrote:
> Perhaps it is a good idea to send the announcement to info-gnu as
> well, to attract more developers.
I thought info-gnu is only for stable versions... Isn't it?
Okuji
___
Grub-devel mailing list
Hollis Blanchard <[EMAIL PROTECTED]> writes:
>> Anyway, I had
>> already mentioned that I would release it regardless of the status,
>> and the
>> PC support is the priority. Don't complain afterwards.
>
> You mentioned you wanted to release something "in the beginning of
> August." There was no r
On Aug 9, 2005, at 1:32 AM, Yoshinori K. Okuji wrote:
On Tuesday 09 August 2005 05:21, Hollis Blanchard wrote:
On Aug 7, 2005, at 12:39 PM, Yoshinori K. Okuji wrote:
I'm happy to announce the release of GRUB 1.90.
I'm disappointed that you chose to announce GRUB 1.90 after knowingly
breaking
On Tuesday 09 August 2005 05:21, Hollis Blanchard wrote:
> On Aug 7, 2005, at 12:39 PM, Yoshinori K. Okuji wrote:
> > I'm happy to announce the release of GRUB 1.90.
>
> I'm disappointed that you chose to announce GRUB 1.90 after knowingly
> breaking the PPC build.
Do not forget that you broke it
On Aug 7, 2005, at 12:39 PM, Yoshinori K. Okuji wrote:
I'm happy to announce the release of GRUB 1.90.
I'm disappointed that you chose to announce GRUB 1.90 after knowingly
breaking the PPC build.
I have fixed the build.
-Hollis
___
Grub-devel
I'm happy to announce the release of GRUB 1.90. This is the first of
our prereleases leading up to GRUB 2.0. We encourage you to try it, as
we have done a significant amount of work towards GRUB 2. Note that this
release is mainly for developers who are willing to contribute to our
project. If yo
28 matches
Mail list logo