Re: broadcast error messages, unofficial Debian 12

[Alan Corey]

Thank you, I'd never heard of Zutty before this Debian turned up using it
as a default terminal.  Normally I use rxvt, on trying harder rxvt and
xterm both installed and don't seem to have the problem.  At first I
thought I was running under Wayland so I was maybe stuck with Zutty.  But
there's no Wayland either, at least by default.

Anyway this Debian 12 doesn't seem too bad, you just need to turn off
(unblock all) rfkill everytime you boot it.

On Wed, Dec 13, 2023 at 7:08 PM Andy Smith  wrote:

> Hi Alan,
>
> debian-devel is for discussion of the development of debian. Your
> query appears to be user support, which takes place on debian-user.
> I've set Reply-To: debian-user.
>
> On Wed, Dec 13, 2023 at 02:52:11PM -0500, Alan Corey wrote:
> > I can have 2 or more Zutty terminal windows running to work on a
> > program. When I get a compiling error in one terminal it gets
> > broadcast to both windows.
> >
> > This particular error is not anything in my code, I don't recognize any
> of
> > it, but it shows up because I had a warning in my stuff:
> >
> >  W [main.cc:1161] (Unimplemented) unhandled OSC: '8;;
> >
> https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wunused-but-set-variable
> > '
> > W [main.cc:1161] (Unimplemented) unhandled OSC: '8;;'
>
> I'm not familiar with Zutty but this message appears to come from
> your terminal, Zutty, which also explains why it appears in all of
> your terminal windows.
>
> An example of suxh a Zutty diagnostic is here:
>
> https://github.com/tomscii/zutty/issues/43
>
> though it is not your specific one.
>
> So, you probably want to seek support from Zutty, e.g. at their
> github issues.
>
> Thanks,
> Andy
>
> --
> https://bitfolk.com/ -- No-nonsense VPS hosting
>


-- 
-
Education is contagious.

Debian versions

[Alan Serrano Peña]

Good afternoon, I have a question about Debian versions. Is there a commercial 
version of Debian? Any version with technical support? I was reading on the 
website that there is a version called Debian LTS, specifically Debian 10 
"Buster," but I'm not sure if this version meets what I'm asking for. I hope 
you can help me or even explain a little more about LTS and the "Buster" 
version.
 
I hope you can assist me as I don't have much knowledge about this operating 
system
 

Installation problem

[Alan Glasser]

I am trying to install Buster on an old 386.
I burned the three full DVDs.
I boot the first DVD and it gets to the point of asking about additional
cds/dvds.
I push the eject button on my dvd drive and nothing happens.  I try to do a
forced eject
with a paperclip, but that doesn't work either.  I click "No" as I can't
eject the DVD.
Nothing happens.

This is repeatable on my machine.
Three times; same behavior.

Any ideas?

Thanks for your help.

Alan Glasser

SRT-tools version upgrade

[Alan Latteri]

Hello,

I request that set-tools be upgraded to the latest version, 1.4.2.

Thanks,
Alan

Re: Nasıl php yükleyebilirim

[Seçkin Alan]

Bu tarz mailler atmadan önce detay içeren bilgileri ekler misin?

Ne hatası aldın nasıl denedin?

On Monday, July 27, 2020, İbrahim Alses  wrote:

> Gnuroot debian indirdim ve php'yi yukleyemedim yardımcı olur musunuz
>


-- 
Seçkin ALAN
http://seckinalan.net.tr

Re: network-manager takes 1-4 restarts in order to recognize and connect to already-configured wifi network, USB dongle NIC

[Alan Tu]

I do not have any other interfaces in /etc/network/interfaces, besides lo.

Thanks for the tip about systemctl -l status network-manager. There is a 
difference.

I ran systemctl -l status network-manager on two boots. In both cases, the USB 
dongle was already plugged in and was not touched. The first boot, I logged 
into Mate, and the wifi connected automatically:
● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Sat 2020-03-28 13:40:43 PDT; 8min ago
   Docs: man:NetworkManager(8)
   Main PID: 584 (NetworkManager)
  Tasks: 4 (limit: 19014)
 Memory: 16.4M
 CGroup: /system.slice/NetworkManager.service
 └─584 /usr/sbin/NetworkManager --no-daemon

Mar 28 13:41:10 raptor NetworkManager[584]:   [1585428070.4504] manager: 
NetworkManager state is now CONNECTED_LOCAL
Mar 28 13:41:10 raptor NetworkManager[584]:   [1585428070.4514] manager: 
NetworkManager state is now CONNECTED_SITE
Mar 28 13:41:10 raptor NetworkManager[584]:   [1585428070.4515] policy: 
set 'wln' (wlx1831bf53a3a2) as default for IPv4 routing and DNS
Mar 28 13:41:10 raptor NetworkManager[584]:   [1585428070.4561] device 
(wlx1831bf53a3a2): Activation: successful, device activated.
...

Now the boot where network-manager repeatedly asked for the same password:
● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Sat 2020-03-28 13:52:45 PDT; 36s ago
   Docs: man:NetworkManager(8)
   Main PID: 584 (NetworkManager)
  Tasks: 3 (limit: 19014)
 Memory: 17.5M
 CGroup: /system.slice/NetworkManager.service
 └─584 /usr/sbin/NetworkManager --no-daemon

Mar 28 13:52:55 raptor NetworkManager[584]:   [1585428775.4776] Config: 
added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Mar 28 13:52:55 raptor NetworkManager[584]:   [1585428775.4776] Config: 
added 'psk' value ''
Mar 28 13:52:55 raptor NetworkManager[584]:   [1585428775.4916] device 
(wlx1831bf53a3a2): supplicant interface state: disconnected -> associating
Mar 28 13:52:55 raptor NetworkManager[584]:   [1585428775.7019] device 
(wlx1831bf53a3a2): supplicant interface state: associating -> 4-way handshake
Mar 28 13:52:59 raptor NetworkManager[584]:   [1585428779.7193] 
sup-iface[0x55bfd02d69f0,wlx1831bf53a3a2]: connection disconnected (reason 2)
Mar 28 13:52:59 raptor NetworkManager[584]:   [1585428779.7195] device 
(wlx1831bf53a3a2): supplicant interface state: 4-way handshake -> disconnected
Mar 28 13:52:59 raptor NetworkManager[584]:   [1585428779.7210] device 
(wlx1831bf53a3a2): Activation: (wifi) disconnected during association, asking 
for new key
Mar 28 13:52:59 raptor NetworkManager[584]:   [1585428779.7212] device 
(wlx1831bf53a3a2): state change: config -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
Mar 28 13:52:59 raptor NetworkManager[584]:   [1585428779.8236] device 
(wlx1831bf53a3a2): supplicant interface state: disconnected -> scanning
Mar 28 13:53:02 raptor NetworkManager[584]:   [1585428782.0772] device 
(wlx1831bf53a3a2): supplicant interface state: scanning -> inactive


> On Mar 28, 2020, at 12:43, Brian  wrote:
> 

Re: network-manager takes 1-4 restarts in order to recognize and connect to already-configured wifi network, USB dongle NIC

[Alan Tu]

The network was and is configured in network-manager. I should add that one out 
of six or seven times, the connection is established automatically at boot.
Alan 

Sent from my iPhone

> On Mar 28, 2020, at 12:02, deloptes  wrote:
> 
> Alan Tu wrote:
> 
>> After trial and error, the best fix is for me to get into a terminal
>> and restart network-manager:
>> # systemctl restart network-manager
>> 
>> After one to four times of this, eventually network-manager
>> establishes the network connection.
> 
> Have you configured the network-card/connection in NetworkManager?
> If not - do so and set to auto connect - otherwise it will not connect
> automatically.
> 

network-manager takes 1-4 restarts in order to recognize and connect to already-configured wifi network, USB dongle NIC

[Alan Tu]

Hello, I have a "Debian testing" system installed with Mate. It has
network-manager 1.22.8-1.

My network adapter is an Asus USB dongle based on rtl8814au, I
compiled and installed a kernel module for it and the network works
great, once it gets going.

My problem is, when I boot the system and it gets to the mate login
prompt, the network isn't connected. Then, even after I log in to the
Mate desktop, I'm usually asked for the WPA wifi credentials.

After trial and error, the best fix is for me to get into a terminal
and restart network-manager:
# systemctl restart network-manager

After one to four times of this, eventually network-manager
establishes the network connection.

I think this probably has something to do with network-manager not
recognizing that the USB dongle is plugged in, even though the kernel
module is loaded.

What can I do to troubleshoot this problem, potentially filing a bug?

Or, maybe this is a problem with the kernel module for the USB adapter?

Alan

Upgraded to buster; screen offset on wake

[alan/james]

Hi all,

I just updated to buster from stretch (no problems).

I have a desktop with two monitors. I have the basic power saving 
setting that blanks the screens after 5 minutes.


When I wake the screens, the primary display is offset to the left by 
about 2 inches, leaving a black band along the right hand side of the 
monitor.


If I change the resolution of the monitor through the system settings 
dialog and then revert to the original the problem is fixed (until the 
screens blank again).


I have this issue with Xorg although it was also present with Wayland.

Many apologies for the non-technical nature of this post. Please let me 
know what sort of diagnostics would be helpful for identifying the issue.


Take care!

-James

Re: Debian 10.3 text installer; guided partitioning does not work; manual partitioning doesn't make USB bootable

[Alan Tu]

Thanks Andrei. The firmware image (thanks Debian team!) did in fact
have my wi-fi driver, saving a step. There is still one issue, and one
point of feedback.

The issue is that despite not needing the second USB, the partitioner
still complains that the free space is too small and I cannot use
guided partitioning. This despite the fact I'm ready to wipe the
target USB. I switched to the Busybox console (Ctrl+Alt+F2) and
checked that the target USB was not mounted. Frustrating.

My computer clearly can boot from both MBR (Windows partition is type
07h partition) and EFI partitions (the Debian ISO has partition type
EFh). How I got the target media to boot was to answer "yes" when the
installer asked whether I wanted to force EFI install. My target drive
is still the USB, not my built-in hard drives which I wanted left
alone. As long as I knew how to manually partition (ext4, swap, then
EFI system partition), this created a bootable system.

But guided partitioning for this scenario seems broken.

Alan


On 3/12/20, Andrei POPESCU  wrote:
> On Mi, 11 mar 20, 12:58:21, Alan Tu wrote:
>>
>> I have the second USB inserted into a different USB port. I need this
>> second USB to have my *.ucode firmware file on it, for my Intel wifi
>> chip. Therefore this second USB has a FAT32 partition at first.
>
> I would suggest you use an image that includes firmware, so the second
> USB is not used by the installation process.
>
> https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/
>
> Kind regards,
> Andrei
> --
> http://wiki.debian.org/FAQsFromDebianUser
>

Debian 10.3 text installer; guided partitioning does not work; manual partitioning doesn't make USB bootable

[Alan Tu]

Hi, I need some ideas for getting Debian 10.3 to install and boot. I
think I'm very close, just missing something.

I'm on an x64 system. What I need to do is to use one live USB to
install to a blank USB, and then have the second USB boot into Debian.

I am blind, which means without speech I don't know what is being
written on the screen.

My OS of comfort is Windows. I downloaded the Debian 10.3 DVD 1 and
used Rufus to burn this image to a USB. This USB boots, and I press S
 at the boot prompt to start the talking (and text) Debian
installer. So my motherboard [1] and USB ports are perfectly capable
of booting a correctly formatted bootable USB.

I have the second USB inserted into a different USB port. I need this
second USB to have my *.ucode firmware file on it, for my Intel wifi
chip. Therefore this second USB has a FAT32 partition at first.

The installer sees the wi-fi firmware file, gets onto the network, and
now its time to partition. At this point I'm ready to erase the second
USB and make it my permanent live USB. For whatever reason, the
installer complains that the free space is too small [2], and guided
partitioning does not work for me.

Suppose the second USB is /dev/sdc. I manually create a partition
table, a single partition taking up the whole 16 GB flash drive,
filesystem is ext4 and mount to /. (I'm ignoring swap.)

Of note, on this partition I set the "bootable flag" to on.

After software is installed, I get presented with the Grub choice. I
choose to install Grub, to the MBR, but to the second USB /dev/sdc. I
leave my built-in hard drives untouched.

I leave in the second USB, and reboot (both warm reboot and cold
boot.) My computer boots into Windows instead of booting the USB.
Fail.

Of note, if the system recognized the USB as bootable, but Grub boot
loader had an error, I think the system would just sit there at the
Grub/boot loader error and not boot into Windows.

I could use some ideas or a clue for what I'm doing wrong. Thanks in advance!

Alan

[1] Motherboard: Asus Maximus VIII GENE; Chipset: Intel Z170

[2] Failed to partition the selected disk
This probably happened because the selected disk or free space is too
small to be automatically partitioned.

Stretch to Buster upgrade from local nonfree DVD iso

[Alan Savage]

I am trying to upgrade from stretch to buster using the nonfree
installation DVD ISO "firmware-10.2.0-amd64-DVD-1.iso" that I downloaded
using the torrent here:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/10.2.0+nonfree/amd64/bt-dvd/

I copied the ISO to the local drive on my computer and added this line to
fstab:

/data/firmware-10.2.0-amd64-DVD-1.iso /mnt/apt iso9660 user,loop 0 0

mounted it, then added the source like this:
sudo apt-cdrom -m -d=/mnt/apt add

which added a line to /etc/apt/source.list, but when I do "sudo apt update"
I get the error

"Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update
cannot be used to add new CD-ROMs"
then
E: The repository 'cdrom://...snip...' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.

What am I doing wrong?

Re: Linux Debian Scretch versiyon server

[Seçkin Alan]

Merhaba,
Debian sitesinde var
https://www.debian.org/releases/stretch/debian-installer/

On Tuesday, January 15, 2019, Muhammet Enes Doğan <
muhammetenesdo...@hotmail.com> wrote:

> Merhabalar Linux Debian Scretch versiyon server kurmam gerekiyor web
> sitesinde bulamadım indirme linkini bana atarmasınız.
>


-- 
Seçkin ALAN
http://seckinalan.com

Re: ssh

[Alan Taylor]

Thanks Mike,

I was slowly coming to that conclusion !
What would be best practice regarding a password for that account (i.e. system 
account such as backuppc that needs ssh access but no shell access).

If I create the user with bash as the shell, I seem to have a few options:
1) don’t set a password (i.e. no reference to password in the adduer command). 
The man page says this results in the password being “disabled”. What does this 
actually mean for security ?
2) use —disabled-password (same as 1 above ?)
3) the —disabled-password option appears to be only available on debian. Redhat 
derivatives only offer useradd which does not have this switch ?

Which would be the most secure, while still allowing ssh access ?

BRgds/Alan
On 18 Nov 2018, 19:50 +0800, Michael Howard , wrote:
> On 17/11/2018 04:28, Alan Taylor wrote:
> > Thanks Everyone.
> >
> > I am getting that together to show you.
> >
> > A question though - are you sure this is not normal behavior ?
> > Most of my research on the net (with caution I know) seems to suggest that 
> > ssh disconnection after authentication because of /bin/false is normal ?
> >
> >
> Yes, it is normal. A user with /bin/false as his ahell should not be able to 
> login. These days www-data has /bin/false too, which caught be out, until I 
> changed it back.
> --
> Mike Howard

Re: ssh

[Alan Taylor]

Thanks Everyone.

I am getting that together to show you.

A question though - are you sure this is not normal behavior ?
Most of my research on the net (with caution I know) seems to suggest that ssh 
disconnection after authentication because of /bin/false is normal ?

BRgds/Alan
On 16 Nov 2018, 01:23 +0800, David Christensen , 
wrote:
> On 11/14/18 10:13 PM, Alan Taylor wrote:
> > Success … sort of.
> >
> > Removing "BatchMode yes” from the backuppc users .ssh/config file fixed 
> > everything EXCEPT
> > the backuppc user still could not ssh out from the backup computer (sirius) 
> > to other computers.
> > However, the error message was now a lot clearer (complaining that login 
> > not allowed because the account was locked).
> > All of the client computers have a backuppc user with the shell set to 
> > /bin/false (the recommended procedure) as there is no shell login required 
> > on these computers.
> > However, changing this to /bin/bash solved the problem … backuppc user can 
> > now ssh from the backup computer (sirius) to others.
> >
> > Any ideas as to what may be causing this last issue ?
> >
> > PS UsePam is set to yes
>
>
> If you want to log in to an account whose /etc/passwd shell is
> /bin/false, one trick is to su(1) to root, then su(1) to that account
> using the '--shell' option:
>
> 2018-11-15 09:17:06 root@tinkywinky ~
> # grep ntp /etc/passwd
> ntp:x:118:124::/home/ntp:/bin/false
>
> 2018-11-15 09:17:10 root@tinkywinky ~
> # su -l -s /bin/bash ntp
> No directory, logging in with HOME=/
> ntp@tinkywinky:/$
>
>
> Can backuppc on one "other" computer log into another "other" computer?
>
>
> It would help if you posted your console session indicating source
> machine (prompt), command issued, and output displayed.
>
>
> It would help if you posted the active lines in ~/.ssh/config,
> /etc/ssh/ssh_config, and /etc/ssh/sshd_config on the relevant machines:
>
> $ grep . ~/.ssh/config | grep -v '#'
>
> $ grep . /etc/ssh/ssh_config | grep -v '#'
>
> $ grep . /etc/ssh/sshd_config | grep -v '#'
>
>
> David
>
>

Re: ssh

[Alan Taylor]

Success … sort of.

Removing "BatchMode yes” from the backuppc users .ssh/config file fixed 
everything EXCEPT
the backuppc user still could not ssh out from the backup computer (sirius) to 
other computers.
However, the error message was now a lot clearer (complaining that login not 
allowed because the account was locked).
All of the client computers have a backuppc user with the shell set to 
/bin/false (the recommended procedure) as there is no shell login required on 
these computers.
However, changing this to /bin/bash solved the problem … backuppc user can now 
ssh from the backup computer (sirius) to others.

Any ideas as to what may be causing this last issue ?

PS UsePam is set to yes

BRgds/Alan

Re: ssh

[Alan Taylor]

her
pkalg/pkblob are acceptable for RSA
SHA256:/TFnCvwpyL6W0Z4I71jw9u3eY4rWqB9lnHVSx3mdYNM [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_key_allowed entering [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_request_send entering: type
22 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_key_allowed: waiting for
MONITOR_ANS_KEYALLOWED [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_request_receive_expect
entering: type 23 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_request_receive entering
[preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_request_receive entering
Nov 13 12:28:07 sirius sshd[2159]: debug3: monitor_read: checking request 22
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_answer_keyallowed entering
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_answer_keyallowed:
key_from_blob: 0x55f0b985d0d0
Nov 13 12:28:07 sirius sshd[2159]: debug1: temporarily_use_uid: 200/200
(e=0/0)
Nov 13 12:28:07 sirius sshd[2159]: debug1: trying public key file
/usr/local/BackupPC/.ssh/authorized_keys
Nov 13 12:28:07 sirius sshd[2159]: debug1: fd 4 clearing O_NONBLOCK
Nov 13 12:28:07 sirius sshd[2159]: debug2: user_key_allowed: check options:
'ssh-ed25519
C3NzaC1lZDI1NTE5IBIG1jFCDbjX1AuKEpi3U0rPtxW79kZwcEAzN+shbnni
Generated on 181113.1203 for backuppc@sirius\n'
Nov 13 12:28:07 sirius sshd[2159]: debug2: user_key_allowed: advance:
'C3NzaC1lZDI1NTE5IBIG1jFCDbjX1AuKEpi3U0rPtxW79kZwcEAzN+shbnni
Generated on 181113.1203 for backuppc@sirius\n'
Nov 13 12:28:07 sirius sshd[2159]: debug1: matching key found: file
/usr/local/BackupPC/.ssh/authorized_keys, line 2 RSA
SHA256:/TFnCvwpyL6W0Z4I71jw9u3eY4rWqB9lnHVSx3mdYNM
Nov 13 12:28:07 sirius sshd[2159]: debug1: restore_uid: 0/0
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_answer_keyallowed: key
0x55f0b985d0d0 is allowed
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_request_send entering: type 23
Nov 13 12:28:07 sirius sshd[2159]: debug3: send packet: type 60 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: userauth_pubkey: authenticated 0
pkalg ssh-rsa [preauth]
Nov 13 12:28:07 sirius sshd[2159]: Postponed publickey for backuppc from
192.168.8.3 port 48708 ssh2 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: Connection closed by 192.168.8.3 port
48708 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug1: do_cleanup [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: PAM: sshpam_thread_cleanup
entering [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug1: monitor_read_log: child log fd
closed
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_request_receive entering
Nov 13 12:28:07 sirius sshd[2159]: debug1: do_cleanup
Nov 13 12:28:07 sirius sshd[2159]: debug1: PAM: cleanup
Nov 13 12:28:07 sirius sshd[2159]: debug3: PAM: sshpam_thread_cleanup
entering
Nov 13 12:28:07 sirius sshd[2159]: debug1: Killing privsep child 2160
Nov 13 12:28:07 sirius sshd[2159]: debug1: audit_event: unhandled event 12
root@sirius:~#


On Tue, 13 Nov 2018 at 11:22, David Christensen 
wrote:

> On 11/12/18 5:49 AM, Alan Taylor wrote:
> > Greetings,
>
> Hi.  :-)
>
>
> > I have an ssh problem - one user can use it successfully, another
> cannot. I have checked and rechecked permissions until I am blue in the
> face …
> > At the moment just trying to ssh into the same machine I am on for the
> problem user (the other user can ssh successfully, both to the console
> machine and outwards to others).
> > Agent problem ? The successful user was setup in the installation, the
> problem user was added at the command line after initial setup.
>
> Trouble-shooting can be tedious...
>
>
> > Log output follows, appears to fail after the preauth stage …
> >
> > Any suggestions gratefully accepted
> >
> > root@sirius/etc/ssh # journalctl | grep sshd | grep "Nov 12 13:45"
> 
>
>
> I would enter the following commands into the indicated accounts and
> computers, substituting place holders with actual values (USERNAME,
> SSH_CLIENT, SSH_SERVER).  If you still don't see it, cut and paste your
> console sessions into a reply:
>
> 1.  As the user having problems on the computer having problems:
>
> $ whoami
>
> $ hostname
>
> $ cat /etc/debian_version
>
> $ uname -a
>
> $ dpkg-query -W openssh-client
>
> $ ls -aFl /home/USERNAME/.ssh
>
> $ ssh -v SSH_SERVER
>
> 2.  As root on the SSH server:
>
> # hostname
>
> # cat /etc/debian_version
>
> # uname -a
>
> # dpkg-query -W openssh-server
>
> # ls -aFl /home/USERNAME/.ssh
>
> # grep USERNAME@SSH_CLIENT /home/USERNAME/.ssh/authorized_keys
>
> # tail /var/log/auth.log
>
>
> David
>
>

Re: ssh

[Alan Taylor]

 after 134217728 blocks
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info:
server-sig-algs=
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering ED25519 public key:
/usr/local/BackupPC/.ssh/sirius_bpc-id_ed25519
debug1: Server accepts key: pkalg ssh-ed25519 blen 51
debug1: Offering RSA public key: /usr/local/BackupPC/.ssh/sirius_bpc-id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 535
debug1: No more authentication methods to try.
Permission denied (publickey).
backuppc@sirius:~$

as root :

root@sirius:~# whoami
root
root@sirius:~# hostname
sirius
root@sirius:~# cat /etc/debian_version
9.6
root@sirius:~# uname -a
Linux sirius 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
GNU/Linux
root@sirius:~# dpkg-query -W openssh-client
openssh-client1:7.4p1-10+deb9u4

root@sirius:~# ls -aFl /usr/local/BackupPC/.ssh
total 36
drwx-- 2 backuppc backuppc 4096 Nov 13 12:08 ./
drwxr-xr-x 6 backuppc backuppc 4096 Nov 13 12:12 ../
-rw--- 1 backuppc backuppc 1790 Nov 13 12:04 authorized_keys
-rw-r- 1 backuppc backuppc 2240 Nov 13 12:02 config
-rw-r--r-- 1 backuppc backuppc  142 Nov 13 12:08 known_hosts
-rw--- 1 backuppc backuppc  484 Nov 13 12:03 sirius_bpc-id_ed25519
-rw-r- 1 backuppc backuppc  126 Nov 13 12:03 sirius_bpc-id_ed25519.pub
-rw--- 1 backuppc backuppc 3479 Nov 13 12:04 sirius_bpc-id_rsa
-rw-r- 1 backuppc backuppc  770 Nov 13 12:04 sirius_bpc-id_rsa.pub

root@sirius:~# grep backuppc@sirius
/usr/local/BackupPC/.ssh/authorized_keys
ssh-ed25519
C3NzaC1lZDI1NTE5IBIG1jFCDbjX1AuKEpi3U0rPtxW79kZwcEAzN+shbnni
Generated on 181113.1203 for backuppc@sirius
ssh-rsa
B3NzaC1yc2EDAQABAAACAQD2fiZLF9Q0+RKERleUw2LnoEXF3FdF/UPPX+khWUVIc+SWG+mTSIlFeEWNeoLpa32Vfb0T8cNooMgR6sodxQZlzC15ByPSotW7AHAdBylzkP0G4GM4zTYlkfuIzeJClNrNuphzbdIa8dH9xhmhqE7FbHcq34LErQX1zBfGcDVyqUABVdXTLqtDKRS2P3hCQ8gR8u0BDesvTUYWPwJXkXaq9UdS9VWsJuyQhnqzFKOm+cPdoqRFtvVAIxlqAyI9ok7d/cve4nIjFPg1n7ralTw4x8D4oxmOpUNqOC4dJYDCbihY3nImq0oB/+zt6uS3t232qjaUGrt0pUB2AywQwULYhGhAsiqGEaoJuuYUonCXT4IHxTIBFJraVSvr53gcM7Jm9kBcLG8x2B5rtiZzBImITv+nZnqTJgBu5q+ZBqm5FK4miBHjinscXxqCLmljXOW7Ui7uhg1NjcYMdaC1BRJoHzsTkIvnoRmONdUbDCK63n9MHikiRrvdme8SUQDjuKHfS5nNMClDfMF69Rgr27QkqOMOYYA2mqvcrjxtXS1n9DA88dnhCKsHfTDXCto710CHzQPh7YuUzlL8uNAE4RwzhOCDxgaI4WV9/qj2J+0C2PE0dkTwFqBuGytyBYFglpIhmnlucukdccZ5i/YpEkITvccB7EO/sPSRzAnm55iGUw==
Generated on 181113.1203 for backuppc@sirius

root@sirius:~# tail -n 20 /var/log/auth.log
Nov 13 12:28:07 sirius sshd[2159]: debug1: fd 4 clearing O_NONBLOCK
Nov 13 12:28:07 sirius sshd[2159]: debug2: user_key_allowed: check options:
'ssh-ed25519
C3NzaC1lZDI1NTE5IBIG1jFCDbjX1AuKEpi3U0rPtxW79kZwcEAzN+shbnni
Generated on 181113.1203 for backuppc@sirius\n'
Nov 13 12:28:07 sirius sshd[2159]: debug2: user_key_allowed: advance:
'C3NzaC1lZDI1NTE5IBIG1jFCDbjX1AuKEpi3U0rPtxW79kZwcEAzN+shbnni
Generated on 181113.1203 for backuppc@sirius\n'
Nov 13 12:28:07 sirius sshd[2159]: debug1: matching key found: file
/usr/local/BackupPC/.ssh/authorized_keys, line 2 RSA
SHA256:/TFnCvwpyL6W0Z4I71jw9u3eY4rWqB9lnHVSx3mdYNM
Nov 13 12:28:07 sirius sshd[2159]: debug1: restore_uid: 0/0
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_answer_keyallowed: key
0x55f0b985d0d0 is allowed
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_request_send entering: type 23
Nov 13 12:28:07 sirius sshd[2159]: debug3: send packet: type 60 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug2: userauth_pubkey: authenticated 0
pkalg ssh-rsa [preauth]
Nov 13 12:28:07 sirius sshd[2159]: Postponed publickey for backuppc from
192.168.8.3 port 48708 ssh2 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: Connection closed by 192.168.8.3 port
48708 [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug1: do_cleanup [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug3: PAM: sshpam_thread_cleanup
entering [preauth]
Nov 13 12:28:07 sirius sshd[2159]: debug1: monitor_read_log: child log fd
closed
Nov 13 12:28:07 sirius sshd[2159]: debug3: mm_request_receive entering
Nov 13 12:28:07 sirius sshd[2159]: debug1: do_cleanup
Nov 13 12:28:07 sirius sshd[2159]: debug1: PAM: cleanup
Nov 13 12:28:07 sirius sshd[2159]: debug3: PAM: sshpam_thread_cleanup
entering
Nov 13 12:28:07 sirius sshd[2159]: debug1: Killing privsep child 2160
Nov 13 12:28:07 sirius sshd[2159]: debug1: audit_event: unhandled event 12
root@sirius:~#

On Tue, 13 Nov 2018 at 11:22, David Christensen 
wrote:

> On 11/12/18 5:49 AM, Alan Taylor wrote:
> > Greetings,
>
> Hi.  :-)
>
>
> > I have an ssh problem - one user can use it successfully, another
> cannot. I have checked and rechecked permissions until I am blue in the
> face …
> > At the moment just trying to ssh into the same machine I am on for the
> problem user (the other user can ssh successfully, both to the console
> machine and outwards to others).
> > Agent problem ? Th

Re: ssh

[Alan Taylor]

No, both users have rsa and ed25519 keys only.
On 12 Nov 2018, 22:07 +0800, Freek de Kruijf , wrote:
> Op maandag 12 november 2018 14:49:23 CET schreef Alan Taylor:
> > Greetings,
> >
> > I have an ssh problem - one user can use it successfully, another cannot. I
> > have checked and rechecked permissions until I am blue in the face … At the
> > moment just trying to ssh into the same machine I am on for the problem
> > user (the other user can ssh successfully, both to the console machine and
> > outwards to others). Agent problem ? The successful user was setup in the
> > installation, the problem user was added at the command line after initial
> > setup.
> >
> > Log output follows, appears to fail after the preauth stage …
> >
> > Any suggestions gratefully accepted
> >
> > root@sirius/etc/ssh # journalctl | grep sshd | grep "Nov 12 13:45"
> > Nov 12 13:45:17 sirius sshd[3155]: debug3: fd 4 is not O_NONBLOCK
> > Nov 12 13:45:17 sirius sshd[3155]: debug1: Forked child 3241.
> > Nov 12 13:45:17 sirius sshd[3155]: debug3: send_rexec_state: entering fd = 7
> > config len 650 Nov 12 13:45:17 sirius sshd[3155]: debug3: ssh_msg_send:
> > type 0
> > Nov 12 13:45:17 sirius sshd[3241]: debug3: oom_adjust_restore
> > Nov 12 13:45:17 sirius sshd[3155]: debug3: send_rexec_state: done
> > Nov 12 13:45:17 sirius sshd[3241]: debug1: Set /proc/self/oom_score_adj to 0
> > Nov 12 13:45:17 sirius sshd[3241]: debug1: rexec start in 4 out 4 newsock 4
> > pipe 6 sock 7 Nov 12 13:45:17 sirius sshd[3241]: debug1: inetd sockets
> > after dupping: 3, 3 Nov 12 13:45:17 sirius sshd[3241]: Connection from
> > 192.168.8.3 port 39668 on 192.168.8.3 port 50400 Nov 12 13:45:17 sirius
> > sshd[3241]: debug1: Client protocol version 2.0; client software version
> > OpenSSH_7.4p1 Debian-10+deb9u4 Nov 12 13:45:17 sirius sshd[3241]: debug1:
> > match: OpenSSH_7.4p1 Debian-10+deb9u4 pat OpenSSH* compat 0x0400 Nov 12
> > 13:45:17 sirius sshd[3241]: debug1: Local version string
> > SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u4 Nov 12 13:45:17 sirius sshd[3241]:
> > debug1: Enabling compatibility mode for protocol 2.0 Nov 12 13:45:17 sirius
> > sshd[3241]: debug2: fd 3 setting O_NONBLOCK Nov 12 13:45:17 sirius
> > sshd[3241]: debug3: ssh_sandbox_init: preparing seccomp filter sandbox Nov
> > 12 13:45:17 sirius sshd[3241]: debug2: Network child is on pid 3242 Nov 12
> > 13:45:17 sirius sshd[3241]: debug3: preauth child monitor started Nov 12
> > 13:45:17 sirius sshd[3241]: debug3: privsep user:group 117:65534 [preauth]
> > Nov 12 13:45:17 sirius sshd[3241]: debug1: permanently_set_uid: 117/65534
> > [preauth] Nov 12 13:45:17 sirius sshd[3241]: debug3: ssh_sandbox_child:
> > setting PR_SET_NO_NEW_PRIVS [preauth] Nov 12 13:45:17 sirius sshd[3241]:
> > debug3: ssh_sandbox_child: attaching seccomp filter program [preauth] Nov
> > 12 13:45:17 sirius sshd[3241]: debug1: list_hostkey_types:
> > ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256 [preauth] Nov 12 13:45:17
> > sirius sshd[3241]: debug3: send packet: type 20 [preauth] Nov 12 13:45:17
> > sirius sshd[3241]: debug1: SSH2_MSG_KEXINIT sent [preauth] Nov 12 13:45:17
> > sirius sshd[3241]: debug3: receive packet: type 20 [preauth] Nov 12
> > 13:45:17 sirius sshd[3241]: debug1: SSH2_MSG_KEXINIT received [preauth] Nov
> > 12 13:45:17 sirius sshd[3241]: debug2: local server KEXINIT proposal
> > [preauth] Nov 12 13:45:17 sirius sshd[3241]: debug2: KEX algorithms:
> > curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2
> > -nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hel
> > lman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha
> > 256,diffie-hellman-group14-sha1 [preauth] Nov 12 13:45:17 sirius sshd[3241]:
> > debug2: host key algorithms: ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256
> > [preauth] Nov 12 13:45:17 sirius sshd[3241]: debug2: ciphers ctos:
> > chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@o
> > penssh.com,aes256-...@openssh.com[preauth] Nov 12 13:45:17 sirius
> > sshd[3241]: debug2: ciphers stoc:
> > chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@o
> > penssh.com,aes256-...@openssh.com[preauth] Nov 12 13:45:17 sirius
> > sshd[3241]: debug2: MACs ctos:
> > umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-etm@openssh.
> > com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac-64@openssh.
> > com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 [preauth] Nov
> > 12 13:45:17 sirius sshd[3241]: debug2: MACs stoc:
> > umac-64-..

ssh

[Alan Taylor]

ov 12 13:45:17 sirius sshd[3241]: debug1: restore_uid: 0/0
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_answer_keyallowed: key 
0x558f44057060 is allowed
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_request_send entering: type 23
Nov 12 13:45:17 sirius sshd[3241]: debug3: send packet: type 60 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: userauth_pubkey: authenticated 0 
pkalg ssh-ed25519 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: Postponed publickey for backuppc from 
192.168.8.3 port 39668 ssh2 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug3: receive packet: type 50 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug1: userauth-request for user backuppc 
service ssh-connection method publickey [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug1: attempt 2 failures 0 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: input_userauth_request: try method 
publickey [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug1: userauth_pubkey: test whether 
pkalg/pkblob are acceptable for RSA 
SHA256:07i2CAzyT2c3NHYQRlCT2bONAW8mIgJ7EVVkmLGzMuw [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_key_allowed entering [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_request_send entering: type 22 
[preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_key_allowed: waiting for 
MONITOR_ANS_KEYALLOWED [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_request_receive_expect entering: 
type 23 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_request_receive entering [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_request_receive entering
Nov 12 13:45:17 sirius sshd[3241]: debug3: monitor_read: checking request 22
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_answer_keyallowed entering
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_answer_keyallowed: key_from_blob: 
0x558f44056f00
Nov 12 13:45:17 sirius sshd[3241]: debug1: temporarily_use_uid: 200/200 (e=0/0)
Nov 12 13:45:17 sirius sshd[3241]: debug1: trying public key file 
/usr/local/BackupPC/.ssh/authorized_keys
Nov 12 13:45:17 sirius sshd[3241]: debug1: fd 4 clearing O_NONBLOCK
Nov 12 13:45:17 sirius sshd[3241]: debug2: user_key_allowed: check options: 
'ssh-ed25519 
C3NzaC1lZDI1NTE5IKgBYt6r7yHGVoM2QFXFhtOdFrReyb2MycRgRdvpsFPr Generated 
on 181112.1124 for backuppc@sirius\n'
Nov 12 13:45:17 sirius sshd[3241]: debug2: user_key_allowed: advance: 
'C3NzaC1lZDI1NTE5IKgBYt6r7yHGVoM2QFXFhtOdFrReyb2MycRgRdvpsFPr Generated 
on 181112.1124 for backuppc@sirius\n'
Nov 12 13:45:17 sirius sshd[3241]: debug1: matching key found: file 
/usr/local/BackupPC/.ssh/authorized_keys, line 2 RSA 
SHA256:07i2CAzyT2c3NHYQRlCT2bONAW8mIgJ7EVVkmLGzMuw
Nov 12 13:45:17 sirius sshd[3241]: debug1: restore_uid: 0/0
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_answer_keyallowed: key 
0x558f44056f00 is allowed
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_request_send entering: type 23
Nov 12 13:45:17 sirius sshd[3241]: debug3: send packet: type 60 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug2: userauth_pubkey: authenticated 0 
pkalg ssh-rsa [preauth]
Nov 12 13:45:17 sirius sshd[3241]: Postponed publickey for backuppc from 
192.168.8.3 port 39668 ssh2 [preauth]
Nov 12 13:45:17 sirius sshd[3241]: Connection closed by 192.168.8.3 port 39668 
[preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug1: do_cleanup [preauth]
Nov 12 13:45:17 sirius sshd[3241]: debug1: monitor_read_log: child log fd closed
Nov 12 13:45:17 sirius sshd[3241]: debug3: mm_request_receive entering
Nov 12 13:45:17 sirius sshd[3241]: debug1: do_cleanup
Nov 12 13:45:17 sirius sshd[3241]: debug1: Killing privsep child 3242
Nov 12 13:45:17 sirius sshd[3241]: debug1: audit_event: unhandled event 12
root@sirius/etc/ssh #

Alan

Re: Get the external IP address from a Linux box

[Alan Greenberger]

On 2018-05-28, David Wright  wrote:
> On Mon 28 May 2018 at 07:54:49 (-0400), Alan Greenberger wrote:
>> On 2018-05-26, Pascal Hambourg  wrote:
>> > Le 25/05/2018 à 02:17, Alan Greenberger a écrit :
>> >> On 2018-05-24, André Rodier  wrote:
>> >>>
>> >>> I am looking for a native package on Debian, that can give me the
>> >>> external IP address of the machine.
>> >> 
>> >> Assuming you are looking for the public internet address of your router,
>> >> you could try:
>> >> /usr/sbin/arp -n
>> >> and it may show up on a line with the HWadress of your router.
>> >
>> > Nope. That would just show the internal address of the router.
>> >
>> >
>> You are mostly correct.  However, I have one machine on which the
>> response to
>> /usr/sbin/arp -n
>> shows two lines with the HWaddress of the router, one with the internal
>> address as you said and the other with the external address.  I have no
>> idea what made arp see the external address.
>
> Can we see what you're seeing (suitably mangled)?
>
> Cheers,
> David.
>
>
192.168.1.1  ether   6x:3x:ex:7x:4x:bx   C eth0
2x.1xx.1xx.1xx   ether   6x:3x:ex:7x:4x:bx   C eth0

Re: Get the external IP address from a Linux box

[Alan Greenberger]

On 2018-05-26, Pascal Hambourg <pas...@plouf.fr.eu.org> wrote:
> Le 25/05/2018 à 02:17, Alan Greenberger a écrit :
>> On 2018-05-24, André Rodier <an...@rodier.me> wrote:
>>>
>>> I am looking for a native package on Debian, that can give me the
>>> external IP address of the machine.
>> 
>> Assuming you are looking for the public internet address of your router,
>> you could try:
>> /usr/sbin/arp -n
>> and it may show up on a line with the HWadress of your router.
>
> Nope. That would just show the internal address of the router.
>
>
You are mostly correct.  However, I have one machine on which the
response to
/usr/sbin/arp -n
shows two lines with the HWaddress of the router, one with the internal
address as you said and the other with the external address.  I have no
idea what made arp see the external address.

Re: Get the external IP address from a Linux box

[Alan Greenberger]

On 2018-05-24, André Rodier  wrote:
> Hello,
>
> I am looking for a native package on Debian, that can give me the
> external IP address of the machine.
>

Assuming you are looking for the public internet address of your router,
you could try:
/usr/sbin/arp -n
and it may show up on a line with the HWadress of your router.

Re: can't boot a Debian on QEMU-mips virtual machine, could be initrd or root device problems

[Alan Tu]

Thanks Reco. The concept I missed is, I need to grab the initrd and
kernel from the installed system, specifically from the /boot
directory. I know that now for all future architectures I mess with!

There are lots of ways to do the same thing, I'm just sharing. To
mount a partition inside raw disk image, one can use the loopback
device.

1.  Determine the byte offset of the desired partition.
$ fdisk -lu
$offset=sector size * start sector

2.  Create the loopback link.
# losetup -o $offset /dev/loop0 image_file

3.  Mount as usual:
# mount /dev/loop0 directory

4.  Copy files, edit/make changes, etc.

5.  When done, umount as usual:
# umount /dev/loop0

6.  Detach the loopback device.
# losetup -d /dev/loop0

Alan


On 4/30/18, Reco <recovery...@gmail.com> wrote:
>   Hi.
>
> On Mon, Apr 30, 2018 at 06:30:32PM +0200, Thomas Schmitt wrote:
>> > # qemu-system-mips -m 2048 -rtc base=localtime -boot order=c
>> > -nographic -hda debian_mips32b.img -kernel vmlinux-4.9.0-6-4kc-malta
>> > -append "root=/dev/sda1"
>>
>> Shouldn't there be a bootloader installed in debian_mips32b.img ?
>
> No. One of the oddities of QEMU's malta that nobody was able to write a
> working bootloader for it. OP is doing it the only way that's possible.
>
> Reco
>
>

can't boot a Debian on QEMU-mips virtual machine, could be initrd or root device problems

[Alan Tu]

Hi, I'm having trouble bootting Debian 9.4 on a QEMU-emulated MIPS
malta virtual machine. I know QEMU introduces some complexity, but I
think my problem is more of a misunderstanding of Linux boot concepts.
I've tried different permutations, and reading, but am stuck.

I installed Debian inside a virtual disk image. Here is the output of
"fdisk -lu" that shows the partition setup of this disk image. I think
it shows a valid and recognized first partition, as set up at
install-time.
$ fdisk -lu debian_mips32b.img
Disk debian_mips32b.img: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6c0f31a2

Device   BootStart  End  Sectors  Size Id Type
debian_mips32b.img1  2048 15992831 15990784  7.6G 83 Linux
debian_mips32b.img2  15994878 16775167   780290  381M  5 Extended
debian_mips32b.img5  15994880 16775167   780288  381M 82 Linux
swap / Solaris

Booting this doesn't work. If I supply the same Debian initrd image I
used to install, I see the installer language selection menu, not the
system. Despite the fact I don't attach a virtual CD-ROM install
media.

If I don't point qemu at the initrd RAM disk, the kernel seems to
start, but it has problems.
# qemu-system-mips -m 2048 -rtc base=localtime -boot order=c
-nographic -hda debian_mips32b.img -kernel vmlinux-4.9.0-6-4kc-malta
-append "root=/dev/sda1"

I've attached the console output, but note:
[0.00] Kernel command line: root=/dev/sda1 console=ttyS0,38400n8r

This suggests that the kernel has received my intention to look for
root on /dev/sda1. But then:

[0.644281] List of all partitions:
[0.644483] No filesystem could mount root, tried: [0.644669]
[0.644847] Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(0,0)

So two questions:

1.  Am I supposed to tell the virtual machine where to find the initrd
RAM disk, and do I use the same initrd downloaded from Debian as the
installer, or a different initrd from somewhere? The kernel seems to
go some way without this.

2.  It seems the kernel is somehow not recognizing the partition. I'm
not sure what the problem is here.

I'd appreciate any hints. Even confirming how things are supposed to
work helps. Thanks.

Alan
[0.00] Linux version 4.9.0-6-4kc-malta (debian-ker...@lists.debian.org) 
(gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 Debian 4.9.82-1+deb9u3 
(2018-03-02)
[0.00] earlycon: uart8250 at I/O port 0x3f8 (options '38400n8')
[0.00] bootconsole [uart8250] enabled
[0.00] Config serial console: console=ttyS0,38400n8r
[0.00] CPU0 revision is: 00019300 (MIPS 24Kc)
[0.00] FPU revision is: 00739300
[0.00] MIPS: machine is mti,malta
[0.00] Software DMA cache coherency enabled
[0.00] Determined physical RAM map:
[0.00]  memory: 1000 @  (usable)
[0.00]  memory: 6000 @ 9000 (usable)
[0.00] Kernel relocated by 0x00fd
 .text @ 0x810d
 .data @ 0x816a0c04
 .bss  @ 0x819e
[0.00] Initrd not found or empty - disabling initrd
[0.00] Reserving 0MB of memory at 0MB for crashkernel
[0.00] Primary instruction cache 2kB, VIPT, 2-way, linesize 16 bytes.
[0.00] Primary data cache 2kB, 2-way, VIPT, no aliases, linesize 16 
bytes
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x-0x00ff]
[0.00]   Normal   [mem 0x0100-0x0fff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x0fff]
[0.00] Initmem setup node 0 [mem 0x-0x0fff]
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 64960
[0.00] Kernel command line: root=/dev/sda1 console=ttyS0,38400n8r
[0.00] PID hash table entries: 1024 (order: 0, 4096 bytes)
[0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[0.00] Writing ErrCtl register=
[0.00] Readback ErrCtl register=
[0.00] Memory: 248996K/262144K available (5946K kernel code, 576K 
rwdata, 1328K rodata, 1420K init, 284K bss, 13148K reserved, 0K cma-reserved)
[0.00] NR_IRQS:256
[0.00] CPU frequency 200.00 MHz
[0.00] clocksource: MIPS: mask: 0x max_cycles: 0x, 
max_idle_ns: 19112599307 ns
[0.000149] sched_clock: 32 bits at 100MHz, resolution 9ns, wraps every 
21474830331ns
[0.006413] Console: colour dummy device 80x25
[0.007713] Calibrating delay loop... [0.058167] 844.80 BogoMIPS 
(lpj=1689600)
[0.058380] pid_max: default: 32768 minimum: 301
[0.059468

Re: stuck at Debian's text installer numerical Software Selection menu

[Alan Tu]

John, I do enjoy giving back by documenting and reporting bugs.

Is there some way, at least theoretically, that you know of to get the
text installer to record the output and the responses it think its
receiving? There's going to be an issue if the media is read-only and
it can't write files, that's why I say "at least theoretically".

I know that if an installation is successful, one can do

debconf-get-selections --installer

to get all the variables but I was hoping for something a little more
low level. Thanks.

Alan


On 4/30/18, john doe <johndoe65...@mail.com> wrote:
> On 4/30/2018 12:01 PM, Alan Tu wrote:
>> Thanks John for confirming how things are supposed to work, that helps
>> because it narrows things down and I don't need to wonder what is the
>> correct way. In MIPS it turns out choices 10 11 is the default.
>> Problem averted/bypassed.
>>
>> We're not going to solve it here, but its still weird. Entering 10 11
>> on x86 is the first thing I tried, and gnome and the rest were still
>> installed. The text installer is weird, sometimes I enter number,
>> Enter and am asked the same question again.
>>
>
> Looks like a bug , are you experiencing the same behavior with an older
> version?
>
> For testing purposes I would check if it is fixed in the below link and
> reported if needed:
>
> https://www.debian.org/devel/debian-installer/
>
> --
> John Doe
>
>

Re: stuck at Debian's text installer numerical Software Selection menu

[Alan Tu]

Thanks John for confirming how things are supposed to work, that helps
because it narrows things down and I don't need to wonder what is the
correct way. In MIPS it turns out choices 10 11 is the default.
Problem averted/bypassed.

We're not going to solve it here, but its still weird. Entering 10 11
on x86 is the first thing I tried, and gnome and the rest were still
installed. The text installer is weird, sometimes I enter number,
Enter and am asked the same question again.

Thanks Dan for the encouragement. Much appreciated too.

Alan


On 4/29/18, john doe <johndoe65...@mail.com> wrote:
> On 4/30/2018 3:00 AM, Alan Tu wrote:
>> Hi, I'm playing with Debian 9.4 stretch on other architectures via the
>> QEMU emulator (eventually for security research.) I can't figure out
>> how to handle the numerical software selection menu in the _text_
>> installer.
>>
>> I managed to install Debian x86 inside QEMU, using the newt installer.
>> However, I'm having trouble getting the newt installer to run on
>> emulated MIPS (I only see a Go Back button at language selection,
>> that's a separate problem.)
>>
>> I can get the text installer to launch via passing
>> DEBIAN_FRONTEND=text as a kernel parameter, and right now my objective
>> is to get Debian installed inside emulated MIPS via the text
>> installer.
>>
>> The challenge is the Software Selection menu, with items 1-11 with
>> items like desktop environments, print server and SSH server.
>>
>> I played with this for several hours yesterday on the x86 installer,
>> and I could not figure this out. I tried entering numbers separated by
>> a space at the prompt, entering ? at this prompt. I tried passing
>> tasks?="ssh-server, standard"
>> tasksel:tasksel/first?="ssh-server, standard"
>> with or without a space after the comma. I looked at preseed files to
>> get the right variables.
>>
>> I read all about boot parameters. No matter what I did, desktop and
>> print-server were installed on x86.
>>
>> I used the newt installer to get x86 Debian installed. But I'm having
>> trouble with newt installer on MIPS right now.
>>
>> At the Software Selection menu in the text installer, with typical
>> numerical options 1-11, how do I make the selection of ssh-server and
>> standard?
>>
>> Thanks in advance. I beat my head on this problem for several hours
>> yesterday, and I'd appreciate a helpful hint.
>>
>
> You simply input eatch desired numbers seperated by spaces:
>
> 10 11
>
> will only install package number 10 and 11
>
> --
> John Doe
>
>

stuck at Debian's text installer numerical Software Selection menu

[Alan Tu]

Hi, I'm playing with Debian 9.4 stretch on other architectures via the
QEMU emulator (eventually for security research.) I can't figure out
how to handle the numerical software selection menu in the _text_
installer.

I managed to install Debian x86 inside QEMU, using the newt installer.
However, I'm having trouble getting the newt installer to run on
emulated MIPS (I only see a Go Back button at language selection,
that's a separate problem.)

I can get the text installer to launch via passing
DEBIAN_FRONTEND=text as a kernel parameter, and right now my objective
is to get Debian installed inside emulated MIPS via the text
installer.

The challenge is the Software Selection menu, with items 1-11 with
items like desktop environments, print server and SSH server.

I played with this for several hours yesterday on the x86 installer,
and I could not figure this out. I tried entering numbers separated by
a space at the prompt, entering ? at this prompt. I tried passing
tasks?="ssh-server, standard"
tasksel:tasksel/first?="ssh-server, standard"
with or without a space after the comma. I looked at preseed files to
get the right variables.

I read all about boot parameters. No matter what I did, desktop and
print-server were installed on x86.

I used the newt installer to get x86 Debian installed. But I'm having
trouble with newt installer on MIPS right now.

At the Software Selection menu in the text installer, with typical
numerical options 1-11, how do I make the selection of ssh-server and
standard?

Thanks in advance. I beat my head on this problem for several hours
yesterday, and I'd appreciate a helpful hint.

Alan

Re: Problema con conexión a internet

[Alan]

El 23/11/17 a las 12:40, sebastian Oldani escribió:
> El día 23 de noviembre de 2017, 12:27, Alan
> <alan_laut...@yahoo.com.ar> escribió:
>> El 23/11/17 a las 10:59, Felix Perez escribió:
>>
>> El 23 de noviembre de 2017, 09:09, Alan <alan_laut...@yahoo.com.ar>
>> escribió:
>>
>> El 23/11/17 a las 02:05, Emiliano Gabriel Reynoso escribió:
>>
>> Alan,
>> Consulta: verificaste el estado de network-manager al iniciar?
>>
>>
>>
>> El 22 nov. 2017 22:33, "Felix Perez" <felix.listadeb...@gmail.com> escribió:
>>
>> El 22 de noviembre de 2017, 19:33, Alan <alan_laut...@yahoo.com.ar>
>> escribió:
>>
>> El 22/11/17 a las 18:38, Felix Perez escribió:
>>
>> El 22 de noviembre de 2017, 15:41, Alan <alan_laut...@yahoo.com.ar>
>> escribió:
>>
>> Saludos, lista. Desde hace tiempo tengo problemas en un viejo PC.
>> Instalé
>> variedad de distribuciones GNU/Linux y el internet funciona. Apago el PC
>> o
>> reinicio y ya no es posible conectarse. La "solución" es desenchufar y
>> volver a conectar para que se arregle.
>>
>> A que llamas "viejo" 1,2,3.. 10 años, ¿Qué hardware? ¿Desenchufar y
>> volever a conectar qué?¿Versión de Debian?
>>
>> Curiosamente en el Windows -que aún no le quité por el problema,
>> dejándolo
>> como dual boot- el internet siempre anda bien, pero si entro a Debian y
>> luego de nuevo a Windows, no me es posible usar el internet sin
>> desenchufar
>> el PC.
>> El comando "lspci -vmmnn" arroja lo siguiente en cuanto al controlador
>> de
>> ethernet:
>>
>>
>> Slot:00:12.0
>> Class:Ethernet controller [0200]
>> Vendor:VIA Technologies, Inc. [1106]
>> Device:VT6102/VT6103 [Rhine-II] [3065]
>> SVendor:Elitegroup Computer Systems [1019]
>> SDevice:VT6102/VT6103 [Rhine-II] [0102]
>>
>>
>> ¿Están bien instalados los módulos VIA?
>>
>> Esa tarjeta de red funciona muy bien en debian, ¿Supongo es la
>> integrada? ya que creo que también había unas PCI.
>>
>> Busqué información en internet pero no encontré nada que sirviera, y
>> otras
>> opciones no las pude probar por necesitar programas que ya no se
>> encuentran
>> en los repositorios de Debian (modconf, por ejemplo).
>>
>> ¿Qué hiciste, probaste?
>>
>> ¿Alguien de la lista conoce alguna solución o se le ocurre algo que
>> pueda
>> probar?
>>
>> Perdón pero los poderes psiquicos no los ocupo en la lista.
>>
>> Muchas gracias
>>
>> PD: No sé si tenga que ver, creo que no pero por las dudas lo consulto.
>> En
>> la carga del sistema, tanto cuando el internet como cuando no, me
>> aparece un
>> mensaje indicando "mpu-401 device not found or device busy".
>>
>> ¿Supongo sabes de que se trata MPU?
>>
>> Debes aportar más datos.
>>
>>
>>
>>
>> Tendrá como diez años. La aplicación neofetch arroja lo siguiente en
>> cuanto
>> a hardware y software:
>>
>> OS: Debian GNU/Linux 9.2 (stretch) x86_64
>> Model: P23G 1.0
>> Kernel: 4.9.0-4-amd64
>> CPU: Intel Pentium 4 3.20GHz (2) @ 3.2GHz
>> GPU: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics
>> Memory: 1940MB (originalmente tenía 512 MB)
>>
>> El comando lpsci (sin argumentos) indica lo siguiente:
>>
>>
>> 00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
>> Host
>> Bridge
>> 00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
>> Host
>> Bridge
>> 00:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
>> Host
>> Bridge
>> 00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
>> 00:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
>> Host
>> Bridge
>> 00:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
>> Host
>> Bridge
>> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
>> 00:09.0 Multimedia controller: Philips Semiconductors SAA7130 Video
>> Broadcast Decoder (rev 01)
>> 00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID
>> Controller (rev 80)
>> 00:0f.1 IDE interface: VIA Technologies, Inc.
>> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
>> 00:10.0 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1
>> Controller (rev 81)
>> 00:10.1 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1
>>

Re: Problema con conexión a internet

[Alan]

El 23/11/17 a las 10:59, Felix Perez escribió:
> El 23 de noviembre de 2017, 09:09, Alan <alan_laut...@yahoo.com.ar> escribió:
>> El 23/11/17 a las 02:05, Emiliano Gabriel Reynoso escribió:
>>
>> Alan,
>> Consulta: verificaste el estado de network-manager al iniciar?
>>
>>
>>
>> El 22 nov. 2017 22:33, "Felix Perez" <felix.listadeb...@gmail.com> escribió:
>>> El 22 de noviembre de 2017, 19:33, Alan <alan_laut...@yahoo.com.ar>
>>> escribió:
>>>> El 22/11/17 a las 18:38, Felix Perez escribió:
>>>>
>>>> El 22 de noviembre de 2017, 15:41, Alan <alan_laut...@yahoo.com.ar>
>>>> escribió:
>>>>
>>>> Saludos, lista. Desde hace tiempo tengo problemas en un viejo PC.
>>>> Instalé
>>>> variedad de distribuciones GNU/Linux y el internet funciona. Apago el PC
>>>> o
>>>> reinicio y ya no es posible conectarse. La "solución" es desenchufar y
>>>> volver a conectar para que se arregle.
>>>>
>>>> A que llamas "viejo" 1,2,3.. 10 años, ¿Qué hardware? ¿Desenchufar y
>>>> volever a conectar qué?¿Versión de Debian?
>>>>
>>>> Curiosamente en el Windows -que aún no le quité por el problema,
>>>> dejándolo
>>>> como dual boot- el internet siempre anda bien, pero si entro a Debian y
>>>> luego de nuevo a Windows, no me es posible usar el internet sin
>>>> desenchufar
>>>> el PC.
>>>> El comando "lspci -vmmnn" arroja lo siguiente en cuanto al controlador
>>>> de
>>>> ethernet:
>>>>
>>>>
>>>> Slot:00:12.0
>>>> Class:Ethernet controller [0200]
>>>> Vendor:VIA Technologies, Inc. [1106]
>>>> Device:VT6102/VT6103 [Rhine-II] [3065]
>>>> SVendor:Elitegroup Computer Systems [1019]
>>>> SDevice:VT6102/VT6103 [Rhine-II] [0102]
>>>>
>>>>
>>>> ¿Están bien instalados los módulos VIA?
>>>>
>>>> Esa tarjeta de red funciona muy bien en debian, ¿Supongo es la
>>>> integrada? ya que creo que también había unas PCI.
>>>>
>>>> Busqué información en internet pero no encontré nada que sirviera, y
>>>> otras
>>>> opciones no las pude probar por necesitar programas que ya no se
>>>> encuentran
>>>> en los repositorios de Debian (modconf, por ejemplo).
>>>>
>>>> ¿Qué hiciste, probaste?
>>>>
>>>> ¿Alguien de la lista conoce alguna solución o se le ocurre algo que
>>>> pueda
>>>> probar?
>>>>
>>>> Perdón pero los poderes psiquicos no los ocupo en la lista.
>>>>
>>>> Muchas gracias
>>>>
>>>> PD: No sé si tenga que ver, creo que no pero por las dudas lo consulto.
>>>> En
>>>> la carga del sistema, tanto cuando el internet como cuando no, me
>>>> aparece un
>>>> mensaje indicando "mpu-401 device not found or device busy".
>>>>
>>>> ¿Supongo sabes de que se trata MPU?
>>>>
>>>> Debes aportar más datos.
>>>>
>>>>
>>>>
>>>>
>>>> Tendrá como diez años. La aplicación neofetch arroja lo siguiente en
>>>> cuanto
>>>> a hardware y software:
>>>>
>>>> OS: Debian GNU/Linux 9.2 (stretch) x86_64
>>>> Model: P23G 1.0
>>>> Kernel: 4.9.0-4-amd64
>>>> CPU: Intel Pentium 4 3.20GHz (2) @ 3.2GHz
>>>> GPU: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics
>>>> Memory: 1940MB (originalmente tenía 512 MB)
>>>>
>>>> El comando lpsci (sin argumentos) indica lo siguiente:
>>>>
>>>>
>>>> 00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
>>>> Host
>>>> Bridge
>>>> 00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
>>>> Host
>>>> Bridge
>>>> 00:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
>>>> Host
>>>> Bridge
>>>> 00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
>>>> 00:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
>>>> Host
>>>> Bridge
>>>> 00:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
>>>> Host
>>>> Bridge
>>>> 00:01.0 PCI brid

Re: Problema con conexión a internet

[Alan]

El 23/11/17 a las 02:05, Emiliano Gabriel Reynoso escribió:
> Alan, 
> Consulta: verificaste el estado de network-manager al iniciar? 
>
>
>
> El 22 nov. 2017 22:33, "Felix Perez" <felix.listadeb...@gmail.com
> <mailto:felix.listadeb...@gmail.com>> escribió:
>
> El 22 de noviembre de 2017, 19:33, Alan <alan_laut...@yahoo.com.ar
> <mailto:alan_laut...@yahoo.com.ar>> escribió:
> > El 22/11/17 a las 18:38, Felix Perez escribió:
> >
> > El 22 de noviembre de 2017, 15:41, Alan
> <alan_laut...@yahoo.com.ar <mailto:alan_laut...@yahoo.com.ar>>
> > escribió:
> >
> > Saludos, lista. Desde hace tiempo tengo problemas en un viejo
> PC. Instalé
> > variedad de distribuciones GNU/Linux y el internet funciona.
> Apago el PC o
> > reinicio y ya no es posible conectarse. La "solución" es
> desenchufar y
> > volver a conectar para que se arregle.
> >
> > A que llamas "viejo" 1,2,3.. 10 años, ¿Qué hardware? ¿Desenchufar y
> > volever a conectar qué?¿Versión de Debian?
> >
> > Curiosamente en el Windows -que aún no le quité por el problema,
> dejándolo
> > como dual boot- el internet siempre anda bien, pero si entro a
> Debian y
> > luego de nuevo a Windows, no me es posible usar el internet sin
> desenchufar
> > el PC.
> > El comando "lspci -vmmnn" arroja lo siguiente en cuanto al
> controlador de
> > ethernet:
> >
> >
> > Slot:    00:12.0
> > Class:    Ethernet controller [0200]
> > Vendor:    VIA Technologies, Inc. [1106]
> > Device:    VT6102/VT6103 [Rhine-II] [3065]
> > SVendor:    Elitegroup Computer Systems [1019]
> > SDevice:    VT6102/VT6103 [Rhine-II] [0102]
> >
> >
> > ¿Están bien instalados los módulos VIA?
> >
> > Esa tarjeta de red funciona muy bien en debian, ¿Supongo es la
> > integrada? ya que creo que también había unas PCI.
> >
> > Busqué información en internet pero no encontré nada que
> sirviera, y otras
> > opciones no las pude probar por necesitar programas que ya no se
> encuentran
> > en los repositorios de Debian (modconf, por ejemplo).
> >
> > ¿Qué hiciste, probaste?
> >
> > ¿Alguien de la lista conoce alguna solución o se le ocurre algo
> que pueda
> > probar?
> >
> > Perdón pero los poderes psiquicos no los ocupo en la lista.
> >
> > Muchas gracias
> >
> > PD: No sé si tenga que ver, creo que no pero por las dudas lo
> consulto. En
> > la carga del sistema, tanto cuando el internet como cuando no,
> me aparece un
> > mensaje indicando "mpu-401 device not found or device busy".
> >
> > ¿Supongo sabes de que se trata MPU?
> >
> > Debes aportar más datos.
> >
> >
> >
> >
> > Tendrá como diez años. La aplicación neofetch arroja lo
> siguiente en cuanto
> > a hardware y software:
> >
> > OS: Debian GNU/Linux 9.2 (stretch) x86_64
> > Model: P23G 1.0
> > Kernel: 4.9.0-4-amd64
> > CPU: Intel Pentium 4 3.20GHz (2) @ 3.2GHz
> > GPU: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800
> Graphics
> > Memory: 1940MB (originalmente tenía 512 MB)
> >
> > El comando lpsci (sin argumentos) indica lo siguiente:
> >
> >
> > 00:00.0 Host bridge: VIA Technologies, Inc.
> CN700/VN800/P4M800CE/Pro Host
> > Bridge
> > 00:00.1 Host bridge: VIA Technologies, Inc.
> CN700/VN800/P4M800CE/Pro Host
> > Bridge
> > 00:00.2 Host bridge: VIA Technologies, Inc.
> CN700/VN800/P4M800CE/Pro Host
> > Bridge
> > 00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
> > 00:00.4 Host bridge: VIA Technologies, Inc.
> CN700/VN800/P4M800CE/Pro Host
> > Bridge
> > 00:00.7 Host bridge: VIA Technologies, Inc.
> CN700/VN800/P4M800CE/Pro Host
> > Bridge
> > 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
> > 00:09.0 Multimedia controller: Philips Semiconductors SAA7130 Video
> > Broadcast Decoder (rev 01)
> > 00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID
> > Controller (rev 80)
> > 00:0f.1 IDE interface: VIA Technologies, Inc.
> > VT82C586A/B/VT82C686/A/B/VT823x

Re: Problema con conexión a internet

[Alan]

El 22/11/17 a las 18:38, Felix Perez escribió:
> El 22 de noviembre de 2017, 15:41, Alan <alan_laut...@yahoo.com.ar> escribió:
>> Saludos, lista. Desde hace tiempo tengo problemas en un viejo PC. Instalé
>> variedad de distribuciones GNU/Linux y el internet funciona. Apago el PC o
>> reinicio y ya no es posible conectarse. La "solución" es desenchufar y
>> volver a conectar para que se arregle.
> A que llamas "viejo" 1,2,3.. 10 años, ¿Qué hardware? ¿Desenchufar y
> volever a conectar qué?¿Versión de Debian?
>
>> Curiosamente en el Windows -que aún no le quité por el problema, dejándolo
>> como dual boot- el internet siempre anda bien, pero si entro a Debian y
>> luego de nuevo a Windows, no me es posible usar el internet sin desenchufar
>> el PC.
>> El comando "lspci -vmmnn" arroja lo siguiente en cuanto al controlador de
>> ethernet:
>>
>>
>> Slot:00:12.0
>> Class:Ethernet controller [0200]
>> Vendor:VIA Technologies, Inc. [1106]
>> Device:VT6102/VT6103 [Rhine-II] [3065]
>> SVendor:Elitegroup Computer Systems [1019]
>> SDevice:VT6102/VT6103 [Rhine-II] [0102]
>>
>>
> ¿Están bien instalados los módulos VIA?
>
> Esa tarjeta de red funciona muy bien en debian, ¿Supongo es la
> integrada? ya que creo que también había unas PCI.
>
>> Busqué información en internet pero no encontré nada que sirviera, y otras
>> opciones no las pude probar por necesitar programas que ya no se encuentran
>> en los repositorios de Debian (modconf, por ejemplo).
> ¿Qué hiciste, probaste?
>
>> ¿Alguien de la lista conoce alguna solución o se le ocurre algo que pueda
>> probar?
>>
> Perdón pero los poderes psiquicos no los ocupo en la lista.
>
>> Muchas gracias
>>
>> PD: No sé si tenga que ver, creo que no pero por las dudas lo consulto. En
>> la carga del sistema, tanto cuando el internet como cuando no, me aparece un
>> mensaje indicando "mpu-401 device not found or device busy".
> ¿Supongo sabes de que se trata MPU?
>
> Debes aportar más datos.
>
>
>
>
Tendrá como diez años. La aplicación neofetch arroja lo siguiente en
cuanto a hardware y software:

OS: Debian GNU/Linux 9.2 (stretch) x86_64
Model: P23G 1.0
Kernel: 4.9.0-4-amd64
CPU: Intel Pentium 4 3.20GHz (2) @ 3.2GHz
GPU: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics 
Memory: 1940MB (originalmente tenía 512 MB)

El comando lpsci (sin argumentos) indica lo siguiente:


00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro
Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
00:09.0 Multimedia controller: Philips Semiconductors SAA7130 Video
Broadcast Decoder (rev 01)
00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID
Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB
1.1 Controller (rev 81)
00:10.1 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB
1.1 Controller (rev 81)
00:10.2 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB
1.1 Controller (rev 81)
00:10.3 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB
1.1 Controller (rev 81)
00:10.4 USB controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge
[KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem
Controller (rev 80)
*00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102/VT6103
[Rhine-II] (rev 78)*
01:00.0 VGA compatible controller: VIA Technologies, Inc.
CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)



Lo que hay que desenchufar y volver a conectar es el cable que alimenta
la fuente del CPU. Sacar y poner la fichita de la conexión a internet no
sirve de nada.

Con respecto a los módulos VIA, no tengo idea si están bien instalados.
Tampoco sé de qué se trata el MPU pero busqué información sobre el error
y leí que no era importante y además estaba relacionado con la parte del
sonido, no del internet, por lo q

Problema con conexión a internet

[Alan]

Saludos, lista. Desde hace tiempo tengo problemas en un viejo PC.
Instalé variedad de distribuciones GNU/Linux y el internet funciona.
Apago el PC o reinicio y ya no es posible conectarse. La "solución" es
desenchufar y volver a conectar para que se arregle.
Curiosamente en el Windows -que aún no le quité por el problema,
dejándolo como dual boot- el internet siempre anda bien, pero si entro a
Debian y luego de nuevo a Windows, no me es posible usar el internet sin
desenchufar el PC.
El comando "lspci -vmmnn" arroja lo siguiente en cuanto al controlador
de ethernet:


Slot:    00:12.0
Class:    Ethernet controller [0200]
Vendor:    VIA Technologies, Inc. [1106]
Device:    VT6102/VT6103 [Rhine-II] [3065]
SVendor:    Elitegroup Computer Systems [1019]
SDevice:    VT6102/VT6103 [Rhine-II] [0102]


Busqué información en internet pero no encontré nada que sirviera, y
otras opciones no las pude probar por necesitar programas que ya no se
encuentran en los repositorios de Debian (modconf, por ejemplo).
¿Alguien de la lista conoce alguna solución o se le ocurre algo que
pueda probar?

Muchas gracias

PD: No sé si tenga que ver, creo que no pero por las dudas lo consulto.
En la carga del sistema, tanto cuando el internet como cuando no, me
aparece un mensaje indicando "mpu-401 device not found or device busy".

Re: ¿Firefox 57 Quantum en Stretch?

[Alan]

El 17/11/17 a las 06:44, Iván Hernández Cazorla escribió:
> Buenas,
> Me gustaría saber si alguien de esta lista sabe si existe alguna fecha
> determinada o prevé cuando estará operativa la versión de Firefox 57
> para Debian 9.
>
> Yo no he encontrado nada en la red. No sé si ustedes tendrán algo a
> mano con lo que podrían ayudarme a despejar estas dudas. Admito que es
> más impaciencia que otra cosa. Además de que me pica mucho la
> curiosidad, ya que Firefox ESR va por la 52.5.0, e ignoro si la
> versión es la semejante a la versión de Firefox 52, o si su desarrollo
> es independiente y no sigue la misma línea.
>
> Gracias de antemano.
>
> Saludos,
> Iván

Puede que esté mal informado, pero tengo entendido que en la rama
estable solo se publicarán las versiones ESR. La actual ESR de Firefox
es la 52 y la próxima es la 59, que según el calendario de Mozilla
estará disponible el 13 de marzo del 2018.

Junto con Firefox 57 se liberó Firefox ESR 52.5, en la personalmente
noté mejoras de rendimiento. Esta versión se encuentra desde ayer en los
repositorios de Stretch, así que sólo hay que actualizar el sistema.

Si tu impaciencia es mucha podrías desinstalar Firefox ESR para que no
haya conflictos y descargar la versión 57 de Mozilla. Desempaquetas y
ejecutas el archivo "firefox". Si te gusta, podrías crear lanzadores en
el escritorio, en el menú, etc.

Igualmente, te advierto que Firefox 57 es muy nuevo y muchas extensiones
todavía no están disponibles. No sería mala idea esperar a la versión ESR.

Saludos

Problema de notificaciones en Debian Buster con Xfce

[Alan]

Saludos, lista. Hoy se me dio por actualizar de "stable" a "testing" en
una netbook. Lo noto algo más lento al sistema y además no me funciona
ninguna notificación. Incluso no aparecen notificaciones al presionar
las teclas para activar o cambiar el volumen (Fn + F3/F4/F5), o para
subir o bajar el brillo (Fn + F7/F8). Además, al usar estas
combinaciones de teclas no se produce el efecto esperado inmediatamente,
sino como después de 45 segundos.
Intenté un "apt install --reinstall xfce4-notifyd" pero no funcionó.
Tampoco sirvió purgar y volver a instalar.
¿A alguien más le pasó y pudo solucionarlo?
Gracias

Re: ¿Cual es la mejor versión de debian?

[Alan]

El 24/10/17 a las 14:28, Adolfo Maltez escribió:
> La testing :)
>
> 2017-10-24 11:24 GMT-06:00 Alex Napanga
>  >:
>
>

La mejor versión de Debian no es ni "stable", ni "testing", ni "sid": es
la que mejor se ajuste a tus necesidades.
Los nombres de cada rama nos rebelan su estado. Stable sería la versión
final de Debian, muy pulida para no contener errores (al menos en
teoría). Testing es la próxima versión de Debian, cuando aún no está
lista, y tiene la ventaja de poseer software más nuevo que la rama
estable (en teoría, también). Finalmente, "sid" es una versión inestable
que no está recomendada para usuarios comunes a menos que quieran tener
paquetes más nuevos que en "testing". También existe una rama
"experimental", que es aún más inestable.
Resumiendo, las versiones más usadas son la estable y la que está en
pruebas. Depende de tus preferencias o necesidades: si querés versiones
más nuevas de tus programas, usá "testing"; si tu prioridad es la
estabilidad del sistema, usá "stable", que después de todo es lo que
recomienda el equipo de Debian:
https://www.debian.org/releases/index.es.html

Saludos

No puedo poner tildes en QEMU

[Alan]

Saludos a todos. Uso el software QEMU para virtualizar distintos
sistemas operativos, utilizando la interfaz gráfica AQEMU. Todo funciona
perfecto, con el inconveniente que no puedo poner ciertos símbolos, como
por ejemplo las tildes, donde al intentar ponerlas aparece una ventana
emergente con la leyenda "Warning: no scancode found for keysym 314".
Busqué en internet la solución pero no obtuve buenos resultados. ¿Por
casualidad alguien de la lista sabe como arreglar el error?
Muchas gracias.

Re: compartir carpetas debian windows

[Alan]

El 31/07/17 a las 17:49, Luis Angel escribió:
>
> Es muy molesto que una tarea tan simple como compartir archivos entre
> sistemas operativos differentes sera tan dificil y cansado, es por eso
> que nadie quiere a debian, por lo complejo de su configuración, llevo
> 3 meses intentando hacer esta compartición, instalando samba, dando
> permisos, y un problema enorme, nomás no  puedo, conecto dos
> computadoras windows y en seguida se encuentran, hagan sistemas
> operativos fáciles de configurar! no es posible que tengo
> usando debian 10 años y en lugar de que con el tiempo sea más facil,
> cada vez lo hacen más dificil, les explicaré, hacerlo sencillo
> significa no tener que usar la línea de comandos queremos que el
> sistema sea una herramienta de trabajo, y no el trabajo en sí mismo,
> seguramente ustedes son todos ingenieros en sistemas, pero los
> usuarios comunes no lo somos, y uno se aleja de linux cuando una tarea
> tan simple requiere tantas operaciones, 
>
>
> ¿COMO PUTOS COMPARTO UNA CARPETA EN DEBIAN 9 PARA PASAR ARCHIVOS A
> WINDOSWS 7'

Yo no soy ingeniero de sistemas, sólo un simple usuario, y me hallo muy
a gusto en Debian.

Por lo general, las personas con conocimientos más avanzados que están
subscriptas a la lista tratan de colaborar con las dudas de los demás.
Sería bueno recordar que Debian es un proyecto comunitario y no una
empresa. Esta lista se mantiene gracias a la buena voluntad de los otros
usuarios, y ninguno recibe un salario por responder preguntas.

Debian tiene una filosofía propia, una manera de hacer las cosas. Si no
estás de acuerdo con ella, existen otras distribuciones GNU/Linux y
otros sistemas operativos que podés probar, o también crear el tuyo
propio o pagarle a alguien para que te cree uno a medida.

Conservemos el respeto y los buenos modos, especialmente cuando estamos
recibiendo un gran producto sin colaborar en absolutamente nada.

Process kill on logout

[Alan Chandler]

I have just upgraded from Jessie to Stretch and my arrangement where I 
logout and then mythtv shuts my computer down and sets a wakeup time 
just before the next recording time has stopped working.  In the past 
when that happens I have set up "screen", and entered an used "sleep 1m 
&& who -u" to find out why its not detecting me as logged out.  I set 
that command running, detach from screen, logout, ensure the minute is 
up, log back in and re-enter my screen session to see what it made of 
things.


That no longer works.  It appears that systemd now kills off all 
processess associated with the user - or rather I found a bug report 
that said that had happened about a year ago as the default had changed. 
That bug report said that /etc/systemd/logind.conf should allow you to 
change that default behaviour by setting KillUserProcesses=no.



Firstly, although commented out, that setting is already showing "no", 
which is supposed to mean that this is the default value anyway.  
Secondly setting it explicitly to "no" doesn't work, screen sessions 
still appear to have been wiped out by the act of logging out.


Can anyone tell me what to do to allow screen sessions to survive logout.




--
Alan Chandler
http://www.chandlerfamily.org.uk

Re: Memorias USB montadas como sólo lectura en Thunar

[Alan]

El 23/06/17 a las 19:20, Paynalton escribió:
>
> El vie., 23 de jun. de 2017 a la(s) 16:31, Alan
> <alan_laut...@yahoo.com.ar <mailto:alan_laut...@yahoo.com.ar>> escribió:
>
> Estimados, les escribo para contarles un inconveniente que me
> ocurre con
> Thunar, el gestor de archivos predeterminado de Xfce y que
> acostumbro a
> usar.
> Al introducir un pendrive o conectar un reproductor de música no soy
> capaz de transferir archivos y aparece una ventana diciéndome que el
> destino es de sólo lectura. Cambié los permisos del directorio
> /media y
> /media/usuario a "Lectura y escritura", pero no ha funcionado. La
> única
> forma de transferir archivos es utilizando Thunar como superusuario,
> algo que en ocasiones puede resultar incómodo. Lo curioso es que en
> Nautilus no tengo ningún tipo de problema y puedo pasar archivos a mis
> memorias USB sin necesidad de utilizar la cuenta de root o sudo.
> Comento este inconveniente para saber si se trata de un bug
> generalizado
> o de una mala configuración de mi sistema. Si se trata del segundo
> caso
> -lo cual es probable- agradecería algún consejo o recomendación para
> solucionar el problema.
>
> También aprovecho el hilo para comentar que tuve dificultades al
> desmontar particiones, siendo el causante el proceso "thumblerd".
>
> Muchas gracias por su tiempo.
> Saludos
>
>
> con la memoria insertada y abierto, podrías darnos la salida del
> comando 'mount' ??? 

Misteriosamente el problema se arregló solo tras comentarlo en la lista...

Lo único que hice fue preparar un pendrive booteable con el netinstall
de Debian 9, mediante la aplicación "gnome-multi-writter". Luego de eso
todos los dispositivos USB dejaron de tener problemas en Thunar. Imagino
que MultiWritter (que solicita permisos de root) habrá modificado alguna
configuración, pero es sólo una hipótesis.

Dejo el hilo abierto un tiempo más por si alguien puede echar luz sobre
el asunto y brindar una solución más "profesional".

El comando mount (tras arreglarse el problema) arroja lo siguiente:

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs
(rw,nosuid,relatime,size=1951436k,nr_inodes=487859,mode=755)
devpts on /dev/pts type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=392536k,mode=755)
/dev/sda2 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs
(rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/perf_event type cgroup
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/pids type cgroup
(rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpuset type cgroup
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/memory type cgroup
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup
(rw,nosuid,nodev,noexec,relatime,devices)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs
(rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=8926)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
/dev/sda1 on /boot/efi type vfat
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
/dev/sda4 on /home type ext4 (rw,relatime,data=ordered)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/1000 type tmpfs
(rw,nosuid,nodev,relatime,size=392532k,mode=700,uid=1000,gid=1000)
/dev/sdb1 on /media/alan/Pendrive type vfat
(rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)

Memorias USB montadas como sólo lectura en Thunar

[Alan]

Estimados, les escribo para contarles un inconveniente que me ocurre con
Thunar, el gestor de archivos predeterminado de Xfce y que acostumbro a
usar.
Al introducir un pendrive o conectar un reproductor de música no soy
capaz de transferir archivos y aparece una ventana diciéndome que el
destino es de sólo lectura. Cambié los permisos del directorio /media y
/media/usuario a "Lectura y escritura", pero no ha funcionado. La única
forma de transferir archivos es utilizando Thunar como superusuario,
algo que en ocasiones puede resultar incómodo. Lo curioso es que en
Nautilus no tengo ningún tipo de problema y puedo pasar archivos a mis
memorias USB sin necesidad de utilizar la cuenta de root o sudo.
Comento este inconveniente para saber si se trata de un bug generalizado
o de una mala configuración de mi sistema. Si se trata del segundo caso
-lo cual es probable- agradecería algún consejo o recomendación para
solucionar el problema.

También aprovecho el hilo para comentar que tuve dificultades al
desmontar particiones, siendo el causante el proceso "thumblerd".

Muchas gracias por su tiempo.
Saludos

Re: No puedo hacer "tapping" en Debian 9

[Alan]

El 18/06/17 a las 16:33, divagante escribió:

> El 18/06/17 a las 16:23, Alan escribió:
>> Saludos a todos. Hoy instalé Debian 9 en mi laptop y lo estoy
>> configurando. El único inconveniente que tengo hasta ahora es que no
>> puedo activar la función "tap to click" de mi touchpad, así como el
>> desplazamiento en el borde.
>> Las soluciones que encontré en internet no funcionaron, hablando casi
>> todas ellas de editar /etc/x11/xorg.conf-d/synaptics.conf
>> Es por eso que recurro a la lista, a ver si alguien me puede dar una
>> mano.
>> Estoy usando Xfce como entorno de escritorio y el modelo de touchpad
>> es "ETPS/2 Elantech Touchpad".
>> Muchas gracias de antemano.
>
> Hola alan! me sucedio lo mismo. Lo que hay que hacer es esto:
>
> edita el archivo de configuracion como root:
>
>
> nano /usr/share/X11/xorg.conf.d/40-libinput.conf (en vez de nano tu
> editor favorto)
>
> En la seccion agregar la linea: Option  "Tapping" "on". !uedando asi:
>
> Section "InputClass"
> Identifier "libinput touchpad catchall"
> MatchIsTouchpad "on"
> MatchDevicePath "/dev/input/event*"
> Option  "Tapping" "on"
> Driver "libinput"
> EndSection
>
>
> Reinicia las Xs y guala!! Saludos
>
> Fuente y mas info: https://wiki.archlinux.org/index.php/Libinput
>
Muchas gracias por tu ayuda. Hice lo que me dijiste y funcionó perfecto.
Además revisé el enlace que dejaste, que me resultó muy útil para hacer
otros cambios.

Saludos

Re: Bluray Debian ISOs: Which app(s) burns bluray images?

[Alan Ianson]

On Mon, 19 Jun 2017 00:35:32 +0200
"Thomas Schmitt"  wrote:
 
> > but when I did, I used K3b or wodim from the command line.
> 
> I omitted wodim from my answer, because it can hardly do DVD and would
> do Blu-ray only by accident. One should use it only for burning CD.

I never knew that. I'm going to get to know xorriso & friends better.. :)

Re: Bluray Debian ISOs: Which app(s) burns bluray images?

[Alan Ianson]

On Sun, 18 Jun 2017 12:25:59 -0400 (EDT)
Anonymous  wrote:

> With downloaded Bluray ISO images, I need to use
> a burning application in Linux which supports blank
> Bluray medium. I know I could try Windows options
> such as ImgBurn via Wine, but I'm hoping for a Linux
> application. Thanks.

I haven't burned a CD/DVD/BD in some time now, I always use a USB drive 
nowadays but when I did, I used K3b or wodim from the command line.

No puedo hacer "tapping" en Debian 9

[Alan]

Saludos a todos. Hoy instalé Debian 9 en mi laptop y lo estoy configurando. El 
único inconveniente que tengo hasta ahora es que no puedo activar la función 
"tap to click" de mi touchpad, así como el desplazamiento en el borde.Las 
soluciones que encontré en internet no funcionaron, hablando casi todas ellas 
de editar /etc/x11/xorg.conf-d/synaptics.confEs por eso que recurro a la lista, 
a ver si alguien me puede dar una mano.Estoy usando Xfce como entorno de 
escritorio y el modelo de touchpad es "ETPS/2 Elantech Touchpad".Muchas gracias 
de antemano.

Re: Manual para instalación de servidor Debian 8 con servidor bd postgresql

[Alan]

Hola, yo no sé nada de servidores pero quizás en este libro haya algo
que pueda servirte:
https://debian-handbook.info/download/es-ES/stable/debian-handbook.pdf

Saludos


El 15/05/17 a las 18:21, Oscar Martinez escribió:
> Buenas tardes grupo, estoy entrando al mundo de debian por primera vez
> y me a costado conseguir informacion o un manual como se monta un
> server de base de datos en debian 8
>
> si alguien seria tan amable de indicarme un link o tiene un tutorial
> estare muy agradecido
>
> ya instale mi servidor en debian 8 y mi bd en postgresql  9.6  
>
>
> me falta ajustar la configuracion del servidor para que puedad apceder
> desde admin a la base de datos via web o remotamente gracias 

Problema con modem 4G

[Alan]

Saludos a todos. Tengo un conocido que tiene un extraño inconveniente
con un modem 4G de Movistar. El modelo es un Huawei E1756.

Resulta que ese modelo en algunas distribuciones GNU/Linux anda
perfecto, y en otras no hay forma de hacerlo andar...

Funciona en una distro con un kernel cargado de componentes privativos
como Ubuntu (lo que usa ahora) pero también en Trisquel, que es 100%
software libre.  Sin embargo, en otras distros como Xubuntu y Fedora no
anda. Debian, lamentablemente, está en este último grupo, aunque en
Canaima, que está basada en Debian, funciona bien.

Me he cansado de buscar información al respecto y de probar distintos
métodos, y ninguno sirve. Aprovechando mi reciente descubrimiento de
esta lista comparto el inconveniente por si alguien sabe cómo
solucionarlo o, por lo menos, sabe a qué se debe (confieso que me
intriga el tema).

Aclaro también que probamos con diversos entornos de escritorio y el
asunto no parece pasar por ese lado. En Windows el modem se conectaba
mediante un programa llamado "Escritorio Movistar" pero en GNU/Linux no
hay tal cosa (existió en su momento pero todas las páginas están
borradas, y aunque se "revivan" con The Internet Archive no queda nada
útil).

Muchas gracias por su tiempo.

Saludos cordiales.

Re: Crear ISO personalizada de Debian

[Alan]

Muchas gracias por su amabilidad, Javier y Alejando. Voy a fijarme en
las recomendaciones que me dieron.

Saludos


El 06/05/17 a las 17:41, Alan escribió:
> Saludos a todos, me registré hoy en la lista.
>
> Quisiera modificar una ISO de Debian con Xfce para que ya traiga
> instaladas ciertas aplicaciones y esté configurado de determinada
> manera. Investigando sobre el tema encontré esta página, donde hay una
> guía utilizando un programa llamado "Systemback" y una máquina virtual:
> https://www.linuxadictos.com/crear-distribucion-linux.html
>
> Creo que funcionará, pero quería saber la opinión de personas más
> experimentadas, para ver si les parecía adecuado este método o conocen
> uno mejor. Aclaro que soy un simple usuario y no tengo grandes
> conocimientos de informática.
>
> Muchas gracias
>

Crear ISO personalizada de Debian

[Alan]

Saludos a todos, me registré hoy en la lista.

Quisiera modificar una ISO de Debian con Xfce para que ya traiga
instaladas ciertas aplicaciones y esté configurado de determinada
manera. Investigando sobre el tema encontré esta página, donde hay una
guía utilizando un programa llamado "Systemback" y una máquina virtual:
https://www.linuxadictos.com/crear-distribucion-linux.html

Creo que funcionará, pero quería saber la opinión de personas más
experimentadas, para ver si les parecía adecuado este método o conocen
uno mejor. Aclaro que soy un simple usuario y no tengo grandes
conocimientos de informática.

Muchas gracias

[no subject]

[Alan Hutchinson]

-- 
Alan Hutchinson
Hi people just a small note to tell you that, I am having a problem in
Debian 8 Jessie ,I have bean trying to run cups.service and it just wont
run, when using system d, and I type systemctl start cups.service, I get
the error

Process:400 Execstart=/usr/sbin/cupsd -f (code=killed,signal=term)

Main Pid:400 (code=killed,signal=term man 7 signal

what do I have to read up on to get my cups.service up and running againe

Re: Sound on jessie

[Alan McConnell]

- Original Message -
From: "Lisi Reisz" <lisi.re...@gmail.com>
To: debian-user@lists.debian.org
Sent: Saturday, September 17, 2016 5:56:13 PM
Subject: Re: Sound on jessie

On Saturday 17 September 2016 14:43:04 Alan McConnell wrote:
> Alas for the days of wheezy, when everything _worked_!!

Wheezy is LTS (though admittedly more successfully for servers), so if 
everything Just Worked, and you liked it, why did you change?  There are 
indeed valid reasons, but what is yours?
   Lisi, as you must know, Debian moves on; eventually Stable becomes
   Old-stable, and after a while support, especially security support
   disappears.  I have been using Debian at least since Sarge.  I forget
   the different Toy Story names(potato, squeeze. etc), but I eventually
   went to wheezy, which is now very old.  I have never had trouble
   moving from one Debian to the next.  Until now.  jessie has given
   me immense trouble, vastly more than any other installation.  Knowing
   what I know now: perhaps I should have stayed with wheezy until
   stretch became stable.

   I hope that answers your question.  I don't think the above answer helps
   you, or anyone else, to solve my problems(the one remaining one, after
   all this time and effort, is _sound_/alsa).  But I am trying to be
   cooperative.

   In another related post you ask:
By what method did you try and what reason have you to think that it is
already installed?
   You are referring to alsa.  My answer: I have alsa-utils in my
   /etc/init.d/, and I have looked at this script.  I get no complaint
   from it upon booting.

Best wishes,

Alan

Re: Sound on jessie

[Alan McConnell]

- Original Message -
From: "Joe" <j...@jretrading.com>
To: debian-user@lists.debian.org
Sent: Saturday, September 17, 2016 3:47:10 PM
Subject: Re: Sound on jessie

On Sat, 17 Sep 2016 12:47:23 -0400 (EDT)
Alan McConnell <a...@his.com> wrote:


> 
>  This suggests to me, and I hope to my readers here, that
> there is something wrong with the way  alsa  works, or doesn't work,
> here. I can't imagine what the difficulty is, since the cogent
> suggestions that have been made here have not worked.
> 
> Perhaps others have some ideas?

First, what did you try, and with what result?
  I tried to install alsa.  No result -- I think it is already installed.
  I installed everything else I could with a name involving alsa.
  I have runps aux | grep alsa   with no result.
  As already described, I tried alsamixer.

Here is the result ofcat /proc/asound/cards:

 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xdf32 irq 142
 1 [NVidia ]: HDA-Intel - HDA NVidia
  HDA NVidia at 0xdf08 irq 17

 I have no idea what the above means.  Presumably one or both are
 functional.

 I remind you and others that my sound works splendidly when I switch 
 OSes and log into my Windoze.

Thank you for showing an interest.

Alan

Re: Difficulties with Firefox/iceweasel

[Alan McConnell]

- Original Message -
From: "Felix Miata" <mrma...@earthlink.net>
To: debian-user@lists.debian.org
Sent: Saturday, September 17, 2016 1:26:23 PM
Subject: Re: Difficulties with Firefox/iceweasel

Alan McConnell composed on 2016-09-17 13:05 (UTC-0400):


> I'll have to log in as root to do this, I'm sure.  But there may be other
> hazards I am not aware of.  I hope for cogent thoughts on this.

There's no compulsion to have a separate partition for /tmp. Simply remove 
that small partition from /etc/fstab.
  Just did it, and rebooted.  And I set Beeth's Fifth to playing on
  youtube for five minutes -- of course there was no sound -- and
  I had no problems.

So thanks for your helpful and effective suggestion, Felix!

Alan

Difficulties with Firefox/iceweasel

[Alan McConnell]

During my experimentation with Iceweasel, described in another post, I
have received warnings from the OS that /tmp was filling up.  It seems
that when running a video a buffer is opened in /tmp, and /tmp fills up
rapidly.  At the moment, df /tmp tells me that 3% of /tmp is used.  When
I'm trying to play a video, only 1% of /tmp is available, and the video
grinds to a halt.

My partition table says that /tmp is partition 10, with 50MB, and partion
11 is my /home, with 750GB.  [  I don't know why I made my /tmp so small. ]

Now to my question.  Can anyone think of any hazard in the following
procedure:  1.  Back up my /home completely(I have a USB stick that will
take what I have on it.)  2.  Run parted to delete partitions 10 and 11,
then create a new partition 10, with, say, a Gig on it, and then create
a new partition 11, name it /home . . . 3.  Put all my backed up stuff
on the new /home.

I'll have to log in as root to do this, I'm sure.  But there may be other
hazards I am not aware of.  I hope for cogent thoughts on this.

TIA,

Alan

Re: Sound on jessie

[Alan McConnell]

- Original Message -
From: "deloptes" <delop...@gmail.com>
To: debian-user@lists.debian.org
Sent: Saturday, September 17, 2016 12:17:55 PM
Subject: Re: Sound on jessie

Alan McConnell wrote:

> 
> 
> - Original Message -
> From: "Anthony Baldwin" <baldwinling...@gmx.com>
> To: debian-user@lists.debian.org
> Sent: Saturday, September 17, 2016 7:56:48 AM
> Subject: Re: Sound on jessie
> 
> 
> I was having a similar problem just last week after an update>safe
> upgrade.. After scratching my head for several days and trying everything
> I could think of (including querying this list), I found I had something
> called PulseAudio-volume-control installed, a graphical tool to manage
> volume for PA , and, when I found it, it showed "analog output" as muted
> (no idea why), I unmuted it, and had my sound back!
> If you can't find it, install it and check all the volume settings.
> It's listed in the repos as pavucontrol.
> so just apt-get install pavucontrol .
>   (or aptitude if you prefer)
> aptitude install pavucontrol
>  Many thanks for your suggestion, Anthony.  But I've already tried
>  pavucontrol, which I had installed quite a while ago.  So I'm still
>  stymied.
> 
>  Alas for the days of wheezy, when everything _worked_!!
> 
> Alan, who is pleased at least to be able to get on line from his jessie
> install

Usually there is a problem with something muted, so if pulse is OK go down
and check alsamixer.
 I have tried that. Both channels(?) are set to 100, and I can move
     them lower with the Arrow keys.  Otherwise I don't know how to
 operate this ncurses device.

Now that we know Alan is using Ubuntu, he could even try ubuntu live in
former or current version to compare.
   I am not part of that "we".  I am not using Ubuntu.  Furthermore
 if I want to hear some nice music or listen to a Sanders speech on
 youtube, I get out of jessie, run my Windoze, use the Edge brower
 and go to youtube, where the sound works just great.

 This suggests to me, and I hope to my readers here, that there is
 something wrong with the way  alsa  works, or doesn't work, here.
 I can't imagine what the difficulty is, since the cogent suggestions
 that have been made here have not worked.

Perhaps others have some ideas?

Alan

Re: Sound on jessie

[Alan McConnell]

- Original Message -
From: "Anthony Baldwin" <baldwinling...@gmx.com>
To: debian-user@lists.debian.org
Sent: Saturday, September 17, 2016 7:56:48 AM
Subject: Re: Sound on jessie


I was having a similar problem just last week after an update>safe upgrade..
After scratching my head for several days and trying everything I could 
think of (including querying this list), I found I had something called 
PulseAudio-volume-control installed, a graphical tool to manage volume 
for PA , and, when I found it, it showed "analog output" as muted (no 
idea why), I unmuted it, and had my sound back!
If you can't find it, install it and check all the volume settings.
It's listed in the repos as pavucontrol.
so just apt-get install pavucontrol .
  (or aptitude if you prefer)
aptitude install pavucontrol
 Many thanks for your suggestion, Anthony.  But I've already tried
 pavucontrol, which I had installed quite a while ago.  So I'm still
 stymied.  

 Alas for the days of wheezy, when everything _worked_!!

Alan, who is pleased at least to be able to get on line from his jessie install

Sound on jessie

[Alan McConnell]

For some reason, my sound doesn't work on my new machine with its present
jessie install.  It worked on my old machine(which had jessie) and it
works fine here on Windoze(I use youtube to play old Bernie Sanders' speeches,
or Mozart).  So what do I have to do?  I can't find alsa to install, and
pulsesudio is already installed.

Any and all suggestions/fixes appreciated.  Please spare the imprecations and
chastisements!

Alan

Test of Windoze Copy and Paste

[Alan McConnell]

Viva yo!  I can now Copy and Paste, as a kind and knowledgeable user
prescribe.

What is below is my very own fstab, much sought after by certain parties
a while back.  It has absolutely no significance or relevance for anyone 
anymore, so this post can and should be Deleted/ignored.


#
#

# / was on /dev/sda7 during installation
UUID=498875eb-a8ee-4190-bdfe-d3730c6f77dd /   ext4
errors=remount-ro 0   1

# /boot was on /dev/sda6 during installation
UUID=94c42b91-e970-40a0-b7b9-dadadc3f7091 /boot   ext4defaults  
  0   2

# /home was on /dev/sda11 during installation
UUID=39977844-fb29-4c61-b345-e0654ee1cb08 /home   ext4defaults  
  0   2

# /tmp was on /dev/sda10 during installation
UUID=e0233918-dcea-4b52-8fcd-51fcb183e5fe /tmpext4defaults  
  0   2

# /usr was on /dev/sda8 during installation
UUID=4fc044b4-7a04-45ef-81a9-080aeda16cd9 /usrext4defaults  
  0   2

# /var was on /dev/sda9 during installation
UUID=9611f2ae-02d5-437a-bae2-3f735b103cef /varext4defaults  
  0   2

# swap was on /dev/sda12 during installation
UUID=a1ffabcf-c93b-4a67-ae2c-003c3252b353 noneswapsw
  0   0
/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0

# Alan added the line below on 11 Sep 2016

/dev/sdb1   /mnt   auto user, noauto  0   0

Re: NTFS access on Debian boot

[Alan McConnell]

- Original Message -
From: "Felix Miata" <mrma...@earthlink.net>
To: debian-user@lists.debian.org
Sent: Thursday, September 15, 2016 10:42:22 PM
Subject: Re: NTFS access on Debian boot

Alan McConnell composed on 2016-09-15 21:02 (UTC-0400):
 
> Felix Miata composed:

>> I'll provide a seed for you to try to fix on your own. This is from Jessie
>> on a multiboot Dell that includes Windows 10:

>> # grep ntfs /etc/fstab
>> /dev/sda6 /win/C ntfs-3g 
>> nofail,users,gid=100,fmask=0111,dmask=,locale=en_US.UTF-8 0 0

> Already this doesn't work. 

Of course it doesn't. A seed isn't a fruiting plant. It's not ready for cut and
paste.
Hmm . . . a good aphorism, I guess.

However, what _does_ work is the command  'blkid'  Its output for my
/dev/sda3 is: LABEL="OS"!  !   So much for the adherents here of
os-prober(You know who you are!)

After further exploration, I found that the command to mount the
Windoze system is: mount UUID="d . . ." /mnt2.  The 'ddd. . . " is
a sixteen digit string given by the blkid command.  And /mnt2 is another
mount point I created, anticipating this use.

With this I can, as root or as user, cd to /mnt2 and explore the arcana
of Windows 10.  I didn't try copying to or from /mnt2, since I was
afraid of disrupting the Windoze system.

Perhaps a lurking installer maintainer can pick up on this.  It
shouldn't be hard to set up a grub file with the capacity to install
Windoze, if desired.  Or to put a mount point into fstab.



of this is irrelevant, because I install and setup Grub myself, writing my own
primary bootloader menu, including in it whatever I please. I can load Grub
from the Windows boot menu if and when I please as well.
There is an enviable talent!  I don't think I'll need more than I
presently have.  My hope is still to get jessie working as well as
wheezy did.  I can now use X11, but I still need to get my jessie
connected to the Internet.  I have a message about that to reply to.

Thanks, Felix, and best wishes to all you other folk!

Alan

Re: internet connectivity from Comcast

[Alan McConnell]

- Original Message -
From: "Felix Miata" <mrma...@earthlink.net>
To: debian-user@lists.debian.org
Sent: Thursday, September 15, 2016 2:20:54 PM
Subject: Re: internet connectivity from Comcast

Alan McConnell composed on 2016-09-15 13:36 (UTC-0400):
 
> It certainly isn't DSL.  I have an Ethernet cable running from my machine
> to a Comcast provided "modem" -- except that it is called a router.  Quite

Called a "router" by whom, and where? Maybe help could better be forthcoming
if you announced its brand name and a model number. From the description so
far in this thread, yours seems to be one of those boxes that combine modem,
router, switch and firewall. Does it also provide wireless?
I don't think so:  the little box on my desk is made by 
 Cisco.   Model number:  LinksysWUMC710

> Also: although ALSA and pulse-audio are installed on the Jessie side, I get
> no sound there...

Different and new problem belongs in a virgin thread.
 One will be forthcoming tomorrow.

This too belongs in a separate thread, but I'll provide a seed for you to try
to fix on your own. This is from Jessie on a multiboot Dell that includes
Windows 10:

# grep ntfs /etc/fstab
/dev/sda6 /win/C ntfs-3g 
nofail,users,gid=100,fmask=0111,dmask=,locale=en_US.UTF-8 0 0
 Already this doesn't work.  I put my /etc/fstab on a USB stick which has a 
VFAT file
 system on it, and my Windoze made a most satisfying chime when I stuck the 
stick
 into one of the sockets on my USB splitter.   I would give you the whole 
short text
 file if I could swipe my mouse over it.  But this is no go in Windoze, and 
I don't
 know how to Copy and Paste in the Windoze world.  So I'll just say here 
that my
 fstab simply enumerates the partitions I made when I installed.  Those are 
/dev/sda3,
 /dev/sda4, etc.  No mention of /dev/sda1, which is I believe called C: in 
the Windoze
 world.  I have my fstab, on E:, open as I write, but the wretched Notepad 
pays no
 attention to the Unix 'CR's !  !  Takes me back decades!.  

 This is another failure of the installer failing to recognize that there 
is another OS
 on my hard drive.  There is a class of people on this E-list who seem to 
think that
 the Jessie installer couldn't possibly be expected to recognize a Windoze 
OS, especially
 since Windows 10 is "so new".  My reaction is: codswallop!

 Thanks for your helpful attempt, Felix.  Were your examples from a box 
with Windoze already
 on it?

Alan

Re: internet connectivity from Comcast (was: How to get Jessie to run...)

[Alan McConnell]

- Original Message -
From: "Felix Miata" <mrma...@earthlink.net>
To: debian-user@lists.debian.org
Sent: Wednesday, September 14, 2016 7:05:50 PM
Subject: Re: internet connectivity from Comcast (was: How to get Jessie to 
run...)

Alan McConnell composed on 2016-09-14 17:11 (UTC-0400):

> My final problem is: how to get my Jessie to get on line.  I don't think this 
> is
> anything anyone here can help me with, since I live in a retirement community
> which has a huge contract with Comcast.

Is it a cable account, or is it a DSL account? Appropriate help from here, 
should you choose to accept any, depends on your answer.
It certainly isn't DSL.  I have an Ethernet cable running from my 
machine
to a Comcast provided "modem" -- except that it is called a router.  
Quite
obviously it works well from my Windoze side(I am using MS Edge the M$ 
new
browser) to dial into mail.his.com, which uses the afore-mentioned 
Zimbra

Any suggestions you can give me would be welcome, especially since I 
know
you know your stuff.

Also: although ALSA and pulse-audio are installed on the Jessie side, I 
get
no sound there(I have a couple of videos and some mp3s to test on.  
They played
well back in the Golden Days of Wheezy.  Maybe you have suggestions 
about
how to get sound working under Jessie?  Needless to say, I can play 
Donald
Trump speeches and Mozart on youtube from this present Edge browser, 
which
hasn't crashed once(iceweasel, under Jessie, used to crash continually; 
it
worked fine under wheezy)

And if Brian is reading this, I remind him that he is going to tell me 
how
to use Jessie to copy to and from my Windows 10.  But he may have given 
up
    with his efforts to "help" me.

Alan

Re: How to get Jessie to run at boot time -- Problem solved

[Alan McConnell]

- Original Message -
From: "Brian" <a...@cityscape.co.uk>
To: debian-user@lists.debian.org
Sent: Wednesday, September 14, 2016 5:09:12 PM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

> What is "unenlightening" to you may not be unenlightening to others;
> trust me on that. "garbage" is *your* value judgement; 
>  No, I'm going to insist on my "garbage" denotation.  Since I have a 
> very
>  acceptable way of going from one OS to another, your input on what 
> os-prober
>  returned to me is of little interest to me, and much less to the 
> other members
>  of this E-list, I'm sure.

You can insist on what you want. It is easy when only you know what the
the output is.
I've seen error messages before.




>  an expert programmer, which I used to be but am not any more, could 
> put those
>  few simple steps into a "first of all" window.  Maybe a simple grub 
> file?

That's fine; it does what you want and will serve you well. Stick with
it. but forget about involving GRUB.
  But a flow chart to do it would be easy:
  Read input
 if input=L then
 do nothing
 else if input=W, then
 change boot method to Windows Boot Manager
 else
 return to read input
 fi
Something like that could be easily implemented, methinks.  But 
I'm
not going to do it.




>  Yes.  If I could move stuff from my Windows OS to my Jessie, and vice
>  versa, that would be a big help.  Any suggestions from anyone about 
> that?
>  Linux used to be able to go into MS-DOS and put files there and get 
> files
>  out of there.  Has anyone any information on that?

I rather think there is an answer in the response you quoted.
 I didn't see it.  Remind me.




>xorg(or maybe it was x11), and my 'startx', from my old 
> wheezy(fortunately
>saved) worked, after I'd done a few tweeks to my .xinitrc.  I tried my
>old beloved sawfish(now wmctl) but that didn't work as well as 
> metacity.

Good. (Your technique is extraordinary but comments on it are outside
the scope of this thread).
 Thank you!  I would rather start off with a X-less tty1 and then enter 
X
 with my own choice of what to run, how the background looks, etc.  
startx,
 with a good .xinit, does all I want.  Simplicity, dear my lord,
 makes computing yare. 



> a username and password which got me, and keeps me, online . . . but only for 
> the
> Windoze side.  I gotta do some exploring to see if I can make this work with 
> Jessie.

I'm confident you are resourceful and will manage.
 I trust that your confidence in me is not misplaced.

Alan

Re: How to get Jessie to run at boot time -- Problem solved

[Alan McConnell]

- Original Message -
From: "Brian" <a...@cityscape.co.uk>
To: debian-user@lists.debian.org
Sent: Wednesday, September 14, 2016 1:51:50 PM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

On Wed 14 Sep 2016 at 11:34:31 -0400, Alan McConnell wrote:

> From: "Felix Miata" <mrma...@earthlink.net>
> 
> It does seem curious that the Debian installer would need knowledge of a 
> particular Windows version in order to provide a boot menu selection for it, 
> rather than simply having one that says "Windows", booting from whatever 
> non-native/NTFS filesystem it happens to find containing anything resembling 
> boot sector code.

This following quotes beginning with > are from Alan McConnell.

>  Yep.  I have been back to my Jessie in the meantime, and run 
> os-prober.
>  I didn't attempt to copy down on a piece of paper what it wrote; 
> trust me
>  that it was unenlightening garbage.
   Ah. That's good.  Your E-mail reader seems to respect my indentations.  
Others
   don't, alas.  Do you perchance use mutt?

What is "unenlightening" to you may not be unenlightening to others;
trust me on that. "garbage" is *your* value judgement; 
 No, I'm going to insist on my "garbage" denotation.  Since I have a 
very
 acceptable way of going from one OS to another, your input on what 
os-prober
 returned to me is of little interest to me, and much less to the other 
members
 of this E-list, I'm sure.

 But I'd like to defend what Lisi calls a "kludge".  Here is what I do: 
when I
 boot, or reboot my machine, if I do nothing I get my Jessie, which is 
what I
 want.  If I want to go to Windoze, I gotta hold the F12, as Felix 
Mieta taught
 me several moons ago, and then I get put into a nice menu: Choose the 
boot
 manager.  I use my Arrow keys to get to Windows boot manager, and 
voila! in a
 few seconds I'm in Windoze.  Not so difficult after all.  And I would 
think that
 an expert programmer, which I used to be but am not any more, could 
put those
 few simple steps into a "first of all" window.  Maybe a simple grub 
file?


We Debian users yearn for the day when copy 'n paste and USB sticks are
invented. It will make things so much easier to move information (which
is severely lacking from you in this thread) about.
 Yes.  If I could move stuff from my Windows OS to my Jessie, and vice
 versa, that would be a big help.  Any suggestions from anyone about 
that?
 Linux used to be able to go into MS-DOS and put files there and get 
files
 out of there.  Has anyone any information on that?

> > Should you be game to try installing Jessie again, you might try a network 
> > installation started via a Stretch installer. 
>  Jeez!  I can't even run X11 on my present install(*) let alone get on
>  line.
   That situation has changed as of just an hour ago.  I did a reinstall of
   xorg(or maybe it was x11), and my 'startx', from my old 
wheezy(fortunately
   saved) worked, after I'd done a few tweeks to my .xinitrc.  I tried my
   old beloved sawfish(now wmctl) but that didn't work as well as metacity.

> (*)  Does anyone here know how to create a .Xauthority file?  That is one of 
> the
> things the Jessie installer failed to provide me with.

You've asked this five months ago:
I did indeed.  That was before my old machine gave up the ghost.  I am 
impressed, Brian, that you keep such careful track of me.

My final problem is: how to get my Jessie to get on line.  I don't think this is
anything anyone here can help me with, since I live in a retirement community
which has a huge contract with Comcast.  I called a tech person here, and he 
gave me
a username and password which got me, and keeps me, online . . . but only for 
the
Windoze side.  I gotta do some exploring to see if I can make this work with 
Jessie.


>  You are probably asking the wrong question.


Best wishes to all, even to Lisi!

Alan

Re: How to get Jessie to run at boot time -- Problem solved

[Alan McConnell]

- Original Message -
From: "Lisi Reisz" <lisi.re...@gmail.com>
To: debian-user@lists.debian.org
Sent: Wednesday, September 14, 2016 2:05:47 PM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

On Wednesday 14 September 2016 19:51:50 Brian wrote:
> You are probably asking the wrong question.

Oh, no, Brian.  He is asking the right question by definition.  Alan is asking 
it, it is therefore right.
   Lisi, is this kind of post helpful?  Is that a question that you even ask
   yourself?  For some reason you've taken a dislike to me, at a distance of
   5000 miles.  That's OK, no skin off my nose.  But you are starting to 
irritate
   other members of this E-list.  So please: make sure from now on that your
   posts contain information, and not just name-calling.  We'd all 
appreciate it.

TIA,

Alan

Re: How to get Jessie to run at boot time -- Problem solved

[Alan McConnell]

- Original Message -
From: "Felix Miata" <mrma...@earthlink.net>
To: debian-user@lists.debian.org
Sent: Wednesday, September 14, 2016 1:44:14 AM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

Alan McConnell composed on 2016-09-13 20:50 (UTC-0400):

> when my home Debian install is, for some reason, not functional.  I apologize 
> for
> Zimbra's inadequacies, failure to produce '>' as my home mutt so nicely does.

> Just because one is unable to get whatever she is using to compose a reply 
> according to standards automatically doesn't excuse one who knows better from 
> conforming. Apologizing, particularly while continuing to not conform, does 
> not excuse. You are responsible for what you post, not your posting agent.
   I just put in the '>'s in the four lines above by hand.  I hope you are 
not
   going to ask me to continue to do so!  Especially since I've already 
explained
   that Zimbra(which is set up to deal with E-mail) is such a cruddy mess.


...
> But maybe someone
> can tell me why the installer can't look at the partitions and determine that 
> there
> is some kind of OS already installed?  Why does it have to know about Windows 
> 10 to
> behave sensibly?  "Curious minds . . . "
 I have just checked and when I sent this it was indented eight spaces 
or so.
 As is this present paragraph.  Do you(plural) see that it is indented? 
 or does
 your(plural) mail reader simply delete the spaces?  I ask, because I 
don't like
 to be chewed out when I'm doing my (present) level best to conform 
with 
 expectations.  Of course, it could be that Zimbra deletes the 
preliminary spaces
 before sending the mail out.  I could tell you tales about how Gmail 
mucks with
 what one has written before it sends the mail.


It does seem curious that the Debian installer would need knowledge of a 
particular Windows version in order to provide a boot menu selection for it, 
rather than simply having one that says "Windows", booting from whatever 
non-native/NTFS filesystem it happens to find containing anything resembling 
boot sector code.
 Yep.  I have been back to my Jessie in the meantime, and run os-prober.
 I didn't attempt to copy down on a piece of paper what it wrote; trust 
me
 that it was unenlightening garbage.

> Should you be game to try installing Jessie again, you might try a network 
> installation started via a Stretch installer. 
 Jeez!  I can't even run X11 on my present install(*) let alone get on
 line.

(*)  Does anyone here know how to create a .Xauthority file?  That is one of the
things the Jessie installer failed to provide me with.

Best wishes,

Alan

Re: How to get Jessie to run at boot time -- Problem solved

[Alan McConnell]

- Original Message -
From: "Lisi Reisz" <lisi.re...@gmail.com>
To: debian-user@lists.debian.org
Sent: Tuesday, September 13, 2016 3:58:01 PM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

On Tuesday 13 September 2016 18:24:07 Gene Heskett wrote:
> On Tuesday 13 September 2016 08:57:19 Alan McConnell wrote:
> > Warning:  This E-mail is for the most part in the nature of a pushback
> > against various insinuations that have been made.
>
> Now I am going to push back Alan.
>
> If you are going to come in here and berate folks about this and that,
> the first thing you need to do is to train your email agent
>
> (wth is "X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - GC46
> (Win)/7.2.6_GA_2926)" never heard of it)

https://www.itg.ias.edu/content/logging-zimbra-web-client
   Interesting that the IAS uses Zimbra.  I've been after Paul Heller for 
years
   to get rid of Zimbra, a huge clunky webmail interface, and I only use it 
when
   when my home Debian install is, for some reason, not functional.  I 
apologize for
   Zimbra's inadequacies, failure to produce '>' as my home mutt so nicely 
does.

It isn't an email client, and obviously can't do threading and quoting and 
things.  Alan clearly doesn't understand them, just as he doesn't understand 
what the word "solved" means.  Hint for Alan:  it doesn't mean the same as 
kludged.
   Sorry, I do know what 'solved' means, and I do say that _my_ problem is
   solved.  But my solution, as I've said over and over again, is not one 
that
   I can give to people who are running a dual boot system at my urging.



> to properly quote, and honor existing quotes, if for no other reason than
> to help us identify who wrote what.  That is what all those leading >
> and >> > are all about. It is also part of the email protocol that has
> existed since the late 80's of the last century.
   Absolutely!  I couldn't agree more.  When I get Jessie running properly 
on
   my new Dell I'll have my emacs put in quotes as they should be.  But I 
don't
   know how to do it on Zimbra, which, I'll repeat, is a foul piece of SW.  
For
   now I'm indenting my replies.  I hope all your mail readers respect my
   indentations; I have a suspicion that some of them don't.

   Re Royal Holloway: boys were added in 1966, a year before my time there. 
 But
   there were always male faculty there, especially in math, which subject 
has,
   most unfortunately, suffered from a dearth of qualified women.  This is 
beginning
   to change: the AMS puts a lot of effort in supporting women and 
departments
   supporting women.

   More perhaps tomorrow.  I have tasks to perform before bed.  But maybe 
someone
   can tell me why the installer can't look at the partitions and determine 
that there
   is some kind of OS already installed?  Why does it have to know about 
Windows 10 to
   behave sensibly?  "Curious minds . . . "

Best wishes,

Alan

Re: How to get Jessie to run at boot time -- Problem solved

[Alan McConnell]

- Original Message -
From: "Brian" <a...@cityscape.co.uk>
To: debian-user@lists.debian.org
Sent: Tuesday, September 13, 2016 9:40:11 AM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

On Tue 13 Sep 2016 at 08:57:19 -0400, Alan McConnell wrote:

> Warning:  This E-mail is for the most part in the nature of a pushback against
> various insinuations that have been made.  

Warning duly noted; most of this mail is snipped so we can concentrate
on the technical aspects of your issue.
 Excellent.


You were asked for some information. You declined to provide it. As a
route to solving a technical problem your response leaves a lot to be
desired.
 Did you read why I declined?  I repeat my reason for your benefit:
 getting information from my only partially installed Jessie means
 shutting down my Windoze OS(I'm writing this from my Windows OS),
 turning on my Jessie, and writing a bunch of detailed information on
 a piece of paper, shutting down Jessie and returning to Windoze and
 transcribing what my paper said to an E-mail.  That process requires
 a lot of error-prone steps, and you or someone else might have called
 for an iteration, which would have driven me up the wall.

The output of interest is from os-prober. You know what it, unless you
are so uninterested in seeking a solution you haven't even run it or are
keeping what it says to yourself.
 I ran os-prober.  I can't here reproduce what it gave me, but it
 didn't reveal the OS that came with the just purchased machine.
 Which leads me to my often-stated conclusion:  since the install
 program stated "No other OS can be found on this machine", the
 installer is broken.

You may be interested to know that the Debian Fairy has waved her magic
wand and made your machine dual bootable. From os-prober's changelog on
unstable:
 Good grief, Brian.  What I have is Jessie.  But it is good to
 know that attention is being paid to this issue, and the installer
 for stretch may be an improvement.

> Finally:  I have taken a resolution not to respond to further chastisement or 
> smarm.
> Please help me to keep it!

I don't do smarm. If you perceived what I wrote to be that, it reveals a
weakness in my irony, sarcasm and mild insults modules.
   I did perceive it.  Advice: delete your ISMI module and pay
 more attention to your courteous and helpful module.  Which I'm sure
 exists.

A final question:  I've used Wiktionary to learn that 'whinging' is the English
for what we Murricans call 'whining'.  Is it used a lot nowadays?  I don't 
recall
ever having heard it when I taught at Royal Holloway College back in 1967-68.

Alan

Re: How to get Jessie to run at boot time -- Problem solved

[Alan McConnell]

Warning:  This E-mail is for the most part in the nature of a pushback against
various insinuations that have been made.  

- Original Message -
From: "Lisi Reisz" <lisi.re...@gmail.com>
To: debian-user@lists.debian.org
Sent: Monday, September 12, 2016 5:38:56 PM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

On Monday 12 September 2016 19:14:53 Alan McConnell wrote:
> Maybe I should apologize for "hijacking a thread"?

Yes, you should.  It has left the person whose thread you have hijacked high 
and dry.  It is most definitely "not done" to hijack threads.  By those who 
care about etiquette and other people, that is.
  You have got to be kidding!  I have stolen(the meaning of "hijacking")
  nothing.  Nothing prevents you or anyone else from ignoring what I write 
or
  have written and concentrating on the other messages in this thread.

  You talk about etiquette.  I have, over the past twenty years, set up
  at least three E-lists; one about Linux(lwob), one about music(vlaviworld)
  and the third about politics(waifllc, using Meetup).  I never prescribed
  any form of behavior for my members, and I'm surprised that you take it on
  yourself to do so for debian-users.

  Besides: since I added "Problem solved" to the Subject line, I am now 
posting
  under a different thread.  However, you or anyone else are free to use it 
for
  further lessons in etiquette, or anything else you choose.
  

Brian was offering you a good technical solution that would actually have 
solved your problem, instead of a "cobble", which you say that Debian should 
fix.
   He was doing no such thing.  He asked a bunch of questions like "What 
was the
   version of Windoze I was using?" ! ? ! He offered no solution at all 
that improved
   on what I use.  I'll get to Brian more in a moment.

Even God is said only to help those who help themselves.
   I _have_ helped myself!  And I am fortunate that I have been able to 
draw the
   attention of a real expert, Felix Miata, who combines his expertize with 
an
   ability to read, and a reluctance to preach.  Would that you and Brian 
would
   emulate him.

On to Brian!  You, Brian, ask: was anyone impolite?  I was accused of being 
impolite and
I reject the accusation.  I will, however, remark that your series of 
"deconstructions"
verge on the smarmy.  Do you claim that they were useful, or even relevant?

And what am I, or anyone, to think of your assertions about "Debian Central" or 
"Abarrane"?
Is it your claim that such comments are useful, or relevant, or even polite?

Again, for the third time:  I hope that an new release of the Debian 
installation SW
will be able to detect when another OS is already on the system, and that a 
proper and
simple procedure will be put in place for e.g. newbies to Linux or to 
dual-bootable
systems to be able to choose between the systems immediately after the machine 
self-test.

Finally:  I have taken a resolution not to respond to further chastisement or 
smarm.
Please help me to keep it!

Best wishes, even to Lisi and Brian!

Alan

Re: How to get Jessie to run at boot time -- Problem solved

[Alan McConnell]

- Original Message -
From: "Felix Miata" <mrma...@earthlink.net>
To: debian-user@lists.debian.org
Sent: Sunday, September 11, 2016 10:14:26 PM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

David Wright composed on 2016-09-11 21:44 (UTC-0500):
...
>> Subject: Re: How to get Jessie to run at boot time -- Problem solved
...
How is it beneficial to list anyone here or searching list archives to 
continue a thread by chastising an OP for being imperfect more than 12 hours 
after OP added string "solved" to the subject and thanked people who provided 
useful help?
Hurrah for Felix!  He got it.

  I don't know what I have to apologize for.  Did I say anything 
impolite?  I'm not
  conscious of having done so.  Maybe I should apologize for "hijacking 
a thread"?

  As Felix and maybe a few others have noticed, I can now log on to 
either my Windoze
  or to Jessie, which is what I originally inquired about.  I persist 
in thinking 
  that the procedure I am using is cumbersome, and I hope
  that a new release of installation SW will a) be sure to detect 
another OS during
  the installation, and b) will ensure that grub puts a good 
notice/question up on a
  beginning screen for people to click on(or perhaps use the arrow 
keys) to indicate
  which OS they wish to boot.

  To conclude this topic:  the folks who think I'm rude or 
uncooperative or both clearly
  have the option to ignore in future anything/everything that I write. 
 I hope they
  will take advantage of this option.

Now I have a follow-on question:  I'd like to be able, from Jessie, to copy 
files to and from my
Windoze system.  I haven't really tried simply cd-ing to e.g. /dev/sda1, which 
is the partition
containing my Windoze stuff.  Is that what you dual OS users do?  is there some 
subtle   mount
command  that you use?   I shall be most grateful for any instructions, or even 
suggestions.

Best wishes to all,

Alan McConnell

Fwd: How to get Jessie to run at boot time -- Problem solved

[Alan McConnell]

I tried to send this only to Brian, but he has set his system to
not accept messages to him.  So I have to send this to the whole
List.  Sorry.

- Forwarded Message -
From: "Alan McConnell" <a...@his.com>
To: "Brian" <a...@cityscape.co.uk>
Sent: Sunday, September 11, 2016 3:38:06 PM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

This only to you, Brian.

- Original Message -
From: "Brian" <a...@cityscape.co.uk>
To: debian-user@lists.debian.org
Sent: Sunday, September 11, 2016 2:51:50 PM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

On Sun 11 Sep 2016 at 15:17:00 -0400, Alan McConnell wrote:

> On Sun 11 Sep 2016 at 11:13:45 -0400, Alan McConnell wrote:
> 
> > Addendum:  during my Jessie install, the install program commented at one 
> > point:
> > "There doesn't seem to be any other OS on your system".  Jeez!!  I hope some
> > maintainer reads this complaint and Debian  works hard to make sure that the
> 
> What is the exact name and version of this OS which is not found?
>  Windows 10.  If there is a more exact name, I don't know it.

Deconstruction of this statement follows:
Brian, you are in a bad temper.  Did you read the amended title of this
and previous messages? "Problem solved".
 
Suggestion: simply don't reply to any of my (perhaps) forthcoming 
questions
    and/or comments.  That will save both you and me time and spare us both
annoyance.

Best wishes,

Alan McConnell

Re: How to get Jessie to run at boot time -- Problem solved

[Alan McConnell]

- Original Message -
From: "Brian" <a...@cityscape.co.uk>
To: debian-user@lists.debian.org
Sent: Sunday, September 11, 2016 1:32:54 PM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

On Sun 11 Sep 2016 at 11:13:45 -0400, Alan McConnell wrote:

> Addendum:  during my Jessie install, the install program commented at one 
> point:
> "There doesn't seem to be any other OS on your system".  Jeez!!  I hope some
> maintainer reads this complaint and Debian  works hard to make sure that the

What is the exact name and version of this OS which is not found?
 Windows 10.  If there is a more exact name, I don't know it.

> operation of installing a second OS(Linux) on a Windoze box is as easy and
> error-proof as it is possible to make it.

1. As a user do

 dpkg -l | grep grub

   Please post the output of this command.

2. Suppose there are four packages listed. As root do

 apt-get --reinstall install 

   for each package

is in the second column of the 'dpkg -l' output.

   So, for example

 apt-get --reinstall install grub-common
 apt-get --reinstall install grub-pc
 apt-get --reinstall install grub-pc-bin
 apt-get --reinstall install grub2-common

   is what I would do on my machine. For the grub-pc reinstall please post
   the lines which begin "Found ." in the output.

3. As root run the command

 os-prober

   and post its output.

 Why?  why all this?  What good will it do? to anyone?  To do this I'd 
have
 to get out of this URL(mail.his.com), shut down my Windoze, reboot to 
Jessie,
 copy the output you are requesting to a piece of paper, and then get 
back here.(*)

 May I ask: are you the Debian installation maintainer?  if you are, 
I'd be
 happy to work with you.

(*)  Many years ago, when I ran a dual boot machine of Linux and MS-DOS, I used 
to be
able to mount the MS-DOS partition from my Linux system, and copy file to and 
from it.
I'm going to try that, when next I (re)boot into Jessie.

Best wishes,

Alan

Re: How to get Jessie to run at boot time -- Problem solved

[Alan McConnell]

- Original Message -
From: "Felix Miata" <mrma...@earthlink.net>
To: debian-user@lists.debian.org
Sent: Saturday, September 10, 2016 11:33:46 PM
Subject: Re: How to get Jessie to run at boot time

Alan McConnell composed on 2016-09-10 17:45 (UTC-0400):

> Good grief.  I just wrote that I am now logged in to a working jessie.
> So I can run any kind of apt-get, aptitude, etc.

> So I repeat:  apt-cache search grub gives me lots of grub files to install.
> Do I want to install a different grub?

> Possibly, though not likely. What does 'dpkg -l | grep grub' show now?
I have grub 2.0.2

What works for me now is the following:  If I do nothing, I boot 
directly
into Jessie.  However, if I wish to boot into Windoze, which is what 
I'll do
a lot for now, since I haven't even got an X11 system running on my 
Jessie,
I press and hold F12, to get into the choose boot method pre-OS screen.
There I choose Windows boot manager(recall that this is a new machine, a
generic Dell, so OF COURSE it had Windows installed.  And after choosing
this, of course what I get is a nice boot into Windoze.

Before leaving this topic, I have a remark:  I have been telling interested and
non-interested people for years that one doesn't have to completely abandon 
one's
long-held Windoze habit, one can install Linux as a second OS and play with both
until Linux has "sold itself".  I shudder to think of someone taking my advice,
following all the instructions, and winding up with a system where only Linux
is available.  Imagine being taken out of one's English-speaking world and 
dumped
into a village in Uzbekistan!

Fortunately I live in a facility where there is a "computer lab" to which I have
access.  And I was able to go there, use their Chrome browser to get to my 
his.com
E-mail facility, whine to you folks, and blunder my way through to a solution.
Other people won't have that good fortune.

Addendum:  during my Jessie install, the install program commented at one point:
"There doesn't seem to be any other OS on your system".  Jeez!!  I hope some
maintainer reads this complaint and Debian  works hard to make sure that the
operation of installing a second OS(Linux) on a Windoze box is as easy and
error-proof as it is possible to make it.

Best wishes, and thanks to all the kind responders who helped me.

Alan McConnell

Re: How to get Jessie to run at boot time

[Alan McConnell]

- Original Message -
From: "Brian" <a...@cityscape.co.uk>
To: debian-user@lists.debian.org
Sent: Saturday, September 10, 2016 12:38:11 PM
Subject: Re: How to get Jessie to run at boot time
 .   .   .   .

> could install.  So I ask again, this time from a position of being able to 
> install
> and configure  grub , how do I do it, and make it give me a good clean choice 
> of
> OS when I turn my machine on in the morning?
> 
> I hope that this is the place to ask; or is there an E-list full of grub 
> experts?

> They'll tell you to reinstall GRUB and run the command 'update-grub'
> from rescue mode. You can ask about this if you are stuck when you get
> rescue mode going.
   Good grief.  I just wrote that I am now logged in to a working jessie.
   So I can run any kind of apt-get, aptitude, etc.  

   So I repeat:  apt-cache search grub gives me lots of grub files to 
install.
   Do I want to install a different grub?  I remember that previously I had 
lots
   of files in /boot/grub/ .  Now I have just a few, which I gave to you 
and the
   List in my previous post.

   Again:  are there people with a working dual boot system?  I'd like a 
response
   from one of them(if they exist here) letting me know how it works, and 
also:
   what is the content of their /boot/grub/ directory.

Again: TIA.

Alan McConnell

Re: How to get Jessie to run at boot time

[Alan McConnell]

(Please excuse my cc to Mr Cater)

- Original Message -
From: "Andrew M.A. Cater" <amaca...@galactic.demon.co.uk>
To: debian-user@lists.debian.org
Sent: Friday, September 9, 2016 2:42:28 PM
Subject: Re: How to get Jessie to run at boot time

On Fri, Sep 09, 2016 at 01:58:03PM -0400, Alan McConnell wrote:
> This one should be _real_ easy!
.  .  .  .  .

> But I don't know how to get my new Jessie to boot!  Back when I had one of my
> first Linuxes and MS-DOS on my system, one got a prompt: "L or M" as soon as
> one turned on the computer.  Things are now more subtle I'm sure, and they are
> too subtle for me!
> 
> So can someone who also has a dual-bootable system(with Windows 10 and Jessie)
> please tell me how you choose, at boot-time, which of your systems you wish to
> boot?

> Boot your install medium - enter rescue mode - reinstall grub?
 I tried Rescue Mode.  Maybe I'm not doing it right, but I got thrown 
into
 "Chose language", "Choose Keyboard" . . . just as if I were doing a 
fresh
 install.  ? ? ?

But I don't need that.  I played with the BIOS a little, and now I boot 
automatically
into my new Jessie.  I am busy installing stuff and getting stuff off of 
backups, etc . . 
But I'd still like to be asked, right after I turn the machine on, which OS I'd 
like
to boot.

My present /boot/grub/ directory contains minimal stuff:
 fonts/ , grub.cfg , grubenv , i386-pc/ , locale/ , unicode.pf2

But when I runapt-cache search grub  , it shows me a lot more stuff that I
could install.  So I ask again, this time from a position of being able to 
install
and configure  grub , how do I do it, and make it give me a good clean choice of
OS when I turn my machine on in the morning?

I hope that this is the place to ask; or is there an E-list full of grub 
experts?

TIA,

Alan McConnell

How to get Jessie to run at boot time

[Alan McConnell]

This one should be _real_ easy!

Two days ago, my hard drive on my (now) discarded computer gave up the ghost.
After consideration, and advice from friends, I went out to Staples and bought
a Dell, with  Windoze installed.  I hooked up everything and Windoze boots
OK, my sound works, etc.

This morning I installed Jessie, and this time the install went well.  I could
put in partitions for / , /usr/, /boot, /var, /tmp, and put in a big swap
partition.  When I rebooted at the end of the install, I got my Windows again, 
which
pleased me, since I'd left it in, giving it 50 gig of my terabyte drive.

But I don't know how to get my new Jessie to boot!  Back when I had one of my
first Linuxes and MS-DOS on my system, one got a prompt: "L or M" as soon as
one turned on the computer.  Things are now more subtle I'm sure, and they are
too subtle for me!

So can someone who also has a dual-bootable system(with Windows 10 and Jessie)
please tell me how you choose, at boot-time, which of your systems you wish to
boot?

TIA

Alan McConnell
 

Re: Jessie (8.0) slow to boot

[Alan McConnell]

On Wed, Aug 31, 2016 at 09:16:00AM -0500, Richard Owlett wrote:
> I have Jessie installed on a desktop and a laptop. They both take about
> 105-110 seconds to boot. Squeeze on the desktop takes ~15 seconds to boot.
  My jessie install also takes a long time to boot.  A lot of it
  is because of attempts to start/stop/do something with
  COMRESET.  Eventually, after a minute, the boot process 'gives
  up'.

  What is COMRESET?  What does it do? can I get rid of these
  attempts?

TIA for anticipated information/help.

Alan McConnell

-- 
Alan McConnell :  http://globaltap.com/~alan/
  Memory says, "I did that."  Pride replies, "I could not have
  done that."  Eventually, Memory yields.(Friederich Nietzsche)

automounted USB drive: All partitions cannot be accessed by user

[Alan Davis]

Hello:

I have four partitions on a USB drive, including ntfs, fat32, and
ext4. None of them is accessible as automounted. Each of them is
accessible as root, however, and  each of them is
accessible when mounted manually with this command:

 $ sudo  mount /dev/sdXN /mnt/

I realize this is a permissions issue.  In fact the error message when
clicking on one of these partitions that shows up in files or dolphin
tells me it is.

I have tried a few things and wasted some hours this morning googling
this problem, encountering a virtual Pacific Garbage Patch of
miscellaneous traffic, not one of them seeming specific to this probably
very simple problem.  (It's a sign of the times, I guess).

I can mount even a partition that already shows up as mounted on files
or dolphin and is unreadable, except for ntfs, which does not allow
itself to be mounted until unmounted first.   At this point, the newly
mounted partitions can be accessed normally.

I have tried a recipe for udev from an archilinux article, but this was
no better.

I wrote entries into /etc/fstab for each partition, using
Label=.  This does not work.  This seems strange because I have
used this in the past.  As long as these fstab entries were in the file,
the system would not boot normally.

There may be a few different things going on here?

I would very much appreciate a pointer.  I can manually mount, for now,
but since I access files on these partitions regularly, it would be
extremely helpful for them to be automatically mounted.

Alan Davis

PS.  It's good to be using Debian GNU/Linux again after many years.  The
sticking point (that led to my giving up) has almost always been
networking, usually a  wifi adaptor that is not supported.  This time it
took two days for me to copy over *deb files one at a time, but
eventually, the install succeeded, in good fashion.  

USB external drive mounting / permissions issues.

[Alan E. Davis]

[I used the wrong email address when I posted this message a few minutes
ago.  I hope I will be forgiven for reposting using this correct address.]
Hello:

I have four partitions on a USB drive, including ntfs, fat32, and
ext4. None of them is accessible as automounted. Each of them is
accessible as root, however, and  each of them is
accessible when mounted manually with this command:

 $ sudo  mount /dev/sdXN /mnt/

I realize this is a permissions issue.  In fact the error message when
clicking on one of these partitions that shows up in files or dolphin
tells me it is.

I have tried a few things and wasted some hours this morning googling
this problem, encountering a virtual Pacific Garbage Patch of
miscellaneous traffic, not one of them seeming specific to this probably
very simple problem.  (It's a sign of the times, I guess).

I can mount even a partition that already shows up as mounted on files
or dolphin and is unreadable, except for ntfs, which does not allow
itself to be mounted until unmounted first.   At this point, the newly
mounted partitions can be accessed normally.

I have tried a recipe for udev from an archilinux article, but this was
no better.

I wrote entries into /etc/fstab for each partition, using
Label=.  This does not work.  This seems strange because I have
used this in the past.  As long as these fstab entries were in the file,
the system would not boot normally.

There may be a few different things going on here?

I would very much appreciate a pointer.  I can manually mount, for now,
but since I access files on these partitions regularly, it would be
extremely helpful for them to be automatically mounted.

Alan Davis

PS.  It's good to be using Debian GNU/Linux again after many years.  The
sticking point (that led to my giving up) has almost always been
networking, usually a  wifi adaptor that is not supported.  This time it
took two days for me to copy over *deb files one at a time, but
eventually, the install succeeded, in good fashion.

-- 

"Sweet instruments hung up in cases. . . keep their sounds to themselves."

 ---Shakespeare, _Timon of Athens_

USB Drive "The location could not be displayed"

[Alan E. Davis]

I am using debian stretch and gnome.

When I plug in a usb external drive with four partitions (including ext4,
ntfs, fat32) they are mounted automatically, but when I click on any of
them in files or dolphin, this message is received: The location could not
be displayed.  You do not have the permissions..."

I am able to read these files as root.  Even in the command line, however,
a normal user can only see: Permission denied.

Trying to mount by label:
# mount Label= /mnt/
   I see "special device  does not exist

I am able to mount any of them with a simple "mount /dev/sdcX
/mnt/, and they are accessible.  They are not shown
automatically on dolphin, although Iall files are visible when I navigate
to the mountpoint and click in files or dolphin.

I tried changing permissions of /media.  Not solved.

an NTFS partition was not mountable unless dismounted from the automatic
mount point; as far as I can see, this is not the case for vfat or ext4
partitions.

I did copy a udev rule for setting permissions---something above my level
of understanding, however.  If anything, the situation was worse.

It has been very frustrating to google for 2 hours on this probably very
simple problem.  I think the solution is just to mount them manually.
Still, it would be helpful to automount them, or mount via fstab.  I have
not had success mouting by label, and one does not know in advance whether
some usb flash drive might preempt these drive designations.

BTW I am pleased to be running a Debian system again after some years.  It
took a good deal of work, though, to get it set up on an iMac with a
broadcom wifi adaptor!

Alan Davis


-- 
[I do not] carry such information in my mind since it is readily
available in books. …The value of a college education is not the
learning of many facts but the training of the mind to think.
  ---Albert Einstein



"Sweet instruments hung up in cases. . . keep their sounds to themselves."

 ---Shakespeare, _Timon of Athens_

How do I change applications which startup when cd inserted

[Alan Chandler]

I am running the gnome 3 desktop under Debian Testing

I am trying to rip some of my cds to mp3 using k3b.

After I have inserted a cd and ask k3b to start ripping it to disk it 
tells me that gvf-cdda has control of the device and do I want to stop 
it.  I have to in order to continue.



However, I am doing all of this in the background, whilst getting on 
with other jobs in the foreground.  About 1 time in 10, the action of 
killing gvf-cdda actually logs me out.  This kills my windows virtual 
machine running in vbox and all sorts of other havoc.  I would rather 
this didn't happen as its a pain to get it all working again.


Firstly - can I stop gvf-cdda grabbing this cd and not releasing it?

Secondly, the gnome help (and indeed the gnome website) says to get a 
list of applications associated with different device types go to the 
Activities Menu and type "Details".  I don't have an activities menu 
per-se, just a desktop with a search bar to type into after I click on 
the activiies button in the top right hand corner.  But typing "Details" 
brings up nothing.


Is there something I should have installed in my system and haven't?  
(there is also a settings looking button on the top right menu (where I 
normally log out) - but clicking on it does nothing.   I am assuming 
this is part of the same problem).



--
Alan Chandler
http://www.chandlerfamily.org.uk

Re: Mythtv has lost all its on screen text

[Alan Chandler]

On 05/08/16 15:14, Ric Moore wrote:

On 08/04/2016 07:12 PM, Alan Chandler wrote:

I have mythtv installed from debian multimedia.  I am running testing
Once you introduce Debian Multimedia to your mix, you get to keep all 
the broken pieces. "These packages are known to not integrate well 
with other software packages in Debian and cause breakage regularly. "
I know its a risk, but how else do I get a working mythtv setup other 
than compiling from scratch?


I just wondered if anyone here had noticed the same problem and found a 
work around.






--
Alan Chandler
http://www.chandlerfamily.org.uk

Mythtv has lost all its on screen text

[Alan Chandler]

I have mythtv installed from debian multimedia.  I am running testing


About a week or so ago now, suddenly it has lost all its on screen text 
when playing a video (recorded TV programs).  The surrounding overlays 
are all there, just the text is missing - including on pop up menus.  As 
soon as you return to the normal mythv menu system the text comes back.



Anyone else experiencing this.  Any solution?

--
Alan Chandler
http://www.chandlerfamily.org.uk

Re: Another appeal about Flaky browsers

[Alan McConnell]

On Wed, Jul 27, 2016 at 05:50:36PM -0400, Ric Moore wrote:
> On 07/27/2016 05:38 PM, Lisi Reisz wrote:
> 
> >The rest of us aren't having the problem, so it must be something in Alan's
> >personal set-up or config files.  Having said which, I do find that Google
> >Chrome is currently eating memory like there is no tomorrow, so is the
> >problem shortage of memory?
 I know no one else on this E-list is having my problems,
   because otherwise the howls would be deafening.

> Have you started it in "safe-mode"? Mo problems with it running sid and
> chrome directly installed from google. Ric
  I have to call chromium from the command-line.  I have just
  tried  'chromium -safe-mode &'.  It runs fine for a while,
  but then the randaom 'Aw snap's start again.

Here are the messages to stderr that have come up in the first five
minutes(just a few of them!):

(start)
 [8316:8316:0728/110824:ERROR:navigation_entry_screenshot_manager.cc(141)] 
Invalid entry with unique id: 11
 [71:71:0728/110845:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented 
reached in static PlatformEvent::Modifiers 
blink::PlatformKeyboardEvent::getCurrentModifierState()
 [71:71:0728/110846:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented 
reached in static PlatformEvent::Modifiers 
blink::PlatformKeyboardEvent::getCurrentModifierState()
 [71:71:0728/110855:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented 
reached in static PlatformEvent::Modifiers 
blink::PlatformKeyboardEvent::getCurrentModifierState()
 [71:71:0728/110902:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented 
reached in static PlatformEvent::Modifiers 
blink::PlatformKeyboardEvent::getCurrentModifierState()
 [71:71:0728/110907:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented 
reached in static PlatformEvent::Modifiers 
blink::PlatformKeyboardEvent::getCurrentModifierState()
 [71:71:0728/110909:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented 
reached in static PlatformEvent::Modifiers 
blink::PlatformKeyboardEvent::getCurrentModifierState()
 [71:71:0728/110910:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented 
reached in static PlatformEvent::Modifiers 
blink::PlatformKeyboardEvent::getCurrentModifierState()
 [71:71:0728/110911:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented 
reached in static PlatformEvent::Modifiers 
blink::PlatformKeyboardEvent::getCurrentModifierState()
 [71:71:0728/110912:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented 
reached in static PlatformEvent::Modifiers 
blink::PlatformKeyboardEvent::getCurrentModifierState()
 [71:71:0728/110912:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented 
reached in static PlatformEvent::Modifiers 
blink::PlatformKeyboardEvent::getCurrentModifierState()
 Received signal 11 SEGV_MAPERR 77a08684
 #0 0xb057a72a 
 #1 0xafc29d28 ([vdso]+0xd27)
 #2 0xb1426899 
 #3 0xb169fb1d 
 #4 0xb169fe8f 
 #5 0xb16df58f 
 #6 0xb16872a8 
 #7 0xb18717b0 
 #8 0xb18705e0 
 #9 0xb151a170 
 #10 0xb1404f96 
 #11 0xb1405311 
 #12 0xb2a7f4ce 
 #13 0xb2a7ffb5 
 #14 0xb2a7db95 
 #15 0xb2a7d50a 
 #16 0xb2a49cee 
 #17 0xb2a4b160 
 #18 0xb2a4b2f0 
 #19 0xb5425cf1 
 #20 0xb237ec6e 
 #21 0xb237e7ed 
 #22 0xb237e3f3 
 #23 0xb237fac8 
 #24 0xb2371cb8 
 #25 0xb2371d2e 
 #26 0xb237edbb 
 #27 0xb22a9002 
 #28 0xb2a5133c 
 #29 0xb22a91f8 
 #30 0xb22a922e 
 #31 0xb257b69c 
 #32 0xb257bf2d 
 #33 0xb258ced0 
 #34 0xb57ddb07 
 #35 0xb57de099 
 #36 0xb57bf94b 
 #37 0xb57c15ff 
 #38 0xb57bd552 
 #39 0xb57bcb82 
 #40 0xb57c33df 
 #41 0xb58049a6 
 #42 0xb5804d59 
 #43 0xb05f7f52 
 #44 0xb580b86f 
 #45 0xb580a41f 
 #46 0xb580d3b2 
 #47 0xb05f7f52 
 #48 0xb0599b9d 
 #49 0xb0599fdf 
 
-(finish)
Again: it would be nice to know: what log files tell the results of
calls to a browser(e.g. opening/closing tabs etc)  Or doesn't the
system record browser activity?

Re another suggestion that a responder made:  I have found a directory,
   /home/alan/.config/chromium/Default/Session Storage
which contains
-rw--- 1 alan alan 33801 Jul 21 08:31 000185.ldb
-rw--- 1 alan alan 21828 Jul 25 11:09 000197.ldb
-rw--- 1 alan alan 34437 Jul 28 11:12 000199.log
-rw--- 1 alan alan 16667 Jul 26 10:58 000200.ldb
-rw--- 1 alan alan16 May 31 14:35 CURRENT
-rw--- 1 alan alan 0 May 31 14:35 LOCK
-rw--- 1 alan alan   272 Jul 28 11:07 LOG
-rw--- 1 alan alan   272 Jul 28 08:24 LOG.old
-rw--- 1 alan alan  6652 Jul 26 10:58 MANIFEST-01
   (the output of  ls -l)

These '000..' files are reported by the file utility as 'data files'.
Does anyone know what they are for? or how to read them?

Thanks to all responde

Another appeal about Flaky browsers

[Alan McConnell]

I wrote about this a while ago, but have to repeat my appeal.

Under  jessie  all the gui browsers I have tried(iceweasel and
chromium) crash continually, with messages "Well, this is embarrassing"
and "Aw, snap" continually appearing.  This happened only rarely with
jessie's predecessor,  wheezy.

Someone suggested I install  'iceweasel - firefoxESR'.  I have done
so, and it is the browser that shows when I click on 'Activities' in
the upper left corner of my Gnome screen.  But it doesn't start at
all!  ?  !  ?  !

Does anyone know where in /var/log  the error messages for this
failure are kept?  Or perhaps someone has suggestions about what
to change in my .cache or .config directories?

Alan, whose animus against Debian is increasing hourly because of
the wretched failures of the  jessie  installation

-- 
Alan McConnell :  http://globaltap.com/~alan/
 One Law for the Lion and Ox is Oppression(W. Blake)
 First Rule of Holes:  When you are in one, stop digging.(M. Ivins)

Instralling from offline sources: broadcom

[Alan E. Davis]

I need to install the broadcom-wl wireless adaptor drivers.  I have no
connection to the internet on this new installation.  So it's either this
or tethering the iphone to get this package installed.

Both of these pathways require a plethora of steps to install various
dependencies for dependencies.  I was a debian user in the early 90s, and
remember alarm at the penchant of devels to split everything into packages;
now I can remembery why

Anyway, I need build-depends.  Make, of all things, is one of the most
difficult things to install.

I have installed stretch.  Up to this point, it's a fantastic process of
installation.  As of now, several problems have kept me back.

1.  I used a usb of HD medium, so many packages are on this usb drive, but
it's beyond me how to get apt-get to recognize the USB drive as a rep, and
go ahead and complete the update.  Probably I need a list of packages.

2.  I cannot find make on this USB drive in pool.

3.  I cannot find patch on this USB drive.

4.  Individually I have installed a bunch of development packages.

5.  Tethering is a huge problem because of ifuse, I think, and other
dependency hells.

This is enough for now.  I would very much appreciate some advice on any of
these topics.  Once I have broadcom-wl installed it's all downhill I think.

I do have the package, but the dependencies are driving me bats.

Thank you.

Alan Davis

-- 
[I do not] carry such information in my mind since it is readily
available in books. …The value of a college education is not the
learning of many facts but the training of the mind to think.
  ---Albert Einstein



"Sweet instruments hung up in cases. . . keep their sounds to themselves."

 ---Shakespeare, _Timon of Athens_

Re: Potentialy OT: Firefox downloads over 6 GB of data streaming < 1 GB movie.

[Alan Greenberger]

On 2016-07-11, Juan R. de Silva  wrote:
> On Mon, 11 Jul 2016 12:25:00 +0200, Andre Majorel wrote:
>
 ...

>
> It is obvious indeed. :-)
>
> The number were taken from Daily usage tab in gkrelm. Before making the 
> test I had purposely not accessed Internet that day (except loading the 
> page with the movie certainly). Thus gkrelm only showed a couple of 
> dozens of MB due to some minor local network activity, which I ignored.
>
> I've already submitted a bug to Mozilla but was interesting to listen to 
> community. If I've experienced some abnormal Firefox behaviour is not 
> very likely that mine was totally unique experience.
>
> I'd hate to switch to Google Chrome from Firefox, since the last is my 
> favourite.
>
In about:config you could try setting network.prefetch-next to false.

Re: Browser Flakiness under Jessie -- Why?

[Alan McConnell]

On Wed, Jul 06, 2016 at 12:14:33AM +, Mark Fletcher wrote:
>
> > Do others have this problem?  Is it part of the general unreliability of
> > jessie?
> >
> > Thoughts, and possible assistance, appreciated.
> >
> > Alan
>
> This won't be anything to do with your internet connection. That error
> happens when the browser can't recover the state of your previous session,
> on startup.
 This I believe.  But it doesn't account for the steady drumbeat
 of crashes.

> Jessie has moved to FireFox -- have you tried that?
   Yes.  I have replaced the   iceweasel   that jessie
 installed withfirefox-esr .  It doesn't open At All, unless
 I run  'firefox-esr --version' or 'firefox-esr --help'.  The
 error message is "Illegal instruction", returned in the terminal
 from which I try to open it.  I don't know which file in
 /var/log to use to try to get more information.

> As to "general unreliability of Jessie" I wonder what kind of dialogue you
> were hoping to start with a remark like that. Here of all places. Anyway,
 Isn't it obvious?  I, who have used Potato, Woody, Etch,
 Squeezy, Wheeze, without any problems, have had _continual_
 problems with Jessie.  I got some help from Mr Mieta months
 ago, which helped me with the basic install.  Because of a
 missing .Xauthority I was unable to use my standard startx
 method of getting a minimum X11 session running.  Finally, in
 desperation, I have installed gnome(!!!) which works, sort of,
 but which leaves me floundering in all kinds of ways.

 That's just me.  But you surely must have noticed the tons
 of difficulties that even experts are having.  I have read, here,
 that there are plans to implement a 'jessie-A'.

> I've been using Jessie since it assumed the "stable" mantle from wheezy,
> and only see that error when I'd expect to ie when I do something stupid
> and crash the browser or when the machine doesn't power down properly eg
> after a power cut.
I felicitate you.

If you, or someone else, can at least tell me where to look
for explanations of the "Illegal instruction", I should be
most grateful.  [  Only with jessie have I had to use
'tail -f' on various /var/log files, and even there I am
floundering.

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
 Have the courage to be ignorant of a great number of things, in 
 order to avoid the calamity of being ignorant of every thing.

Browser Flakiness under Jessie -- Why?

[Alan McConnell]

Assembled Wisdom!

Using jessie, all the GUI browsers seem to be extremely flakey.
With iceweasel, I get, much too often "Well, This is Embarrassing".
With chromium, I get, much too often "Aw, Snap!".  I use lynx to
read some newspapers, and it never crashes.

I live in a retirement community, which has purchased, from Comcast,
a wi-fi installation which is almost always up, and continually
monitored.  The router I have been given is property of Comcast and/or
the community, and is state of the art.  So I don't believe my browser
problem has anything to do with my ISP.

Do others have this problem?  Is it part of the general unreliability of
jessie?

Thoughts, and possible assistance, appreciated.

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
 "St Francis! preaching to the birds!  if he had really
 wanted to save birds, he'd have preached to the cats."

Re: The Dreaded 'canberra-gtk-module' !

[Alan McConnell]

On Thu, Jun 23, 2016 at 09:21:34PM +0100, Brad Rogers wrote:
> On Thu, 23 Jun 2016 16:02:25 -0400
> Alan McConnell <a...@his.com> wrote:
> 
> Hello Alan,
> 
> >I can't find this module on my system, presumably because it is hidden
> >in some sub-directory.  I think that I'm actually looking for
> >libcanberra-gtk-module.
> 
> libcanberra-gtk-module is for creating/playing sound events.  All that
> will happen if you install it is that mutt still won't do what you want,
> but you'll get an error sound to tell you.
  I have also read that (lib)canberra-gtk-module has to do with
  sound.  But I have to go by the error message which I gave, no?

  And I asked: where is the file  libcanberra-gtk-module  ?  And
  no one has yet given me an answer to this question.

Alan, hoping for further information

-- 
Alan McConnell :  http://globaltap.com/~alan/
  "It is a great advantage for a system of philosophy
  to be substantially true." (Sophia Loren)

The Dreaded 'canberra-gtk-module' !

[Alan McConnell]

My mutt will no longer put my text/html mail up on my iceweasel.
The error message is:
  Gtk-Message: Failed to load module "canberra-gtk-module"
The difficulty seemed to occur after I had done some alterations
to my system, trying to get my _printer_(sic) to work.

I can't find this module on my system, presumably because it is hidden in
some sub-directory.  I think that I'm actually looking for
libcanberra-gtk-module.

Has anyone else had this difficulty? do you know where
libcanberra-gtk-module is hiding?

TIA for assistance!

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
   "Women run for office to do something, and men run for
   office to be somebody." (Debbie Walsh)

Re: Non-firefox browser?

[Alan McConnell]

On Fri, Jun 10, 2016 at 11:39:04PM -0400, Leon.37428 wrote:
>
> Here's a list of others: https://wiki.debian.org/WebBrowsers
 I have been used to, and using, iceweasel, for many years.
 But under Jessie I have found that it crashes several times
 a day. I am getting tired of "Well, this is embarrassing!",
 so I'd like to ask:  how does one get firefox-esr, and what
 does one do to replace   iceweasel  with it?

TIA for all constructive suggestion!

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
 What is the difference between terrible and interesting?
 Answer:  Whether it happens to you or not. (Jane Flanders)

Re: CUPS under jessie

[Alan McConnell]

On Fri, Jun 03, 2016 at 11:15:22PM +0100, Lisi Reisz wrote:
> On Friday 03 June 2016 21:00:52 Alan McConnell wrote:
> > I would be very grateful for any aid.  Just to show how bad things
> > are:  I try to access  http://localhost:631 on my iceweasel and I get
> > the message:  Unable to connect.    ? ? ? ?    Aaaagghhh!!
> 
> You said that you purged CUPS.  Since you have removed it, how do you expect 
> iceweasel to connect to it?  That doesn't show me "how bad things are", 
> it shows me that you have successfully removed CUPS.
  Sorry for the misunderstanding.  I was describing how
bad things _were_.  I really wasn't trying to run cups after I had
 -- partially -- purged it.

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
The beauty of an object, a song, or a dance can never be altogether
intrinsic, independent of old associations and acquired understanding.

CUPS under jessie

[Alan McConnell]

CUPS seems to be the standard printing SW used by Linux, or at least
by Debian.  But my CUPS is totally broken and I'd like to get rid of
it all and reinstall.  So I ran apt-get purge cups, but there
are still lots of cups-related files on my system, like in
/etc/cups/, /usr/lib/cups, /usr/share/cups, and likely other
places as well.

How do I make sure that my system is cups-clean, before I reinstall?

[ Background: I have a Canon 4770n three-in-one, connected to my
computer by a USB cable.  It is a very handsome piece of machinery,
it worked fine when I ran wheezy, but now that I've moved to jessie,
the printing part doesn't work at all.  However, the scanning capability
works just fine, as does the copying, which is of course independent of
the computer.  ]

I would be very grateful for any aid.  Just to show how bad things
are:  I try to access  http://localhost:631 on my iceweasel and I get
the message:  Unable to connect.? ? ? ?Aaaagghhh!!

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
The beauty of an object, a song, or a dance can never be altogether
intrinsic, independent of old associations and acquired understanding.

festival -- text to speech software

[Alan McConnell]

Assembled Wisdom!

'festival' is speech-synthesized software that has been around for
over 15 years, and I have installed it from my Debian jessie DVDs.
It worked splendidly for a while, but I have tried to install
new 'voices' and I have run into the following error;  I get
   {FND} Feature Token_Method not defined
when I try the simplest festival command.  I expect that there are
path difficulties involved . . .

Any help/suggestion provided will be greatly appreciated!

Alan

-- 
Alan McConnell :  http://globaltap.com/~alan/
"Laughter is the closest distance between two people."(V. Borge)
Religions revolve madly around sexual questions.

Re: canberra-gtk-module not loaded?

[Alan McConnell]

- Original Message -
From: "Sven Arvidsson" <s...@whiz.se>
To: debian-user@lists.debian.org
Sent: Friday, April 22, 2016 4:24:51 PM
Subject: Re: canberra-gtk-module not loaded?

On Fri, 2016-04-22 at 19:35 +, Blair, Charles E III wrote:
>    I have just installed the stable jessie using netinst on a
> laptop.  When I run certain programs, I am getting a message
> "canberra-gtk-module not loaded."  How do I fix this?   How serious
> is it?

GTK+ uses canberra to play event sounds (on errors dialogs etc).

It isn't serious at all and can be fixed by installing the canberra
library.
  Suppose one doesn't like the squawks that are emitted when e.g.
  a typing mistake is made, or a file isn't found.  Can one
  dis-install, or disable canberra, without otherwise messing up
  the sound?

Alan, who hopes to listen to Otello tomorrow on his computer!

Two questions

[Alan McConnell]

First, about my .iso downloads.  I have  debian-8.4.0-i386-DVD-2.iso, containing
4560861184 bytes, and debian-8.4.0-i386-DVD-3.iso, containing 4649361408 bytes.
Are the byte counts correct?  [ Yes, I know I should use checksums or something
like that, but I don't know anything about that  ]

Second,  I'd like to revive my ftp skills.  I could access ftp.debian.org, and
move around in it, and download some files.  But I'd like to use ftp to
download the two .isos given above, and I couldn't find them.  Can someone
give me the path to these two .isos?  I'll try using ftp to get them(again)

Finally, jigdo.   Ugh.  I grabbed a file jigdo-bin-0.7.3.tar.bz2 and tried to
unpack it.  tar worked for an hour, couldn't do it.  ! ? ! ?

TIA,

Alan

Re: Three Problems Yet Remaining

[Alan McConnell]

Problems are solved!  For the answer, see below.  I suspect that, for the
first time, I am making a useful contribution here that may help others.

- Original Message -
From: "Mark Fletcher" <mark2...@gmail.com>
To: "Alan McConnell" <a...@his.com>, debian-user@lists.debian.org
Sent: Wednesday, April 6, 2016 10:13:22 AM
Subject: Re: Three Problems Yet Remaining


The first and most important problem is: my iceweasel crashes instantaneously 
upon 
being invoked, whether from the Activities list on the LH side or from the 
command 
line. It was totally reliable under wheezy. 

Second: my mutt, invoked from the terminal/command line. crashes 
instantaneously 
also. Before I resigned myself to the gnome environment, it ran fine. 

I suspect the cause of these 2 issues is the same. We'd need to see log files 
eg /var/log/messages or something, or maybe the xsession-errors file, to make 
any progress on what might be the problem. Are you running Jessie now? I'm 
running Iceweasel on Jessie on amd64 architecture with no stability problems. 
What I did was to install the vmlinuz-3.16.0-4-686-pae kernel.  As I 
wrote a long time ago,
I tried to install this when in the midst of installing  jessie , but I 
couldn't do it.  So
I went to another kernel, and had all the problems I last complained 
about.  Physical
Address Extension is what pae stands for. and I advise all who can to 
use it.

My iceweasel runs fine, totally robust.  My mutt, ditto.  'file' is 
there, and works.
'touch', previously missing, now works.  The one thing I don't have is 
sound, and I can
fight that through on my own, I hope.  I've done it before.

Thanks to all for the suggestions, and even for the chastisements.  I hope 
that some day some
one will figure out about COMRESET, which continues to delay my boot.

Alan, writing this from his own computer!

Three Problems Yet Remaining

[Alan McConnell]

Assembled Wisdom!

The first and most important problem is:  my iceweasel crashes instantaneously 
upon
being invoked, whether from the Activities list on the LH side or from the 
command
line.  It was totally reliable under   wheezy.

Second:  my mutt, invoked from the terminal/command line.  crashes 
instantaneously
also.  Before I resigned myself to the gnome environment, it ran fine.

Three:  where is the utility  file  ?  I used this all the time in previous
Debian installations.

Any help/suggestions much appreciated!

Alan

Re: Modified Rapture, and a new question

[Alan McConnell]

  New developments!  When I turned my machine on this morning, I was given
a lovely blue screen with "Alan McConnell" in a box in the center and a space 
for
the password just below.  I typed in my password and was presented with a bunch 
of
icons on the left hand side of the screen.  Very pretty.  But when I clicked on 
any
of them, trying to find a terminal emulator so I can run from the command line, 
I
get a frowny face, telling me that an error occurred(???) and the system is 
suspending.
All I can do is click OK and then I get put into the original login screen, as 
above.
I am not given a clue what the problem is.  I do know that I don't have an 
.Xauthority
file in /home/alan, and this may be part of the difficulty.  Does anyone know 
how to
create an .Xauthority with  xauth?  I find the man page of xauth pretty 
impenetrable.

 [  What is the difference between hitting the reset button, causing a reboot, 
and
turning the machine off?  It seems that there is one; otherwise why didn't I 
get this
result yesterday?  ]

I am still not able to connect to "the Internet" aka the outside world, and I 
don't
know why this is.  I am living in a retirement community and when I first moved 
in, in
December, a staff member came in with a router, connected my machine to it, and 
it
"worked".  That was with   wheezy  .  I haven't a clue why it doesn't work with
  jessie .  Of course this is a problem that I can expect only suggestions from 
the
friendly and innovative members of this E-list.

- Original Message -
From: "Brian" <a...@cityscape.co.uk>
To: debian-user@lists.debian.org
Sent: Tuesday, April 5, 2016 5:51:25 AM
Subject: Re: Modified Rapture, and a new question

On Mon 04 Apr 2016 at 16:51:23 -0400, Alan McConnell wrote:

>  solved now, I hope!  Now my progress report: after futzing around 
> and
> trying to install this and that, I decided to bite the bullet/go with 
> the
> flow, and install GNOME, the whole thing.  Which I did, and it took 
> just
> short of an hour.  For some reason, Libreoffice was not installed.  I 
> hope
> I can get it later, since I know no other method of reading the 
> occasional
> .doc and .docx files that come my way.

Strange. Libreoffice packages are dependencies of gnome (as is gdm3). You
could try
  I did get it later(apt-get install libreoffice).


> [  By the way: I could and did get  emacsen-common, but still have no 
> working
> emacs.  How does one get such?  ]

emacs24 is on DVD-2, so either you obtain this disk or (as was suggested
earlier in this thread) set up sources.list for an external mirror and
get it over the network.
  Once I get the network working, I can try this.  I think I will have 
to
  edit /etc/apt/sources.list, a ticklish procedure.  I am going to ask 
my
  GSFC friend if he can burn me the Official Debian jessie disks 2 and 
3,
  which should keep be busy for a while.

The saga continues!

Alan, swimming through molasses

Re: Modified Rapture, and a new question

[Alan McConnell]

- Original Message -
From: "Brian" <a...@cityscape.co.uk>
To: debian-user@lists.debian.org
Sent: Monday, April 4, 2016 3:18:49 PM
Subject: Re: Modified Rapture, and a new question

On Sat 02 Apr 2016 at 16:42:35 -0400, Alan McConnell wrote:

>  Well, it doesn't contain emacs or tex or mutt, or ImageMagick.  Why 
> are you
>  telling me what it 'should' have?

I have touched on this in another post but here is a fuller answer:
   I owe Brian an apology.  When asked to put in my DVD, I put it into my
   _second_ DVD/CD drive, which is what I used to install.  Now I have
   detached my USB-connected CD/DVD reader-writer, and I have made a lot
   of progress.  But I am still having problems; see below.


assume it is DVD-1. This image contains mutt and ImageMagick. That is
why you are being told it "'should' have". Why you think it doesn't is a
mystery.
 solved now, I hope!  Now my progress report: after futzing around 
and
trying to install this and that, I decided to bite the bullet/go with 
the
flow, and install GNOME, the whole thing.  Which I did, and it took just
short of an hour.  For some reason, Libreoffice was not installed.  I 
hope
I can get it later, since I know no other method of reading the 
occasional
.doc and .docx files that come my way.
  
[  By the way: I could and did get  emacsen-common, but still have no 
working
emacs.  How does one get such?  ]

Result of my GNOME install:  I typed   'startx'  from my command line, 
and I
got a beautiful blue screen, a delight to the eye after days of 
perusing tiny
characters on a black display.  And in the middle of the blue screen 
there was
a handsome mouse arrow, which moved around elegantly when controlled by 
my right
hand.   

And that was _all_!!  No icons, nothing to click on . . . I typed on 
the keyboard,
no reaction . . .   There must be some simple way to get a proper GNOME 
started,
but since I've never used it before, I wonder if someone can give me a 
hint.

> I hope for further responses from people who have _answers_, although I'll 
> try to
> respond to questions of significance.  To repeat: I want to know how to 
> install
> SW that I need from off the thumb drive(aka USB stick)
 That's another discovery I've made.  The data on the DVD and the data 
on
 the thumb drive are exactly the same!  I don't know why 
LinuxCollections
 offers such a silly coupling for sale.  As I wrote previously, I 
thought
 there was some 'new technology' going on.  Not so at all.

You have had responses from people who have answers. None of them appear
to meet your "significance" criterion. Repeating your question again is
unlikely to produce better answers. Responding to a mail or two might
get you further on.
 An unfair charge, Brian.  I've done a _lot_ of work, learning about and
 coping with a Debian version totally unlike the one's I've used before.
 I have paid attention to, and benefitted from, and acknowledged the
 help of several people.  Other people.

 As someone elsewhere has remarked: an experienced user, familiar with
 Debian, should be able to install a new version in a half hour.  This 
 experience -- and I'm not done yet -- has taken me _days_.  I still 
don't
 know why.

Best wishes to all, and I hope Brian is satisfied

Alan