I'd like to note that this discussion should probably be moved to
bug-hurd, as that's the appropriate list.
Daniel Borgmann <[EMAIL PROTECTED]> wrote:
> On Mon, 2002-06-17 at 12:31, Wolfgang Jährling wrote:
> > I don't think it should be a pipe. It should make it possible for
> > applications to
Daniel Borgmann <[EMAIL PROTECTED]> writes:
> That sounds like a good plan. Any thoughts how this should work in
> detail? I mean, should the translator just be something like a "pipe" to
> the video memory or should it already provide drawing functions?
One could start with saying that it should
On Mon, 2002-06-17 at 12:31, Wolfgang Jährling wrote:
> > I mean, should the translator just be something like a "pipe" to
> > the video memory or should it already provide drawing functions? Should
> > it allow access from every application?
>
> I don't think it should be a pipe. It should make
Daniel Borgmann <[EMAIL PROTECTED]> wrote:
> That sounds like a good plan.
It is our plan, so obviously it must be good. ;-)
> I mean, should the translator just be something like a "pipe" to
> the video memory or should it already provide drawing functions? Should
> it allow access from every ap
On Mon, 2002-06-17 at 09:42, Niels Möller wrote:
> > The idea seems to be to use memory mapping and a translator so
> > applications can just write to this translator to access the video
> > memory. The kernel would than directly talk to the
> > hardware, for example through a VESA driver. Is that
Daniel Borgmann <[EMAIL PROTECTED]> writes:
> The idea seems to be to use memory mapping and a translator so
> applications can just write to this translator to access the video
> memory. The kernel would than directly talk to the
> hardware, for example through a VESA driver. Is that correct?
Mo
Hi Marcus,
Sunday, June 16, 2002, 6:14:30 PM, you wrote:
>> kernel /boot/gnumach.gz root=hd0s2
>> -T typed ${root}
MB> Shouldn't this be "root=device:hd0s@" because of the "typed"?
This works, great! Hm, just looked at the installation guide and it
also says device:hd0sx... Don't know
On Sat, Jun 15, 2002 at 10:30:58AM +0200, Daniel Borgmann wrote:
> kernel /boot/gnumach.gz root=hd0s2
> -T typed ${root}
Shouldn't this be "root=device:hd0s@" because of the "typed"?
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED]
Marcus Brinkman
Hello,
On Sat, 2002-06-15 at 11:30, Kapil Hari Paranjape wrote:
> > --- snip ---
> > title GNU/Hurd
> > root(hd0,1)
> > kernel /boot/gnumach.gz root=hd0s2
> > module /hurd/ext2fs.static
> > --multiboot-command-line=${kernel-command-line}
> > --host-priv-port=${hos
> When I try to boot using the module statements from the installation
> instructions (I did copy and paste), it always hangs up. The message
> where it hangs up is:
> "start /hurd/ext2fs.static:"
> right after loading the modules.
>
> This is pasted from my menu.lst:
>
> --- snip ---
> title
Hello,
On Sat, Jun 15, 2002 at 10:30:58AM +0200, Daniel Borgmann wrote:
> This is pasted from my menu.lst:
>
> --- snip ---
> title GNU/Hurd
> root(hd0,1)
> kernel /boot/gnumach.gz root=hd0s2
> module /hurd/ext2fs.static
> --multiboot-command-line=${kernel-comman
Hello list!
Since yesterday I have the Hurd running and so far I like it (very
interesting to start learning Hurd-hacking). There is just one glitch so
and I thought it might not hurd.. err... hurt to ask you about it.
When I try to boot using the module statements from the installation
instructi
12 matches
Mail list logo
