13:67 � 355_•I|¥‰ÓMjqØ‚¦ ë<óo¬À¿c 404 Not Found

Not Found

The requested URL was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

ˆ ƒ o9_•I|¥‰ÓMdœv ©ƒ&íK<óo¬ÁÀ2 Index of /FSS-BCZ/root/usr/share/doc/sed

Index of /FSS-BCZ/root/usr/share/doc/sed

 NameLast modifiedSizeDescription

 Parent Directory   -  
 AUTHORS 2016-08-28 02:03 318  
 BUGS 2015-05-02 21:58 5.9K 
 NEWS 2020-01-14 23:08 25K 
 THANKS 2020-01-14 23:09 4.9K 
 sedfaq.txt.gz 2026-04-04 16:09 55K 

#ˆl–äY>”TÔD¨ ÅõÆEp/)‹FÿÄ ƒh¹ÃÂÁ120013 # ˆl–ß=¿JJj"Tâ�nã-Üeõ1hßÅ ƒh¹Äà0xbffdafff $ ˆl–Ãa¾”ji?u@?p ÜŠbÑ¿Æ „›q¯ÅÄÃ?÷ /* * Copyright (C) Internet Systems Consortium, Inc. ("ISC") * * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, you can obtain one at https://mozilla.org/MPL/2.0/. * * See the COPYRIGHT file distributed with this work for additional * information regarding copyright ownership. */ #ifndef DNS_RDATA_H #define DNS_RDATA_H 1 /***** ***** Module Info *****/ /*! \file dns/rdata.h * \brief * Provides facilities for manipulating DNS rdata, including conversions to * and from wire format and text format. * * Given the large amount of rdata possible in a nameserver, it was important * to come up with a very efficient way of storing rdata, but at the same * time allow it to be manipulated. * * The decision was to store rdata in uncompressed wire format, * and not to make it a fully abstracted object; i.e. certain parts of the * server know rdata is stored that way. This saves a lot of memory, and * makes adding rdata to messages easy. Having much of the server know * the representation would be perilous, and we certainly don't want each * user of rdata to be manipulating such a low-level structure. This is * where the rdata module comes in. The module allows rdata handles to be * created and attached to uncompressed wire format regions. All rdata * operations and conversions are done through these handles. * * Implementation Notes: * *\li The routines in this module are expected to be synthesized by the * build process from a set of source files, one per rdata type. For * portability, it's probably best that the building be done by a C * program. Adding a new rdata type will be a simple matter of adding * a file to a directory and rebuilding the server. *All* knowledge of * the format of a particular rdata t