devil-linux-develop — developer discussions

[Devil-linux-develop] [ devil-linux-Bugs-782850 ] new boot process to slow with floppy

[SourceForge.net <no...@so...>]

Bugs item #782850, was opened at 2003-08-04 09:50
Message generated for change (Settings changed) made by smiley73
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=782850&group_id=34096

Category: Configuration / Scripts
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Heiko Zuerker (smiley73)
>Assigned to: Heiko Zuerker (smiley73)
Summary: new boot process to slow with floppy

Initial Comment:
the new boot process is to slow when using a floppy 

drive.

check if memory > 16 MB and then access floppy only 

once.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=782850&group_id=34096

Re: [Devil-linux-develop] vesa

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:
>>>That would be REALLY nice, but I'm not sure it's possible.  The results
>>>for ldconfig & modconfig are both stored in /etc (I think the modules
>>>are in /etc/modules, right?).   That means if someone updated their CD
>>>without creating a new /etc from the fresh tar file, they would have a
>>>ton of problems.
>>
>>That's the main reason why I didn't remove it yet.
> 
> 
> I guess we could move/link those files to the CD, then they can't they
> are matched to the CD, and they can't change (not counting my script).
> If it's even possible to create the resulting files in the build ...


Actually we could just go ahead and leave it to the user to run "depmod 
-a && save-config" .
I'll take a look if I can add some intelligence to depmod.
I'll disable ldconfig for the meantime, we shouldn't need it.


>>>I agree.  I'm still in favor of 5 seconds and no "vga=" by default.
>>
>>Just do it, I can change it later. ;-)
> 
> 
> OK, the changes are committed.
> 
> EVERYONE, update from CVS NOW, before Heiko changes the defaults!  ;->

Too late ! (just kidding)

cya
   Heiko

[Devil-linux-develop] [fmII] Linux FreeS/WAN 2.02 released (Default branch)

[<no...@fr...>]

This email is to inform you about the release of version '2.02' of 'Linux
FreeS/WAN' through freshmeat.net. All URLs and other useful information
can be found at

    http://freshmeat.net/projects/freeswan/

The changes in this release are as follows:
One-line configuration for initiator-only Opportunistic Encryption,
(OE) using ipsec.conf's new "myid" option. There is a new RPM spec
file. This will help folks who need to compile RPMs from the
FreeS/WAN source. In addition, wavesec and OE now coexist nicely. 

Project description:
Linux FreeS/WAN provides IPSEC (IP Security, which is both encryption
and authentication) kernel extensions and an IKE (Internet Key
Exchange, keying and encrypted routing daemon) as well as various rc
scripts and documentation. It is known to interoperate with other
IPSEC and IKE system already deployed by other vendors such as
OpenBSD, Cisco, or CheckPoint. It also features Opportunistic
Encryption, subnet extrusion, and with the appropriate patches
interops nicely with Microsoft Windows XP/2000 using X.509
certificates. 

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects you're
subscribed to in the right column, which you may cancel by highlighting
the project in question and clicking the 'delete' button.

Sincerely,
freshmeat.net 

[Devil-linux-develop] [fmII] OpenVPN 1.4.3 released (Default branch)

[<no...@fr...>]

This email is to inform you about the release of version '1.4.3' of
'OpenVPN' through freshmeat.net. All URLs and other useful information can
be found at

    http://freshmeat.net/projects/openvpn/

The changes in this release are as follows:
An md5.h include has been added to crypto.c to fix a build problem on
OpenBSD. 

Project description:
OpenVPN is a robust and highly configurable VPN (Virtual Private
Network) daemon which can be used to securely link two or more
private networks using an encrypted tunnel over the Internet.
OpenVPN's principal strengths include wide cross-platform
portability, excellent stability, support for dynamic IP addresses
and NAT, adaptive link compression, single TCP/UDP port usage, a
modular design that offloads most crypto tasks to the OpenSSL
library, and relatively easy installation that in most cases doesn't
require a special kernel module.  

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects you're
subscribed to in the right column, which you may cancel by highlighting
the project in question and clicking the 'delete' button.

Sincerely,
freshmeat.net 

RE: [Devil-linux-develop] vesa

[Bruce S. <bw...@ar...>]

> >Most of my DL boxes don't even have a monitor.  I use SSH, and can make
> >the window size & font anything I like.  :-)
> 
> And I have a DL (test) box hooked up to my Bigscreen TV. :-))

Wow!  It's a good thing there isn't a 2560x2048 frame buffer mode, or
you'd make that the default!  ;-)

> >Right, that's why I suggested 5 seconds.  I set my GRUB/LILO prompt
> >timeout at THREE seconds on my Redhat boxes for that reason.
> 
> That's to short for me:
> eye -> brain -> *warm up* - > *anaylize* -> *decide* -> brain -> hand
> 
> *lol*

I have the same problem, which is it's nice that if you press a key at
the "boot:" prompt, it cancels the timeout and waits forever for you to
decide what selection to pick.

I actually find I miss the prompt MORE often, the LONGER I set it!
If it's too long, I think I have time, start doing something else and
miss it!  If it's real short, then I pay closer attention when I boot.

> >That would be REALLY nice, but I'm not sure it's possible.  The results
> >for ldconfig & modconfig are both stored in /etc (I think the modules
> >are in /etc/modules, right?).   That means if someone updated their CD
> >without creating a new /etc from the fresh tar file, they would have a
> >ton of problems.
> 
> That's the main reason why I didn't remove it yet.

I guess we could move/link those files to the CD, then they can't they
are matched to the CD, and they can't change (not counting my script).
If it's even possible to create the resulting files in the build ...

> >I agree.  I'm still in favor of 5 seconds and no "vga=" by default.
> 
> Just do it, I can change it later. ;-)

OK, the changes are committed.

EVERYONE, update from CVS NOW, before Heiko changes the defaults!  ;->

 - BS

RE: [Devil-linux-develop] vesa

[Heiko Z. <hz...@pr...>]

On 09/05/2003 03:04:07 PM Bruce Smith wrote:
>> >Hmmm, should we give it a try with 1024x768 and see if users
>complain?
>> >We can then always switch back for Beta 2
>>
>> Hmm, I would certainly disagree with 1024x768.  I don't know about
>most
>> users, but I run my Devil-Linux box with a little old 15" monitor.  =
I
>would
>> expect most users to be using the same.
>
>Well, we have one complaint already, and I haven't made any changes! :=
-)
>
>Most of my DL boxes don't even have a monitor.  I use SSH, and can mak=
e
>the window size & font anything I like.  :-)

And I have a DL (test) box hooked up to my Bigscreen TV. :-))

>> >>My recommendation would be to turn prompt on, with a message
>displayed
>> >>about they options they can type in, timeout of 5 seconds, default=

>to no
>> >>vga=3D parameter specified.
>> >
>> >Do 10 seconds, I always miss those prompts.
>>
>> We are already taking a -significant- amount of time to boot.
>
>Right, that's why I suggested 5 seconds.  I set my GRUB/LILO prompt
>timeout at THREE seconds on my Redhat boxes for that reason.

That's to short for me:
eye -> brain -> *warm up* - > *anaylize* -> *decide* -> brain -> hand

*lol*

>>  (Of course,
>> if we could get rid of ldconfig/module update we could reduce the
>boot time
>> by what - 60%?).
>
>That would be REALLY nice, but I'm not sure it's possible.  The result=
s
>for ldconfig & modconfig are both stored in /etc (I think the modules
>are in /etc/modules, right?).   That means if someone updated their CD=

>without creating a new /etc from the fresh tar file, they would have a=

>ton of problems.

That's the main reason why I didn't remove it yet.

>> Most people are expecting to miss the prompts - just hit the power
>switch
>> and go.  So a long delay would add to the annoyance factor.
>
>I agree.  I'm still in favor of 5 seconds and no "vga=3D" by default.

Just do it, I can change it later. ;-)

Heiko
=

RE: [Devil-linux-develop] vesa

[Bruce S. <bw...@ar...>]

> >Hmmm, should we give it a try with 1024x768 and see if users complain?
> >We can then always switch back for Beta 2
> 
> Hmm, I would certainly disagree with 1024x768.  I don't know about most
> users, but I run my Devil-Linux box with a little old 15" monitor.  I would
> expect most users to be using the same.

Well, we have one complaint already, and I haven't made any changes! :-)

Most of my DL boxes don't even have a monitor.  I use SSH, and can make
the window size & font anything I like.  :-)

> >>My recommendation would be to turn prompt on, with a message displayed
> >>about they options they can type in, timeout of 5 seconds, default to no
> >>vga= parameter specified.
> >
> >Do 10 seconds, I always miss those prompts.
> 
> We are already taking a -significant- amount of time to boot. 

Right, that's why I suggested 5 seconds.  I set my GRUB/LILO prompt
timeout at THREE seconds on my Redhat boxes for that reason.

>  (Of course,
> if we could get rid of ldconfig/module update we could reduce the boot time
> by what - 60%?).

That would be REALLY nice, but I'm not sure it's possible.  The results
for ldconfig & modconfig are both stored in /etc (I think the modules
are in /etc/modules, right?).   That means if someone updated their CD
without creating a new /etc from the fresh tar file, they would have a
ton of problems.

> Most people are expecting to miss the prompts - just hit the power switch
> and go.  So a long delay would add to the annoyance factor.

I agree.  I'm still in favor of 5 seconds and no "vga=" by default.

 - BS

RE: [Devil-linux-develop] vesa

[Dean N. <di...@ti...>]

>>
>>Question #1.  Do we turn "prompt" on, or leave it off and make the user
>>press SHIFT or ALT to get a prompt to change resolution?
>>
>>Question #2.  How long do we make the timeout?  (before it continues
>>with the default label)
>>
>>Question #3.  Which resolution should be the default?  Standard 80x24
>>(no vga= parameter specified) is the safest.
>
>Hmmm, should we give it a try with 1024x768 and see if users complain?
>We can then always switch back for Beta 2

Hmm, I would certainly disagree with 1024x768.  I don't know about most
users, but I run my Devil-Linux box with a little old 15" monitor.  I would
expect most users to be using the same.

>>My recommendation would be to turn prompt on, with a message displayed
>>about they options they can type in, timeout of 5 seconds, default to no
>>vga= parameter specified.
>
>Do 10 seconds, I always miss those prompts.

We are already taking a -significant- amount of time to boot.  (Of course,
if we could get rid of ldconfig/module update we could reduce the boot time
by what - 60%?).

Most people are expecting to miss the prompts - just hit the power switch
and go.  So a long delay would add to the annoyance factor.

Dean Nedelman
TimeLord Consulting.

Re: [Devil-linux-develop] vesa

[Heiko Z. <hz...@pr...>]

On 09/05/2003 02:04:14 PM Bruce Smith wrote:
>> I haven't changed isolinux.cfg yet.  I want to research the prompt
>> parameter first.
>
>OK, as I suspected, the isolinux.cfg file is very similar to lilo.cfg.=

>
>We can have multiple sections (labels) in the cfg file.  I recommend w=
e
>put one in for standard text mode (no vga=3D on the append line), one =
for
>640x480, one for 800x600 and one for 1024x768.  (all 256 color)
>
>Then we can turn on the prompt parameter, with a timeout value, and th=
e
>user can select any mode they like.  For unattended mode, the timeout
>will continue with the default label after a specified amount of time.=

>
>Question #1.  Do we turn "prompt" on, or leave it off and make the use=
r
>press SHIFT or ALT to get a prompt to change resolution?
>
>Question #2.  How long do we make the timeout?  (before it continues
>with the default label)
>
>Question #3.  Which resolution should be the default?  Standard 80x24
>(no vga=3D parameter specified) is the safest.

Hmmm, should we give it a try with 1024x768 and see if users complain?
We can then always switch back for Beta 2

>My recommendation would be to turn prompt on, with a message displayed=

>about they options they can type in, timeout of 5 seconds, default to =
no
>vga=3D parameter specified.

Do 10 seconds, I always miss those prompts.

>Of course any of these value things can be changed by using my script =
to
>rewrite isolinux.cfg in a new ISO image.

I love it!


cya
  Heiko
=

Re: [Devil-linux-develop] vesa

[Bruce S. <bw...@ar...>]

> I haven't changed isolinux.cfg yet.  I want to research the prompt
> parameter first.

OK, as I suspected, the isolinux.cfg file is very similar to lilo.cfg.

We can have multiple sections (labels) in the cfg file.  I recommend we
put one in for standard text mode (no vga= on the append line), one for
640x480, one for 800x600 and one for 1024x768.  (all 256 color)

Then we can turn on the prompt parameter, with a timeout value, and the
user can select any mode they like.  For unattended mode, the timeout
will continue with the default label after a specified amount of time.

Question #1.  Do we turn "prompt" on, or leave it off and make the user
press SHIFT or ALT to get a prompt to change resolution?

Question #2.  How long do we make the timeout?  (before it continues
with the default label)

Question #3.  Which resolution should be the default?  Standard 80x24
(no vga= parameter specified) is the safest.

My recommendation would be to turn prompt on, with a message displayed
about they options they can type in, timeout of 5 seconds, default to no
vga= parameter specified.

Of course any of these value things can be changed by using my script to
rewrite isolinux.cfg in a new ISO image.

 - BS

Re: [Devil-linux-develop] vesa

[Bruce S. <bw...@ar...>]

> >>Are you going to check in those changes?
> > 
> > Sure, I can do that.
> 
> cool

I committed the new kernel config with Frame Buffer support.

I haven't changed isolinux.cfg yet.  I want to research the prompt
parameter first.

 - BS

Re: [Devil-linux-develop] vesa

[Heiko Z. <hz...@pr...>]

On 09/05/2003 05:39:53 AM Diego Torres wrote:
>On Wed, Sep 03, 2003 at 04:25:00PM -0400, Heiko Zuerker wrote:
>> But it needs to be compiled into the Kernel first.
>
>is there a fallback in case there is no vesa board? will dl still be
>bootable if there is no vga card on the motherboard?

With no VESA available, it falls back to standard VGA (80x25) as far as=
 I
know.
You will also have the option to change the VGA=3D parameter in the ISO=

Image.

Heiko

=

Re: [Devil-linux-develop] vesa

[Diego T. <dt...@co...>]

On Wed, Sep 03, 2003 at 04:25:00PM -0400, Heiko Zuerker wrote:
> But it needs to be compiled into the Kernel first.

is there a fallback in case there is no vesa board? will dl still be bootable if there is no vga card on the motherboard?

-- 
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC  2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.  
Diego Torres - dt...@co... - Madrid / España

[Devil-linux-develop] usb boot

[Heiko Z. <he...@zu...>]

Hey,

the USB boot does work now.
BUT I have problems with a corrupt file system once the system boots. 
Sometimes it also doesn't find the config.

I don't know if those are problems with my systems, so I would 
appreciate if somebody could try it out.

You need to do a "make dist" and then will find the script 
"install-on-usb" in the dist folder. Just execute it and follow the 
instructions.

cya
   Heiko

Re: [Devil-linux-develop] vesa

[Bruce S. <bw...@ar...>]

> > I was thinking of the "prompt" parameter in the isolinux.cfg.
> > Would turning on prompt let us change the vga value?
> 
> It would help only to play around.
> I don't see a reason to enable it per default, since you would have to 
> enter this every time you boot.

Unless there is a timeout parameter, or some way to interrupt the boot
process by pressing a key to get a prompt.

I've never used isolinux before, so I don't how close it is to LILO/GRUB

I'll do some reading and play around with it when I get a chance.

 - BS

Re: [Devil-linux-develop] vesa

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:
>>>Also, is it possible to change it on boot prompt by typing in another
>>>value?  I tried "vga=ask", and it wouldn't take any of the 7xx values.
>>
>>Hmmm, but specifying vga=7xx works ?
> 
> 
> I only tried one, vga=773, and it worked fine for me.
> 
> I was thinking of the "prompt" parameter in the isolinux.cfg.
> Would turning on prompt let us change the vga value?

It would help only to play around.
I don't see a reason to enable it per default, since you would have to 
enter this every time you boot.

Heiko

Re: [Devil-linux-develop] vesa

[Bruce S. <bw...@ar...>]

> >>Where  should we set the default resolution ? I would suggest 1024x768x256 .
> > 
> > Is it safe to set a resolution that high?  Or are some PC's with cheap
> > video cards going to have problems?  
> 
> Could be, I remember one PC heaving "lines". But I think that's quite a 
> few Kernel releases ago.
> 
> > Would 800x600x256 be safer? (standard vga)
> 
> I don't know, we could start with this or just see if people run into 
> problems with 1024x768x256.

Sure, we can try it on a beta release and see what happens.

> > Also, is it possible to change it on boot prompt by typing in another
> > value?  I tried "vga=ask", and it wouldn't take any of the 7xx values.
> 
> Hmmm, but specifying vga=7xx works ?

I only tried one, vga=773, and it worked fine for me.

I was thinking of the "prompt" parameter in the isolinux.cfg.
Would turning on prompt let us change the vga value?

 - BS

Re: [Devil-linux-develop] vesa

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:
>>Where  should we set the default resolution ? I would suggest 1024x768x256 .
> 
> 
> Is it safe to set a resolution that high?  Or are some PC's with cheap
> video cards going to have problems?  

Could be, I remember one PC heaving "lines". But I think that's quite a 
few Kernel releases ago.

> Would 800x600x256 be safer? (standard vga)

I don't know, we could start with this or just see if people run into 
problems with 1024x768x256.

> Also, is it possible to change it on boot prompt by typing in another
> value?  I tried "vga=ask", and it wouldn't take any of the 7xx values.

Hmmm, but specifying vga=7xx works ?

cya
   Heiko

Re: [Devil-linux-develop] vesa

[Bruce S. <bw...@ar...>]

> Where  should we set the default resolution ? I would suggest 1024x768x256 .

Is it safe to set a resolution that high?  Or are some PC's with cheap
video cards going to have problems?  

Would 800x600x256 be safer? (standard vga)

Also, is it possible to change it on boot prompt by typing in another
value?  I tried "vga=ask", and it wouldn't take any of the 7xx values.

 - BS

Re: [Devil-linux-develop] vesa

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:
>>>OK, I set those three options, recompiled the kernel, and ...
>>>
>>>pcmcia-cs aborts on the make clean install iso.  :-(
>>
>>That's normal
> 
> 
> Is there something I can manually run in that directory to fix it?
> 
> 
>>>Then I make a new ISO with vga=773, and it works great in VMware4!
>>
>>Cool !
>>
>>
>>>However, Tux (the standard logo, not the DL penguin with horns) stays at
>>>the top of the screen and doesn't go away, wasting viewable space.  How
>>>can I get rid of that?
>>
>>I don't know, I know it only this way.
>>But only the first console should be affected, correct.
> 
> 
> I don't know about the first console, but when I started scrolling in
> the console (SHIFT + PGUP/PGDN) it went away.

Even better !

>>Are you going to check in those changes?
> 
> 
> Sure, I can do that.

cool

>>At some point we should then also replace Tux with our Logo.
> 
> 
> Point me in the right direction and I'll give it a try.
> (I have no idea where to start looking for that).

www.google.com
linux boot logo vesa tux replace

Where  should we set the default resolution ? I would suggest 1024x768x256 .

cya
   Heiko

Re: [Devil-linux-develop] vesa

[Bruce S. <bw...@ar...>]

> > OK, I set those three options, recompiled the kernel, and ...
> > 
> > pcmcia-cs aborts on the make clean install iso.  :-(
> That's normal

Is there something I can manually run in that directory to fix it?

> > Then I make a new ISO with vga=773, and it works great in VMware4!
> 
> Cool !
> 
> > However, Tux (the standard logo, not the DL penguin with horns) stays at
> > the top of the screen and doesn't go away, wasting viewable space.  How
> > can I get rid of that?
> 
> I don't know, I know it only this way.
> But only the first console should be affected, correct.

I don't know about the first console, but when I started scrolling in
the console (SHIFT + PGUP/PGDN) it went away.

> Are you going to check in those changes?

Sure, I can do that.

> At some point we should then also replace Tux with our Logo.

Point me in the right direction and I'll give it a try.
(I have no idea where to start looking for that).

 - BS

Re: [Devil-linux-develop] vesa

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:
>>>[*] Support for frame buffer devices
>>
>>>[ ]   VESA VGA graphics console
>>>  VGA 16-color graphics console
>>
>>The rest looked good to me.
> 
> 
> OK, I set those three options, recompiled the kernel, and ...
> 
> pcmcia-cs aborts on the make clean install iso.  :-(
That's normal

> So, I turned off pcmcia in the .config, and tried again.
> 
> Then I make a new ISO with vga=773, and it works great in VMware4!

Cool !

> However, Tux (the standard logo, not the DL penguin with horns) stays at
> the top of the screen and doesn't go away, wasting viewable space.  How
> can I get rid of that?

I don't know, I know it only this way.
But only the first console should be affected, correct.

> Also, vga=773 is 256 colors.  Is there ANY reason to go higher?  Is
> there any software on DL that would use more colors?

Should not.

Are you going to check in those changes?
At some point we should then also replace Tux with our Logo.

cya
   Heiko

Re: [Devil-linux-develop] vesa

[Bruce S. <bw...@ar...>]

> >[*] Support for frame buffer devices
> 
> >[ ]   VESA VGA graphics console
> >   VGA 16-color graphics console
> 
> The rest looked good to me.

OK, I set those three options, recompiled the kernel, and ...

pcmcia-cs aborts on the make clean install iso.  :-(

So, I turned off pcmcia in the .config, and tried again.

Then I make a new ISO with vga=773, and it works great in VMware4!

However, Tux (the standard logo, not the DL penguin with horns) stays at
the top of the screen and doesn't go away, wasting viewable space.  How
can I get rid of that?

Also, vga=773 is 256 colors.  Is there ANY reason to go higher?  Is
there any software on DL that would use more colors?

 - BS

Re: [Devil-linux-develop] vesa

[Heiko Z. <hz...@pr...>]

T24gMDkvMDMvMjAwMyAwNToxOTo1NSBQTSBCcnVjZSBTbWl0aCB3cm90ZToNCj4+ID4gPj4gPj4g
b2ZmZXIgYSB3YXkgdG8gY2hhbmdlIHRoZSAiVkdBPSIgYm9vdCBwYXJhbWV0ZXIuDQo+PiA+ID4+
ID4NCj4+ID4gPj4gPkknbGwgdHJ5IGl0IQ0KPj4gPiA+PiA+DQo+PiA+ID4+ID5XaGF0IGZpbGUg
ZG8gd2UgY2hhbmdlPyAgRG8geW91IGhhdmUgYSBsaXN0IG9mIHRoZSBWR0E9IHZhbHVlcw0KPmhh
bmR5Pw0KPj4gPiA+Pg0KPj4gPiA+PiBEbyB0aGUgZm9sbG93aW5nIHRvIHF1aWNrbHkgdHJ5IGl0
Og0KPj4gPiA+PiBHbyBpbnRvICB0aGUgS2VybmVsIGRpcmVjdG9yeSBhbmQgbW9kaWZ5IGl0IHZp
YSAibWFrZQ0KPm1lbnVjb25maWciLg0KPj4gPiA+PiBUaGVuIGRvIGEgImJ1aWxkL2J1aWxkLnNo
IGJ1aWxkIG9wdD1saW51eCIgYW5kIGEgIm1ha2UgY2xlYW4NCj5pbnN0YWxsDQo+PiA+ID5pc28i
Lg0KPj4gPiA+DQo+PiA+ID5BcyBmYXIgYXMgSSBjYW4gdGVsbCwgaXQncyBhbHJlYWR5IHR1cm5l
ZCBvbi4gIFRoaXMgb3B0aW9uIGlzDQo+c2VsZWN0ZWQ6DQo+PiA+ID4NCj4+ID4gPoENCj4+ID4g
PkNPTkZJR19WSURFT19TRUxFQ1Q6DQo+PiA+ID6BDQo+PiA+DQo+PiA+IFRoaXMgaXMgbm90IHRo
ZSBvbmUsIHlvdSBuZWVkIHRvIHR1cm4gb24gVkVTQSBGcmFtZWJ1ZmZlciBzdXBwb3J0Lg0KPg0K
PkFzc3VtaW5nIHlvdXIgY29ycmVjdCAoSSdtIHN0aWxsIHNrZXB0aWNhbCA6KSAgV2hlbiBJIHNl
bGVjdCBmcmFtZQ0KPmJ1ZmZlciBzdXBwb3J0LCBJIGdldCB0aGlzIHN1Ym1lbnUuICBXaGF0IG90
aGVyIG9wdGlvbnMgZG8gSSBuZWVkIGhlcmU/DQo+SnVzdCAiVkVTQSBWR0EgZ3JhcGhpY3MgY29u
c29sZSI/ICBGb250cz8gIEFueXRoaW5nIGVsc2U/DQo+DQo+DQo+WypdIFN1cHBvcnQgZm9yIGZy
YW1lIGJ1ZmZlciBkZXZpY2VzDQoNCj5bIF0gICBWRVNBIFZHQSBncmFwaGljcyBjb25zb2xlDQo+
ICAgVkdBIDE2LWNvbG9yIGdyYXBoaWNzIGNvbnNvbGUNCg0KVGhlIHJlc3QgbG9va2VkIGdvb2Qg
dG8gbWUuDQoNCmVpa28NCg0K

Re: [Devil-linux-develop] vesa

[Heiko Z. <hz...@pr...>]

T24gMDkvMDMvMjAwMyAwNTowNToyOSBQTSBCcnVjZSBTbWl0aCB3cm90ZToNCj4+ID4+ID4+IG9m
ZmVyIGEgd2F5IHRvIGNoYW5nZSB0aGUgIlZHQT0iIGJvb3QgcGFyYW1ldGVyLg0KPj4gPj4gPg0K
Pj4gPj4gPkknbGwgdHJ5IGl0IQ0KPj4gPj4gPg0KPj4gPj4gPldoYXQgZmlsZSBkbyB3ZSBjaGFu
Z2U/ICBEbyB5b3UgaGF2ZSBhIGxpc3Qgb2YgdGhlIFZHQT0gdmFsdWVzDQo+aGFuZHk/DQo+PiA+
Pg0KPj4gPj4gRG8gdGhlIGZvbGxvd2luZyB0byBxdWlja2x5IHRyeSBpdDoNCj4+ID4+IEdvIGlu
dG8gIHRoZSBLZXJuZWwgZGlyZWN0b3J5IGFuZCBtb2RpZnkgaXQgdmlhICJtYWtlIG1lbnVjb25m
aWciLg0KPj4gPj4gVGhlbiBkbyBhICJidWlsZC9idWlsZC5zaCBidWlsZCBvcHQ9bGludXgiIGFu
ZCBhICJtYWtlIGNsZWFuDQo+aW5zdGFsbA0KPj4gPmlzbyIuDQo+PiA+DQo+PiA+QXMgZmFyIGFz
IEkgY2FuIHRlbGwsIGl0J3MgYWxyZWFkeSB0dXJuZWQgb24uICBUaGlzIG9wdGlvbiBpcw0KPnNl
bGVjdGVkOg0KPj4gPg0KPj4gPoENCj4+ID5DT05GSUdfVklERU9fU0VMRUNUOg0KPj4gPoENCj4+
DQo+PiBUaGlzIGlzIG5vdCB0aGUgb25lLCB5b3UgbmVlZCB0byB0dXJuIG9uIFZFU0EgRnJhbWVi
dWZmZXIgc3VwcG9ydC4NCj4NCj5BcmUgeW91IHN1cmU/ICBJIGFkZGVkICJ2Z2E9YXNrIiB0byB0
aGUgQVBQRU5EIGxpbmUuDQoNClllcyBJIGFtLg0KDQo+SW4gVk13YXJlLCBJIGdldCBhIG1lbnUg
b2Y6DQo+DQo+TW9kZTogIENPTFNYUk9XUzoNCj4wIDBmMDAgODB4MjUNCj4xIDBmMDEgODB4NTAN
Cj4yIDBmMDIgODB4NDMNCj4zIDBmMDMgODB4MjgNCj40IDBmMDUgODB4MzANCj41IDBmMDYgODB4
MzQNCj42IDBmMDcgODB4NjANCj4NCj5XaGVuIEkgaW5wdXQgYSBudW1iZXIgbGlrZSAxLCAyLCAz
LCAuLi4gIEkgZ2V0IHJlYWxseSBzbWFsbCB0eXBlLg0KDQpUaGUgVkVTQSBtb2RlcyBwcm92aWRl
IGhpZ2hlciByZXNvbHV0aW9ucywgaS5lLiAxNjB4NjANCg0KSGVpa28NCg==