Re: Grub-devel Digest, Vol 26, Issue 1

[Z3tbl4 []]

Christian Laursen, nobody could help you HERE, i tried to get some
help about week with no result. but i still don't loose a hope.

2006/4/1, address@hidden <address@hidden>:
> Send Grub-devel mailing list submissions to
>        address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.gnu.org/mailman/listinfo/grub-devel
> or, via email, send a message with subject or body 'help' to
>        address@hidden
>
> You can reach the person managing the list at
>        address@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Grub-devel digest..."
>
>
> Today's Topics:
>
>   1. Problem building grub 1.93 on FreeBSD (Christian Laursen)
>   2. [patch] fixed menu so you can use it... (Vesa J??skel?inen)
>   3. Re: [patch] fixed menu so you can use it... (Marco Gerards)
>   4. TCP timers and telnet (Marco Gerards)
>   5. Re: TCP timers and telnet (Yoshinori K. Okuji)
>   6. Re: TCP timers and telnet (Marco Gerards)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 31 Mar 2006 19:48:01 +0200
> From: Christian Laursen <address@hidden>
> Subject: Problem building grub 1.93 on FreeBSD
> To: The development of GRUB 2 <address@hidden>
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> I am attempting to build grub 1.93 on FreeBSD but are experiencing problems
> when trying to tell the configure script where to find the LZO library.
>
> Lzo 2 is installed and located in /usr/local/lib:
>
> -rw-r--r--  1 root  wheel  161066 Mar 31 15:33 /usr/local/lib/liblzo2.a
> -rwxr-xr-x  1 root  wheel     798 Mar 31 15:33 /usr/local/lib/liblzo2.la
> lrwxr-xr-x  1 root  wheel      12 Mar 31 15:33 /usr/local/lib/liblzo2.so -> 
> liblzo2.so.2
> -rwxr-xr-x  1 root  wheel  120428 Mar 31 15:33 /usr/local/lib/liblzo2.so.2
>
> I am defining LDFLAGS and CFLAGS before running ./configure they do not
> seem to be used when trying to detect LZO.
>
> The typescript of the configure run is here:
> http://borderworlds.dk/~xi/grub2/configure.txt
>
> The config.log is here:
> http://borderworlds.dk/~xi/grub2/config.log
>
> As far as I can see, my CFLAGS and LDFLAGS are used in some of the tests
> but not in the last ones when trying to detect LZO. I don't understand
> autoconf enough to figure out how to fix this so any hints would be
> greatly appreciated.
>
> Thanks.
>
> --
> Christian Laursen
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 01 Apr 2006 17:32:42 +0300
> From: Vesa J??skel?inen <address@hidden>
> Subject: [patch] fixed menu so you can use it...
> To: The development of GRUB 2 <address@hidden>
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> I made some fixes to menu. Now you can even select a menu entry :).
>
> There were also some odd code in elsewhere so I fixed some issues
> related to those too.
>
> Thanks,
> Vesa Jääskeläinen
> -------------- next part --------------
> Index: ChangeLog
> ===================================================================
> RCS file: /sources/grub/grub2/ChangeLog,v
> retrieving revision 1.228
> diff -u -r1.228 ChangeLog
> --- ChangeLog   31 Mar 2006 14:26:33 -0000      1.228
> +++ ChangeLog   1 Apr 2006 14:28:58 -0000
> @@ -1,3 +1,9 @@
> +2006-04-01  Vesa Jaaskelainen  <address@hidden>
> +
> +       * normal/main.c (grub_normal_menu_addentry): Fixed menu size
> +       calculation.
> +       (read_config_file): Made it to close file before returning.
> +
>  2006-03-31  Vesa Jaaskelainen  <address@hidden>
>
>        * DISTLIST: Added include/grub/i386/pc/vbeblit.h,
> Index: normal/main.c
> ===================================================================
> RCS file: /sources/grub/grub2/normal/main.c,v
> retrieving revision 1.14
> diff -u -r1.14 main.c
> --- normal/main.c       17 Jan 2006 09:50:47 -0000      1.14
> +++ normal/main.c       1 Apr 2006 14:28:59 -0000
> @@ -153,6 +153,8 @@
>   (*last)->next = 0;
>   (*last)->sourcecode = sourcecode;
>
> +  current_menu->size++;
> +
>   return GRUB_ERR_NONE;
>  }
>
> @@ -223,10 +225,8 @@
>       grub_script_free (parsed_script);
>     }
>
> -  return newmenu;
> -
>   grub_file_close (file);
> -  return 0;
> +  return newmenu;
>  }
>
>  /* This starts the normal mode.  */
>
> ------------------------------
>
> Message: 3
> Date: Sat, 01 Apr 2006 16:37:46 +0200
> From: Marco Gerards <address@hidden>
> Subject: Re: [patch] fixed menu so you can use it...
> To: The development of GRUB 2 <address@hidden>
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=iso-8859-1
>
> Vesa Jääskeläinen <address@hidden> writes:
>
> Hi Vesa,
>
> > I made some fixes to menu. Now you can even select a menu entry :).
> >
> > There were also some odd code in elsewhere so I fixed some issues
> > related to those too.
>
> This looks fine to me.  Please apply it.
>
> Thanks,
> Marco
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 01 Apr 2006 18:15:43 +0200
> From: Marco Gerards <address@hidden>
> Subject: TCP timers and telnet
> To: The development of GRUB <address@hidden>
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> Hi,
>
> Lately I have been reading a bit about Open Firmware and that it has
> TCP support and support to telnet into an Open firmware box:
> http://developer.apple.com/technotes/tn/tn2004.html
>
> So I was thinking, why not add such functionality to GRUB 2?  It's
> easy to implement with the networking code I currently have.  The only
> thing about it that sucks is that we have to implement multitheading,
> kinda...
>
> My idea is that we use the timer interrupt to regularly schedule time
> for the TCP timers and the incoming telnet connections.  It will not
> be very hard to implement, but we have to think about how to do proper
> locking.  We will at least need locking in disk access and for the
> loaders.  So only in a small part of GRUB.
>
> What do you guys think?  I think it is not as hard as it sounds now...
>
> Thanks,
> Marco
>
>
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 1 Apr 2006 18:25:14 +0200
> From: "Yoshinori K. Okuji" <address@hidden>
> Subject: Re: TCP timers and telnet
> To: The development of GRUB 2 <address@hidden>
> Message-ID: <address@hidden>
> Content-Type: text/plain;  charset="iso-8859-1"
>
> On Saturday 01 April 2006 18:15, Marco Gerards wrote:
> > So I was thinking, why not add such functionality to GRUB 2?  It's
> > easy to implement with the networking code I currently have.  The only
> > thing about it that sucks is that we have to implement multitheading,
> > kinda...
>
> I object to multithreading. It makes our life just harder. I prefer an
> event-driven approach as you suggested before.
>
> Okuji
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Sat, 01 Apr 2006 18:30:52 +0200
> From: Marco Gerards <address@hidden>
> Subject: Re: TCP timers and telnet
> To: The development of GRUB 2 <address@hidden>
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> "Yoshinori K. Okuji" <address@hidden> writes:
>
> > On Saturday 01 April 2006 18:15, Marco Gerards wrote:
> >> So I was thinking, why not add such functionality to GRUB 2?  It's
> >> easy to implement with the networking code I currently have.  The only
> >> thing about it that sucks is that we have to implement multitheading,
> >> kinda...
> >
> > I object to multithreading. It makes our life just harder. I prefer an
> > event-driven approach as you suggested before.
>
> My previous suggestion would have worked, if you didn't telnet into
> GRUB.  The current discussion is about having multiple different GRUB
> sessions simultaniously.  So in that case you will need locking, etc.
>
> --
> Marco
>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
> End of Grub-devel Digest, Vol 26, Issue 1
> *****************************************
>