On Wed, 18 Sep 2019 at 08:17, Gene Heskett wrote:
> On Tuesday 17 September 2019 15:07:30 ghe wrote:
> > On 9/17/19 11:01 AM, Gene Heskett wrote:
> > > And that results in exactly the same effect, partitiuon 1 is an
> > > iso9660 image, and I don't believe the rpi-3b supports that for a
> > > boo
Thomas Schmitt writes:
> I get the impression that uboot is a usual firmware and bootloader,
> but that there are also mechanisms which rather remind me of the ROM
> of my VIC-20.
On boards like this UBoot is usually stored in onboard memory and pretty
much is the "BIOS" and the bootloader as well
On Tuesday 17 September 2019 15:07:30 ghe wrote:
> On 9/17/19 11:01 AM, Gene Heskett wrote:
> > And that results in exactly the same effect, partitiuon 1 is an
> > iso9660 image, and I don't believe the rpi-3b supports that for a
> > boot medium. dos/fat32 only I believe. Obviously I got those ima
Le mardi 17 septembre 2019 22:00:05 UTC+2, Étienne Mollier a écrit :
[...]
> I am seriously considering sticking to UEFI
> Secure Boot, not exactly for security, mostly to have a general
> idea of how things work, by practice.
[...]
I have not tested it myself (only KVM/Ovmf but without SecureBoot
Baptiste, on 2019-09-17:
> I have two critical systemd services running on my clients :
> -> "puppet" that ensure propagation of my whole network configuration.
> -> "samba winbind" that allow users pam authentication and Name Service
> Switch.
> These two services use DNS to find their services s
Two problems after a distribution upgrade to Buster
1. At login window after boot up the desktop selection is locked a
Gnome. That is, if the symbol to change the desktop selection is
selected a list of available desktops is displayed with a dot indicating
Gnome is the current selections. Ther
On Tue, Sep 17, 2019 at 10:59:53PM +0200, Sven Joachim wrote:
> On 2019-09-17 09:13 -0400, Greg Wooledge wrote:
> > wooledg:~$ aptitude why systemd-sysv
> > i udev Depends dpkg (>= 1.19.3) | systemd-sysv
> >
> > OK... I'll admit, I do not quite understand that dependency.
>
> The udev init scrip
On 2019-09-17 09:13 -0400, Greg Wooledge wrote:
> On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
>> What causes systemd-sysv to be installed?
>
> wooledg:~$ aptitude why systemd-sysv
> i udev Depends dpkg (>= 1.19.3) | systemd-sysv
>
> OK... I'll admit, I do not quite understand that dep
On Tuesday 17 September 2019 14:04:30 Thomas Schmitt wrote:
> Hi,
>
> Gene Heskett wrote:
> > I once wrote the "debian-10.0.0-arm64-netinst.iso" to an u-sd card,
> > which booted and did a net-install on an rpi-3b [...]
> > /dev/sde1 /media/sde1 iso9660 ro,relatime 0 0
> > /dev/sde2 /media/sde2 vf
On 2019-09-17 11:10 -0500, David Wright wrote:
>
> Well, the only link *needed* is init, hence its dependency on package
> init, whose sole function is to keep the number of init configurations
> more than zero and less than two.
>
> The rest of those links just mean that I can read, say, a 60 lin
On Tuesday 17 September 2019 13:48:35 John Hasler wrote:
> Looks like you copied the file to the first partition rather than
> writing the image to the raw device (I've made that mistake
> myself). What command did you use?
sudo dd if=debian-10.1.0-armhf-netinst.iso bs=4096 of=/dev/sde
The /dev/
Didier Gaumet, on 2019-09-17:
> Le lundi 16 septembre 2019 21:00:04 UTC+2, Étienne Mollier a écrit :
> [...]
> > does someone know if UEFI
> > prevents unsigned "driver" or "firmware" loading ? (or both?)
> [...]
>
> it forbids it if SecureBoot is activated:
> https://wiki.debian.org/SecureBoot#S
On 9/17/19 11:01 AM, Gene Heskett wrote:
> And that results in exactly the same effect, partitiuon 1 is an iso9660
> image, and I don't believe the rpi-3b supports that for a boot medium.
> dos/fat32 only I believe. Obviously I got those images from the wrong
> place in the debian file system.
On Sun 11 Aug 2019 at 19:55:12 (+0200), to...@tuxteam.de wrote:
> On Sun, Aug 11, 2019 at 07:11:19PM +0200, Mart van de Wege wrote:
> > Felix Miata writes:
> > > Curt Howland composed on 2019-08-09 13:53 (UTC-0400):
> > >
> > >> plymouth-quit-wait.service
> > > ...
> > >> I have no idea what a "p
Hello Debian Team !
I'm the network Administrator of a french High School and I have
troubles debugging a DNS lookup problem affecting all my 550 Debian
Buster clients.
I have two critical systemd services running on my clients :
-> "puppet" that ensure propagation of my whole network configurati
On Tue 17 Sep 2019 at 13:29:16 -0400, Greg Wooledge wrote:
> On Tue, Sep 17, 2019 at 06:25:05PM +0100, Brian wrote:
> > Upgrades from wheezy to jessie did not change the init system because
> > libpame-systemd had the dependency
> >
> > systemd-shim (>= 8-2) | systemd-sysv
>
> https://www.debi
Hi,
Gene Heskett wrote:
> I once wrote the "debian-10.0.0-arm64-netinst.iso" to an u-sd card,
> which booted and did a net-install on an rpi-3b [...]
> /dev/sde1 /media/sde1 iso9660 ro,relatime 0 0
> /dev/sde2 /media/sde2 vfat
> rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortn
Looks like you copied the file to the first partition rather than
writing the image to the raw device (I've made that mistake
myself). What command did you use?
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On Tue, Sep 17, 2019 at 06:25:05PM +0100, Brian wrote:
> Upgrades from wheezy to jessie did not change the init system because
> libpame-systemd had the dependency
>
> systemd-shim (>= 8-2) | systemd-sysv
https://www.debian.org/releases/jessie/amd64/release-notes/ch-upgrading.en.html#issues-sys
On Tue 17 Sep 2019 at 09:13:30 -0400, Greg Wooledge wrote:
> On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
> > What causes systemd-sysv to be installed?
>
> wooledg:~$ aptitude why systemd-sysv
> i udev Depends dpkg (>= 1.19.3) | systemd-sysv
>
> OK... I'll admit, I do not quite under
On Tue 17 Sep 2019 at 10:37:15 +0100, Brian wrote:
> On Sun 15 Sep 2019 at 23:31:23 +0100, Roger Lynn wrote:
>
> > I have three Stretch AMD64 systems with sysvinit - a desktop and laptop
> > running KDE and a headless server. Is there any information available
> > anywhere to tell me what will ha
On Tuesday 17 September 2019 12:45:51 Gene Heskett wrote:
> Greetings to all debian puzzle solvers incorporated;
>
> I once wrote the "debian-10.0.0-arm64-netinst.iso" to an u-sd card,
> which booted and did a net-install on an rpi-3b but my user software,
> linuxcnc was built for armhf and would
Greetings to all debian puzzle solvers incorporated;
I once wrote the "debian-10.0.0-arm64-netinst.iso" to an u-sd card, which
booted and did a net-install on an rpi-3b but my user software, linuxcnc
was built for armhf and would not run.
I'm capable of building that from src, but was not able
On Tue 17 Sep 2019 at 09:45:21 (-0400), Greg Wooledge wrote:
> On Tue, Sep 17, 2019 at 09:40:50AM -0400, The Wanderer wrote:
> > I believe its name was chosen with
> > insufficient consideration, and is not in fact derived from its
> > function.
>
> You're not looking closely enough.
>
> > $ apt-
On 2019-09-17, The Wanderer wrote:
>>> Yes, but unless I'm greatly misunderstanding matters, /sbin/init is
>>> not specific to sysvinit.
>> That's okay, as I never came close to claiming it was. But you focus
>> uniquely upon this "point," while ignoring the part about the "links
>> needed for s
On 2019-09-17 at 09:45, Greg Wooledge wrote:
> On Tue, Sep 17, 2019 at 09:40:50AM -0400, The Wanderer wrote:
>
>> I believe its name was chosen with
>> insufficient consideration, and is not in fact derived from its
>> function.
>
> You're not looking closely enough.
>
>> $ apt-file show systemd
On Tue, Sep 17, 2019 at 09:40:50AM -0400, The Wanderer wrote:
> I believe its name was chosen with
> insufficient consideration, and is not in fact derived from its
> function.
You're not looking closely enough.
> $ apt-file show systemd-sysv
> systemd-sysv: /sbin/halt
> systemd-sysv: /sbin/init
On 2019-09-17 at 09:28, Curt wrote:
> On 2019-09-17, The Wanderer wrote:
>
>>> Why he would say "despite its name" eludes this correspondent,
>>> because the package has *everything* to do with sysvinit,
>>> providing as it does the "links needed for systemd to replace
>>> sysvinit. Installing
On 2019-09-17, The Wanderer wrote:
>> Why he would say "despite its name" eludes this correspondent,
>> because the package has *everything* to do with sysvinit, providing
>> as it does the "links needed for systemd to replace sysvinit.
>> Installing systemd-sysv will overwrite /sbin/init with a
On 2019-09-17 at 09:13, Greg Wooledge wrote:
> On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
>
>> What causes systemd-sysv to be installed?
>
> wooledg:~$ aptitude why systemd-sysv
> i udev Depends dpkg (>= 1.19.3) | systemd-sysv
>
> OK... I'll admit, I do not quite understand that de
On Mon, Sep 16, 2019 at 11:11:33PM +0100, Brian wrote:
> What causes systemd-sysv to be installed?
wooledg:~$ aptitude why systemd-sysv
i udev Depends dpkg (>= 1.19.3) | systemd-sysv
OK... I'll admit, I do not quite understand that dependency. But
what I really need to do is check this on a je
On Tue, Sep 17, 2019 at 07:09:08AM +0100, Tixy wrote:
> Conclusion, to me, it looks like the mainline kernel doesn't yet have
> RPi4 support, and when it does, would anyone want to go to the effort
> to backport that to 4.19? I wouldn't be holding my breath for RPi4B
> support in a Buster netinst i
Hi George,
Quoting George (2019-09-17 11:56:38)
> I noticed when i name a folder in home directory Documents it
> automatically adds a slightly different icon that the normal folder.
>
> I want to have this kind of icon to different place in my directory.
>
> More presicly i want to organize my
Hi there!
I noticed when i name a folder in home directory Documents it
automatically adds a slightly different icon that the normal folder.
I want to have this kind of icon to different place in my directory.
More presicly i want to organize my home folder into 2 subfolder.
One personal folder
On 2019-09-17 at 04:09, Curt wrote:
> On 2019-09-16, Brian wrote:
[that on some earlier date which has been clipped out, someone else -
who happens to be The Wanderer - wrote:]
>>> The dist-upgrade will have resulted in installing the
>>> systemd-sysv package, which (despite its name) has nothi
On Sun 15 Sep 2019 at 23:31:23 +0100, Roger Lynn wrote:
> I have three Stretch AMD64 systems with sysvinit - a desktop and laptop
> running KDE and a headless server. Is there any information available
> anywhere to tell me what will happen when I attempt to upgrade them to
> Buster? The release n
Le lundi 16 septembre 2019 21:00:04 UTC+2, Étienne Mollier a écrit :
[...]
> does someone know if UEFI
> prevents unsigned "driver" or "firmware" loading ? (or both?)
[...]
it forbids it if SecureBoot is activated:
https://wiki.debian.org/SecureBoot#Secure_Boot_limitations
On 9/17/19 2:41 AM, Curt wrote:
On 2019-09-17, Mark Allums wrote:
Well, what you provided in the initial OP was a bit on the parsimonious
side. Now that we know a little more maybe this is the applicable bug
(although it concerns a previous version of the package, and you haven't
said--or have
On 2019-09-16, Brian wrote:
>>
>> The dist-upgrade will have resulted in installing the systemd-sysv
>> package, which (despite its name) has nothing to do with sysvinit; it is
>> the package which sets systemd as the primary / active / default init
>> system.
>>
>> Installing sysvinit-core will
On 2019-09-17, Mark Allums wrote:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923377
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915831
>
> The first doesn't apply, and I don't think the second does, either. See
> my new post in this thread.
Well, what you provided in the
40 matches
Mail list logo
