-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Allums wrote:
> On 4/26/2010 5:24 PM, Clive McBarton wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Mark Allums wrote:
>>> Some people are scared of shared folders as possible attack vectors,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stan Hoeppner wrote:
> Rob Owens put forth on 4/28/2010 8:26 PM:
>> Many/most
>> users don't run a UPS and sudden unexpected power loss is a real
>> possibility for them.
>
> Really? I was under the impression that laptops and netbooks are now the
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Allums wrote:
> Some people are scared of shared folders as possible attack vectors, thus
> security risks.
What exactly are those risks?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin Ross wrote:
> "Reply to List" button (which I know
> was available as an add-on before)
You remember what the add-on is called? Searching for "reply to list" in
add-ons didn't give me anything.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Kulzer wrote:
> On Tue, Apr 20, 2010 at 07:08:23 -0500, John Hasler wrote:
>> Clive McBarton writes:
>>> The debian-multimedia-keyring is not restricted by patents or any
>>> other licence issues. I understand why
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Ianson wrote:
> Clive McBarton wrote:
>> It would help a lot if the key of d-m (package
>> debian-multimedia-keyring) was in the debian repos, not just the d-m
repos.
>
> All the stuff at debian-multimedia can't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron Johnson wrote:
> On 2010-04-19 16:19, Clive McBarton wrote:
> [snip]
>>
>> How come there is no link anywhere on debian.org pointing to
>> debian-multimedia.org? Anything to establish a chain of trust. As it is,
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Camaleón wrote:
> I was a KDE 3.5.x user for long time (2003-2010) but switched to GNOME as
> soon as the first KDE 4.0 came to scene (it was not intended for end-
> users but *we had* to deal with it and the result was many people
> searched another
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron Johnson wrote:
>>> There use to be a "preloader", but I don't see it anymore.
>>
> There was a feature where GNOME or KDE would pre-load OOo at DE
> startup. That way, it *appears* that OOo loads much faster, even though
> it was really just shift
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Liam O'Toole wrote:
>> Adding debian-multimedia.org breaks a couple of things. Including vlc. I
>> don't know why they don't fix their repository.
>>
>> I'm curious if many people use debian-multimedia. Is it trustworthy?
>>
>>
>
> I have been using d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark wrote:
> I also have been using debian-multimedia for LAME mp3 and am very thankful
> for its existence.
Yes, it's useful for that. Though if it's just lame, it's probably
simpler to compile the source than to add a repo.
> without the debian-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron Johnson wrote:
> ATX means you'll get lots of built-in features. I like my Gigabyte
> GA-MA780G-UD3H mobo with AM2+/AM2 socket.
>
> 8GM RAM, 6 SATA, 1 (or 2, I forget) rear eSATA, lots of USB, a front and
> rear Firewire and decent on-board audio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark wrote:
> On Thu, Apr 15, 2010 at 11:06 AM, Mark wrote:
>
>> Has anyone else experienced mplayer generating Fatal Error "Error
>> opening/initializing the selected video_out (-vo) device" after adding
>> debian-multimedia.org to sources.list and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
M.Lewis wrote:
> Would it be better to move the LVM to a larger SATA drive and migrate
> the boot drive on to a new small IDE HD? I've even thought to set it up
> to boot from a flash drive. Not sure that would be wise either.
>
> My question is is th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul E Condon wrote:
>> My understanding is that S.M.A.R.T. doesn't generally work over USB.
>
> So, the fact that my WD drives don't play well with S.M.A.R.T doesn't
> make them special, and I should not spend much, if any, time looking
> for a USB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sjoerd Hardeman wrote:
> Clive McBarton schreef:
>> Sjoerd Hardeman wrote:
>>> mount the new device (mount -odev /dev/newdevice), and do a
>>> rsync -ax / /media/newdevice.
>> What exactly is the advantage of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Kulzer wrote:
> Did you have any security upgrades lately
Sure, I install them regularly. Doesn't everybody?
> or did you install packages from backports or volatile
I do have the following as part of my sources.conf:
deb http://volatile.d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron Johnson wrote:
>Never destroy the original until you know the copy works!
In my earlier days I would have avoided mv for exactly that reason. But
when copying (including rsync), you cannot easily see that it worked
from the emptyness of the origin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eduardo M KALINOWSKI wrote:
>>> mount the new device (mount -odev /dev/newdevice), and do a
>>> rsync -ax / /media/newdevice.
>>>
>> What exactly is the advantage of this approach over "cp -a" or "mv"?
>>
>
> Over mv? That you keep the ori
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sjoerd Hardeman wrote:
> mount the new device (mount -odev /dev/newdevice), and do a
> rsync -ax / /media/newdevice.
What exactly is the advantage of this approach over "cp -a" or "mv"?
I would have suggested mv. It has the useful property that you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Kulzer wrote:
> On Sat, Apr 10, 2010 at 19:20:42 +0200, Clive McBarton wrote:
>> I run KDE and normally mount usb devices with the "Storage Media" applet
>> in the task bar. Recently I have been getting strange erro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony Nelson wrote:
> If the data in a sector was not readable, the sector
> will be listed as "Pending". Pending sectors are much worse than
> Reallocated sectors, as Pending sectors mean lost data (if the sector
> was in actual use, which SMART do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I run KDE and normally mount usb devices with the "Storage Media" applet
in the task bar. Recently I have been getting strange errors and
mounting failed:
Rejected send message, 3 matched rules; type="method_call",
sender=":1.21" (uid=101 pid=13921 c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Kulzer wrote:
>> Interesting. So what is /badblocks/ for,
>
> I would say it is useful to make the drive access every single block;
> afterwards you can check in the SMART log if that caused any remappings.
That's a good idea.
Another appl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrei Popescu wrote:
> On Sat,10.Apr.10, 08:51:16, Clive McBarton wrote:
>
>> Certainly so. What I meant to ask is what to do if you (like the OP)
>> want automatic upgrades (downloaded and installed without the admin
>> pre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul E Condon wrote:>
> dumpe2fs -b is supposed to print the bad blocks that have
> been marked on a device. When I run it, it prints nothing. I find it
> hard to believe that a 500GB HD contains ZERO bad blocks.
Every HD that is even remotely close
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Hasler wrote:
> Clive writes:
>> It does help the OP since he uses apt-get, but what about the people
>> who normally use aptitude?
>
> If you are only using it for downloads (usual) it doesn't matter.
Certainly so. What I meant to ask is what t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron Johnson wrote:
> Anyway, the cron-apt package does what you want. It is recommended,
> though, to use it only for downloads.
It does help the OP since he uses apt-get, but what about the people who
normally use aptitude? There's no "cron-aptitude
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rick Thomas wrote:
>
> On Mar 22, 2010, at 7:10 PM, Clive McBarton wrote:
>
>> prepends it with
>> sufficiently many (3 suffices?) good nameservers, so it never gets used
>> and everything is fine.
>
> Nothing is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Zuelow wrote:
>> Yet, relying on the immutability of /etc/resolv/conf is like
>> relying on
>> the persistence of files on /tmp: just DON'T!
>>
>
> 2nd note that my suggestion to make /etc/resolv.conf immutable was not to
> keep his changes, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dotan Cohen wrote:
> I can have as many open connections as I want, it's on the LAN. But I
> would _prefer_ just one terminal window for both commands (SSH) and
> file transfers.
First of all, I believe the ssh protocol (not necessarily the ssh
progra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Camaleón wrote:
> Didn' you try some of the tips? They only require passing some options to
> the kernel at boot time and there is nothing harmful in doing that :-?
Most of them are harmless. Some even make the error message go away. At
least one of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Allums wrote:
> probably more and more people have a mail UA that has reply-to-list,
> like Thunderbird 3.
Lenny's default Thunderbird (that is, 2.0.0.22) doesn't though. I
believe it requires manually changing "Cc:" to "To:" in the list address
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron Johnson wrote:
> You must have missed the BIG BOLD LETTERS that tell you not to write
> into resolv.conf by hand.
>
> $ cat /etc/resolv.conf
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
> resolvconf(8)
> # DO NOT EDIT THI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron Johnson wrote:
>> I carefully type a domain name and some decent nameservers into
>> resolv.conf.
>>
>> Then all of it gets deleted and replaced by one single nameserver, which
>> is the router and the nameserver of my provider.
>
> Well, yeah, th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Camaleón wrote:
> Not sure if this has something to do with some BIOS option that allow
> "memmory remapping" :-?
There's no such option. Not in any BIOS I've ever seen.
> There is an Ubuntu forum thread that may help a bit
It doesn't. It's a long
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Powell wrote:
> What kinds of changes do you see happening and what changes are you
> trying to prevent? What harm is being caused by those changes?
> In other words, what is the real world problem you are trying to solve?
I carefully type a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To make my original question more precise: I want the stuff I write into
resolv.conf to persist, but it does not have to be in that file. I'm
happy to write things elsewhere as long as *some place* makes my changes
persistent.
Sjoerd Hardeman wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Camaleón wrote:
> On Thu, 18 Mar 2010 16:53:20 +0100, Clive McBarton wrote:
>
>> My /etc/resolv.conf gets overwritten periodically. Any ideas why?
>
> Maybe because you are using a DHCP setup?
Yes.
> http://wiki.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My /etc/resolv.conf gets overwritten periodically. Any ideas why?
I thought network-manager was the culprit and deinstaled it, but the
problem persists.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Powell wrote:
> If you can't figure out how to make grub use the "list of sectors"
> method, I once again suggest that you switch to lilo.
The whole point is to make the system secure. So let's look at lilo's
security:
Password stored as pl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Monnier wrote:
>> this evidently does not overwrite the boot sector, does grub-install do
>> this? I have yet to run grub-install. Of course, this would not explain why
>> my system still boots after deleting the vmlinuz files.
>
> Yes it could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob McGowan wrote:
> This brings up the question, though, as to why these forced checks are
> done in the first place. The man page talks about failed hardware and
> kernel bugs, etc., but ...
Very interesting point. Indeed running fsck when the shut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carlos Davila wrote:
> I deleted the following files from /:
>
> initrd.img initrd.img.old vmlinuz vmlinuz.old
>
> and I deleted all files in /boot:
>
> config-2.6.26-2-686initrd.img-2.6.26-2-686
> System.map-2.6.26-2-amd64
> config
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Brockway wrote:
> Hi Clive. I've never used diff to compare binary files.
>
> Is the md5sum of the different files the same?
diff works fine on binary, why shouldn't it? The output is empty or
"binary files differ". I never bothered to verify
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Brockway wrote:
> Are you concerned about corruption
Filesystem corruption? Not at all. It's a read-only partition. It cannot
go corrupt unless the disk breaks.
> or someone (with root) compromising your kernel image
Indeed.
> Also even if /
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Hector wrote:
> On Mon, 2010-03-08 at 23:11 +0100, Clive McBarton wrote:
>
>> When I reboot, the partition /boot (it is a separate partition, not a
>> directory) changes. It is not supposed to. None of the files on it have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mario 'BitKoenig' Holbe wrote:
> Clive McBarton wrote:
>> and while the system is turned off. The "online to offline" comparison
>> works fine, whereas the "offline to online" does not always work, h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thib wrote:
>>> Would you care to share your solution, Clive?
>>
>> Currently I take checksums of the partition regularly during operation
>> and while the system is turned off. The "online to offline" comparison
>> works fine, whereas the "offline to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron Johnson wrote:
> Note that "Last write time:" might not mean what you think it does. I
> say that because on my system /dev/sda2 is / and I've written a whole
> bunch of data to it in the past 25.5 days, yet the LWT still matches the
> LMT.
Very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron Johnson wrote:
> # dumpe2fs -h /dev/sda2 | grep time
> dumpe2fs 1.41.10 (10-Feb-2009)
> Last mount time: Sat Feb 13 08:39:01 2010
> Last write time: Sat Feb 13 08:39:01 2010
>
Great command. Good to know it.
I used that and fou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cameron Hutchison wrote:
> If it were me trying to diagnose this, I would be diffing the images
> that should be the same and seeing where they are different.
OK. I tried that. Unfortunately more rebooting did not produce any new
change in the boot pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thib wrote:
> Sorry, I meant, how would you run the hashing program before the
> reboot? I think it has little value if it's ran by the live system
> beeing checked. Sames goes for a check after the actual boot - only a
> hypervising or external syste
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thib wrote:
> Clive McBarton wrote:
>>> For the record, grub can also load a kernel and an initrd by just
>>> providing a block list, as you described for lilo. Since the filesystem
>>> is made read-only, this shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> ro Mount filesystem read only. Note that ext3 will replay
>> the journal (and thus write to the partition) even when
>> mounted "read only". Mount options "ro,noload" can be
>> used to prevent writes to the filesystem.
Great! Spect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thib wrote:
> For the record, grub can also load a kernel and an initrd by just
> providing a block list, as you described for lilo. Since the filesystem
> is made read-only, this shouldn't be too ugly and certainly worth trying.
Really? Great. How e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thib wrote:
> Well, ask the
> developers of whatever is touching it. If noboby knows, that will
> require some code digging.
But I don't know what is touching it. That's what this thread is about.
It's about me asking what is touching it. All I know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thib wrote:
> maybe it would be acceptable to ask for a new little switch.
> Or hack ext3.
Ask who? The maintainers of tune2fs? The maintainers of ext3? Both will
say what I already know, that manually mounting and unmounting an ext3
partition read-on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thib wrote:
> Maybe someone simply has reasons not to put /boot on a separate volume.
> Now I sure agree that it isn't needed in virtually every other cases,
> but would it really hurt?
We are already discussing this in your thread "Single root files
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thib wrote:
> I would suggest going through the tune2fs(8) manpage and find
> out what could be.. tuned. You know what? I think your first
> suggestion is a good one - look at the mount count configuration for a
> starter.
OK, I studied the tune2fs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob McGowan wrote:
> It is almost certainly the mount count.
I just manually unmounted and mounted the device a few times. With the
arguments I have in fstab ("ro","noatime"). In other words, I did
umount /boot; mount /boot; dd_rescue /dev/sda1 /tmp/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Moore wrote:
> Is this checksum failing for every file, or just some?
It's the checksum for the partition that changes. I don't have checksums
of the individual files but since the metadata of every single file
stays the same, presumably so do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thib wrote:
> I'm guessing OP literally checksums the volume from the block device.
Yes, of course. I mean "md5sum /dev/sda1".
> If I'm right, it could be anything, really, lots of filesystem metadata
> moving around without actually touching any fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When I reboot, the partition /boot (it is a separate partition, not a
directory) changes. It is not supposed to. None of the files on it have
changed or can change, since it is mounted with option "ro". But the
checksum of the partition changes.
Is th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stan Hoeppner wrote:
> http://www.debian-administration.org/articles/388
>
> "Based on all testing done for this benchmark essay, XFS appears to be the
> most appropriate filesystem to install on a file server for home or
> small-business needs :
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a file which is a dump of a disk partition. It has LVM on it and
a couple of LVs in the LVM, each containing a filesystem. How do I
access them? The lvm tools like lvdisplay, vgdisplay, lvs, lvscan,
lvdiskscan expect block devices and do not hav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alex Samad wrote:
> my 2c, with the size of HD's and the processing power we have now, I
> really wonder if spending more than a second on deciding on a single
> partition or not is worth it.
It's theoretical reasoning. It's good for understanding. A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thib wrote:
>> You trust ext4, and so does Ubuntu. Others (including most distros,
>> including Debian) do not.
>
> I'm sorry if I should know, but is that a clear position or the general
> fear around delayed allocation?
google "ext4 kde4" and the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stan Hoeppner wrote:
> /var up2uext2sequential write/read, journal unnecessary
I don't see the advantage of ext2 over ext3 here (or for that matter
anywhere else, which may just be my ignorance). The journal may be
unnecessary, but it doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I find the concept very interesting in principle, although I am not sure
I can recommend it. In some respects single file systems are more
acceptable nowadays. In others they are not. Here are my $.02:
> * Filesystem corruption containment
>
> I use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why does the current major update (kernel even!) not show up on
http://www.debian.org/security/ ? Nor does it show up in the list
"Security Advisories from 2010" http://www.debian.org/security/2010/ . I
had to go to http://lists.debian.org/debian-secur
71 matches
Mail list logo
