Bug 218494

Summary:	Upgrading from RHEL4 to RHEL5 blew away my minicom configurations.
Product:	Red Hat Enterprise Linux 5	Reporter:	Jay Fenlason <fenlason>
Component:	minicom	Assignee:	Miroslav Lichvar <mlichvar>
Status:	CLOSED NOTABUG	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.0	CC:	jfeeney
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-01-29 16:56:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jay Fenlason 2006-12-05 18:52:50 UTC

Description of problem: 
I had configured my RHEL4 box so I could use "minicom -w ttyS1" to access the 
serial console of my rawhide box.  After I upgraded from RHEL4 to RHEL5, 
minicom no longer had a ttyS1 configuration. 
 
Version-Release number of selected component (if applicable): 
minicom-2.1-3 
 
How reproducible: 
Haven't tried. 
 
Steps to Reproduce: 
1.Configure minicom on rhel4 
2.Upgrade to rhel5b2 
3.attempt to use minicom. 
   
Actual results: 
[root@fenlason-lab2 ~]# minicom -w 
minicom: WARNING: configuration file not found, using defaults 
Device /dev/modem access failed: No such file or directory. 
[root@fenlason-lab2 ~]# minicom -w ttyS1 
minicom: WARNING: configuration file not found, using defaults 
Device /dev/modem access failed: No such file or directory. 
 
Expected results: 
minicom should've kept its configuration. 
 
Additional info:

Comment 1 Miroslav Lichvar 2006-12-06 12:48:00 UTC

Hm, can't reproduce. /etc/minirc.* files aren't owned by minicom package, so
update of the package couldn't remove the files.

Can you reproduce it just with minicom update?

Comment 2 Miroslav Lichvar 2007-01-29 16:56:19 UTC

This really looks like NOTABUG as the config files aren't even managed by rpm,
something else probably removed the files. Please reopen when you can reproduce.