Re: When/how/why to use "sudo", "su" or "su -" -- was [Re: rocks n diamonds]

[rhkramer]

On Saturday, September 14, 2019 03:48:40 AM Joe wrote:
> On Fri, 13 Sep 2019 21:20:18 -0500
> 
> John Hasler  wrote:
> > rhkramer writes:
> > > When I used Windows, it was not multiuser.
> > 
> > Which version? Win95 was MSDOS with a GUI stuck on with bubblegum.
> 
> Windows 1, 2, 3, 95, 98 and Me didn't have file permissions. Every other
> version had, though in the home versions it was generally hidden, and
> they couldn't join domains.

Following up on my earlier reply, the first Windows I used to any extent was 
3(.1).  I might have had an earlier version of Windows, and might have 
experimented with it, but not very much.  Essentially, the last version of 
Windows I used was 95, although I've had some exposure to later versions by 
helping other people with problems.

Oh, I guess I have a much more modern version of Windows on a used laptop I 
bought -- I think it might have even been upgraded to Windows 10.  I keep it 
around because I need Windows to update the map in my Garming GPS -- I haven't 
done that in probably 5 years or longer and I need to do it.

Re: Re: Buster installer sets fs_passno 1 for /boot/efi in /etc/fstab

[Nicholas A Fleisher]

> https://www.freedesktop.org/software/systemd/man/systemd-fstab-generator.html
> 
>  The passno field is treated like a simple boolean, and the ordering 
> information
>  is discarded. However, if the root file system is checked, it is checked 
> before
>  all the other file systems.
> 
> So apparently it's indifferent whether the fstab sixth field contains a 1 or a
> 2 in the world of systemd.

Aha, thanks! I can confirm that things work just fine after changing it
manually to 2.

Re: black screen (only mouse visible) after resume with xfce4 on kernel 5.2.0

[Mike Kupfer]

Andrea Borgia wrote:

> how do I get xfce to use xscreensaver as
> locking when suspending?

For Xfce4 4.12, it's on the Advanced tab of the Session and Startup
settings.

mike

Donación por Brave

[Carlos Cosio]

Buenas tardes, a quien corresponda:

El motivo del correo es porque me encanta el desarrollo y el funcionamiento
de este gran proyecto.

Me gustaría aportar una idea sobre las donaciones que se pueden hacer, y
creo que deberían integrar el sistema de donaciones a través de
criptomonedas ya que es más fácil y genera un poco de mayor seguridad para
los interesados. Pueden inclusive agregar la página al canal de Brave para
hacerlo aún más fácil.

No sé si este sea el correo indicado para hacer llegar esta información o
si se por favor me pueden indicar cuál sería?

Por su atención gracias.

Re: Installation problem

[Felix Miata]

Thomas D Dial composed on 2019-09-14 13:30 (UTC-0600):

> As a first "next step" I suggest the following:

> When you see the "Debian page" - that is the Grub boot menu - press the
> 'e' key. This will present the boot control instructions for the default
> boot into your Linux in a form you can edit using the arrow keys to move
> the cursor, backspace to erase, and normal keys to add things.

> Locate the line beginning "linux." This probably has the word "quiet" at
> or near the end, which prevents display of normal boot messages that do
> not report serious problems; erase it and press control-x or the F10 key
> to continue the boot.

> You should see messages as the system boots and initializes Linux. The
> last of them are likely to provide information about the reason the
> system initialization does not complete. They may be self explanatory,
> but if not, you can post them here and they may help others to provide
> additional assistance.

As a second step, if above seems minimally or un- helpful, after removing quiet,
append a space, then the string

nomodeset

which is primarily a troubleshooting parameter, also for enabling repairs,
explained among other places at:

-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Installation problem

[Thomas D Dial]

On Sat, 2019-09-14 at 08:46 +0200, john doe wrote:
> On 9/14/2019 7:36 AM, David Christensen wrote:
> > On 9/13/19 4:45 PM, Anne wrote:
> > > Hi, I am new to debian and I can not seem to get the OS installed
> > > properly.
> > > 
> > > What I have done so far is to
> > > 
> > > Make a free space partition of 100GB on drive D and then
> > > 
> > > 1. download the first DVD of 10.1.0
> > > 2. used rufus to put it on a thumb drive
> > > 3. Booted from the thumb drive and selected "graphical Install"
> > > 4. followed the prompts
> > > 5. Program said OS was installed and to reboot the system
> > > 6. reboot
> > > 7. Debian page showed up and I selected the first selection.
> > > 8. after a bit of doing things I get a black screen with a small
> > > cursor in the upper left of the screen
> > > 9. a power off or ctrl alt del is required to go further.
> > > 10. after reboot I get the Debian screen and select windows and I
> > > am
> > > up and running again.
> > > 
> > > I have done this three times
> > > 
> > > Twice with the DVD debian-10.1.0-amd64-DVD-1.iso
> > > and once with the DVD firmware-10.1.0-amd64-DVD-1.iso
> > > 
> > > results were the same each time...
> > > 
> > > What am I doing wrong???
> > 
> > You are headed down the path of "dual boot", which is unnecessarily
> > difficult and risks damaging your Windows installation.
> > 
> > 
> > If you have a Windows computer and you want to experiment with GNU/
> > Linux , you are better off installing virtual machine hosting
> > software
> > and downloading a pre-built virtual machine.  Obvious choices
> > include
> > Microsoft Hyper-V, Oracle VirtualBox, and VMware Workstation Player:
> > 
> > https://docs.microsoft.com/en-us/virtualization/
> > 
> > https://www.virtualbox.org/
> > 
> > https://www.vmware.com/
> > 
> 
> https://qemu.org
> 
> Given that you didn't crash your system with multiboot and that you
> see
> the prompt to select which OS to choose, I would keep the multiboot
> going.
> 
> Have you turned off fastboot on windows?
> 
> You shouldn't see D on Windows but somespace that Windows can't use.

Welcome to Debian. I suspect your installation, from either of the
sources you mention, is salvageable. And I think the advice here from
john doe is a good continuation point; it appears you have succeeded in
building a very nearly successful Windows/Linux dual boot setup.

As a first "next step" I suggest the following:

When you see the "Debian page" - that is the Grub boot menu - press the
'e' key. This will present the boot control instructions for the default
boot into your Linux in a form you can edit using the arrow keys to move
the cursor, backspace to erase, and normal keys to add things.

Locate the line beginning "linux." This probably has the word "quiet" at
or near the end, which prevents display of normal boot messages that do
not report serious problems; erase it and press control-x or the F10 key
to continue the boot.

You should see messages as the system boots and initializes Linux. The
last of them are likely to provide information about the reason the
system initialization does not complete. They may be self explanatory,
but if not, you can post them here and they may help others to provide
additional assistance.

Regards,
Tom Dial
 
> 
> --
> John Doe

Re: update and upgrade file size problems

[The Wanderer]

On 2019-09-14 at 14:50, Ryan Dean wrote:

> On Sat, Sep 14, 2019 at 8:57 PM The Wanderer  wrote:
> 
>> On 2019-09-14 at 13:26, Ryan Dean wrote:
>>
>> > I have problems with update and upgrade with several packages since
>> > buster 10.1 new release on September 7th. Even with apt-get upgrade
>> > --fix-missing, still does not work It always says File has unexpected
>> > size (3108672 != 3134284). Below is the logs, any ideas how to solve
>> > it?
>>
>> For what it's worth, that .deb file exists in my system's APT package
>> cache with size 3108672, and I've never seen this error.
>>
>> Does that file exist in the cache on your system? If so, what size is it?
>>
>> You can check with:
>>
>> ls -l /var/cache/apt/archives/gdb_8.2.1-2+b1_amd64.deb
>>
>> If it doesn't exist, my initial guess is that the APT archive mirror
>> which deb.debian.org is currently pointing you at has a corrupt copy of
>> that file. You could try using a different mirror in your sources.list;
>> mine is configured with ftp.us.debian.org,
> 
> Can you write the exact url of the mirror in the source list, eg deb
> ftp.us.debian.org or deb-src https://ftp.us.debian.org buster main
> contribute non-free etc so that I can copy and paste to my source file?

I don't use lines which target buster by that name; instead, I use lines
which target stable and testing explicitly, so that they shift whenever
a new release is made. As a result, just sharing the lines from my own
sources.list won't give you what you probably want.

That said, the relevant pair of lines with that substitution made would
probably be:

deb http://ftp.us.debian.org/debian/ buster main contrib non-free
deb-src http://ftp.us.debian.org/debian/ buster main contrib non-free

and you can of course drop contrib and/or non-free as you see fit.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: update and upgrade file size problems

[Ryan Dean]

On Sat, Sep 14, 2019 at 8:57 PM The Wanderer  wrote:

> On 2019-09-14 at 13:26, Ryan Dean wrote:
>
> > I have problems with update and upgrade with several packages since
> > buster 10.1 new release on September 7th. Even with apt-get upgrade
> > --fix-missing, still does not work It always says File has unexpected
> > size (3108672 != 3134284). Below is the logs, any ideas how to solve
> > it?
>
> For what it's worth, that .deb file exists in my system's APT package
> cache with size 3108672, and I've never seen this error.
>
> Does that file exist in the cache on your system? If so, what size is it?
>
> You can check with:
>
> ls -l /var/cache/apt/archives/gdb_8.2.1-2+b1_amd64.deb
>
> If it doesn't exist, my initial guess is that the APT archive mirror
> which deb.debian.org is currently pointing you at has a corrupt copy of
> that file. You could try using a different mirror in your sources.list;
> mine is configured with ftp.us.debian.org,


Can you write the exact url of the mirror in the source list, eg deb
ftp.us.debian.org or deb-src https://ftp.us.debian.org buster main
contribute non-free etc so that I can copy and paste to my source file?

With only ftp.us.debian.org, it seems the source list and apt gives me
error.

The problems with debian is that if there is one letter missing in the url
source list, the source list and apt will not work at all and debian does
not put the precise url on its website for me to  copy and paste.

Thanks.



> and as I said, I didn't have
> this problem.
>
> --
>The Wanderer
>
> The reasonable man adapts himself to the world; the unreasonable one
> persists in trying to adapt the world to himself. Therefore all
> progress depends on the unreasonable man. -- George Bernard Shaw
>
>

Re: update and upgrade file size problems

[The Wanderer]

On 2019-09-14 at 13:26, Ryan Dean wrote:

> I have problems with update and upgrade with several packages since
> buster 10.1 new release on September 7th. Even with apt-get upgrade
> --fix-missing, still does not work It always says File has unexpected
> size (3108672 != 3134284). Below is the logs, any ideas how to solve
> it?

For what it's worth, that .deb file exists in my system's APT package
cache with size 3108672, and I've never seen this error.

Does that file exist in the cache on your system? If so, what size is it?

You can check with:

ls -l /var/cache/apt/archives/gdb_8.2.1-2+b1_amd64.deb

If it doesn't exist, my initial guess is that the APT archive mirror
which deb.debian.org is currently pointing you at has a corrupt copy of
that file. You could try using a different mirror in your sources.list;
mine is configured with ftp.us.debian.org, and as I said, I didn't have
this problem.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

update and upgrade file size problems

[Ryan Dean]

I have problems with update and upgrade with several packages since buster
10.1 new release on September 7th. Even with apt-get upgrade --fix-missing,
still does not work It always says File has unexpected size (3108672 !=
3134284). Below is the logs, any ideas how to solve it?

The following packages will be upgraded:
  gdb
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,134 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian buster/main amd64 gdb amd64 8.2.1-2+b1
[3,134 kB]
Err:1 http://deb.debian.org/debian buster/main amd64 gdb amd64 8.2.1-2+b1
  File has unexpected size (3108672 != 3134284). Mirror sync in progress?
[IP: 151.101.244.204 80]
  Hashes of expected file:
   - SHA256:8085c893f3b15a7802a47afb3f9cf819c223624d2bac894a8be5884eb8771ac1
   - MD5Sum:27ac5ace5fed107805cd914bec5a8cd8 [weak]
   - Filesize:3134284 [weak]
E: Failed to fetch
http://deb.debian.org/debian/pool/main/g/gdb/gdb_8.2.1-2+b1_amd64.deb  File
has unexpected size (3108672 != 3134284). Mirror sync in progress? [IP:
151.101.244.204 80]
   Hashes of expected file:
-
SHA256:8085c893f3b15a7802a47afb3f9cf819c223624d2bac894a8be5884eb8771ac1
- MD5Sum:27ac5ace5fed107805cd914bec5a8cd8 [weak]
- Filesize:3134284 [weak]

Re: black screen (only mouse visible) after resume with xfce4 on kernel 5.2.0

[Andrea Borgia]

Hello, Christopher.



If this is the same problem I had (and discussed prior on this list),
there is a bug in light-locker that seems to cause this behavior
randomly even without hibernation.  Consider switching from light-locker
to xscreensaver; this resolved the problem for me.


Thing is, I never ever have any problem if I lock the screen but do not 
suspend, though. Anyhow, how do I get xfce to use xscreensaver as locking when 
suspending?




See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913062


Killing light-locker gets me absolutely nowhere when it happens, I had 
already tried it :(



Andrea.

Re: When/how/why to use "sudo", "su" or "su -" -- was [Re: rocks n diamonds]

[Andy Smith]

Hello,

On Fri, Sep 13, 2019 at 06:57:11AM -0500, Richard Owlett wrote:
> I think what is needed is an essay comparing/contrasting the proper usage of
> "sudo" versus "su" versus "su -". It should also include a discussion of the
> change from "su" to "su -".

A lot has already been written about the change of "su" program in
Debian and it's difficult to see how writing one more page will help
anyone. The information is there for anyone to find, if they know
they need to look.

I think that's the problem here: those stumbling over issues with
changed "su" behaviour are already used to the old behaviour of
"su", so when they type something like:

$ su
# some-admin-command

and get back a message that "some-admin-command" can't be found,
they do not immediately think, "what can be wrong with my usage of
su?" Instead they think, "what can be wrong with my install of
some-admin-command?" hence threads like these. They feel they are
comfortable with their use of "su" because it's worked for them so
many times before. It's the new "some-admin-command" that must be
messed up.

So in fact the problem is harder than education because it is
actually re-education.

Over time, the "new" behaviour of "su" (which is now consistent with
the behaviour of "su" on most other Linux distributions) will
implant itself as the only known behaviour for "su" users, so these
problems should reduce.

As for "su" vs "sudo", it is a debate that has raged amongst small
factions for years and I don't see it as possible to objectively
make recommendations as to which is best and when, as it is all
personal preference. Whatever "recommendation" one would make, there
are going to be plenty of people who will pop up to say that is an
anti-recommendation.

You could try to just describe their functionality in contrast to
each other, but it's been done so many times already. Type
"difference between su and sudo" in your favourite search engine and
there are pages and pages of results.

It is probably some sort of failure that a GUI application needs the
user to do anything at all with "su" or "sudo" or anything at a
shell prompt. Although I would never want to give up use of the
shell prompt, it is a steep learning curve for the new user, who
just wants to install and play a game.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Buster installer sets fs_passno 1 for /boot/efi in /etc/fstab

[Curt]

On 2019-09-14, Nicholas A Fleisher  wrote:

> In the /etc/fstab written by the installer, the sixth field of the
> /boot/efi line has the value "1". My understanding is that only 
> the root
> partition should have this value (and it does in this case; the
> installer wrote two lines in /etc/fstab where the sixth field has 
> the
> value "1").
>

https://www.freedesktop.org/software/systemd/man/systemd-fstab-generator.html

 The passno field is treated like a simple boolean, and the ordering information
 is discarded. However, if the root file system is checked, it is checked before
 all the other file systems.

So apparently it's indifferent whether the fstab sixth field contains a 1 or a
2 in the world of systemd.

-- 
Thug: This is a stickup! Now come on. Your money or your life.
[long pause]
Thug: [repeating] Look, bud, I said, 'Your money or your life.'
Jack Benny: I'm thinking, I'm thinking!

UUID PARTUUID

[Jordi]

Bon dia. Des que vaig instal·lar el Buster, tinc alguns problemes per
encriptar la swap. Després de configurar tot i funcionar correctament,
quan reinicio l'ordinador sembla que el UUID de la swap es perd i
canvia, amb la qual cosa em quedo sense swap i em surt el "Gave up
waiting for suspend/resume device".  

He desfet i refet els canvis unes quantes vegades. Per ara sembla que
funciona només ficant el nom del dispositiu /dev/sdXX a /etc/crypttab i
a /etc/initramfs-tools/conf.d/resume de la següent forma:

/etc/fstab : /dev/mapper/cryptswap none swap sw 0 0

/etc/crypttab : cryptswap /dev/sda8 /dev/urandom swap

/etc/initramfs-tools/conf.d/resume : RESUME=/dev/sda8

Si hi fico el UUID, no funciona. Si no encripto la swap, funciona tot
be amb la UUID.

Fent sudo blkid :
/dev/mapper/cryptswap: UUID="d832f5be-0915-486b-8725-xxx"
TYPE="swap"
/dev/sda8: PARTUUID="000b0989-08"
On veiem dues entrades per la swap, la UUID de la primera no és la
mateixa que vaig configurar i a /dev/sda8 no surt la UUID, a totes les
altres /dev/sdXX surt PARTUUID i UUID

Salutacions

Jordi.

Re: Buster installer sets fs_passno 1 for /boot/efi in /etc/fstab

[Sven Joachim]

On 2019-09-14 04:32 +, Nicholas A Fleisher wrote:

> In the /etc/fstab written by the installer, the sixth field of the
> /boot/efi line has the value "1". My understanding is that only the
> root partition should have this value (and it does in this case; the
> installer wrote two lines in /etc/fstab where the sixth field has the
> value "1").

That's documented in fstab(5), indeed.

> Is this intended behavior, or is this a bug in the installer? If it's
> a bug, where is the right place to report it to? (I'm not sure which
> package(s) are involved)

It is partman-efi[1].  Don't know if there is any particular reason why
they chose a pass value of 1 rather than 2, but it does not seem to
cause actual problems.

Cheers,
   Sven


1. 
https://salsa.debian.org/installer-team/partman-efi/blob/master/fstab.d/efi#L26

Re: Installation problem

[Esteban L]

What Video card do you have?

I experienced annoyance with AMD video card/driver. If that is the case,
you can search on google, or ask the mailling list again for how to
install the required firmware.

Unfortunately, it is not smooth.

On 14.09.19 01:45, Anne wrote:
>
> Hi, I am new to debian and I can not seem to get the OS installed
> properly.
>
> What I have done so far is to
>
> Make a free space partition of 100GB on drive D and then
>
> 1. download the first DVD of 10.1.0
> 2. used rufus to put it on a thumb drive
> 3. Booted from the thumb drive and selected "graphical Install"
> 4. followed the prompts
> 5. Program said OS was installed and to reboot the system
> 6. reboot
> 7. Debian page showed up and I selected the first selection.
> 8. after a bit of doing things I get a black screen with a small
> cursor in the upper left of the screen
> 9. a power off or ctrl alt del is required to go further.
> 10. after reboot I get the Debian screen and select windows and I am
> up and running again.
>
> I have done this three times
>
> Twice with the DVD  debian-10.1.0-amd64-DVD-1.iso
> and once with the DVD firmware-10.1.0-amd64-DVD-1.iso
>
> results were the same each time...
>
> What am I doing wrong???
>
> Anne
>

Trobada tècnica dissabte 21

[Aniol Marti]

Bon dia,

Aprofitant que dissabte que ve (21 de setembre) a la tarda se celebra el
DLP [0] al centre la Violeta a Gràcia hem dit de fer una jornada tècnica
al matí al bar de la Violeta. El pla seria treballar de 10 a 13 i
llavors anar a dinar per allà. He preparat un Dudle [1] per apuntar-se.


[0]: https://caliu.cat/blog/2019/06/26/dlp-2019/
[1]: https://dudle.inf.tu-dresden.de/p_H2LdNOSA/


Salut!

-- 
Aniol Martí gpg C6F0514F
www.aniolmarti.cat
__
P Please consider the environment before printing this email.

Buster installer sets fs_passno 1 for /boot/efi in /etc/fstab

[Nicholas A Fleisher]

I've just installed Buster using the installer's guided 
partitioning and
noticed a possible error in the resulting /etc/fstab.

Under guided partitioning, I chose the option to use the whole 
disk with
LVM on LUKS. Apart from the LUKS partition and the LVs inside it, 
the
installer created an ext2 /boot partition and a vfat /boot/efi 
partition
(this is a UEFI laptop).

In the /etc/fstab written by the installer, the sixth field of the
/boot/efi line has the value "1". My understanding is that only 
the root
partition should have this value (and it does in this case; the
installer wrote two lines in /etc/fstab where the sixth field has 
the
value "1").

Is this intended behavior, or is this a bug in the installer? If 
it's a
bug, where is the right place to report it to? (I'm not sure which
package(s) are involved)

Thanks,
Nick

Re: Installation problem

[Joe]

On Fri, 13 Sep 2019 22:36:06 -0700
David Christensen  wrote:

> On 9/13/19 4:45 PM, Anne wrote:
> > Hi, I am new to debian and I can not seem to get the OS installed
> > properly.
> > 
> > What I have done so far is to
> > 
> > Make a free space partition of 100GB on drive D and then
> > 
> > 1. download the first DVD of 10.1.0
> > 2. used rufus to put it on a thumb drive
> > 3. Booted from the thumb drive and selected "graphical Install"
> > 4. followed the prompts
> > 5. Program said OS was installed and to reboot the system
> > 6. reboot
> > 7. Debian page showed up and I selected the first selection.
> > 8. after a bit of doing things I get a black screen with a small
> > cursor in the upper left of the screen
> > 9. a power off or ctrl alt del is required to go further.
> > 10. after reboot I get the Debian screen and select windows and I
> > am up and running again.
> > 
> > I have done this three times
> > 
> > Twice with the DVD debian-10.1.0-amd64-DVD-1.iso
> > and once with the DVD firmware-10.1.0-amd64-DVD-1.iso
> > 
> > results were the same each time...
> > 
> > What am I doing wrong???  
> 
> You are headed down the path of "dual boot", which is unnecessarily 
> difficult and risks damaging your Windows installation.
> 

Doesn't have to be. I bought a Win10 netbook last year, with no legacy
BIOS option, and stretch installed on it on a second drive without a
problem. I hadn't actually intended to use it dual-boot, but I found
that the grub menu contained a Windows entry, and it worked easily.

> 
> If you have a Windows computer and you want to experiment with GNU/ 
> Linux , you are better off installing virtual machine hosting
> software and downloading a pre-built virtual machine.  Obvious
> choices include Microsoft Hyper-V, Oracle VirtualBox, and VMware
> Workstation Player:
> 
> https://docs.microsoft.com/en-us/virtualization/
> 
> https://www.virtualbox.org/
> 
> https://www.vmware.com/

What I'd suggest first is trying a live version of Debian, perhaps
Knoppix https://www.knopper.net/knoppix/index-en.html and preferably
also straight Debian, to see if there are any hardware issues. Doing a
graphical install does not guarantee that the graphics drivers in the
installed Debian will work, I've had trouble in that area.

-- 
Joe

Re: When/how/why to use "sudo", "su" or "su -" -- was [Re: rocks n diamonds]

[Joe]

On Fri, 13 Sep 2019 21:20:18 -0500
John Hasler  wrote:

> rhkramer writes:
> > When I used Windows, it was not multiuser.  
> 
> Which version? Win95 was MSDOS with a GUI stuck on with bubblegum. 

Windows 1, 2, 3, 95, 98 and Me didn't have file permissions. Every other
version had, though in the home versions it was generally hidden, and
they couldn't join domains.

-- 
Joe

Re: Installation problem

[john doe]

On 9/14/2019 7:36 AM, David Christensen wrote:
> On 9/13/19 4:45 PM, Anne wrote:
>> Hi, I am new to debian and I can not seem to get the OS installed
>> properly.
>>
>> What I have done so far is to
>>
>> Make a free space partition of 100GB on drive D and then
>>
>> 1. download the first DVD of 10.1.0
>> 2. used rufus to put it on a thumb drive
>> 3. Booted from the thumb drive and selected "graphical Install"
>> 4. followed the prompts
>> 5. Program said OS was installed and to reboot the system
>> 6. reboot
>> 7. Debian page showed up and I selected the first selection.
>> 8. after a bit of doing things I get a black screen with a small
>> cursor in the upper left of the screen
>> 9. a power off or ctrl alt del is required to go further.
>> 10. after reboot I get the Debian screen and select windows and I am
>> up and running again.
>>
>> I have done this three times
>>
>> Twice with the DVD debian-10.1.0-amd64-DVD-1.iso
>> and once with the DVD firmware-10.1.0-amd64-DVD-1.iso
>>
>> results were the same each time...
>>
>> What am I doing wrong???
>
> You are headed down the path of "dual boot", which is unnecessarily
> difficult and risks damaging your Windows installation.
>
>
> If you have a Windows computer and you want to experiment with GNU/
> Linux , you are better off installing virtual machine hosting software
> and downloading a pre-built virtual machine.  Obvious choices include
> Microsoft Hyper-V, Oracle VirtualBox, and VMware Workstation Player:
>
> https://docs.microsoft.com/en-us/virtualization/
>
> https://www.virtualbox.org/
>
> https://www.vmware.com/
>

https://qemu.org

Given that you didn't crash your system with multiboot and that you see
the prompt to select which OS to choose, I would keep the multiboot going.

Have you turned off fastboot on windows?

You shouldn't see D on Windows but somespace that Windows can't use.

--
John Doe

Re: Installation problem

[Joao Emanuel]

Hi, first sorry for horrible english, well try to turn off secure boot in
bios and try again to install Debian. Or like David suggestion, get
virtualbox or enable hyper-v and install in virtual machine.

Em sex, 13 de set de 2019 às 19:54, Anne  escreveu:

> Hi, I am new to debian and I can not seem to get the OS installed properly.
>
> What I have done so far is to
>
> Make a free space partition of 100GB on drive D and then
>
> 1. download the first DVD of 10.1.0
> 2. used rufus to put it on a thumb drive
> 3. Booted from the thumb drive and selected "graphical Install"
> 4. followed the prompts
> 5. Program said OS was installed and to reboot the system
> 6. reboot
> 7. Debian page showed up and I selected the first selection.
> 8. after a bit of doing things I get a black screen with a small cursor in
> the upper left of the screen
> 9. a power off or ctrl alt del is required to go further.
> 10. after reboot I get the Debian screen and select windows and I am up
> and running again.
>
> I have done this three times
>
> Twice with the DVD  debian-10.1.0-amd64-DVD-1.iso
> and once with the DVD firmware-10.1.0-amd64-DVD-1.iso
>
> results were the same each time...
>
> What am I doing wrong???
>
> Anne
>


-- 

Muito obrigado antecipadamente pela atenção prestada a esta mensagem.

--

{}s

Joao Emanuel