RE: Building lm_sensors-2.8.2 RPM - Help Needed
by Kwan Lowe
>
> First, I must admit that I am extremely inexperienced when it comes to
> the process of building RPMs. I consider myself quite adept with RedHat
> administration, so I didn't think it would be that hard to learn how to
> build RPMs. I was wrong. If anyone knows of a good place to get solid
> background information that will help with this learning process, please
> let me know.
>
> On to the problem at hand. I'm trying to build my own RPM of
> lm_sensors-2.8.2 so that I can begin to take advantage of the newly
> included asb100 support for my ASUS boards. I've tried to use the SPEC
> file that is included with the lm_sensors source. Despite my attempt to
> modify everything for a current RedHat 9 machine, it did not work. I
> then tried to start from the SPEC file that was included with
> lm_sensors-2.8.1-1.src.rpm. This crashes when attempting to apply the
> RedHat patch. I've tried countless variations and nothing seems to
> work.
>
I have a short guide at http://www.digitalhermit.com/linux/rpm
Check out the links section for more in depth guides to building. If you
want, email me the spec privately and I'll take a look see.
--
* The Digital Hermit http://www.digitalhermit.com
* Unix and Linux Solutions kwan(a)digitalhermit.com
20 years, 4 months
Re: Flash Disk (Margo)
by Jason Riker
Margo,
I had this same problem with a SD card in a Sharp Zaurus PDA. The only
way I was able to resolve it was to put the card back into a Windows
machine and let Windows format it.
Hope this helps.
Good Luck,
Jason
> When I plug it in now, it's picked up as a flash disk (good) however
> the filesystem comes up as unknown or not recognised.
>
> I have searched everywhere to find out the command to reformat the disk
> as vfat in linux... perhaps its too basic a command to be in any faq.
> Can anyone help.
>
> Margo
20 years, 4 months
Building lm_sensors-2.8.2 RPM - Help Needed
by Brian Hanks
First, I must admit that I am extremely inexperienced when it comes to
the process of building RPMs. I consider myself quite adept with RedHat
administration, so I didn't think it would be that hard to learn how to
build RPMs. I was wrong. If anyone knows of a good place to get solid
background information that will help with this learning process, please
let me know.
On to the problem at hand. I'm trying to build my own RPM of
lm_sensors-2.8.2 so that I can begin to take advantage of the newly
included asb100 support for my ASUS boards. I've tried to use the SPEC
file that is included with the lm_sensors source. Despite my attempt to
modify everything for a current RedHat 9 machine, it did not work. I
then tried to start from the SPEC file that was included with
lm_sensors-2.8.1-1.src.rpm. This crashes when attempting to apply the
RedHat patch. I've tried countless variations and nothing seems to
work.
I'll gladly forward the spec file to anyone that might desire to review
it.
Thanks for your help,
Brian
bhanks(a)bhanks.com
20 years, 4 months
2.4.22-1.2115.nptl and VIA SATA driver
by Simon@theThreshold
Lo there,
I've recently updated to the 2.4.22-1.2115.nptl kernel for fedora core 1
,I've a Abit KV7 motherboard. Athlon (Duron) processor.
Basicly I've been waiting for a bia of VIA SATA (Southbridge 8237)
support and thought I might be there.
When the kernel boots it detects the controler and gives the following
output:-
libata version 0.81 loaded.
sata_via version 0.11
ata1: SATA max UDMA/133 cmd 0x9000 ctl 0x9402 bmdma 0xA000 irq 11
ata2: SATA max UDMA/133 cmd 0x9800 ctl 0x9C02 bmdma 0xA008 irq 11
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003
88:407f
ata1: dev 0 ATA, max UDMA/133, 160086528 sectors
ata1: dev 0 configured for UDMA/133
ATA: abnormal status 0x7F on port 0x9807
ata2: thread exiting
scsi1 : sata_via
scsi2 : sata_via
Vendor: ATA Model: Maxtor 6Y080M0 Rev: 0.81
Type: Direct-Access ANSI SCSI revision: 05
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB)
sda: sda1
ata1: thread exiting
scsi : 1 host left.
libata version 0.81 loaded.
sata_via version 0.11
ata1: SATA max UDMA/133 cmd 0x9000 ctl 0x9402 bmdma 0xA000 irq 11
ata2: SATA max UDMA/133 cmd 0x9800 ctl 0x9C02 bmdma 0xA008 irq 11
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003
88:407f
ata1: dev 0 ATA, max UDMA/133, 160086528 sectors
ata1: dev 0 configured for UDMA/133
ATA: abnormal status 0x7F on port 0x9807
ata2: thread exiting
scsi1 : sata_via
scsi2 : sata_via
Vendor: ATA Model: Maxtor 6Y080M0 Rev: 0.81
Type: Direct-Access ANSI SCSI revision: 05
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB)
sda: sda1
ata1: thread exiting
scsi : 1 host left.
However even though Its clearly identifed the serial ata bus and the
Maxtor disk I can't access the assigned scsi device.
As root I get unable to open any of the disk utilities (fdisk/parted etc.).
Anyone have any ideas?
Regards
Simon
20 years, 4 months
where do I go to configure openssh
by Ben Davis
technical <technical(a)sojourn.dyndns.org> schreef om 1 Jan 2004 02:56:12
-0500 (EST)
> Solution :
> If you use OpenSSH, set the option 'Protocol' to '2'
> If you use SSH.com's set the option 'Ssh1Compatibility' to 'no'
edit /etc/ssh/sshd_config (as root), uncomment
#Protocol 2,1
to read
Protocol 2
exec: service sshd restart... et voila. HTH.
--
Jamin - @Manchester UK | @Maastricht NL | @Tallinn EE
t: 0044-161-285-1338
20 years, 4 months
RE: bitmappes mouse cursor
by Kwan Lowe
> Message: 23
> Date: Thu, 1 Jan 2004 10:54:38 +0100
> From: Joolz <joolz(a)xs4all.nl>
> To: fedora-list(a)redhat.com
> Subject: bitmappes mouse cursor
> Reply-To: fedora-list(a)redhat.com
>
> Happy new year!
>
> Can anybody tell me how I can use the old-style bitmapped mousecursors
> (not the default alpha ones) on FC1? Thanks!
>
You can try one of the following:
Add CursorShadow "False"
to the Screen section of your XF86Config, or try:
export XCURSOR_CORE
in your .bash_profile.
I think some of these are hardware dependent.
--
* The Digital Hermit http://www.digitalhermit.com
* Unix and Linux Solutions kwan(a)digitalhermit.com
20 years, 4 months
Re: fedora-list digest, Vol 1 #661 - 26 msgs
by Paul Dubinsky
At 05:32 AM 1/1/2004, you wrote:
>Message: 26
>Subject: Re: CUPS Problem
>From: Jaakko Ruutiainen <jaakko.ruutiainen(a)keypro.fi>
>To: fedora-list(a)redhat.com
>Date: Thu, 01 Jan 2004 12:32:00 +0200
>Reply-To: fedora-list(a)redhat.com
>
>On Thu, 2004-01-01 at 00:07, Paul Dubinsky wrote:
>
> > I'm trying to setup a JetDirect queue on FC1 and I keep getting an error
> > when the CUPS system tries to create the queue. Everything goes fine until
> > I try to print a test page. Then I get the following error msg:
> >
> > Cannot write queues
> >
> > sh: line 1: /usr/bin/lpr - no such file or directory
> >
> >
> > /usr/bin/lpr links to /etc/alternatives/print which links to
> > /usr/bin/lpr.LPRng which doesn't exist.
> >
> > This FC1 was installed as an upgrade of an existing installation of RHL7.3.
> >
>Hi,
>
>I had same problems just few days ago. To fix it I just relinked
>printing related stuff (all links to something ending with .LPRng) from
>/etc/alternatives/ to point into /usr/(s)bin/*.cups instead of
>/usr/(s)bin/*.LPRng For example 'ln -sf /usr/bin/lpr.cups
>/etc/alternatives/print'
>
>--
>Jaakko Ruutiainen
>- jaakko.ruutiainen(a)keypro.fi
Thanks for the info. It worked perfectly.
Happy New Year and my wishes for all the best in 2004.
Paul Dubinsky
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.555 / Virus Database: 347 - Release Date: 12/23/2003
20 years, 4 months
RE: where do I go to configure openssh
by Kwan Lowe
>
> Message: 20
> From: technical <technical(a)sojourn.dyndns.org>
> Date: Thu, 1 Jan 2004 02:56:12 -0500 (EST)
> Subject: where do I go to configure openssh
> To: fedora-list(a)redhat.com
> Reply-To: fedora-list(a)redhat.com
>
> I want to resolve this issue
>
> Warning found on port ssh (22/tcp)
>
>
> The remote SSH daemon supports connections made
> using the version 1.33 and/or 1.5 of the SSH protocol.
>
> These protocols are not completely cryptographically
> safe so they should not be used.
>
> Solution :
> If you use OpenSSH, set the option 'Protocol' to '2'
> If you use SSH.com's set the option 'Ssh1Compatibility' to 'no'
>
Look in the /etc/ssh/sshd_config file. It will read something like:
Protocol 2,1
Change this line to read:
Protocol 2
For more information on the options, do "man sshd_config"
--
* The Digital Hermit http://www.digitalhermit.com
* Unix and Linux Solutions kwan(a)digitalhermit.com
20 years, 4 months
kernel 2.6
by David Rigler
when would we expect to see the 2.6.?? kernel in fedora ??
Dave
20 years, 4 months
where do I go to configure openssh
by Technical
I want to resolve this issue
Warning found on port ssh (22/tcp)
The remote SSH daemon supports connections made
using the version 1.33 and/or 1.5 of the SSH protocol.
These protocols are not completely cryptographically
safe so they should not be used.
Solution :
If you use OpenSSH, set the option 'Protocol' to '2'
If you use SSH.com's set the option 'Ssh1Compatibility' to 'no'
Risk factor : Low
Nessus ID : 10882
20 years, 4 months