On Friday 08 June 2018 16:18:36 Reco wrote:
> Hi.
>
> On Fri, Jun 08, 2018 at 02:05:45PM -0400, Gene Heskett wrote:
> > On Friday 08 June 2018 10:44:32 Dejan Jocic wrote:
> > > On 08-06-18, stuv wrote:
> > > > Hi everyone,
> > > >
> > > > I'm using a debian derivate of linux and i'm searchin
Hi.
On Fri, Jun 08, 2018 at 02:05:45PM -0400, Gene Heskett wrote:
> On Friday 08 June 2018 10:44:32 Dejan Jocic wrote:
>
> > On 08-06-18, stuv wrote:
> > > Hi everyone,
> > >
> > > I'm using a debian derivate of linux and i'm searching for a way to
> > > make permanent changes to the kern
On Friday 08 June 2018 10:44:32 Dejan Jocic wrote:
> On 08-06-18, stuv wrote:
> > Hi everyone,
> >
> > I'm using a debian derivate of linux and i'm searching for a way to
> > make permanent changes to the kernel boot parameters without GRUB or
> > any other boot loader, i want to disable ipv6 perm
On Fri, 08 Jun 2018 16:14:39 +0200
stuv wrote:
> Hi everyone,
>
> I'm using a debian derivate of linux and i'm searching for a way to
> make permanent changes to the kernel boot parameters without GRUB or
> any other boot loader, i want to disable ipv6 permanently, when i do it
> over /init.d/mo
On 08-06-18, stuv wrote:
> Hi everyone,
>
> I'm using a debian derivate of linux and i'm searching for a way to
> make permanent changes to the kernel boot parameters without GRUB or
> any other boot loader, i want to disable ipv6 permanently, when i do it
> over /init.d/modprobe.d the changes onl
Hi,
You can use the option --revision in make-kpkg
(make-kpkg --initrd --revision 1.0 kernel_image)
or you can change the default in file /etc/kernel-pkg.conf to 1.0
so everytime you give make-kpkg the revision is always want you want.
Bye
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Hello Miguel,
if you are using make-kpkg ,
you may try the option `--revision'
hth,
Jerome
Miguel J. Jiménez wrote:
Hi... I am testing self made kernels on my desktop, using the debian way
found in http://www.howtoforge.com... My question is about the name
given to the deb package generated..
On 08/28/2007 02:15 PM, [EMAIL PROTECTED] wrote:
Quoting "Mumia W.." <[EMAIL PROTECTED]>:
On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote:
I notice there is a source package for the kernel and a package of
debian patches. Has the kernel source already been patched or would
one need to patch
On Tue, 28 Aug 2007 15:15:08 -0400
[EMAIL PROTECTED] wrote:
> Quoting "Mumia W.." <[EMAIL PROTECTED]>:
>
> > On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote:
> >> I notice there is a source package for the kernel and a package of
> >> debian patches. Has the kernel source already been patched
Quoting "Mumia W.." <[EMAIL PROTECTED]>:
On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote:
I notice there is a source package for the kernel and a package of
debian patches. Has the kernel source already been patched or would
one need to patch it with all of the included debian patches when
On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote:
I notice there is a source package for the kernel and a package of
debian patches. Has the kernel source already been patched or would one
need to patch it with all of the included debian patches when building a
custom kernel?
It's already p
Bill Moseley wrote:
On Fri, Jul 09, 2004 at 01:04:13PM -0400, Roberto Sanchez wrote:
do_clean := NO
to your /etc/kernel-pkg.conf
Then, it won't clean the tree prior to starting a make. Now you can do
it the Debian way and not worry about wasting too much time.
Well, that will be a huge help! I s
On Fri, Jul 09, 2004 at 01:04:13PM -0400, Roberto Sanchez wrote:
> do_clean := NO
>
> to your /etc/kernel-pkg.conf
>
> Then, it won't clean the tree prior to starting a make. Now you can do
> it the Debian way and not worry about wasting too much time.
Well, that will be a huge help! I suspect
Bill Moseley wrote:
On Fri, Jul 09, 2004 at 01:20:06PM +0200, Pim Bliek wrote:
It is maybe harder in the beginning, but once you get used to it is
really easier in my opinion. Why? Because you can easily go back to
previously built kernels; you still have the .debs in /usr/src, so it
makes it rathe
On Fri, Jul 09, 2004 at 01:20:06PM +0200, Pim Bliek wrote:
> It is maybe harder in the beginning, but once you get used to it is
> really easier in my opinion. Why? Because you can easily go back to
> previously built kernels; you still have the .debs in /usr/src, so it
> makes it rather flexible.
j smith wrote:
thanks!
i read the Debian book, but it explicitly says:
"Note that you don't have to compile your kernel the
``Debian way''; but we find that using the packaging
system to manage your kernel is actually safer and
easier."
so i choose non-debian way. the correct command is
"make modul
j smith wrote:
> thanks!
>
> i read the Debian book, but it explicitly says:
>
> "Note that you don't have to compile your kernel the
> ``Debian way''; but we find that using the packaging
> system to manage your kernel is actually safer and
> easier."
>
> so i choose non-debian way. the correct
It is maybe harder in the beginning, but once you get used to it is
really easier in my opinion. Why? Because you can easily go back to
previously built kernels; you still have the .debs in /usr/src, so it
makes it rather flexible.
And yes, I've got xawtv running using 2.6.5 if I am correct (I am
i find it easier.
have you followed instruction in the Debian handbook
and installed kernel 2.6 and successfully run xawtv?
if so, i will have to try debian way, which i find
harder.
--- Pim Bliek <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > i read the Debian book, but it explicitly says:
> >
> > "
Hi,
> i read the Debian book, but it explicitly says:
>
> "Note that you don't have to compile your kernel the
> ``Debian way''; but we find that using the packaging
> system to manage your kernel is actually safer and
> easier."
>
> so i choose non-debian way. the correct command is
Just out o
thanks!
i read the Debian book, but it explicitly says:
"Note that you don't have to compile your kernel the
``Debian way''; but we find that using the packaging
system to manage your kernel is actually safer and
easier."
so i choose non-debian way. the correct command is
"make modules_install",
First of all, you shouldn't be compiling kernels from source from
kernel.org unless you have a special reason for it and you what you
are doing.
Instead, you should be installing / compiling new kernels "the Debian
way", which is slightly different, but is quite cool once you get the
hang of it :)
Hi !
I marked the Realtek 8139 and the VIA Rhine in menuconfig and everything
works fine now.
eth0 became eth1 and vice versa but that's not a problem.
Thank you all.
Joachim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Jocahim,
Roberto Sanchez wrote:
--- Joachim Smit <[EMAIL PROTECTED]> escribió:
I have 2 controllers, 1 is on board and the other a PCI controller, not a
3com. I will try it again WITH support for 3com.
Kind regards,
Joachim Smit
What onboard controller (chipset) do you have?
-Rober
--- Joachim Smit <[EMAIL PROTECTED]> escribió:
> I have 2 controllers, 1 is on board and the other a PCI controller, not a
> 3com. I will try it again WITH support for 3com.
>
> Kind regards,
>
> Joachim Smit
What onboard controller (chipset) do you have?
-Roberto
_
On Sat, 12 Jul 2003 18:13:55 +0200
"Joachim Smit" <[EMAIL PROTECTED]> wrote:
> This is what I did: (according to documentation from www.debian.org)
Try this:
http://newbiedoc.sourceforge.net/system/kernel-pkg.html
In the kernel configuration, you need to include support for both your
onboard co
>
> When you went into menuconfig, did you enable support for the 3com NIC
> specifically (either as a module or as a compiled in feature)? If not,
> that could be the problem.
>
In menuconfig, I enabled support for:
Network device support -> Ethernet 10 or 100 Mbit -> EISA, VLB, PCI and on
boar
--- Joachim Smit <[EMAIL PROTECTED]> escribió:
> >
> >
> > did u make a "make modules && make modules install" ???
> >
>
> This is what I did: (according to documentation from www.debian.org)
>
> login root
> apt-get install gcc kernel-package kernel-source-2.4.18 libc6-dev tk8.3
> libncurses5-
>
>
> did u make a "make modules && make modules install" ???
>
This is what I did: (according to documentation from www.debian.org)
login root
apt-get install gcc kernel-package kernel-source-2.4.18 libc6-dev tk8.3
libncurses5-dev fakeroot
adduser joachim src
logout
login joachim
cd /usr/src
tar
- Original Message -
From: "Joachim Smit" <[EMAIL PROTECTED]>
To: "Debian" <[EMAIL PROTECTED]>
Sent: Saturday, July 12, 2003 5:39 PM
Subject: Fw: Question about kernel upgrade
> > >
> > >I'm a newbie with Debian.
> > >
> > >I've upgraded my kernel from 2.2.20 to 2.4.18.
> > >
> > >After
>
>- Original Message -
>From: Joachim Smit
>To: [EMAIL PROTECTED]
>Sent: Saturday, July 12, 2003 5:05 PM
>Subject: Question about kernel upgrade
>
>
>I'm a newbie with Debian.
>
>I've upgraded my kernel from 2.2.20 to 2.4.18.
>
>After a reboot I was running the new kernel indeed, but m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 11 January 2002 01:44 pm, Mark Ferlatte wrote:
> On Fri, Jan 11, 2002 at 01:26:24PM -0600, Ron Johnson wrote (1.00):
> > So... anyone know what tsc means?
>
> Time Stamp Counter. An instruction was added in the Intel Pentium line
> called R
On Fri, Jan 11, 2002 at 01:26:24PM -0600, Ron Johnson wrote (1.00):
> So... anyone know what tsc means?
Time Stamp Counter. An instruction was added in the Intel Pentium line
called RDTSC, which you can use for high resolution timing, performance
monitoring, etc.
>From what I can tell, if you h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 11 January 2002 01:13 pm, Sander Smeenk wrote:
> Quoting Ron Johnson ([EMAIL PROTECTED]):
> > kernel-image-2.4.17-586tsc
> > What does the tsc stand for?
>
> I don't know for sure wat 'tsc' stands for, but additional "version
> information"
Quoting Ron Johnson ([EMAIL PROTECTED]):
> kernel-image-2.4.17-586tsc
> What does the tsc stand for?
I don't know for sure wat 'tsc' stands for, but additional "version
information" tells you what options are compiled in the kernel or what
patches are used to create the kernel. Like this:
2.4
On Mon, 20 Apr 1998, Carroll Kong wrote:
> Yes. There is the new 'nestea' attack ... linux is linux,
> regardless of distribution. In other words, debian is definately
> vulnerable, there are patches available. I forgot exactly where I got
> mine, (sorry), but it is something like ip_f
Yes. There is the new 'nestea' attack ... linux is linux, regardless of
distribution. In other words, debian is definately vulnerable, there are
patches available. I forgot exactly where I got mine, (sorry), but it is
something like ip_fragment.c and you throw it into your kernel source
37 matches
Mail list logo
