Opened 21 years ago
Closed 20 years ago
#522 closed defect (fixed)
readline in chapter 6?
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | lowest | Milestone: | |
| Component: | Book | Version: | CVS |
| Severity: | normal | Keywords: | |
| Cc: | iwanek@…, uli@… |
Description
See URL where thread started.
This is something worth exploring at a later date.
Change History (9)
comment:1 by , 21 years ago
| Cc: | added |
|---|
comment:2 by , 21 years ago
comment:3 by , 21 years ago
| Cc: | added |
|---|
comment:4 by , 21 years ago
Just checked again: My debugfs appears not to be linked to readline, so same problem here as with JamesI. Other than that, my system has been running flawlessly for almost 2 months now.
comment:5 by , 21 years ago
As discussed on the lists:
1) build standalone libreadline with "make SHLIB_LIBS=-lcurses" to link it against libncurses
2) debugfs from e2fsprogs will now dynamically use libreadline via the dlopen() interface i.e. it does NOT show up with ldd.
If this ever goes into the book, I would suggest location directly after ncurses. i.e. somewhere before inetutils and bash. The ftp client program from inetutils will build in support for libreadline if it finds it available at configure time. Bash can be configured with "--with-installed-readline".
comment:6 by , 20 years ago
| Priority: | low → lowest |
|---|
Down to P5 -- unclassified for now. Not sure yet if we want to add it to the book.
Is there a real benefit of having e2fsprogs use readline?
comment:7 by , 20 years ago
From Billy O'Connor:
The debugfs shell will get history and command line editing if you have it.
e2fsprogs dosnt seem to automatically detect readline here - could anyone else using latest cvs check to see if they have the same problem?