On Saturday 05 Jan 2013 02:26:18 Walter Dnes wrote:
> One last gasp... were you doing this as root? Regular users cannot dd
> directly to a device, for obvious reasons.
Yes, also tried it as root. No change. BTW, with the device mounted I
shouldn't have a problem with dd on a file.
--
Rega
On Friday 04 Jan 2013, Canek Peláez Valdés wrote:
> On Fri, Jan 4, 2013 at 10:11 AM, Robin Atwood
>
> wrote:
> > Having observed all the ranting, I thought I would try systemd on a
> > laptop. It actually seems to work quite well and it is a lot faster.
> > However I am having trouble getting my
I have a very severe problem after a recent disk replacement. After a few days
running, all new processes just hang. The kernel reports:
Jan 5 02:25:36 opal kernel: INFO: task mysqld:11387 blocked for more than 120
seconds.
Jan 5 02:25:36 opal kernel: "echo 0 >
/proc/sys/kernel/hung_task_time
This is relay wired. You also cannot lock on startup. Maybe something
with your config. Did you try backup all E17 configuration and run with
clean? (eg: "mv .e .e.old" with E17 not running) Than try if lock on
startup can be configured.
Please post your "emerge -pv enlightenment:0.17".
Robert.
james wrote:
After deleting the 70-persistent-net.rule file
udev does not re-create it. All is now fine with rc-status
only showing net.eth0 which is set up how I like it
per /etc/conf.d/net. All services are fine
Beware. The automatic persistent net rules generator is intrinsically
broken be
On Sat, Jan 5, 2013 at 8:03 AM, Kerin Millar wrote:
> james wrote:
>>
>> After deleting the 70-persistent-net.rule file
>>
>> udev does not re-create it. All is now fine with rc-status
>> only showing net.eth0 which is set up how I like it
>> per /etc/conf.d/net. All services are fine
>
>
> Beware
Hello All loop-aes Users,
Up to now, every time a new version of util-linux was out, we had to
wait for loop-aes patch in order to use it within loop-aes
environment.
The dependency between loop-aes and util-linux was hard to maintain
for both base-system, crypto and users.
Basically, all we nee
On Sat, Jan 5, 2013 at 7:36 AM, Robin Atwood wrote:
> On Friday 04 Jan 2013, Canek Peláez Valdés wrote:
>> On Fri, Jan 4, 2013 at 10:11 AM, Robin Atwood
>>
>> wrote:
>> > Having observed all the ranting, I thought I would try systemd on a
>> > laptop. It actually seems to work quite well and it i
I think I touched on this a couple of weeks ago but never had time to
dig in. At that time I thought this problem was only on one machine
but now I see it's on every machine I've looked at this morning. Not a
single machine has /dev/cdrom anymore, nor /dev/dvd or any of the
other incantations that
Mark Knecht wrote:
>I think I touched on this a couple of weeks ago but never had time to
>dig in. At that time I thought this problem was only on one machine
>but now I see it's on every machine I've looked at this morning. Not a
>single machine has /dev/cdrom anymore, nor /dev/dvd or any of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/05/2013 02:53 PM, Mark Knecht wrote:
> I think I touched on this a couple of weeks ago but never had time
> to dig in. At that time I thought this problem was only on one
> machine but now I see it's on every machine I've looked at this
> morning
On Sat, Jan 5, 2013 at 11:53 AM, Mark Knecht wrote:
> I think I touched on this a couple of weeks ago but never had time to
> dig in. At that time I thought this problem was only on one machine
> but now I see it's on every machine I've looked at this morning. Not a
> single machine has /dev/cdrom
On Sat, Jan 5, 2013 at 12:36 PM, J. Roeleveld wrote:
> Mark.
>
> Not seen this behaviour myself. But I also only have one machine with a
> dvd-drive in it. And that one has not been updated in several months. (It's
> scheduled for a complete rebuild)
>
> Did you try temporarily removing that ru
On Sat, 5 Jan 2013 12:44:07 -0800
Mark Knecht wrote -
> On Sat, Jan 5, 2013 at 11:53 AM, Mark Knecht wrote:
> > I think I touched on this a couple of weeks ago but never had time to
> > dig in. At that time I thought this problem was only on one machine
> > but now I see it's on every machine I'v
Mark Knecht wrote:
> I think I touched on this a couple of weeks ago but never had time to
> dig in. At that time I thought this problem was only on one machine
> but now I see it's on every machine I've looked at this morning. Not a
> single machine has /dev/cdrom anymore, nor /dev/dvd or any of t
15 matches
Mail list logo
