-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jan 20, 2017 at 02:05:26PM +0300, Gokan Atmaca wrote:
> I did it. I first erased all parts. Without saying "W". Then I called
> the new section and gave default values.
> I've done it the next time I restart. :)
>
> #resize2fs /dev/sda1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jan 20, 2017 at 11:59:36AM +0200, Georgi Naplatanov wrote:
> On 01/20/2017 11:54 AM, Gokan Atmaca wrote:
> > Hello
> >
> > Debian is running as a VM on the KVM. I enlarged the disk with QEMU.
> > But the disk is as follows.
> > So he did not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Aug 19, 2016 at 07:41:56AM -0500, Richard Owlett wrote:
[...]
> As I had said in last paragraph of
> https://lists.debian.org/debian-user/2016/08/msg00609.html :
> "Why would I be interested in ssh as both machines are sitting on my
> desk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 27, 2017 at 07:17:56AM -0600, Richard Owlett wrote:
> The last time I needed a relational database my employer was using
> dBaseII on a MS-DOS machine.
Hm. A strange "relational" database indeed...
> What is a functional equivalent in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Feb 28, 2017 at 06:04:24AM -0500, Chuck Hallenbeck wrote:
>
> On Tue, Feb 28, 2017 at 07:59:01AM -0300, Eduardo M KALINOWSKI wrote:
> > On 27-02-2017 21:03, Chuck Hallenbeck wrote:
> > > Hi everyone,
> > >
> > > I'm attempting to install a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Feb 28, 2017 at 06:52:56AM -0500, Chuck Hallenbeck wrote:
> My comment below:
>
>
> On Tue, Feb 28, 2017 at 12:30:25PM +0100, to...@tuxteam.de wrote:
> > On Tue, Feb 28, 2017 at 06:04:24AM -0500, Chuck Hallenbeck wrote:
> > >
> > > On Tue,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Feb 28, 2017 at 12:28:22PM -0500, Chuck Hallenbeck wrote:
> Okay, I think we're closing in on it.
>
> The Cepstral swift package runs fine on archlinux, where using ldd -r
> on the executable lists eleven libraries, all but one of which is
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Feb 28, 2017 at 08:30:13AM -0500, Chuck Hallenbeck wrote:
> Here is a summary of what we now know:
>
> The only package in play now is
> Cepstral_William_x86-64-linux_6.2.3.873.tar.gz
>
>
> It was downloaded with wget from a link given to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Feb 28, 2017 at 01:47:15PM -0500, Chuck Hallenbeck wrote:
> My thanks for all the help and suggestions, and my apologies for all
> the floundering. Cepstral support spotted the problem pretty quickly.
>
> Evidently somehow I managed to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Mar 01, 2017 at 09:30:00AM +, GiaThnYgeia wrote:
> Boy Microsoft10 and Office-Access and share all your data with the
> seattle bureau in a cloud and have no annoyance what so ever.
Veering dangerously off-topic. But my $EMPLOYER just did
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Mar 01, 2017 at 06:33:58AM -0600, Richard Owlett wrote:
[...]
> >How do you increase fontsize on the LibeOffice (writer) toolbar and dropdown
> >meuns?? [closed] - Ask LibreOffice
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Mar 01, 2017 at 07:48:37AM -0600, Richard Owlett wrote:
> On 03/01/2017 06:37 AM, to...@tuxteam.de wrote:
[...]
> >How about filing a bug report? That won't solve your problem
> >*right now*, but... you know, giving back and that.
> I'm not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Mar 02, 2017 at 11:40:10AM +0100, Hans wrote:
> Checked my system again.
> It looks like have allowed the standard user to execute applications like
> synaptic with root rights. I know, this is going to be asked in KDE, when you
> start a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Mar 02, 2017 at 01:19:00PM +0100, Hans wrote:
> Hi Tomas
> > Hm. I'm not sure I've got that one right. Who has allowed the standard
> > user to execute applications with root rights? How?
> It was me, beeing haven asked by of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 27, 2017 at 09:07:19AM +0100, deloptes wrote:
> Stefan Monnier wrote:
>
> >>> I would like to hear some ideas on how to set various environment
> >>> variables (PATH, MANPATH, EDITOR etc.) in one place that would make them
> >>> effective
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 27, 2017 at 10:46:16AM -0600, Richard Owlett wrote:
[...]
> A little research indicates that Tcl/Tk plays well with sqlite. A
> couple of years ago I started learning it for a now abandoned
> project. I'll follow up on that combo.
Funny
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Sep 05, 2016 at 08:43:44AM -0400, Patrick Wiseman wrote:
> On Mon, Sep 5, 2016 at 8:29 AM, Richard Owlett wrote:
>
> > I attempted to copy contents of one partition to another using
> >cp -R /media/richard/myrepo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Sep 05, 2016 at 09:55:46AM -0300, Henrique de Moraes Holschuh wrote:
> On Mon, 05 Sep 2016, Richard Owlett wrote:
> > I received "illegal operation" error messages as symbolic links were
> > encountered.
>
> That means the target filesystem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Sep 05, 2016 at 07:29:52AM -0500, Richard Owlett wrote:
> I attempted to copy contents of one partition to another using
>cp -R /media/richard/myrepo /media/richard/test
>
> /media/richard/myrepo is a hard disk partition
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Sep 09, 2016 at 09:03:33PM +0300, Jarle Aase wrote:
> Hi,
>
> I was just about to order some usb2serial hardware when I read this.
[...]
> I'll try it when I get the first server assembled. Thanks a lot!
Hey, glad to help :-)
- -- t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Sep 10, 2016 at 07:36:11PM +0200, Andre Majorel wrote:
> Is there a tool which would take IPv4 addresses on the command
> line and say whether or not they are regular and routable ?
>
> host(1) is not very useful for that as it doesn't seem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Sep 08, 2016 at 10:26:59PM +0300, Jarle Aase wrote:
> I want to set up a few servers at home. Unfortunately, as I live in
> Bulgaria at the moment, the electric power is gone pretty often for
> longer periods than my UPS'es can deal with. So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Sep 13, 2016 at 12:04:53PM +0200, Siard wrote:
> to...@tuxteam.de wrote:
> > I haven't yet seen a complete table (nor have I yet bothered to find out
> > how one configures that in X -- some day I'll do).
>
> Well, there is a complete listing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Sep 09, 2016 at 04:05:28PM -0300, Daniel Bareiro wrote:
>
>
> On 09/09/16 15:05, Stephan Beck wrote:
[...]
> H... I do not quite understand this situation. That is, lkeusa.com
> asked to use SMTP authentication, but this would make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Sep 09, 2016 at 02:10:53PM -0500, Tim McDonough wrote:
> On 9/9/2016 4:26 AM, Cindy-Sue Causey wrote:
> >You know what, though, I did have two entries in there the other day.
> >And I found that tip because I was getting the "RTNETLINK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Sep 13, 2016 at 05:07:28AM +, david...@freevolt.org wrote:
> On Mon, 12 Sep 2016, Doug wrote:
[...]
> >And ½, ⅓, ⅜, ©, 75°, µF, 17¢, and others.)
>
> I see recognisable glyphs for five out of seven of those. My
> environment does not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Sep 23, 2016 at 04:41:00PM +, Stephan Beck wrote:
> Thank you very much, Tomás.
glad to help.
[...]
> But once my user's (in your terminology, steph's) public key is in the
> test account's authorized_keys file, user steph can login
ses writing into deleted files. You
> >> can see them with lsof +L1 (as root)
> >
> > Short and sweet. That's even better :-)
> >
> That's great; thanks Tomas and Erwan (and others who replied).
>
> So, I'm seeing this:
>
> root@shell:~# lsof +L1
> COMM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Oct 08, 2016 at 11:35:21AM -0400, Tony Baldwin wrote:
[...]
> >Can you use the chrome developper tools to see what's going on ? (Press
> >the F12 key while chrome is open) Select the network tab, and type the
> >url in your address bar.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Sep 21, 2016 at 11:38:41AM +0100, Brian wrote:
[...]
> Although it is a different topic
>
>
> http://stackoverflow.com/questions/26066535/ps2pdf-creates-a-very-big-pdf-file-from-paps-created-ps-file
>
> backs up your "pretty funny"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Sep 21, 2016 at 10:18:55AM -0400, Gene Heskett wrote:
> Greetings all, Dr Klepp in particular;
>
> Where can I get a tut on doing the ssh keyfile login, and where can I
> find a tutorial that is essentialy what Dr. Klepp had me do about a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Sep 23, 2016 at 08:57:18AM +, Curt wrote:
[...]
> Nicolas Georges gave some interesting information once when I said that
> .Xdefaults was "deprecated" concerning what is read by what where and
> why (went over my head, of course).
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Sep 23, 2016 at 11:31:20AM +0200, to...@tuxteam.de wrote:
[...]
> > It makes a big difference for remote applications, since they will see the
> > .Xresources from the server but the .Xdefaults from the client.
Forgot to say that
[mumble]
> >
> >>> This is the bird's view. Ask if you get stuck.
> >
> >
> >> Sorry, Tomas, it's not Gene, it's me who has a special question
> >
> > No need to be sorry :-)
>
> Fine! :-)
> >
> > But I see you found a solution an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Sep 22, 2016 at 04:02:37PM +0200, Tony van der Hoff wrote:
[...]
> It turns out that the recent upgrade took mysql from 5.5 to 5.6. It
> uninstalled mysql-server-5.5, but failed to install mysql-server-5.6,
> due to an unmet dependency on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Sep 22, 2016 at 10:44:28AM +0300, Lars Noodén wrote:
> On 09/21/2016 11:39 PM, Gene Heskett wrote:
> > On Wednesday 21 September 2016 10:23:09 Greg Wooledge wrote:
> ...
> >> man ssh-keygen
> >> http://mywiki.wooledge.org/SshKeys
> >
> > I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Sep 22, 2016 at 12:20:24PM +0200, deloptes wrote:
[...]
> I still use google and if I type in "debian p1109w", the first 10 results
> cover both threads.
> About 1999 doing a research on search engine algos, we (at the university)
> came to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Sep 22, 2016 at 12:43:18PM +0200, Tony van der Hoff wrote:
> Hi,
>
> Running Jessie here. Performed apt-get upgrade yesterday, which included
> a new version of mysql.
>
> I now cannot connect to mysql:
> ERROR 2002 (HY000): Can't connect to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Sep 22, 2016 at 03:35:00PM +, Stephan Beck wrote:
>
>
> to...@tuxteam.de:
[mumble]
> > This is the bird's view. Ask if you get stuck.
> Sorry, Tomas, it's not Gene, it's me who has a special question
No need to b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Sep 22, 2016 at 07:09:53AM -0400, Gene Heskett wrote:
> On Thursday 22 September 2016 03:44:28 Lars Noodén wrote:
>
> > On 09/21/2016 11:39 PM, Gene Heskett wrote:
> > > On Wednesday 21 September 2016 10:23:09 Greg Wooledge wrote:
> >
> > ...
>> Any suggestions on how to fix, please?
> >
> > Is the mysql daemon running? Try "service mysqld status" or however
> > that's named in the brave new systemd world (I'm still in the messy
> > old sysv world, mind you ;-)
> >
> Thanks tomas;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Sep 20, 2016 at 06:30:10PM +0100, Brian wrote:
> On Tue 20 Sep 2016 at 16:12:35 +0100, Lisi Reisz wrote:
>
> > On Monday 19 September 2016 14:15:03 Celejar wrote:
> > > On Sun, 18 Sep 2016 16:14:37 -0400
> > > Haines Brown
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Sep 20, 2016 at 11:01:09AM -0500, David Wright wrote:
[...]
> Sorry, missed out a step. The paps output is filtered through ps2pdf
> so that could explain a lot. Thanks for reminding me. (The clue is in
> the name!)
See above. I can
sion
setup when changing the DM and remember: in the good ol' times DM
and X proper didn't have to run on the same box). Here's one of those
typical Xsession files (I hacked it to give me, as a user, the power
to configure my environment):
tomas@rasputin:~$ cat /etc/X11/Xsession.d/80x1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Aug 17, 2016 at 05:49:39PM +1000, Igor Cicimov wrote:
> On 17 Aug 2016 5:43 pm, "ML mail" wrote:
> >
> > Hello
> >
> > On my Debian 8 machine I have two XFS data partitions on my disk:
> >
>
> Afaik you cant shrink xfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 29, 2016 at 04:59:04AM -0400, brian wrote:
> On Sun, 28 Aug 2016 23:06:16 +0200, you wrote:
>
> >Hi,
> >
> >So it is 12 years later;
> >
> >has someone found something working?
> >
>
> This will be a recommendation which most likely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 29, 2016 at 06:15:23AM -0400, brian wrote:
[Gnus]
> But will it download from multiple newsfeeds *simultaneously*, and
> combine the feeds if you subscribe to the same group from more than
> one source? [...]
TBH I never tried that,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Sep 28, 2016 at 05:03:26PM -0400, Miles Fidelman wrote:
> As a general rule, I find that using Debian packaging for perl makes
> absolutely no sense - and often problematic.
It's more complicated than this. There are other (non-Perl,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Bob.
Welcome.
First, a meta-suggestions
Try to use a good subject line (I tried to modify it).
This list is read by many volunteers, and is pretty high
volume. Nobody reads everything. A good subject line
will make it more probable that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Sep 28, 2016 at 03:34:13PM -0700, Bob Holtzman wrote:
> Sorry. Hit the send key too soon. Subject should have been network
> configuration.
and you already got two proposals for a nicer Subject.
Ain't we a nice bunch ;-)
regards
- -- t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Sep 28, 2016 at 08:36:00AM +, Stephan Beck wrote:
> Hi Lars,
>
> Lars Noodén:
> > On 09/27/2016 06:07 PM, Stephan Beck wrote:
> >> Lars Noodén:
> >>> On 09/27/2016 02:02 PM, Stephan Beck wrote:
> >>> Can you tell more about how your login
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Sep 27, 2016 at 05:53:05PM +0200, Sven Hartge wrote:
[...]
> You should add this _after_ fiddling with the files [...]
Exactly.
regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Oct 03, 2016 at 04:24:42PM -0400, Ken Heard wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> In my jessie box I need to increase the non-encrypted root partition
> (/) size from 14G to 19G. I was able successfully to increase the
sk yourself in each case whether the file behind this symlink
migh be responsible for the missing space.
A practical example:
First, I create a process which keeps a file open, writing into it from
time to time:
| tomas@rasputin:~$ ( while true ; do echo "bip"; sleep 5 ; done ) >
/tmp/lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Sep 26, 2016 at 12:54:49PM +0200, Erwan David wrote:
> A possibility is that you have processes writing into deleted files. You can
> see them with lsof +L1 (as root)
Short and sweet. That's even better :-)
- -- t
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Sep 27, 2016 at 10:55:52AM +0200, Tony van der Hoff wrote:
> On 26/09/16 17:04, to...@tuxteam.de wrote:
> > On Mon, Sep 26, 2016 at 04:38:01PM +0200, Tony van der Hoff wrote:
> >> On 26/09/16 16:03, to...@tuxteam.de wrote:
> >>> On Mon, Sep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Oct 26, 2016 at 04:00:08PM +, Matyas A. Sustik wrote:
> I installed qemu with apt-get. However the qemu command is not found. What
> am I missing? Can anyone point me in the right direction?
I'm assuming you installed "plain qemu", i.e.
sda2
> >
> > Not really.
>
> That gives "-bash: /dev/sda2: Permission denied" for me with a fixed
> disk. It's the same for a removable disk. The system came like that.
Hopefully. But that's not because bash checks that (as parted is).
It's because the permis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Nov 08, 2016 at 02:41:45PM -0500, Stefan Monnier wrote:
> >>> *HOWEVER* parted requires root privileges. That is not acceptable.
> >>> Suggestions?
> >>> TIA
> > Futzing with partitions is the admin's job.
>
> Could be, but it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Nov 06, 2016 at 07:42:40AM +0100, Frank wrote:
> Op 06-11-16 om 04:52 schreef H.S.:
> >So, how do I tell gpg to work on std in when on a terminal instead of
> >relying on a graphical session?
>
> The man page for gpg-agent suggests you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Nov 09, 2016 at 06:29:32PM +, Brian wrote:
[...]
> Raw disk access to a device the user does not own *is* sacred.
YES! And the OS takes care of that part!
> Access to a device the user does own is up to the user.
Again:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Nov 09, 2016 at 05:38:01PM +, Brian wrote:
> On Tue 08 Nov 2016 at 17:54:41 -0500, Stefan Monnier wrote:
>
> > >> > Futzing with partitions is the admin's job.
> > >> Could be, but it's not (g)parted's job to enforce these kinds of rules:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Nov 09, 2016 at 08:48:04PM +, Brian wrote:
> On Wed 09 Nov 2016 at 21:35:14 +0100, to...@tuxteam.de wrote:
[...]
> > Hm. Layering error.
>
> Sorry. I'm unfamiliar with this term ("layering errors")
Sorry. Was meaning to say "layering
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Nov 09, 2016 at 10:45:52AM +, Brian wrote:
[...]
> I hope cfdisk is an acceptable alternative to gparted, which is not on
> my system. 'fakeroot /sbin/cfdisk' gives "cfdisk: cannot open /dev/sda:
> Permission denied".
We are talking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Nov 08, 2016 at 08:39:51PM +, Brian wrote:
> On Tue 08 Nov 2016 at 14:41:45 -0500, Stefan Monnier wrote:
>
> > >>> *HOWEVER* parted requires root privileges. That is not acceptable.
> > >>> Suggestions?
> > >>> TIA
> > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Nov 07, 2016 at 09:35:32AM -0500, Greg Wooledge wrote:
> On Mon, Nov 07, 2016 at 03:27:12PM +0100, to...@tuxteam.de wrote:
> > Two things:
[...]
> I started writing that in my previous message, but then I actually
> tested it on my own
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Nov 07, 2016 at 08:48:29AM -0600, Richard Owlett wrote:
> On 11/7/2016 7:57 AM, to...@tuxteam.de wrote:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
> >On Mon, Nov 07, 2016 at 07:12:00AM -0600, Richard Owlett wrote:
[...]
> I
lves (or more
> >>accurately,
> >>the devices via which your operating system makes the partitions
> >>available to user space). By default (and there are some reasons
> >>for it) they're not readable by everyone. They are writable by
> >>even less. On my box, f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Nov 07, 2016 at 09:27:11AM -0500, Greg Wooledge wrote:
> On Mon, Nov 07, 2016 at 08:18:28AM -0600, Richard Owlett wrote:
> > Evidently not a solution. Added myself to both "disk" and "root"
> > groups.
> > Had no effect when attempting to run
sons
> > for it) they're not readable by everyone. They are writable by
> > even less. On my box, for example:
> >
> > tomas@rasputin:~$ ls -al /dev/sd*
> > brw-rw 1 root disk 8, 0 Nov 7 09:06 /dev/sda
> > brw-rw 1 root disk 8, 1 Nov 7 09:06 /de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Nov 07, 2016 at 07:25:33AM -0600, Richard Owlett wrote:
[...]
> >>*HOWEVER* parted requires root privileges. That is not acceptable.
> >>Suggestions?
[...]
> >So you'd have to be associated to the "disk" group to read those
> >things and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Nov 07, 2016 at 06:37:53AM -0600, Richard Owlett wrote:
> On 11/7/2016 6:20 AM, Felipe Salvador wrote:
> >On Mon, Nov 07, 2016 at 06:11:50AM -0600, Richard Owlett wrote:
> >>*HOWEVER* parted requires root privileges. That is not acceptable.
>
ailable to user space). By default (and there are some reasons
for it) they're not readable by everyone. They are writable by
even less. On my box, for example:
tomas@rasputin:~$ ls -al /dev/sd*
brw-rw 1 root disk 8, 0 Nov 7 09:06 /dev/sda
brw-rw 1 root disk 8, 1 Nov 7 09:06 /dev/sda1
brw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Nov 07, 2016 at 07:12:00AM -0600, Richard Owlett wrote:
[...]
> >Debian is trying to protect you from someone taking over your...
> >say Apache [...]
>
> My Debian machines do not physically have networking capability.
> See my email
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Nov 07, 2016 at 07:54:23PM +0300, Reco wrote:
> Hi.
>
> On Mon, Nov 07, 2016 at 04:05:17PM +0100, to...@tuxteam.de wrote:
> > On Mon, Nov 07, 2016 at 09:35:32AM -0500, Greg Wooledge wrote:
> > > I started writing that in my previous
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Nov 08, 2016 at 11:49:40AM +0100, Laurent Debian wrote:
> Hi and thanks for your ideas
>
> Unfortunately there is no directory /sys/class/backlight on my system.
> After a
>
> > locate backlight
> >
> I juste had the following files as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Nov 10, 2016 at 07:40:06AM -0600, Richard Owlett wrote:
> On 11/10/2016 5:20 AM, to...@tuxteam.de wrote:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
> >On Thu, Nov 10, 2016 at 04:53:47AM -0600, Richard Owlett wrote:
> >>On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Nov 09, 2016 at 04:56:36PM -0700, Joe Pfeiffer wrote:
> Brian writes:
[...]
> >> Hopefully. But that's not because bash checks that (as parted is).
> >> It's because the permissions on the device file are set right!
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Nov 10, 2016 at 04:53:47AM -0600, Richard Owlett wrote:
> On 11/9/2016 5:16 PM, Lisi Reisz wrote:
> >On Sunday 06 November 2016 16:47:00 Richard Owlett wrote:
> >>[snip]
> >>Based on responses to previous posts titled "Trivial script will
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Nov 10, 2016 at 08:27:58AM -0600, Richard Owlett wrote:
> On 11/10/2016 7:58 AM, to...@tuxteam.de wrote:
[...]
> >>I don't understand.
> >
> >Hm. Too concise (both of us ;-)
> >
> >I'll give it a shot. By "you" I meant "user owl, i.e. any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Nov 10, 2016 at 02:53:14PM +, Lisi Reisz wrote:
> On Thursday 10 November 2016 10:53:47 Richard Owlett wrote:
> > On 11/9/2016 5:16 PM, Lisi Reisz wrote:
> > > On Sunday 06 November 2016 16:47:00 Richard Owlett wrote:
> > >> [snip]
> > >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Oct 19, 2016 at 11:37:08AM +0100, Brian wrote:
> On Tue 18 Oct 2016 at 10:22:24 -0500, Richard Owlett wrote:
>
> > On 10/18/2016 9:20 AM, Darac Marjal wrote:
> > >On Tue, Oct 18, 2016 at 08:51:00AM -0500, Richard Owlett wrote:
> > >>With
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Oct 19, 2016 at 09:22:00AM -0500, Richard Owlett wrote:
> On 10/19/2016 6:08 AM, to...@tuxteam.de wrote:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
> >On Wed, Oct 19, 2016 at 11:37:08AM +0100, Brian wrote:
> >>On Tue 18 Oct 2016
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Oct 23, 2016 at 05:09:06PM -0400, Carl Fink wrote:
> So I have a ThinkPad Yoga 11s ultrabook.
>
> If I copy over the firmware-realtek package, Debian can install just
> fine over the WiFi connection. (I don't have wired internet at my
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Oct 18, 2016 at 10:22:24AM -0500, Richard Owlett wrote:
> On 10/18/2016 9:20 AM, Darac Marjal wrote:
[...]
> >You will need to convert a font of your choice to GRUB's pf2 format:
[...]
> I'm confused. We may be using the term "font"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Oct 24, 2016 at 07:58:52AM -0500, Richard Owlett wrote:
> I suspect an appropriate response would be being pointed an
> *atypical* tutorial.
> A Google search for "bash tutorial pipe redirect" [w/o quotes] gave
> results for "normal" users. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Oct 23, 2016 at 03:30:52PM -0700, Bob Holtzman wrote:
> On Thu, Sep 29, 2016 at 11:31:28AM +0200, to...@tuxteam.de wrote:
>
> My abject apologies for the delay in this reply. just got back in town
> and am just catching up on my email.
No
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Oct 25, 2016 at 10:59:20AM +0100, Brian wrote:
> On Tue 25 Oct 2016 at 11:16:49 +0200, to...@tuxteam.de wrote:
>
> > > loLink encap:Local Loopback
> > > inet addr:127.0.0.1 Mask:255.0.0.0
> >
> > This is the "local"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Oct 25, 2016 at 01:05:54PM +0100, Brian wrote:
[...]
> Uncharacteristically, I did wander a bit off topic, didn't I?
This way I (and perhaps others) learnt something.
> Back on the straight and narrow now. :)
But not too much: everything
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Oct 25, 2016 at 11:54:27AM +0100, Brian wrote:
> On Tue 25 Oct 2016 at 12:36:11 +0200, to...@tuxteam.de wrote:
>
> > On Tue, Oct 25, 2016 at 10:59:20AM +0100, Brian wrote:
> > > On Tue 25 Oct 2016 at 11:16:49 +0200, to...@tuxteam.de wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Oct 25, 2016 at 11:40:10AM -0400, Greg Wooledge wrote:
> On Tue, Oct 25, 2016 at 10:32:29AM -0500, Richard Owlett wrote:
> > I'm in a multi-boot environment, multiple installs of Debian.
> > I want all install to have read/write/execute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Oct 21, 2016 at 01:17:21PM -0500, Richard Owlett wrote:
[...]
> CONCLUSION
> Can *NOT* blame Microsoft Windows for EVERYTHING ;/
My conclusion too. There's something else acting up. Linux should
pick up the hw clock and *know* it's not in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Oct 21, 2016 at 09:11:07PM +0200, to...@tuxteam.de wrote:
> On Fri, Oct 21, 2016 at 09:21:17AM -0500, Richard Owlett wrote:
>
> [...]
>
> > Relavant lines of preseed.cfg are
> >
> > ### Clock and time zone setup
> > #d-i clock-setup/utc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Oct 21, 2016 at 09:21:17AM -0500, Richard Owlett wrote:
[...]
> Relavant lines of preseed.cfg are
>
> ### Clock and time zone setup
> #d-i clock-setup/utc boolean false
> d-i clock-setup/utc boolean true
> d-i time/zone string US/Central
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Oct 21, 2016 at 03:09:46PM -0500, Richard Owlett wrote:
[...]
If you want to get to the ground of things, on my system (yes, I'm on SysV
init, for systemd you'll have to find out for yourself), the magic happens
in /etc/init.d/hwclock.sh.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Oct 21, 2016 at 08:09:38AM -0500, Richard Owlett wrote:
> I'm creating a preseed.cfg file for installing Debian 8.6 in a
> dual-boot enviroment with some version of MS Windows. There are two
> distinct use cases:
>1. Two of my machines
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Oct 21, 2016 at 10:28:34PM +0900, Mark Fletcher wrote:
[...]
> I went with vfat, but I'd like to resolve the question of exfat if
> possible, out of curiosity.
I was curious too, so I dropped the thing into my favourite search
engine (no,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Nov 12, 2016 at 01:25:50PM -0600, Richard Owlett wrote:
> On 11/12/2016 12:26 PM, Pascal Hambourg wrote:
> >Le 12/11/2016 à 18:22, Richard Owlett a écrit :
> >>
> ddrescue /dev/sda /mnt/defective_drive.img
> /mnt/defective_drive.log
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Nov 25, 2016 at 03:57:53PM -0800, Patrick Bartek wrote:
> On Fri, 25 Nov 2016 21:26:06 + (UTC) Latincom
> wrote:
>
> > On Fri, 25 Nov 2016 16:31:54 +, Brian wrote:
> >
> > > On Fri 25 Nov 2016 at 15:21:23 +,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Nov 26, 2016 at 10:27:07AM +, Joe wrote:
> On Sat, 26 Nov 2016 10:02:50 +0100
> wrote:
>
> > On Fri, Nov 25, 2016 at 03:57:53PM -0800, Patrick Bartek wrote:
>
> > >
> > > If you do a normal dist-upgrade Wheezy to
601 - 700 of 4838 matches
Mail list logo