[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#644798: marked as done (Interface naming in linprocfs)



Your message dated Fri, 28 Jul 2023 16:47:41 +0000
with message-id <[🔎] E1qPQcv-00EwDn-Ap@fasolo.debian.org>
and subject line Bug#1041056: Removed package(s) from unstable
has caused the Debian Bug report #644798,
regarding Interface naming in linprocfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
644798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644798
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kfreebsd-10
Severity: normal

I'm opening a bug to keep track of this. Please followup there (and
please use the BTS next time).

2011/10/8 Mats Erik Andersson <mats.andersson@gisladisker.se>:
> Dear all,
>
> for some time now I have been somewhat annoyed by the Linux kind
> of network adapter names put to display in "/proc/net/dev".
>
> Imagine now that we would revert the file to be displaying
> the BSD kernel names instead. What negative effects or failures
> are we to expect from such a change?
>
> At present "ifconfig", "netstat", and "route" use the BSD names.
> A priori I know of no utility the depends on Linux naming.
>
> Should one influence the corresponding functionality in
>
>   sys/compat/linprocfs/linprocfs.c
>
> to compile into either convention, based on a macro?

We can't make this a static decision because it depends on the
runtime.  If the runtime are Linux binaries (as is usually the case
when using linprocfs with FreeBSD), linprocfs should print Linux
names. If the runtime are GNU/kFreeBSD (or FreeBSD) binaries,
linprocfs should print BSD names.

What you propose would break chroots setups where people run
GNU/kFreeBSD in a chroot on FreeBSD, or vice-versa.

Fortunately, the runtime can be detected, since Linux binaries run in
a special compatibility mode.  This should be worked with upstream.
In general you should be careful before changing kernel ABI. Diverging
from upstream kernel ABI has many detrimental consequences.

Btw, we have the same problem with /proc/mounts (see
debian/patches/908_linprocfs_is_not_proc.diff).

-- 
Robert Millan



--- End Message ---
--- Begin Message ---
Version: 10.3~svn300087+ds1-1+rm

Dear submitter,

as the package kfreebsd-10 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1041056

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply to: