On Thu, Sep 19, 2019 at 09:10:20AM +0200, John Paul Adrian Glaubitz wrote:
> (...)
> So, can you please type "ip a" and check what device name is actually assigned
> to your wired card and if it differs from "eth0", adjust your /etc/network/
> interfaces file?
>
> If your wired card is actually
Hi Bob!
On 9/19/19 7:09 AM, Bob Tracy wrote:
On Wed, Sep 18, 2019 at 11:46:06AM +0200, John Paul Adrian Glaubitz wrote:
Your permanent bashing of systemd makes answering your mails stressful
for me.
Adrian -- please accept my apology for my rantings... They contribute
nothing to the
On Wed, Sep 18, 2019 at 11:46:06AM +0200, John Paul Adrian Glaubitz wrote:
> Your permanent bashing of systemd makes answering your mails stressful
> for me.
Adrian -- please accept my apology for my rantings... They contribute
nothing to the conversation, and as you note, irritate the very
On Wed, Sep 18, 2019 at 11:46:06AM +0200, John Paul Adrian Glaubitz wrote:
> is just annoying. Please let's have a more constructive discussion, after
> all, the previous issues on alpha were not caused by systemd either but
> a bug in glibc for alpha.
I would not be so quick to blame glibc. (If
Hi Bob!
On 9/18/19 1:48 AM, Bob Tracy wrote:
It appears that all the configuration info in "/etc/network/interfaces"
for my "eth0" interface was completely ignored other than the IPv4
address. No IPv6 address, no "dns-*" config items, etc. Thanks,
systemd! Not :-(. I blame "systemd",
On Mon, Sep 16, 2019 at 09:38:55PM -0500, Bob Tracy wrote:
> I say "almost clean", because a recent update managed to break my
> resolver configuration: "/etc/resolv.conf" came up completely empty, in
> spite of "/etc/network/interfaces" having the requisite
> "dns-nameservers" and "dns-search"
Cc: debian-alpha@lists.debian.org
Subject: Re: systemd woes continue
Hi Bob!
On 9/17/19 4:38 AM, Bob Tracy wrote:
> Verified. Life is now better, if not good :-). This is the first time
> I've been able to accomplish an "almost clean" boot of my Alpha in MANY
> mon
Hi Bob!
On 9/17/19 4:38 AM, Bob Tracy wrote:
Verified. Life is now better, if not good :-). This is the first time
I've been able to accomplish an "almost clean" boot of my Alpha in MANY
months.
Great. Thanks for confirming.
I say "almost clean", because a recent update managed to break
On Mon, Sep 09, 2019 at 10:49:25PM +0200, Aurelien Jarno wrote:
> > ...
> >
> > You are in emergency mode. After logging in, type "journalctl -xb" to view
> > system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
> > to boot into default mode.
> > Give root password for
On 2019-09-01 21:12, Aurelien Jarno wrote:
> On 2019-07-17 20:36, Michael Cree wrote:
> > On Wed, Jul 10, 2019 at 09:54:40PM -0500, Bob Tracy wrote:
> > > First, "systemd" still cannot handle systems with persistent filesystems
> > > other than "/" and "/usr". As far as I know, the bug report I
Hi!
On 9/1/19 9:12 PM, Aurelien Jarno wrote:
>> The bug I see on my XP1000 with systemd is that it fails to mount
>> the filesystems in /etc/fstab and so stops in emergency mode; one
>> can enter the root password, issue "mount -a" and "swapon -a" and
>> exit and the boot resumes fines.
>
> This
On 2019-07-17 20:36, Michael Cree wrote:
> On Wed, Jul 10, 2019 at 09:54:40PM -0500, Bob Tracy wrote:
> > First, "systemd" still cannot handle systems with persistent filesystems
> > other than "/" and "/usr". As far as I know, the bug report I filed
> > against "systemd" is still open, and no
On Wed, Jul 17, 2019 at 01:45:21PM +, Witold Baryluk wrote:
> Hey John,
>
> > The gist is: A lot of projects don't test their code on systems with
> separate
> > /usr partitions anymore, so things get silently broken.
>
> I don't have separate /usr, just single / (ext4) partition, and just
>
On Wed, Jul 17, 2019 at 03:16:09PM +0200, Frank Scheiner wrote:
> To sum things up: what Adrian intends to do for Alpha - pre-include the
> firmware on the installer discs - seems to be the only way to get this
> problem fixed w/o manual intervention during installation.
Many other things to
On 7/17/19 4:13 PM, Frank Scheiner wrote:
> Probably not, as [3] shows that one still needs to use different
> directories for the different targets.
>
> [3]: http://deb.debian.org/
>
> Ok, what about a redirect on the Debian-Ports mirror for a
> "/debian-ports/pool/non-free/" directory to e.g.
On 7/17/19 3:50 PM, Frank Scheiner wrote:
> Ok, could it work when using the CDN (deb.debian.org) as described on
> [2]? Or does this just redirect to the actual ports mirror for ports
> architectures?
>
> [2]: https://www.ports.debian.org/mirrors
debian-cd requires a mirror to be available
On 7/17/19 3:45 PM, Witold Baryluk wrote:
>> The gist is: A lot of projects don't test their code on systems with separate
>> /usr partitions anymore, so things get silently broken.
>
> I don't have separate /usr, just single / (ext4) partition, and just separate
> /boot (ext2), and still systemd
On 7/17/19 15:50, Frank Scheiner wrote:
On 7/17/19 15:41, John Paul Adrian Glaubitz wrote:
On 7/17/19 3:16 PM, Frank Scheiner wrote:
To sum things up: what Adrian intends to do for Alpha - pre-include the
firmware on the installer discs - seems to be the only way to get this
problem fixed w/o
On 7/17/19 15:41, John Paul Adrian Glaubitz wrote:
On 7/17/19 3:16 PM, Frank Scheiner wrote:
debian-installer doesn't use fdisk (anymore), it uses partman. Did you try any
of
the recent installation images, see [1]. Please note these images are currently
shipped without proprietary firmware.
Hey John,
> The gist is: A lot of projects don't test their code on systems with
separate
> /usr partitions anymore, so things get silently broken.
I don't have separate /usr, just single / (ext4) partition, and just
separate /boot (ext2), and still systemd fails to mount this /boot file
system,
On 7/17/19 3:16 PM, Frank Scheiner wrote:
debian-installer doesn't use fdisk (anymore), it uses partman. Did you try
any of
the recent installation images, see [1]. Please note these images are
currently
shipped without proprietary firmware.
>>>
>>> Yeah, that's a
On 7/17/19 11:54, John Paul Adrian Glaubitz wrote:
On 7/17/19 11:00 AM, Michael Cree wrote:
On Thu, Jul 11, 2019 at 04:11:44PM +0200, John Paul Adrian Glaubitz wrote:
I assume you are talking about the non-functionality of a separate /usr
partition,
but this is something that isn't guaranteed
On 7/17/19 11:00 AM, Michael Cree wrote:
> On Thu, Jul 11, 2019 at 04:11:44PM +0200, John Paul Adrian Glaubitz wrote:
>> systemd works the same way on my Alpha XP-1000 as it works on my Intel boxes.
>
> Interesting. It doesn't work on mine; it fails to mount the
> filesystems even when I
I do have similar issue with systemd.
It fails "local-fs.target" task, unless I remove /boot (which is on
separate device) entry from "/etc/fstab"
swap works (based on "free" and "/proc/swaps"), and systemd does enable it
automatically.
Another issue I do face, is that systemd doesn't bring up
On Thu, Jul 11, 2019 at 04:11:44PM +0200, John Paul Adrian Glaubitz wrote:
> systemd works the same way on my Alpha XP-1000 as it works on my Intel boxes.
Interesting. It doesn't work on mine; it fails to mount the
filesystems even when I recently tried a new install into a
spare partition (but
On Wed, Jul 10, 2019 at 09:54:40PM -0500, Bob Tracy wrote:
> First, "systemd" still cannot handle systems with persistent filesystems
> other than "/" and "/usr". As far as I know, the bug report I filed
> against "systemd" is still open, and no progress has been made on that
> front.
The bug I
On Thu, Jul 11, 2019 at 09:48:14PM +0900, John Blake wrote:
> (...)
> I have a DS10L 617mhz and I can't figure out which version is the best to
> attempt to install on it.?? I'd rather avoid things like this issue with
> systemd where they obviously haven't tried to actually test it on an alpha
>
It's been a year or two since I last tried to install the experimental
debian alpha image on my DS10L, and my abiding memory of the last
attempt was banging my head against a problem with creating BSD
disklabel on the ide hard drive due to fdisk being updated a few years
prior to remove the
Hi John!
On 7/11/19 2:48 PM, John Blake wrote:
> I have a DS10L 617mhz and I can't figure out which version is the best to
> attempt to install on it. I'd rather avoid things like this issue with
> systemd where they obviously haven't tried to actually test it on an alpha
> processor, but I
This brings up a question I need to ask of the people who know best on
this mailing list:
I have a DS10L 617mhz and I can't figure out which version is the best
to attempt to install on it. I'd rather avoid things like this issue
with systemd where they obviously haven't tried to actually
30 matches
Mail list logo
