Displaying 20 results from an estimated 2000 matches similar to: "Random numbers in pxe config"
2008 Jun 05
1
illegal opcode on cold pxe boots
Using the latest version of syslinux/pxelinux..
When cold pxe booting a HP DL585 G2 (Broadcom NIC), if the pxemenu item is
LOCALBOOT 0 and is selected, then a red screen with the following error
occurs:
Illegal OpCode
EAX=000E09AC EBX=00000000 ECX=00000000 EDX=00000000
EBP=00004408 ESI=0000F000 EDI=000045E9
DS=F000 ES=0000 FS=0000 GS=0003
CS:EIP=1000:00000240
2008 Mar 06
4
PXELINUX "Fancy" advanced menu question
Hello.
I am trying to run advanced dialog-like menus from com32.
But I can not boot anything... ? it always fails. :-)
So, my /path/to/pxelinux.cfg/default looks like this:
--------------8<--------------
DEFAULT pxemenu/fancy.c32
PROMPT 0
IMPLICIT 1
TIMEOUT 600
LABEL test
MENU LABEL Test
KERNEL suse10_3/vmlinuz
APPEND initrd=suse10_3/initrd.img ....(and so on)....
2020 Feb 13
4
[PATCH] virtio: Work around frames incorrectly marked as gso
On Wed, Feb 12, 2020 at 05:38:09PM +0000, Anton Ivanov wrote:
>
>
> On 11/02/2020 10:37, Michael S. Tsirkin wrote:
> > On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
> > > On 11/02/2020 02:51, Jason Wang wrote:
> > > >
> > > > On 2020/2/11 ??12:55, Anton Ivanov wrote:
> > > > >
> > > > >
> >
2020 Feb 13
4
[PATCH] virtio: Work around frames incorrectly marked as gso
On Wed, Feb 12, 2020 at 05:38:09PM +0000, Anton Ivanov wrote:
>
>
> On 11/02/2020 10:37, Michael S. Tsirkin wrote:
> > On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
> > > On 11/02/2020 02:51, Jason Wang wrote:
> > > >
> > > > On 2020/2/11 ??12:55, Anton Ivanov wrote:
> > > > >
> > > > >
> >
2020 Feb 12
1
[PATCH] virtio: Work around frames incorrectly marked as gso
On Wed, Feb 12, 2020 at 10:03:31AM +0000, Anton Ivanov wrote:
>
>
> On 11/02/2020 10:37, Michael S. Tsirkin wrote:
> > On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
> > > On 11/02/2020 02:51, Jason Wang wrote:
> > > >
> > > > On 2020/2/11 ??12:55, Anton Ivanov wrote:
> > > > >
> > > > >
> >
2020 Feb 11
2
[PATCH] virtio: Work around frames incorrectly marked as gso
On 2020/2/11 ??12:55, Anton Ivanov wrote:
>
>
> On 09/12/2019 10:48, anton.ivanov at cambridgegreys.com wrote:
>> From: Anton Ivanov <anton.ivanov at cambridgegreys.com>
>>
>> Some of the frames marked as GSO which arrive at
>> virtio_net_hdr_from_skb() have no GSO_TYPE, no
>> fragments (data_len = 0) and length significantly shorter
>> than the
2020 Feb 11
2
[PATCH] virtio: Work around frames incorrectly marked as gso
On 2020/2/11 ??12:55, Anton Ivanov wrote:
>
>
> On 09/12/2019 10:48, anton.ivanov at cambridgegreys.com wrote:
>> From: Anton Ivanov <anton.ivanov at cambridgegreys.com>
>>
>> Some of the frames marked as GSO which arrive at
>> virtio_net_hdr_from_skb() have no GSO_TYPE, no
>> fragments (data_len = 0) and length significantly shorter
>> than the
2020 Feb 11
5
[PATCH] virtio: Work around frames incorrectly marked as gso
On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
> On 11/02/2020 02:51, Jason Wang wrote:
> >
> > On 2020/2/11 ??12:55, Anton Ivanov wrote:
> > >
> > >
> > > On 09/12/2019 10:48, anton.ivanov at cambridgegreys.com wrote:
> > > > From: Anton Ivanov <anton.ivanov at cambridgegreys.com>
> > > >
> > >
2020 Feb 11
5
[PATCH] virtio: Work around frames incorrectly marked as gso
On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
> On 11/02/2020 02:51, Jason Wang wrote:
> >
> > On 2020/2/11 ??12:55, Anton Ivanov wrote:
> > >
> > >
> > > On 09/12/2019 10:48, anton.ivanov at cambridgegreys.com wrote:
> > > > From: Anton Ivanov <anton.ivanov at cambridgegreys.com>
> > > >
> > >
2020 Feb 13
1
[PATCH] virtio: Work around frames incorrectly marked as gso
On 2020/2/13 ??1:38, Anton Ivanov wrote:
>
>
> On 11/02/2020 10:37, Michael S. Tsirkin wrote:
>> On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
>>> On 11/02/2020 02:51, Jason Wang wrote:
>>>>
>>>> On 2020/2/11 ??12:55, Anton Ivanov wrote:
>>>>>
>>>>>
>>>>> On 09/12/2019 10:48, anton.ivanov
2020 Feb 13
3
[PATCH] virtio: Work around frames incorrectly marked as gso
On Thu, Feb 13, 2020 at 07:44:06AM -0800, Eric Dumazet wrote:
>
>
> On 2/13/20 2:00 AM, Michael S. Tsirkin wrote:
> > On Wed, Feb 12, 2020 at 05:38:09PM +0000, Anton Ivanov wrote:
> >>
> >>
> >> On 11/02/2020 10:37, Michael S. Tsirkin wrote:
> >>> On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
> >>>> On
2020 Feb 13
3
[PATCH] virtio: Work around frames incorrectly marked as gso
On Thu, Feb 13, 2020 at 07:44:06AM -0800, Eric Dumazet wrote:
>
>
> On 2/13/20 2:00 AM, Michael S. Tsirkin wrote:
> > On Wed, Feb 12, 2020 at 05:38:09PM +0000, Anton Ivanov wrote:
> >>
> >>
> >> On 11/02/2020 10:37, Michael S. Tsirkin wrote:
> >>> On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote:
> >>>> On
2019 Dec 09
3
[PATCH] virtio: Work around frames incorrectly marked as gso
From: Anton Ivanov <anton.ivanov at cambridgegreys.com>
Some of the frames marked as GSO which arrive at
virtio_net_hdr_from_skb() have no GSO_TYPE, no
fragments (data_len = 0) and length significantly shorter
than the MTU (752 in my experiments).
This is observed on raw sockets reading off vEth interfaces
in all 4.x and 5.x kernels I tested.
These frames are reported as invalid while
2018 Feb 01
4
How to grant user access to his .dovecot.sieve.log?
Hi,
What are the recommended ways to give access to their .dovecot.sieve.log
messages to the users?
I am thinking about placing this file into users Maildir/new, or piping
to dovecot-lda.
--
Regards,
Sergey Ivanov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital
2007 Oct 13
2
a question on impulse responses
Dear R users,
I am using the vars package to calculate the impulse response functions and the forecast error variance decomposition of a VAR model. Unfortunately I do not know whether these functions assume unit or one standard deviation shocks. I tried to look into the code of these functions, but in vain: neither irf, nor vars::irf, nor vars:::irf output the code of the functions. Does someone
2014 Jul 23
2
pxelinux HTTP transport UEFI vmlinuz
Hi,
Since which version of pxelinux.0 is understood in pxelinux.cfg/default that
kernel http://host.lan/netboot/vmlinuz
means vmlinuz should be transported over HTTP?
Since which version of pxelinux.0 is it possible to boot on UEFI?
Those questions elaborated:
What I want is fast netboot UEFI servers.
What I'm looking for is an advice which version of PXELINUX
between version
2006 Jun 22
2
trying to build dovecot-sieve
Hi,
I'm trying to compile dovecot with dovecot-sieve, both from CVS.
There is file dovecot-config.in.in in current dovecot module, which
produce dovecot-config.in after ./configure'ing. But dovecot-sieve
requires file dovecot-config to be in dovecot's directory.
I think it is just typo, because after renaming dovecot-config.in to
dovecot-config the building succeeded.
--
Sergey
2008 Jul 01
2
"select NULL as password..." failing after upgrade to dovecot-1.1
Hi,
I've upgraded mail server to dovecot-1.1, on solaris-10 with mysql user
database.
I used sql query
"SELECT NULL as password, login as user,
concat('/mail/var/dovecot/',login) AS userdb_home, 501 AS userdb_uid,
501 AS userdb_gid FROM users WHERE login='%n' AND
password=old_password('%w')" with dovecot-1.0.15 and it worked perfectly.
But since upgrade
2007 Mar 29
2
dovecot mmap() complaints: No such device
I'm trying to use dovecot-deliver with sieve plugin, delivering to
Maildirs. Everything seems working O.K., but I'm getting the following
lines in /var/log/maillog:
---
Mar 29 00:06:00 alt64 dovecot: imap-login: Login: user=<seriv>,
method=PLAIN, rip=66.80.117.2, lip=192.168.10.8, TLS
Mar 29 00:06:00 alt64 dovecot: IMAP(seriv): mmap() failed with index
file
2008 Jul 24
3
how to store flags \Seen into read-only mailbox?
Hi,
I'm trying to use dovecot for storing mailing lists and read-only access for users.
The OS is Solaris, authentication for all readers of these lists are from Ldap through PAM, and one local user "listuser" will receive all mail and store them into it's folders (Maildirs). These maildirs are readable (read-only) for all others and they are shared by setting
---
mail_location: