Slashdot Mirror
Introducing Linux 2.2
Submitted for your approval, my final i386 change summary. (I've now had three separate "final" versions, but I really mean it this time.) This document is intended as an expanded laundry list of new features and additions to the 2.2.x kernel, a major milestone in the history of Linux.
Please note that this document does not cover all the new hardware that Linux supports. Many devices, such as scanners and printers, are handled exclusively in user space. Other devices, such as video cards and mice, are handled by a combination of user and kernel drivers. If you don't see a device class that you are interested in listed in this document, it is quite likely that Linux 2.2 supports it -- just not necessarily using the kernel to do so.
Also, I do not claim that everything in this document is PC. I believe that I am being fair and I have pulled some puches with respect to how I phrased certain portions. If you think that I should reword a certain portion so as not to offend someone, let me know but I will not make any promises.
Chips Galore The world of Intel chips is a fast and interesting thing to follow, if you have nothing better to do. Merced, Celeron, MMX... the names of Intel technologies float past to be replaced by new cutting-edge technology. (Whether or not these technologies are worthwhile is a matter that I'm not even going to begin to try and debate.) In addition, AMD, Cyrix, and other companies have become solid competitors in the market and each have their own little optimizations, quirks, and bugs. It's a mess, to say the least.Linux 2.2 will be the first stable Linux to support options for the various non-Intel processors in the kernel configuration tool. Perhaps even more importantly, Linux 2.2 (and later revisions of 2.0 for obvious reasons) supports bugfixes and workarounds for widespread processor bugs including the infamous F00F Pentium bug. Other bugs that can't be worked around, such as an AMD K6 sig11 bug, are reported during startup.
Merced hasn't arrived yet and probably isn't immediately forthcoming, but Linux 2.2 has already been ported to Sparc64, Alpha, and other 64-bit platforms so the infrastructure for a 64-bit native kernel is already happily in place. (There are, of course, other obstacles that would have to be overcome before Linux/Merced could be released but having a 64-bit ready kernel is an important step.)
Multiple-Processor machines now will operate much more efficiently than they did in Linux 2.0 with issues such as the global spinlock removed. Up to 16 processors are supported (the same as with 2.0) but the performance difference should be amazing. Also, there is now greater support for the IO-APIC on Intel boards that will make SMP generally better supported. And finally, it is now possible to specify a multi-processor configuration without ever leaving the kernel configuration tool.
In terms of other ports, Linux 2.2 will feature improved support for a large number of 'workstation' machines such as Sparc, Sparc64, and Alpha machines. As for 'desktop' machines, Linux 2.2 has been ported to Motorola's m68k and PPC processors and now can be expected to run on many of these platforms, including the Macintosh. (with varying degrees of hardware support, of course. Support for m68k Macs in particular is not ready for prime-time.) Linux is also moving to processors, such as ARM that are increasingly popular for embedded systems.
On somewhat of a tangent, there is continuing work to support a subset of the Linux kernel on 8086, 8088, 80186, and 80286 machines. This project will never integrate itself with Linux-proper but will provide an alternative Linux-subset operating system for these machines.
In terms of memory consumption, the average Linux 2.2 setup will require more memory than Linux 2.0. (Although a larger number of components can now be modularized or compiled-out to allow a system administrator more flexibility if memory is tight.) There is some debate as to what is the lower limit in terms of functionality with a text-only system but it should still be possible to have only 4 megs of RAM in many situations. (8 megs are still recommended.) On the bright side, Linux 2.2 includes a number of new optimizations that should actually improve the performance of machines with at least 16 megs of RAM. The more, the merrier.
System Busses and Assorted Ilk Although somewhat less crucial and cutting edge, Linux 2.2 will support a larger proportion of the existing x86 computers with the addition of complete support for the Microchannel bus found on some PS/2s and older machines.In addition to hundreds of minor patches to the bus system (including many new PCI device names), larger improvements have taken place. The PCI subsystem, in particular, has undergone several major changes. Firstly, the PCI device reporting interface has been changed and moved to allow for easier addition of new information fields. This particular change doesn't spell much of a difference for an end user but it makes the lives of developers much easier. Additionally, it is now possible to choose whether you want to scan your PCI bus using your compatible PCI BIOS or through direct access. This allows Linux 2.2 to work on a larger set of machines as several PCI BIOSes were incompatible with the standards and caused booting problems.
Sadly, there is still little kernel support for Plug-and-Play ISA devices. While that would be a great addition, there are some problems with the currently proposed systems that will need to be resolved sometime in 2.3 before inclusion. Fortunately enough, there happens to be a great user-level utility, isapnp, for setting up PnP devices that requires just a tad more work than we'd like but gets the job done in true Linux fashion.
Laptops and many workstations can also benifit from improved support for power management, including worksrounds for a number of incompatible BIOS implementations. Also new in 2.2 is the ability to use some functions of an APM BIOS on multi-processor systems.
IDE, and SCSI, and USB... Oh my! As far as Linux IDE is concerned, not much obvious has changed for Linux 2.2. The most obvious change is that it is now possible to load and unload the IDE subsystem as a module, just like SCSI. (This also has the added bonus of allowing one to use a PnP-based IDE controller.) For less bleeding-edge machines, the updated IDE driver now supports older MFM and RLL disks and controllers without having to load an older version of the driver. Linux 2.2 now also has the ability to detect and configure all PCI-based IDE cards automatically, including the activation of DMA bus-mastering to reduce CPU overhead and improve performance. And finally, more drivers have been developed for controllers that are buggy or simply different. It's amazing how even excellent things can continue to get better.Elsewhere in the IDE world, parallel port IDE devices have become more common and are now supported by Linux 2.2, for the most part. It is a good assumption that many devices that are not supported currently will be added as 2.2 progresses.
The SCSI subsystem's main improvements have been the addition of many new drivers for many new cards and chipsets. Too many, in fact, to even begin to name here.
PCMCIA adapters (or PC-card slots, as they are called now) are not supported in the standard Linux 2.2 but are supported by an external module provider. Thus, while not in the kernel, PCMCIA support will be included in most distributions.
IRDA support has also been added to the kernel although many controllers are not yet supported. As this feature was added only in the closing days of Linux 2.1 development, it may not be as generally usable as other, more mature, portions of the kernel.
Alas, there is some bad news here. Despite ongoing efforts by several parties to finish USB support, no support was included in time for a Linux 2.2 release. Several prominent developers have looked at USB support and it is likely that there will be some support before we get too far into Linux 2.2.x. (Alternatively, USB support could be provided through an external source in the same way that PCMCIA support is now.)
Ports: Parallel and Serial Nothing much new on this front, Linux has always had incredible support for these basic building blocks. The parallel port driver has been rewritten with cross-platform issues in mind and thus what was once just a 'Parallel Port' is now a 'PC-Style Parallel Port' Functionality-wise, the only obvious change is that you can now effortlessly share a single parallel port device with multiple device drivers. (Note however that the naming convention used to label parallel ports has changed so you may find that your lp1 has become your lp0. Distributions should allow for this change automatically however.)Serial support is chugging along as well as it always has but with one notable difference. Previously, a serial device such as a modem involved two devices, one for call-in and one for call-out. (ttyS and cua respectively) As of Linux 2.2, the two are combined in one device (ttyS) and accessing the cua devices now prints a warning message to the kernel log. On the bright side, Linux 2.2 includes support for having more than 4 serial ports, it allows serial devices to share interrupts, and it includes a number of drivers for non-standard ports and multi-port cards. My only complaint with serial support is its lack of support for the standard methods for modules to pass device parameters at module-load time via the modules.conf file and kmod. (Instead, these parameters are set using the 'setserial' command. Somewhat yuck.)
It should also be mentioned that Linux 2.2 will support newer UART chips than 2.0 which may translate into higher transfer rates using newer modems.
CD-ROMs, Floppies, and removable media Thankfully, the hodge-podge of hundreds of CD-ROM standards has solidified behind the 'standard' of ATAPI CD-ROMs. This reprieve has given developers time to completely rewrite the CD-ROM driver system to be more standardized in terms of support. Small, quirky differences between the individual drivers have now all been fixed for better support.Rewritable CD-ROMs aren't supported nearly as well as one would like, unfortunately. SCSI CD-ROMs are well done (and most IDE drives use SCSI-over-ATA, the SCSI-emulation driver). With other rewritable CD-ROMs, your mileage may vary.
Floppies are working as well as ever. There are new developments in terms of large volume floppies and it remains to be seen whether or not all of these will be supported. Those devices that communicate using ATAPI (a large number of them, actually) are already supported to some degree.
IOMEGA's zip drive, an increasingly popular storage solution, is fairly well supported under Linux 2.2. These beasts come in three versions: SCSI, ATAPI (IDE), and Parallel. Under SCSI and ATAPI, the Zip drives are supported just as any other disk would be. The parallel version of these drives actually use a sort of SCSI-over-parallel protocol that is also supported in Linux 2.2. (Other IOMEGA solutions such as DITTO drives may also be supported using the ftape drivers.)
DVD drives are already supported, to some degree, under Linux as they represent themselves largely as ATAPI drives. (SCSI DVD drives may not, but they will probably work using the excellent SCSI CD-ROM driver.) Unfortunately, this does not necessarily mean that all will be rosy in the Linux/DVD world as Linux does not currently support any DVD-centric filesystems that have been proposed nor are any user-space tools developed to display DVD movies and etc. Once the standards stabilize a bit, it is highly likely that the requisite parts will be added to the Linux kernel sometime during the 2.2.x cycle, following the initial release.
Other removable media may or may not be supported under Linux 2.2. If the device connects through the parallel port, it is possible that it is supported using one of the Parallel Port IDE device protocol modules that are included in the kernel.
Glorious Sounds! At long last, the sound code has been partially rewritten to be completely modular from start to finish. Distributions will be able to more easily include generic sound support out-of-the-box for their users as well as making it easier for the rest of us to load and configure sound devices. (Especially pesky Plug-and-Play ones.) Lots of new sound devices are supported as well and it looks like this is one area where Linux will really improve in the next year.One very notable defect here is the remaining lack of support for the PC internal speaker, if only for completeness. Then again, Windows 95/98 doesn't do it either so who am I to judge?
Video4Linux Linux 2.2 now has amazing support for a growing number of TV and radio tuner cards and digital cameras. This is a truly bleeding edge addition to 2.1's roster so there may still be some outstanding issues but it is reasonable to assume that they will be fixed in time. In my humble opinion, this is just an amazing area for Linux to be in at all. Back me up, Scotty! Linux 2.2's backup and tape device subsystem has not changed much since the 2.0 release. More drivers for devices have been written, of course and substantial improvement has been made for backup devices that work off of the floppy disk controller (including the IOMEGA DITTO).Rewritable CD-ROMs have become a popular solution for backing up data and they are supported under Linux 2.2 There are still outstanding issues in this regard, see my note above on CD-ROMs for details.
Joysticks, Mouse, and Input Devices Joysticks are better supported in 2.2 including a large number of new joysticks and joysticks with an inordinate numbers of buttons. Likely, your joystick will work under Linux 2.2.Mice in 2.2 aren't really different from mice in 2.0. (As in 2.0, there are some inconsistencies regarding mouse support that will be addressed in the future. For the most part, mouse control is provided through a daemon external to the kernel. Some mouse drivers however deliberately emulate a Microsoft standard mouse. The reasoning behind this is obvious but it would be nice if it was decided on in one way or the other.) It should be noted that, while not solely a kernel issue, mice with Microsoft's spinning wheel extension are supported in recent versions of the XFree86, Linux's most popular GUI. (However many Linux applications have not been designed to take advantage of this feature.)
Additionally, several other input devices are now supported under Linux 2.2 including some digitizer pads. If your devices emulates a mouse (as many do) then it is already supported by Linux 2.2 (and, in fact, Linux 2.0).
Video Perhaps the most surprising and cutting-edge addition to the Linux kernel version 2.2 is what is called the 'frame-buffer console' driver (or 'fbcon', for short.)Previously, the Linux kernel (for Intel-based machines) only understood and manipulated the video devices in text mode. Graphical support was to be provided by two other systems: 'svgalib' for console-based graphics, and a specialized X Server for window-based graphics. This kludgey system often required configuration information to be repeated and each system supported only a limited slice of the myriad of video devices in common use.
Since this addition is rather new, it remains to be seen whether it will truly replace the previous and long-standing duality. Unfortunately, it could be nearly a year after Linux 2.2 ships before this new system could be robust enough to support the cards and technologies that we already take for granted as working. My personal opinion is that this is the right idea, but I'm going to withhold judgment until we see exactly how far Linus and the developers decide to take this feature.
As an added side-effect of this new feature, primitive multi-heading has been added into the kernel for some devices. Currently, this is limited to some text-mode output but it is reasonable to assume that this very new addition to the Linux kernel will mature somewhat during the 2.2.x and 2.3.x cycles.
It should also be mentioned that it is now possible to remove support for 'virtual' terminals as provided by the kernel. This allows very memory-conscious people to save just a tad more.
Although unimaginable to the desktop user, Linux can now work even better on systems that do not actually include any sort of video device. In addition to being able to log in over serial or networked lines, as Linux 2.0 and previous Linuxes allowed, it is now possible to redirect all the kernel messages (usually sent to the console directly before any hardware was initialized) to a serial device.
Networking: Ethernet, ISDN, and the lowly modem. I don't have a huge amount of experience here; I've been using the same network cards in all my machines for several years. But, it doesn't take an Alan Cox to see that the number of supported Ethernet and ISDN devices supported in Linux 2.2 has risen sharply. I have been told that newer solutions such as cable modems are supported, also.My only gripe in this regard is the continued non-support of so-called 'Winmodems.' Not that I blame Linux for their absence, making modems that are 80% software is just a dumb idea anyway, but the idealist in me hopes that some day these pesky devils will be supported like their less stripped cousins.
Amateur Radio people are Linux people, too. Since before Linux 2.0, Linux has been one of the few desktop OSes to include native support for computer-based amateur radio people. (Not that I actually know what that entails but it seems to be a more popular option outside the US.) Linux 2.2 adds support for NetROM and ROSE amateur radio protocols. The basic AX.25 layer has also been materially enhanced. Filesystems for the World Linux 2.2 has a wide array of new filesystems and partition types for interconnectivity. In addition, many of Linux's supported filesystems (including those I haven't listed here) have been updated with a new caching system to markedly improve performance. (In fact, not updating the drivers wasn't even an option if one wanted them included in Linux 2.2.)For the Microsoft nut, Linux will now read NTFS (Windows NT) drives and Windows 98's FAT32 drives (also used by some later versions of Windows 95). Linux 2.2 also understands Microsoft's Joliet system for long filenames on CD-ROMs. And finally, Linux also understands a new type of extended partition that Microsoft invented. Drivers to read and write Microsoft and Stacker compressed drives are being developed but not yet included in the kernel. There is continuing work with NTFS to allow for both reading and writing, but that support is still experimental.
For Mac connectivity, a HFS driver for reading and writing Mac disks has been included. HFS+ and MFS (ancient floppy format) are not yet supported. Macintosh partition tables can now also be read by the kernel; this allows Mac SCSI disks to be mounted natively.
Sadly, OS/2 users will still not be able to write to their HPFS drives. Some updates have been made to the HPFS driver to support the new 'dcache' system but not the complete overhaul that some were hoping for. There is ongoing work outside the kernel to include read/write support in this driver but those changes did not make it into the initial release of 2.2.0.
If there are any Amiga users left (and there are), they will be pleased to know that the FFS driver has undergone some minor updates since 2.0. This is especially useful as the new generation of PPC Amigas will continue to support this format.
For connectivity to other UNIXes, Linux 2.2 has come forward in leaps and bounds. Linux 2.2 still includes the UFS filesystem which is used on BSD derived systems, including Solaris and the free versions of BSD. Linux 2.2 can now also read the partition table formats used by FreeBSD, SunOS, and Solaris. For SysV-style UNIXs, Linux 2.2 features a somewhat updated version of SysVFS. Linux 2.2 can also read the Acorn's RiscOS disks. And finally, Linux 2.2 features a somewhat updated version of the ever-popular Minix filesystem, which can be used for small drives and floppies on most UNIXes. With so many incompatible formats (and Linux 2.2 reading so many of them), it's amazing anyone ever got any work done.
In other news, support for 'extended' drives (the format used by much older versions of Linux) has been removed in favor of the 'second extended' filesystem. (This shouldn't matter to many people, 'ext2' is far superior to its predecessor.) With the increased support of initial ramdisks, a 'romfs' has been created which has very minimal overhead.
While not quite a filesystem, Linux 2.2 includes enhanced support for stretching a filesystem across several disks transparently. At present, this support can be used in RAID 0, 1, 4, and 5 modes as well as a simple linear mode.
Networking II: Under the Hood On the protocol front, a lot has happened that I simply don't understand completely. The next generation Internet protocol, IPv6, has made an appearance. SPX, a compliment to IPX is new, as well. DDP, the protocol of choice for older AppleTalk networks has also been improved. And, just as you would come to expect by now, the existing protocols have been improved, as well. I only wish I had the need to use some of this stuff...On the low-end front, not much has changed. PPP, SLIP, CSLIP, and PLIP are all still available for use. I guess some things don't need much improvement. (Although each of those drivers have been updated in one way or another.)
The list keeps going, however. Linux 2.2 will have an excellent new networking core, new tunneling code, a completely new firewalling and routing system called 'ipchains', support for limiting bandwidth consumption, and a ton more. It's just amazing. I wish I could keep track of it all. (But, who am I kidding?)
It should be noted that file and printer sharing protocols have also been improved and markedly enhanced. SMB, the protocol for accessing Windows-based shared filesystems has been somewhat improved with bugfixes and the like. If you are a fan of NetWare (some people are...), you'll be happy to know that Linux 2.2 supports a large number of improvements in this area, including access to two different kinds of NCP long file names. Trusty NFS has also been improved, both at the server level and the client level. And finally, those eggheads over at CMU have been hard at work developing the new distributed network filesystem, Coda. This filesystem supports a large number of highly-requested features including disconnected operations for laptops, an advanced cache system, and security improvements.
On somewhat of a tangent, Linux 2.2 also includes a driver which will allow one to share (and remotely mount) whole disk images over a network.
Not Everyone Speaks English. Linux 2.0 is a very international OS with support for international keyboards and the like. Linux 2.2 adds to this and other internationalization features the ability to load some Microsoft/UNICODE codepages for translating filenames into Linux's native system. (Which is UTF8, another encoding of UNICODE) Currently, the only filesystems that use these translations include Microsoft's VFAT and Microsoft's Joilet ISO 9660 (CD-ROM filesystem) extension. Unix98: The Next Generation Linux 2.2 will be a more 'standard' UNIX in a number of ways. The most pronounced of these ways to the end user will be the addition of UNIX98-style Pty devices using a new filesystem (devpts) and a cloning device to provide the functionality. And, finally... In addition to those noted above, there are a large number of other drivers and things that just don't fit in anywhere but should still be noted. So, in no given order, the oddball updates of Linux 2.2:The loopback driver, which allows disk images to be mounted and manipulated just like any regular drive, has been improved in a number of ways. Of these improvements, the most notable difference to users will be its increased support for encryption and the mounting of encrypted hard disks and disk images.
A driver for accessing your computer's CMOS memory has also been provided in Linux 2.2 which may be useful in some applications. (Sadly, a similar driver to access your BIOS's flashable RAM did not make it, it will still be necessary to boot from a DOS floppy to flash your computer's BIOS to a new version.)
And finally, in the past, Linux used a half-user/half-kernel method of loading in and out drivers (called 'modules') called 'kerneld' This method was good but inefficient. Linux 2.2 has removed kerneld and replaced it with a smaller all-kernel solution called 'kmod'.
This is the 'revised millennium penguin' version of this document (1/26/99) and is really just a minor update over the last three final versions. Linux 2.2 is out now, so obviously no new features will be added and I should be safe.As always, I can be reached at jpranevich@lycos.com.
Thank you, and Good Night.
Joseph Pranevich
This has been on linuxtoday.com for a while
I'm glad I didn't complile last night. :-)
for that first patch to appear, did it? ;-)
Does anyone know if there's any work being done for support of union/overlay filesystems, like BSD got in 4.4?
Sigh. I hope we have something better to show
people out there. This piece is embarrasing!
Full of "In my opinion.." and meaningless
babble "gee, it's great and it became better".
Don't tell me to lighten up. This is a disgrace.
"My only gripe in this regard is the continued non-support of so-called 'Winmodems.' Not that I blame Linux for their absence, making modems that are 80% software is just a dumb idea anyway, but the idealist in me hopes that some day these pesky devils will be supported like their less stripped cousins. "
Unfortunately, every single winmodem (and even revisions of winmodems, as the driver installs will sometimes update the firmware) have different interfaces. The only way for a winmodem to work is for the modem manufacturer to write it.
If there was one driver that needed to be written to get all winmodems to work, you could be sure some kernel hacker would go to it, if for no other reason than to get people to stop whining about it, or to save him $40 on the cost of his next 56k modem..
But with (by my estimate) 50 different types of winmodems out there, nobody cares. They will just be sure to spend the extra $40 and get a modem that works.
Umm, it is my currrent understanding that if you run FBCON, your console is locked into a specific resolution... THAT IS NOT TEXT MODE. Correct me if I'm wrong, but IMO this sucks. I think that something like KGI (from what I understand of KGI) would be much cooler.
Solaris is not, as the article suggests, BSD-derived. The old SunOS was, but Solaris is definitely SysV-derived.
-jaz
I think there's a paragraph missing in the Video section between paragraphs two and three. In two he says what "the old way" of doing support is, then in paragraph three, talks about the ramifications of "the new way" without ever discussing what "the new way" is. _I_ know what fbcon is about, but probably not everyone does.
Lighten up.
If you'd been following linux-kernel, you'd have noticed a fair amount of work going into an idiot friendly press release.
Slashdot is news for nerds and this article is of a suitably technical nature for nerds. Who wants watered down articles on Slashdot?
fbcon isn't that bad. I use the VESA 2.0 fbcon driver, in 640x480x8bpp. My console behave exactly as before, with one exception. Shift-PgUp no longer scrolls back on the display. But as far as switching resolutions and such, I've had no problems switching back and forth between consoles and XFree86 3.3.3(3DLabs Server), or with running (and exiting) SVGAlib games.
KGI behaves in much the same way, as far as the user-interface goes, but allows for modular card-specific drivers to accelerate the video. Technically, this could also be done for fbcon, but not as gracefully. KGI also adds quite a bit of security for switching between video modes, and a more extensive GGI interface for builing simpler X servers and other UIs on top of the console driver, without all the kludge we currently see in SVGAlib and X.
Not everyone knows everything there is to know about the Linux kernels. Some people just buy Redhat and install it and don't think twice about what capabilities they may or may not have. Ever try to find out what a product does by reading the company's commercial website? That is informationless babble...
Is this another release or something? How can /.
just throw that on the main page and not explain it.
What about all us clueless people hehe.
I hope I dont have to download another 12 megs.
I'm sure we'd all be happy to see your version
of the 2.2 overview . . . so where is it?
Simply saying "disgrace" is utterly useless --
you've added nothing.
But if you use it you get a warning in the kernel log. No biggy.
So where's -your- writeup...
If you dont like it, then show us how you can do better... After all that's what OSS is all about.
IMO, it's useful and readable.
I just compiled 2.2 the other day and it runs great except for one thing: Quake 2 crashes my computer. I have no idea what causes this. Has anyone else had this problem?
You can download a patch that contains the *differences* only. Your
Get it from:
ftp://ftp.linux.org.uk/pub/linux/alan/2.2/
You need bzip to unzip the file.
Get bzip/bunzip from:
http://www.muraroa.demon.co.uk/
You could say it's BSD derived in the sense that
SVR4 was a merge of BSD 4.3 and SVR3, and Solaris
is SVR4 derived.
At any rate, the Solaris UFS is certainly BSD
based code.
Troll. Ignore him. It's not true.
Solaris is, incorrectly, being called a BSD derived system, which is (mostly) false -- with the caveat mentioned by the next poster.
So on how Linux has it's version numbering.. If it followed Microsofts version numbering we would all be using Linux V16 or would that be Version 32?
Aint it silly how Microsoft calls a buxfix or patch a new version? Ohh gotta go get Win98! it's much better than win95! let alone the jump from 3.11 to 95 (4.0) oh yeah that was a re-write.. HA!
This is yet another example of how Linux will achieve the "world domination" and Microsoft and Apple will be merely footnotes in the fodder of society.
I actually followed the instructions on the Changes and here is what I got(with some editing):
(NOTE: I did not install everything mentioned)
#########################
insmod version 2.1.85
(gcc -v) 2.7.2.3
GNU ld version 2.9.1 (with BFD 2.9.1.0.15)
(rpm -q glibc) glibc-2.0.7-29
(rpm -q libc) libc-5.3.12-28
ldd (GNU libc) 2.0.7
procps version 1.2.9
This is procinfo version 14 (1998-05-24)
pstree from psmisc version 17
net-tools 1.46
hostname 1.97 (1998-06-29)
basename (GNU sh-utils) 1.16
Linux automount version 3.1.1
Universal NFS Server 2.2beta37
ncpmount must be installed suid root (hrm).
(rpm -qf `which ncpmount`) ncpfs-2.2.0-1
pppd version 2.3 patch level 5
util-linux 2.8
################
Compare that with what was mentioned in Documentation/Changes.txt
################
- Kernel modules 2.1.121
- Gnu C 2.7.2.3
- Binutils 2.8.1.0.23
- Linux libc5 C Library 5.4.46
- Linux libc6 C Library 2.0.7pre6
- Dynamic Linker (ld.so) 1.9.9
- Linux C++ Library 2.7.2.8
- Procps 1.2.9
- Procinfo 15
- Psmisc 17
- Net-tools 1.49
- Loadlin 1.6a
- Sh-utils 1.16
- Autofs 3.1.1
- NFS 2.2beta40
- Bash 1.14.7
- Ncpfs 2.2.0
- Pcmcia-cs 3.0.7
- PPP 2.3.5
- Util-linux 2.9g
###########
However, if you don't want to compile most of those things and stick to redhat's rpms, I think most are at ftp://rawhide.redat.com I also believe that net.tools for redhat may be different since a number o people clamed that dhcpcd for redhat needed to be upgraded (its in separate package).
Dhcpcd sure as heck didn't work for me when I booted linux 2.2.0pre9.
That's an important change in the 2.1.x kernels.
There's a redhat ipchains package available, no need for Slackware.
Another password forgetter: My Nick: Painting
When will there be support for the S3 ViRGE chipset? It said that the S3 Trio driver is not to be used for the ViRGE (or something like that).
What chipsets ARE supported or that have Vesa 2.0 currently?
The BSD union FS is broken and unused. There isn't even an effort to repair it. I've waited for years but the FreeBSD dipshits won't fix it. As usual FreeBSD is long on gas and short on code.
Subject says it all. What is it and what I do with it?
linux 2.2 doesn't find my swap. any ideas
-/+ buffers/cache: 31092 97104
Swap: 0 0 0
Hello, my name is Linus. You may call me L.T.
I feel that I am an expert in this field, having designed and engineered the first video card in history. I feel that the Mighty Penguin's decision to totally disavow any knowledge of the S3 Virge's existance is the right thing to do. After all, everybody knows that the Virge sucks.
Yep, they sit outside of your computer's case, have nice little lights so you can actually check their status and see if the line is open/transferring data/whatever, plus there's no way for them to be winmodems! What the fuck is it with people wanting internal modems anymore?!? External modems are superior in every single way. Arrg.
- RF (dfelker@cnu.edu)
Be sure to download the latest PCMCIA drivers, as your stock copy (IIRC 3.0.8) won't work with 2.2 kernels..
Be sure to download the latest PCMCIA drivers, as your stock copy (IIRC 3.0.8) won't work with 2.2 kernels..
(sorry bout the dopplepost.. damn less-than signs..)
Be sure to download the latest PCMCIA drivers, as your stock copy (IIRC < 3.0.8) won't work with 2.2 kernels..
(sorry bout the dopplepost.. damn less-than signs..)
with NT i can have up to 128 modems. WIth linux I CAN HAVE ONLY 4! and it is very buggy. Wow what a crappy isp server os linux would be. I am definetly sticking with NT because of the modem support and increased security.
I wonder when linux will finally support primary and backup domain controllers so I can have better security. Don't believe me on linux security, then check out the top 10 lies about windows NT on zdnet or windowsmag.com . If your linux box is not a member of a security domain then all the hacker has to do is crack your root password and he is in. With NT you need a trust relationship before the hacker can even have basic rights to the domain's resources.
One more thing! Is it really true that unix security is so weak that just loging in for email gives average users root priveledges. Boy I am glad that NT doesn't have to do this with exchange. Thats pretty sad if you have to make a different root user for every client who wants access to sendmail. Does linux even support user replication for a process like this? I think not!
yeah, i want my console to be statrek lilke with borders and status lights and lots of shit
10 lights for status,/incoming requestts, warning bar, 1 line syslog bar and round corners to boot
i want 1280 mode graphics with text on it using the inner 95% withthe rest graphics/borders/status
I WANT A KILLER CONSOLE
Is this the *same* article that was in Linux Journal, and the *same* author that posted this *same* message to a Linux web site months ago? If not, then he lifted this paragraph:
> One very notable defect here is the remaining
> lack of support for the PC internal speaker, if
> only for completeness. Then again, Windows 95/98
> doesn't do it either so who am I to judge?
with NT i can have up to 128 modems. WIth linux I CAN HAVE ONLY 4! and it is very buggy. Wow what a crappy isp server os linux would be.
I'm not for sure where you get your info, but my ISP is run off of Linux and they have a hell of a lot more than 4 modems for users to dial in with
If you'd rather use NT, go ahead. I prefer Linux, myself.
Luckily, we have a choice now.
I'll probably get flamed for saying this, but I think Katz' articles are the best ones posted here. They actually contain thought rather than covering up the inability to think with an abundance of technical information.
The people who don't get Katz' articles are generally the same people who can't see OSS as anything more than just another way to write software.
Yer on glue, I worked at an NT powered ISP for 2 years, soon as we put more than 32 modems per machine on the port servers NT started to buckle heavily!
:)
Luckily I've escaped that hellhole and get to play with Linux servers all day....what a treat
Still trying to convince that ISP to at least switch to Apache/Linux for a web server...but alas he likes his slow IIS box with it's pretty desktop.
er, was this with or without the loopback interface compiled into the kernel? Quake 1 runs just fine on my box whether or not I have the ppp0 or eth0 interfaces up...
It's hard to believe that all those large ISPs who
use linux are limited to 4 connections. The reliability and efficiency of Linux is a big plus.
It's funny that so many people assume that Microsoft invents everything, even things that have been used for ages.
The rumor is that Microsoft NT 5 will support a
central domain directory, but NT5 is a way off and a number of other vendors _already_ support this sort of thing ( Novell 4 for example ). And then there was Banyan VINES before them.
Actually you should probably learn about NT and Linux before you babble complete nonsense like this. Linux can support more than 4 modems for starters.
Secondly as an Administrator of many hundreds of NT machines across Europe and Africa looking after multiple Master Domains, I think I understand NT security/trust relationships etc... something you obviously don't. Whats this "[a hacker] needs a trust relationship..."? Do you actually know anything about NT apart from how to spell it?
I have thought about this too, but there are a number of problems (there are certainly detailed in the papers about 4.4BSD union/null/portal fs).
First this is likely to break a number of programs that make assumptions about the FS semantics. You can have several times the same filename with differents inode. Removal of files if problematic: you remove a file, but then it can still be there in an inferior layer (I think that unionfs create a "blank" entry to mark that a particular filename has disappeared ; but then reboot and do the exact same mounts: bingo, the filename reappears).
Also sometimes the expected semantics can require heavy processing ; for instance if you just wish to have a CDROM mounted and a directory were modified files would be written, there would still be a problem: you may expect that the modified files would be transparently copied ; even if you don't require this semantics, you probably prefer that the non-existing parent directories in the path of your created file would be automatically created. But then what if they are symbolic links, etc... If you don't do that, then you have to manually mirror the whole directory tree of your cdrom: at that point you may realise that you may as well mirror the whole tree using symbolic links for non-directories, and that you won very little. If you change the cdrom, or if the partition, over which you did a mount, changes (say a NFS server serving /usr/local), you have to reflect the changes in your mirror-directories, etc... (looks like a nightmare)
So I think that even though union filesystems are very useful, they are only part of any solutions when they are used in real world (for packages versionning, pretending to write other a read-only partition [cdrom, workgroup NFS server], security by restricting the visible portion of the FS...). But maybe Inferno or {Open,Net}BSD or Hurd(?) users have more informations about using union filesystems in Real World.
An idea would be to experiment with a metalevel for filesystem namespace operations, i.e. for certain processes, each of their operations involving a filename could be forwarded to another process ("metalevel process" or something) that would decide how to handle this filename, and inform the kernel. I think that kernel modification (as opposed to glibc modification) is necessary, for operation atomicity (you don't want the filesystem to change because of another process, without being informed), and because only there inode manipulation can be done.
-- Cedric Adjih (adjih@technologist.com)
With VESA 3.0 you can switch videomodes in pmode.. That would be cool... Anyone interested in implementing this?
Please don't tell us anything about Linux when you don't even know how to use more than 4 modems with it! The only thing you need to do this is a good hardware, for example four Cyclom-YeP expansion cards from Cyclades, each handles up to 32 modems. Look at http://www.cyclades.com/y-dat.html. And this is not a new feature of kernel 2.2, you can do it with the good old kernel 2.0 as well.
More cords to plug in, an extra serial port card
to buy, more clutter on my desk, a silly little
power cube plug that takes up the space of two
normal power plugs...
External modems just suck.
Linux is getting bloated. Why don't they also include the kitchen sink while they're at it?
Oh but I can recompile with only the stuff I want? Great, I'm sure your average user will be entirely comfortable doing that too. Just like the guy yesterday who "lost" his Win95 taskbar and had to get me to come over and fix it for him.
Anyone else have this problem? when I go to patch it, it comes up and asks me what file it is supposed to be applied to, and displays the first couple of lines of the patch...
what am I supposed to do from this point?
The second part, you could also do with some journaling filesystem. Or better: with a source-version-control system.
The first part, I thought I read something about a patch doing so a while ago.
Same exact trouble here...How do I implement/get the patch to fix it?
this was addressed on x11amp.org..
Where? I looked around and couldn't find anything about it on the front pages, FAQ, or the known bug list.
Guys, Warning. Don't upgrade to the glibc RPM from RawHide. ( glibc-2.0.110 ) Most user applications stop working afterwards. I just did this and I am getting ready to downgrade back.
I think Debian already does that. It has a menu
utility and packages can register with it to have
their programs added to the menu of all supported
window managers.
Try ftp://rpmfind.net/linux/rawhide/1.0/i386/RedHat/RP MS/ipchains-1.3.8-1.i386.rpm
Well... Different kinds of programs have different building instructions. Some use autoconf, some imake, some just plain Makefile. It would be next to impossible to automatize all this. I would though like a utility that would do some parsing on the output of make and would tell me exactly where did it put things ( some installs are fairly complex and I am not yet that good with reading this from screen ) and possibly even recording this in some database ( a la CleanSweep for Windows ). As for WMs Red Hat and Caldera use wmconfig ( although a little different versions ) to make common menues for common WMs. SuSe has it's own methods to do the same thing ( think it is caled SuSeWM or something... Anyway I think that SuSe would be a great distro if not for the UGLY Yast based configuration scripts and strategies ) And as always there is KDE and GNOME each of them has ways for programs to add themselves to the menu and one of these is bound to become preferred desktop manager for Linux ( unfortunately it looks like it is gonna be KDE... sucks... )
Well... That's all folks.
P.S. Nice article but it looks like the author is a bit clueless... aren't we all...
I'm a helpdesk tech. If you can't recompile, SUCKS to be you. Those that take the time to learn will have greater success with the system; don't ask us to drag it down to your level.
I'm tired of rawhide. Too much of it is pure crap. Just on e of many examples,
I installed libstdc++-2.9, and it didn't install a libstdc++-2.9 lib,
it wrote over libstdc++-2.8! Didn't anyone check this at all?!!?
They let their Guinness do their innovation? Explains a whole lot.
At least they chose a good brew this time. I heard DOS was innovated by Budweiser.
I had this problem as well. But applying the ac1 patch made the compile problem about ten times worse in my case (about 100 sb_ess related errors). I've gone back to 2.2.0pre8 (that worked better than the alleged 'final' release).
Maybe you should use it first before you judge it dumbass. There is a util called fbset that can change the resolution at any time. I kinda like watching my computer boot right into 1152x864 and watching the tux logo on the screen. And last i checked no one is forcing you to use it.
A fair summary of what has changed. Bid you well.
Fuck Ajit Pai
that's what patches are for, so you dont need to download a large file again
Why were the cua devices removed? What do you do if you want to open a port and not block on CD? Bleah.
They jump on problems fast and fix them often on the same day. I'll be getting my fresh copy of the kernel and it's associated packages and going 2.2.
:)
The "Kernel Crew" have finished an industry shaking release and now the "Kernel Maintainer" is doing his magic on the now stable source.
On the Linux front, I see SMP nodes in Beowulf Clusters. I see USB and NTFS R/W before the end of the year. I see widespread support of OpenGL in hardware. I see lots of new users and games for them. I see 25% - 30% server marketshare by 2000. I see desktop penetration take off. I see Java becoming a popular major player in crossplatform development (moreso than today). Dang! Am I rambling?
I'll just say this...
What a great community.
Codifex Maximus ~ In search of... a shorter sig.
Posted by fotang:
jeez..lighten up!
Posted by buchur:
if you want to invoke linux from the bootsector of a dos filesystem, you can use syslinux: .
Posted by Bill, the Galactic Hero:
Nice job. I like it. Having said that...
You omitted the fact that SMP for Alpha is now available for the first time.
This support came late in the 2.1 series, but Microway is selling a dual (no, not duel, godammit) 21264 which is apparently working well under Linux.
This could be good for both Alpha and Linux, as the combo will make a killer SMP server/number cruncher.
Posted by Buffy the Overflow Slayer:
At the last computer show I went to, I saw real
56K internal modems going for $48, and Winmodems
going for $33. So the difference can be as
small as $15.00. (And the $48 modem works under
linux - I bought one).
-buffy
Posted by Guy Piggford:
:-( 2 Matrox cards, 2 Voodoo II cards, Adaptec SCSI, etc. etc. don't leave a lot of expansion space.
Whilst I do agree about the blasted plug cube, I'd rather have that than give up another slot. Since I don't have any spare slots
Guy
Posted by Drizuid:
/usr/src/linux to /usr/src/linux.ac then patch then change it back to linux, then it will all work out fine, or you can edit the patch, in the first few lines it checks for linux.ac and another folder, just change one of those to say linux and change any other references to linux.ac to linux and that will work too, but the first way is easier
I had the same error what you need to do, is change
I'll write everything from now on, Kniggit, and you can steal from me. :) (Just teach me how...)
(this has been a personal message to see if jpranevich checks the comments again. Move along, nothing to see here.)
Frys has genuine internal modems for sale, with jumpers even. I think the name is ActionTec or something.
Nice write up, but I'm looking for the next step.
When 2.0.0 came out I had to compile a new version of ppp (come to think of it I'm still using that now old version) and kernel module tools.
What do I need to do to upgrade correctly? Its been hinted that I should upgrade to glibc something I've been meaning to do for a while anyway.
I do not upgrade my distribution, I upgrade what I feel like, when I feel like, from sources.
Though I'm considering not upgrading to the latest 2.2.0 kernel, I'm not sure it gains me anything over the 2.0.3x kernels.
Hmmm. With all the different platforms Linux is now running on, you'ld be surprised not to see these kinds of patches. Does Windows 98 or NT run on a Amiga or a Mac for instance? Linux does...
From 2.1.120 till now I had no problems compiling, now that 2.2.0 is out, I get
drivers/sound/sound.a(sb_ess.o): In function `ess_init':
sb_ess.o(.text+0xdfe): undefined reference to `esstype'
any one else have this problem????
Check out the Overlay Filesystem.
--
All Glory To The Hypnotoad!
Oh yeah? Then how come I'm playing an mp3 on my PC-Speaker right now via /dev/pcsp? :)
More info
I was told that support is also available for Windows, but I don't know more about that...
--
All Glory To The Hypnotoad!
fbcon, unless you use vesafb, which can only set
a mode at boot time. Yes, you are limited to
graphical modes, but that's really not a problem,
as the console works just as well, and (with
hardware accelerated drivers like matroxfb) is
damned near as fast. And with the drivers that
support scrollback, you can get huge scrollback
buffers if you have enough video memory.
Of course, I don't suppose there's anything stopping a framebuffer from supporting text as well as graphics, seeing as there was a text-only framebuffer a while ago. It's just not as much of an issue as it might seem.
http://www-stu.calvin.ed u/~clug/users/jnieho38/goto22.html
Check out http://www-stu.calvin.ed u/~clug/users/jnieho38/goto22.html
Hey buddy, I've been there and done that (1.1.13 through 1.3.3). He's done a damn fine job. If he's not an expert on all aspects of the kernel, well, nobody is these days. Lighten up; YOU're a disgrace. If you're so fardling smart, YOU do it.
-russ
And if I respond to you, am I feeding a different AC's troll? I can't win, of course.
-russ
Another thing that rocks is the MCA support: this means that I'll almost certainly be able to use a distro other than slackware on my PS/2 77, and maybe i'll even be able to get X running on the XGA-2 adapter.
I think I'll be a busy fellow for a while...
fbcon is *extremely* useful for anyone with a new video card (e.g. Voodoo Banshee) for which there is not yet an X server. Yes, it switches to a single resolution (1280x1024 for me) at boot-up and stays there, but I rarely need to change resolution anyway (and "text mode" at 1280x1024 is actually quite nice).
fbcon could also be used as the base for a prettier-looking installation/setup utility, by giving you nice graphics and windows before trying to probe for the details of your graphics card (sorry, but the RedHat install screens are rather DOS-ugly). Given my Amiga heritage, I guess I'm just not in love with "text mode" in the first place.
I'm not actively working on this -- it's not on the top of my list to get 2.2 working on my system, but I'm having some trouble, maybe someone can point me in the right direction.
The system is a Dual PentPro Compaq Proliant 6000 (which is the first problem). It's got a 3c905 Boomerang 100baseTx netcard, a triple channel aic7xxx SCSI card, and embedded dual ncr53c8xx SCSI. It has 384megs of ram. As far as I can tell, it's got a "Compaq" motherboard -- no other indication of motherboard type. Note that the SMP notes for 2.0.x say to not use certain types of hardware -- and this machine has all the types of hardware the SMP FAQ said not to use (not much I do about that, all the hardware I have access to is the same kind).
I'm currently running 2.0.35 with a single processor (scheduling in interrupt panics with SMP conf periodicly, often enough that we considered using SMP with 2.0.35 on this box unstable). When I boot 2.2pre8 (with SMP, of course) (the last one I tried), it locked hard right after the detection of the network card... nothing seemed out of the ordinary -- it found both processors, the scsi cards and their drives, and the network card. Any hints someone can provide?
BTW, for those who care, the "scheduling in interrupt" panic with 2.0.35 SMP was happening in, if I remember correctly, wait_on_buffer, which doesn't give me any indication as to which hardware was causing the problem.
This would lead to stories that claim particular features were only added to Linux on 1999-01-25.
That would be very annoying.
Read /usr/src/linux/Documentation/Changes. This file should give you all the information you need on which packages you need to upgrade, and which versions you need to have installed.
No that just makes the computers that store sells hard to buy. ;-)
--
Aaron Gaudio
"The fool finds ignorance all around him.
"Every man is a mob, a chain gang of idiots." - Jonathan Nolan, Memento Mori
The acX suffix means "Alan Cox patch X". It's basically a pre-patch for the next version (in this case, 2.2.1). They only come in patch form. There is a special area of www.linuxhq.com dedicated to Alan Cox's prepatches. Note that if you apply an ac patch, you typically have to reverse it ("unapply" it, as it were) before applying an official patch (such as the 2.2.1 patch). I don't know if you have to reverse a previous ac patch when applying a later ac patch but I think so.
--
Aaron Gaudio
"The fool finds ignorance all around him.
"Every man is a mob, a chain gang of idiots." - Jonathan Nolan, Memento Mori
Just delete /dev/cua0 through /dev/cua3, then create them as soft links to /dev/ttyS0 through /dev/ttyS3. Then you can even boot with old kernels, and have them work :)
IIRC, it was done with Unix98 compatability in mind (and better design?) It unifies the in/out interface for the serial ports.
See topic :)
I make money because I tell my clients that I can replace their NT servers with something that doesn't crash, and will do everything their old servers do. And I can do it for far less than they paid for the original server.
I've set up Primary Domain Controllers with Samba, web servers, SQL servers, multi-port cards (far more than 4 ports), etc., and they all work as advertised.
If they ask what it is, I tell them about Open Source. Otherwise, I don't even bother.
And I keep getting those darned support contracts to maintain those systems.
So, keep doing what you're doing. It only makes us linux consultants get more contracts.
We already have 27% market share in server OS's shipped, from 6% last year, according to some recent study done by IDG, as I recall.
You may certainly keep your text-mode console. I will take my 1024x768 text console with 8000 lines of scrollback.
To each his own, I guess.
Uh, yeah, right. You can have thousands of modems on a single Linux server if you really want to.
I think they key matter is that you have a recent enough version of LILO. 0.20 works just fine for me. Possible some ancient lilos won't work.
This just screams out for three little letters: USB
Powered busses [homer drool]
I've finally had it: until slashdot gets article moderation, I am not coming back.
Hmmm...Centralise security server... I wonder what happen if it crash or being hacked.....
BTW, if you don't notice, UNIX have centralise security server, using Kerbose+YP/NIS. We here in Imperial College DoC we use this combo and everything is as safe as ever, even the Windows NT WKS we use which runs off SAMBA (one NT server here just to please NT WKS's profiles roaming/auto installation).
I wonder how long does it take for M$ to fix their OOB/Denial of service/etc attack and how long does it take for Linux.....
Enough said
NT only has Primary and Secondary domain controllers if configured to act in such a configuration. Ever heard of Kerberos? DCE? Maybe you should look them up, since NT is *switching* to use them in NT 5. Linux is the kernel. The surrounding applications are the distributions. Kerberos and DCE crush NT as far as security goes. Most distributions don't come with them, but both are freely available.
Only an NT user would think that a PC with modems hanging off it is an adequate way of running an ISP. Terminal servers are what most ISPs use, whether in the form of an older model with individual modems, or a 3com/USR Total Control unit that can support over *300* modems in a single chassis.
Basically, it lets you layer two filesystems so that modifications you make get stored on one, but you read old data off the other. One example would be layering a read-write filesystem on top of a CD so that you could `change' the CD, without having to copy the whole CD to a read-write medium. Another would be having different developers with their own private layers above a shared source code directory; a developer can compile, change and delete files, and he'll affect his private workspace but not the other developers (until the changes are moved to the shared layer).
cjs
The world's most portable OS: http://www.netbsd.org.
So chill out, I was more annoyed about the bit on the PC Speaker driver. (there is a patch for it, but it has some issues with low-level timing which is why no one wanted to include it into the main source tree. But it worked just fine in 2.0, and probably still works. So unless you want to clean it up, either use the patch, or don't complain, no one with a soundcard really needs it anyhow.)
Is there some reason that patch couldn't be reworked into a sound module now? Then people would only have to deal with those timing issues if they choose to load the module. At least it would offer a least-common-denominator option for sound and help people with unsupported soundcards...
Deven
"Simple things should be simple, and complex things should be possible." - Alan Kay
Has anyone gotten the Linux Loader to work on FAT32 drives?
Who are you kidding? According to the blurb about Stanford's matchbox-sized HTTP server, Linux can push a whooping 27 kBps across a PLIP line. I used PLIP for over half a year between my laptop and my home box, under FreeBSD 2.2 and 3.0, about a year ago. Sustained transfer rate averaged 80 kBps and peaked around 90 kBps.
Don't take my word for it - try it out for yourself: http://www.freebsd.org/
I don't suppose anyone's written up a howto for upgrading out-of-the-box (or, rather, off-of-the-Cheapbytes-disk) Red Hat 5.2 to use kernel 2.2.X? I've heard some word that not all of RH5.2's components were recent enough, and I'd like to know what I'd need to change out.
Thanks...
Robotech_Master
Editor Emeritus and Senior Writer, TeleRead.org
Having a walked a mile in one pair of Russ's shoes,
I feel comfortable in seconding his sentiments:
AC, where's your contribution? Put up or shut up.
I love reading this stuff. As soon as your boss
sees what a competent Linux administrator can do
with Linux, compared to what you can do with NT,
they will conclude that they are a lot better off
with Linux.
Looks, and sounds good to me! I like the new media supports, thankgod!
-Michael J. Lu
-Michael J. Lu
"The little secret that haunts Corporate America...a techonology that won't go away."
OK, I'm doing my homework before upgrading. No I haven't downloaded the src yet, but have read the docs at linuxhq. This is the first I've seen about the Virge. I'm stuck with one of those. Is this only a problem trying to run fbcon? Is it still possible just to run "the old way" with a "regular console" and the S3V X-server (I know SVGA server works too, but Redhat's install put in the S3V a little too automagically, but it seems to work fine)
And what's fbcon 1.0 vs. fbcon 2.0? Isn't fbcon just aprt of the kernel source, or is it like ftape where later versions are available outside the stock source? Nothing about this in http://www.linuxhq.com/doc21/fb/
Those things are over $100. I'll probably get broad-band access before the paint dries on a new modem.
-- Liquor up front, poker in the rear.
2.2.0 has so far worked great, except for now I get a "too many files open Caught a bug, email psy@x11amp.ml.org.
Works just fine. I haven't actually tried it
with 2.2.0 yet, but it worked with 2.0.36.
Don't see any reason why it wouldn't work
with the 2.2-series.
I have both Linux and Windows, so I prefer to
use Loadlin & DOS-bootmenu combo. Looks nicer.
Linux is the BEST OS ever. I wonder though if adding so many bells and whistles might ulitmately compromise its greatest strength: stability. My Linux 2.0 system has *never* crashed while my Win machines crash everyday. Let's hope not...
After upgrading to Linux 2.2 on a Debian-2.0 system, I have lost the ability to use smbmount. I tried recompiling it from the smbfs-2.0.2 distribution and the smbmount-1.3 distributions, no luck, still getting the "mount error: Invalid argument" each time where before I had no problems.
Anyone else experienced this / found out any way around it? I'm currently investigating Sharity, but I would prefer to use a GNUer solution.
Can i say winnuke.. yah thats secure but not stable.. oh yah and if there is a exploit for linux it gets fixed within hours instead of denying that it exists for months..
does this sound like a plausible idea for future development? i thought it would be an interesting idea for console backgrounds... (?) opinions?
yeah...i wasn't planning on it to be in the kernel. that would be bad. but seriously. how hard do you suppose it would be just do a simple vga background for the console? and...who could i contact about this?
I've read, and re-read the "document" and nowhere can I see ANY reference to a 4 modem limitation. Perhaps the "more than 4 serial ports" statement has confused you? Did you happen to read the end of that sentence, it mentions "multi-port cards"? Geez, I wonder what they're fo(u)r?