The following is specific to Ubuntu 24.04. If it should go to a
Ubuntu-specific list, let me know and I'll find out how to make that
happen. For now though, ...
... I have a new Ubuntu 24.04 system which is a rebuild of a 20.04
system. On the old system, I had logins set to use username and
I gave up on the NFS business and went back to good old buggy but
reliable SAMBA (LOL), which is what I was using when I was on Debian 8,
and which worked fine. Except for one thing, everything's great.
In /etc/fstab, I have:
//192.168.1.156/BigVol1 /mnt/bigvol1 civs
vers=2.0,credentials=/r
I upgraded a version 8 system to version 11 from scratch--e.g., I
totally reinitialized the internal drive and laid down an entirely fresh
install of 11. Then 12 came out about a week later, but I haven't yet
upgraded to 12 because I have a show-stopper on 11 which I absolutely
must solve befor
Please reply privately, unless you really think it's on-topic. Me, I'm
not sure.
I trying to build a package using automake (aclocal). I have all the
tools installed that I need--autotools, autotools-dev, libtool, etc
After patching the package's configure script, I attempted to
regenerate the bu
wrote:
> Hi.
>
>On Thu, Jul 28, 2016 at 04:44:09AM -0400, Steve Matzura wrote:
>> 2: eth0: mtu 1500 qdisc pfifo_fast
>> state DOWN group default qlen 1000
>
>Check your Ethernet cable. NO-CARRIER either means that the cable is
>unplugged from your NIC, or from w
That article talks about upgrading from 7 (Weezy) to 8 (Jessie). I am
already on 8--8.0 specifically. I was thinking of updating, maybe
upgrade is the wrong term, to 8.5.
On Thu, 28 Jul 2016 12:38:12 +0300, you wrote:
>Steve Matzura [2016-07-28 05:21:59-04] wrote:
>
>> Should
I am running 8.0; 8.5 is out. Came out on June 24. Are you saying I
should wait for 9 to become stable release and then upgrade to that
version? I thought by going to 8.5 would be a good idea. Maybe not?
On Thu, 28 Jul 2016 11:34:01 +0200, you wrote:
>Steve Matzura:
>>
>> Shou
Should I follow the standard procedure--edit sources.list to include
the DVD drive (if it's not there already), then 'apt-get upgrade'
followed by 'apt-get full-upgrade'?
On Wed, 27 Jul 2016 20:46:23 +0200, you wrote:
>Le 27/07/2016 à 15:43, Steve Matzura a écrit :
>> My 8.0 system has been running great up until Monday evening when
>> users started reporting they were unable to connect. Sure enough, I
>> couldn't even connect from my
My 8.0 system has been running great up until Monday evening when
users started reporting they were unable to connect. Sure enough, I
couldn't even connect from my LAN. I rebooted, looked at messages from
dmesg, and saw nothing unusual--nothing that said networking couldn't
start, or there was a ha
Are 'apt-get update' and 'apt-get dist-upgrade' sufficient?
Dan,
On Fri, 13 May 2016 05:12:56 -0400, you wrote:
>The options field in fstab should include "_netdev" for devices
>which cannot be mounted until networking is stable.
I have never heard of that option. I'll try it and report back. Now,
what about the lines for the binds that immediately follo
While the rest of my system is just cherry, I have not yet been able
to solve the problem of why an NFS mount and associated binds don't
work unless and until I wait a minute or two after the system comes
up, then issue a 'mount -a'. I have tried putting 'mount -a' into
/etc/init.d/rc.local, and s
On Wed, 27 Apr 2016 23:00:53 +0100, Lisi wrote:
>Did you discover the Adriane version? Now available as an alternative boot on
>the mainstream disk. It is specifically for the blind and partially sighted,
>and has things like Daisy Player there, as well as screen readers and speech.
>Adriane
Joe:
On Wed, 27 Apr 2016 19:05:26 +0100, you wrote:
>The most versatile system that I know of is Debian-based Knoppix, but
>the development effort goes into hardware detection and driving, with
>the result that it is not maintainable. It is installable to a hard
>drive, but you throw it away and
On Mon, 25 Apr 2016 19:04:40 -0700, David Christensen
wrote:
>Alternatively, make your own Debian Live images (hybrid ISO -- can put
>on optical discs or USB drives):
>
> https://www.debian.org/devel/debian-live/
Good solution. It solves the drivers problem for sure.
On Mon, 25 Apr 2016 20:22:48 +0100, Joe wrote:
>I've found that a minimal installation, then dpkg --get-selections and
>--set-selections and a bit of judicious /etc copying, to be a fairly
>painless way to get a clean near-copy of an existing installation. I
>migrated a server, I think lenny or sq
Joe:
On Mon, 25 Apr 2016 15:17:08 +0100, you wrote:
>I run ssh on a non-standard port, and my router redirects to 22 of my
>server, alternatively ssh itself will listen wherever you tell it to.
That's probably what I should be doing. As you say, it keeps the logs
clean and the riff-raff at bay.
My system that I built late last year/early this year is running
great, except for the occasional overrun of inbound ssh from such
addresses as 59.*.*.*, 213.*.*.* and others, but that's only because I
have not put any blockers in place, either on my home gateway device
or my Debian system, but tha
Martin:
On Sun, 28 Feb 2016 08:44:07 +, you wrote:
>Ever since Windows 3.11 its networking has been just awful and prone to
>malfunction without notice, they originally lifted the network stack from
>FreeBSD but managed to completely screw it, and it is still awful now, both
>in sharing and e
Just when I thought it was safe to let my Debian 8.2 system alone for
a few days, I started getting emails from users of the service I
provide which uses that system that they could not access any content
on the shared-mounted drives on one of my Windows machines. Sure
enough, I tried an 'ls' and g
On Sun, 7 Feb 2016 17:27:11 -0500, Carlos Kosloff
wrote:
>There was a package installed liblockfile1, which was causing grief.
I wonder if this might be my problem as well, but I don't find any
such package installed on my system.
After a couple system reboots for various things, mostly some hardware
changes, adding disks, etc., my Windows shares aren't mounting any
more, plus I'm getting a console error that the mount failed error
connecting to socket, error 115 mount operation in progress, etc. What
I want to know, aside f
Thanks to all who've helped me climb the learning curve of Debian 8.2
to get my system up and running. Specific thanks go, in no particular
order, to Daniel, Gary, Reco, Lisi, Dan, Mudongliang, Joe, the
Wanderer, Rick Thomas, and many others who took the time and had the
patience to bootstrap my kn
Emanuel,
On Sun, 17 Jan 2016 00:41:11 +0100, you wrote:
>modprobe cifs maybe can help you.
What is supposed to happen when I enter that command? All I got was
another shell prompt.
Reco:
On Sat, 16 Jan 2016 23:48:54 +0300, you wrote:
>Correct sequence would be:
>
>iptables -F INPUT
>iptables -A INPUT -p tcp --dport 22 -m conntrack --ctstate NEW \
> -m hashlimit --hashlimit 1/hour --hashlimit-burst 16 \
> --hashlimit-mode srcip --hashlimit-name ssh \
> --ha
Reco:
On Sat, 16 Jan 2016 23:49:57 +0300, you wrote:
>Reverse the order of these two rules. As I wrote in another part of this
>thread, I mistook rules' sequence.
Like this?
iptables -I INPUT -p tcp --dport 22 --tcp-flags SYN,RST,ACK SYN \
-j DROP
iptables -I INPUT -p tcp --dport 22 -m
After a reboot, one of my shares will no longer mount. And of course,
it's the big one, the NAS box. Here is output from `strace mount.cifs
//DISKSTATION1/BigVol1 /mnt/bigvol1 -o
vers=2.1,username=***,password=*** (*** is real username and password
covered up):
execve("/sbin/mount.cifs", ["mount.
14/01/16 13:10, Steve Matzura wrote:
>
>> Failing connection:
>> (...)
>> no matching cipher found: client
>> aes192-cbc,3des-cbc,blowfish-cbc,aes128-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-...@lysator.liu.se,des-cbc,des-...@ssh.com
>> se
Daniel,
On Sat, 16 Jan 2016 14:50:20 -0300, you wrote:
>I'm sorry. I Had forgotten of the detail of the accessibility :(
No worries. Things are in a sorry state at the moment because of other
things I did without realizing I did them, but I've already told my
usership that Voyager will have to g
On Sat, 16 Jan 2016 20:16:28 +0300, you wrote:
>> What'd I do?
>>
>
>Exactly this:
>
>iptables -F INPUT
>iptables -I INPUT -p tcp --dport 22 -m conntrack --ctstate NEW \
> -m hashlimit --hashlimit 1/hour --hashlimit-burst 16 \
> --hashlimit-mode srcip --hashlimit-name ssh \
> --
I tried redoing the tables:
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -p tcp -m tcp --dport 22 --tcp-flags SYN,RST,ACK SYN -j DROP
-A INPUT -p tcp -m tcp --dport 22 -m conntrack --ctstate NEW -m
hashlimit --hashlimit-upto 1/hour --hashlimit-burst 16
--hashlimi
Well, I thought I was doing so well. I discover now that no one,
including me, can get into my system any more via ssh. Here are the
current iptables rules:
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -p tcp -m tcp --dport 22 --tcp-flags SYN,RST,ACK SYN -j DROP
Reco:
On Sat, 16 Jan 2016 12:57:30 +0300, you wrote:
>>-j, --jump target
>> This specifies the target of the rule; i.e., what to do
>> if the packet matches it. The target can be a user-defined
>> chain (other than the one this rule is in), one of the special builtin
Reco:
All of this is an excellent learning opportunity for me. Please bear
with me just a bit as I ask the following:
On Sat, 16 Jan 2016 01:55:38 +0300, you wrote:
>A simple solution:
>
>iptables -I INPUT -p dcp -s 59.46.71.0/24 -j DROP
`-p dcp'? manpages says:
[!] -p, --protocol proto
On Sat, 16 Jan 2016 01:55:38 +0300, Reco wrote:
>A complex one:
>
>iptables -I INPUT -p tcp --dport 22 -m conntrack --ctstate NEW \
> -m hashlimit --hashlimit 1/hour --hashlimit-burst 16 \
> --hashlimit-mode srcip --hashlimit-name ssh \
> --hashlimit-htable-expire 6 -j ACCEPT
On Sat, 16 Jan 2016 01:55:38 +0300, Reco wrote:
>A simple solution:
>
>iptables -I INPUT -p dcp -s 59.46.71.0/24 -j DROP
iptables v1.4.21: unknown protocol "dcp" specified
Try `iptables -h' or 'iptables --help' for more information.
Should I try the complex solution, or find out what went wrong
On Fri, 15 Jan 2016 14:36:24 +, you wrote:
>:-) O.K. Please, no group "hugs" among friends I haven't met yet. ;-) Let's
>wait until we know each other better. ;-)
My arms are at my sides where they belong. :-)
My new fledgling server is being slammed, and I mean slammed like
Sandy slammed New York, by root login attacks from 59.46.71.36,
ShenYang, China. Of course, I don't allow root logins except from the
console or via ssh key pair, so I presume I'm safe that way, but I'd
sure like to cut down on the l
One more piece of the puzzle. The working system is Red Hat Fedora 20,
the non-working one is Debian 8.2.
More info. I used getenforce' and found SELinux is installed but
disabled on the system where FTP Voyager can connect using SFTP over
ssh, and not installed at all on the system where FTP Voyager cannot
connect. In fact, using either the `getenforce' or `'sestatus' on the
no-connect system yields `
Whoa folks, let's apply the brakes.
The fact is, if you think about it, Lisi is quite correct, but for a
reason she may not even realize. Visually impaired people, at least
those of us whose visual impairment is to the point where we don't use
print at all, don't hear in paragraphs, but anybody wh
Daniel,
On Thu, 14 Jan 2016 09:05:36 -0300, you wrote:
>Hi, Steve.
>
>On 14/01/16 08:45, Steve Matzura wrote:
>
>> This is clearly the problem area. I tried some ssh option settings in
>> Voyager with no success. Should this client be retired? It's not
>> *that
I decided to put the two logs from `sshd -d' side-by-side to try to
figure out where the differences are. Both logs have the following
lines immediately after the connection request:
debug1: Client protocol version 2.0; client software version
FTP-Voyager-15.2.0.15
debug1: no match: FTP-Voyager-15
Lars,
On Thu, 14 Jan 2016 12:45:09 +0200, you wrote:
>Can you update the client to one that uses the safer ciphers and avoids
>the deprecated ones?
You and I came to the same conclusion with the same lines of log as
evidence at about the same time. Amazing.
Many of my users use Voyager version
Tomas,
On Thu, 14 Jan 2016 05:32:04 -0500, I wrote:
>debug1: Enabling compatibility mode for protocol 2.0
>debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Debian-5
>debug1: permanently_set_uid: 107/65534 [preauth]
>debug1: list_hostkey_types:
>ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519 [p
Tomas,
On Wed, Jan 13, 2016 at 07:13:57PM -0500, Steve Matzura wrote:
>> I hope this isn't off-topic by too much. If it is, a word to me
>> privately and I'll wait for responses to queries I've made elsewhere.
>I'm not as much of an SSH guru to "get"
Jonathan,
On Wed, 13 Jan 2016 16:07:47 +, you wrote:
>On Wed, Jan 13, 2016 at 04:38:12AM -0500, Steve Matzura wrote:
>> Now to look up the syntax for putting it into fstab to make it
>> permanent. THANK YOU AGAIN EVER SO MUCH!
>
>The syntax is
> /
On Wed, 13 Jan 2016 22:08:02 +, Lisi wrote:
>On Wednesday 13 January 2016 09:38:12 Steve Matzura wrote:
>> And once again, I ask you to hand me the spatula so's I can scrape the
>> egg off my face. I completely forgot I needed to `mkdir -p' the mount
>> point di
I hope this isn't off-topic by too much. If it is, a word to me
privately and I'll wait for responses to queries I've made elsewhere.
I maintain two FTP servers and support four Windows-based FTP clients
for users of those servers--FTP Voyager, FlashFXP, Filezilla, and
WinSCP. One server accepts a
Tomas,
On Wed, 13 Jan 2016 08:26:16 +0100, you wrote:
>Those are totally meaningless. Just ignore them (BTW there was a
>discussion about this not long ago in this mailing list: if you're
>interested I can dig it out for you).
I would be very interested. So as not to clutter up the list, please
On Wed, 13 Jan 2016 10:01:03 +0300, you wrote:
>strace is used for tracing system calls, it does not influence your
>problem per se. Please install it first, run mount via strace second.
In between your message and now, my mount problem was solved, but I
installed strace anyway for future use. Th
On Tue, 12 Jan 2016 23:49:02 -0500, you wrote:
>On 12/01/16 10:23 PM, Steve Matzura wrote:
>> On Tue, 12 Jan 2016 18:12:11 -0300, Daniel wrote:
>>
>>> M... I used the following syntax:
>>>
>>> mount --bind /mnt/nas/doc /home/steve/doc
>>>
&
Gary:
>I just tried something similar with an NFS share and was able to do it.
>My situation was I have ///mnt mounted in ~/mnt. I was then
>able to (as root) mount -o bind ./mnt/archives ./mnt1 while in my normal
>~ folder.
>
>You could also try mounting the share locally or sharing the "doc"
Reco:
On Wed, 13 Jan 2016 00:21:19 +0300, you wrote:
>Please post the output of:
>
>strace mount -B /mnt/nas/doc /home/steve/doc
I *knew* I was missing something. I get 'command not found".
On Tue, 12 Jan 2016 22:56:28 +0100, you wrote:
>Le 12/01/2016 22:12, Daniel Bareiro a écrit :
>
>> mount --bind /mnt/nas/doc /home/steve/doc
>>
>>
>> That works for you?
>
>I use such syntax failry often
>
>jdd
Even on a virtual filesystem like a Windows share or NAS volume? Am I
maybe missing a
On Tue, 12 Jan 2016 18:12:11 -0300, Daniel wrote:
>M... I used the following syntax:
>
>mount --bind /mnt/nas/doc /home/steve/doc
>
>
>That works for you?
Sorry ...
mount: mount point docs does not exist
My SFTP setup works, almost. Local file access is OK. However,
symlinks can be seen but not followed. The symlink itself is owned by
root and in the root group, but the thing to which the symlink points
I have changed to the owner and group names associated with the login
username I'm using for the
I am trying to get around the restriction of symlinks not resolving in
FTP when the account is DefaultRoot'ed and CHRoot'ed. I mounted a NAS
volume, some directories of which I want to appear as being rooted
elsewhere, thus:
# mkdir -p /mnt/nas
# mount.cifs //ds1/vol1 /mnt/nas -o [various options]
Dan,
On Mon, 11 Jan 2016 14:15:53 -0500, Dan wrote:
>In general, you want your SFTP users to send you their own
>public keys, and you drop them into ~user/.ssh/authorized_keys
That's going to be difficult, as most of my users wouldn't know a
public key from their house key (LOL). I was hoping it
In order to use SFTP, I will be needing to generate key pairs for all
my users, all of whom will log into the same directory structure. It
seems no one on the system has keys generated, or they're not in what
I think is the normal place, ~/.ssh - Should I just create this
directory and use ssh-keyg
I asked this question on the ProFTPD list, but I thought it might be
more of a system question than an FTP server question. The more I look
at the message, I think it's probably both.
My system, which is now working correctly after reboot testing
following fstab changes discussed elsewhere, will s
Joe:
On Mon, 11 Jan 2016 08:23:27 +, you wrote:
>My best guess is a typo in fstab, as you said that was the next thing
>to modify. The very first time I ran a systemd-enabled Debian, I got
>that rather cheerful message, as I had removable drives there that were
>suddenly a problem.
Ya know,
On Mon, 11 Jan 2016 11:35:22 +0100, Sven wrote:
>There seems to be quite a few bug reports about problems with fstab and
>dropping into emergency mode, so worth a shot.
>
>(Always make a backup before changing stuff in /etc!)
Oh, I did; I simply forgot about that change, mostly because with all
t
On Sun, 10 Jan 2016 23:40:28 -0500, Gary wrote:
>On 10/01/16 07:15 PM, Steve Matzura wrote:
>> After solving all my mount problems and changing from dynamic to
>There are lots of things that can go wrong, but if you had been booting
>normally, it's likely something you'
Gary:
On Sun, 10 Jan 2016 23:40:28 -0500, you wrote:
>What messages are you seeing in dmesg or syslog (or the new SystemD
>versions)? What do you see on the screen before you get the emergency
>mode messages?
dmesg shows no errors. /var/log/syslog's last message has a time stamp
of just before
Tim,
On Sun, 10 Jan 2016 22:33:03 -0600, you wrote:
>If you are using Debian Jessie a static IP address is set using
>/etc/dhcpcd.conf and the much debated "systemd". I just worked my way
>through this on a Raspberry Pi which uses "Raspian" Jessie, a port of
>Debian. The details can be found h
After solving all my mount problems and changing from dynamic to
static addressing by editing /etc/network/interfaces, I reboot the
system and was greeted with:
Welcome to emergency mode. "systemctl default", "systemctl reboot" to
try again, or press Control-D to continue:
That's a mild paraphras
I added the "Everyone" username object to the list of those permitted
to access the drives, and it worked. No username or password required.
Now I have to get it into fstab and I'm totally done with system
setup!
rigin software="rsyslogd"
swVersion="8.4.2" x-pid="569" x-info="http://www.rsyslog.com";]
rsyslogd was HUPed
>And perhaps also run mount with the -v flag (or possibly -vvv).
# mount.cifs //box1/d /mnt/d -v -overs=2.1,username="Steve
Matzura",passw
Let me rephrase/clarify that. There are lots of things on which
screenreaders can be blamed, but this one wasn't one of them.
On Sat, 09 Jan 2016 20:49:59 -0500, you wrote:
>On Sat, 9 Jan 2016 22:46:20 +, Lisi wrote:
>
>>On Saturday 09 January 2016 22:00:46 Steve Matzura wro
On Sat, 9 Jan 2016 22:46:20 +, Lisi wrote:
>On Saturday 09 January 2016 22:00:46 Steve Matzura wrote:
>> Mea culpa. I didn't read far enough down the page.
>
>The fact you have to do so is clearly the result of your screen reader,
>Steve - the link actually opens
rk, I will, but having Windows automatically
log me in and restart all the applications I normally run after reboot
is important enough to me not to.
On Sat, 09 Jan 2016 20:52:35 +0100, you wrote:
>On Sat, 2016-01-09 at 13:59 -0500, Steve Matzura wrote:
>> I tried it, but nothing changed. An
On Sat, 9 Jan 2016 21:05:40 +, Joe wrote:
>> I've not heard cifs mounting without password but this is interesting
>>
>
>Yes, it can be arranged, but of course it's a bad idea unless the
>network is guaranteed (!) to be secure.
Not sure what would mean "guaranteed" for you, but two firewalls
On Sat, 09 Jan 2016 17:53:38 +0100, Sven wrote:
>On Sat, 2016-01-09 at 11:04 -0500, Steve Matzura wrote:
>> The Windows username is my own name, I have no password set on that
>> acount. It mounts flawlessly from another Windows machine, but when I
>> try:
>>
>>
Sven:
On Thu, 7 Jan 2016 16:12:51 +0100, you wrote:
>You said in your first mail that /dev/sda6 was swap. And since Linux
>always numbers the logical partitions beginning from 5 and /dev/sda1 was
>/, /dev/sda2 can only be the extended partition, containing sda5-8.
>Simple deduction (and experienc
I have a sneaky suspicion it's a writing-style thing. I'll make 'em
shorter next time.
On Thu, 7 Jan 2016 12:51:53 +, you wrote:
>On Thursday 07 January 2016 12:36:25 Steve Matzura wrote:
>> Lisi,
>>
>> On Thu, 7 Jan 2016 11:04:33 +, you wrote:
>
The Windows username is my own name, I have no password set on that
acount. It mounts flawlessly from another Windows machine, but when I
try:
# mount -t cifs //box1/d /mnt/d -o username="Steve
Matzura",password=""
I get:
mount error(121): Remote I/O error
Refer to the mount
Sven:
On Thu, 7 Jan 2016 08:29:46 +0100, you wrote:
>/dev/sda5 to /dev/sda8 are logical partitions inside an extended
>partition. The extended partition is /dev/sda2.
How did you know that? sda6 isn't even a mounted filesystem--sda1, 5,
7 and 8 are the mounted filesystems for /, /tmp, /var, and
Richard:
On Mon, 04 Jan 2016 05:53:15 -0600, you wrote:
>On 1/4/2016 5:07 AM, Chris Bannister wrote:
>> On Sun, Jan 03, 2016 at 09:32:36AM -0600, Richard Owlett wrote:
>>>
>>> A side question to Steve, "Is this post screen reader friendly?"
>>
>> That reminds me of the lecturers who say 'Hands up
Thanks Gary. I was overdoing it (as usual). I put in things like the
`-t' in front of `cifs' and the `-o' in front of the options list. All
fixed now.
On Wed, 6 Jan 2016 13:13:31 -0500, you wrote:
>On 06/01/16 12:25 PM, Steve Matzura wrote:
>> I have two things that ne
I have two things that need to go into /etc/fstab. One's a network
share with a username and password. The other is a Windows share which
is public, no username and password for that one. Both shares will
bmnounted on the Debian system read-only. I know how to do this with
mount and the -t switch,
You were. Standalone is best for my purposes.
On Sat, 2 Jan 2016 23:18:07 -0500 (EST), you wrote:
>On Sat, 2 Jan 2016, Steve Matzura wrote:
>
>> Hope I was right!
>
>What was your choice? Inet or standalone?
On Sat, 2 Jan 2016 23:06:29 +, Lisi wrote:
>My blind friend with his screen reader seems to have much less trouble with
>messy HTML than I (partially sighted) do. His screen reader just reads it to
>him. I stare at the mess of "pretty" colours and fancy writing, with
>blotches and swirls
On Sat, 2 Jan 2016 18:10:19 -0500, you wrote:
>There are lots of things that can go wrong. What I found worked recently
>when I had a similar problem was:
>
>#mount -t cifs -o username=,password=
>//192.168.1.19/images /mnt/images
>
>Using the DNS name returned errors but the IP address of the
y; if you're running it as non-root, IIRC the "specify
>>> both mount point and device to mount" will be rejected as "only
>>> root can do that". Either way, this doesn't look quite right.
>>
>> I'm running it as root all right.
places.
>If you're running that command as root, the fstab entry should not be
>necessary; if you're running it as non-root, IIRC the "specify both
>mount point and device to mount" will be rejected as "only root can do
>that". Either way, this doesn&#x
On Sun, 3 Jan 2016 06:22:11 +1300, Chris Bannister
wrote:
>> You would do well to read *all* of Steve Matzura's posts before
>> bemoaning your lot. You'll come across "speech synthesis" and
>> "screen reader".
>
>In that case, mails in html must be almost impossible to comprehend. :)
>I'm guessin
I have a Windows machine called 'box' with a directory called 'users'
which is shared publicly with no access username or password as
'users2'. On my Jessie system, I created the mount point successfully:
mkdir -p /mnt/users
I then installed the cifs-utils package as instructed by a Website
with
I figured it out after much playing around and gnashing of teeth. When
I pressed TAB, the OK button turned a different color, and then the
up- and down-arrow keys let me make a choice as to which type of
install I wanted, standalone or inet. I assumed the one with colors
other than gray was the act
The following is purely a visual impairment issue.
When installing ProFTPD, a dialog box is displayed wherein I must
choose whether to run it as a standalone service or via inet. I don't
know which is the default choice, and there's no graphic next to the
choices to indicate which one is checked o
On Thu, 31 Dec 2015 13:33:44 -0500 (EST), Jude wrote:
>If I were setting up an ftp server, I would create a /pub directory in
>/home and would also create a /home/pub/incoming directory then lock any
>guest into the /home/pub and /home/pub/incoming directories. The
>/home/pub directory would b
>Hi, Steve.
>
>On 31/12/15 14:07, Steve Matzura wrote:
>
>> That locks the user in their home directory, but I have to give them
>> access to other things outside that directory, just not let them go
>> walking around and get into any other directory on the system. That
On Thu, 31 Dec 2015 17:37:09 +0100, you wrote:
>Le primidi 11 nivôse, an CCXXIV, Steve Matzura a écrit :
>> ProFTPD? VSFTP? Something else? I'm needing a secure connection,
>> non-SSH, because a lot of ssh built into FTP clients let you go
>> wandering around outside you
On Thu, 31 Dec 2015 16:47:43 +, Brian wrote:
>'fdisk -l /dev/sdX' will show a partition table (as described by Thomas
>Schmitt). A 21GB image will not fit on a 16GM USB stick.
Yes, the ISO is good. fdisk shows everything's fine. I'll have to try
this with one of my 32's just to see it work. I
Fascinating stuff. The one thing I forgot is cp and dd are not the
same.
Now, does this mean I should run the ISO I made with Jigdo through
isohybrid now that I have a running Linux system?
On Thu, 31 Dec 2015 17:25:39 +0100, you wrote:
>Hi,
>
>Steve Matzura:
>> Thomas, just dd
ProFTPD? VSFTP? Something else? I'm needing a secure connection,
non-SSH, because a lot of ssh built into FTP clients let you go
wandering around outside your home area, unless there's a way to
protect against that in the ssh configuration file, which I did look
for but have not found. My FTP serve
the temp file that was created as soon as the process started
was expanded to 20.9GB and never changed, so it's probably full of a
lot of 0's toward the end.
On Thu, 31 Dec 2015 16:12:44 +, you wrote:
>On Thu 31 Dec 2015 at 10:37:22 -0500, Steve Matzura wrote:
>
>Thanks fo
On Thu, 31 Dec 2015 15:57:38 +, Lisi wrote:
>Some years ago a friend complained to me that I ignored his advice and never
>listened. I said, not at all. I always listen avidly to advice. I always
>think about advice. I just don't always follow advice. ;-)
LOL. I always find something in
Joe,
On Thu, 31 Dec 2015 15:43:12 +, you wrote:
>No, it's the very opposite of knowing where things go. The dd command
>is a very simple, completely unintelligent copier. But an ISO file is
>an image, literally every byte stored on some medium being scraped up
>in order, with the intention th
1 - 100 of 136 matches
Mail list logo
