similar to: Network Boot IP Configuration Dilemma

Displaying 20 results from an estimated 1000 matches similar to: "Network Boot IP Configuration Dilemma"

2003 Sep 14
2
FWD: Network Boot IP Configuration Dilemma
If you want eth0 to be used and no dynamic IP configuration request should not occur in the Linux kernel, specify *both* APPEND and IPAPPEND options like: APPEND ip=:::::eth0:none IPAPPEND 1 It's very tricky but it works, at least Linux 2.4.18 which I tested. The IP-PNP routine in the kernel doesn't modify values if the option values are not explicitly specified. IPAPPEND doesn't
2003 Jul 05
2
Anyone tried SYSLINUX 2.05-pre2 yet?
-?
2009 Feb 08
1
[PATCH 1/1] COMBOOT API: Add calls for directory functions; Implement for FAT; Try 2
From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add calls for directory functions; Implement most only for FAT (SYSLINUX). Uses INT 22h AX= 001Fh, 0020h, 0021h and 0022h to prepare for the COM32 C functions getcwd(), opendir(), readdir(), and closedir(), respectively. INT22h, AX=001Fh will return a valid value for all variants. INT22h, AX= 0020h, 0021h, and 0022h are only
2013 Jun 24
2
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
core and the simple menu do not interpret the IPAPPEND/SYSAPPEND directives in the same way. Which is the proper way? Either way, this should be clarified in the documentation. com32/elflink/ldlinux/readconfig.c: } else if ((ep = looking_at(p, "ipappend")) || (ep = looking_at(p, "sysappend"))) { uint32_t s = strtoul(skipspace(ep), NULL,
2017 Sep 19
0
CentOS, PHP & OwnCloud/Nextcloud: the version dilemma
-----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Nicolas Kovacs Sent: den 19 september 2017 09:37 To: CentOS mailing list <centos at centos.org> Subject: [CentOS] CentOS, PHP & OwnCloud/Nextcloud: the version dilemma Hi, I'm currently experimenting with OwnCloud and Nextcloud on a sandbox CentOS 7 server. I've been using OwnCloud for
2002 Aug 14
0
re: using mac-addr for selecting configfile now working
Hi everybody hacking in the 200-pre4 i found everything i needed, so i gave it a try ... and it works! But dont blame for the code, its just quick and dirty! --- ../syslinux-2.00-pre4/pxelinux.asm Sat Jun 15 07:25:51 2002 +++ ./pxelinux.asm Wed Aug 14 10:05:00 2002 @@ -17,6 +17,11 @@ ; version; incorporated herein by reference. ; ;
2013 Jun 24
2
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
On Sun, Jun 23, 2013 at 3:16 PM, Gerardo Exequiel Pozzi <vmlinuz386 at yahoo.com.ar> wrote: > I guess the bug is here (com32/menu/readconfig.c) > > 910 } else if (looking_at(p, "ipappend") || looking_at(p, > "sysappend")) { > 911 if (ld.label) > 912 ld.ipappend = atoi(skipspace(p + 8)); > 913
2013 Jun 26
2
[PATCH][git] IPAPPEND: standardize and document
The following changes since commit 4ff8fcac8e7b5046987dee15592ab510ab343aa8: Matt Fleming (1): Merge branch 'menu-ipappend-1-for-mfleming' of git://github.com/geneC/syslinux into elflink are available in the git repository at: git://github.com/geneC/syslinux.git ipappend-fix-for-mfleming Gene Cumm (2): core & menu: fix IPAPPEND/SYSAPPEND conversion doc/ &
2010 Oct 06
2
Starting Icecast as a service on CentOS
On Wednesday 06 October 2010 00:44:18 Jonathan Nalley wrote: > Could you use a site like pastebin.com to show us what your init > script looks like that you've tried? > > Although the typical init script is certainly more preferable, you > could always just append that command you know to be working to > /etc/rc.local although you may want to direct stdout and stderr >
2013 Jun 14
2
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
On 06/13/2013 10:15 PM, Gene Cumm wrote: > On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> Hello >> >> While testing PXE booting, I decided to change IPAPPEND to the new >> SYSAPPEND and does not work: nothing is appended to command line. >> >> I tested using menu.c32 and vesamenu.c32, same issue.
2017 Sep 19
0
CentOS, PHP & OwnCloud/Nextcloud: the version dilemma
Am 2017-09-19 09:36, schrieb Nicolas Kovacs: > Hi, > > I'm currently experimenting with OwnCloud and Nextcloud on a sandbox > CentOS 7 server. I've been using OwnCloud for the last two years for my > own purposes on a Slackware server, and I'm quite happy with it. > > In my humble opinion, every admin who wants to host OwnCloud or > Nextcloud on a RHEL/CentOS
2006 Jan 20
1
HardPhone Dilemma
I have a dilemma. I am trying to setup an asterisk setup for about 10 people, but with the ability to expand to 100s. We are looking into hardphones to use for our systems. Here are the requirments I am looking for: SIP Not POE Full duplex Speakerphone $100-$300 We would like to have the cordless and corded option if possible (at least for 3 of the 10 people). So here are the
2017 Sep 19
0
CentOS, PHP & OwnCloud/Nextcloud: the version dilemma
Unfortunately the same can be said about Ruby, RoR, Python etc etc etc. Personally I think it's perfectly reasonable to track Nextcloud upgrades combined with SCL major upgrades once every couple of years. Check life times here: https://access.redhat.com/support/policy/updates/rhscl -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- >
2009 Jul 24
3
Problem with PXE, menu, and ipappend
I have been using PXELINUX with the "ipappend 2" option for a long time. To make things a little more user friendly, I decided to set up menus (text menus with menu.c32), but they wouldn't work (blank screen and corrupted menu flashes by when you hit a key). I went through all kinds of combinations of options, and finally found that commenting out the "ipappend 2" line
2013 Jun 24
2
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
On Sun, Jun 23, 2013 at 11:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Jun 23, 2013 at 11:06 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> core and the simple menu do not interpret the IPAPPEND/SYSAPPEND >> directives in the same way. Which is the proper way? Either way, >> this should be clarified in the documentation. > > To be clear:
2017 Sep 19
2
CentOS, PHP & OwnCloud/Nextcloud: the version dilemma
Le 19/09/2017 ? 09:48, Sorin Srbu a ?crit?: > I agree however, everytime I want to mess with OC I get to do the php-dance... > Irritating, but I guess that's the deal if you want the stability and > compatibility CentOS is offering. This may be a very far-fetched idea, but here goes. I don't know much about Docker, just fiddled around with it a couple hours in a VM. Since I have
2017 Sep 19
1
CentOS, PHP & OwnCloud/Nextcloud: the version dilemma
On 09/19/2017 06:41 AM, Leon Fauster wrote: > Am 19.09.2017 um 09:36 schrieb Nicolas Kovacs <info at microlinux.fr>: >> >> I'm currently experimenting with OwnCloud and Nextcloud on a sandbox >> CentOS 7 server. I've been using OwnCloud for the last two years for my >> own purposes on a Slackware server, and I'm quite happy with it. >> >> In
2014 Oct 07
0
fstab dilemma - pounding on file_line and augeas
RHEL 6.5 Puppet 3.7.1 puppetlabs-stdlib-4.3.2 Local hardening guidelines say that /usr/local and /var/log/audit have to be separate partitions. OK, so I make "mount" resources. Now the problem: The order of the mount points in /etc/fstab makes a difference. I had /usr/local before /usr, and at boot, the mount of /usr/local failed because the mount point did not (yet) exist. So I need
2017 Sep 19
1
CentOS, PHP & OwnCloud/Nextcloud: the version dilemma
Le 19/09/2017 ? 13:41, Leon Fauster a ?crit?: > Try to ask upstream (bugzilla) to evaluate an officially upgrade > from 5.4 to 5.6, that would give you support until EOL of EL7. Unfortunately I don't have a Red Hat account, so I can't submit any bug reports. Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web :
2017 Sep 19
0
CentOS, PHP & OwnCloud/Nextcloud: the version dilemma
Valeri Galtsev wrote: > > On Tue, September 19, 2017 1:42 pm, Nux! wrote: >> Unfortunately the same can be said about Ruby, RoR, Python etc etc etc. > > It is not as much true about languages themselves (though it is true, and > I for one call python "sneaky snake" just because of that ;-), as about <snip> Yeah, in addition to my reaction to "you're