similar to: tftpd-hpa: remap '/tftpboot/ncd4/foo' into 'ncd4/foo'

Hi I am using windows. I cant install ncdf4 package but it didn't work . any suggestions!! -- View this message in context: http://r.789695.n4.nabble.com/ncd4-package-tp4477496p4477496.html Sent from the R help mailing list archive at Nabble.com.

Not being familiar with chip sets and other factors that "hardware experts" understand, I am perplexed with the multitude of available motherboards. Is there a Web site that can be of help or a "strategy"? My goal is to replace my motherboard with one that is Centos compatible and uses a Pentium 4 in the 2 MHz range. As example, when I go to Mwave, I am presented with

I don't seem to be able to find the necessary hardware specs for an Asterisk server. What I have in mind is a dedicated server to serve 50 or so people. All users will use SIP phones and there will be an ISDN gateway for outgoing/incoming calls. Do you have any suggestions about the server specs (CPU, RAM, HD, etc)? Also, has anyone used Epigi Quadro ISDN gateway with Asterisk? If so, what is

Hey guys, In your experience what is the best way to go for a production asterisk box in your offices? With desktop prices so cheap you might think that you should just buy them off the shelf, but is that really a reliable machine? Anything you can tell me that would assist me in deciding the best way to obtain and maintain these boxes would be very helpful. I have even looked into building

I'm looking to install a basic asterisk system for my church with: 8 inbound sip channels 8 sip handsets basic voicemail room to grow (maybe doubling each of the above) What would be a recomended system as to needed processor and memory? Thanks, Eric

Hi all, I took my decision to use Asterisk server for handling my VOIP calls...My next step is to choose the best hardware that I should use i order to have the best performance...Here I faced 2 choices for my hardware (CPU)... 1- Using Intel CPU or AMD 2- Use 32 or 64 bits Can you help me please to choose between the above choices and what is the advantage and disadvantage of each of choices

I've tried both RedHat EL4 Update 7 and EL5 Update 4, both give me the same problem. 3.82 will install no problem at all : [root at rdoogan-lnx ~]# rpm -Uvh syslinux-tftpboot-3.82-1.i386.rpm Preparing... ########################################### [100%] 1:syslinux-tftpboot ########################################### [100%] However, starting wth 3.83 I get the

Has anyone had any luck with moving files outside of /tftpboot? Its been particularly frustrating in my environment to support files within this directory. Especially since I support three different architectures and need to differentiate their boot loaders, kernels, configs, initrd's, etc. I'd really like to symlink off to my AFS space and let the sysname values do the work. Is there a

On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: > Sorry for the confusion, I am actually using 6.02. It turns out that I was > trying to use the 32-bit efi binary to load 64-bit kernels. I switched to > using "syslinux64.efi" but it hangs during boot, just before loading the > menu. I have not been able to get it to load the menu

On Thu, Mar 6, 2014 at 6:45 PM, Bryan Romine <bromine1027 at gmail.com> wrote: > Yes, I am using efi64/efi/syslinux.efi and > efi64/com32/elflink/ldlinux/ldlinux.e64. I tried binaries from 6.03-pre7 and > it gets farther along but brings up the error "Default boot device missing > or boot failed". Maybe I am not installing all of the required dependencies? > Are

> > > On 2014/3/7 05:23, Gene Cumm wrote: > > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: > >> Sorry for the confusion, I am actually using 6.02. It turns out that I was > >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to > >> using "syslinux64.efi" but it hangs during boot,

On Sat, Mar 8, 2014 at 2:05 AM, Steven Shiau <steven at nchc.org.tw> wrote: > Hi Gene, > Thanks. As you mentioned, atftpd has better logging, and my files are > smaller than 92 MB, so I switched to atftpd for testing. Now I could > find that somehow after bootx64.efi is downloaded by client, the next > ldlinux.e64 has never been fetched by client: > ====================

On Mar 8, 2014 8:36 AM, "Steven Shiau" <steven at nchc.org.tw> wrote: > > > On 2014?03?08? 20:57, Gene Cumm wrote: > > Please try 6.03-pre6. I see a regression on 6.03-pre7 with EFI64 netboot > > > >> > Another thing you I'd like to mentioned is, after bootx64.efi was > >> > downloaded, the next download for ldlinux.e64 was about 15

On Mar 8, 2014 9:27 AM, "Steven Shiau" <steven at nchc.org.tw> wrote: > > > > On 03/08/2014 10:06 PM, Gene Cumm wrote: > >> Hi Gene, > >> > Thanks. As you suggested, I did a test about 6.03-pre6, and I still got > >> > the same issue. My client machine > >> > still only shows: > >> > ==================== >

On Sat, Mar 8, 2014 at 12:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mar 8, 2014 10:08 AM, "Gene Cumm" <gene.cumm at gmail.com> wrote: >> >> vNIC not VMNet. AMD PCNet32 vlance, Intel e1000, Intel e1000e, VMware >> VMXNet3? Feel free to directly email me your .vmx file if you don't know. > > So that should be vlance or flexible

On Fri, Mar 7, 2014 at 10:50 AM, Steven Shiau <steven at nchc.org.tw> wrote: > > On 2014?03?07? 23:05, Ady wrote: >> I understand that these remarks might seem not the main issue, but I >> tend to think that once you are successful while using only "default" >> >> values and in a minimalistic case, you could add complexity >> (different paths,

Hi, I'm using PXELinux (on Windows NT5.x, with Windows NT5.x tftpd and the PXE server included in the "Windows XP Embedded Remote Boot Server"). This works well here since more than 10 years now. Recently I created a subdirectory "syslinux" in my "tftpboot" ... and PXELINUX failed with the message "unable to locate configuration file". Renaming that

On 03/08/2014 10:06 PM, Gene Cumm wrote: >> Hi Gene, >> > Thanks. As you suggested, I did a test about 6.03-pre6, and I still got >> > the same issue. My client machine >> > still only shows: >> > ==================== >> > Getting cached packets >> > My IP is 192.168.120.1 >> > ==================== >> > The syslog log

On Fri, Mar 7, 2014 at 12:34 PM, Bryan Romine <bromine1027 at gmail.com> wrote: > I'm convinced that my Syslinux install may be broken with all the hacking > around and testing I have been doing. If I were to install fresh from the > syslinux-6.03-pre7 archive, what would I need to do. I do not see any > documentation on installation other than "make installer" in

> > On 20140307 18:24, Ady wrote: > > Hi Steven, > > > > Perhaps this could be of some basic sample/help, being based on > > Debian: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 > > > > where: > > _ if gpxelinux.0 is needed, it should probably be replaced by ipxe. > > _ lpxelinux.0 (from official Syslinux archive) could