On Sunday 22 March 2009 21:50:22 Yoshinori K. Okuji wrote:
> On Sunday 22 March 2009 21:29:23 Robert Millan wrote:
> > On Sun, Mar 22, 2009 at 04:01:35PM +0900, Yoshinori K. Okuji wrote:
> > > I will work towards this direction. I will first fix up the sector
> > > handling and change the format to
On Sunday 22 March 2009 22:23:53 phcoder wrote:
> Yoshinori K. Okuji wrote:
> > On Sunday 22 March 2009 19:48:36 phcoder wrote:
> >> Hello, I agree that non-sector aligned writes should be handled
> >> correctly. However I disagree with removing of the magic number. I
> >> personally would prefer i
Yoshinori K. Okuji wrote:
On Sunday 22 March 2009 19:48:36 phcoder wrote:
Hello, I agree that non-sector aligned writes should be handled
correctly. However I disagree with removing of the magic number. I
personally would prefer if this file would have magic number and
checksum. AFAIK currently
On Sunday 22 March 2009 19:48:36 phcoder wrote:
> Hello, I agree that non-sector aligned writes should be handled
> correctly. However I disagree with removing of the magic number. I
> personally would prefer if this file would have magic number and
> checksum. AFAIK currently grub2 doesn't write t
On Sunday 22 March 2009 21:29:23 Robert Millan wrote:
> On Sun, Mar 22, 2009 at 04:01:35PM +0900, Yoshinori K. Okuji wrote:
> > I will work towards this direction. I will first fix up the sector
> > handling and change the format to plain text. Naming changes are quite
> > trivial, so they can be d
On Sun, Mar 22, 2009 at 04:01:35PM +0900, Yoshinori K. Okuji wrote:
>
> I will work towards this direction. I will first fix up the sector handling
> and change the format to plain text. Naming changes are quite trivial, so
> they can be done later.
I notice some changes went in for the new imp
Hello, I agree that non-sector aligned writes should be handled
correctly. However I disagree with removing of the magic number. I
personally would prefer if this file would have magic number and
checksum. AFAIK currently grub2 doesn't write to FS except in
load_env/save_env so a bug in code ca
On Sunday 15 March 2009 14:52:05 Bean wrote:
> On Sun, Mar 15, 2009 at 5:10 AM, Yoshinori K. Okuji wrote:
> > On Friday 13 March 2009 21:23:19 phcoder wrote:
> >> Look at load_env/save_env commands and grub-editenv util
> >
> > Thanks. Now I really regret that I didn't find those additions earlier
On Sun, Mar 15, 2009 at 5:10 AM, Yoshinori K. Okuji wrote:
> On Friday 13 March 2009 21:23:19 phcoder wrote:
>> Look at load_env/save_env commands and grub-editenv util
>
> Thanks. Now I really regret that I didn't find those additions earlier.
>
> I do not like this implementation for the followi
On Friday 13 March 2009 21:23:19 phcoder wrote:
> Look at load_env/save_env commands and grub-editenv util
Thanks. Now I really regret that I didn't find those additions earlier.
I do not like this implementation for the following reasons:
- The saved file is not plain text, unlike GRUB Legacy.
Look at load_env/save_env commands and grub-editenv util
Yoshinori K. Okuji wrote:
On Thursday 05 March 2009 05:59:52 Robert Millan wrote:
We don't need a complete match of all the GRUB Legacy features in order to
migrate. The things I identified as needed for migration in Debian are
listed her
On Thursday 05 March 2009 05:59:52 Robert Millan wrote:
> We don't need a complete match of all the GRUB Legacy features in order to
> migrate. The things I identified as needed for migration in Debian are
> listed here:
>
> http://wiki.debian.org/GrubTransition
>
> I think Xen is fixed now thou
On Sun, Mar 01, 2009 at 06:15:43PM +0100, phcoder wrote:
> I personally see following features still missing from grub2 comparing
> to grub1:
> -network
Notice that in the GRUB Legacy shipped by Debian, network is disabled anyway
(without module support, you can't ship a prebuilt image that supp
On Sat, Feb 28, 2009 at 11:28:05PM -0500, Pavel Roskin wrote:
> On Sat, 2009-02-28 at 12:54 +0100, phcoder wrote:
> > Robert Millan wrote:
> > > Seems nice. Would you be willing to write a summary for these? Then we
> > > could add it to grub-soc.html.
> > Where is this file?
> > Here is elaborat
On Sat, Feb 28, 2009 at 7:54 PM, phcoder wrote:
> ...
>
...
> Scripts:
> -Finish scripting engine, loops, functions, pipes,...
> Scripting engine is still incomplete
> -Runtime autoconfig.
> It scans all the drives and creates a list of detected OSes in grub2. Very
> useful for demonstrations and
I personally see following features still missing from grub2 comparing
to grub1:
-network
It's in the list
-lock
It's more a question of discussing design that actually coding
-simple partition manipulation
I started a design discussion about this subject but nobody seems to be
interested. If I
liu Aleaxander wrote:
can Implementing a chinese supported grub be a grub-soc idea?
thanks.
No. Because it's already done
On Wed, Feb 25, 2009 at 7:59 PM, phcoder wrote:
Some other ideas:
HID:
-bluetooth keyboard
-mouse support
More graphics drivers
FS:
-btrfs
-Hammer (dragonflybsd)
Networ
can Implementing a chinese supported grub be a grub-soc idea?
thanks.
On Wed, Feb 25, 2009 at 7:59 PM, phcoder wrote:
> Some other ideas:
> HID:
> -bluetooth keyboard
> -mouse support
> More graphics drivers
> FS:
> -btrfs
> -Hammer (dragonflybsd)
> Network
> -TFTP
> -TCP/IP
> --NFS
> --SMB
> -
On Sat, 2009-02-28 at 12:54 +0100, phcoder wrote:
> Robert Millan wrote:
> > Seems nice. Would you be willing to write a summary for these? Then we
> > could add it to grub-soc.html.
> Where is this file?
> Here is elaborated list:
In my opinion, matching all features of GRUB 1 on i386-pc should
Robert Millan wrote:
Seems nice. Would you be willing to write a summary for these? Then we
could add it to grub-soc.html.
Where is this file?
Here is elaborated list:
HID:
-bluetooth keyboard
Often BIOS lacks bluetooth support completely. This means that if
someone uses bluetooth keyboard he
On Wed, Feb 25, 2009 at 12:59:31PM +0100, phcoder wrote:
> Hello. Marco Gerards already agreed that this port is ok. I made some
> investigations into their code and have to say that it won't be just a
> port. It seems that some features (e.g. directory listing) are missing.
> It also uses di
Hello. Marco Gerards already agreed that this port is ok. I made some
investigations into their code and have to say that it won't be just a
port. It seems that some features (e.g. directory listing) are missing.
It also uses dirty tricks which limit their code to one opened file in
time. All t
22 matches
Mail list logo
