On Sun, Apr 14, 2024 at 12:03 PM wrote:
>
> i don't see an armel repo on any of the mirrors i checked
> it was there a week ago
> has it been deleted or am i just old and blind
>
Hi.. I just took a quick poke at this by using the following k/t debootstrap:
http://deb.debian.org/debian
By clicki
i don't see an armel repo on any of the mirrors i checked
it was there a week ago
has it been deleted or am i just old and blind
Clinton Scott wrote:
> Is there a package available that both walks you through the steps and has
> the os to install debian on an rca galileo tablet?
Do you mean that you want to install Debian as the boot OS for
this tablet, or that you want to have access to a Debian
environment that is somet
Is there a package available that both walks you through the steps and has
the os to install debian on an rca galileo tablet?
Thanks in advance
On 2/16/19 5:41 AM, rhkra...@gmail.com wrote:
On Friday, February 15, 2019 10:39:58 PM Peter Ehlert wrote:
I don't really know,
What don't you really know? It would be a lot easier to know what you're
talking about if you put your answer under the relevant question (i.e., not
top posting)
Pa
On Friday, February 15, 2019 10:39:58 PM Peter Ehlert wrote:
> I don't really know,
What don't you really know? It would be a lot easier to know what you're
talking about if you put your answer under the relevant question (i.e., not
top posting)
> it is a net install, draws the current packag
I don't really know, it is a net install, draws the current packages
from the repos... so it must have access. no wire was plunged in and my
wifi adapter needed iwiwifi-7260-17.ucode and asked for it.
The installer seems to Only install needed/desired packages.
for example, I did Not want the "d
On 2/15/2019 11:01 AM, Peter Ehlert wrote:
Buster install on 820 Friday, February 15 2019
on USB #1: firmware-buster-DI-alpha5-amd64-netinst.iso
I also have on USB #2: firmware-9.4.0-amd64-DVD-1.iso
booted with #1, ... It did ask for firmware, I put #2 in and pressed
"continue" and install co
Buster install on 820 Friday, February 15 2019
on USB #1: firmware-buster-DI-alpha5-amd64-netinst.iso
I also have on USB #2: firmware-9.4.0-amd64-DVD-1.iso
booted with #1, ... It did ask for firmware, I put #2 in and pressed
"continue" and install continued and I was able to select my wifi
Hop
On 14/02/19 2:30 AM, deb wrote:
> Thank you Alexander.
>
> I kinda like the idea of pulling the Intel wifi and just going with a
> Think Penguin free software wifi.
>
> https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb
>
>
The one that says: "Debian 7,
On 2/12/2019 3:25 PM, Alexander V. Makartsev wrote:
In response to that painful "(still installing 9.7 ...)".
You can also use these official and unofficial at the same time images
to install Debian. [1]
As a last resort you can disassemble laptop and physically remove Intel
WiFi NIC before ins
On 12.02.2019 3:46, deb wrote:
>
> Thanks ~everyone:
>
> Do I gather correctly that Brian is the resident, sarcastic,
> cranky-pants herein?
>
> I stopped reading his replies to folks.
>
>
> anyways:
>
> > A suggestion, especially when installing on unfamiliar hardware, is
> to download the fi
On Mon 11 Feb 2019 at 17:46:19 (-0500), deb wrote:
> [ Peter wrote: ]
> > A suggestion, especially when installing on unfamiliar hardware, is
> to download the firmware archive for your platform and unpack it into
> a directory named firmware
>
> I hear you on this @Peter^
>
> I guess I'm kinda w
On Mon 11 Feb 2019 at 17:46:19 -0500, deb wrote:
> Do I gather correctly that Brian is the resident, sarcastic, cranky-pants
> herein?
Flatterer.
--
Brian.
deb, on 2019-02-11 :
> Do I gather correctly that Brian is the resident, sarcastic,
> cranky-pants herein?
>
> I stopped reading his replies to folks.
Well, I prefer to make no assumptions about people just by
looking on the content of two emails. After all the first
intervention from Brian has m
Thanks ~everyone:
Do I gather correctly that Brian is the resident, sarcastic,
cranky-pants herein?
I stopped reading his replies to folks.
anyways:
> A suggestion, especially when installing on unfamiliar hardware, is
to download the firmware archive for your platform and unpack it i
the last time I had such a problem (Buster net install using wifi) I
bookmarked this
https://wiki.debian.org/Firmware#Firmware_during_the_installation
I believe restarting the installer (from USB) with a second USB inserted
with the firmware solved it... needed packages were found and used.
s
On Mon 11 Feb 2019 at 14:01:06 -0600, David Wright wrote:
> Are you sure about 8625, rather than 8265?
Well-spotted.
https://packages.debian.org/stretch/firmware-iwlwifi
--
Brian.
On Mon 11 Feb 2019 at 20:42:10 +0100, Étienne Mollier wrote:
> I believe I found those firmware images in the package
> firmware-misc-nonfree. You can install it using:
I believe you have not.
https://packages.debian.org/sid/all/firmware-misc-nonfree/filelist
--
Brian.
On Mon 11 Feb 2019 at 13:33:39 (-0500), deb wrote:
>
> Hello folks:
>
> When I hit the networking section on a fresh install of 9.6 (full
> install .ISO, not live),
>
> I'm told to insert a USB of these non-free bits.
>
> iwlwifi-8625-26.ucode, iwlwifi-8625-25.ucode,
> iwlwifi-8625-24.ucode,
On 2/11/19 8:42 PM, Étienne Mollier wrote:
> I believe I found those firmware images in the package
> firmware-misc-nonfree. You can install it using:
>
> $ sudo apt install firmware-misc-nonfree
Whoopsie, one should read "firmware-iwlwifi".
Anyway, the iwlwifi-8625-22.ucode alone should d
Good Day,
Usually this shouldn't be an issue, but due to the nature of
the recent vulnerability in the package installer APT, any
Debian ISO up to 9.6 should be trashed and replaced by 9.7 or
greater.
See https://www.debian.org/security/2019/dsa-4371
and https://www.debian.org/News/2019/20190123
On Mon 11 Feb 2019 at 13:33:39 -0500, deb wrote:
[...]
> * wouldn't it be useful for the installer to Also say what exact hardware it
> is, that is requiring various bits & pieces?
As far as I can see, you haven't given which hardware you are using either.
--
Brian.
Hello folks:
When I hit the networking section on a fresh install of 9.6 (full
install .ISO, not live),
I'm told to insert a USB of these non-free bits.
iwlwifi-8625-26.ucode, iwlwifi-8625-25.ucode, iwlwifi-8625-24.ucode,
iwlwifi-8625-23.ucode, iwlwifi-8625-22.ucode
The Problem is -
On Wed, 21 Feb 2018 23:19:04 +0100
Pascal Hambourg wrote:
> Le 21/02/2018 à 03:53, Dan Norton a écrit :
> >
> > In contrast, with GPT and LVM, for the second and subsequent
> > installations, the partitioning and defining of PVs, VGs, and LVs
> > needs to be done before installation using gdisk
Le 21/02/2018 à 03:53, Dan Norton a écrit :
In contrast, with GPT and LVM, for the second and subsequent
installations, the partitioning and defining of PVs, VGs, and LVs needs
to be done before installation using gdisk and the LVM tools in /sbin.
Then, the installer with manual partitioning can
As the OP, I want to try to clear up some of the confusion. I have
caused plenty of it. :-)
I drop-kicked the partitions I had set up and started over with a bare
(nothing but free space) sda block device. At some point I have
expressed doubt that my PC could handle UEFI correctly. This is not
tru
8 November and 12
December postings on account of his single multiboot project, beginning
"Debian 8 and Debian 9 Dual Boot" 12 Nov 2017 22:27:36 -0500
https://lists.debian.org/debian-user/2017/11/msg00443.html
then
"Installer Can Not Find Root" 18 Nov 2017 21:26:33 -0500 (GMT-
Le 07/12/2017 à 00:03, Felix Miata a écrit :
In the context of a GPT partitioned disk,
That context was missing from post you're complaining about.
That was your post, and it had plenty enough context :
- BIOS boot partition only exists in GPT
- type EE is used in GPT protective MBR
Anyw
On 12/05/17 15:18, Pascal Hambourg wrote:
Le 05/12/2017 à 06:55, David Christensen a écrit :
4. The firmware finds the first GPT partition and file system, which
look "right" for EFI boot images.
No.
5. The firmware reads this file system and finds only one file, which
it loads and runs (s
Pascal Hambourg composed on 2017-12-06 23:16 (UTC+0100):
> Felix Miata composed:
>> Nothing in that post makes it unambiguous that an MBR (MSDOS) partitioned
>> disk
>> was not the subject of discussion.
> In the context of a GPT partitioned disk,
That context w
Le 05/12/2017 à 03:33, Felix Miata a écrit :
Pascal Hambourg composed on 2017-12-05 00:41 (UTC+0100):
You're the only one bringing additional confusion.
Nobody but you talked about doing such a stupid thing as removing a type
ee partition. Dan and I only talked about removing the BIOS boot
part
Le 05/12/2017 à 06:55, David Christensen a écrit :
I wiped the SSD, ran d-i, and chose "Partitioning method" -> "Guided -
use entire disk and set up encrypted LVM", which produced:
LVM VG debian-vg, LV home - 3.5 GB Linux device-mapper (linear)
#1 3.5 GB f ext4
lest automagic partitioning and see what happens.
I don't know anything about UEFI firmware. I'm only just inheriting
a UEFI laptop with W10 on it and hope to split a partition for linux,
but I've only booted linux from a USB stick just to have a poke about.
The OP/Subject li
On 12/04/2017 12:17 AM, David Christensen wrote:
On 12/03/17 13:44, Dan Norton wrote:
On 12/02/2017 02:35 PM, David Christensen wrote:
I'm not making progress with this PC so I'll probably abandon GPT.
The disk is 1T and it was handled by the extended partition scheme
before this experiment an
On 12/04/17 17:34, David Christensen wrote:
That's why I plan to try again with the simplest automagic partitioning
and see what happens.
I wiped the SSD, ran d-i, and chose "Partitioning method" -> "Guided -
use entire disk and set up encrypted LVM", which produced:
LVM VG debian-vg
Pascal Hambourg composed on 2017-12-05 00:41 (UTC+0100):
> You're the only one bringing additional confusion.
> Nobody but you talked about doing such a stupid thing as removing a type
> ee partition. Dan and I only talked about removing the BIOS boot
> partition sda1.
In https://lists.debian.
On 12/04/17 07:21, David Wright wrote:
I recently reformatted a disk thus:
puck: GPT-style, master
Part # filesys sizecoderôle
puck- 1007KiB partition tables and alignment space
puck01 - 3MiBEF02bios-boot for Grub (bios
On 12/04/17 06:39, Dan Norton wrote:
On 12/04/2017 12:27 AM, David Christensen wrote:
Are there any other commands that readers might find interesting
(before I wipe the SSD)?
Just out of curiosity, lvdisplay?
# lvm lvdisplay
--- Logical volume ---
LV Path/dev/vg-stretch/
Le 04/12/2017 à 00:40, Felix Miata a écrit :
Pascal Hambourg composed on 2017-12-03 23:40 (UTC+0100):
...
Then, to proceed, remove /dev/sda1 partition followed by grub-install?
Removing the partition won't help. It is just useless, it does not harm.
If sda1 is a type EEh partition, doin
On Sun 03 Dec 2017 at 21:27:20 (-0800), David Christensen wrote:
> On 12/03/17 21:17, David Christensen wrote:
> >But, it was not a total loss -- I can now dissect the SSD.
>
> More info:
>
> # lsblk /dev/sda
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:00 14.9G 0 disk
> |-sda1
On 12/04/2017 12:27 AM, David Christensen wrote:
On 12/03/17 21:17, David Christensen wrote:
But, it was not a total loss -- I can now dissect the SSD.
More info:
# lsblk /dev/sda
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 14.9G 0 disk
|-sda1 8:1 0 953M 0 part
`-sda2
On 12/03/17 21:17, David Christensen wrote:
But, it was not a total loss -- I can now dissect the SSD.
More info:
# lsblk /dev/sda
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 14.9G 0 disk
|-sda1 8:10 953M 0 part
`-sda2 8:20 4.7G 0 part
# parted /dev/sda u s p
On 12/03/17 13:44, Dan Norton wrote:
On 12/02/2017 02:35 PM, David Christensen wrote:
I'm not making progress with this PC so I'll probably abandon GPT. The
disk is 1T and it was handled by the extended partition scheme before
this experiment and it probably can again. I still want to do LVM an
On 12/02/2017 02:35 PM, David Christensen wrote:
[...]
Where is /boot?
Possibly, this is a better answer:
$ df -Th
Filesystem Type Size Used Avail Use% Mounted on
[...]
/dev/sda1 vfat 992K 855K 138K 87% /boot/efi
/dev/mapper/debian8--vg-tmp
Pascal Hambourg composed on 2017-12-03 23:40 (UTC+0100):
...
>>> Then, to proceed, remove /dev/sda1 partition followed by grub-install?
> Removing the partition won't help. It is just useless, it does not harm.
>> If sda1 is a type EEh partition, doing that will probably dig your hole too
>> d
On 12/03/2017 02:04 PM, Felix Miata wrote:
Dan Norton composed on 2017-12-04 08:00 (UTC-0500):
Felix Miata wrote:
Dan Norton composed on 2017-12-03 16:44 (UTC-0500):
Note the above is currently from the future. Apparently the PC you are emailing
from is advanced one day.
Must be a result of m
Le 03/12/2017 à 22:51, Felix Miata a écrit :
Dan Norton composed on 2017-12-03 15:54 (UTC-0500):
Pascal Hambourg wrote:
Dan Norton composed:
Yes, no grub in mbr - unless installer insists.
Then what you wrote earlier was wrong : GRUB is not installed in
/dev/sda1, and this partition is
Dan Norton composed on 2017-12-03 15:54 (UTC-0500):
> Pascal Hambourg wrote:
>> Dan Norton composed:
>>> Yes, no grub in mbr - unless installer insists.
>> Then what you wrote earlier was wrong : GRUB is not installed in
>> /dev/sda1, and this partition is useless. As I wrote earlier, a BIOS
On 12/03/2017 02:16 PM, Pascal Hambourg wrote:
Le 04/12/2017 à 13:32, Dan Norton a écrit :
On 12/03/2017 06:49 AM, Felix Miata wrote:
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
Felix Miata composed:
...
So I guess that the OP means that the core image of GRUB is in
sda1, an
On 12/03/2017 01:04 PM, Felix Miata wrote:
Dan Norton composed on 2017-12-04 07:32 (UTC-0500):
Note your posts are still coming from the future. Today ATM in zone -0500 it
is
still the 3rd of December.
Felix Miata wrote:
I'm pretty sure that was not OP's intent, i.e., none of Grub at all i
Le 04/12/2017 à 13:32, Dan Norton a écrit :
On 12/03/2017 06:49 AM, Felix Miata wrote:
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
Felix Miata composed:
...
So I guess that the OP means that the core image of GRUB is in sda1, and
the boot image of GRUB is in the MBR of sda.
(.
Dan Norton composed on 2017-12-04 07:32 (UTC-0500):
Note your posts are still coming from the future. Today ATM in zone -0500 it is
still the 3rd of December.
> Felix Miata wrote:
>> I'm pretty sure that was not OP's intent, i.e., none of Grub at all in MBR.
> Yes, no grub in mbr - unless inst
On 12/03/2017 06:49 AM, Felix Miata wrote:
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
Felix Miata composed:
...
So I guess that the OP means that the core image of GRUB is in sda1, and
the boot image of GRUB is in the MBR of sda.
Based on OP's response to
https://lists.debi
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
> Felix Miata composed:
...
> So I guess that the OP means that the core image of GRUB is in sda1, and
> the boot image of GRUB is in the MBR of sda.
Based on OP's response to
https://lists.debian.org/debian-user/2017/11/msg00563.html
i
Le 02/12/2017 à 05:07, Dan Norton a écrit :
On 12/01/2017 08:54 PM, David Christensen wrote:
>
> # fdisk -t dos /dev/sda
Your original post indicated a GPT partition table. Forcing an MS-DOS
MBR partition type means the tool will be looking at fake information
that your GPT formatting tool
Le 03/12/2017 à 00:09, Felix Miata a écrit :
Michael Lange composed on 2017-12-02 22:33 (UTC+0100):
On Fri, 1 Dec 2017 23:07:15 -0500 Dan Norton wrote:
(...)
What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
where?
GRUB2 to sda1.
I did not read this thread in detail,
Michael Lange wrote:
> Windows is a pain in the neck of
> course, still booting a Live system and reinstalling grub from a chroot
> environment seems comparatively easy to me compared to the OP's
> troubles ;)
Agreed here and this is exactly what I do.
+ grub2 finds windows automatically and perh
th jessie installed. The
problem is it will not boot normally. Network booting has been
disabled in the NVRAM setup. After POST there is a one-liner which
says it can not find disk.
Please post the *exact* contents of the console screen.
ERROR:No boot disk has been detected or the disk has fai
On Sat, 2 Dec 2017 18:09:56 -0500
Felix Miata wrote:
> Michael Lange composed on 2017-12-02 22:33 (UTC+0100):
>
> > On Fri, 1 Dec 2017 23:07:15 -0500 Dan Norton wrote:
>
> > (...)
> >> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
> >> > where?
>
> >> GRUB2 to sda1.
>
>
Michael Lange composed on 2017-12-02 22:33 (UTC+0100):
> On Fri, 1 Dec 2017 23:07:15 -0500 Dan Norton wrote:
> (...)
>> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
>> > where?
>> GRUB2 to sda1.
> I did not read this thread in detail, so maybe this has already been
> dis
On Fri, 1 Dec 2017 23:07:15 -0500
Dan Norton wrote:
(...)
> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
> > where?
> >
>
>
> GRUB2 to sda1.
>
I did not read this thread in detail, so maybe this has already been
discussed, but I have just now been thinking, shouldn't g
normally. Network booting has been disabled in
the NVRAM setup. After POST there is a one-liner which says it can
not find disk.
Please post the *exact* contents of the console screen.
ERROR:No boot disk has been detected or the disk has failed.
It can be booted with a supergrub2 cd
Hi,
Dan Norton wrote:
> OK, the syslinux and syslinux-efi packages are now installed
SYSLINUX and GRUB are competitors (with GRUB winning the race on hard disk
but lagging behind on ISO 9660 for old BIOS).
I mentioned the SYSLINUX file "mbr.bin" (source: mbr.S) only to
substantiate my statement a
On 12/01/2017 02:58 PM, Thomas Schmitt wrote:
Hi,
Dan Norton wrote:
# fdisk -l
...
Disklabel type: gpt
In the dim past, fdisk
could set a partition as "active", which was its euphemism for "bootable".
I guess, this applies only to MBR partition tables, not to GPT as on your
disk.
As Pascal st
the NVRAM setup. After POST there is a one-liner which says it can
not find disk.
Please post the *exact* contents of the console screen.
ERROR:No boot disk has been detected or the disk has failed.
It can be booted with a supergrub2 cd, however.
# fdisk -l
Disk /dev/sda: 931.5 GiB
which says it can not find
disk.
Please post the *exact* contents of the console screen.
It can be booted with a supergrub2 cd, however.
# fdisk -l
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes
Dan Norton composed on 2017-12-01 16:23 (UTC-0500):
> The PC is simply not seeing the 1T sda, which is the only disk. It's not
> even getting as far as the mbr/grub. The PC appears to be no more than 5
> years old, based on the BIOS date, but it may be old enough to have a
> flaky UEFI. Should
On 12/01/2017 02:29 PM, Pascal Hambourg wrote:
Le 01/12/2017 à 19:57, Greg Wooledge a écrit :
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
Disklabel type: gpt
Apparently, BIOS does not see a bootable device. In the dim past, fdisk
could set a partition as "active", which was i
Hi,
Dan Norton wrote:
> # fdisk -l
> ...
> Disklabel type: gpt
> In the dim past, fdisk
> could set a partition as "active", which was its euphemism for "bootable".
I guess, this applies only to MBR partition tables, not to GPT as on your
disk.
As Pascal stated, there is a bit defined in GPT to
Le 01/12/2017 à 19:57, Greg Wooledge a écrit :
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
Disklabel type: gpt
Apparently, BIOS does not see a bootable device. In the dim past, fdisk
could set a partition as "active", which was its euphemism for "bootable".
However now:
GPT
On Fri, Dec 01, 2017 at 01:57:37PM -0500, Greg Wooledge wrote:
> On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
> > Disklabel type: gpt
>
> > Apparently, BIOS does not see a bootable device. In the dim past, fdisk
> > could set a partition as "active", which was its euphemism for "boo
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
> Disklabel type: gpt
> Apparently, BIOS does not see a bootable device. In the dim past, fdisk
> could set a partition as "active", which was its euphemism for "bootable".
> However now:
GPT disk labels don't have active/bootable partit
Maybe this is the wrong forum, but please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem is
it will not boot normally. Network booting has been disabled in the
NVRAM setup. After POST there is a one-liner which says it can not find
disk. It can
Dan Norton composed on 2017-11-22 19:09 (UTC-0500):
...
> 4. This laptop I'm borrowing is notorious for having a hyper-sensitive touch
> pad. You can be typing along in the spot you have chosen for input and
> suddenly
> it gets a wild hair and relocates the cursor to somewhere else. As a hunt and
-Original Message->From: mrma...@earthlink.net>Sent: Nov 21, 2017 3:37 PM>To: debian-user@lists.debian.org>Subject: Re: OT plain text missing from web mail (was: Installer Can Not Find Root">>Tom Furie composed:>>> On Mon, Nov 20, 2017 at 05:47:55
-Original Message-
>From: Tom Furie
>Sent: Nov 22, 2017 5:48 AM
>To: debian-user@lists.debian.org
>Subject: Re: Installer Can Not Find Root
>
>On Tue, Nov 21, 2017 at 09:28:55PM -0500, Dan Norton wrote:
>
>> > ...and all of Dan's mails to the list...
On Tue, Nov 21, 2017 at 09:28:55PM -0500, Dan Norton wrote:
> > ...and all of Dan's mails to the list...
> All? How far back?
That was my error, somehow my fingers typed "list" when my brain was
thinking "thread".
Cheers,
Tom
--
BOFH excuse #185:
system consumed all the paper for paging
si
On Tuesday 21 November 2017 21:28:55 Dan Norton wrote:
> -Original Message-
>
> >From: Tom Furie
> >Sent: Nov 21, 2017 3:25 AM
> >To: debian-user@lists.debian.org
> >Subject: Re: Installer Can Not Find Root
> >
> >On Mon, Nov 20, 2017 a
Dan Norton composed on 2017-11-21 21:28 (UTC-0500):
>>That's weird. The original mail, and all of Dan's mails to the list, have
>>only a single html part. An incredibly badly constructed html part at
>>that.
> All? How far back?
Just this thread (all written with Earthlink web mail), until this,
-Original Message-
>From: Tom Furie
>Sent: Nov 21, 2017 3:25 AM
>To: debian-user@lists.debian.org
>Subject: Re: Installer Can Not Find Root
>
>On Mon, Nov 20, 2017 at 05:47:55PM -0500, Cindy-Sue Causey wrote:
>
>> That's weird. I don't see that o
Tom Furie composed on 2017-11-22 01:05 (UTC):
> On Tue, Nov 21, 2017 at 03:37:03PM -0500, mrma...@earthlink.net wrote:
>> As this will be, it was sent using
>> X-Mailer: EarthLink Zoo Mail 1.0
>> with
>> Content-Type: text/html; charset=UTF-8
> You came through fine
On Tue, Nov 21, 2017 at 03:37:03PM -0500, mrma...@earthlink.net wrote:
> As this will be, it was sent using
>
> X-Mailer: EarthLink Zoo Mail 1.0
>
> with
>
> Content-Type: text/html; charset=UTF-8
You came through fine as text/plain. Shame about breaking the threadi
Tom Furie composed:
> On Mon, Nov 20, 2017 at 05:47:55PM -0500, Cindy-Sue Causey wrote:
>> That's weird. I don't see that on my end. The original email looks as
>> normally expected from Debian lists. :)
> That's weird. The original mail, and all of Dan's mails to the list, have
> only a single
On Mon, Nov 20, 2017 at 05:47:55PM -0500, Cindy-Sue Causey wrote:
> That's weird. I don't see that on my end. The original email looks as
> normally expected from Debian lists. :)
That's weird. The original mail, and all of Dan's mails to the list, have
only a single html part. An incredibly badl
-Original Message->From: Tom Dial >Sent: Nov 19, 2017 6:44 PM>To: "debian-user@lists.debian.org" >Subject: Re: Installer Can Not Find Root>>>>On 11/18/2017 07:26 PM, Dan Norton wrote:>> While trying to netinst Debian 8.9 into an LVM physical volume
On 11/20/17, Greg Wooledge wrote:
> On Mon, Nov 20, 2017 at 08:43:30AM -0500, Dan Norton wrote:
>>
On Mon, Nov 20, 2017 at 08:43:30AM -0500, Dan Norton wrote:
>
-Original Message->From: Pascal Hambourg >Sent: Nov 19, 2017 3:26 PM>To: "debian-user@lists.debian.org" >Subject: Re: Installer Can Not Find Root>>Le 19/11/2017 à 20:02, Dan Norton a écrit :>>-Original Message->>>From: Pascal Hambourg&
On 11/18/2017 07:26 PM, Dan Norton wrote:
> While trying to netinst Debian 8.9 into an LVM physical volume I keep
> running into "installer can not find root" or words to that effect. This
> is a dead end in the installer AFAICT.
>
> I have tried GPT but this HP UEFI
Le 19/11/2017 à 20:02, Dan Norton a écrit :
-Original Message-
From: Pascal Hambourg
Sent: Nov 19, 2017 11:03 AM
To: "debian-user@lists.debian.org"
Subject: Re: Installer Can Not Find Root
Le 19/11/2017 à 03:26, Dan Norton a écrit :
user@debian:/$ sudo mount /dev/debi
-Original Message->From: Pascal Hambourg >Sent: Nov 19, 2017 11:03 AM>To: "debian-user@lists.debian.org" >Subject: Re: Installer Can Not Find Root>>Le 19/11/2017 à 03:26, Dan Norton a écrit :>> >> Using LVM, one physical volume is defined on the
Le 19/11/2017 à 03:26, Dan Norton a écrit :
Using LVM, one physical volume is defined on the entire sda5 partition. A volume
group named "debian8-vg" is defined as the only vg in that pv. Five logical
volumes have been defined in the vg. One lv intended as root was defined like
this with a Debia
While trying to netinst Debian 8.9 into an LVM physical volume I keep running into "installer can not find root" or words to that effect. This is a dead end in the installer AFAICT.I have tried GPT but this HP UEFI does not play nicely with it. So, reverting to Disklabel type: dos, and u
t time.
>
> Thanks you all for taking time and helping me to find out the root
> casue for a debian package which exists in cdrom and its index i.e.
> 'Package & Package.gz', but 'apt-get install MYPACAKGE'
> can not find this package in index resulting in
casue for a debian package which exists in cdrom and its index i.e.
'Package & Package.gz', but 'apt-get install MYPACAKGE'
can not find this package in index resulting in not installing it into
the system.
I want to let this list know that if size of debian package which is
le
On Wed, Apr 3, 2013 at 7:33 PM, Wayne Topa wrote:
> On 04/03/2013 06:22 AM, Ravi Roy wrote:
>
> Have you tried "sudo dpkg -i /media/cdrom/MYPACKAGE"
>
Yes, using "sudo dpkg -i /media/cdrom/MYPACKAGE" install the package
perfectly in the system.
This is very strange behaviour I have observed firs
On 04/03/2013 06:22 AM, Ravi Roy wrote:
On Wed, Apr 3, 2013 at 3:31 PM, Mihamina Rakotomandimby
wrote:
What is in your /etc/apt/sources.list?
I have only cdrom entry in /etc/apt/sources.list
deb cdrom:[my product installation cd]/ squeeze main
I can mount this cd perfectly using "$ sudo
On Wed, Apr 3, 2013 at 3:31 PM, Mihamina Rakotomandimby
wrote:
> What is in your /etc/apt/sources.list?
>
I have only cdrom entry in /etc/apt/sources.list
deb cdrom:[my product installation cd]/ squeeze main
I can mount this cd perfectly using "$ sudo apt-cdrom add" and I can
see cdrom content
On 2013-04-03 13:00, Ravi Roy wrote:
I verfied it and it is available in cdrom; I'm using apt and apt-utils
versions 0.8.10.3.
It would be helpful if somebody can point to a direction which may
help to resolve this issue.
What is in your /etc/apt/sources.list?
--
RMA.
--
To UNSUBSCRIBE, emai
1 - 100 of 131 matches
Mail list logo
