At 07:45 PM 4/7/2005 +, Jeremy Abbott wrote:
[...]
I bought Suse about a year ago. Very nice Distro with package
management through Yast. My problem with it though, was that it does
not come with a C compiler. If all youare installing is binary
packeges, that's fine. I wanted to do some com
one workaround u can try is to open a terminal, become
root
and issue following command:
$> /etc/init.d/gpm restart
The problem is due to the incompatibility of KVM with
linux.
regds,
-rpm
On Thu, 07 Apr 2005 13:37:15 -0700
Ray Olszewski <[EMAIL PROTECTED]> wrote:
At 11:10 PM 4/7/2005 +0300, [
Peter wrote:
>Hi,
>
>having read all the replies I would almost be scared to go to a Linux OS. It
>is not that difficult at all. With Fedora I would call the installation a
>child's or grandma's play, however, would recommend to do the partitioning
>yourself after having read how to go about it
Mounting thumb drive.
On my two Slackware 9.1 (kernel 2.4.22) systems
each mounted my thumbdrive (Sandisk microcruzer 128 MB) with
mount /dev/sda1 /mnt/hd
df -T indicated that it was a 'umsdos' filesystem.
Slackware v10.0 & 10.1's kernel (2.4.26 & 2.4.29) found a
/dev/sda1 device and I could
mount
Hi,
having read all the replies I would almost be scared to go to a Linux OS. It
is not that difficult at all. With Fedora I would call the installation a
child's or grandma's play, however, would recommend to do the partitioning
yourself after having read how to go about it.
As for me slackwa
[EMAIL PROTECTED] wrote:
On Thu, 7 Apr 2005, smertz wrote:
mount /dev/sdc1 /mnt/thumb
Trying this gives me the error
mount: special device /dev/sdsc1 does not exist
^^^
Same error message below
[EMAIL PROTECTED] ~]# mount /dev/sdc /mnt/thumb
mount: special device
On Thu, 7 Apr 2005, smertz wrote:
mount /dev/sdc1 /mnt/thumb
Trying this gives me the error
mount: special device /dev/sdsc1 does not exist
^^^
should be sdc1
Also you could try with
mount /dev/sdc /mnt/thumb
maybe you don't have sdc1 or sdc in your /dev/ director
mount /dev/sdc1 /mnt/thumb
Trying this gives me the error
mount: special device /dev/sdsc1 does not exist
dmesg lines again
usb 1-1: new high speed USB device using address 4
scsi3 : SCSI emulation for USB Mass Storage devices
Vendor: Generic Model: STORAGE DEVICERev: 1.22
Type: Direc
smertz wrote:
Ray Olszewski wrote:
At 02:35 PM 4/7/2005 -0600, smertz wrote:
I have a new computer I installed Linux on Red Hat Enterprise Linux
ES release 4 (Nahant), it has one of those all-in-one card readers on
it. I have made mountpoints as root as follows for my thumb, Compact
flash and se
smertz wrote:
Ray Olszewski wrote:
[snip]
This is the last few lines from dmesg. Based on this how would one
mount if I have made the mountpoint of /mnt/thumb
SCSI device sdc: 256000 512-byte hdwr sectors (131 MB)
sdc: Write Protect is off
sdc: Mode Sense: 02 00 00 00
sdc: assuming drive cache:
Ray Olszewski wrote:
At 02:35 PM 4/7/2005 -0600, smertz wrote:
I have a new computer I installed Linux on Red Hat Enterprise Linux ES
release 4 (Nahant), it has one of those all-in-one card readers on it.
I have made mountpoints as root as follows for my thumb, Compact flash
and secure digital d
smertz wrote:
I have a new computer I installed Linux on Red Hat Enterprise Linux ES
release 4 (Nahant), it has one of those all-in-one card readers on it. I
have made mountpoints as root as follows for my thumb, Compact flash and
secure digital drive.
mkdir /mnt/thumb
mkdir /mnt/cf
mkdir /mnt/
At 02:35 PM 4/7/2005 -0600, smertz wrote:
I have a new computer I installed Linux on Red Hat Enterprise Linux ES
release 4 (Nahant), it has one of those all-in-one card readers on it. I
have made mountpoints as root as follows for my thumb, Compact flash and
secure digital drive.
mkdir /mnt/thu
On Thu, 7 Apr 2005, smertz wrote:
I have a new computer I installed Linux on Red Hat Enterprise Linux ES
release 4 (Nahant), it has one of those all-in-one card readers on it. I have
made mountpoints as root as follows for my thumb, Compact flash and secure
digital drive.
mkdir /mnt/thumb
mkdir
At 02:11 PM 4/7/2005 -0500, James Miller wrote:
I'll start the testing responses to this, your most recent, posting, and
move to your previous posting after this one. I wanted to ask about udev
before running the tests in your previous post on the assumption that its
presence might change someth
I have a new computer I installed Linux on Red Hat Enterprise Linux ES
release 4 (Nahant), it has one of those all-in-one card readers on it. I
have made mountpoints as root as follows for my thumb, Compact flash and
secure digital drive.
mkdir /mnt/thumb
mkdir /mnt/cf
mkdir /mnt/sd
Now when I
At 11:10 PM 4/7/2005 +0300, [EMAIL PROTECTED] wrote:
On Thu, 7 Apr 2005, Eve Atley wrote:
Simply put...my mouse has started having a mind of its own in our Redhat
Enterprise Workstation 3 (Taroon) Linux box. It wants to focus on the bottom
left-hand corner of the screen, and clicks on whatever happ
>see /etc/X11/xorg.conf or /etc/X11/XF86Config
Thanks; I tried reverting back to my XF86Config.backup but that didn't work.
The old and new ones appear to be the same.
And if it helps, it's actually a Logitech PS2 trackball attached to a KVM
switch.
My entries in each show:
XF86Config.backup
On Thu, 7 Apr 2005, Eve Atley wrote:
Simply put...my mouse has started having a mind of its own in our Redhat
Enterprise Workstation 3 (Taroon) Linux box. It wants to focus on the bottom
left-hand corner of the screen, and clicks on whatever happens to be there
at the time (Languages at login, as a
Additionally, the VNC Redhat desktop has no such problems with the mouse.
Thanks,
Eve
-Original Message-
From: Eve Atley [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 07, 2005 3:58 PM
To: 'linux-newbie@vger.kernel.org'
Subject: Mouse going nuts in RH Linux Enterprise 3 (Taroon)
S
Simply put...my mouse has started having a mind of its own in our Redhat
Enterprise Workstation 3 (Taroon) Linux box. It wants to focus on the bottom
left-hand corner of the screen, and clicks on whatever happens to be there
at the time (Languages at login, as an example). When I try to move the
c
On Thu, 7 Apr 2005, James Miller wrote:
module line in /etc/modules. I do have the option of swapping Soundman (3)
and Soundblaster (5) IRQ's, I suppose, to see if that makes any difference.
Haven't tried that yet.
Just tried it (made Soundman IRQ 5 and Soundblaster 3 and edited
/etc/modules acc
On Thu, 7 Apr 2005 [EMAIL PROTECTED] wrote:
On Wed, 6 Apr 2005, James Miller wrote:
if that relieves any potential IRQ 3 conflict. Possible IRQ's for the card
are: 2, 3, 5, 7, 10, 11, 12, 15 for "Soundman" and 2, 3, 5, and 7 for
"Sound blaster."
i think you can use interrupt 5 or 9 if there's a w
On Wed, 6 Apr 2005, James Miller wrote:
On Thu, 7 Apr 2005 [EMAIL PROTECTED] wrote:
Can you post your /proc/interrupts here ?
[EMAIL PROTECTED]:~$ cat /proc/interrupts
CPU0
0: 25759543 XT-PIC timer
1: 23960 XT-PIC i8042
2: 0 XT-PIC cascade
I'll start the testing responses to this, your most recent, posting, and
move to your previous posting after this one. I wanted to ask about udev
before running the tests in your previous post on the assumption that its
presence might change something fundamental in testing procedures. The
test
At 12:31 PM 4/7/2005 -0500, James Miller wrote:
[...]
Anyway, I'll try what you've suggested. But one aspect needs some further
comment and clarification, namely:
2. Create the device entries if they are not present. (I was a bit
surprised that they are not present, but if they are not, you are
On Thu, 7 Apr 2005, Ray Olszewski wrote:
bit more systematic than what you've been doing. (I'm seeing some gaps in
your testing, and I can't tell if you really are skipping steps or just being
terse in your reports to us.)
I'd call what I'm doing semi-controlled, semi-informed flailing. I know
s
At 02:50 PM 4/7/2005 +0800, Yawar Amin wrote:
[...]
Here's what I think: Debian is excellent, but ... outdated. And
if you want to be cautious and not try to do full upgrades from the
'net for fear of breaking something, then you're stuck with older
stuff. (Sorry, Ray! I had to get that out. I mys
On Thu, 7 Apr 2005, smertz wrote:
Is there a command to see how the LV partitioning was done by the installer?
If so what is it?
I think the mount command might get what you want. If not, maybe dh. I've
used a system set up with LVM a little, but not enough to remember
precisely.
James
-
To uns
At 09:09 AM 4/7/2005 -0500, James Miller wrote:
On Wed, 6 Apr 2005, James Miller wrote:
range) or to disable ttyS1 (COM 2 as the BIOS sees it, I believe) and see
if that relieves any potential IRQ 3 conflict.
I tried disabling COM 2 in the BIOS (set it to "off" there). When I look
at dmesg output
Mike Turcotte wrote:
Many new Serial ATA controllers have their modules listed as SCSI
devices, I am not sure why, I think it has to do with their standards or
something. This is normal. Also, what the auto partitioning did was
create a 100 Mbyte partition for use as /boot, and the rest of the driv
Many new Serial ATA controllers have their modules listed as SCSI
devices, I am not sure why, I think it has to do with their standards or
something. This is normal. Also, what the auto partitioning did was
create a 100 Mbyte partition for use as /boot, and the rest of the drive
allocated as LVM (L
I noticed after installing Red Hat Enterprise Linux ES release 4
(Nahant) last week when I do a fdisk -l that the automatic partitioning
might not have done such a good job of partitioning out my 200 GIG HD.
[EMAIL PROTECTED] ~]# fdisk -l
Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63
On Wed, 6 Apr 2005, James Miller wrote:
range) or to disable ttyS1 (COM 2 as the BIOS sees it, I believe) and see if
that relieves any potential IRQ 3 conflict.
I tried disabling COM 2 in the BIOS (set it to "off" there). When I look
at dmesg output, it does, indeed, appear to be off and is not g
I recently tried using DAR on my Gentoo machine. This program works
great as it has a $#!7 load of options including compression. One of the
greatest features of this program is that it can split up its output
file into user definable sized chunks so you can easily put it onto your
choice of media.
James Miller <[EMAIL PROTECTED]> wrote:
> A couple of ways to adress this: 1) find a distro with a good support
> community (e.g., Ubuntu is a newbie-oriented distro with a really
> active forum) and ask about your hardware there ahead of time. This
> presumes you know what kind of hardware is in
36 matches
Mail list logo
