Re: ldso 1.8.11 makes system unusable
On Wed, 30 Jul 1997, joost witteveen wrote: So, you were doing something unnatural. I know I'm mad by using Linux. But I'm not so mad to upgrade an production system only because there is a new release of Debian. I guess you've already reboted your computer now. No, fortunatly not. I managed to use minicom to dial out and fetch the previous version of ld.so, used dpkg-deb -x to extract the files under /tmp and copied them by hand in the right locations. Apart from the fact that some colleagues get nervous about their email (an operating system which doesn't require a P200 to can is suspicious anyways!) no real harm happend. Thanks for your help -Winfried -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
ldso 1.8.11 makes system unusable
I tried to upgrade some packages on a 1.1.* installation. Made the system nearly and so I have two questions: is it a known problem (- bug report) and how do I fix it? -Winfried [EMAIL PROTECTED]:/home/winni dpkg -i ldso_1.8.11-1_i386.deb (Reading database ... 19925 files and directories currently installed.) Preparing to replace ldso 1.8.11-1 (using ldso_1.8.11-1_i386.deb) ... sh: can't resolve symbol 'rl_ignore_some_completions_function' dpkg: warning - old pre-removal script killed by signal (Segmentation fault) dpkg - trying script from the new package instead ... sh: can't resolve symbol 'rl_ignore_some_completions_function' dpkg: error processing ldso_1.8.11-1_i386.deb (--install): subprocess new pre-removal script killed by signal (Segmentation fault) sh: can't resolve symbol 'rl_ignore_some_completions_function' dpkg: error while cleaning up: subprocess post-installation script killed by signal (Segmentation fault) Errors were encountered while processing: ldso_1.8.11-1_i386.deb -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
[LOCAL] Any Debian-People at the GUUG-meeting in february?
The German Association of Unix Users (GUUG) will hold their spring meeting (Fruehjahrsfachgespraeche) from 26.-28. of February in Cologne (Germany). Sven Rudolph and I will be present to give some talks about Debian and Linux in general (1 full-day tutorial and 3 work-in-progress reports). If somebody needs free accommodation during the event, please contact me. Sven suggested to meet each other at that event. In case somebody is interested in planing this, contact him or me (no replies to the list, please). -Winfried -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Dselect suggestions: mailing list created
Pete Templin ([EMAIL PROTECTED]) wrote: : If any one else wishes to provide this service (in a more standard There is a mailinglist debian-admintool@lists.debian.org which works just as any other Debian mailing-list (if you don't know what this means, it's the wrong list for you). Please keep the traffic low on this list in the following sense: Over the past 2 years I've seen 99.99% good suggestions in this business. Only 0.01% (or less) code. That's the reason why we do not have a better dselect today: nobody actually got his fingers on the keyboard and implemented it. Did you now that the problem is just that easy? Yes, we all agree that dselect should be improved. We agreed about it 1 year ago, too. So please nobody wastes his time by making good suggestions. We need coders, nothing else. I warn you: if you are serious about coding, you will need _much_ time. It's far more work than one usally expects because you will have to program something which suits everyone: package maintainers, first time newbies and experts. Not to forget writing documentation, signing up long-time responsibility for the tool ... I estimate the workload at about 8h/week. -Winfried -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Interesting idea (was: Apache config error)
CoB SysAdmin (Joe Emenaker) ([EMAIL PROTECTED]) wrote: : export LOGS=/var/log/apache : export DOCS=/var/web/webspace : export CGI=/var/web/cgi-bin : the config files. However, I think there *may* exist somewhere in this idea : the ability to avoid more configuration change hassles than it would create. This is being worked on but with a slightly modified approach: using a database instead of sourcing a file (sourcing only moves the original problem to a new location). And of course the idea of using environment variables instead of hardcoded values in shell-scripts has several other advantages. There is already a mailinglist for discussing that issue which will be announced RSN (end of the week or so). The database is working and polished and the first public (ALPHA !) version will be available RSN, too. -Winfried -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: NTeX for Debian generalized packaging
Mark Phillips ([EMAIL PROTECTED]) wrote: : I myself have been using NTeX and have found it very good. Until july, NTeX shipped with modified cm-fonts that made it _incompatible_ with every other TeX of the world. Some students here at the university of cologne installed the german SuSE-Distribution (shipped with NTeX) and they wondered why their articles looked completly different when printed/viewed at university ... The difference between NTeX and the rest of the world was a 12 pages more/less on an 70-page document. It's a feature not a bug was the reaction to my bug-report. Sigh. The advantage of using teTeX instead is: it already ships with binaries for 23 plattforms and is proven to be a high quality TeX-Distribution (rumors say the author had tested it recently by installing it at CERN with several thousand users). My opinion is that we should not waste our time by providing several TeX-Distributions for Debian-users. We should stick either with the packages from Nils (works but is not that rich) or we should package up teTeX _instead_. -Winfried
Re: teTeX (was Re: dvips top margin)
Paul Seelig ([EMAIL PROTECTED]) wrote: : Updating of the ls-lR database should only be allowed to root anyway and : not to other users of the system as well! So i don't see the point in : this! The last time I used teTeX it was necessary to allow ordinary users to re-build the database so new pk-files were found. -Winfried
Re: adobe acrobat viewer in debian?
Matthew D Moss ([EMAIL PROTECTED]) wrote: : I found Adobe's beta3 of their Acrobat viewer, but they claim it is only : for the yggdrasiL (sp?) distribution... From the reports in linux.dev.kernel (awful it's used for this) it's likely the Reader will work under all distributions. A drawback: it only works on the console, not on X-Terminals ... -Winfried
Re: Need advise on repartitioning
Pedro I. Sanchez ([EMAIL PROTECTED]) wrote: : I have two hard disks, /dev/hda and /dev/hdb. The latter has only two : primary partitions assigned to swap and /home. I want to create a third : partition in /dev/hdb and asign it to /var, which currently lives in : /dev/hda in the same partition of / (no separate partition for /var). Two cases: (1) swap and /home do _not_ take up the whole space on /dev/hdb, so you effectivly have only to _add_ the partition (2) swap and /home take up the whole space and you must shrink one of both to get enough free space for /var The first case is simple: go into single-user mode and umount /home and swapoff /dev/hdb1. Now you can _add_ the new partition on /dev/hdb with cfdisk or similar and after that check that the new partition is recognized by the kernel with dmesg. If it is, you don't have to reboot and you can re-mount /home and re-activate the swap. Then run an mke2fs /dev/hdb3make the filesystem mkdir /var2-new create the mount-point mount /dev/hdb3 /var-newdo the mount cd /var-new change to the new partition cp -a /var/* . copy everything there mv var var-old rename the old one mv var-new var rename the new one In the second case you must make a backup of /home before doing anything else. Changing the size of a partition without destroying it is currently not supported by Linux. If you have done this, follow the steps about and destroy the /home-partion before re-creating it and adding the /var-partition. The rest is similar, you just have to perform everything twice (once for /home, once for /var) and write the backup back. If everything works, change /etc/fstab appropreciatly. -Winfried
Re: teTeX (was Re: dvips top margin)
Paul Seelig ([EMAIL PROTECTED]) wrote: : hierarchie. To my mind teTeX is the most up to date and most easy to : install and maintain LaTeX system because of it's well thought out design. I did not look into the new 0.4-release, but there was no upgrade-mechianism in the past. And if several users try to update the ls-lR database, it gets (got) messed up resulting in a not-working TeX/LaTeX (we had that several times and therefore stucked with debian-TeX). Beside that, teTeX is really nice! It would be a nice thing to have a teTeX-dummy package that satisfies all dependencies for dpkg if teTeX is installed. Re-packaging teTeX would be much work. -Winfried
Re: Does IP aliasing work?
John D. Amidon ([EMAIL PROTECTED]) wrote: : vtcs-cvs# ifconfig eth0:0 136.0.0.1 : SIOCSIFADDR: Invalid argument It means you have no eth0:0. Probably you didn't load the ip_alias module; just issue insmod ip_alias and it should work. A good idea would be to run kerneld (he manages things like that for you). The file /proc/net/alias exists wether you load the module or not. -Winfried
Re: Java Workshop
Miro Torrielli ([EMAIL PROTECTED]) wrote: : I doubt it, because there are some new shared libraries : and executables not mentioned in the howto, obviousy in : Solaris format. You may wish to ask Mike Gaertner [EMAIL PROTECTED], he is the maintainer of that HOWTO and very reponsive in general. -Winfried
Re: time to split the list?
I'm only subscribed to lists which do not carry more than 10 mails/week. This way my mailbox keeps mostly interesting stuff which I can oversee. It is a _must_ to convert high-traffic lists into newsgroups because: - one gets overwhelmed by the number of e-mails per day, - the disk gets clobbered by the size of the whole bunch (argh, I had 5 people sumitted to debian-users on my system), - newbies are not capable of (or have other problems than) setting up e-mail filters to sort the whole junk (hint: gnus is really cool), - high-traffic often means general interest (so why not make it more public?), - one actually pays for the whole junk to download it via modem, - one has to unsubscribe when going on holidays, On the other hand I see that + developers need to communicate more quickly than via news (takes up to 4 days) + it is much easier to create a mailing-list than a newsgroup So my suggestions are: o Tell the people about the newsgroup linux.debian.users as an alternative to the mailinglist when confirming their subscription. Ignoring the technical stuff is a special case of ignoring subjects of no personally interest and can be done with most news-readers. (Yes, you can do this easily with mailinglist by using gnus, too but thats the exception.) o make at least debian-users-digest for those people who want to keep on with the most interesting things o split the mailing-list to keep developers off from newbie-questions (they are likely to waste their time!) into debian-installation for questions not covered by the installation-manual :-) debian-newbies for those who have at least reached the login-prompt but aren't familiar with the system yet [no technical discussion allowed here; even such evil words as emacs, kernel and such are strictly forbidden] :-) debian-users the good old list; for long-time debian-users debian-towers high-level technical discussions o make a debian-all-digest from all that lists above -Winfried
Re: printing in debian/unix is hard...
Carlos Carvalho ([EMAIL PROTECTED]) wrote: : using apsfilter. It's more flexible than magicfilter, btw. The config Please explain this. Last time I used apsfilter, it was horrible to set up (that was more than 1 year ago). Winfried
Re: Getting 'less' to do the right thing (was Re: xterm subtleties)
Austin Donnelly ([EMAIL PROTECTED]) wrote: : $ export LESS='-M -X -z-2' In addition to that, I suggest '-I' which makes the text-search case insensitive (a search for Linux will match Linux, linux or LINUX ...). Winfried
Re: Dselect proposed interface (was Re: 1.1 installation notes.)
Kevin M Bealer ([EMAIL PROTECTED]) wrote: : The current dselect screen isn't bad -- it's efficient, etc. But it is : too 'unix' ... which is to say, you're expected to think. At this stage : the first time user has ~ 400 packages to deal with. All the power in : the world can be hidden _just_below_ the surface, but the steering wheel : and brakes have to be easy to find. I suggest a tree structure for hiding the details. Displaying everthing plus the kitchen sink to new users is only confusing. Call me stupid but is is even still confusing to me, after 1 year of debian. Sorry for wasting your time with the following incomplete and contradictory concept (Ian, I can already hear you moaning). I have no time to work this over, but I want to trough in some ideas. -Winfried ### Hint Sektion Type of SelectionSize admin X individualmost completenone 3.7 Important packages in section admin: [X] at delayed job execution and batch processing [-] cpio GNU cpio: a program to manage archives of files. [+] cron management of regular background processing Optional packages in section admin: ]-[ acct The GNU accounting utilities. [ ] dump Ported 4.4BSD dump and restore utilities. NEW [ ] linconf A GUI to configure every aspect of Linux ERROR[ ] quotaAn implementation of the diskquota system. === at - delayed job execution and batch processing (admin/important) at and batch read commands which are to be executed later. at is used to run a command at some specified future time, and batch is used to run a command when system load levels permit. The at system uses cron to get the commands executed, so you need cron to use at. Keys: ## v=verbose ## h=help ## ?=search ## +=select ## -=deselect ## q=quit ## ### Perhaps I should explain the meaning of the checklist-buttons: Symbol Description -- [X] installed [+] selected for installation [-] installed, selected for de-installation ]-[ installed, selected for de-installation and purge everything [ ] not installed I think this is an improvement over the current bitmask consisting of stars because it is more intuitive and directly corresponds to keys. Note that there is also enough leading space for unencrypted hints like NEW or ERROR. This space comes from not displaying the Section an priority over and over again (it wastes 15% of the space of every line on the upper half of the screen. Provoking: this is much better used by spaces). My motivation for calling it a waste: *** develOpt dchanges build the changes file for a debian *** develOpt dld dld - a library package of C functions *** develOpt dlltools Tools used to create DLL jumptable *** develOpt expect The expect/expectk programs and *** develOpt f2c A Fortran77 to C/C++ translator, plus *** develOpt fort77 An f2c front end to make it look like a *** develOpt g77 The GNU Fortran 77 compiler (ELF *** develOpt gcl GNU Common Lisp compiler. *** develOpt glibcdoc GNU C library Info documentation. *** develOpt guileThe GNU extension language. You see 10 times, that your're in section devel, inspecting the optional packages. Even if the current view is splitted up: - All Standard packages in section base - *** base Std libc5The Linux C library version 5 (run-time *** base Std libdb1 the Berkeley database routines (runtime *** base Std libgdbm1 GNU dbm database routines (runtime - All Unclassified packages in section base - *** base ? passwd Change password data. *** base ? util-linux Miscellaneous system utilities. --- All packages in section comm --- - All Optional packages in section comm - *** comm Opt lrzszzmodem/ymodem/xmodem transfer package you _can_ see that your're in a certain section, by looking at the headings. (This is even easier, if the screen is not full with chars). So, the information about the section and the priority could be displayed once instead. Where? For example, use the line in the middle: libdb1 installed; selected (was: selected). Standard It is no longer required to display
