Sponsored Content
Full Discussion: Unix/Linux Support?
Top Forums UNIX for Dummies Questions & Answers Unix/Linux Support? Post 46143 by cbkihong on Friday 9th of January 2004 12:13:55 AM
Old 01-09-2004
The point is closed-source software needs official support because the developers are the only people with access to source code for maintenance. For open-source software, anybody with the knowledge can provide good support. Don't forget the point that open-source software are not developed by a single delegated team of developers in the first place, but by members from the public. So it seems natural that they be supported by the public as well.

And, evidence shows that patches for open-source OSes usually come even faster than that of closed-source ones.

Of course, for some "obstinate" enterprises that insist on buying expensive service contracts as an absolutely essential part of the procedure, then software without official support are not for them.
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SMP support in Linux 7.3

What is the SMP support like when you are running Linux 7.3 on a system with 2-4 CPUs? (3 Replies)
Discussion started by: AngryRabbi
3 Replies

2. Linux

Ntfs5 Support For Linux

Hello, the other day i was trying to mount my WindowsXP partition in Linux and it said that the fs type was not supported. I know that WindowsXP does not use ntfs but uses ntfs5. If any of you guys know where i can find a file that will allow me to mount my ntfs5 please tell me. by the was i am... (1 Reply)
Discussion started by: xcaliber
1 Replies

3. Hardware

How to make terminals with a PC(UNIX/LInux) support?

I want to build a network, in this network there is only one PC and 50 terminals, 50 students can use this system to study UNIX/Linux. In the old days, computer was very expensive, many scientists shared a computer with terminals, that means a terminal has no cpu, memory and hardisk. In... (5 Replies)
Discussion started by: haixiao_liu
5 Replies
FBB::IFdStreambuf(3bobcat)				File Descriptor Input Stream Buffer				FBB::IFdStreambuf(3bobcat)

NAME
FBB::IFdStreambuf - Input stream buffer initialized by a file descriptor SYNOPSIS
#include <bobcat/ifdstreambuf> Linking option: -lbobcat DESCRIPTION
FBB::IFdStreambuf objects may be used as a std::streambuf of std::istream objects to allow extractions from a file descriptor. File descriptors are not defined within the context of C++, but they can be used on operating systems that support the concept. Realize that using file descriptors introduces operating system dependencies. NAMESPACE
FBB All constructors, members, operators and manipulators, mentioned in this man-page, are defined in the namespace FBB. INHERITS FROM
std::streambuf ENUMERATION
The public enumeration Mode defined in the class FBB::IFdStreamBuf has the following values: o CLOSE_FD, indicating that the file descriptor used by the object must be closed; o KEEP_FD (the default) indicating that the file descriptor used by the object must not be closed. CONSTRUCTORS
o Ifdstreambuf(): This constructor initializes the streambuf, without associating it to a file descriptor, and without using buffering. The member open() can be used subsequently to associate the object with a file descriptor and optionally a buffer size. When the object is destroyed or if the mode-less overloaded version of the open member is called, the file descriptor will not be closed. o Ifdstreambuf(Mode mode): This constructor initializes the streambuf, without associating it to a file descriptor, and without using buffering. The member open() can be used subsequently to associate the object with a file descriptor and optionally a buffer size. When the object is destroyed or if the mode-less overloaded version of the open member is called, the Mode argument determines whether the file descriptor will be closed or will remain open. o IFdStreambuf(int fd, size_t n = 1): This constructor initializes the streambuf, associating it to file descriptor fd, and an optional unget buffer size (by default hav- ing size 1). When the object is destroyed or if the mode-less overloaded version of the open member is called, the file descriptor will not be closed. o IFdStreambuf(int fd, Mode mode, size_t n = 1): This constructor initializes the streambuf, associating it to file descriptor fd, and an optional unget buffer size (by default hav- ing size 1). When the object is destroyed or if the mode-less overloaded version of the open member is called, the Mode argument determines whether the file descriptor will be closed or will remain open. There is no copy constructor. MEMBER FUNCTIONS
All members of std::streambuf are available, as FBB::IFdStreambuf inherits from this class. Some of the std::streambuf's member are over- ridden by FBB::IFdStreambuf, see below. o void close(): The file descriptor used by the IFdStreambuf is closed, irrespective of the Mode that was specified when the IFdStreambuf object was constructed. Following close the IFdStreambuf object can no longer be used until one of its open members has been called. o int fd() const: The file descriptor used by the IFdStreambuf object is returned. If the OFdStreambuf is not associated with a file descriptor -1 is returned. o void open(int xfd, size_t n = 1): The streambuf is (re)initialized, using file descriptor fd, and an optional unget buffer size (by default having size 1). When called repeatedly, the Mode specification used whem the object was constructed determines whether the file descriptor will be closed or will remain open. o void open(int xfd, Mode mode, size_t n = 1): The streambuf is (re)initialized, using file descriptor fd, a file descriptor closing parameter and an optional unget buffer size (by default having size 1). Depending on the Mode argument the object's currently used file descriptor will be closed or will remain open when the IFdStreambuf object is destroyed. Note that there is no overloaded assignment operator available for this class. EXAMPLE
To do FILES
bobcat/ifdstreambuf - defines the class interface SEE ALSO
bobcat(7), ifdstream(3bobcat), ofdstreambuf(3bobcat), std::streambuf BUGS
The member xsgetn(char *dest, std::streamsize n) will set istream::good() to false when fewer bytes than n were read using istream::read(). Also see xsgetn's description. Note that by default the provided file descriptors remain open. The complementary class ofdstreambuf(3bobcat) closes the file descriptor by default. This inconsistency was deliberately accepted to keep the classes interfaces backward compatible. DISTRIBUTION FILES
o bobcat_3.01.00-x.dsc: detached signature; o bobcat_3.01.00-x.tar.gz: source archive; o bobcat_3.01.00-x_i386.changes: change log; o libbobcat1_3.01.00-x_*.deb: debian package holding the libraries; o libbobcat1-dev_3.01.00-x_*.deb: debian package holding the libraries, headers and manual pages; o http://sourceforge.net/projects/bobcat: public archive location; BOBCAT
Bobcat is an acronym of `Brokken's Own Base Classes And Templates'. COPYRIGHT
This is free software, distributed under the terms of the GNU General Public License (GPL). AUTHOR
Frank B. Brokken (f.b.brokken@rug.nl). libbobcat1-dev_3.01.00-x.tar.gz 2005-2012 FBB::IFdStreambuf(3bobcat)
All times are GMT -4. The time now is 03:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy