On Friday, November 11, 2011 08:48:42 AM Dale wrote:
J. Roeleveld wrote:
On Tue, November 8, 2011 10:33 am, Dale wrote:
The only report that raccoon will give is a bright flash of light.
Shorting out 250,000 volts sort of puts a period on the end of the
briefest report there has ever
Joost Roeleveld wrote:
On Friday, November 11, 2011 08:48:42 AM Dale wrote:
Now that you mention it, maybe they will run out of test subjects. o_O
They're currently in the middle of negotiations to take over the penal system
of the rabbits ;)
Once they get that contract, they'll have a
On Tue, November 8, 2011 10:33 am, Dale wrote:
J. Roeleveld wrote:
On Mon, November 7, 2011 1:32 pm, Dale wrote:
All this from a raccoon knocking out power. Pesky critter.
Raccoons are doing some behaviour studies in your area, didn't you get
the
memo? :)
--
Joost
The only report that
J. Roeleveld wrote:
On Tue, November 8, 2011 10:33 am, Dale wrote:
The only report that raccoon will give is a bright flash of light.
Shorting out 250,000 volts sort of puts a period on the end of the
briefest report there has ever been. Those lines are the TVA lines that
come from a few
On Wed, 09 Nov 2011 21:18:05 -0500, Mike Edenfield wrote:
There is, but the file is called .version. The contents of this are
appended to the kernel name when you have the relevant options set.
There is no manual intervention needed.
But I still need to create .version every time I
On 11/9/2011 2:04 AM, Mick wrote:
On Wednesday 09 Nov 2011 02:43:43 Mike Edenfield wrote:
On 11/6/2011 8:54 PM, Dale wrote:
Mine is like this:
-rw-r--r-- 1 root root 4547936 Aug 22 03:53
/boot/bzImage-3.0.3-1
-rw-r--r-- 1 root root 4548640 Sep 1 07:19
/boot/bzImage-3.0.4-1
-rw-r--r-- 1 root
On Wed, 09 Nov 2011 08:47:07 -0500, Mike Edenfield wrote:
Are you saying then that every time you download new source files you
have to create or cp new localversion* files in /usr/src/linux/ for
this auto-numbering to work?
Yeah, though I wouldn't be surprised if there was already a
On 11/9/2011 8:55 AM, Neil Bothwick wrote:
On Wed, 09 Nov 2011 08:47:07 -0500, Mike Edenfield wrote:
Are you saying then that every time you download new source files you
have to create or cp new localversion* files in /usr/src/linux/ for
this auto-numbering to work?
Yeah, though I wouldn't
On Mon, November 7, 2011 1:32 pm, Dale wrote:
SNIP
I looked for such a option but I can't find it anywhere. It may be
there but I can't find it. Since it is working and the AHCI controller
sees the drives, I'm going to leave well enough alone.
I checked my desktop at home last night and the
J. Roeleveld wrote:
On Mon, November 7, 2011 1:32 pm, Dale wrote:
SNIP
I looked for such a option but I can't find it anywhere. It may be
there but I can't find it. Since it is working and the AHCI controller
sees the drives, I'm going to leave well enough alone.
I checked my desktop at
On 11/6/2011 8:54 PM, Dale wrote:
Mine is like this:
-rw-r--r-- 1 root root 4547936 Aug 22 03:53
/boot/bzImage-3.0.3-1
-rw-r--r-- 1 root root 4548640 Sep 1 07:19
/boot/bzImage-3.0.4-1
-rw-r--r-- 1 root root 5162752 Oct 12 21:49
/boot/bzImage-3.0.4-2
-rw-r--r-- 1 root root 5167840 Oct 13 00:05
On Wednesday 09 Nov 2011 02:43:43 Mike Edenfield wrote:
On 11/6/2011 8:54 PM, Dale wrote:
Mine is like this:
-rw-r--r-- 1 root root 4547936 Aug 22 03:53
/boot/bzImage-3.0.3-1
-rw-r--r-- 1 root root 4548640 Sep 1 07:19
/boot/bzImage-3.0.4-1
-rw-r--r-- 1 root root 5162752 Oct 12
On Mon, 7 Nov 2011 12:00:39 +1100, Adam Carter wrote:
All it does it copy the kernel, system map and config to /boot and
reset the symlinks to point to the new and previous kernels. You can
still keep as many kernels as you want in /boot, but you can always
boot the last two without
Mark Knecht wrote:
On Sun, Nov 6, 2011 at 7:06 AM, Dalerdalek1...@gmail.com wrote:
SNIP
IF by the 'first screen' you mean what you see when booting up then it
may or may not be a problem. I suspect your BIOS settings got
scrambled a bit. With my Asus MB there is an option to tell it to show
Hi,
This is weird and I'm not sure what info to give yet. This is the
events tho. First, a raccoon got on the power substation transformer
that supplies power for the whole county, excluding my local city which
has its own transformer. So, we lost power. It was sudden just like a
power
On Sunday 06 Nov 2011 12:43:06 Dale wrote:
Hi,
This is weird and I'm not sure what info to give yet. This is the
events tho. First, a raccoon got on the power substation transformer
that supplies power for the whole county, excluding my local city which
has its own transformer. So, we
Dale wrote:
Hi,
This is weird and I'm not sure what info to give yet. This is the
events tho. First, a raccoon got on the power substation transformer
that supplies power for the whole county, excluding my local city
which has its own transformer. So, we lost power. It was sudden just
Mick wrote:
Can you set in your BIOS which controller IDE or SATA manages the
drives? I'm not sure why you have a symlink to your /usr/src/linux
files from /boot (I don't understand it). In /boot you should have the
image files themselves of your desired kernels (plus corresponding
System and
On Sun, Nov 6, 2011 at 4:43 AM, Dale rdalek1...@gmail.com wrote:
SNIP
When I did my ls on
/boot, the kernels were symlinks to the kernel sources on /usr which is not
mounted yet.
SNIP
Why in the world would a kernel on /boot _ever_ be a symlink? That's
just not right for guys like you and me
Mark Knecht wrote:
On Sun, Nov 6, 2011 at 4:43 AM, Dalerdalek1...@gmail.com wrote:
SNIP
When I did my ls on
/boot, the kernels were symlinks to the kernel sources on /usr which is not
mounted yet.
SNIP
Why in the world would a kernel on /boot _ever_ be a symlink? That's
just not right for
On Sun, Nov 6, 2011 at 7:06 AM, Dale rdalek1...@gmail.com wrote:
SNIP
IF by the 'first screen' you mean what you see when booting up then it
may or may not be a problem. I suspect your BIOS settings got
scrambled a bit. With my Asus MB there is an option to tell it to show
the drives on the
Hi,
is it an Asus board?
Because Asus went cheap on bios chips not too long ago. Now we have the fun of
Asus bioses getting confused because of stuff like turning off and similar
cruel treatment. The fuck up with your transformer might habe caused a short
spike, damaging the settings.
In my
Volker Armin Hemmann wrote:
Hi,
is it an Asus board?
Because Asus went cheap on bios chips not too long ago. Now we have the fun of
Asus bioses getting confused because of stuff like turning off and similar
cruel treatment. The fuck up with your transformer might habe caused a short
spike,
Am 06.11.2011 15:26, schrieb Dale:
Mick wrote:
Can you set in your BIOS which controller IDE or SATA manages the
drives? I'm not sure why you have a symlink to your /usr/src/linux
files from /boot (I don't understand it). In /boot you should have the
image files themselves of your desired
Florian Philipp wrote:
Am 06.11.2011 15:26, schrieb Dale:
Mick wrote:
Can you set in your BIOS which controller IDE or SATA manages the
drives? I'm not sure why you have a symlink to your /usr/src/linux
files from /boot (I don't understand it). In /boot you should have the
image files
On Sun, 06 Nov 2011 13:21:33 -0600, Dale wrote:
Odd thing. I never noticed they were symlinks. A simple `sudo cp ...`
does the right thing here. Did you use `cp -a`, maybe through an
alias?
I do use -av out of habit. That habit started when I was copying
installs from one drive to
Neil Bothwick wrote:
On Sun, 06 Nov 2011 13:21:33 -0600, Dale wrote:
Odd thing. I never noticed they were symlinks. A simple `sudo cp ...`
does the right thing here. Did you use `cp -a`, maybe through an
alias?
I do use -av out of habit. That habit started when I was copying
installs from
On Sun, 06 Nov 2011 16:22:41 -0600, Dale wrote:
Or you could use make install and remove the possibility for
screw-ups. After all, you trust make to build and kernel, then build
and copy the entire module tree. Surely you can manage to trust it
with one more file :-O
I did use it once
All it does it copy the kernel, system map and config to /boot and reset
the symlinks to point to the new and previous kernels. You can still keep
as many kernels as you want in /boot, but you can always boot the last two
without modifying GRUB's config.
Can you please ls -l /boot so i can
On Nov 7, 2011 8:03 AM, Adam Carter adamcart...@gmail.com wrote:
All it does it copy the kernel, system map and config to /boot and reset
the symlinks to point to the new and previous kernels. You can still
keep
as many kernels as you want in /boot, but you can always boot the last
two
On Nov 7, 2011 8:18 AM, Pandu Poluan pa...@poluan.info wrote:
On Nov 7, 2011 8:03 AM, Adam Carter adamcart...@gmail.com wrote:
All it does it copy the kernel, system map and config to /boot and
reset
the symlinks to point to the new and previous kernels. You can still
keep
as many
Pandu Poluan wrote:
On Nov 7, 2011 8:18 AM, Pandu Poluan pa...@poluan.info
mailto:pa...@poluan.info wrote:
On Nov 7, 2011 8:03 AM, Adam Carter adamcart...@gmail.com
mailto:adamcart...@gmail.com wrote:
All it does it copy the kernel, system map and config to /boot
and reset
the
32 matches
Mail list logo
