The Bridge 2000-August Archive by Date

Wayback MachineAbout this captureCOLLECTED BY Organization: Alexa Crawls Starting in 1996, Alexa Internet has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to the Wayback Machine after an embargo period. Collection: Alexa Crawls DE Crawl data donated by Alexa Internet. This data is currently not publicly accessible TIMESTAMPSloading

Starting:Wed Aug 2 08:49:43 2000
Ending:Thu Aug 31 09:47:56 2000
Messages: 53

Last message date:Thu Aug 31 09:47:56 2000
Archived on:Thu Aug 31 01:32:53 2000

This archive was generated by Pipermail 0.05 (Mailman edition).

E2compr 0.4 User Manual – compression error

Wayback MachineAbout this captureCOLLECTED BY Organization: Alexa Crawls Starting in 1996, Alexa Internet has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to the Wayback Machine after an embargo period. Collection: Alexa Crawls DE Crawl data donated by Alexa Internet. This data is currently not publicly accessible TIMESTAMPSloadingGo to the first, previous, next, last section, table of contents.

[Note: the information below pertains to e2compr-0.3. Once I’ve addedthe appropriate code to e2fsck, I’ll probably get rid of theEXT2_ECOMPR_FL flag and just call ext2_error() whencorrupted compressed data is found. Users can use `tune2fs -e’ totell ext2_error() what to do.]

If the read/write routine in the kernel finds an error when accessingcompressed clusters, then the kernel raises the EXT2_ECOMPR_FLflag, which shows in lsattr output as an `E’ wherethe `c’ would usually be.

The kernel will still allow you to try to read the file (though you mayget an I/O error for erroneous clusters), but the kernel won’t allow youto open the file with write access while the `E’ flag is set.

You can clear the `E’ flag using chattr -E, but chances arethat it will be set again the next time the file is accessed, unless youfound the origin of the error and corrected it.

Of course, data are not lost. e2decompress should be able to beused to retrieve most of the data, with any undecompressible clustersbeing copied verbatim (i.e. the raw data), with a warning on standarderror. [Newbie note: `on standard error’ generally means `to thescreen’.]

[In e2compr versions prior to 0.3.5, user programs didn’t have readaccess to raw compressed data, so e2decompress wouldn’t work inthe way it was supposed to (so it was useless for recovering data)unless one were to reboot to a kernel without e2compr support.]

Go to the first, previous, next, last section, table of contents.

[Bridge] bridge, ipchains, and dhcp?

Wayback MachineAbout this captureCOLLECTED BY Organization: Alexa Crawls Starting in 1996, Alexa Internet has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to the Wayback Machine after an embargo period. Collection: Alexa Crawls DE Crawl data donated by Alexa Internet. This data is currently not publicly accessible TIMESTAMPSloadingAlex Winbowawinbow@mail.utexas.edu
Thu, 3 Feb 2000 20:47:01 -0600 (CST) After reading the bridge archives, and seeing the recent posts onipchains, I wonder if to ressurect a crazy old dream: bridging, chains anddhcp? I’m on a cable modem, with two linux boxen pulling dhcp throughthe hub and cable modem. I’d like to insert a firewall box in between. Trouble is, the firewall would have to bridge the networks transparently,forwarding dhcp packets silently back and forth using the original MACaddresses, so that the cable modem (and cable system) doesn’t know thefirewall is there. This seems conceivable in theory; is it remotely possible with thebridging code? (BTW, apologies if this has been covered already. I found no FAQson the subject.) Thanks, Alex Winbow __________________ T \ Alex Winbow \______________ Houston/Austin E \ awinbow@mail.utexas.edu \_________________ U.of X \________ http://uts.cc.utexas.edu/~awinbow \ A \_____________________________________\ S