I'll try to add PCMCIA support to the follow-up release of 1.3.47. 47
is already stable and I'd rather not de-stabilize it. It will be
released tonight or tomorrow.
Any volunteers to check it as I have no way to test it.
Also, I have a PCMCIA 130 MB disk. I have written UnixWare drivers for
it
__ Reply Separator _
Subject: Re: Linux Kernel 1.3.47 Uploaded
Author: "mitchell"@[EMAIL PROTECTED]@MAILGW at DECPostmaster
Date:20/12/95 3:31 PM
On Tue, 19 Dec 1995, Simon Shapiro wrote:
>> 2. I'd like
Okay. I have created a new version of the pcmcia-cs package and am
currently uploading it. Here is a list of the files it creates:
pcmcia-cs-1.3.100_2.8.16-1_i386.deb
The binary version of the package. It includes the modules
compiled for kernel version 1.3.100 and all of the
I put the 2.0 kernel packages in the release yesterday evening.
Bruce
Package: fileutils
Version: 3.12-4
Under a recent kernel, dd seems to produce spurious extra output *only* if
stdout isn't redirected ...
$ echo 'This is a test.' | dd of=/tmp/testing bs=10k conv=sync
0+1 records in
1+0 records out
$ wc /tmp/testing
1 5 10240 /tmp/
hy.
ok, i have libc5-dev installed without changing anything with the header
files. and i have the current kernel source and headers installed.
i'm kompiling a program, that needs to access current kernel headers
(isdnutils), so i compile it with -I/usr/src/linux/include .
the problem :
-image.NEWS (revision 18757)
> +++ debian/linux-image.NEWS (working copy)
> @@ -1,3 +1,18 @@
> +linux-latest (44) unstable; urgency=low
> +
> + * The new kernel version includes security restrictions on links, which
> +are enabled by default. These are specified in
>
+ debian/linux-image.NEWS (working copy)
> @@ -1,3 +1,18 @@
> +linux-latest (44) unstable; urgency=low
> +
> + * The new kernel version includes security restrictions on links, which
> +are enabled by default. These are specified in
> +Documentation/sysctl/fs.txt in the
On Fri, Mar 02, 2012 at 05:11:58AM +, Ben Hutchings wrote:
> + * The new kernel version includes security restrictions on links, which
> +are enabled by default. These are specified in
> +Documentation/sysctl/fs.txt in the linux-doc-3.2 and linux-source-3.2
> +packag
Hi,
On Freitag, 2. März 2012, Kees Cook wrote:
> > + * The new kernel version includes security restrictions on links,
> > +These restrictions may cause some legitimate programs to fail.
> > +In particular, if the 'at' package is installed, you should either:
On Fri, 2012-03-02 at 07:43 +, Lars Wirzenius wrote:
> On Fri, Mar 02, 2012 at 05:11:58AM +, Ben Hutchings wrote:
> > + * The new kernel version includes security restrictions on links, which
> > +are enabled by default. These are specified in
> > +Documenta
On 02.03.2012 10:47, Holger Levsen wrote:
On Freitag, 2. März 2012, Kees Cook wrote:
> + * The new kernel version includes security restrictions on
links,
> +These restrictions may cause some legitimate programs to
fail.
> +In particular, if the 'at' package is in
=
> --- debian/linux-image.NEWS (revision 18757)
> +++ debian/linux-image.NEWS (working copy)
> @@ -1,3 +1,18 @@
> +linux-latest (44) unstable; urgency=low
> +
> + * The new kernel version includes security restrictions on links, which
> +are enabled by default. These are
t; > Index: debian/linux-image.NEWS
> > ===
> > --- debian/linux-image.NEWS (revision 18757)
> > +++ debian/linux-image.NEWS (working copy)
> > @@ -1,3 +1,18 @@
> > +linux-latest (44) unstable; urgency=low
> > +
>
ably very limited.
I see that audit follow_link messages are generated in the kernel
logs when doing completion as root in /tmp, but everything seems
to be fine.
--
Vincent Lefèvre - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Wor
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: Linux Unified Kernel
Version: 0.2.4-1
Upstream Author: Insigma li...@insigma.com.cn
URL: http://www.longene.org/en/
License: GPL
x27;s very visible with Ubuntu's kernel for many releases (since it uses
libata). The way that I'm working with that computer is that I'm
hand-compiling my own kernels, for the moment, but I'm not always there
to support my parents using it and the distribution kernels don't
Le lundi 19 octobre 2009 à 22:54 +0100, Vincent Sanders a écrit :
> IDE to libata decision
> --
>
> Debian will perform this transition using the udev packages in a
> similar way to Ubuntu. The Ubuntu developers have offered their
> assistance with this transition.
When is th
On Mon, 19 Oct 2009 22:54:47 +0100
Vincent Sanders wrote:
> A constructive discussion was held about the outstanding firmware
> issues, how the team addresses them and how we might work with upstream
> to address our DSFG issues with kernel sources.
By chance, did any of that discussion
> to address our DSFG issues with kernel sources.
>
> By chance, did any of that discussion touch on patching drivers so that
> they can load without the firmware? Many Eee PC owners currently have
> no DFSG-free option for wifi (short of replacing the card) because
> rt2860st
Due to changes in udev 147, squeeze will not support kernels earlier
than 2.6.27.
If your packages have code needed to support old kernels, this is the
right time to clean it up.
This means that lenny->squeeze upgrades will use the same lockstep
kernel/udev upgrade method used for etch->
Hi,
Now that we have a 2.6.32 kernel in unstable, can you updates us
on the various things mentioned in this mail?
For instance, as I understand it, most other distro's recently
had a release with a 2.6.31 kernel? Do you know if there are
plans to have a kernel with backported drivers
On Sun, 2009-12-20 at 17:22 +0100, Kurt Roeckx wrote:
> Hi,
>
> Now that we have a 2.6.32 kernel in unstable, can you updates us
> on the various things mentioned in this mail?
>
> For instance, as I understand it, most other distro's recently
> had a release with a
On Mon, Dec 21, 2009 at 12:50 AM, Ben Hutchings wrote:
>> > OSS
>> > ---
>> >
>> > This has been a deprecated kernel interface for some time and will be
>> > disabled for squeeze
>
> Done.
>
>> > with mechanisms put in place to deal
On Mon, 2009-12-21 at 09:24 +0800, Paul Wise wrote:
> On Mon, Dec 21, 2009 at 12:50 AM, Ben Hutchings wrote:
>
> >> > OSS
> >> > ---
> >> >
> >> > This has been a deprecated kernel interface for some time and will be
> >> > di
throws the data
back out to userspace would also work, I guess.
> this item refers to. (The existing snd-pcm-oss and snd-mixer-oss don't
> seem to be good enough.)
Specifically since they are in kernel they don't (and can't really) play
at all with any userspace ALSA stuff s
On Sun, Dec 20, 2009 at 04:50:22PM +, Ben Hutchings wrote:
> On Sun, 2009-12-20 at 17:22 +0100, Kurt Roeckx wrote:
> > Hi,
> >
> > Now that we have a 2.6.32 kernel in unstable, can you updates us
> > on the various things mentioned in this mail?
> >
> >
On Tue, Dec 22, 2009 at 07:39:22PM +0100, Kurt Roeckx wrote:
> On Sun, Dec 20, 2009 at 04:50:22PM +, Ben Hutchings wrote:
> > On Sun, 2009-12-20 at 17:22 +0100, Kurt Roeckx wrote:
> > Fedora 12, Ubuntu 9.10 and openSUSE 11.2 have this kernel version.
> I was hoping that var
On Sun, Dec 20, 2009 at 16:50:22 +, Ben Hutchings wrote:
> > > The X packages will be able to use modprobe
> > > config files to enable KMS at run time as required.
>
> This is not for the kernel team to do.
>
FWIW, this is done for intel in experimental, pro
On Tue, 2009-12-22 at 19:39 +0100, Kurt Roeckx wrote:
> On Sun, Dec 20, 2009 at 04:50:22PM +, Ben Hutchings wrote:
> > On Sun, 2009-12-20 at 17:22 +0100, Kurt Roeckx wrote:
> > > Hi,
> > >
> > > Now that we have a 2.6.32 kernel in unstable, can you up
Ben Hutchings wrote:
> Currently you can install kernel images from unstable or backports
> without any extra dependencies. I'm not aware of any significant
> breakage though some packages may rely on deprecated and removed stuff
> in procfs or sysfs.
I've been running up
Kurt Roeckx wrote:
> Now that we have a 2.6.32 kernel in unstable, can you updates us
> on the various things mentioned in this mail?
I have another question. The naming policy for linux-image packages seems
to have changed: instead of an ABI we now have "trunk". First I thought
On Wed, 2009-12-23 at 01:51 +0100, Frans Pop wrote:
> Ben Hutchings wrote:
> > Currently you can install kernel images from unstable or backports
> > without any extra dependencies. I'm not aware of any significant
> > breakage though some packages may rely on deprecate
On Wed, 2009-12-23 at 01:57 +0100, Frans Pop wrote:
> Kurt Roeckx wrote:
> > Now that we have a 2.6.32 kernel in unstable, can you updates us
> > on the various things mentioned in this mail?
>
> I have another question. The naming policy for linux-image packages seems
>
On Wed, Dec 23, 2009 at 01:51:01AM +0100, Frans Pop wrote:
> The following change in /etc/init.d/nfs-kernel-server fixes this:
> # See if our running kernel supports the NFS kernel server
> - if [ -f /proc/kallsyms ] && ! grep -qE 'init_nf(sd|
Michael Gernoth wrote:
> On Wed, Dec 23, 2009 at 01:51:01AM +0100, Frans Pop wrote:
>> The following change in /etc/init.d/nfs-kernel-server fixes this:
>> # See if our running kernel supports the NFS kernel server
>> -if [ -f /proc/kallsyms ] && ! grep -q
Ben Hutchings wrote:
> On Wed, 2009-12-23 at 01:51 +0100, Frans Pop wrote:
>> Ben Hutchings wrote:
>>> Currently you can install kernel images from unstable or backports
>>> without any extra dependencies. I'm not aware of any significant
>>> breakage th
Hello,
I have been working on an enhancement to the kdump-tools package that I maintain
and that implements the remote kernel crash dump capability
for Debian.
With this enhancement, it is possible to have the result of the makedumpfile
pass or the plain vmcore content to be sent remotely to a
Jeremy, le Mon 03 Nov 2014 09:03:25 -0500, a écrit :
> if only the kernel were replaced, the rest would still work as we al
> like it to. (This is evident with Debian GNU Hurd & kFreeBSD projects).
It's not so easy :)
> We all hear everyone say "The code is open
On Nov 03, Samuel Thibault wrote:
> You'll end up with contradictory issues: having driver support and
+---+ .:\:\:/:/:.
| PLEASE DO NOT |:.:\:\:/:/:.:
| FEED THE TROLLS | :=.' - - '.=:
Don't feed the troll.
signature.asc
Description: This is a digitally signed message part
y Pi.
Focus all effort into supporting one piece of hardware, then grow from
there when possible. Preferably open-source hardware. (lemote anyone?)
But focusing back on Linux kernel, their direction is questionable. Linus
himself hates security. He doesn't care. That mentality will trickle down.
On Mon, Nov 3, 2014 at 3:51 PM, Jeremy wrote:
[...]
> Also, look at the success of the Raspberry Pi.
[...]
> Preferably open-source hardware. [...]
[...]
https://wiki.debian.org/FreedomBox/TargetedHardware#Unsuitable
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a sub
Hello,
I am preparing a package for a scientific camera andor3.
This package contain a kernel module for the video grabber.
>From the constructor documentation, I need to add the nopat option to the
>linux command line.
So I would like to know what is the proper way to customize this c
avoid filling up /boot. And it is
the job of the installer to make sure systems get a kernel installed;
there is no sense in random packages also recommending/suggesting it!
* linux-headers
Same problem with auto-removal. The linux-headers-
metapackages built by linux-latest also provide this vi
Hello,
Installing (and booting into) linux-image-3.11-1-amd64 has fixed this for me.
Hi, all.
I think it's time to announce, that I've been working on a new Debian
port from the last fall.
This is Debian on illumos kernel (formerly OpenSolaris) - http://osdyson.org
It really aims to be *general-purpose* OS, not a server, a destop or
an appliance.
I was motivated becau
With the Wheezy kernel, I've experienced serious problems in WiFi
support because of the iwlwifi driver for Intel Centrino Ultimate
6300. For quite a while, I've been running kernels from the Debian
experimental server, various little things would break from
time-to-time. The wireless
On Sun, 2011-03-20 at 16:49 +0100, Harald Dunkel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi folks,
>
> I am using upstream's build procedure for creating Linux kernel packages
> ("make deb-pkg"). For 2.6.38 it gives you these packages:
&g
distinguish
>> between the hooks for linux-image and for linux-headers somehow?
>
> The headers package should invoke hook scripts in
> /etc/kernel/header_postinst.d (etc). dkms already installs a hook
> script there.
>
Sorry, I missed that.
Do you think that dkms sho
e run by the postinst script
> >> of linux-image, but of linux-headers. Shouldn't we distinguish
> >> between the hooks for linux-image and for linux-headers somehow?
> >
> > The headers package should invoke hook scripts in
> > /etc/kernel/header_postins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/21/11 14:22, Ben Hutchings wrote:
> On Mon, 2011-03-21 at 06:17 +0100, Harald Dunkel wrote:
>>
>> Do you think that dkms should drop its /etc/kernel/postinst.d/dkms
>> script? AFAICS this script might be called b
On Thu, 2011-03-31 at 10:59 +0200, Harald Dunkel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/21/11 14:22, Ben Hutchings wrote:
> > On Mon, 2011-03-21 at 06:17 +0100, Harald Dunkel wrote:
> >>
> >> Do you think that dkms should
nt handlers to run after the
>> installation
>> of all packages has been completed?
> [...]
>
> We had an extensive discussion defining a policy for the kernel and
> initramfs builder hooks only last year. It's a little late to comment
> now.
>
Two points a
this is highly complex. Maybe it would help to
>>> introduce some scheme to register event handlers to run after the
>>> installation
>>> of all packages has been completed?
>> [...]
>>
>> We had an extensive discussion defining a policy for the kernel
tand that this is highly complex. Maybe it would help to
> >> introduce some scheme to register event handlers to run after the
> >> installation
> >> of all packages has been completed?
> > [...]
> >
> > We had an extensive discussion defining a policy f
From the udev 168-2 changelog:
* Earliest kernel release supported raised from 2.6.27 to 2.6.32 due
to the usage of accept4(2).
So you may want to clean up your packages to remove all code needed for
compatibility with older kernels.
--
ciao,
Marco
signature.asc
Description: Digital
s not fully featured one yet. At least, I want to
provide it with squeeze.
and hope kernel-package would enable patch support again... ;)
--
Regards,
Hideki Yamane henrich @ debian.or.jp/iijmio-mail.jp
http://wiki.debian.org/HidekiYamane
--
To UNSUBSCRIBE, email to debian
Hi Yann
Thanks for the reminder. Yes it is time to remove at least the openvz
kernel patch package.
Best regards,
// Ola
On Sat, Mar 20, 2010 at 03:14:59PM +0100, Yann Dirson wrote:
> Since April 2009, kernel-package has no use any more for the
> {kernel,linux}-patch-* packages (AFA
to do so that I
> missed ?
As linux-patch-tomoyo1.7 package maintainer, tomoyo is merged with
mainline, but it's not fully featured one yet. At least, I want to
provide it with squeeze.
and hope kernel-package would enable patch support again... ;)
I won't speak for Manoj
As linux-patch-tomoyo1.7 package maintainer, tomoyo is merged with
> mainline, but it's not fully featured one yet. At least, I want to
> provide it with squeeze.
>
> and hope kernel-package would enable patch support again... ;)
I won't speak for Manoj here, but I feel we
> >> As linux-patch-tomoyo1.7 package maintainer, tomoyo is merged
> > >>with mainline, but it's not fully featured one yet. At least, I
> > >>want to provide it with squeeze.
> > >>
> > >> and hope kernel-package would enable patch suppor
t; > or is there any remaining reason not to do so that I missed ?
> >
> > As linux-patch-tomoyo1.7 package maintainer, tomoyo is merged with
> > mainline, but it's not fully featured one yet. At least, I want to
> > provide it with squeeze.
> >
> > a
On Tue, Mar 23 2010, Yann Dirson wrote:
> Let's maybe stay focussed on the initial problem: we *had* a way to
> handle kernel patches as part of a self-contained distribution, but
> there is no support for this any more. Moreover that support we had
> was not 100% satisfactory
the 'sid' branch in Subversion is now
available at:
git://git.debian.org/kernel/linux-2.6.git squeeze
http://git.debian.org/?p=kernel/linux-2.6.git;a=shortlog;h=refs/heads/squeeze
This *will* be rebased at will; please don't treat it as anything more
than informative at present.
Dear Debian Team,
Many thanks for releasing the 2.6.32-4-amd and -686 Debian kernel in
sid. This is really a big step forward. I especially benefit from
DRM/KMS in conjunction with the new radeon (also frame buffer) drivers.
A great kernel!
Thanks again, and best regards
Han, Shi-Ming
#1 If I use ./linux-2.6.38/README I get errors (see below).
If I use ./linux-2.4.20/README I get a [good] kernel.
#2 Nowhere can I find "root=/dev/hdax" needs to be "root=/dev/sdax" due to new SATA changes in
driver code. Others have reported this. I found it by accide
2011/12/5 John D. Hendrickson and Sara Darnell :
> #1 If I use ./linux-2.6.38/README I get errors (see below).
> If I use ./linux-2.4.20/README I get a [good] kernel.
>
Could you be more specific? mine so called ./linux* doesn't even
exists to begin with
> #2 Nowhere can I fin
one of the "kernel bug report" sites load in firefox (i get a
> 404, why? ipv6 only?). I can't post bug to them and have no "gpg
> key" either.
bugzilla.kernel.org is down due to the kernel.org outage reported at
<https://www.linuxfoundation.org/news-media/blogs/br
e and
manuals to see if the previous, that "hda==sda but use uuid isn't depreciated" is true.
FIRST UUID. Then "far below" "./linux" (/usr/src) and kernel bugs org.
No sorry. It's diffuclt to find. I don't see where it's been documented
Correcting myself! sorry. not sure anyone cares. I said "make deb-pkg"
didn't leave me any .deb **
"make deb-pkg" did make 4 .deb packages. they are in "$(srctree)/../", and one
I tried is good.
"make tar-pkg" leaves it in "$(srctree)/" and I'm still unsure how i would know to look in ".."
Ooops! Forgot the reference:
[1]http://wiki.debian.org/rtl819x
El 27/01/12 17:20, Luis Alejandro Martinez Faneyth escribio:
> Hi,
>
> I was wondering what was the package (or packages) where linux kernel
> modules that are not shipped with it (i.e. not included in the
> linux-ima
On Fri, 2012-01-27 at 17:20 -0430, Luis Alejandro Martínez Faneyth
wrote:
> Hi,
>
> I was wondering what was the package (or packages) where linux kernel
> modules that are not shipped with it (i.e. not included in the
> linux-image package) are packaged.
Various packages for dif
Hi Patrice,
Patrice Duroux, on 2022-11-05:
> There are many projects here and there (Termux, AnLinux, etc.) that are based
> on
> some sorts of kernel-free images of a minimal Debian system to be used through
> chroot (other Linux) or PRoot (Android) or whatever environments.
> M
On Sat, 2022-11-05 at 20:20 +0100, Patrice Duroux wrote:
> There are many projects here and there (Termux, AnLinux, etc.) that are based
> on
> some sorts of kernel-free images of a minimal Debian system to be used through
> chroot (other Linux) or PRoot (Android) or whatever environ
Many thanks Étienne and Paul for all the resources.
Regards,
Patrice
Also updated this to 6.5.1 today and still works
Den tors 7 sep. 2023 kl 08:37 skrev Luna Jernberg :
>
> Hey!
>
> Just installed Kernel 6.5 from experimental during Debcamp 2023 on my
> ThinkPad Edge 0217A16 and it works as intended on this laptop :)
>
> //Luna bittin Jernberg
Hello,
After the latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in
light of meltdown -- my nvidia drivers failed to load.
Rebulding the modules manually --
https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017
-- did fix it.
Did I m
Hi,
I want the following patch to be back ported to 4.9 kernel. Can you please let
me know if it can be back ported to 4.9 kernel?
https://github.com/torvalds/linux/commit/63a6fff353d01da5a22b72670c434bf12fa0e3b8
Thanks
I notice the dbg package for the kernel was moved, but it doesn't appear
to be installable.
I've added the necessary entry to /etc/apt/sources.list:
deb http://debug.mirrors.debian.org/debian-debug/ stretch-debug main
non-free contrib
and then I try to get the package:
# apt-g
On Mon, Feb 27, 2017 at 05:59:53PM +0100, Daniel Pocock wrote:
> Can anybody make any suggestions or add anything to the wiki?
My old Mac Mini had a crazy clock and ntp was not enough to sanitize it.
I fixed it by using adjtimex in addition to ntp.
As an example, my clock was off by 2890 parts p
Daniel Pocock writes:
> I've observed a system that had a wildly incorrect hardware clock (when
> it was first unboxed), I ran ntpdate to sync the kernel clock but after
> a shutdown and startup again it had a wacky time again.
> I came across the discussion about how the har
On Mon, 2017-02-27 at 11:18 -0800, Russ Allbery wrote:
> > Daniel Pocock writes:
>
> > I've observed a system that had a wildly incorrect hardware clock (when
> > it was first unboxed), I ran ntpdate to sync the kernel clock but after
> > a shutdown and startup
On 27/02/17 20:18, Russ Allbery wrote:
> Daniel Pocock writes:
>
>> I've observed a system that had a wildly incorrect hardware clock (when
>> it was first unboxed), I ran ntpdate to sync the kernel clock but after
>> a shutdown and startup again it had a wacky ti
Daniel Pocock writes:
> However, at the time when I ran ntpdate, ntp was not running. I had
> brought up the network manually due to an interface renaming issue on
> the first boot. Maybe when somebody runs ntpdate in a scenario like
> that the kernel is not sending the new date
Ben Hutchings writes:
> On Mon, 2017-02-27 at 11:18 -0800, Russ Allbery wrote:
>> The much simpler systemd-timesyncd doesn't set the hardware clock for
>> reasons that one may or may not agree with (I honestly haven't
>> researched it in any depth),
> It looks like it does iff the RTC is set to
somebody runs ntpdate in a scenario like
> > that the kernel is not sending the new date/time to the hardware clock.
>
> Right, ntpdate for some reason doesn't set the flag to do this.
[...]
There is a very good reason, which is that without continuous
adjustment the system clock cann
t; the first boot. Maybe when somebody runs ntpdate in a scenario like
>>> that the kernel is not sending the new date/time to the hardware
>>> clock.
>> Right, ntpdate for some reason doesn't set the flag to do this.
> [...]
> There is a very good reason, which
brought up the network manually due to an interface renaming issue on
> > > > the first boot. Maybe when somebody runs ntpdate in a scenario like
> > > > that the kernel is not sending the new date/time to the hardware
> > > > clock.
> > > Right, ntpdate f
On 27/02/17 21:26, Ben Hutchings wrote:
> On Mon, 2017-02-27 at 11:18 -0800, Russ Allbery wrote:
>>> Daniel Pocock writes:
>>
>>> I've observed a system that had a wildly incorrect hardware
>>> clock (when it was first unboxed), I ran ntpdate to sync
On Tue, Feb 28, 2017 at 10:15:23AM +0100, Daniel Pocock wrote:
> > But ntpd is also known to have a large amount of code written
> > without as much regard for security as one would hope. It seems
> > like an unnecessary risk for most systems.
>
>
> Thanks for that security tip, I'm tempted to g
Adam Borowski writes:
> On Tue, Feb 28, 2017 at 10:15:23AM +0100, Daniel Pocock wrote:
>> > But ntpd is also known to have a large amount of code written
>> > without as much regard for security as one would hope. It seems
>> > like an unnecessary risk for most systems.
>>
>>
>> Thanks for tha
Daniel Pocock writes:
> On 27/02/17 21:26, Ben Hutchings wrote:
>> But ntpd is also known to have a large amount of code written
>> without as much regard for security as one would hope. It seems
>> like an unnecessary risk for most systems.
> Thanks for that security tip, I'm tempted to get ri
ever, at the time when I ran ntpdate, ntp was not running. I had
> > > > > brought up the network manually due to an interface renaming issue on
> > > > > the first boot. Maybe when somebody runs ntpdate in a scenario like
> > > > > that the kernel is
Kurt Roeckx writes:
> Having ntpdate clear the unsynced flag doesn't make sense since it would
> start writing a time to the RTC each 11 minutes, and as Ben said you
> have no idea which of the 2 clocks is the most correct one.
Oh, I thought it was a one-shot thing, but it turns on syncing behav
On 28/02/17 01:00, Ben Hutchings wrote:
> On Mon, 2017-02-27 at 16:09 -0800, Russ Allbery wrote:
>> Right, ntpdate for some reason doesn't set the flag to do this.
>
> There is a very good reason, which is that without continuous
> adjustment the system clock cannot be assumed more stable than the
On Sat, 2017-03-04 at 20:33 +, Roger Lynn wrote:
> On 28/02/17 01:00, Ben Hutchings wrote:
> > On Mon, 2017-02-27 at 16:09 -0800, Russ Allbery wrote:
> > > Right, ntpdate for some reason doesn't set the flag to do this.
> >
> > There is a very good reason, which is that without continuous
> >
On 2017-02-28 20:01:52 +0100, Carsten Leonhardt wrote:
> Daniel Pocock writes:
>
> > On 27/02/17 21:26, Ben Hutchings wrote:
> >> But ntpd is also known to have a large amount of code written
> >> without as much regard for security as one would hope. It seems
> >> like an unnecessary risk for m
On 2017-03-05 03:52:33 +, Ben Hutchings wrote:
> I would also expect that users running command-line tools to set the
> time, such as ntpdate, have enough technical understanding to
> distinguish the system clock and RTC.
And what's worse is that by default, ntpdate is run automatically from
/
On Thu, 2016-06-02 at 09:12 +0200, Mathieu Malaterre wrote:
> Hi,
>
> I am starring at the documentation for rebuilding the Debian kernel.
> I'd like to test a change in a non-module section of the kernel code
> (CONFIG_FB_OF=y), to resolve #825840. So I thought I could
1001 - 1100 of 2571 matches
Mail list logo
