From: Bill Mitchell [EMAIL PROTECTED]
Am I that confused. I thoght that the release presently reachable
through ftp.debian.org:/debian/development was the development
release.
Yes. He means making it reachable to mirror programs that aren't
explicitly looking for it.
Bruce
--
Bruce
The `genksyms' executable is installed in /usr/bin, despite its
manual page belonging to section 8. The 1.3.47 kernel module support
at least expects to find it in /sbin. I made a symlink to pacify my
system, but perhaps it should really be moved there?
No, genksysm should be in /usr/bin
Okay, but the kernel makefile calls /sbin/genksyms explicitly, which
is why I think *something* ought to be there.
Actually I see now it is a kernel version issue: 1.2.13 calls
/usr/bin/genksyms, while 1.3.47 calls /sbin/genksyms. What to do?
The makefile ought to call `genksyms'. The PATH
umsdos with windows '95 filesystem might be a problem...
With linux's msdos-fs I were not able to delete a directory;
only got 'directory is not empty'-message even the directory
were empty.
Juhana
Sorry about the first message on this bug, I was trying to figure out how
to submit one and accidently submitted the gaff instead.
This report should have said:
Running kernel 1.3.43 in a 1.0 ELF system;
less-290-5 has been patched for the /proc filesystem, except that when
you less a proc
See if it works OK in non-compressed mode. I think the compression module
is buggy at the moment. That will probably go away once Simon, our new
kernel maintainer, is up to speed.
It's a little less dain-bramaged, but it still doesn't work. It's just
not executing ifconfig or route for some
See if it works OK in non-compressed mode. I think the compression module
is buggy at the moment. That will probably go away once Simon, our new
kernel maintainer, is up to speed.
It's a little less dain-bramaged, but it still doesn't work. It's just
not executing ifconfig or route for
Bill Mitchell writes (Re: ncurses build options...):
Should all packages which use common unix commands provided
by essential digest packages such as cat (textutls), echo
(shellutls), mkfs (miscutls) declare explicit dependencies on
the digest packages they need,
No.
or is the fact that
Bug: 2032 2036. Printer stuck #3.
_
the problem reports system sent me THIS:
Your message didn't have a Package: line at the start (in the
pseudo-header following the real mail header), or didn't have a
psuedo-header
Bruce Perens writes (Re: coming soon):
From: Ian Jackson [EMAIL PROTECTED]
[Bruce wrote:]
4. The /etc/init.d/functions file will no longer be used.
Please make it exist and be empty so that existing programs don't
break.
How about having it exist and have its _current contents_ and a
Bruce Perens writes (Re: New ftp method for dselect):
I used Andy Guy's FTP method for dselect to upgrade a bunch of ELF
packages automaticaly this evening. It worked very well, and even
detected corrupt and partially-downloaded packages when I used a kernel
with networking problems.
Good !
David Engel writes (Re: ncurses-1.9.8a ELF release):
Let's say I have a package named foo-n with a shared library in it
named libfoo.so.x.y that, at least for the time being, must always be
available by that name, even while dpkg is moving things around. Now,
at some point in the future, I
It's been a while since this subject has been raised here.
It is sometimes useful to mail authors of programs with non-free
copyrights to ask them to relax the copyright. This is generally
especially fruitful when the original copyright is very unclear or
badly-phrased, as this usually means the
Susan G. Kleinmann writes (Bug#2035: dpkg-deb and dpkg share the '-i' flag):
I had been under the impression that dpkg-deb was invoked when dpkg itself
was called with certain flags. If this is the plan, then the '-i' option
to dpkg doesn't follow the plan. Here are the ambiguities:
dpkg
Bruce Perens writes (Re: coming soon):
I was talking about moving initrunlvl to /etc, not /var/log .
Ah, sorry, I misunderstood you too.
Ian.
Martin Schulze writes (Where are the bugs?):
I'm missing bugs. In fact on ftp.debian.org /debian/debian-bugs/text
only bugreports up to #1810 do exist. Where are newer ones?
We're working on it. The US bugs mirror is broken atm - use the UK
site instead.
Ian.
Ian Murdock writes (Re: coming soon ):
I also agree that compatibility between distributions is paramount, but
I'd rather convince Caldera, Red Hat, etc. to be compatible with System V
than change Debian to be incompatible with it. We should make talking to
them the first step in resolving
Bill Mitchell writes (0.93 - 1.1 upgrade procedure?):
I had been running a hybrid system with the variously-revisioned
elf development packages announced on 11 Nov. Those packages
are now lost from my system, and I've now dropped back to a
0.93R6 system. What's the current recommended
'Michael Alan Dorman wrote:'
On Sun, 17 Dec 1995, Chris Fearnley wrote:
This is a preliminary release. It seems to work, but I'm disatisfied
with my handling of httpd configuration (basically there is none - you
have to edit /etc/httpd/* by hand).
Hmm. That's what kept me from releasing
Ian Jackson writes:
Ian Right. In order to avoid having to rename lots of packages or change
Ian their version numbers I propose the following naming scheme for files
Ian on the FTP site in the `binary' directory:
Ian
Ian package-name--version[-revision].deb
Ian
Ian Note the
On Mon, 18 Dec 1995, Chris Fearnley wrote:
* Should we create a new user and/or group to control access to the
hierarchy of html files? If so, why don't we make it official and get
Bruce to include in the base /etc/group and /etc/passwd files.
User nobody and group nogroup is either already
On Fri, 15 Dec 1995, roro wrote:
My bash is now (and should be in the future, maybe even with shared
readline):
[EMAIL PROTECTED]:tty1:/lib# ldd /bin/bash
libncurses.so.3.0 = /lib/libncurses.so.3.0
libc.so.5 = /lib/libc.so.5.2.18
and don't like to be invoked without
Let's say I have a package named foo-n with a shared library in it
named libfoo.so.x.y that, at least for the time being, must always be
available by that name, even while dpkg is moving things around. Now,
at some point in the future, I know that libfoo.so.x.y whill no longer
be needed
and don't like to be invoked without libncurses.so.3.0 handy. Is it
really ok to move libncurses.so.3.0 to libncurses.so.3.0.new in pre
I thought of an obvious solution to this problem, and I'd like it shot
down if possible:
simply write the scripts for doing these moves in something that's
On Mon, 18 Dec 1995, Richard Kettlewell wrote:
I believe under ELF it would actually be dynamically loaded are
therefore not drag libncurses into perl unless you actually used it,
but it's so wonderful I think it deserves a mention l-)
You know, you'd think I'd remember that, considering I
I have rebuilt the m4 package as ELF (per Ian J.'s request) and placed
the binary package into ftp.debian.org//debian/private/project/Incoming.
I haven't figured out how to create a .changes file yet (any pointers
would be appreciated) but it should look something like this:
Package: m4
I could make the bootstrap floppies support an FTP installation if you
would do the work necessary to integrate this method into dselect.
To do this you need a package naming standard - perhaps a deviation from
your plan, but easy enough to do and it would be of great benefit to us
in
What does AC power have to do with run-parts ??
run-parts is just a utility to run all the scripts in a directory.
I think you should think where else this problem should be solved -
possible the answer is to modify your /etc/crontab.
Yes. On second thought I shouldn't be running
I haven't figured out how to create a .changes file yet (any pointers
would be appreciated) but it should look something like this:
You need the dchanges package. Ian Murdock has been holding off
moving it into the distribution. The last time I looked, it
was in
'Michael Alan Dorman wrote:'
/usr/lib/apache is my choice for serverroot. Where the documents go
is site-specific. I'd like to also include an option to chroot httpd
to /usr/local/http or somesuch. Can dpkg install a package under some
arbitrary directory? If so then the preinst script
Karl Ferguson writes (Packages/Contents under 0.93):
I'm just wondering - does the Packages* and Contents* files really need
to be updated every day? There are no new packages being put in the
0.93 area, and therefor I'm no so sure we have to... Just saves the
mirrors downloading the same
Juhana K Kouhia:
umsdos with windows '95 filesystem might be a problem... With
linux's msdos-fs I were not able to delete a directory; only got
'directory is not empty'-message even the directory were empty.
Are you sure this is because of w95?
You can also get a directory into this
apache-httpd provides httpd (as does cern-httpd) so dpkg won't
install one until the other is removed.
This isn't completely optimal (for the people who want to use apache
but also need a proxy server). Ideally, someone should write up a
mini-howto on how to work around this simplicity
For the short term, I will provide a redhat compatibility package that
provides the symbolic links, etc., so that redhat packages will work
on Debian systems. Thus, the ugly symbolic links will only be there if
you ask for redhat compatibility. This is preparatory to arriving at some
sort of way
No! It is a conffile because /usr/bin/fax, a bash script, was the
only place to set your local fax settings as serial port, modem capabilities,
INIT strings, phone number, prinyer what have you.
If this is still the case, then /usr/bin/fax should be a symlink into
/etc, and the script should
Bruce wrote:
] For the short term, I will provide a redhat compatibility package that
] provides the symbolic links, etc., so that redhat packages will work
] on Debian systems. Thus, the ugly symbolic links will only be there if
] you ask for redhat compatibility. This is preparatory to arriving
From: Bjoern Stabell [EMAIL PROTECTED]
a common package format would be great, high priority for me at least :)
Thanks. I think going with a redhat compatibility package is the right
way for now, as it allows me to sidestep the esthetic objections for the
short term - the objectors need not
Package: ksmbfs
Version: 0.2.4-2
The `smbmount' and `smbumount' commands are supposed to be suid-safe so that
normal users can mount and unmount SMB filesystems.
Could the package please install these suid root, or perhaps at least query
the user to see if they should be?
If they are installed
Isn't it just as likely that /var/log will be on a mounted filesystem?
(In fact /var is a separate filesystem on mine.)
Ditto here ( and /var/spool is separate too). To be sane/safe, assume
that /sbin, /lib, and /etc are all that / has at boot time. Anything
else can be mounted on some mut's
I've heard other reports of UMSDOS interacting badly with W95's long
filename stuff. I'd put it down as a `backup first' thing for now -
though I don't use either of them.
umsdos with windows '95 filesystem might be a problem... With
linux's msdos-fs I were not able to delete a
I noticed that some but not all of the new packages
that get uploaded to the Incoming directory don't have
read permissions. Is there a reason for this? Are they
uploaded that way? I like to install the latest and
greatest as quick as possible. I know, that could be asking
for trouble but that's
Please, do not be offended but an introductory book to Unix may help you
here (to a degree).
1. I didn't have lp installed since the installation parameter screen
for this said line printer, not just printer.
``Line printer'' is as valid in Linux as a ``tty'' device name. We do
not have line
Package: xbase?
Version: 3.1.2-4
x11perf is not present in the current Debian distribution. The prescence of
manual pages and Xmark (a script relying on the output of x11perf) suggest that
it should be. A similiar situation exists for x11perfcomp and possibly xieperf.
Note that Xmark is
Where does it say they are suid safe?
From the smbmount(8) man page:
If the real uid of the caller is not root, smbmount
checks whether the user is allowed to mount a filesys-
tem on the mount-point. So it should be safe to make
smbmount setuid
Where does it say they are suid safe? What is different between a user mounting
a NFS and a smbfs, why should normal users be able to do this?
My reply address is quite likely corrupt. Please mail to [EMAIL PROTECTED]
or [EMAIL PROTECTED]
Andrew
__ Reply Separator
I missed the first part of this thread. Sorry. What is the resoning
for this drastic change?
Distribution file names don't parse at the moment because you can't
disambiguate the package name from the version number. I had suggested
that we standardize package names so that FTP scripts
From: Simon Shapiro [EMAIL PROTECTED]
And why do we want this brain dead file system (which even M$ does not
use for its own 1980 eras OS's) to boot a Unix O/S with?
Because it is the lowest common denominator, and it would let people
alter the bootstrap floppy from a non-Linux system before
From: [EMAIL PROTECTED] (David Engel)
OK, so package file names don't parse easily. Why couldn't the cross
reference be included in the Packages file? It's needed by dselect
anyway. Also, what about packages like ld.so where the file name
doesn't match the package name (ldso)? What am I
David Engel wrote:
OK, so package file names don't parse easily. Why couldn't the cross
reference be included in the Packages file? It's needed by dselect
anyway. Also, what about packages like ld.so where the file name
doesn't match the package name (ldso)? What am I missing?
Working
49 matches
Mail list logo
