search for: serien

...sk = 0775 [player] comment = player browseable = yes read only = yes directory = /var/ftp/player public = yes [upload] comment = upload browseable = yes read only = no directory = /var/ftp/upload public = yes force create mode = 777 force directory mode = 777 [serien] comment = serien browsable = yes read only = yes directory = /var/ftp/serien guest ok = true [cinema] comment = cinema browsable = yes read only = yes directory = /var/ftp/cinema public = yes [printers] comment = HP4LaserJet browseable = yes path = /tmp pr...

...s man f?r den Videospass braucht browseable = yes read only = yes directory = /var/ftp/player public = yes [upload] comment = upload browseable = yes read only = no directory = /var/ftp/upload public = yes force create mode = 777 force directory mode = 777 [serien] comment = serien browsable = yes read only = yes directory = /var/ftp/serien guest ok = true [cinema] comment = cinema browsable = yes read only = yes directory = /var/ftp/cinema public = yes [printers] comment = HP4LaserJet browseable = yes path = /tmp pr...

I performed an experiment in which I had dhcpd specify a named file ("foo") instead of one based on a client's MAC address. Lo and behold, the same problem occured. The PXE stack requested and was served the right file, the kernel loaded as did the initrd. But again, the boot sequence stopped at "Ready." Keep in mind that the contents of the file are the same as was in the

Hi, I've been looking at the pxelinux code and I was wondering a couple of things: 1) Why does pxelinux create UDP packets from scratch instead of use the Intel PXE TFTP OPEN/CLOSE/READ calls? I'm assuming this is to support TFTP options like tsize right? Did earlier versions of pxelinux use the TFTP calls directly? 2) How big of an image can pxelinux download (minus memory