similar to: isolinux probles

Hello, I?m trying install "icecast-1.3.12" on my Linux Red Hat 7.2. When I introduce: ./configure it give me back: creating cache ./config.cache Building icecast-1.3.12... checking for a BSD compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets ${MAKE}... yes checking for working aclocal... found checking

I have just uploaded a new version of the 2.0.2b .lrp: http://shorewall.net/pub/shorewall/shorewall-2.0.2b/shorwall-2.0.2b.lrp ftp://shorewall.net/pub/shorewall/shorewall-2.0.2b/shorwall-2.0.2b.lrp This version already includes the normal LEAF changes that are present in the shorewall.lrp distributed with Bering and Bering-uClibc. Thanks to K.-P. Kirchdörfer, future versions of the .lrp will

https://bugs.freedesktop.org/show_bug.cgi?id=70130 Priority: medium Bug ID: 70130 Assignee: nouveau at lists.freedesktop.org Summary: unable to compile fragment shader program Severity: normal Classification: Unclassified OS: Linux (All) Reporter: infyquest at gmail.com Hardware: x86 (IA32)

The 2.0.2 .lrp released yesterday contained the wrong version of /usr/share/shorewall/functions. I have updated the .lrp with the correct version of the functions file. [root@lists shorewall-2.0.2]# ls -l shorwall-2.0.2.lrp -rw-r--r-- 1 root ftp 78325 May 14 06:28 shorwall-2.0.2.lrp [root@lists shorewall-2.0.2]# grep shorwall 2.0.2.md5sums 3ae771fcbfe217006e88e69a597c6455

Attached please find updated build and publish scripts. They set the ''ulink.target'' parameter appropriately when converting docbook->HTML. I have always hacked my xhtml/params.xsl file to set this parameter; these updated scripts make that abomination unnecessary. Paul/Mike: It might be a good idea to add a CVS project for these scripts. -Tom -- Tom Eastep \ Nothing is

Latest syslinux 2.00 stable version from freshmeat. Are the programs that will just copy boot sectors or create boot sectors for /dev/hda1, /dev/hda2 etc.. that I can simply copy with a dd command? Mohan -----Original Message----- From: leaf-user-admin at lists.sourceforge.net [mailto:leaf-user-admin at lists.sourceforge.net]On Behalf Of Luis.F.Correia Sent: 05 November 2002 15:01 To: leaf-user

Hello, I would like to use .lrp version of 2.1.3 Shorewall development release. But it is not accessible on FTP/WWW server and LrpN project on the CVS Repository includes some old version. So my question is - is there any script for creating .lrp file from .tgz or .rpm instead of hand work? ;-) Thank you, Milos

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The packages that I uploaded earlier were unfortunately incorrect. I have uploaded the correct packages. The incorrect md5sums are: 14e8f2bfa08cc5ca2715c8b1179d5eb2 shorewall-2.0.10-1.noarch.rpm 54bcbb2216ad3db9870507cd9716fd99 shorewall-2.0.10.tgz c2fe0acc7f056acb56d089cf8dafa39a shorwall-2.0.10.lrp The correct md5sums are:

Beta 1 is now available. http://shorewall.net/pub/shorewall/Beta ftp://shorewall.net/pub/shorewall/Beta Contrary to my previous plan, Beta 1 uses the same file and directory names as the current Shorewall version so the Beta will not be able to co-exist with a Shorewall 1.4 installation. Before installing the Beta, please review the release notes carefully. Once you have installed the Beta,

Hi I have noticed that some versions of syslinux later than 1.66 fail to install a working boot block on a CF card in Soekris net4521 board. The Bios is: comBIOS ver. 1.05 20020419 Copyright (C) 2000-2001 Soekris Engineering. The card is a 64M Sandisk and I am useing a version of LEAF called WISP-dist but I also experianced the same problem with the Bering distro. Here is my syslinux.cfg:

---------- Original Message ---------------------------------- From: "Jim Van Eeckhoutte" <jim@vaneeckhoutte.com> Reply-To: <jim@vaneeckhoutte.com> Date: Mon, 8 Jul 2002 15:27:14 -0700 this is shorewall status output: tcp 6 431899 ESTABLISHED src=192.168.20.5 dst=64.4.12.45 sport=2185 dport=1863 src=64.4.12.45 dst=63.25.123.58 sport=1863 dport=2185 [ASSURED] use=1

Hi all .... I Have installed Bering LRP on Many sites and I am very pleased with the capabilites of shorewall. Howerver I came across a prob that I am unaware ot its solution. Using shorewall 2.0.2f Kernel 2.4.24 On one Site LRP box serves internet outgoing connections through ( static IP ) a DSL line AND an incoming dial-in PPP conection. My shorewall configuration Is based upon the fact

--On Wednesday, January 15, 2003 8:57 AM +0000 Julian Church <jc@ljchurch.co.uk> wrote: > Tom > > There''s no reason you should let a complete stranger question your better > judgement, but weren''t you supposed to be taking a break from all of this? > The problem I am having is "Now what do I do with myself in the early mornings and evenings?":

A little over a week ago I posted asking about setting up a linux box between an existing router and a switch in order to provide firewall service to a subnet of machines. I was curious what experience others had with this type of setup in terms of machines, configurations, and the appropriateness of using linux in this manner. There were basically three issues discussed in replies: hardware

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In this release: 1) Dynamic Ipsec Zones now work. 2) Output Traffic Accounting by user/group is supported (thanks to Tuomas Jormola). 3) The following negative test options are added in /etc/shorewall/ipsec and /etc/shorewall/masq: reqid!=<number> spi!=<number> proto!=esp|ah|ipcomp mode!=tunnel|transport

The first alpha version is in CVS -- /Shorewall and /Shorewall-docs. There are tarballs at: ftp://ftp1.shorewall.net/pub/Alpha Sorry -- no .lrp yet... -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net

This release just rolls up the fixes for the few problems that have surfaced in the first two to three weeks of Shorewall 2.2 availability. If 2.2.0 is working ok for you, there is no reason to upgrade. So far I''ve been very pleased with the stability of the 2.2 release and attribute much of that to the new release model. http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.1

Original was DOA. Updated MD5 sums are: ec30299a4c60f026838a02927b37cb71 releasenotes.txt 40017223e14f7b47a165eed599d13da6 shorewall-2.2.0-0Beta5.noarch.rpm c9ae4690d342c9602a696084d3f786a4 shorewall-2.2.0-Beta5.tgz 139703c7a28a32c9f2ad90548644a874 shorewall-docs-html-2.2.0-Beta5.tgz 8da4e53fbea986083483c878dca879f8 shorewall-docs-xml-2.2.0-Beta5.tgz 343d085a4fc8224bd105701717065f1f

This is from Sean Covel: -------------------------------------------------------------------------- parsefw is a C program to parse Shorewall (netfilter) logfiles and display them in a pretty format similar to the old ipchains format. Some text is added about certain well-known destination ports, and they are linked to a FIREWALL FAQ website for further explaination. The original parsefw.c was

This is a minor release of Shorewall. In this release: 1. RFC1918 checking in the mangle table has been streamlined to no longer require packet marking. 2. A ''check'' command has been added that does a cursory validation of the zones, interfaces, hosts, rules and policy files. 3. UPnP probes (UDP port 1900) are now silently dropped unless explictly ACCEPTed. 4. The