uranus ~ # minicom -s minicom: there is no global configuration file /etc/minicom/minirc.dfl Ask your sysadmin to create one (with minicom -s). uranus ~ # minicom -s /etc/minicom/minirc.dfl minicom: there is no global configuration file /etc/minicom/minirc._etc_minicom_minirc.dfl Ask your sysadmin to create one (with minicom -s). uranus ~ # [ebuild R ] net-dialup/minicom-2.4 USE="nls" LINGUAS="fr -cs -da -de -es -fi -hu -id -ja -nb -pl -pt_BR -ro -ru -rw -sv -vi -zh_TW" 0 kB
Created attachment 237895 [details] /tmp/emerge--info
"Ask your sysadmin to create one (with minicom -s)." Man page says: COMMAND-LINE -s Setup. Root edits the system-wide defaults in /etc/minirc.dfl with this option. When it is used, minicom does not initialize, but puts you directly into the configuration menu. This is very handy if minicom refuses to start up because your system has changed, or for the first time you run minicom. For most systems, reasonable defaults are already compiled in. So just run `minicom -s' as root...
i was root ! dhp@uranus ~ $ su Password: uranus ~ # minicom -s minicom: there is no global configuration file /etc/minicom/minirc.dfl Ask your sysadmin to create one (with minicom -s). uranus ~ # id uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video) uranus ~ #
Oh. What does `stat /etc/minicom/minirc.dfl' say?
uranus ~ # stat /etc/minicom/minirc.dfl stat: cannot stat `/etc/minicom/minirc.dfl': No such file or directory uranus ~ # ls -lha /etc/minicom* total 16K drwxr-xr-x 2 root root 4.0K May 29 00:11 . drwxr-xr-x 111 root lp 12K Jul 7 18:25 .. uranus ~ # ls -lha /etc/conf.d/min* ls: cannot access /etc/conf.d/min*: No such file or directory uranus ~ # should answer all future questions ... IMHO, the guy prints out the error message BEFORE interpreting the options ...
(In reply to comment #5) > uranus ~ # stat /etc/minicom/minirc.dfl > stat: cannot stat `/etc/minicom/minirc.dfl': No such file or directory > uranus ~ # ls -lha /etc/minicom* > total 16K > drwxr-xr-x 2 root root 4.0K May 29 00:11 . > drwxr-xr-x 111 root lp 12K Jul 7 18:25 .. > uranus ~ # ls -lha /etc/conf.d/min* > ls: cannot access /etc/conf.d/min*: No such file or directory > uranus ~ # > > > should answer all future questions ... > > IMHO, the guy prints out the error message BEFORE interpreting the options ... > I solved this by copying the file from /usr/portage/net-dialup/minicom/files/minirc.dfl to /etc/minicom. Maybe the ebuild should do this as well?
If this works, it could be a good idea. Still, copying /usr/portage/net-dialup/minicom/files/minirc.dfl is neither a fix or a WA for the present bug: when that file is not present, it says to use -s to create it ... but ignores "-s" option ... => I stick to my previous comment: <<IMHO, the guy prints out the error message BEFORE interpreting the options ...>> Adding the copy to ebuild would NOT fix this bug.
I'm having this same issue on Mac OS 10.6.4 I try "sudo minicom -s" and I get this error: minicom: there is no global configuration file /opt/local/etc/minirc.dfl Ask your sysadmin to create one (with minicom -s).
Oddly enough, there is no bug in minicom's tracker, but Debian does patch this out in debian/patches/bug204522.diff: --- minicom.orig/src/config.c 2009-06-06 23:19:36.000000000 +0200 +++ minicomsrc/config.c 2009-11-21 12:37:17.151703178 +0100 @@ -51,14 +51,10 @@ char *p; /* Read global parameters */ - if ((fp = fopen(parfile, "r")) == NULL) { - fprintf(stderr, - _("minicom: there is no global configuration file %s\n"), parfile); - fputs(_("Ask your sysadmin to create one (with minicom -s).\n"), stderr); - exit(1); - } + if ((fp = fopen(parfile, "r")) != NULL) { readpars(fp, CONFIG_GLOBAL); fclose(fp); + } /* Read personal parameters */ if ((fp = fopen(pparfile, "r")) != NULL) { readpars(fp, CONFIG_PERSONAL);
Can not reproduce this with 2.6, it seems fixed a long time ago Closing this as OBSOLETE
