similar to: chaing freebsd pxeboot.0 from pxelinux.0

Hi, Some words about my Dovecot setup: - 10 dovecot servers - each server has some local mailboxes - each server has proxying enabled to seamlessly connect to another host if the mailbox is not local Running Dovecot 1.1.1 on FreeBSD 6.3-RELEASE-p3. First of all, local mailbox access is fine. Proxying works also as expected. Now for the actual problem: Shortly after startup, Dovecot starts

Excuse me form reposting the quesiton, but I didn''t find any solution. Any suggestion is welcome Hi, I''m running a Debian 2.2r2 on a university server with 3 public ip o(1.1.1.1 2.2.2.2 and 3.3.3.3 on one ethernet card (but soon we will have three cards). There''s a tunnel (implemented with vtund on a tun interface with local address 192.168.1.10 and remote

Hi, I'm from Italy (sorry for my english...). I've two questions about the plot function. I've to create a simple graph for the data set "n_species": species=sqlQuery(dati, "select count(distinct species), season from captures_complete_r group by species, season") n_species=tapply(species$count, species$season, sum) n_species=data.frame(n_species) n_species

Hi, I''m running a Debian 2.2r2 on a university server with 3 public ip on one ethernet card (but soon we will have three cards). There''s a tunnel (implemented with vtund on a tun interface with local address 192.168.1.10 and remote 192.168.1.20) from this server to another server without public ip and behind a router. I wanted to make the second server visible to the world, so

This is my third mail in the last three months and still no-one has answered, while I received some comments from other users about the fact that the problem is known. So if you have any info on how to fix this, please post a message :-) Here is the problem: I used to share a vfat mounted partition with other collegues through samba (2.0.7). Everything worked and still works fine with kernel

I downloaded version 0.3.12 of TZInfo from [1], and observed that it has a very robust set of timezones including, for example, ''America/ Anchorage'': irb(main):001:0> require ''rubygems'' => false irb(main):002:0> require ''tzinfo'' => true irb(main):003:0> TZInfo::Timezone.get(''America/Anchorage'') =>

Hi, Say I download a large file from the net to /mnt/a.iso. I then download the same file again to /mnt/b.iso. These files now have the same content, but are stored twice since the copies weren''t made with the bcp utility. The same occurs if a directory tree with duplicate files (created with bcp) is put through a non-aware program - for example tarred and then untarred again. This

I have the following forced up mew by evil telco problem: - One IP - Homebrew LAN - portforwarding for some services. - extra PPTP/ppp layer to an internal 10.* network which mutilates DNS answers. Setup: Machine A has ip a.b.c.d (real IP) and is reachable over ADSL with it from the world. It does NAT for an internal LAN 192.168.0.0/24) and has portforwading turned on for some ports (eg 80)

I see a single post by a Stephen Childs about a way to pxe-boot paravirtualized xen guests [1] but there is no follow up. I do see a link to the product in question [2] the funny thing is that I don''t see any discussion (or mention of rolling this into the main xen distro) - speaking as someone who manages many servers, virtual and non-virtual, the more I can get to run off my

Hi all, Well I''ve managed to waste a day on this. Posted a similar message earlier today on the fedora list and got no nibbles. I read every article in the archives regarding pxebooting; there is no mention of it in the wiki. I have a box with two kernels, a standard fedora 6 and a xen fedora 6. Both boot fine. I''ve setup another server with dhcp and tftpboot and can now

latest pxeboot (7.1): mother-board NIC/LOM CPU ------------- ------- --- Intel SWV25 em xeon works fine SUN X2200 bge amd works fine DELL PE 2950 bce xeon failes 95% of the times hangs or goes into btx dump regs. mode :-) Intel SE7320VP21 msk xeon failes 50% of the times - hangs pxeboot with btx.S 1.45 2008/02/27 23:35:39, works fine. so it seems that changes since 1.45 have

Hi guys, This may be a stupid question... I was trying to get a machine to boot with PXE. Everything supportive is setup, the DNS/DHCP works fine, TFTP is also handing over pxelinux.0 and config files correctly. The problem happens at: label xxx kernel memdisk initrd blabla My machine would report "cannot find kernel: memdisk". When doing a tcpdump, I found the machine actually

I am in the process of migrating my desktop system from 32-bit CentOS 4.8 to 64-bit CentOS 5.4. One of the things I want to be able to do is boot my IBM Thinkpad X25 laptop via its PXEBoot ROM over the LAN (it has a hard disk and boot locally just fine, I just want a way to boot it for rescue and/or new O/S installs). On my 32-bit CentOS 4.8 this works just fine. It also works on another

I am using pxeboot (syslinux) 1.75 and I'm attempting to boot diskless with the pxeboot.0 system. The system boots, downloads the pxeboot.0, the kernel and then the screen turns to garbage. Does anyone know what this is/how to fix this? Thanks. -- Paul Slinski System Administrator Global IQX http://www.globaliqx.com/ pauls at globaliqx.com

Hello... Last week I demonstrated a problem with PXELINUX's ability to launch the FreeBSD "pxeboot" program. Mr. Anvin suggests that this can be fixed. I'm glad, because this PXELINUX/pxeboot problem is the very last technical issue for a project on which I've been working since September. My company has a proprietary disk-imaging system that they would like to replace.

Hello... With syslinux pre7, I am consistently getting what looks like a stack dump out of the FreeBSD loader. I have seen this behavior from pxeboot before. Maybe once out of every fifty or so runs of pxeboot, I would see an error message like the one below, but it was both rare and inconsistent. Now I am getting this message every time pxelinux invokes pxeboot: BTX loader 1.00 BTX

This is slightly off topic since I am all the way upto the login prompt, but I appeal to you all because you probably have experience in this: I am passing a diskless workstation a compressed root filesystem that is copied from a server (chopped down). I am only intereted in text consoles being available on the client (runlevel 3). The diskless workstation goes well up to the login: RedHat

Hi Brock, I'm trying set full duplex on a server that is being pxeboot/provisioned via autoyast. We want to ensure the duplex is full DURING the autoyast provisioning itself. I've played the syslinux configs to specify the bcm5600 driver, but was having trouble with setting the network options. I've tryed appending them as well, but nothing on the internet seems to indicate that

Hi, I've been hacking this week-end on a Vortex86[0] based device (ebox 3300) and had quite a few trouble with pxelinux.0 on it. Actually, I narrowed the problem to the `pxenv' routine always returning 1. This lead to an infinite loop while trying to transfer the config file. I'm not sure what the problem is, but the FreeBSD PXE bootloader does work on the same hardware, with the same

Please indicate what version of Syslinux you are using, and also a hint at your system configuration. I presume the packet dump was taken on the server. They indicate the client trying to initiate a TFTP transaction but apparently not getting the reply. This *may* be the same bug that ended up in 6.02 but has since been fixed. -hpa