Pages

Search

[Help] Problem with soundcard - Forums Linux

[Help] Problem with soundcard - Forums Linux

[Help] Problem with soundcard

Posted: 22 Dec 2005 08:07 AM PST

Scilli wrote: 

Why do people insist on installing RHL 6.2 that came out about 1991 and was
totally discontinued about three years ago? The last RHL (9) was
discontinued a year or two ago.

If you want to use an enterprise server distribution, you should consider
Red Hat Enterprise Linux 4 (CentOS 4.2 is a clone of this) or SuSE (I do not
know what version they are up to). Enterprise distributions tend to be for
servers and are not the latest and greatest, but tend to be the most stable.
I use RHEL3 on my main machine that is a desktop workstation, and CentOS 4.2
on my other machine. Updates are only for bug or security fixes. Nothing new
gets added.

If you want the latest and greatest, and like Red Hat, go with the Fedora
Core releases; I think they are up to Core 4 at the moment, but I have not
been keeping track.

Now, the recent RHEL releases do not seem to run my old (CT4170)
Soundblaster ISA card. After spending several whole days trying to get it to
work, I gave up and put in a newer PCI Soundblaster in there and it worked
fine. It may be that the 2.6 kernels do not come with support for those old
boards, though I am surprised that they ever delete drivers for stuff.

IIRC, Fedora Core 2 did not run my ISA CT4170 either, although all the RHL
from 6.0 up to 9 did support it and Windows XP Home supports it. But now it
is sitting in my spare parts bin, along with the ISA dial-up real modem.

--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 11:55:00 up 25 days, 22:26, 5 users, load average: 4.24, 4.19, 4.12

What to install first linux10 or win2000

Posted: 21 Dec 2005 06:00 PM PST

In <dod1bi$stn$Stanford.EDU>, on 12/21/2005
at 06:00 PM, com said:
 

I would install windoze first; some release of m$ malware sabotage
existing operating systems. Partition the disk with a primary
partition for C, a primary[1] partition for /boot and an extended
logical partition containing a D drive, / (root), /home and any other
Linux file systems that you want to keep separate from root.
 

You can read that from Linux. If you need to transfer files from Linux
to NT, create a small logical drive formatted as FAT.

[1] Not necessary if you use the grub MBR, but it gives you more
flexibility.

--
Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel>

Unsolicited bulk E-mail subject to legal action. I reserve the
right to publicly post or ridicule any abusive E-mail. Reply to
domain Patriot dot net user shmuel+news to contact me. Do not
reply to lspace.org

Problem setting up NFS on Ubuntu

Posted: 20 Dec 2005 08:46 AM PST

In message <home.lan>
"Enrique Perez-Terron" <no> wrote:
 

<huge snip>
 

Thanks Enrique. This and your later post will be most useful, and are
flagged for further attention, when I return from a short break.

A little background might be of interest. I've been using computers in one
way or another since the early 1970's. Much of that time (around 20 years of
it) was spent running VMS for a large production site. VMS, as you probably
know, was entirely command-line driven for almost all of that period. So
it's not having to use a command line which bothers me. It does help that
VMS commands are, in the main, English words which reflect the action they
perform. e.g. search instead of grep. This makes it easier to use HELP to
find out what you need.

The other major difference from a sysadmin point of view, is that VMS has
around 40 privileges, each broadly related to a job function. For example if
you want to administer printers or tape drives, you need OPER. That way,
your operators can do protected operations without needing the full root
access. As an administrator, I had SETPRV, which allowed me to claim the
privilege I needed to do a specific operation. I rarely ran as SYSTEM (the
equivalent of the root account). I did once get badly bitten by running a
system upgrade while NOT logged in as SYSTEM however - the process quotas
were wrong for the operation. (The non-paged memory quota I think - another
difference from Unix).

It is however long enough ago that I'm no longer fluent in EDT, so rather
than trying to find the EDT clone for Linux, I need to decide on an editor,
and learn it. (Just one though - I find learning editors stressful for some
reason, so stick with one per operating system as far as possible.)

I've been reading this group for about a month now. I am not surprised by
the types of responses I got from various people (except that Peter's wasn't
as harsh as I expected).

There will be more questions...

--
Alan Adams, from Northamptonshire
freeserve.co.uk
http://www.nckc.org.uk/

LDAP over Putty

Posted: 19 Dec 2005 04:07 PM PST

On Tue, 20 Dec 2005 06:12:42 +0100, com <com> wrote:
 

But isn't the ssh connection going to the server that is serving the LDAP
data?

In that case, you must tell putty to forward the port to the ldap server.
Putty will tell the ssh server on the linux side to connect to the server
you say to putty.

I haven't used putty for a few years now, but the openssh client has the
option format -L [bind_address:]port:host:hostport, where host:hostport
should be the ldap server and its port. bind_address is an address on the
ssh client. A typical client can have the loopback interface, a nic for
the local network, and a ppp interface to the outside world, and most
people want the port on the client side to be available only on the
loopback interface, i.e., only to the client computer itself.

-Enrique

(re-)activation boot manager

Posted: 19 Dec 2005 09:46 AM PST

Thank you John! Sven

Just downloaded Fedora iso 386 files.

Posted: 18 Dec 2005 04:38 PM PST

On Tue, 20 Dec 2005 02:16:20 +0100, Nico Kadel-Garcia <net> wrote:
 

I just looked at xcdroast. I cannot see any obvious way of burning an
existing .iso image. How come that no single cd tool has that option
reasonably accessible? Is k3b better in this respect? Oh, I just
installed k3b, and that was much better!!

But I am not sure it detected the write speed correctly. Actually,
I have no idea how fast it can write, it is Sony CD-RW CRX140E, and
it's labeled "8x/4x/32x", and I always assumed the last number would
be the max reading speed. K3b asked me to check if its guess of 32x
is right, but I don't know how to find out, other than googling or
just trying.

Googling seems to indicate the numbers are write, rewrite, and read.
OK. I vote for k3b since it actually lets you burn an iso.

-Enrique

dual boot with xp on same drive

Posted: 18 Dec 2005 10:49 AM PST

On Tue, 20 Dec 2005 18:24:59 +0000, popkjo wrote:
 
Caveat: I am not running XP. I am not running Fedora.

Fedora has a complete set of help documentation which you should review to
understand what the steps and final goal of the installation.
This is the link for FC4:
http://fedora.redhat.com/docs/fedora-install-guide-en/fc4/

Study the documentation for the version of Fedora you will be
installing.

In general, you would proceed as follows:
1. Backup your Windows partitions.
2. Decide if you need to resize parititions. If all of the disc is
allocated to Windows partitions, then you will either need to resize,
recreate, remove, or avoid touching Windows.

Option A: Resize windows partitions. "Partition Magic" is probably the
leader in Windows tools for resizing partitions. It works by
consolidating free space and moving data as necessary to fit on a smaller
partition. It has worked for me, but it is not free (about $50 when
bundled with Ghost.) When resizing, plan how much space you want to
allocate for each OS. You say you have 15G free; therefore, you
might assign 14G for the Fedora install. That will give you some working
room on your new OS, and very little for changes on XP.

Option B: Recreate windows from a backup. This might be fastest if you are
competent and have a good backup/restore procedure. There are a lot of
"gothas" with this route, so only choose this option if you really know
what you're doing. First, take a snapshot backup of your drive. The
method I use is ntfsclone, a linux utility. Unfortunately, you can't
run linux utilities until you're running linux (catch 22).

Another tool is drivesnapshot, http://www.drivesnapshot.de/en/index.htm

Option C: Remove windows (Best of all!). Go for it. Then, if you
should need to refer to any of the old data, you can "mount" your
backup under linux. This is possible with ntfsclone image files.

Option D: Avoid touching windows (leaves fingerprints ;-)). Buy a
separate disc drive dedicated entirely to linux and do not touch your
Windows install.

BTW, I have heard some recent versions of SuSE linux can do the partition
resizing for you as part of the installation process. This may or may not
be true for the version of FC you are installing. Caution: refer to "Step
1." above.

When you have free space on your disc, then you can add partitions.
Depending upon what your plan is with Windows, you should consider
reserving partition 1 for Windows, that is, if you are keeping it.

Here is one option for you paritioning scheme:
Partition Size For
1 x? XP
2 y? XP Data
3 13.2G FC (linux root)
4 0.8G FC (linux swap)

With that plan in mind, begin the Fedora install. Keep in mind the basic
rules for disc partitioning (in the PC world):
1. There can be a maximum of 4 primary partitions.
2. Windows likes to be on partition 1
3. A primary partition can be assigned to be an "extended partition."
4. An extended partiton can contain more partition entries (not limited
to 4). Partitions within the extended partition are referred to as
"logical partitions."

--
Douglas Mayne

Printing problem (DELL OptiPlex GX260)

Posted: 17 Dec 2005 02:40 PM PST


<com> wrote in message
news:googlegroups.com... 

My experience with Suse and real systems administration is that it bites
goat rocks. The Autoyast tools obscure, moddy, and in fact violate the
software that they are supposed to manage, including the printing tools, the
X manager, the software update system, and the kernel management.

If you possibly can, install a recent RedHat release such as Fedora Core 4
or RH Enterprise 4.2, and use the system-config-printer tool to actually
correctly set it up. Then take a look at what the setup did to /etc/cups,
/etc/printcap, etc. and if you're still stuck with SuSE emulate the setup
there.
 

Why do you expect this to work? If the printer is a local device,
 

See above. Debian stable (where you probably have your 2.4 kernel) is also
not reasonably expected to have the latest device drivers and software
compatibility.
 

I still think SuSE 9.3 is asking for trouble in any print server setups. But
are the laptop and the server both running the same kernel, the same CUPS
version, the same configurations? I thoroughly doubt it: transferring
printer configurations from SuSE system to SuSE system is compounded in
complexity by the autoyast configuration wrappers, so even if you set things
identically in the configuration tools to all appearances you can still have
unknown differences under the hood. Autoyast is *BAD* about reporting the
details of its software configurations, and even worse about re-writing them
unannounced.